Related
Hi everybody,
after endless nights and days of experimenting and crying I ask for your help.
My Aim: rooting my HTC One S C2.
So here is my story:
In my first attempt I unlocked my bootloader and tried to put a Custom Recovery on my phone. It failed. I got always stuck at the HTC screen with the red writing underneath the logo ("This build is for ...").
I then found out that I need the superboot.bat to root my phone.
So I proceeded to re-lock my phone and put a RUU on it to get back to the original Recovery.
All went well, so I unlocked my phone again via htcdev.com.
After that I tried to run the superboot.bat but again I am stuck at the HTC screen with the red writing!
I know that this screen should only appear for a few seconds and the phone should go into recovery but I am always stuck endless in this screen. To get out of it I have to soft reset my phone.
So I am not able to root it.
In a video I saw that on other phones the HTC screen with red writing has some kind of a "loading bar" on the upper right which appears after trying to access the recovery.
Well this bar doesn't even appear on my phone
Please help me I really don't know what to do further
same issue here, so subscribing to thread!
If you can get to download mode try to flash stock firmware with Odin. Search for a guide on youtube.
--------------------------------------------
Sent from my GT-S5830 running ImaGinary ICS.
Thank if it helped.It's there for a reason
Ähm isn't Odin for Samsung devices?
This is about HTC... Or does it work for both?
i recommend reading through this guide to rooting the one s. i've rooted quite a few phones using this method and it has worked flawlessly every time
http://forum.xda-developers.com/showthread.php?t=1583427
@HidaKureku - thats where i've got stuck; end of part two.
the recovery image seems to flash fine (both of them), and i've done the CWM recovery multiple times (some sites sugest that it works on the second attempt).
try to boot to recovery, and as per the OP it just sits there saying that it's for "This build is for HTC use only..." or whatever it says. no further. I've left it for 10mins in this state have have to power it off.
i have found that when i boot back to the UK retail ROM, it comes up with an error and wants to send it to HTC (i haven't yet been able to grab the error though).
has anyone sucessfully flashed recovery with the hboot 9.02.0001 image? i've seen a post on modaco with a user having the same problems as in this thread....
are you sure you're model has the S4 processor? if not, try this thread
http://forum.xda-developers.com/showthread.php?t=1785777&highlight=twrp
looks like i'm on the s3 version! twrp2 doesn't work either - same issue. (using openrecovery-twrp-2.2.2.0-ville.img)
seems the UK is one of these 'select' countries.
anyway - even an S3 compatible recovery isnt working....
I hope in not threadjacking here. @OP - if im intruding let me know and i'll create my own thread
No you are not intruding as I have exactley the same problem as you!
I'm glad that I'm not the only one I started to think I'm doing something completely wrong.
It's like the stock recovery is damaged even with the RUU version.
I just cannot get past this screen with the red warning!
My HTC One S is kind of new (about 3 weeks old). Maybe something changed with new models?
good news; i'm recovery-ed
you need 'openrecovery-twrp-2.2.2.1-villec2.img'.
It was 'tricky' to find, as the 'villec2' image doesnt appear to have any public links. As per the thread http://forum.xda-developers.com/showthread.php?t=1785777, Get 'goomanager', allow it to find and download recovery image, however, it wont sucessfully apply with goomanager (you dont have root yet).
It will download this recovery image to to /mnt/sdcard/goomanager/ (you can change/confirm it in goomanager menu options)
mount storage & copy this to your computer. Use fastboot to flash as per the unlock/recovery/root guide.
i dont mind hosting the file, but the above should be the quickest way
Yes!!!
That's it!!
Thank you so much
You made my day
Thread can be marked as solved!
now that you know you have the s3 processor be careful which roms you flash, make sure they are compatible with your version. the rom i'm running (check my signature for the link) is supposed to be compatible with both. but just read carefully and flash responsibly
HidaKureku said:
now that you know you have the s3 processor be careful which roms you flash, make sure they are compatible with your version. the rom i'm running (check my signature for the link) is supposed to be compatible with both. but just read carefully and flash responsibly
Click to expand...
Click to collapse
Thanks for the heads up, although that JB ROM in your sig says S4 in the title (thats about as far as i got )
@Schlengge - glad your sorted too i didnt even realise i was on s3 untill tonight; i thought all UK HOS's were s4's - seems not.
yeah XD i went back and looked at it and realized i got it confused with one rom i saw that was supposedly compatible with both processors (which struck me as odd) but there are a few roms out there for the s3, sadly not as many as for the s4, but you should be able to find one you're happy with. best of luck
veehexx said:
good news; i'm recovery-ed
you need 'openrecovery-twrp-2.2.2.1-villec2.img'.
It was 'tricky' to find, as the 'villec2' image doesnt appear to have any public links. As per the thread http://forum.xda-developers.com/showthread.php?t=1785777, Get 'goomanager', allow it to find and download recovery image, however, it wont sucessfully apply with goomanager (you dont have root yet).
It will download this recovery image to to /mnt/sdcard/goomanager/ (you can change/confirm it in goomanager menu options)
mount storage & copy this to your computer. Use fastboot to flash as per the unlock/recovery/root guide.
i dont mind hosting the file, but the above should be the quickest way
Click to expand...
Click to collapse
well, thanks for that advice. It is kinda confusing to find a recovery for c2 version of the ONE S, cause any other recovery will not work with it. The twrp-team should definatly add the link to that on their website.
Hello,
I just got my transformer tf300t (US) yesterday. It came with 10.4.2.18 on it. It tried to update to 10.4.2.18 right away, but i had heard so much about problems unlocking the bootloader, i went ahead and an postponed the updated, and unlocked immediately. The unlock went without a hitch! I thought, great! However now I don't know how to update the firmware to 10.4.2.20, as when I tell it to check for udpates, it says that it is up to date(and from what i read this is because its unlocked).
I thought about just installing a customer recovery, and flashing a customer rom based on 10.4.2.20, but they all say in the instructions to update to the newest rom before flashing(i assume this is because the bootloader needs to be up to date?)
Any help or guidance would be appreciated, thanks!
urushiol said:
Hello,
I just got my transformer tf300t (US) yesterday. It came with 10.4.2.18 on it. It tried to update to 10.4.2.18 right away, but i had heard so much about problems unlocking the bootloader, i went ahead and an postponed the updated, and unlocked immediately. The unlock went without a hitch! I thought, great! However now I don't know how to update the firmware to 10.4.2.20, as when I tell it to check for udpates, it says that it is up to date(and from what i read this is because its unlocked).
I thought about just installing a customer recovery, and flashing a customer rom based on 10.4.2.20, but they all say in the instructions to update to the newest rom before flashing(i assume this is because the bootloader needs to be up to date?)
Any help or guidance would be appreciated, thanks!
Click to expand...
Click to collapse
You have an Index for the TF300T/TG here, and you will find all you need for your TF :good:
and try this : [ROOT/ROM] Root Stock/Deodex Firmware 10.4.2.20 (US/WW) | Insecure kernel !
philos64 said:
You have an Index for the TF300T/TG here, and you will find all you need for your TF :good:
and try this : [ROOT/ROM] Root Stock/Deodex Firmware 10.4.2.20 (US/WW) | Insecure kernel !
Click to expand...
Click to collapse
I went through a few hours of heartache to be able to update my tab to stock jb 4.1 about a month back, and to be honest I don't really remember how I did it, though I think it involved adb/fastboot...
I am currently running cm 10.1 off of the asus 4.1 bootloader, and I will be attempting to update to asus stock 4.2 in about 20 minutes and I will let you know my findings... but sofar, you are off in the right direction, though I might recommend the NVflash tutorial in the dev area to make sure you cant f up your tab...
Alright brother, so here is what I have got figured out since I last posted about, oh, say 8 hours ago...
Now, assuming you took my advice and did the whole lovely NVFlash Tutorial, then what I would do is go to Asus.com, pick your region, go to support, firmware, then select the 10.4.2.20 update that matches your tab's region (mine is in the US, so I picked US). Then download that sucker, go smoke a cig or two (however long it takes) or do whatever you do that will take THAT time to download the ~500mb file...
FROM THERE, assuming you are using windows (like I am, Windows 7 to be exact) use your favorite unzipping prog. to open the file, then extract the .zip within (called US_epad-user-10.4.2.20.zip) to somewhere on your interal (or I prefer external) sd card.
NOW, if you haven't done so already, you need a Custom Recovery, and I HIGHLY recommend TWRP because in my experience, it is simply more versatile that CWM (clockword mod). Again, you can find this in the Developement section of this forum...
Once you have both TWRP, and your official update file on an sd card, you are almost home free here... Alls you have to do is boot up into recovery from, say... device turned off... by first holding Volume Down then pressing and holding (at the same time) The power button until device comes on. You will then be met with a small message in the upper left hand screen saying "press Volume up to enter RCK" (or recovery) and TWRP should load from here.
Once it does, then it's easy here, first, for grins, create a backup, simply by hitting the backup button (you'll know it when you see it) that way you have a dyed-in-the-wool backup of your actual stock rom (THIS CAN BE VERY HELPFUL should you need to return or repair the tab, which Asus will no longer cover since it's unlocked, but if you got it from, say Amazon or Best Buy, you should have almost NO problems being able to do that... jejejeje) once backup is complete (should take about 3-5 minutes or so) then hit the Home softkey in the upper right corner, go to "install" then find where you put that update file that I had you extract earlier (hopefully on your external sd card for simplicity)... You are given a some-what easy to navigate file system that should help you locate it where your folder tree will be on the left window and your files within the active folder are in the right, select the file, then install...
WHEEEEE! Now let that bad boy go, when it says Success! and displays the buttons again at the bottom, then you are good to return home to the main screen (of TWRP) or to just Reboot the tab. Upon rebooting, you will first see your Asus splash screen with the device unlocked text in the upper left, following some new text saying something silly like official update ok, then the next screen will have a slightly different Asus splash with a progress bar that fills up blue as it updates/installs the system. THIS WILL TAKE A LITTLE WHILE, and when done it will reboot again ( I believe) and then show the Asus logo with a dotted rotating "loading" circle, and this too, will take a while to finish doing what it's doing...
From here, it's just the waiting game....until you are prompted to set it up like you did the first time out of the box.
Congrats! Now you are fully up to date until Asus posts the NEW 4.2 update on the site, which is currently only available in the US via OTA update (which would require you NOT be unlocked, but who cares)
You can find info on THAT update below...
http://www.androidcentral.com/android-42-roll-out-asus-transformer-pad-tf300-begins-today-us
Other than that, once you are where you wanted to be (which was on the official JB 4.1.1 update, things will go smoothly for you, it ran real nice for me, but I don't know if it's just my Wi-Fi setup or what, but I seemed to lose Wi-Fi stability after a month or so... Asus has been known for that I hear, but then again, you might not have that issue...
At any rate, you are now able to safely flash your brains out on this tab... I was on CM 10.1 (which gives you the bleeding edge Android 4.2.2) and it works nicely, but I experienced some seriously noticeable lag on screen rotation when using the nightlies that simply just weren't there on the stock rom. Not only that but the stock rom gives you a cute feature at the bottom of the screen, in the middle of the notification/nav bar... a navigation locker (great for games, especially if you have kids or just hit the nav buttons accidently when using media).
I am currently running the newest AOKP, and it does everything that CM10.1 does (as far as I can tell) and isn't short of any features (again, as far as I can tell after about an hour of toying) that CM10.1 has...
*finally exhales* Hope this has been helpful to you... God, I know it would have been helpful to me back when I did this.
VERY IMPORTANT: as it is almost 7 am, I just realised that after you flash the official 4.1.1 update, you will need to reinstall TWRP in order to use other ROMs...too easy, doesn't take hardly any time, I just forgot to mention it... Wish you well on your new tab!
So it had been quite some time since I tried messing with my tf300 so....
I was on cm-9, when to update to cm-10.1, tried to update twrp then it wouldn't boot to recovery, tried to flash back to stock JB bootloader using "fastboot flash system.blob" gave me a flash error (invalid size) and for some reason fastboot doesnt recognize my device.
So I have no recovery and no rom.
I tried "fastboot boot boot.blob" from cm-9 and cm-10 and it wont boot. just stuck on "waiting for device"
When I type "fastboot devices" it just starts a new command line, no serial number.
I can include any information needed to help my situation, I just need to be told where to look.
To be honest, I couldn't remember what bootloader I was on. It had been a while. Is there a way to tell?
Can't get the tablet to stay off either while I wait for help. Lol
Sent from my LG-LS970 using xda premium
Any ideas?
Sent from my LG-LS970 using xda premium
Now I think my situation might have gotten worse.
I can't get into fastboot now. It just keeps trying to go into recovery mode but there is no recovery so it just continuously reboots.
No one can help?
Sent from my LG-LS970 using xda premium
Well that sucks...
Sent from my LG-LS970 using xda premium
Depends on what you were trying to do, were you trying to update the recovery first and to what version. I believe cm 9 is based on an older build of bootloader. What exactly did you do. From my knowladge as to reading and seeing so many people just flashing before reading the threads you should first update the bootloader then the recovery depending on what recovery version you were trying to update to. From what it sound like you tried to update the recovery before bootloader just not sure what version of recovery but if wrong one and didnt update bootloader sounds like you maybe un recoverably bricked like what everyone else is doing before reading and as of now. Aslo if you have an nvflash backup there may be a fix i'm just not sure how as i never had it but accorging to some it seems that was the only hope for them to get out. Reaad the threads there maybe help on here some where just so many are flashing and bricking before reading people are getting frustrated because theres no help for it.
I know it doesn't help, but since you wanted to know what happened, I can tell you that much. Since you were on CM9, you had to be on the original ICS bootloader. Stock JB can't be fastboot-flashed over ICS because of changes to the partitioning and other low-level stuff, which is why it wouldn't flash and why it subsequently failed to boot.
I'm also just picking up my TF300 for the first time since August. I just recovered from a soft-brick today (my story, which in hindsight was a complete f-up on my part), which was why I hadn't been using it. I ended up fastboot-flashing the newest ICS firmware (I actually tried it back in August, but fastboot wouldn't work; I didn't do anything differently today, but fastboot had been updated recently and magically worked), then performing the NVFlash backups from the sticky thread (this isn't quite where our paths diverged, but it may have been a good idea to do that before you tried upgrading to JB -- not that it helps now, but for future reference).
Like you, I tried fastboot-flashing the stock JB firmware over the ICS firmware and got the same error you got. So, I tried flashing the ICS firmware again, but got the same Invalid Size error. At this point, my tablet wouldn't boot past the splash screen (not the animation with the spinner; the first one with the NVidea logo in the corner), and fastboot wouldn't flash any firmware.
This next part is the part where our stories more-or-less fork.
Faced with another soft brick just hours after fixing one, I fastboot-flashed TWRP instead (made sure to use an ICS version since the JB firmware didn't flash, and the NVFlash bootloader I had was based on the ICS bootloader), which worked, and I booted into recovery. I used TWRP to flash the ICS firmware (I actually had it on my internal SD card in August, but I could have also pushed it with ADB if I didn't already have it), and I got a functioning tablet again.
Next, to upgrade to Jellybean correctly, I booted into Android and used ADB to push the Jellybean firmware to my tablet. I put it on the root of the internal storage, and the tablet saw it and alerted me to the update. Since TWRP had been replaced by the stock recovery when I flashed the ICS firmware, I just let the tablet do its thing with the update, and I ended up with a perfectly-functioning stock Jellybean ROM. I then performed each subsequent update (I never once skipped any update steps) the same way until I was on the newest 4.1.1 firmware (I'm not updating to 4.2.1 until CM10.1 works with it).
I'm not sure how much research you did before you updated your tablet, but I was trolling the TF300 forums for a good 2 or 3 hours before I even tried upgrading, and I still had trouble (I never saw any posts about people trying to fastboot-flash JB over ICS, so I didn't know it wouldn't work until I tried it at least 3 times). From the limited details you provided, it doesn't sound like you did much searching before you started flashing. In the future, it may be a good idea to research a lot more than you think you have to before flashing things on expensive devices.
Also, in the future, when you're asking for help like this, it's best to go overboard on the details - just like a murder investigation, we want to help you figure out what killed your tablet, but we can't do that if you don't tell us about the strange footprints you saw in your neighbor's lawn the night before. Mention every single icon or word that appears on the tablet, every single button-press you've made, every keystroke you've typed, etc., whether it seems important or not. We can't be there with you, so you have to bring your situation to us.
At this point, the only advice I can give is to let the tablet die, charge it again (so the battery's full but the tablet's powered off), and try again when the battery's full. If you can get ADB to work while the tablet is trying to boot recovery, you may be able to flash a new recovery and then try flashing the ICS firmware (flashing the JB firmware might work, but then you can't use NVFlash). That's about the best you can do if you can't get it into fastboot mode (short of RMAing your tablet). If you can get fastboot to work somehow, then you can easily flash a new recovery and follow the steps I took. But if you do get your tablet booting with the ICS firmware, perform the NVFlash backups ASAP before you update to Jellybean.
I hope you can get your tablet to work. I thought mine was a goner until I got lucky with an updated fastboot. Now, I'm ecstatic that it works, and I'm going to be a lot more careful in the future.
Hi,
I've come here as last resort, been trying to upgrade to Androwook 2.2 but always getting stuck in bootloop on Asus load screen. I'll try and be as detailed as possible concerning what I've already tried, but please bear with me as I'm quite a beginner with Android;
I'm currently running Androwook 2.11 on my TF700, but I'm getting some small issues such as frequent Google Play crashes and random restarts, it's livable but I wanted to upgrade to 2.2, which seems to have quite a lot of fixes compared to 2.11.
My Infinity is unlocked and rooted, I've done a complete nandroid backup using TWRP 2.6. which I pushed using ADB/Fastboot method, but there is something I don't quite understand; when I boot into bootloader using volume down and power buttons, I only see 3 icons, the USB icon is missing from the lot. Message on the top left says "Key driver not found... Booting OS, Android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.14.4-20130329" A03, Satrting Fastboot USB download protocol". Funny thing is that running the "adb devices" command from my Windows 7 Ultimate PC results in a blank "List of devices attached" message, but when running the "fastboot -i 0x0B05 flash recovery twrp.blob" it actually flashes the device correctly. Furthermore, when running "adb devices" while booted into the OS, the device is recognized but indicated as offline. Is the fact that I'm not seeing the USB icon in bootloader a problem or is it ok as fastboot still seems to work?
Anyway I download and copy the "13683789011409181222_Hairybean 2.2".zip file to my external SD card, follow the full instructions as indicated on the official Androwook XDA thread, installation is successfull but on reboot I always go into the Asus logo bootloop. I've left this running for about 30 minutes with no success, the Rom just doesn't boot up.
So I started searching the forums for solutions and tried what I could find; found some guys saying that checking the "Install custom boot animation" box during the Androwook setup before the installation seemed to have gotten them out of bootloop, but didn't work for me. I've of course tried to redownload the Hairybean 2.2 zip file thinking that it might have gotten corrupted but 3 different download locations and still no success.
I'm thinking that pushing Androwook 2.2 via ADB/Fastboot might help, but I'm not quite sure of exactly how to do that, anyone think it's worth a try?
I can't list exactly everything I've tried to get this working as I've been trying for about a month now, but believe me, I've spent a lot of time searching and trying, to no avail. So I would really appreciate it if someone could take the time to accompany me to Androwook 2.2, back to 2.11 and really getting frustrated now
Thanks in advance!
Foolmax said:
Hi,
I've come here as last resort, been trying to upgrade to Androwook 2.2 but always getting stuck in bootloop on Asus load screen. I'll try and be as detailed as possible concerning what I've already tried, but please bear with me as I'm quite a beginner with Android;
I'm currently running Androwook 2.11 on my TF700, but I'm getting some small issues such as frequent Google Play crashes and random restarts, it's livable but I wanted to upgrade to 2.2, which seems to have quite a lot of fixes compared to 2.11.
My Infinity is unlocked and rooted, I've done a complete nandroid backup using TWRP 2.6. which I pushed using ADB/Fastboot method, but there is something I don't quite understand; when I boot into bootloader using volume down and power buttons, I only see 3 icons, the USB icon is missing from the lot. Message on the top left says "Key driver not found... Booting OS, Android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.14.4-20130329" A03, Satrting Fastboot USB download protocol". Funny thing is that running the "adb devices" command from my Windows 7 Ultimate PC results in a blank "List of devices attached" message, but when running the "fastboot -i 0x0B05 flash recovery twrp.blob" it actually flashes the device correctly. Furthermore, when running "adb devices" while booted into the OS, the device is recognized but indicated as offline. Is the fact that I'm not seeing the USB icon in bootloader a problem or is it ok as fastboot still seems to work?
Anyway I download and copy the "13683789011409181222_Hairybean 2.2".zip file to my external SD card, follow the full instructions as indicated on the official Androwook XDA thread, installation is successfull but on reboot I always go into the Asus logo bootloop. I've left this running for about 30 minutes with no success, the Rom just doesn't boot up.
So I started searching the forums for solutions and tried what I could find; found some guys saying that checking the "Install custom boot animation" box during the Androwook setup before the installation seemed to have gotten them out of bootloop, but didn't work for me. I've of course tried to redownload the Hairybean 2.2 zip file thinking that it might have gotten corrupted but 3 different download locations and still no success.
I'm thinking that pushing Androwook 2.2 via ADB/Fastboot might help, but I'm not quite sure of exactly how to do that, anyone think it's worth a try?
I can't list exactly everything I've tried to get this working as I've been trying for about a month now, but believe me, I've spent a lot of time searching and trying, to no avail. So I would really appreciate it if someone could take the time to accompany me to Androwook 2.2, back to 2.11 and really getting frustrated now
Thanks in advance!
Click to expand...
Click to collapse
I can only shed a tiny little light on your problem since I am not familiar with Androwook.
JB 4.2 defaults to fastboot mode if and when you boot into the bootloader. So in 4.2 you only have the icons for recovery, Android and Wipe Data.
To use ADB you have to be booted into the rom. Actually, I have read with the correct drivers yo can also use ADB in recovery, but I have never tried that myself.
Just ignore the 'key driver not found'. Every TF700 displays that message when you boot into the BL.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
AndroWook 2.2 works fine on my TF700 and technically it should on yours. It shares the same base as CROMi-X 4.x. Have you tried CROMi-X to see if it boots?
I think flumpster recommended you do a clean install for AndroWook 2.2 as well have you tried that? Also which bootloader are you on? I'm reluctant to recommend TWRP 2.6 just yet as users have reported some problems with it, so I'd also recommend you drop back down to TWRP 2.5.
Thanks for your replies, I was beginning to despair when I saw that my post had 35 views and no replies
@berndblb: Thanks for that confirmation, at least I can stop searching in that direction, it's just that most tutorials, even recent ones, indicate the USB icon, I guess there musn't be many of us on TF700 running JB roms.
@sbdags: nope, haven't tried CROMi-X yet, will do when I get home after work tonight if you think it's worth it, thanks for the tip. Concerning the clean install I've already tried if you mean completely wiping Internal memory via TWRP. I just haven't wiped the SD card as it was containing the rom.
Concerning the bootloader I thought I had given the version in my first post (Android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.14.4-20130329" A03), isn't that it? I know the bootloader could be an issue as originally I installed it with a pack destined to the TF300, that might be something I could try, but which bootloader shoul I install and what is the best method for installing it? If that isn't my bootloader version where can I find it?
I know what you mean with TWRP 2.6, I'm ususally also very carefull with new versions, but have same issue on TWRP 2.5 and 2.4.4 (in fact most of my failed attempts were done on 2.4.4), haven't tried lower yet.
Foolmax said:
Thanks for your replies, I was beginning to despair when I saw that my post had 35 views and no replies
@berndblb: Thanks for that confirmation, at least I can stop searching in that direction, it's just that most tutorials, even recent ones, indicate the USB icon, I guess there musn't be many of us on TF700 running JB roms.
@sbdags: nope, haven't tried CROMi-X yet, will do when I get home after work tonight if you think it's worth it, thanks for the tip. Concerning the clean install I've already tried if you mean completely wiping Internal memory via TWRP. I just haven't wiped the SD card as it was containing the rom.
Concerning the bootloader I thought I had given the version in my first post (Android cardhu-user bootloader <1.00 e> released by "ww_epad-10.6.1.14.4-20130329" A03), isn't that it? I know the bootloader could be an issue as originally I installed it with a pack destined to the TF300, that might be something I could try, but which bootloader shoul I install and what is the best method for installing it? If that isn't my bootloader version where can I find it?
I know what you mean with TWRP 2.6, I'm ususally also very carefull with new versions, but have same issue on TWRP 2.5 and 2.4.4 (in fact most of my failed attempts were done on 2.4.4), haven't tried lower yet.
Click to expand...
Click to collapse
Do me a favour go to my CROMi-X thresd (linked in my sig) for the TF700 and download and install the bootloader and recovery package for your SKU. This will give you a working bootloader on 10.6.1.14.8 and TWRP 2.5
Then we can take it from there.
sbdags said:
Do me a favour go to my CROMi-X thresd (linked in my sig) for the TF700 and download and install the bootloader and recovery package for your SKU. This will give you a working bootloader on 10.6.1.14.8 and TWRP 2.5
Then we can take it from there.
Click to expand...
Click to collapse
It'll be done tonight as soon as I get home, thanks for your time, I'll keep you posted ASAP.
Well, your advice worked; thanks a lot! Only thing is that Androwook still won't install but your Rom does, I'm busy testing it at the moment to see if it suits me, might stay on it, so far so good (well done for that work!)
Downloaded the 10.6.1.14.8 WW Bootloader and TWRP 2.5.0.0, dropped it on my SD card and flashed it via Recovery. I immediately tried to flash Androwook again after the successfull installation of the bootloader and recovery, but same thing happened; bootloop on ASUS screen. One of the things I haven't tried yet is to Wipe Cache/Delvik after the Rom installation, before the reboot to the actual Rom, could that make a difference?
Noticed two things when installing the above package via TWRP though; you say the install should last about a minute, on my device in 20 seconds it was done, blue bar just progressed in two phases; once until halfway and full almost 10 seconds later. In TWRP, after each message during the installation process I'm getting a "Done" line, but on the last command, which is "updating partition details", I'm not getting the "Done" confirmation, it just stays on that last line. Same when I click the top right icon (right of "back" and "home" buttons buttons on TWRP Home screen); it starts updating partitions but freezes right there, have to restart tablet with power button to get back in Recovery. Could there be something screwed up in my partitions?
Foolmax said:
Well, your advice worked; thanks a lot! Only thing is that Androwook still won't install but your Rom does, I'm busy testing it at the moment to see if it suits me, might stay on it, so far so good (well done for that work!)
Downloaded the 10.6.1.14.8 WW Bootloader and TWRP 2.5.0.0, dropped it on my SD card and flashed it via Recovery. I immediately tried to flash Androwook again after the successfull installation of the bootloader and recovery, but same thing happened; bootloop on ASUS screen. One of the things I haven't tried yet is to Wipe Cache/Delvik after the Rom installation, before the reboot to the actual Rom, could that make a difference?
Noticed two things when installing the above package via TWRP though; you say the install should last about a minute, on my device in 20 seconds it was done, blue bar just progressed in two phases; once until halfway and full almost 10 seconds later. In TWRP, after each message during the installation process I'm getting a "Done" line, but on the last command, which is "updating partition details", I'm not getting the "Done" confirmation, it just stays on that last line. Same when I click the top right icon (right of "back" and "home" buttons buttons on TWRP Home screen); it starts updating partitions but freezes right there, have to restart tablet with power button to get back in Recovery. Could there be something screwed up in my partitions?
Click to expand...
Click to collapse
Sorry should have said don't flash the bootloader package and rom at the same time.
Not sure what is going on with the freezing. It doesn't sound quite right. Sorry I don't know the fix.
sbdags said:
Sorry should have said don't flash the bootloader package and rom at the same time.
Not sure what is going on with the freezing. It doesn't sound quite right. Sorry I don't know the fix.
Click to expand...
Click to collapse
Absolutely no need to apologize, you helped me out man, thanks^^
When I said immediately I meant after a reboot, might not be an android expert but I know that rebooting after each process is strongly advised
Anyway, point is; TWRP 2.5 and bootloader are correctly installed (I can do without the partition thingys I guess), and your Rom seems fine and stable, so I'm all fixed basically, I'll just try to avoid flashing new Roms on this tablet, might be a hardware issue.
Another nub question to finish; what is the officail way of marking this thread a solved?
Edit: Just donated a couple of bucks to your account, Rom really seems stable, haven't had a single issue yet, thanks again!
Foolmax said:
Absolutely no need to apologize, you helped me out man, thanks^^
When I said immediately I meant after a reboot, might not be an android expert but I know that rebooting after each process is strongly advised
Anyway, point is; TWRP 2.5 and bootloader are correctly installed (I can do without the partition thingys I guess), and your Rom seems fine and stable, so I'm all fixed basically, I'll just try to avoid flashing new Roms on this tablet, might be a hardware issue.
Another nub question to finish; what is the officail way of marking this thread a solved?
Edit: Just donated a couple of bucks to your account, Rom really seems stable, haven't had a single issue yet, thanks again!
Click to expand...
Click to collapse
Cheers mate for the donation! Glad you got it all sorted!
Darren
Hello again,
I would like to install the least buggy Jelly Bean ROM onto my ASUS Transformer Pad TF300T. I have never rooted my Tablet before and I am on the latest OTA update by ASUS
Android Version 4.2.1
Build JOP40D.WW_epad-10.6.1.27.5-20130902
I very much would appreciate some hand holding on this whole process. I have signed up to the CyanogenMod website but as yet not had any replies.
I don't really know what ROM to go for as its a minefield, but I would like the most stable Jelly Bean version. Not too keen on moving over to Kit Kat yet.
I have never done this before and I have quite a bit of trepidation about the whole process but as it is, my official ASUS Jelly Bean operating system is laggy and the battery drain is exceptionally noticeable. The tablet can drain empty on Stand By within a couple of days. I have tried all the tricks to extend battery life, including charging Tablet and battery spereately, Cold Boots and Fresh installs but nothing helps.
Cheers
the lemming said:
I don't really know what ROM to go for as its a minefield, but I would like the most stable Jelly Bean version. Not too keen on moving over to Kit Kat yet.
Click to expand...
Click to collapse
If you ask 5 people about this you will get at least 10 opinions...
I choose not to vote on that part of your question.
I have never done this before and I have quite a bit of trepidation about the whole process
Click to expand...
Click to collapse
The most important point is to select the right recovery version for your bootloader/ROM. As you are going to install a 4.2 ROM, I suggest TWRP 2.5.0.0-42. Not the latest, but proven and stable. Make sure to pick the -42 version matching your bootloader. The next point is: don't use the wipe data option on the bootloader screen, but use the wipe options in recovery instead.
If you follow these two points, you avoid most of the issues that get reported over and over again.
Sent from my TF300T using Tapatalk
f69m said:
The most important point is to select the right recovery version for your bootloader/ROM. As you are going to install a 4.2 ROM, I suggest TWRP 2.5.0.0-42. Not the latest, but proven and stable. Make sure to pick the -42 version matching your bootloader. The next point is: don't use the wipe data option on the bootloader screen, but use the wipe options in recovery instead.
If you follow these two points, you avoid most of the issues that get reported over and over again.
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
Hello
Thank you for replying. I am very green at all this and I don't want to mess things up. You mention getting a matching boot loader. How do I check what bootloader I posses and where do I find the correct stuff?
I now next to nothing about this process other than bricking my Samsung Ace phone a year ago and I have not dabbled in this since then. I am willing to get my hands dirty but I want to know how to get out of trouble should I do something stupid, which will most definitely happen.
Are you able to post a link to a tutorial that will help me out?
Cheers
the lemming said:
Thank you for replying. I am very green at all this and I don't want to mess things up. You mention getting a matching boot loader. How do I check what bootloader I posses and where do I find the correct stuff?
Click to expand...
Click to collapse
You can see the version of your bootloader at the top left of the bootloader screen. It should match the last Asus stock ROM version you installed: 10.6.1.27.5 in your case. This is the latest bootloader available and should work fine with all up-to-date 4.2 ROMs. Read the first post carefully, it should mention, which bootloader versions are supported. No nee to update.
Note that flashing custom ROMs will not touch your existing bootloader.
I now next to nothing about this process other than bricking my Samsung Ace phone a year ago and I have not dabbled in this since then. I am willing to get my hands dirty but I want to know how to get out of trouble should I do something stupid, which will most definitely happen.
Click to expand...
Click to collapse
Have a look at nvflash flatline for your bootloader 4.2. It allows you to extract some files from your device. If you keep those safe, you are almost brick-safe, as you can then use nvflash to recover your tablet from most known issues.
http://forum.xda-developers.com/showthread.php?t=2545610
Are you able to post a link tersion o a tutorial that will help me out?
Click to expand...
Click to collapse
I am not aware of a guide specifically for flashing custom ROMs, but most ROMs should have good instructions in the first post. Anyhow, you can browse the stickies in the General forum. They have a lot of good information.
Sent from my TF300T using Tapatalk