Database Info

[HOW-TO]Rogers Updating your radio if "you're already rooted"

(removed --> see post #2)

WARNING: This tutorial is for RogersDream users only! It does not apply to G1/dream users. If your wireless telephone carrier is not Rogers, this tutorial is not for you!
This how-to/tutorial's intent is to provide clear/safe/concise steps for Rogers users to keep root, update to the latest RogersRadio & Build and get your data connection back from Rogers, while keeping your root! Since I do not want to dis-rotate on the various potential setups you may or may not have currently installed, this is a start-to-finish guide. Meaning, this guide will work, so long as you are ALREADY ROOTED! If you're not already rooted, <this apparently is not solved yet, sorry>).
The only other note I'll make is that if you currently already have the latest RogersRadio installed (3.22.26.17), the ENG-1.33.2005-SPL and a testkeys recovery image (Amon_RA's 1.5.2R preferred) you may directly proceed to installing a rooted/custom ROM made specifically for EBI1 device layouts.
In order to determine what your RogersDream currently has installed on it, perform the following.
1) Determine Radio & SPL Version.
- PowerOff your phone.
- Press and Hold your Camera button and tap the power button, this will load the bootloader.
- Read the versions, if you see "RADIO-3.22.26.17" and "HBOOT-1.33.2005", then you have the proper radio/spl, if not, perform the steps in this guide.
2) Determine Recovery Image Version.
- PowerOff your phone.
- Press and Hold the Home button and tap the power button, this will load the recovery image.
- If you see "Build: RA-dream-v1.5.2R" at the bottom of your screen, you have the correct recovery image. If you see a Triangle with an "!" mark or you see nothing at all after the Rogers SPLASH SCREEN, perform the steps in this guide.
General Step Sections
1) Backup your phone and sdcard, just to be safe!
2) Charge your battery fully!
3) Gather/Download the prerequisite files/tools, check the MD5's, unpack and copy to your sdcard.
4) Downgrade your RogersDream to gain root and ensure proper EBI1 setup/layout.
5) Install flashrec to install Amon_RA's 1.5.2R recovery image.
6) Upgrade/Convert your SPL to 1.33.2005 ENG, to ensure root going forward.
7) Install Rogers latest Radio Update, version 3.22.26.17.
8) Confirm everything updated correctly.
9) Install Custom/Rooted ROM w/EBI1 kernel support.
THE GUIDE
Section 1) Backup your phone and sdcard, just to be safe!
a) Seriously do this! Backup whatever you deem necessary on the phone, however you see fit. This guide is not meant to walk you through this process. One suggestion though, if you're currently rooted, perform a nandroid backup in recovery, then backup all of your sdcard's contents to a computer. If you need help with this step, search around. If that doesn't help, then perhaps rooting (or this guide) is not for you, perhaps.
Section 2) Charge your battery fully!
a) Seriously do this! Just make sure you have well over 90% battery charge, just to be 100% safe. Also make sure you're battery is very secure during this process, meaning never pull the battery and if you know that your battery is prone to falling out or something like that, fix it somehow b/c you don't want it falling out during this process, k? Nuf Said.
Section 3) Gather/Download the prerequisite files/tools, check the MD5's, unpack and copy to your sdcard.
a) You're going to need adb setup and functioning for section #5, in order to install flashrec w/out a data connection. You *may* be able to get installed via wifi, by downloading it directly from the internet, but don't count on this!!! I will only cover the adb method in this how-to. So get adb installed on your computer and test/make-sure it functions before following this guide! If you don't get adb tested/installed before going through with this guide, you'll be stuck at section-#5 until you do! If you need help with this step, search around. There is plenty of information on xda for getting adb setup and tested.
b) Download this ZIP file, check it's MD5 checksum and make sure it matches the one in this post! If it matches, great!, unpack the contents and copy them to your phone's sdcard. If it doesn't match, redownload the ZIP file. You will need approxiately 114MB of freespace on your phone's sdcard for the unpacked contents.
Rogers_RootUpdate_SDCARD_files.zip
MD5: 013ed64ca02dbebb5e49a8a8474bebe1
I) Files in the zip that need to be copied to your phone's sdcard are ...
--- DREAIMG.nbh
--- ar152r-rec.img
--- rogers_radio_3.22.26.17_update.zip
--- rogers_spl_1.33.2005_update.zip
c) Download this flashrec.apk, check it's MD5 checksum and make sure it matches! Keep this handy on your computer to install with adb later.
flashrec.apk
MD5: 4634f88b8dfdb2332b447c0d85ff4bb6
Secion 4) Downgrade your RogersDream to gain root and ensure proper EBI1 setup/layout.
a) PowerOff your phone.
b) Press and Hold the Camera button and tap the Power button, this will boot into the bootloader.
c) At this point the bootloader should automagically detect the presence of DREAIMG.nbh on the sdcard and prompt you to "update" your phone with the message, "Do you want to start update?". It should say "<ACTION> Yes" and "<POWER> No". Press the rollerball in (this is the action button) to begin the update.
d) The update process will begin (really a downgrade to version 146733-1.85.631.5) ... it will go through the update process, wait till this process is 100% finished! You will be prompted once it is finished, with a reboot prompt with a similar "<ACTION> YES" and "<POWER> NO" prompt. Go ahead and reboot by pressing the rollerball.
e) You are now downgraded and ready to root.
Section 5) Install flashrec to install Amon_RA's 1.5.2R recovery image.
a) Once your phone is booted up, skip through the setupwizard by hitting the series of skip and next buttons.
b) Go into Settings, Applications and check the box for "Unknown sources", press 'OK' at the prompt.
c) Then press the "Development" button and check the box for "USB debugging".
d) Plug your phone into your computer via the USB cable.
e) Install flashrec.apk via adb with the command "adb install flashrec.apk". You should receive a success message and be able to confirm that "Recovery Flasher" is installed by viewing the phone's apps now.
f) Launch the "Recovery Flasher" app.
g) If there is a URL in the textedit box, remove (backspace it) completely. And enter the following
Code:
/sdcard/ar152r-rec.img
This should change the "Download Recovery Image" button into the "Flash Recovery Image" button. If not, make sure you typed the above properly and have that file on your sdcard.
h) Now press the "Backup Recovery Image", which will backup the original image, once it's complete the "Flash Recovery Image" button will enable itself.
i) Press the "Flash Recovery Image" button, which will install Amon_RA's v1.5.2R recovery image. Let it finish, you now have a rooted recovery image installed. Proceed to section-#6.
Section 6) Upgrade/Convert your SPL to 1.33.2005 ENG, to ensure root going forward.
a) PowerOff your phone.
b) Press and Hold the Home button and tap the power button, this will load Amon_RA's recovery image.
c) Use the rollerball to scroll down the "[Alt+F] Flash zip from sdcard" option and press-in on the rollerball.
d) You should see an entry in the list labeled "SDCARD:rogers_spl_1.33.2005_upd", roll the rollerball over this to highlight it and press-in on the rollerball.
e) You will prompted to confirm your selection, ensure the prompt says "SDCARD:rogers_spl_1.33.2005_update.zip" and if so, press the Home button to confirm.
f) It will flash through quickly with a message indicating "Extracting hboot image ..." and then a message saying "Reboot via home+back or menu to complete installation".
g) The rollerball will already have the top option highlighted "[Home+Back] Reboot system now", press in the on the rollerball. You should quickly see "writing hboot image ..." on the bottom ... followed by a quick reboot showing an "HTC" logo ... followed by another reboot which returns to Amon_RA's recovery. Proceed to section-#7.
(SEE POST #3 for Next Steps)

Section 7) Install Rogers latest Radio Update, version 3.22.26.17.
a) Use the rollerball to scroll down the "[Alt+F] Flash zip from sdcard" option and press-in on the rollerball.
b) You should see an entry in the list labeled "SDCARD:rogers_radio_3.22.26.27_", roll the rollerball over this to highlight it and press-in on the rollerball.
c) You will prompted to confirm your selection, ensure the prompt says "SDCARD:rogers_radio_3.22.26.27_update.zip" and if so, press the Home button to confirm.
d) It will flash through quickly with a message indicating "Extracting radio image ..." and then a message saying "Reboot via home+back or menu to complete installation".
e) The rollerball will already have the top option highlighted "[Home+Back] Reboot system now", press in the on the rollerball. You should see "writing radio image ..." on the bottom ... followed by a reboot showing an "HTC" logo for a few moments ... followed by another reboot which returns to Amon_RA's recovery. Proceed to section-#8.
Section 8) Confirm everything updated correctly.
a) At this point you should be back in Amon_RA's recovery.
b) Make sure the rollerball is highlighting the top option "[Home+Back] Reboot system now", then Press and Hold the Camera button, then tap/press-in the rollerball.
c) This will reboot you into the bootloader, at which point the Radio and SPL versions will be presented. If all went well you should now have "HBOOT-1.33.2005 (DREA10000)" and "RADIO-3.22.26.17".
Section 9) Install Custom/Rooted ROM w/EBI1 kernel support.
a) You are now ready to flash a custom ROM w/EBI1 support. If you flash my "TheOfficial Rogers v2.0.1 EBI1", it is a mirror image of everything necessary to get your data turned back on from Rogers. I'm also aware that CyanogenMOD has an EBI1 support/patch for RogersDream users, and I "hear" it works too in terms of not shutting off your data plan.
TheOfficial Rogers v2.0.1-EBI1 can be found here ... http://forum.xda-developers.com/showthread.php?t=556933 .
Simply download the v2.0.1-EBI1 version of the ROM (at the bottom of POST#1), copy it to your sdcard, boot into recovery, perform a data wipe, flash the ROM and reboot. And you'll be all set.
CyanogenMOD for EBI1 ... reference his wiki here ... http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Rogers_Dream_EBI1_to_CyanogenMod ... not 100% sure how the full install goes, but skip to "updating cyanogenmod" section and probe his thread for ROM+gapps installation process, etc. ... or visit them on freenode #cyanogenmod, they're always very happy to help.

Reserved......

Doing it right now! I'll give you an update on how it went. Thank you soooo much!

Is this supposed to work even on Rogers Dream with 1.89.631.1 applied (911 fix)?
I receive the following screen output when trying to flash DREAIMG.nbh:
Main Version is older!
Update Fail!
Do you want to reboot device?​

bt1980 said:
Is this supposed to work even on Rogers Dream with 1.89.631.1 applied (911 fix)?
I receive the following screen output when trying to flash DREAIMG.nbh:
Main Version is older!
Update Fail!
Do you want to reboot device?​
Click to expand...
Click to collapse
Not sure ... I had thought that Haykuro was suggesting it would. Honestly I do not have a personal experience with that update so I can't say for sure. But the message you are receiving would imply that ... what SPL version do you have ?
~enom~

enomther said:
Not sure ... I had thought that Haykuro was suggesting it would. Honestly I do not have a personal experience with that update so I can't say for sure. But the message you are receiving would imply that ... what SPL version do you have ?
~enom~
Click to expand...
Click to collapse
from my HBOOT:
DREAM PVT 32B SHIP S-ON d
HBOOT-1.33.0010 (DREA21000)
CPLD-4
RADIO-3.22.26.17
June 2 2009,21:33:16

bt1980 said:
from my HBOOT:
DREAM PVT 32B SHIP S-ON d
HBOOT-1.33.0010 (DREA21000)
CPLD-4
RADIO-3.22.26.17
June 2 2009,21:33:16
Click to expand...
Click to collapse
Yea ... again not sure ... if you reference (like I did) Haykuro's thread ... here ...
http://forum.xda-developers.com/showthread.php?t=625073
It seemed to me that it was suggesting you could indeed downgrade with that image. The image is one and the same.
EDIT: OK apparently they never found a fix if you're already running the latest non-rooted rogers update. So apparently you need to be rooted already. Sorry 'bout that. I'll update the OP with this information.
~enom~

bt1980 said:
from my HBOOT:
DREAM PVT 32B SHIP S-ON d
HBOOT-1.33.0010 (DREA21000)
CPLD-4
RADIO-3.22.26.17
June 2 2009,21:33:16
Click to expand...
Click to collapse
I updated the OP with this information. Sorry ... the testing Rogers devices I had access to were already rooted. Didn't take enough care to read that entire thread.
Hopefully a solution will be found soon via GoldCard or the like.
~enom~

Upgrade
I just finished my upgrade and I will wait for me data to return. Fingers are crossed!!
Also, acore seems to crash quite often. Is this normal?

AndroidFann said:
I just finished my upgrade and I will wait for me data to return. Fingers are crossed!!
Also, acore seems to crash quite often. Is this normal?
Click to expand...
Click to collapse
Did you wipe before installing the new ROM ? That can cause the acore FC problem if you didn't.
If so ... wipe again in recovery and if you used Apps2SD ...make sure you ext partition is wiped too.
~enom~

Hey, I'm already rooted with CM 1.4's recovery and HBOOT 1.33.2005. Is Amon_Ra and the ENG version of HBOOT really needed or can the Radio just be updated?
Sorry if this has been addressed in other threads already.
Thanks,
Tom

Welll so far, it's working. Now I just have to wait for my data to be restored. Thank you!

anonymoustom said:
Hey, I'm already rooted with CM 1.4's recovery and HBOOT 1.33.2005. Is Amon_Ra and the ENG version of HBOOT really needed or can the Radio just be updated?
Sorry if this has been addressed in other threads already.
Thanks,
Tom
Click to expand...
Click to collapse
I'm really recommending ALL versions match. Really knowing which ROM your running says it all.
If you're running my TheOfficial Rogers EBI0 ... meaning the "original" ROM ... and not the new EBI1 ROM, then you must update.
But simply as the first post states, if you're running an older radio ... such as 2.22.19.26I ... you must follow all of the steps. It's a complete rebuild to get you to EBI1, to support the newer radio.
~enom~

darkspirit386 said:
Welll so far, it's working. Now I just have to wait for my data to be restored. Thank you!
Click to expand...
Click to collapse
Awesome! Not sure if you'll have to beg Rogers to cut back on your data now or not, but once it's on, you should be golden.
~enom~

I am currently running your rogers original. I will update. Quick question however, does Amon_Ra's support SwitchROM? I really love that script!

anonymoustom said:
I am currently running your rogers original. I will update. Quick question however, does Amon_Ra's support SwitchROM? I really love that script!
Click to expand...
Click to collapse
Yes it does, just goto console and type switchrom -s WhateverYouWannaCallIt to save and switchrom -r to restore.

anonymoustom said:
I am currently running your rogers original. I will update. Quick question however, does Amon_Ra's support SwitchROM? I really love that script!
Click to expand...
Click to collapse
Yea it does ... but again ... with moving to an EBI1 setup, your ROM choices will be much more limited now.
I'm only aware of my RogersEBI1 and the CyanogenMOD w/EBI1 kernel patch working. There may be others, I haven't bothered to dig around enough ... but the point is ... limited options, as virtually all of the ROM's in this section are EBI0 ROM's.
~enom~

Thanks shadow (I don't like your avatar)
I need the full exchange support that your ROMs offer. I have been very limited in my choices anyways. Good thing you make excellent ROM's!

[ROM][32b] Official AOSP 2.2 OTA

*** You must be running the 1.6 OTA in order to flash use the SPL (OFFICIAL) section. Otherwise look to the DOWNGRADE TO DONUT or SPL (WORKAROUND) section. ***
SPL (OFFICIAL):
1. Copy this SPL to your sdcard and rename it update.zip
2. Reboot recovery, power off phone, then: home + power, press home + power again to access the menu.
3. Select apply sdcard:update.zip
4. Once finished, let android reboot.
5. Delete the old update.zip and copy the Froyo OTA to your sdcard and rename it update.zip.
6. Reboot recovery, power off phone, then: home + power, press home + power again to access the menu.
7. Select apply sdcard:update.zip
8. Once finished, let android reboot.
9. Delete the old update.zip and copy the Market OTA fix to your sdcard and rename it update.zip.
10. Reboot recovery, power off phone, then: home + power.
11. Once finished, let android reboot.
12. Root here.
DOWNGRADE TO DONUT OTA:
* Make sure to have an engineering (s-OFF) SPL installed. If you don't, use the SPL (WORKAROUND) section to flash clockwork recovery and flash the engineering SPL, then start back here.
1. Download the original COC10 build of Cupcake and the 1.6 OTA and rename the 1.6 update to update.zip.
2. Make sure to have the adb binary on your computer, you can grab it from the SDK under the /tools folder. Grab fastboot here.
3. Copy SAPPIMG.nbh to your sdcard.
4. Boot to fastboot mode, power off phone, then: back + power
5. Select hboot mode, blanking, but I believe it is Volume up, the SPL will scan the sdcard and ask to apply SAPPIMG.nbh, enter <yes> by pressing the trackball.
6. Let it install, and boot to Android. *** DO NOT POWER OFF PHONE OR YOU'LL BE SORRY!! ***
7. Copy update.zip to your sdcard.
8. Power off the phone and enter recovery: home + power, press home + power again to access the menu.
9. Select: apply sdcard:update.zip
10. Congrats, you are now ready to apply the STOCK (OFFICIAL) update.
SPL WORKAROUND (OFFICIAL):
This is assuming you are running stock 1.6:
1. Download Univeral Androot and install it. Once installed, run it and root. Also, download and install busybox from the market. Open busybox and install the 1.18.0git version.
2. Download cm 4.2.15.1 and extract flash_image from /system/bin/
a. This stand alone flash_image may work also.
b. Some users have reported that after rooting, using ROM Manager to flash clockwork recovery has worked, I was never able to get a 100% workable flash on stock, so use at your own risk.
3. Download this SAPPIMG.zip *** DON"T FLASH, DON"T ASK TO FLASH!!! ***
4. Download clockwork recovery from here and rename it recovery.img.
5. Download this engineering SPL and rename it spl.zip.
6. Download Froyo OTA. Rename to update.zip.
7. Extract hboot_7201A_1.33.0013G_091021.nb0 from SAPPIMG.zip.
8. Make sure to have the adb binary on your computer, you can grab it from the SDK under the /tools folder. Grab fastboot here.
9. Enable USB Debugging: Menu -> Settings -> Applications -> Development -> USB Debugging
10. Copy these files to your /sdcard/
a. flash_image
b. recovery.img
c. spl.zip
d. update.zip
11. Now it's time for adb.
Code:
adb shell
su
cp /sdcard/flash_image /cache/
chmod 755 /cache/flash_image
cd /cache
./flash_image /sdcard/recovery.img
12. exit adb, *nix: ctrl + d, Windows: exit, press enter
13. adb reboot recovery
14. You're in clockwork recovery now: Install zip from sdcard -> choose zip from sdcard -> spl.zip
15. You're phone will reboot twice, once done, power off your phone.
16. Press and hold: back + power, this will drop you in fastboot mode with 1.33.2005 and s-OFF.
17. Now we need to flash the new SPL:
Code:
fastboot flash hboot hboot_7201A_1.33.0013G_091021.nb0
18. It should say OKAY, power off the phone.
19. Power on the phone and enter recovery: home + power
20. It will probably be the stock recovery again, press: home + power when in recovery with the exclamation mark. Select: apply sdcard:update.zip
21. Let it finish and reboot. Welcome to froyo!
UPDATES:
Self-Signed Flashable SPL *** Requires Non-stock recovery ***
Official Flashable SPL
Official Flashable SPL Mirror 1
Froyo OTA
Froyo OTA Mirror 1
OTA Market Fix
OTA Market Fix Mirror 1
ROOTING:
Root Me
If you like my work, buy my family and I a pizza. Thanks!
DONATE

mytouch froyo 2.2
i been looking for it too but i cant find it.. maybe they haven't release it yet...
if you find it please post link for it thanks...

dasunsrule32 said:
Please post the link to the OTA for the 32b. Thanks. I will change the thread title as soon as it's posted so we can pull this update and begin hacking. Thanks.
Click to expand...
Click to collapse
You should also explain how to extract the update zip from their phone. I believe it's stored in /system/etc. It'll be something like this
Code:
adb remount
adb shell
cd /system/etc
ls -a
the ls -a command will show you everything in that directory and it most likely won't be called update.zip. it'll have some crazy unneccesarily long name. But you'll know it when you see it. Also don't apply it obviously until you extract it.I wouldn't suggest applying it at all it'll take all of five minutes to add superuser and busybox to it

It is going to be 2 parts. One about 5-10 to download and the other an hour. Will be 2 fer. Needs both lol.
Sent from my T-Mobile myTouch 3G using XDA App

M9x3mos said:
It is going to be 2 parts. One about 5-10 to download and the other an hour. Will be 2 fer. Needs both lol.
Sent from my T-Mobile myTouch 3G using XDA App
Click to expand...
Click to collapse
so you got it on your phone? And that is the eta? that's a hell of a download
is that with wifi

As soon as I can grab the URL's I will post them. Tried unsuccessfully to get the URL from the t-mo csr's.

Asadullah said:
You should also explain how to extract the update zip from their phone. I believe it's stored in /system/etc. It'll be something like this
Code:
adb remount
adb shell
cd /system/etc
ls -a
the ls -a command will show you everything in that directory and it most likely won't be called update.zip. it'll have some crazy unneccesarily long name. But you'll know it when you see it. Also don't apply it obviously until you extract it.I wouldn't suggest applying it at all it'll take all of five minutes to add superuser and busybox to it
Click to expand...
Click to collapse
It would more than likely be downloaded to /cache.

I always like reading customer service stories

1st they said everyone should receive it by the 25th,now it's the 31st?Yeah and I'm waiting for tmo to announce it's been delayed due to some bull**** reason,cause they will.cause that's what tmo does. They strait bull****.I remember them promising us 2.1 for mt3g,never happened.and the poor cliq users are still on 1.5 after countless dates had been set for 2.1 update only to enevitably be canceled,just like this will. That's right tmo you suck and I'm calling your bluff.try to prove me wrong but I know you wont.worst product support of any carrier.Fu tmo Fu.

Jerzeeloon said:
1st they said everyone should receive it by the 25th,now it's the 31st?Yeah and I'm waiting for tmo to announce it's been delayed due to some reason,cause they will.cause that's what tmo does. They strait.I remember them promising us 2.1 for mt3g,never happened.and the poor cliq users are still on 1.5 after countless dates had been set for 2.1 update only to enevitably be canceled,just like this will. That's right tmo you suck and I'm calling your bluff.try to prove me wrong but I know you wont.worst product support of any carrier.
Click to expand...
Click to collapse
Don't spam this thread.

dasunsrule32 said:
Don't spam this thread.
Click to expand...
Click to collapse
That's what she said.

Jerzeeloon said:
1st they said everyone should receive it by the 25th,now it's the 31st?Yeah and I'm waiting for tmo to announce it's been delayed due to some bull**** reason,cause they will.cause that's what tmo does. They strait bull****.I remember them promising us 2.1 for mt3g,never happened.and the poor cliq users are still on 1.5 after countless dates had been set for 2.1 update only to enevitably be canceled,just like this will. That's right tmo you suck and I'm calling your bluff.try to prove me wrong but I know you wont.worst product support of any carrier.Fu tmo Fu.
Click to expand...
Click to collapse
The Cliq was the worst phone ever though, their fault for buying a motorola.

My dad received the update today... as soon as he gets home ill see if i can find the .zip file.

TJ Gonz said:
My dad received the update today... as soon as he gets home ill see if i can find the .zip file.
Click to expand...
Click to collapse
Rock on! Can't wait for that sweet update.
That rhymed.
I might be a poet and I didn't even know it.

I unrooted and been using the MyTouch since yesterday and no update yet

can teh man said:
Rock on! Can't wait for that sweet update.
That rhymed.
I might be a poet and I didn't even know it.
Click to expand...
Click to collapse
Same here. it may be a while, he's a repo man and might be out late.

tj gonz said:
same here. It may be a while, he's a repo man and might be out late.
Click to expand...
Click to collapse
go get the phone and upload a nandroid or something

A couple people on twitter (@daintyyardie @sleepyeyes11) are posting that they have received the update, however they are saying that Market is missing for some reason. I seriously hope this does not delay the update for the rest of us, I can deal without having market in the meantime.

callmeradical said:
A couple people on twitter (@daintyyardie @sleepyeyes11) are posting that they have received the update, however they are saying that Market is missing for some reason. I seriously hope this does not delay the update for the rest of us, I can deal without having market in the meantime.
Click to expand...
Click to collapse
my theory: the update is rumored to be in two parts.
1st part is rom
2nd is gapps
person did something to mess up the 2nd update.

Well both are saying that they are missing market. I doubt both of them messed up the same update. Plus the first update is the smaller one which would be the Gapps, probably only around 17 MBs or so, the second would likely be ~90 MBs for the actual update?

[guide] tmous 1.45.531 + cwm + root

THE HOW TO GUIDE​
This guide will show you how to go from whatever you are on to the TMOUS 1.45.531.1 + ClockWorks Custom Recovery + Root​
The intention of this guide is to create a NOOBPROOF guide so any assistance or guidance in creating such a guide is welcomed
ASSUMPTIONS
This guide is under the assumption that:
1. You have S-Off
2. You have Clockworks 4.0.1.4 (The one with the BLUE writing)
3. You are rooted
4. You have a T-Mobile-branded Sensation
If you don’t have any of the assumptions above, Go to this post and run steps 1 through 3
CHANGES
The T-Mobile OTA v1.45.531.1 changes from T-Mobile
The radio attached with this OTA is 10.56.9035.00U_10.14.9035.01 which is the same version as the 1.45.401.2 OTA/RUU in our European counterparts. Link to radio only is here Read how to flash radio here
The Radio-Interface-Layer or RIL found on this version is HTC-RIL 2.2.0169HMQ which is what is known to compatible with 2.3.4 ROMs and found with the 1.45.401.2 OTA/RUU update in our European counterparts.
DISCLAIMER
ALL TOOLS, DOWNLOADS, LINKS AND OTHER RELATED INFORMATION ARE PROVIDED AS IS WITHOUT ANY WARRANT – EXPRESSED, IMPLIED OR OTHERWISE INCLUDING AS TO THEIR LEGAL EFFECT AND COMPLETENESS.
They are for guidance and should be modified to meet your needs. Use at your own risk.
In most, if not all, cases; these actions void warranty.
PROCEDURES
1. NANDROID BACKUP!! I cannot stress how important it is to backup. Enter CWM and backup! Problems remembering how to start CWR Check out the subsection marked “To Start Clockwork Recovery” of this post
2. Get the RUU_Pyramid_TMOUS_1.29.531.2_Radio_10.42.9007.00P_ 10.11.9007.15_M_release_193714_signed from the Shipped Pyramid ROM Collection. Link to post is here
3. Flash the above file to your phone. Needless to say – THIS WILL WIPE YOUR DEVICE AND PLACE YOU BACK TO STOCK 1.29. PLEASE NOTE! This will NOT remove S-OFF !!
4. On your phone, Go to Settings -> About Phone -> HTC Updates, and press the check now button. It should prompt you to download the 1.45 Update. Download and install the update.
5. Once you have downloaded and installed the update, it’s time to install Clockworks Recovery. Carefully follow the instructions in Step 2 here
6. Once Clockworks Recovery installed and working, just continue with Step 3 in above post or here to get rooted.
7. Once rooted, re-run Revolutionary! Check Step 1 in the above post or here The reason for rerunning Revolutionary is that the OTA update changes the HBOOT so you don’t have all fastboot commands like fastboot flash. This may be necessary when it comes to assistance with other ROMs.
8. NANDROID BACKUP!! – That way you don’t have to do this twice!
9. Press Thanks at the bottom of the post if this has helped you in any way.
NOTES
Revolutionary still works!
Fr3vo Exploit for temp root does NOT work after OTA update!
The biggest SHOUT OUT and THANK YOU to nxt! Without your work, I’d be doing all the research myself lol.
Go to his thread and thank him as well

Reserved for whatever use it may hold

I'm at step 4. The system isn't prompting me to download it, but I already have the .zip on my sdcard from when T-Mobile did prompt me earlier. I can see it, even extract the folders using ES File Explorer but I don't know how to actually launch the installation of this update. I tried rebooting into recovery, thinking I could install it from zip, but I get to the main screen, then I select backup and recovery and it doesn't let me access that. I'm still S-off. Any ideas?
Thank you,
Tim

Figured it out. I was able to get into stock recovery using the up arrow and pwr button. I did have to move the OTA zip file to the root of my sdcard, because for some reason the Download folder wasn't displayed. Currently the update is installing and then I'll rerun the Revolution to get perm root again.
Thank you,
Tim

did you rename the zip i have the same problem?

amorek13 said:
did you rename the zip i have the same problem?
Click to expand...
Click to collapse
No, I didn't rename it, I only moved it to the root of the sdcard, because the Downloads directory wasn't visible for some reason in stock recovery. Once I did that I could see the file and launched it. It updated, I then ran the revolutionary tool to install the Clockworks recovery, and then ran the file that gives the perm root again.
Seems to be working fine, although I haven't seen any incredible advantages to it so far. Perhaps I'll notice the differences after using it for a time.
Thank you,
Tim

[ROM][ICS][STOCK][GT-P5100] ICS 4.0.3 Stock Safe / Recovery / Root (P5100XWALD7)

=========================================================================================
=== Device: GT-P5100 (Galaxy Tab 2, 10.1", 3G model)
=== Description: Safe stock ODIN image, recovery and root
=== Packaged by: cheatman ( xda - http://forum.xda-developers.com/member.php?u=490310 )
=== Stock ROM version: P5100XWALD7
=== Build date: 07 June 2012
=========================================================================================
Disclaimer: I am not responsible and assume no liability on how this information is used. This package is provided "as is" without any warranty and does not guarantee any fitness for any purpose.
ONLY FOR GT-P5100 (3G model)!!! Do not flash on any other Galaxy Tab 2!!!
Download the ZIP (large, about 600MB) from here:
=> DOWNLOAD FROM HERE (HotFile)
How to use: Read the readme.txt file or this post here.
On to the safe stock restore process:
1. Make sure you have the Samsung device drivers installed before you begin. If you don't, install them from here:
- 64bit: http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x64.shtml
- 32bit: http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x86.shtml
2. Make sure your tablet's battery is at least 30% charged up before you begin.
3. Make sure you have an external microSD inserted in the device, if you also plan on rooting afterwards. Nothing will be erased from the microSD, there is no need to worry about that.
4. Run procedure to flash back the stock ROM from Samsung (Ice Cream Sandwitch 4.0.3 - P5100XWALD7) from the folder "Step1-Stock". STOP HERE FOR PURE STOCK!!!
5. Run procedure to enable ClockworkMod recovery from the folder "Step2-Recovery". This step is OPTIONAL (only if you want a custom recovery). STOP HERE IF YOU DON'T WANT ROOT!!!
6. Run procedure to enable "root" access from the folder "Step3-Root".
7. Done! Enjoy! Profit!
===============================================================
========== Step 1 - Flashing Stock P5100XWALD7 ================
===============================================================
1. Download the file from the link above.
2. Shut down your tab.
3. Disconnect tab from USB and/or power cables.
4. Hold "Power+Volume UP" physical buttons on your tablet to initiate download mode.
5. Press "Volume DOWN" physical button on your tablet to confirm and enter ODIN mode.
6. On your PC, open "Odin3 v1.85.exe"
7. Press "PDA" button in ODIN and select the "PLATFORM_P5100XWALD7_482645_REV02_user_low_ship.tar.md5" file.
8. Press "PHONE" button and select the "MODEM_P5100XXLD7_REV_01_CL1128355.tar.md5" file.
9. Connect your tablet using a USB cable. In ODIN you should see the device "<added>" message appear. If you do not, there is a problem with the Samsung drivers installation.
10. Confirm that only the following options are checked in ODIN: "Auto Reboot", "F. Reset Time", "PDA", "PHONE". DO NOT CHECK RE-PARTITION!!! NEVER!!!
11. Click the big "Start" button and WAIT. Be patient!!! The process takes about 3-4 minutes but can take longer.
12. Do not power down the tablet while this takes place. Do not shut down your PC. Do not touch anything! Just wait! Get a coffee or something...
13. After full flash the tablet will reset automatically.
14. Congratulations you are now safely back to stock P5100XXALD6.
15. There is no need to flash the bootloader and CSC. Do so at your own risk.
===================================================================
========== Step 2 - Flashing ClockworkMod Recovery ================
===================================================================
1. Download the attached recovery file "p5100-recovery.tar.md5.zip" and extract it.
2. Shut down your tab.
3. Disconnect tab from USB and/or power cables.
4. Hold "Power+Volume UP" physical buttons on your tablet to initiate download mode.
5. Press "Volume DOWN" physical button on your tablet to confirm and enter ODIN mode.
6. On your PC, open "Odin3 v1.85.exe"
7. Press "PDA" button in ODIN and select the "p5100-recovery.tar.md5" file.
8. Connect your tablet using a USB cable. In ODIN you should see the device "<added>" message appear. If you do not, there is a problem with the Samsung drivers installation.
9. Confirm that only the following options are checked in ODIN: "Auto Reboot", "F. Reset Time", "PDA". DO NOT CHECK RE-PARTITION!!! NEVER!!!
10. Click the big "Start" button and wait a few seconds. Flashing recovery.img is super-fast!
11. After recovery flash, the tablet will reset automatically.
12. Congratulations you are now running recovery for your tablet.
13. Note: Internal SD is not working with this recovery, you must use external microSD cards to load up ZIPs.
14. You can also download and extract the kernel and flash it also on "PDA" if you want a rooted Kernel
=========================================================
========== Step 3 - Enabling root access ================
=========================================================
1. Download the attached file "CWM-root-P5100-v1.zip".
2. Copy the "CWM-root-P5100-v1.zip" file to the external microSD card.
3. Shut down your tab.
4. Insert the microSD in the tablet.
5. Hold "Power+Volume DOWN" physical buttons on your tablet to initiate recovery mode. It takes a while to start up recovery (10-15 seconds) so be patient. Try not to press too hard on the buttons as it does not help at all (takes same amount of time :-D)
6. Use the "Volume UP" and "Volume DOWN" buttons to navigate (select options) and the "Power" button to select. Don't HOLD the buttons, just press them (like a click or something).
7. Select the option to install ZIP from sdcard.
8. Navigate to where you copied the "CWM-root-P5100-v1.zip" file and select it.
9. Wait for the operation to complete.
10. Navigate back and select option to "Reboot system"
11. Congratulations you have a fresh stock ROM with CWM and root ready to go!
12. Enjoy
=======================================================================================
Thanks and greetings go to:
- Galaxian-Soup
- nycbjr
- All others who help and bring value to the XDA comunity!
Peace and have fun!
C.

Reserved!
Looking for mirrors. This is a very large file!
Thanks.

Ah damnit lol this was almost what i was looking for. I need the one for the wifi version.
Do you think the recovery would be the same? Thats the only part i really need lol.
Nvmind i see its all in one file lol

Recovery is in an independent folder, you don't flash the initial zip lol.
Anyway, the recovery and root steps should apply to p5110 as well.
Cheers,
C.

Thank you for all the hard work. I'm sure my Willy nilly ways will require me to use this
Sent from a note on fire in the middle of the sea

Hi,
I see that in your instructions for flashin stock do not use file "BOOTLOADER_P5100XXALD6_365113_REV02_user_low_ship. tar.md5" which is otherwise included in the package, does that mean that it did not necessarily use one?
When it is necessary to use that file?
Thanks.

Updating the bootloader is not required.
Playing with bootloaders is very risky and dangerous in general (can permanently brick tab).
Bootloader is responsible for the download mode. If you can access it and flash using odin, there is no need to mess with it. Upgrading it may result in a locked boot mode, meaning you can't flash custom stuff anymore.
I included only the required files and steps so you guys don't have to look for the right combination.
Peace,
C.

Thank you for the file sir oh sir.
Rapidshare mirror
Sized at 492.65MB, i recompressed the file using 7-zip to cut off the size a bit. It is below 500MB, meaning it's Dev Host friendly.
Code:
stock-safe-p5100-4.0.3-v1.zip 2E5566F2311BAD666A8CFD9674AEE0A5
stock-safe-p5100-4.0.3-v1.7z 946AAC1EDE408FFCA48BAF592AC3F92C
Step1-Stock
MODEM_P5100XXLD6_REV_01_CL1128355.tar.md5 07EFC235DC6989D50C9321076EDCDFC1
PLATFORM_P5100XXALD6_365113_REV02_user_low_ship.tar.md5 8186B1660ED2D4C1752336014ED047FD
Step2-Recovery
recovery.tar.md5 16AFDD2FEDBD8476521D9C144C823023
Step3-Root
CWM-root-P5100-v1 4D2E472F0C0A640F4170B9500F39FCAC
Can someone please confirm the hashs?

I rooted my Galaxy Tab 2 10.1 WiFi GT-P5110 using the manual and it works fine!
Thanks for the manual
Sent from my r00t3d GT- P5110 using XDA Premium App

Updated new version of the stock image.
Thanks for this find go to our friend "zi0m3k" (cheers, mate!)
C.

How did you capture the stock recovery from the device? I would like to do the same from my GT-P5113, but (of course) one has to flash CWM first to get access, and that overwrites the recovery.

Stock recovery comes with the stock ROM, so you need to overwrite it, not capture it.
But, to clarify the issue, you can root your device without a custom recovery. After you root, you can dump system images using the "dd" command.
Rooting using CWM zips is just more convenient and easier for everyone, it's not the only option, though. There was root before recovery...
C.

cheatman said:
Stock recovery comes with the stock ROM, so you need to overwrite it, not capture it.
But, to clarify the issue, you can root your device without a custom recovery. After you root, you can dump system images using the "dd" command.
Rooting using CWM zips is just more convenient and easier for everyone, it's not the only option, though. There was root before recovery...
C.
Click to expand...
Click to collapse
I know that the final goal is to overwrite the recovery to get the benefits of CWM (e.g.). But if you want to save the *stock* recovery first, you need to capture/dump it from the device somehow before flashing (correct me if my logic here is incorrect).
Also, yes, I know a good way to dump it is with "dd", but one needs root to do that (I tried for the hell of it, to see if there was non-root read access, but alas, no).
I think you have hit upon my question regarding root: did you root the tab without flashing CWM? If so that will allow "dd" to capture the stock recovery, yes. If you used CWM, that you overwrote the recovery, and you would not have been able to save the stock recovery in that case.
I have not found a rooting method for the GT-P5113 that does not involve flashing CWM, so I cannot figure out how to same my stock recovery, which I would like to do before flashing CWM (and thereby losing the stock recovery forever).

I obviously dumped the recovery before I flashed CWM, otherwise it wouldn't be stock.
If I get you right, you want to know the root exploit I used to root my p5100 to get suid and be able to copy the "su" binary. In fact, getting elevated rights on a linux system if you have direct access to it is not rocket science. However, because that's a lot to write, here is a more simple solution you can apply to get a stock recovery that I didn't have at the time:
1. Go to samfirmware.com and download a stock rom for your device.
2. Extract the .tar.md5 files and get the "recovery.img" out of them. Usually the "boot" and "platform" files have one inside.
I reckon all p51xx devices have the same recovery anyway, but it might not be the case.
C.

cheatman said:
I obviously dumped the recovery before I flashed CWM, otherwise it wouldn't be stock.
If I get you right, you want to know the root exploit I used to root my p5100 to get suid and be able to copy the "su" binary. In fact, getting elevated rights on a linux system if you have direct access to it is not rocket science. However, because that's a lot to write, here is a more simple solution you can apply to get a stock recovery that I didn't have at the time:
1. Go to samfirmware.com and download a stock rom for your device.
2. Extract the .tar.md5 files and get the "recovery.img" out of them. Usually the "boot" and "platform" files have one inside.
I reckon all p51xx devices have the same recovery anyway, but it might not be the case.
C.
Click to expand...
Click to collapse
Hi, yes, that's exactly right - I wanted to know how you got elevated rights in order to use dd for this.
I really want the recovery image from *my* stock tablet - not one off the net.
Could you private message me, if you are uncomfortable talking about it here. I am well-versed in Linux (I've done kernel development, I'm part of the Gentoo Linux dev team, etc.), so I am no stranger to Linux. I know there are exploits now and then, but they are not usually trivial. If you found a new one for the current kernel, then I'm impressed, and please do tell. If you found the exploit somewhere on the net, can you send me a link?
Thanks, Joe

Well, I must admit I actually took my time thinking whether I should actually write a reply :-D
However, my main concern is having to write a lot to explain stuff, but considering you are a kernel dev, this should be easy peasy. In short, I didn't force my way in, I just *convinced* the system to let me in. It's an inherent problem of Android, in fact:
1. Extracted the boot.img and unpacked it.
2. Replaced the adbd binary in the ramdisk with an unsecure one.
3. Repackaged and flashed using ODIN.
4. Used adb root to get into the system, the *regular* way. Once adbd lets
5. Installed su and superuser.apk.
There is no need to exploit the kernel if the system is inherently flawed when it comes to direct access (adb root exists). Any and all Android devices that use this layout (boot.img) can be rooted this way. Sorry to disappoint you about the exploit, but I am no *real* dev. I just know my way around :-D
PS: You can get the latest boot.img I did for this purpose here
Hope it helps with your recovery dump,
C.

cheatman said:
There is no need to exploit the kernel if the system is inherently flawed when it comes to direct access (adb root exists).
Click to expand...
Click to collapse
Very interesting - that was my missing piece of the puzzle - I had not realized one could replace the adbd. Makes sense. I will certainly give this all a try! I may be experienced with Linux, but I have a lot less background in android internals; learning quickly, though. In fact, my next project (when I get some time) is to try building the GT-P5113 ROM from source (and also some delving into AOSP). Being able to customize at the source level would be very cool.

LavaJoe said:
Very interesting - that was my missing piece of the puzzle - I had not realized one could replace the adbd. Makes sense. I will certainly give this all a try! I may be experienced with Linux, but I have a lot less background in android internals; learning quickly, though. In fact, my next project (when I get some time) is to try building the GT-P5113 ROM from source (and also some delving into AOSP). Being able to customize at the source level would be very cool.
Click to expand...
Click to collapse
I would be eternally grateful if you could post the stock rom for the 5113 (including stock recovery) if you can. I would settle for just the stock recovery in flashable form via odin etc.

A read through Samsung's kernel source reveals that the governors are already coded into the kernel (install voltage control and you can switch between governors and schedulers at will).
It looks like the set stock speed on the 10.1 5113 is 1008MHz.
Does anyone know how/where in the kernel overclocking is programmed?
The source also looks pretty comprehensive for the tablet and apparently is very similar to that of the 7" tab. I imagine it wouldn't be too hard for a veteran coder to fix this up for the 10" users.
I haven't coded in years and I'm not familiar enough with Android to do anything but attempt to compile the source from Samsung.

Hi,
Does this work on P5100XXLD6 ?
Android version 4.0.3
Thanks

Need help with TF700T with Katkiss 6.0 installed

I recently bought a second hand TF700T that has been rooted with Katkiss 6.0 but it has numerous problems that I need to know which is the best way to resolve. This is what I have:
Model: TF700T
Android Version: 6.0.1
Kernel Version: 3.1.10 katkernel-tf700
Build: Katkiss-024.6.0.1
ClockworkMod Recovery v6.0.4.7
The problems I have are:-
1. It has no Play Store and I am able to download the apk file but 'can't read/open' so it won't install from download (yes I have allowed apps from unknown sources). I managed to pull the apk file using ADB but the Play Store simply opens and closes a white page.
2. If I go to settings there is a SuperSU – clicking on it I get 'Unfortunately, settings has stopped'. I don't think this should happen. I don't know how to check if Super SU Beta 2.52 is installed.
3. If I go to Accounts I have Personal (IMAP) and + Add Account where I only have Exchange and Personal (IMAP). So I can't seem to be able to select a Google Account.
Presently I have nothing on the tablet I need (i.e. no data I need to keep) so if I have to start again I am happy to do that but I'm just learning so saying 'flash the rom' or such is too vague for me at this stage. I'm also not sure what or how to get 'data as f2fs' if that is important.
If someone could assist with a clear step by step of how I might resolve these issues I'd be very grateful. Happy to provide any other info sought. Not sure if this was caused when the seller wiped his personal data before selling or what, he says Play Store was working, so don't know if he bungled the rooting or what.

I got your PM and first of all, congrats you did a good amount of reading and you are on the right track.
Your problems with Google account and Play Store are probably due to either the wrong gapps (Google apps) version or the previous owner did a wipe of /data and did not reflash properly. Yep, arm 6.0 is right, but it has to be the pico edition. Since you did buy the tablet used, it probably would be a good idea to start from scratch. At least you would then know that if something won't work, it's because of something you did.
And yes, I agree with the advice to flash the Kang TWRP recovery. I have no idea if CWM supports f2fs but I don't think so. Most people use TWRP as recovery - it's the right way to go.
So let's get you prepped:
Download the rom, gapps and SuperSU from the links in Tim's thread (first post) and put them on a microSD. http://forum.xda-developers.com/transformer-tf700/development/rom-t3282166
Then head here and download the flashable zip of the Kang TWRP recovery: http://forum.xda-developers.com/showpost.php?p=59299365&postcount=2
Also copy that to the microSD
Boot into CWM recovery, go to Install and navigate to the Kang TWRP zip.
To tell the truth I can't even remember if CWM supports the microSD but I think it does. If it doesn't you have to use adb to push the zip to internal memory and then flash it from there.
Anyway, flash the Kang TWRP and then reboot. Let it boot up, then turn the tablet off and boot via buttons (Power and Vol Down to get into bootloader, VolUp on flashing RCK) into recovery which should be TWRP at this time.
Go to Wipe > Format data > type "Yes" and go have a beer (did I mention the battery needs to be full before you start?). This will take 60 minutes plus and may look as if nothing happens but it does, don't mess with it!
Once that is done follow this guide to convert internal data to f2fs: http://forum.xda-developers.com/tra.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
Start at step 4 and ignore any instructions related to data2sd/rom2sd.
Alright, now you got a squeaky clean tablet itching for a rom.
In TWRP go to Install > navigate to the microSD and select the rom zip. If you like, you can line up the other two files to be flashed right after the rom zip:
Touch: Add another zip, and repeat this for both the gapps and the supersu zips.
Or you flash them one by one - doesn't matter. But all 3 have to be flashed without rebooting in between and the rom has to be first!
Make sure "verify zip signature" is not checked, then swipe the button.
Have another beer
Once it's done, reboot to system and set up your new rom.
You definitely want to install the SuperSU app from the Play Store. You gain root by flashing the SuperSU zip, but you need the app to manage root.
If anything is unclear: Ask!
Have fun!

I'm up to the part where I get to have a beer...haaa. Wasn't all plain sailing. Having TWRP as an img file wasn't recognised on the sd card so I was unable to flash twrp that way. I managed to push twrp using ADB. (The small issue I had here originally was when I renamed the img file from say twrp-2.8.x.x-xxx.img to twrp.img (for ease of typing in adb) it was really twrp.img.img as it appears with a zip icon on my XP. After realising this it was straightforward after putting twrp.img into the adb folder and connecting the device and accessing the command prompt:
C:\adb>adb devices (to check I'm connected)
response:
List of devices attached
(numbers&letters here) device
C:/adb>adb reboot bootloader
This reboots the device into the bootloader and you hear the device buzz
C:/adb>fastboot flash recovery twrp.img
response
sending 'recovery' (7038kb)
Okay
writing 'recovery'
Okay
finished total time etc
then
c:/adb>fastboot reboot
rebooting....
I then used the power vol down buttons and yahoo I'm in TWRP and currently at the wipe data phase.
Can't tell you how much I appreciate this help and I'll repost a report after I get further along. Hope this helps others also.

Unexpected Clean Android waiting for a ROM
Beers were great. I finished the bit of 'convert internal data to f2fs' and thought when I rebooted, well don't know what I expected but 'squeaky clean tablet itching for a rom' wasn't a still present KatKiss rom logo start but that's what happened. Then I went to 'Install > navigate to the microSD and select the rom zip' and nothing on the SD card seemed to be recognised other than a self created 'LOST.DIR' directory so I copied the files into this directory ( Heh, at least it can see this directory). So I'm now in the process of installing KatKiss, Gapp 6 pico and SU User Beta.
If I'm on the wrong track here please let me know. Cheers
Paul;

No, you're doing good. You formatted /data, so did not touch /system where the rom lives. That's why your old room still boots. /system gets formatted during installation of the new rom = squeaky clean.
Sent from my Nexus 5X using Tapatalk

berndblb said:
No, you're doing good. You formatted /data, so did not touch /system where the rom lives. That's why your old room still boots. /system gets formatted during installation of the new rom = squeaky clean.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I've completed all the instructions - changed data to f2fs and then starting with the Katkiss, then Gapp pico and SuperSU (adding one zip after the other) and rebooted. Rebooted and device installed 73 apps and took me to a welcome screen with a language dropdown and a swipe button. I can access and change the language but the swipe button won't work so I'm locked on this screen. I went back to TWRP and pressed 'reboot' but what happened was the reboot button(located bottom right), settings button above it and the two bottom buttons on the left disappeared... so from there it wouldn't reboot. I had to hold the power button down to reboot and back in the flash screen but still can't get past that.

plato2 said:
I've completed all the instructions - changed data to f2fs and then starting with the Katkiss, then Gapp pico and SuperSU (adding one zip after the other) and rebooted. Rebooted and device installed 73 apps and took me to a welcome screen with a language dropdown and a swipe button. I can access and change the language but the swipe button won't work so I'm locked on this screen. I went back to TWRP and pressed 'reboot' but what happened was the reboot button(located bottom right), settings button above it and the two bottom buttons on the left disappeared... so from there it wouldn't reboot. I had to hold the power button down to reboot and back in the flash screen but still can't get past that.
Click to expand...
Click to collapse
Heck! I did not think we needed to check your bootloader if it had Katkiss on it, but now I think we do:
Boot into fastboot and read the tiny text top left. The part with 10.6.1...... is what we need

Bootloader problem now! More beer required....
berndblb said:
Heck! I did not think we needed to check your bootloader if it had Katkiss on it, but now I think we do:
Boot into fastboot and read the tiny text top left. The part with 10.6.1...... is what we need
Click to expand...
Click to collapse
OK, I went back to the wipe data bit and did it all again.... I noted that when installing the Katkiss, Gapps and SuperU zips I saw 2 lines:
checking for md5 file
skipping md5 check: No md5 file found
Have no idea if it matters or not....
OK the tiny writing at top on fastboot (why does this have to be so small....really).
Anyway it says:
Key Driver not found.. booting as
Android CardHU-User Bootloader <2.0 e> released by "ww_epad-10.6.1.14.10-2013601" A?3
It is hard to be exact with it that small so hope that helps, but the 10.6.1.14.10 is correct can't be as sure with the last numbers though.

Thinking about a solution
plato2 said:
OK, I went back to the wipe data bit and did it all again.... I noted that when installing the Katkiss, Gapps and SuperU zips I saw 2 lines:
checking for md5 file
skipping md5 check: No md5 file found
Have no idea if it matters or not....
OK the tiny writing at top on fastboot (why does this have to be so small....really).
Anyway it says:
Key Driver not found.. booting as
Android CardHU-User Bootloader <2.0 e> released by "ww_epad-10.6.1.14.10-2013601" A?3
It is hard to be exact with it that small so hope that helps, but the 10.6.1.14.10 is correct can't be as sure with the last numbers though.
Click to expand...
Click to collapse
I've done a bit of reading and I'm currently downloading ww_10_6_1_18_SDupdate.zip
I think my next step will be to unzip this file and find the T4_SDupdate file and put it on the sdmicro in root and boot into recovery. I'm guessing it will be located and the update begin. After that I'm not sure of what to expect. Will I have to go and flash twrp, wipe date, change to f2fs and install Katkiss,Gapps and SuperSU again? Will it matter if other files (TWRP, Katkiss, Gapps,SuperSU) are also on the microsd while this happens. If you could let me know if I'm on the right track that would be great.

plato2 said:
I've done a bit of reading and I'm currently downloading ww_10_6_1_18_SDupdate.zip
I think my next step will be to unzip this file and find the T4_SDupdate file and put it on the sdmicro in root and boot into recovery. I'm guessing it will be located and the update begin. After that I'm not sure of what to expect. Will I have to go and flash twrp, wipe date, change to f2fs and install Katkiss,Gapps and SuperSU again? Will it matter if other files (TWRP, Katkiss, Gapps,SuperSU) are also on the microsd while this happens. If you could let me know if I'm on the right track that would be great.
Click to expand...
Click to collapse
Sorry, that should be 22_10_26_1_18_SDupdate.zip

plato2 said:
Sorry, that should be 22_10_26_1_18_SDupdate.zip
Click to expand...
Click to collapse
Third time luck...(should be) ww_10_26_1_18_SDupdate.zip

plato2 said:
Third time luck...(should be) ww_10_26_1_18_SDupdate.zip
Click to expand...
Click to collapse
Don't do that!!
Whatever it is that is not firmware for the TF700!
You are on the latest bootloader, no reason to mess with it!!
---------- Post added at 09:29 AM ---------- Previous post was at 09:28 AM ----------
Give me some time, I'll get back to you
Sent from my Nexus 5X using Tapatalk

That was TF701 firmware you were thinking to flash. It is totally incompatible with your tablet and the T4 SD Update method works only with stock recovery. But all that aside....
Ok, what you experience is quite weird and I have no idea what caused it. Maybe a bad download maybe something went wrong during the flash - I have no idea...
So what is your situation now? Can you reboot from TWRP? Does the recovery work normally?
Because if not, that is the first thing you need to fix.
You may want to reflash TWRP anyway - just to be sure it did not get corrupted. You know how to flash in fastboot - excellent! Then let's do it that way.
Download from the first link for Kang TWRP 2.8.7.4. https://www.androidfilehost.com/?fid=24352994023705509
Look at the info under "Download information" on that page: You'll see the md5 checksum for that file. That is control value to make sure the file you downloaded is complete and not corrupted.
You'll need a small program like Hashtab on your PC to check the md5. Install it, then right click on a zip, go to Properties and there you'll see a new tab: FileHashes. Copy the string from the download page into the "Compare" box and it instantly tells you if the file you have on your PC matches the one on the server. TWRP has a feature that it will compare the md5 if you have it along with the zip in form of a small text file on your microSD. If it doesn't find a md5 it just skips the integrity check.
Your microSD - something else to check. That TWRP doesn't see the downloaded files unless they are in the LOST directory is totally crazy. How is that microSD formatted? You got another one you can use? One that actually works and does not add another question mark to this situation? If not, at least format the microSD to fat32 on your PC, load your files and then check if TWRP sees them. Also check the md5 AFTER copying the files to the card.....
Do that with all the files you downloaded.
So, first thing is to flash TWRP again. Then make sure it works, you can reboot from it etc.
Then just perform a quick wipe in TWRP. From Home select Wipe > swipe the button > done
Then reflash the rom zip, gapps and supersu on which you checked the md5.
Let me know how that goes.....

Thanks for that info. No I wasn't going to do anything stupid without you OKing it first.
I redownloaded Kang TWRP 2.8.7.4 and pushed it again successfully with adb no problem. I am still unable to reboot from bootloader using adb or pressing reboot... these problems weren't present prior to installing Katkiss, Gapps and SuperSU. Still frozen on front screen of rom. I put the twrp.img file onto the micro SD Card and tried to flash. It gives me an option to select staging which I didn't tick so it tells me no partitions selected for flashing. Didn't want to tick something and stuff it up. I think TWRP is OK as it did work fine before I installed the other 3 programs.
The micro SD is fine it's FAT32 formatted. The issue with the recovery program not seeing the zip files in the root dir was when I was using CWM - no longer a problem.

plato2 said:
Thanks for that info. No I wasn't going to do anything stupid without you OKing it first.
I redownloaded Kang TWRP 2.8.7.4 and pushed it again successfully with adb no problem. I am still unable to reboot from bootloader using adb or pressing reboot... these problems weren't present prior to installing Katkiss, Gapps and SuperSU. Still frozen on front screen of rom. I put the twrp.img file onto the micro SD Card and tried to flash. It gives me an option to select staging which I didn't tick so it tells me no partitions selected for flashing. Didn't want to tick something and stuff it up. I think TWRP is OK as it did work fine before I installed the other 3 programs.
The micro SD is fine it's FAT32 formatted. The issue with the recovery program not seeing the zip files in the root dir was when I was using CWM - no longer a problem.
Click to expand...
Click to collapse
There's some fundamental flaw in your thinking: You cannot flash the .img file in TWRP.
twrp_tf700t_kang_2.8.7.4.img - this file you have to flash in fastboot (fastboot flash recovery twrp_tf700t_kang_2.8.7.4.img)
twrp_tf700t_kang_2.8.7.4-signed.zip - this is the same recovery packaged into a flashable zip. This you can flash in recovery
I am still unable to reboot from bootloader using adb or pressing reboot... these problems weren't present prior to installing Katkiss, Gapps and SuperSU
Click to expand...
Click to collapse
You mean rebooting from recovery??? That sentence does not make sense. And something else is going on. Flashing a rom, gapps, supersu cannot have anything to do with your recovery not working properly. The recovery lives on it's own partition and boots from there.
Maybe time to take a break and retrace your steps. I cannot put my finger on it but somewhere you are doing something wrong.
Edit: Ha! Interesting! Just remembered that something changed in TWRP and yes, this latest version lets you flash an .img file to staging (from where it will get installed to it's proper partition during the next boot). I have no idea how solid this new feature is, so I'd still recommend falshing TWRP in fastboot.
But 2.8.7.4 works fine flashing Katkiss and associated files. Tried it myself this afternoon. All the components work. So the problem is most likely in the "how", not the "what".....

Sorry for the confusion. Really can't see what I may be doing wrong here. I followed exactly the same procedure as I did when I installed TWRP over CWM initially. I re-downloaded twrp_tf700t_kang_2.8.7.4.img , placed it in the adb folder and renamed it twrp.img. I then followed the same procedure I did originally:
C:\adb>adb devices (to check I'm connected)
response:
List of devices attached
(numbers&letters here) device
C:/adb>adb reboot bootloader
This reboots the device into the bootloader and you hear the device buzz
C:/adb>fastboot flash recovery twrp.img
response
sending 'recovery' (7038kb)
Okay
writing 'recovery'
Okay
finished total time etc
then
c:/adb>fastboot reboot
rebooting....
However, this time the response to the last command:
c:/adb>fastboot reboot
(waiting for device) and it hangs and the device doesn't reboot from recovery. However, all the other stuff before it is the same. Not sure what to try next.

plato2 said:
However, this time the response to the last command:
c:/adb>fastboot reboot
(waiting for device) and it hangs and the device doesn't reboot from recovery. However, all the other stuff before it is the same. Not sure what to try next.
Click to expand...
Click to collapse
Elaborate on this please.
You are in fastboot.
The command fastboot reboot does nothing?
Then what? Did you reboot manually?
You are not in recovery here, so i do not understand "the device does not reboot from recovery".....

Sorry, my lack of understanding. I suppose I mean I am in the bootloader which is where adb>reboot>bootloader puts me so that I can flash twrp.img. Then to get out of there and go back to the rom fastboot>reboot would put me back into the rom and I would get the response >rebooting. Now that doesn't happen it simply says (waiting for device)....So I have to reboot manually.

Just got home and playing around with it. I went into the bootloader and installed just the katkiss rom. It installed fine and then I clicked reboot and it rebooted no problem. But of course that doesn't give me any Play Store or SuperSU.... so there's still hope. So now I'm back in the bootloader and going to try the 3 together again and see what happens.Let you know shortly

Setup wizerd stopped - google play services stopped
plato2 said:
Just got home and playing around with it. I went into the bootloader and installed just the katkiss rom. It installed fine and then I clicked reboot and it rebooted no problem. But of course that doesn't give me any Play Store or SuperSU.... so there's still hope. So now I'm back in the bootloader and going to try the 3 together again and see what happens.Let you know shortly
Click to expand...
Click to collapse
So now when I install the katkiss, Gapps and SuperSU from TWRP and reboot I get 2 repeating messages Setup wizerd has stopped' and Google Play Services has stopped. It just goes from one to the other when I press OK....