Database Info

[GUIDE] Official [unroot] guide here

I have seen a lot of unfinished info on UNROOTING so rather than see a bunch of people stuck like I was last night I thought I would toss a little guide together for everyone.
I take no credit for any guides I post just pitching in, if I help you CLICK me a THANKS!
download the asus firmware from here: http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF101/UpdateLauncher_US_epad_user_8239.zip
extract the blob from the zip file and put it in your adb folder located at something like:
AndroidSDK/platform-tools/
as you did to root the device.
open cmd promt window type the following and return after each.
\cd
\cd AndroidSDK\platform-tools\
adb devices
*adb your device make sure it is hooked up and id'ing your transformer.*
adb push blob /data/local
adb shell
*at the # type the following*
dd if=/data/local/blob of=/dev/block/mmcblk0p4
*wait a few mins to be safe*
now reboot the device, on reboot you should see a progress bar indicating the flashing of the “blob” file. this will remove the clockwork recovery and put your tablet into BOOTLOOP this is ok.
----------------------------------------------------------------------------------
-----------------------------------------------------------------------------------
Now that your tablet is stuck in a boot loop, put on the root of the micro sd card on your computer-> the update normally found in the asus/update/ folder from the firmware zip you download from asus. I used the .9 US update and it worked fine, you must then rename it to EP101_SDUPDATE.zip make sure you leave it a zip dont change the extension AND->make sure it is on the root of the card.
Now put your card in your transformer, hold the down volume and power till it prompts you in the upper left about wiping or booting to recovery**> let go and push up on the volume, which will load the factory recovery android with a box and a loading bar *** IF IT IS STILL CLOCKWORK RECOVERY THEN YOU MISSED SOMETHING START OVER DO NOT CONTINUE***> it will begin to flash the update do not bother it turn it off or anything else will take up to 10 mins to complete. it will restart and you will see the bar load again on boot up then it will boot to the asus logo and then to the homescreen and your good.
-Ian

Faved for later use when INeed to RMA
Sent from my Transformer TF101

I don't have .12 for you, but here is a link to .9 (That's the one that really matters anyway right?). I would appreciate a link to .12 just for my OCD.
V8.2.3.9(US)
http://db.tt/EEElFqP
If you could please rehost it somewhere.

Thanks for this. I have been holding off trying to root my Tablet until I had some clear indication that there would be a "way back".
I will PM you a link to V8.2.3.9 US Firmware as soon as it's done uploading to MegaUpload (Aborted as someone beat me to it)

I haven't found a need to root my TF yet as all I need for it is running pretty smoothly.
My phone on the other hand gets flashed with a new ROM every few days.
Great to know that I can go back if I do root one day. Thx

I get to this point...
ianandamy said:
...let go and push up on the volume, which will load the factory recovery android with a box and a loading bar...
Click to expand...
Click to collapse
See the box with a loading bar for about three seconds then the screen switches to the image of the android robot logo and an exclamation point within a triangle. I think its because I accidentally wiped my data last night when I was trying to fix the boot loop issue. I'm about to give up on this one...
Edit: Hey it works great, just make sure you don't add a .zip extension to the E101_SDUPDATE rename.

Big Thanks to ianandamy this works great! Got it up and running. The only problem is that I am being prompted to enter a password in order to get it to the homescreen...The second problem is that I never had a security password in order to access the tablet. I have a feeling this has to do with it being rooted by the previous owner before I purchased the tablet. Would the settings return to how he customized it pre-root? If so the password the tablet is asking for would be the one he set before I ever owned the tablet. How do I get around this?!

worked great, and like the profile pic

Added to ultimate thread. Nice job.

isdnmatt said:
I don't have .12 for you, but here is a link to .9 (That's the one that really matters anyway right?). I would appreciate a link to .12 just for my OCD.
V8.2.3.9(US)
http://db.tt/EEElFqP
If you could please rehost it somewhere.
Click to expand...
Click to collapse
Can someone host it and pm me a link to post

It's also still on the website, even though its been removed from the support page.
http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF101/UpdateLauncher_US_epad_user_8239.zip

isdnmatt said:
It's also still on the website, even though its been removed from the support page.
http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF101/UpdateLauncher_US_epad_user_8239.zip
Click to expand...
Click to collapse
GREAT!
I've extrapolated the WW version with that http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF101/UpdateLauncher_WW_epad_user_8239.zip

This cool and all.. but what would really be nice is to have the stock recovery yanked out of that 500MB blob so we don't have to transfer 500MB around, instead maybe 8-10MB (guessing based on CWM blob).
I'd do it, but I'm lame and don't have a linux box or VM setup .. that and I sold my eeePad to pay for vet bills... something about 'daddy save the puppy' is haunting me now.
P.S. Thanks for the info, just trying to save time if this is possible

sirmx said:
This cool and all.. but what would really be nice is to have the stock recovery yanked out of that 500MB blob so we don't have to transfer 500MB around, instead maybe 8-10MB (guessing based on CWM blob).
Click to expand...
Click to collapse
There you go. I extracted the recovery.img from the stock 8.2.3.9 US blob and put it into a clockwork flashable package. Tested it on Prime 1.3r2
After flashing this you should be able to use ASUS firmware packages again, but ymmv.

Segnaro said:
There you go. I extracted the recovery.img from the stock 8.2.3.9 US blob and put it into a clockwork flashable package. Tested it on Prime 1.3r2
After flashing this you should be able to use ASUS firmware packages again, but ymmv.
Click to expand...
Click to collapse
Mind explaining what exactly this is going to allow me to do? I flash it, then do what with the original firmware? And in doing this would it be a more complete restore back to stock removing everything related to root/cwm/custom boot and so on?
Either or, appreciate the work, you guys are awesome!

StirCwazy said:
Mind explaining what exactly this is going to allow me to do? I flash it, then do what with the original firmware? And in doing this would it be a more complete restore back to stock removing everything related to root/cwm/custom boot and so on?
Either or, appreciate the work, you guys are awesome!
Click to expand...
Click to collapse
After flashing it, you take the ASUS folder from the original firmware and put it on your SD card. The Transformer will ask you if you want to install that firmware.
Now that clockwork recovery has been replaced by stock recovery, it should be able to install normally.
I went from Prime 1.3r2 back to unrooted stock 8.2.3.9, no problem.

Segnaro said:
After flashing it, you take the ASUS folder from the original firmware and put it on your SD card. The Transformer will ask you if you want to install that firmware.
Now that clockwork recovery has been replaced by stock recovery, it should be able to install normally.
I went from Prime 1.3r2 back to unrooted stock 8.2.3.9, no problem.
Click to expand...
Click to collapse
Sorry to be a bit pesky here, but just want to be real sure: Based on ROM work I've done on my Android phone, unrooting is not the same as going back to a stock ROM. Actually the reverse is true: you can apply a stock ROM< and it will effectively unroot the phone.
So, if we have put PRIME on (or other ROMS...I think there is another...), then do this process, the phone will be stock, and in shape to send in for warranty if necessary?

ewingr said:
So, if we have put PRIME on (or other ROMS...I think there is another...), then do this process, the phone will be stock, and in shape to send in for warranty if necessary?
Click to expand...
Click to collapse
Yes, and after a factory reset it would be like when you just took it out of the box.

Will this un-root process work for the HC 3.1 leak? And if not what modifications would need to be done to unroot from HC 3.1? Am I able to wipe data/cache/dalvik from CWM then install HC 3.0.1 (Prime) so I can then follow this unroot process?
Edit: I found my answer in another thread. I'll post the link because I think it might be helpful to others with the same question.
http://forum.xda-developers.com/showthread.php?t=1103147

b1ackplague said:
Will this un-root process work for the HC 3.1 leak? And if not what modifications would need to be done to unroot from HC 3.1? Am I able to wipe data/cache/dalvik from CWM then install HC 3.0.1 (Prime) so I can then follow this unroot process?
Edit: I found my answer in another thread. I'll post the link because I think it might be helpful to others with the same question.
http://forum.xda-developers.com/showthread.php?t=1103147
Click to expand...
Click to collapse
Yes, I went from 3.1 direct to .9 without any issue.

Something just not right in my attempt to flash roms.

About to tear my hair out at its roots trying to get this thing up to Jellybean. I bought it being told it was Jellybean capable but it had not been upgraded yet and all I had to do was go to the Asus site and get the files.
Well I go to the asus site and sure enough I download the file but thenit does not mention how to do the upgrade process. So I then go to - http://forums.androidcentral.com/an...-jelly-bean-asus-infinity-tf700t-minutes.html and this tells me to get the file needed to make it a specific file name and then do the reboot into the regular bootloader.
Well this worked like a hill of beans. I kept getting an error about the signature being invalid though I downloaded it off the ASUS site and I tried downloading the file three different ways (at work) on my phone and off my home Cablemodem) so if its a file problem its a file problem on the hosted site Asus is using.
I then used the unlocker and I unlocked my Asus it even shows it is unlocked every time it unboots so this part I know I did right.
I then ran DebugfsRoot_Generic_v2.3.zip from the link here - http://dottech.org/78441/how-to-root-asus-transformer-pad-infinity-tf700-debugfs-method-guide/ - and it said that it gave me root access on the OS installed. I however downloaded SU and RootChecker both which indicated I did not have root.
So then I decided if I was going to do this I would go full gusto. So I got a CWM GUI from http://forum.xda-developers.com/showthread.php?t=2094746 because I use CWM on my phones and figured if I stuck with the gui version of this I would be fairly competent on doing a rom replacement.
So then I downloaded a couple of roms from here - http://forum.xda-developers.com/showthread.php?t=1834521
as well as the SU that can be flashed. before boot up but I seem to still not to be able to get root (though the tool I used indicated I have it) on the current system.
The problem I have right now is rigt now anything I try and load from my sd card that is a zip shows -
E: Can't Open /sdcard/filename.zip
(bad)
Installation aborted.
For Filename.zip I have tried CWM-SuperSU-v0.99.zip from http://download.chainfire.eu/310/SuperSU/UPDATE-SuperSU-v1.04.zip as well as multiple ROM files from http://forum.xda-developers.com/showthread.php?t=1834521 as well as a couple from Asus
Things i know 1) I have correct USB from the Tablet to the PC this is evident because I was able to update the bootloader to the CWM GUI. 2) The MicroSD card is a 4 gb card and it works just fine. I have used it in my computer many times and I can open and copy and move files just fine on it any which way. 3) I am unsure as to why DebugfsRoot_Generic_v2.3.zip indicated it was all Rooted but then rootchecker is not showing it as rooted.
Is the fact I don't have Root the main reason for the files not being able to be opened? If so is there a better TF700T root program out there?

So for my clarification you want Jelly Bean rooted?
Is this correct?

Although it could be risky, you can actually toggle file system hashing verifications off in CWM. Make absolutely sure that the file downloaded correctly by verifying the MD5 yourself, other wise you could end up with a brick of the same value but even less practical use than the one you currently have.
Sent from a comfortable chair from the outer ring of Purgatory. The red guy asked me to say 'hi'.
---------- Post added at 12:50 PM ---------- Previous post was at 12:42 PM ----------
StumpedTechy said:
About to tear my hair out at its roots trying to get this thing up to Jellybean. I bought it being told it was Jellybean capable but it had not been upgraded yet and all I had to do was go to the Asus site and get the files.
Click to expand...
Click to collapse
To answer Thats_OK's question: I read this to mean that the 700 is still ICS, and he wants to get JB on there.
1) I have correct USB from the Tablet to the PC this is evident because I was able to update the bootloader to the CWM GUI.
Click to expand...
Click to collapse
Just to correct a minor error in terminology, just to get it straight: CWM is a recovery, and not a bootloader nor a "GUI" to the bootloader.
2) The MicroSD card is a 4 gb card and it works just fine. I have used it in my computer many times and I can open and copy and move files just fine on it any which way.
Click to expand...
Click to collapse
Not thT IT SEEMS TO BE THE ROOT Cuse here, but what filesystem is it formatted to?
3) I am unsure as to why DebugfsRoot_Generic_v2.3.zip indicated it was all Rooted but then rootchecker is not showing it as rooted.
Click to expand...
Click to collapse
I do not have a clue either -- the script should do everything for you and you should not have to undertake any action afterwards.
Is the fact I don't have Root the main reason for the files not being able to be opened?
Click to expand...
Click to collapse
Nope, an unlocked bootloader and a suitable recovery is all you need. Once those two are in place and working correctly, you should be able to flash anything. Rooting pertains to the access granted to the filesystem once you're 'inside', i.e. with the tablet running the ROM installed.
If so is there a better TF700T root program out there?
Click to expand...
Click to collapse
Nah, this works for pretty much anyone. I've had the error of "bad installation" a few times as well, and I toggled the hashing. Worked like a charm, although, as said, there is a minor risk involved if you do not keep your head cool and forget to verify manually. I haven't had this on the latest version of CWM, though.
Sent from a comfortable chair from the outer ring of Purgatory. The red guy asked me to say 'hi'.

Go to settings--> about tablet and provide the full build number for your device.

Thats OK said:
So for my clarification you want Jelly Bean rooted?
Is this correct?
Click to expand...
Click to collapse
I want Jellybean, roooted isn't so much a need but would be a plus.
Go to settings--> about tablet and provide the full build number for your device.
Click to expand...
Click to collapse
Build number is IML74K.US_epad-9.4.5.30-20120907
Not thT IT SEEMS TO BE THE ROOT Cuse here, but what filesystem is it formatted to?
Click to expand...
Click to collapse
The card is formatted to fat32
I've had the error of "bad installation" a few times as well, and I toggled the hashing.
Click to expand...
Click to collapse
I am not seeing anythign for hashing i am seeing signiture varification but with this enabled or disabled it is not changing the error I am getting.

If you just want JellyBean have you tried looking here? >>> http://forum.xda-developers.com/showpost.php?p=28374043&postcount=1

Thats OK said:
If you just want JellyBean have you tried looking here? >>> http://forum.xda-developers.com/showpost.php?p=28374043&postcount=1
Click to expand...
Click to collapse
I appreciate the link but did you read this part of my post?
Well I go to the asus site and sure enough I download the file but thenit does not mention how to do the upgrade process. So I then go to - http://forums.androidcentral.com/and...t-minutes.html and this tells me to get the file needed to make it a specific file name and then do the reboot into the regular bootloader.
Click to expand...
Click to collapse
I have already followed these instructions multiple times and each time it is giving me errors about the files being invalid or something of the sort.
I have tried about 4 different roms to load and each time I get bad file indicators even after comparing md5s and verifying the files are okay.
Is there any way to wipe this thing 100% and just load something on fresh?

StumpedTechy said:
I appreciate the link but did you read this part of my post?
I have already followed these instructions multiple times and each time it is giving me errors about the files being invalid or something of the sort.
I have tried about 4 different roms to load and each time I get bad file indicators even after comparing md5s and verifying the files are okay.
Is there any way to wipe this thing 100% and just load something on fresh?
Click to expand...
Click to collapse
Hmmm..Guess I'm not catching what you have done.
When you downloaded from the Asus website did you rename the file inside the zip to: EP201_768_SDUPDATE.zip then place this on your microSD?
Also I don't see any mention of ADB to push files to the tablet.
Sorry for my confusion.
Just not understanding where your at.
It is possible to wipe the internal SD card (eMMC) memory using TWRP...yet I'd wait until we get things sorted.

Let me go over what I did and what didn't work and let me go over what I finally did that did work now that I have mine all upgraded.
Didn't work -Scenario 1 -
Go into Settings->About Tablet-> System update this did absolutely nothing for getting me jellybean it just sat at a connecting screen that gave me nothing.
Didn't work -Scenario 2 -
Straight from the last link you provided -
1. Decompress downloaded .zip file (it will be another .zip)
2. Rename it to EP201_768_SDUPDATE.zip
3. Format FAT32 the MicroSD card that you will be using for the update process
4. Copy the file to (the root directory of) your MicroSD
5. Insert it into the tablet
6. Shutdown (power off) the tablet
7. Power it on by pressing and holding VOLUME DOWN and POWER buttons simultaneously
8. When you see white text in the top left corner of the screen, release the buttons ^^ and press VOLUME UP button until you see Android logo and process bar
9. Wait patiently for 10 minutes or so
(when I reached number 8 nothing happened automatically and I had to use the blue screened system recovery and when I pointed it to the SD file it told me it was a bad file.)
Didn't work -Scenario 3 -
Loaded
Transformer ADB Tool v6 and then loaded CWM GUI and then tried loading different rom from all over the place Asus main site, and all over the Index site here for different roms. http://forum.xda-developers.com/showthread.php?t=1834521
Finally however I finally made it work -
I am not sure why ALL the other ways did not work but on mine this is what I had to do.
1) From my first post I got the program from Asus that did the Unlocker I ran that from the Asus site.
2) From the first post I installed CWM GUI and I installed that.
3) From the index site I downloaded Stock Rooted Odex 10.4.4.23 to a USB stick - mainly because it says its rooted and I don't have to worry about rooting it AND I don't mind being .02 revisions behind.
4) I did an MD5 check vrs the download verified all was correct.
5) Tried to install from the MicroSD card and it failed yet again same errors as before.
6) On a whim I rebooted the TF700T and I copied the Stock Rooted Odex 10.4.4.23 to the device directly.
7) I booted to CWM GUI again and this time it installed when I selected to load from the internal SD.
8) I reloaded all my apps on the top.
9) I then loaded the apk of flash that "isn't supported" but works well enough on JB even on my phone.
So basically it would not install from my MicroSD though everything said it should but it would work fine from the internal memory.
This is with me using 2 different MicroSD cards and both are known working ones out of current phones I use all the time.
So I am now up to Jellybean and I am sporting all I needed to be upgraded for. Thanks for the attempts but it was just my constant tenacity that got me through this process.

Sounds like you have loaded my stock rooted rom. Which means you will still be on the old ice cream sandwich bootloader. Recommend you flash the JellyBean bootloaderfrom one of my threads in the ddevelopment section.
The reason your ota Asus updates failed is because you were already unlocked.

sbdags said:
The reason your ota Asus updates failed is because you were already unlocked.
Click to expand...
Click to collapse
Good point. Any idea why the other ROMs were failing as well?
@OP: now you have found a way that works, I suggest to try CROMI.

sbdags said:
Sounds like you have loaded my stock rooted rom. Which means you will still be on the old ice cream sandwich bootloader. Recommend you flash the JellyBean bootloaderfrom one of my threads in the ddevelopment section.
The reason your ota Asus updates failed is because you were already unlocked.
Click to expand...
Click to collapse
Ugh so I actually just made this worse? Basically since I did Stock Rooted Odex 10.4.4.23 over the version 9 ICS I am still running version 9ICSwith files over the top that are from 10.4.4.23 making it now some mixture of the two? So confused because I thought when I did a rom upgrade it wiped out the old and put in the new? it is showing the right version in Settings and it is acting right with what Jellybean should be doing so I am a lot confused right now.

StumpedTechy said:
Ugh so I actually just made this worse? Basically since I did Stock Rooted Odex 10.4.4.23 over the version 9 ICS I am still running version 9ICSwith files over the top that are from 10.4.4.23 making it now some mixture of the two? So confused because I thought when I did a rom upgrade it wiped out the old and put in the new? it is showing the right version in Settings and it is acting right with what Jellybean should be doing so I am a lot confused right now.
Click to expand...
Click to collapse
boot into recovery, when you see 4 icons, take a look at the second line (white text), it should say the version of your bootloader (1.00e is JB bootloader and 2.00e is ICS), then next to it is your JB or ICS version.
What sdbags said is when you flash a premade rom from XDA, it only included the ROM/kernel, but no bootloader. The only way is to flash the full firmware download from Asus site which included everything and bootloader is one of them.

buhohitr said:
boot into recovery, when you see 4 icons, take a look at the second line (white text), it should say the version of your bootloader (1.00e is JB bootloader and 2.00e is ICS), then next to it is your JB or ICS version.
What sdbags said is when you flash a premade rom from XDA, it only included the ROM/kernel, but no bootloader. The only way is to flash the full firmware download from Asus site which included everything and bootloader is one of them.
Click to expand...
Click to collapse
Ahhh gotcha. So I have really only done it halfway and have to get the bootloader flashed up as well. Will work on this next then. Right now I only have three options in my bootloader android, USB and the wipe data when all the others I read about indicate 4 icons should be there so I thought something was off there.

StumpedTechy said:
Ahhh gotcha. So I have really only done it halfway and have to get the bootloader flashed up as well. Will work on this next then. Right now I only have three options in my bootloader android, USB and the wipe data when all the others I read about indicate 4 icons should be there so I thought something was off there.
Click to expand...
Click to collapse
You could flash just JB bootloader with custom recovery from here: http://forum.xda-developers.com/showthread.php?t=2049274

StumpedTechy said:
Ahhh gotcha. So I have really only done it halfway and have to get the bootloader flashed up as well. Will work on this next then. Right now I only have three options in my bootloader android, USB and the wipe data when all the others I read about indicate 4 icons should be there so I thought something was off there.
Click to expand...
Click to collapse
I uploaded sbdags' version I used to DropBox for you: https://www.dropbox.com/s/js0m8nas00ts95h/tf700t-WW-JB-bootloader-only.zip
It's just a matter of flashing this (and update your recovery, if applicable), and then reflash any ROM you'd like.
https://www.dropbox.com/s/js0m8nas00ts95h/tf700t-WW-JB-bootloader-only.zip

Thanks guys I went ahead I went ahead and downloaded it from the link right on the website that sbdags was talking about just did a quick forum search and found the proper JB bootloader. So now I have a CWM GUI recover, JB bootloader and the sdbags stock rooted JB rom on it.
Now I know this is a loaded question and someone has already mentioned CleanROM Inheritance 3.2
But are there any clear cut "great" JB roms that run pretty much flawlessly on the TF700T that are prerooted? Just checking because as I mentioned I have tried quite a few roms on my Samsung S2 and used AOKP, SuperNexus, and am now on ShoStock3. Are the roms on the TF700Ts about the same in "feel" to their galaxy s counterparts? E.G. AOSP TF700T like a AOKP Galaxy S2? (assuming AOSP and AOKP are the same developer?
Thanks for everyone sticking with me through this. This has been such a learning curve over my phone which was simply install CWM (non gui) and download the rom and then flash. Didn't have to worry about unlocking anything, didn't have to worry about where I was installing the rom from and all that.

StumpedTechy said:
Thanks guys I went ahead I went ahead and downloaded it from the link right on the website that sbdags was talking about just did a quick forum search and found the proper JB bootloader. So now I have a CWM GUI recover, JB bootloader and the sdbags stock rooted JB rom on it.
Click to expand...
Click to collapse
Good job -- wherever you got it from, it served you well. I'll keep the JB bootloader on that DropBox link for a while so others can benefit from it too.
Now I know this is a loaded question and someone has already mentioned CleanROM Inheritance 3.2
Click to expand...
Click to collapse
Yup.
But are there any clear cut "great" JB roms that run pretty much flawlessly on the TF700T that are prerooted?
Click to expand...
Click to collapse
Pretty much all of them are preooted, but in my opinion, none of them is as smooth as CROMI. BBB7 has been quite a bufggy experience for most of the people that tried it (or so I gather from the thread), and although the CM team is making nice progress on their 10.x version, some minor niggles remain (and sometimes resurface, such as shortcut keys on the dock being broken every once in a while). Also, CROMI is developed actively in the meantime as well, and you can take the mods with it that disable those annoying notifications.
Just checking because as I mentioned I have tried quite a few roms on my Samsung S2 and used AOKP, SuperNexus, and am now on ShoStock3.
Click to expand...
Click to collapse
I agree that the SGS2 was a breeze to flash compared to the TF700 -- I was in the same boat as you. Flashed away without a care, then had to learn how to do it anew with the Infinity.
Are the roms on the TF700Ts about the same in "feel" to their galaxy s counterparts? E.G. AOSP TF700T like a AOKP Galaxy S2? (assuming AOSP and AOKP are the same developer?)
Click to expand...
Click to collapse
The differences are greater, because the TF700 has a lot of pixels to push and therefore its hardware is more hard-pressed than the SGS2's. The Exynos in the SGS2 is a VERY good chip, so it handles itself quite nicely in lots of scenarios. The Tegra3, I am pained to say, has impressed me less in everyday use than the numbers on paper did. With CROMI, it's pretty good, so I'm happy as it is now, but it should have been better out-of-the-box.
Thanks for everyone sticking with me through this. This has been such a learning curve over my phone which was simply install CWM (non gui) and download the rom and then flash. Didn't have to worry about unlocking anything, didn't have to worry about where I was installing the rom from and all that.
Click to expand...
Click to collapse
All I worried about was that darned yellow triangle. Thanks to Chainfire we could disable that too, so I was a happy camper.

[Q] TF300T RCK issues after reflashing stock ROM

So I couldn't find my issue on google, and I read somewhere I should just start a thread since this seems...complicated.
I also read that the tablet only supports USB3.0 ports for this stuff, and IRONICALLY I was always using one.
Anyway, so I "unLocked" my boot loader from my android 4.1.1, then I installed CWM recovery, and flashed a 4.2.2 ROM. However, I hated the keyboard on that ROM, and I liked the menus more on the stock ROM, so I decided to switch back to that and see if I could just customize the latest ROM or something.
So I got the US 4.2.1 ROM from ASUS' firmware downloads page, and flashed it fine. I can use the tablet fully, no problem. I copied the files to root it onto my internal memory since I figured I would do it later. I try to boot it into RCK, there is no USB option(I figured that's normal since it wasn't plugged in). I select RCK, it's loading for a minuted, then the android is on the ground and there was some kind of exclamation mark above his open corpse. (I figure there's not too many errors like that, if you need more specifics I'll check it out again.
I thought maybe it needed a USB connection to load the RCK, but long story short I never have a USB option and RCK won't load, but android itself is fine. I thought maybe I needed the USB debugging(I turned that off momentarily after I had the ROM), I tried turning that back on, but no luck.
Any ideas?
Or tips. Tips are cool.

Rojikku said:
So I couldn't find my issue on google, and I read somewhere I should just start a thread since this seems...complicated.
I also read that the tablet only supports USB3.0 ports for this stuff, and IRONICALLY I was always using one.
Anyway, so I "unLocked" my boot loader from my android 4.1.1, then I installed CWM recovery, and flashed a 4.2.2 ROM. However, I hated the keyboard on that ROM, and I liked the menus more on the stock ROM, so I decided to switch back to that and see if I could just customize the latest ROM or something.
So I got the US 4.2.1 ROM from ASUS' firmware downloads page, and flashed it fine. I can use the tablet fully, no problem. I copied the files to root it onto my internal memory since I figured I would do it later. I try to boot it into RCK, there is no USB option(I figured that's normal since it wasn't plugged in). I select RCK, it's loading for a minuted, then the android is on the ground and there was some kind of exclamation mark above his open corpse. (I figure there's not too many errors like that, if you need more specifics I'll check it out again.
I thought maybe it needed a USB connection to load the RCK, but long story short I never have a USB option and RCK won't load, but android itself is fine. I thought maybe I needed the USB debugging(I turned that off momentarily after I had the ROM), I tried turning that back on, but no luck.
Any ideas?
Or tips. Tips are cool.
Click to expand...
Click to collapse
First I use usb 2.0 as I have no 3.0 ports and have no problems (just for info).
The 4.2 update changed the bootloader menu. Now when you enter the menu if you do nothing it will automatically enter fastboot - watch the upper left for a message. You will need usb debugging. I suggest leaving it turned on as you never know when there will be an issue and you can't get into the os to turn it on.
Good Luck!

Rojikku said:
So I couldn't find my issue on google, and I read somewhere I should just start a thread since this seems...complicated.
I also read that the tablet only supports USB3.0 ports for this stuff, and IRONICALLY I was always using one.
Anyway, so I "unLocked" my boot loader from my android 4.1.1, then I installed CWM recovery, and flashed a 4.2.2 ROM. However, I hated the keyboard on that ROM, and I liked the menus more on the stock ROM, so I decided to switch back to that and see if I could just customize the latest ROM or something.
So I got the US 4.2.1 ROM from ASUS' firmware downloads page, and flashed it fine. I can use the tablet fully, no problem. I copied the files to root it onto my internal memory since I figured I would do it later. I try to boot it into RCK, there is no USB option(I figured that's normal since it wasn't plugged in). I select RCK, it's loading for a minuted, then the android is on the ground and there was some kind of exclamation mark above his open corpse. (I figure there's not too many errors like that, if you need more specifics I'll check it out again.
I thought maybe it needed a USB connection to load the RCK, but long story short I never have a USB option and RCK won't load, but android itself is fine. I thought maybe I needed the USB debugging(I turned that off momentarily after I had the ROM), I tried turning that back on, but no luck.
Any ideas?
Or tips. Tips are cool.
Click to expand...
Click to collapse
You lost your version of Cwm when you flashed the official update.
You will need to find the version of TWRP that is posted on here that has been modified to work with new bootloader and flash it thru fastboot.

tobdaryl said:
First I use usb 2.0 as I have no 3.0 ports and have no problems (just for info).
The 4.2 update changed the bootloader menu. Now when you enter the menu if you do nothing it will automatically enter fastboot - watch the upper left for a message. You will need usb debugging. I suggest leaving it turned on as you never know when there will be an issue and you can't get into the os to turn it on.
Good Luck!
Click to expand...
Click to collapse
Thanks! That was INCREDIBLY helpful. I noticed that message but I didn't know what it meant. Funny the solution was so obvious...
flumpster said:
You lost your version of Cwm when you flashed the official update.
You will need to find the version of TWRP that is posted on here that has been modified to work with new bootloader and flash it thru fastboot.
Click to expand...
Click to collapse
Alright, thanks. I have no idea how that works, but if that's what I need to do to fix it whatever. xD

Rojikku said:
Thanks! That was INCREDIBLY helpful. I noticed that message but I didn't know what it meant. Funny the solution was so obvious...
Alright, thanks. I have no idea how that works, but if that's what I need to do to fix it whatever. xD
Click to expand...
Click to collapse
The twrp mentioned above can be found here.

tobdaryl said:
The twrp mentioned above can be found here.[/URL]
Click to expand...
Click to collapse
Thanks... I actually installed openrecovery-twrp-2.2.2.0-tf300t-JB.blob
On that note, I get a password prompt every time I boot into it. I read somewhere wiping and reinstalling helped with that, but even after wiping everything with every button I had I could still boot and everything was there...
And since APPARENTLY my internal storage isn't good enough, I can't install a 4.2.2 ROM(I'm still debating what ROM I will end up using.) I can't find anything in TWRP...
EDIT: To clarify, I can't find anything under / or /sdcard where I would normally find stuff.

Rojikku said:
Thanks... I actually installed openrecovery-twrp-2.2.2.0-tf300t-JB.blob
On that note, I get a password prompt every time I boot into it. I read somewhere wiping and reinstalling helped with that, but even after wiping everything with every button I had I could still boot and everything was there...
And since APPARENTLY my internal storage isn't good enough, I can't install a 4.2.2 ROM(I'm still debating what ROM I will end up using.) I can't find anything in TWRP...
EDIT: To clarify, I can't find anything under / or /sdcard where I would normally find stuff.
Click to expand...
Click to collapse
Wrong twrp! You need openrecovery-twrp-2.4.4.0-tf300t-4.2.blob until you are off stock 4.2 then you need openrecovery-twrp-2.4.4.0-tf300t-JB.blob. Unless the rom you flash is also for 4.2 bootloader. Both are located at teamwin.
4.2 changes directories in your sdcard for multi-user operation. Look under the 0 directory in /sdcard/0.
The password is for encryption that 4.2 uses to provide multi-user. The /sdcard allows total freedom under normal roms(even without root) but to stop user interaction 4.2 encrypts for user restriction. The first user gets directory 0 and so on.
Flash the proper twrp for 4.2 stock.
As far as flashing a new rom look at the op and determine if it is for the new stock 4.2 bootloader. If not do not flash over 4.2 but downgrade first. I have upgraded from 10.4.2.20 to stock 4.2 and downgraded from stock 4.2 to 10.4.2.20 several times without issue.
Stock 4.2 includes an assert to only allow upgrade from 10.4.2.20.

tobdaryl said:
Wrong twrp! [/URL]You need openrecovery-twrp-2.4.4.0-tf300t-4.2.blob until you are off 4.2 then you need openrecovery-twrp-2.4.4.0-tf300t-JB.blob. Both are located at teamwin.[/URL]
4.2 changes directories in your sdcard for multi-user operation. Look under the 0 directory in /sdcard/0.
The password is for encryption that 4.2 uses to provide multi-user. The /sdcard allows total freedom under normal roms(even without root) but to stop user interaction 4.2 encrypts for user restriction. The first user gets directory 0 and so on.
Flash the proper twrp for 4.2 stock and hold a minute or you are going right back where you were or worse. You need slightly more info before going forward and I need to check my notes while you get the proper twrp flashed.
Click to expand...
Click to collapse
Yeah, I really don't know that much about all this. I'd basically barely used android before I got this tablet a couple days ago, so I only have two days worth of experience...and I didn't get to use it a horribly large amount.
You seem like you're going to help a lot though, so thanks in advance. xD I'll get to flashing that twrp.

Rojikku said:
Yeah, I really don't know that much about all this. I'd basically barely used android before I got this tablet a couple days ago, so I only have two days worth of experience...and I didn't get to use it a horribly large amount.
You seem like you're going to help a lot though, so thanks in advance. xD I'll get to flashing that twrp.
Click to expand...
Click to collapse
I'll try but this new stock 4.2 is a new animal with many changes and we are just learning.

tobdaryl said:
I'll try but this new stock 4.2 is a new animal with many changes and we are just learning.
Click to expand...
Click to collapse
It actually was stock 4.1.1 >>; I just upgraded it. WHICH APPARENTLY WAS A HORRID DECISION. Regardless, I'm trying to install my twrp.img file, ran the command, and it's been writing for like ten minutes... 7672KB. I'm not certain if it's still writing or not...but it claims to be.

Rojikku said:
It actually was stock 4.1.1 >>; I just upgraded it. WHICH APPARENTLY WAS A HORRID DECISION. Regardless, I'm trying to install my twrp.img file, ran the command, and it's been writing for like ten minutes... 7672KB. I'm not certain if it's still writing or not...but it claims to be.
Click to expand...
Click to collapse
OK. Sometimes it takes seconds and sometimes longer. When you upgraded you used 4.2 (10.6.1.8)?

tobdaryl said:
OK. Sometimes it takes seconds and sometimes longer. When you upgraded you used 4.2 (10.6.1.8)?
Click to expand...
Click to collapse
Uhm. First. ****. It was frozen, so I canceled it and restarted it(Been a good twenty minutes doing nothing). Is it safe to reboot my tablet? I can't restart it, fastboot crashes. >>; Restart? Leave it? What?

I decided to take the risk and reboot it. Everything fine. I flashed the tool, ran the reboot command(Which actually didn't work... >>; But I rebooted it manually and it seems fine...)
On that note, is it actually possible to destroy a device beyond repair accidentally? And the TWRP tool said it flashed fine but I still have the old version. Odd....
I do have the image you said currently installed, I checked the version against my download.

Rojikku said:
Uhm. First. ****. It was frozen, so I canceled it and restarted it(Been a good twenty minutes doing nothing). Is it safe to reboot my tablet? I can't restart it, fastboot crashes. >>; Restart? Leave it? What?
Click to expand...
Click to collapse
I'm not sure where you are reading the above. Tell me your current situation and what rom you were on when you began this flash.

tobdaryl said:
I'm not sure where you are reading the above. Tell me your current situation and what rom you were on when you began this flash.
Click to expand...
Click to collapse
I originally flashed the ROM image of TF300T_US_epaduser_10_6_1_8_SDupdate, and I can still boot into that fine. I tried to install the RCK tool you recommended, but it froze. I did a ctrl+c, and then coldbooted the tablet. I tried to do it again, said it was fine, nothing happened. So I think "Maybe I need to boot into the OS and retry it after rebooting from there." So I do that, and now the recovery is frozen again. my command is fastboot -i 0x0b05 flash recovery twrp.img.
That the info you needed?

Rojikku said:
I originally flashed the ROM image of TF300T_US_epaduser_10_6_1_8_SDupdate, and I can still boot into that fine. I tried to install the RCK tool you recommended, but it froze. I did a ctrl+c, and then coldbooted the tablet. I tried to do it again, said it was fine, nothing happened. So I think "Maybe I need to boot into the OS and retry it after rebooting from there." So I do that, and now the recovery is frozen again. my command is fastboot -i 0x0b05 flash recovery twrp.img.
That the info you needed?
Click to expand...
Click to collapse
Go back and check my previous post with the links for twrp, I specified use of blob files. Either should work but some units seem to have an issue with img files. Also check that you have usb debugging turned on in developer options.

tobdaryl said:
Go back and check my previous post with the links for twrp, I specified use of blob files. Either should work but some units seem to have an issue with img files. Also check that you have usb debugging turned on in developer options.
Click to expand...
Click to collapse
I downloaded the .blob version now. That one worked fine. I guess it either didn't like the .img or my download was a bit corrupt.
I now have TWRP version 2.4.4.0.It still wants a password I never set though. I was just finishing making sure it actually worked as you posted.

Rojikku said:
I downloaded the .blob version now. That one worked fine. I guess it either didn't like the .img or my download was a bit corrupt.
I now have TWRP version 2.4.4.0.It still wants a password I never set though. I was just finishing making sure it actually worked as you posted.
Click to expand...
Click to collapse
When it asks for the password hit cancel and just ignore the error.

tobdaryl said:
When it asks for the password hit cancel and just ignore the error.
Click to expand...
Click to collapse
Okay. THEN what do I do? It doesn't seem to detect an OS even though I can boot into one. I can't find my ROM.zip in there and I'm not sure what to do from there... If I could find the ROM I would be fine, possibly. I'm trying to flash this one http://fitsnugly.euroskank.com/?rom=cm10&device=tf300t just to see if it works right. (I want it to show my dock's battery and have the overclocking menu in that drag-up interface.)

Rojikku said:
Okay. THEN what do I do? It doesn't seem to detect an OS even though I can boot into one. I can't find my ROM.zip in there and I'm not sure what to do from there... If I could find the ROM I would be fine, possibly. I'm trying to flash this one http://fitsnugly.euroskank.com/?rom=cm10&device=tf300t just to see if it works right. (I want it to show my dock's battery and have the overclocking menu in that drag-up interface.)
Click to expand...
Click to collapse
Thanks for the link. I looked at the info provided for that rom. You don't want to flash that over an encrypted tablet which you now have. The only safe way I have found to go to or from stock 4.2 rom is with stock 10.4.2.20.
To do that you would flash 10.4.2.20 with twrp, boot into os, reboot back to the bootloader which will now be four icons, select usb, use fastboot to flash twrp again, and now flash your new rom.
This sounds long but removes encryption from your tablet and you should be able to flash the jb rom of choice that does not require stock 4.2 bootloader.

Restoring stock firmware from CWM- Anyone have a usable .ZIP?

Hello! I need to restore my Photon Q to the stock firmware, ideally ICS. I have CWM installed, but every ZIP I see is either a custom firmware, uses .win files that are only TWRP compatible, or it's a file for RSD Lite. So far I haven't found any way to restore this phone to stock from CWM.
You're probably asking, "why not use fastboot or RSD"? I presently do not have access to a PC with administrator access. Therefore I can't install the USB drivers or RSD.
The reason I am trying to get back to stock is because for some reason, with EVERY custom ROM I have tried-- CM10.2, CM10.1, Carbon, SlimBean, MIUI, AOKP ... WiFi, BlueTooth and GPS are all broken. I don't have a cell plan for this phone, I just use it on WiFi- and I regularly use it for navigation. So, that's a pretty huge problem.
The weird thing is that I have had CM10.2 working with WiFi/BT/GPS before, and it was using the exact same ZIP. Weird, huh?
Thanks for any help!

RSD would be your best bet.
Perhaps borrow a PC?
Maybe someone with CWM will take pity upon you...

We're in the same boat...
Epicenter714 said:
Hello! I need to restore my Photon Q to the stock firmware, ideally ICS. I have CWM installed, but every ZIP I see is either a custom firmware, uses .win files that are only TWRP compatible, or it's a file for RSD Lite. So far I haven't found any way to restore this phone to stock from CWM.
You're probably asking, "why not use fastboot or RSD"? I presently do not have access to a PC with administrator access. Therefore I can't install the USB drivers or RSD.
The reason I am trying to get back to stock is because for some reason, with EVERY custom ROM I have tried-- CM10.2, CM10.1, Carbon, SlimBean, MIUI, AOKP ... WiFi, BlueTooth and GPS are all broken. I don't have a cell plan for this phone, I just use it on WiFi- and I regularly use it for navigation. So, that's a pretty huge problem.
The weird thing is that I have had CM10.2 working with WiFi/BT/GPS before, and it was using the exact same ZIP. Weird, huh?
Thanks for any help!
Click to expand...
Click to collapse
I am also looking for a stable ROM.
Just like you, Cm 10 worked. I even tried Cm 10.2 nightly and that's when I started having problems. Tons of force start problems.
Now I'm back to stock ROM and for some reason, YouTube and Google Play won't work.
My Wifi stays white and never goes to blue. As well, I am not on any carrier and rely on Wifi.have been flashing ROMS since the original HTC EVO. This has been quite a challenge (with the incorrect bootloader instructions on Motorola's website not helping any..) but I'll let you knowif I can find a flawless recovery stock of Photon Q!!
Thanks
Zombieguy
Rooted:
HTC Evo-running MYn's Warm 2.2 (still loving it)
Droid Bionic-Retired
ZTE Warp- running ???(really fast blue something)
ZEPAD (wannabe Ipad ZT-180) in the trash
---------- Post added at 06:45 AM ---------- Previous post was at 06:37 AM ----------
Epicenter714 said:
Hello! I need to restore my Photon Q to the stock firmware, ideally ICS. I have CWM installed, but every ZIP I see is either a custom firmware, uses .win files that are only TWRP compatible, or it's a file for RSD Lite. So far I haven't found any way to restore this phone to stock from CWM.
Thanks for any help!
Click to expand...
Click to collapse
Then I found this link here on another thread.
http://forum.xda-developers.com/showthread.php?t=2295643
ICS and JB both. I'll try them and let you know what happens!!
Thanks
Zombieguy
Rooted:
HTC Evo-running MYn's Warm 2.2 (still loving it)
Droid Bionic-Retired
ZTE Warp- running ???(really fast blue something)
ZEPAD (wannabe Ipad ZT-180) in the trash

zombieguy said:
Then I found this link here on another thread.
http://forum.xda-developers.com/showthread.php?t=2295643
ICS and JB both. I'll try them and let you know what happens!!
Glad to see I'm not the only one in this predicament. I have seen that thread- unfortunately the recovery files are .win -- which I think is for TWRP only? I think the only way to get TWRP on here is with Fastboot, and that's not doable in my situation I thought I saw a ZIP somewhere on these forums but now it's nowhere to be found.
Thanks and I will post if I find a solution!
Click to expand...
Click to collapse

Epicenter714 said:
Glad to see I'm not the only one in this predicament. I have seen that thread- unfortunately the recovery files are .win -- which I think is for TWRP only? I think the only way to get TWRP on here is with Fastboot, and that's not doable in my situation I thought I saw a ZIP somewhere on these forums but now it's nowhere to be found.
Thanks and I will post if I find a solution!
Click to expand...
Click to collapse
You can install TWRP with GooManager, assuming you are already rooted.

arrrghhh said:
You can install TWRP with GooManager, assuming you are already rooted.
Click to expand...
Click to collapse
\
Will try that.. getting an APK of Goomanager now. thx

Hm, does goomanager need an internet connection to DL TWRP, or I can I somehow supply it with a file? .. I have no way to get the rooted Photon on the net, as I have no data plan and WiFi is broken. Thanks.

Epicenter714 said:
Hm, does goomanager need an internet connection to DL TWRP, or I can I somehow supply it with a file? .. I have no way to get the rooted Photon on the net, as I have no data plan and WiFi is broken. Thanks.
Click to expand...
Click to collapse
I suppose you can supply it with a file, although I am unsure of how to do so. Never attempted myself...

I use root explorer and it asks what app do you want to use to open file.
Sent from my XT897 using XDA Premium 4 mobile app

I've got a Photon Q sitting in the mailbox from ebay today, plan to root and use CWM (more familiar with it over TWRP). I can probably grab a nandriod image of the stock rom rooted (depending on the root procedure, haven't read everything yet) and can send that to you. That should get you there w/o need for network connection. :good:

Installed TWRP on StraightTalk SCH-S968C Samsung Galaxy S III - now no OS! - resolved

I have a rooted StraightTalk SCH-S968C Samsung Galaxy S III (with the stock AOSP ROM) that I just screwed up. I had used EZ-Recovery to flash TWRP 2.2.0 to the phone. Now TWRP says there is no OS! I can only boot into TWRP - nothing else. It won't even let me power-down the phone. Is there some way I can recover from this, or do I now have a very expensive electronic brick (that runs TWRP)? I have adb installed on my laptop and I know it works, so that's one possible route to recovery. Any help would be much appreciated!

ScottDB said:
I have a rooted StraightTalk SCH-S968C Samsung Galaxy S III (with the stock AOSP ROM) that I just screwed up. I had used EZ-Recovery to flash TWRP 2.2.0 to the phone. Now TWRP says there is no OS! I can only boot into TWRP - nothing else. It won't even let me power-down the phone. Is there some way I can recover from this, or do I now have a very expensive electronic brick (that runs TWRP)? I have adb installed on my laptop and I know it works, so that's one possible route to recovery. Any help would be much appreciated!
Click to expand...
Click to collapse
I'm pretty sure it's possible to return it completely to stock with the COMBINATION_S968CUDUAMH1_S968CTFNAMH1_1304014_REV09_user_low_ship.tar.md5 file through Odin. I just to happen to have the file right here.. small warning though, it's 1.2 gigs.
https://mega.co.nz/#!gRI3DD5L!dRW8ORzfQI5j1JyKHVBTNifomPCXoqL14B9GF4oxvQY

aekel87 said:
I'm pretty sure it's possible to return it completely to stock with the COMBINATION_S968CUDUAMH1_S968CTFNAMH1_1304014_REV09_user_low_ship.tar.md5 file through Odin. I just to happen to have the file right here.. small warning though, it's 1.2 gigs.
https://mega.co.nz/#!gRI3DD5L!dRW8ORzfQI5j1JyKHVBTNifomPCXoqL14B9GF4oxvQY
Click to expand...
Click to collapse
That's the file I am offering to host on my Website, since nobody seems to be able to download it from Dropbox. I'm having trouble downloading it from Mega... Since the file is over 1 GB, Mega insisted I needed to download their extension, but it's not compatible with Firefox 22. I tried Chrome, and Mega says that Chrome on my laptop is "a bit outdated"... sheesh! I'll try and update it.
(added later) - I found a Dropbox link for the file and it's downloading now.
If you want to FTP the file to my Website, let me know by PM and I'll give you the username and password.
I tried using fastboot to install CWM Recovery, but fastboot is eternally "waiting for device" even though it's there (adb can see it).
Aug. 7 - Got the file I needed, but didn't use it since Windows7 would not recognize the phone even after I installed the drivers. (I think it was an issue with automatic updates being disabled...) In the meantime... I tried the button-combo for the bootloader (which I swore I tried the day before and it didn't work), and the phone booted into the bootloader! From there, I pressed "Volume down" to cancel & reboot the phone, and it went into the stock system - it was all still there! First thing I did was immediately use EZ-Recovery to flash CWM 5.8.4.5. - Issue resolved!

Deleted.

ScottDB said:
That's the file I am offering to host on my Website, since nobody seems to be able to download it from Dropbox. I'm having trouble downloading it from Mega... Since the file is over 1 GB, Mega insisted I needed to download their extension, but it's not compatible with Firefox 22. I tried Chrome, and Mega says that Chrome on my laptop is "a bit outdated"... sheesh! I'll try and update it.
(added later) - I found a Dropbox link for the file and it's downloading now.
If you want to FTP the file to my Website, let me know by PM and I'll give you the username and password.
I tried using fastboot to install CWM Recovery, but fastboot is eternally "waiting for device" even though it's there (adb can see it).
Aug. 7 - Got the file I needed, but didn't use it since Windows7 would not recognize the phone even after I installed the drivers. (I think it was an issue with automatic updates being disabled...) In the meantime... I tried the button-combo for the bootloader (which I swore I tried the day before and it didn't work), and the phone booted into the bootloader! From there, I pressed "Volume down" to cancel & reboot the phone, and it went into the stock system - it was all still there! First thing I did was immediately use EZ-Recovery to flash CWM 5.8.4.5. - Issue resolved!
Click to expand...
Click to collapse
Thank you!!!! I just had the same problem. However even when using cwm i get errors in the recovery. Unable to mount anything or do anything besides reboot. Any ideas?

need stock Firmware
Have any idea where i can get this file? Ive bricked my phone too. Durnnit!

iamwaynes said:
Have any idea where i can get this file? Ive bricked my phone too. Durnnit!
Click to expand...
Click to collapse
This is the h1 stock you need. type this in google you should find the download if not I have it.
COMBINATION_S968CUDUAMH1_S968CTFNAMH1_1304014_REV0
Dont use e-z recovery. I had the same problem neither cwm or twrp from ez recovery worked and then cwm said no os on my phine so I flashed that file from download mode and was back to stock.

How did u find a recovery that worked mine is saying the same thing
Sent from my SM-N900T using Tapatalk

iamwaynes said:
How did u find a recovery that worked mine is saying the same thing
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1771398
In that thread go down to method 2 of getting a custom recovery. I downloaded cwm touch from the link there and then installed it with android terminal emulator using the codes that it says to type in. I tried to look up that stock rom but I didnt find it. Its on the forum somewhere in a thread about how to root the straight talk s3 and how first you need to download and flash the h1 baseband stock rom

Thanks I found the stock rom fixing it now.
Sent from my SM-N900T using Tapatalk

iamwaynes said:
Thanks I found the stock rom fixing it now.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Ok I've re rooted and tried to install recovery. Odin put it in wrong place. Says no operating system . What now?
Sent from my SM-N900T using Tapatalk

iamwaynes said:
Ok I've re rooted and tried to install recovery. Odin put it in wrong place. Says no operating system . What now?
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Have you gotten recovery installed and straightened out yet?
Let me know if you need some help, tell me where you're at and what you've got going on with what you have.

I returned phone to stock. The recovery wasn't in the right place obviously. So that's where I am . Stuck back at stock. Thanks for any help you can give.
Sent from my SM-N900T using Tapatalk

iamwaynes said:
I returned phone to stock. The recovery wasn't in the right place obviously. So that's where I am . Stuck back at stock. Thanks for any help you can give.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Are you on stock not rooted or you are rooted?
Do you have stock recovery or custom.
I can get you to wherever you need or want. Tell me what you need or where you'd like to be.

Droidriven said:
Are you on stock not rooted or you are rooted?
Do you have stock recovery or custom.
I can get you to wherever you need or want. Tell me what you need or where you'd like to be.
Click to expand...
Click to collapse
I have combined 2 s3's to make one good one. This is the proper thread for the model of the chipset. The phone has been worked on buy someone who only thought they were a genious. I've found traces and from surfing the forums I'm pretty sure I know what they did even. I'm gonna grab these stock images and flash back to stock. I just wanted to put a word in now to see how dead this thread is. BTW just for the record easy safe root is achievable with safroot for Att g s 4. I've confirmed that. Root is no issue. Modem drivers are jacked up. I want what I have now with WiFi in tact and custom recovery. Just wanted to get the word in in case I hit a wall with recovery as I am now before the flash to stock. Thanks in advance for any help. Sorry for the ramble
---------- Post added at 07:23 AM ---------- Previous post was at 07:03 AM ----------
ScottDB said:
That's the file I am offering to host on my Website, since nobody seems to be able to download it from Dropbox. I'm having trouble downloading it from Mega... Since the file is over 1 GB, Mega insisted I needed to download their extension, but it's not compatible with Firefox 22. I tried Chrome, and Mega says that Chrome on my laptop is "a bit outdated"... sheesh! I'll try and update it.
(added later) - I found a Dropbox link for the file and it's downloading now.
If you want to FTP the file to my Website, let me know by PM and I'll give you the username and password.
I tried using fastboot to install CWM Recovery, but fastboot is eternally "waiting for device" even though it's there (adb can see it).
Aug. 7 - Got the file I needed, but didn't use it since Windows7 would not recognize the phone even after I installed the drivers. (I think it was an issue with automatic updates being disabled...) In the meantime... I tried the button-combo for the bootloader (which I swore I tried the day before and it didn't work), and the phone booted into the bootloader! From there, I pressed "Volume down" to cancel & reboot the phone, and it went into the stock system - it was all still there! First thing I did was immediately use EZ-Recovery to flash CWM 5.8.4.5. - Issue resolved!
Click to expand...
Click to collapse
Does anyone have a good link for h1 stock. All the links I can find including aa51 are dead. I need to go stock to fix the modem. I can handle everything from there I just need stock and I've trolled XDA , aa51, and several others. All links are dead. Probably for a long long time . any help is greatly appreciated
---------- Post added at 07:42 AM ---------- Previous post was at 07:23 AM ----------
sazendrak said:
I have combined 2 s3's to make one good one. This is the proper thread for the model of the chipset. The phone has been worked on buy someone who only thought they were a genious. I've found traces and from surfing the forums I'm pretty sure I know what they did even. I'm gonna grab these stock images and flash back to stock. I just wanted to put a word in now to see how dead this thread is. BTW just for the record easy safe root is achievable with safroot for Att g s 4. I've confirmed that. Root is no issue. Modem drivers are jacked up. I want what I have now with WiFi in tact and custom recovery. Just wanted to get the word in in case I hit a wall with recovery as I am now before the flash to stock. Thanks in advance for any help. Sorry for the ramble
---------- Post added at 07:23 AM ---------- Previous post was at 07:03 AM ----------
Does anyone have a good link for h1 stock. All the links I can find including aa51 are dead. I need to go stock to fix the modem. I can handle everything from there I just need stock and I've trolled XDA , aa51, and several others. All links are dead. Probably for a long long time . any help is greatly appreciated
Click to expand...
Click to collapse
Finally found it here
https://forum.xda-developers.com/showthread.php?t=2516498&page=28