At least, I think I installed incorrectly. I'm currently unlocked and rooted on stock MB1. I'm decently tech savvy, but I am not a programmer and need a bit of handholding in this environment.
A few months ago I was wanting to install CM 10.1 and read that it needed an older bootloader, which I found, downloaded, and flashed in Odin. However, I flashed with the bootloader option rather than PDA which I'm thinking was a mistake. Since then, all I've really noticed is that google now no longer works, and there have been some odd slow-downs, like the keyboard taking forever to show up, even after a factory reset. Oh, also, when I plug my phone into the computer, now some Verizon autorun update stuff wants to get in the way, even though I've disabled any autorun programs. This installer only lasts a few seconds before switching to normal usb file mode.
I'm now looking to update and probably install jellybean17, so I'd rather fix before I do that.
a) Did I actually make a mistake I need to fix? Or is what I've noticed merely coincidental and due to something else?
b) If so, how can I fix it?
Thanks for any pointers!
Hmmmmm weird.... You may wanna install VRBMF1 firmware in Odin, then reroot and install ROM of choice. I've also never heard of cm requiring a different bootloader.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 4 Beta
Related
Hey guys, I just got a T-Mobile SGH-T869 and it came with Honeycomb on it.
I've been able to root it (which was as dumb as flashing a ZIP on the stock recovery), and I've flashed the CWM 5 I found (here). However, I'm unable to flash CM10 from that, so I'm looking to figure out what's wrong or the missing step.
Any suggestions?
Just to follow up on my own issue, I figured it'd be a good idea to update my SGH-T869 to ICS, because HoneyComb is kinda terrible.
For this device, at least for now, the "official" ICS update isn't being made available over the air, only available via the Samsung Kies program.
Its totally free and you can get it for Mac or Windows here http://www.samsung.com/us/kies/
The procedure to update was seriously as dumb as "Install Kies, then plug in your device".
Kies should auto-detect and in the case of my SGH-T869, it immediately offered to update the firmware. However, Kies requires your battery to be charged up before it'll let you proceed, so initially it didn't allow me to flash (my battery was down to around 43%).
After updating this way, everything was back to stock and I had no root anymore.
I re-obtained root by downloading the two attached files. The attached CWM is a "temporary" touch-enabled version. Flashing it from the stock recovery boots you into CWM but after you reboot, its gone. I booted to that and then flashed the attached root.zip, which re-established root on my tablet.
So, sort of progress. Next step: figure out how to get CM10 on this bad boy, since the stock ICS kinda blows
Hi all, Soon to be joining the ranks of happy tf300t owners but I have a couple of questions.
I bought my tf second hand and only afterwards I noticed that It comes rooted and unlocked.
Will this affect my ability to get OTA updates? And will I be okay to use factory restore when I get it to be sure its securely wiped (I softbricked my hannspad once by performing a factory reset after applying a honeycomb ROM, still don't understand why but just want to be sure theres no chance of that happening here.)
If it does affect me is there an easy way I can set the device to a way that I can get OTA? And do factory resets if thats even an issue (I do have some limited flashing experience with my Hannspad).
And lastly are there any must have apps? (Willing to pay) Or even just tweaks etc to make my transforming experience more pleasant?
Running JB 4.1.1
Well if it already unlocked then doing a factory reset will be fine and will not brick anything. But before you do that i would boot into recovery and make sure its twrp 2.2.2.0 and not another twrp version or clockworks.
No you can't get OTA updates since its unlocked but that is not a big deal, just wait for a Dev to add it to there ROM or just get the stock firmware from asus site and flash it yourself.
flashing the updates your self is only slighty more work the the ota ones mate but as its already roote thats makes up for it and the first few apps that come to mind are adaway, titanium back up, bsplayer (for movies) and dolphin browser (with the jet pack add on)
Just so you know, if you are running jb, do not attempt to flash anything ICS, either ROM or recovery. Make sure what you're flashing is designed for jb, otherwise you might brick your tablet.
You can't get ota when unlocked, but Asus is good for posting their Roms on their website shortly after an ota update is released. There are several guides here which tell you different ways you can install them. Its not hard at all.
Finally, if unlocked, you cannot relock.
Hope this helps a little.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Hello I am still dealing with a weird problem that I posted on this forum over a year ago that was never resolved. Basically my tablet is stuck running Android version 4.1.1 (Build JRO03C.US_epad-10.4.4.25-20121228) because if I upgrade to any new versions (whether I do it as OTA or via micro USB) my wifi card stops functioning (it does not see any networks). Anyways I even went so far as to RMA it and Asus said they fixed it, shipped it back to me, but in reality all they did was roll me back to 4.1.1, saw the wifi was working and shipped it back to me saying they "fixed" it. Well of course the second I got it back I installed the OTA and wifi broke again... So I just rolled back to 4.1.1 and said screw it, I just won't update it anymore. Well this week I figured I'd try installing the latest OTA and hoped that this version would not kill my wifi, unfortunately the same exact issue has occurred and thus I have once again rolled back to v4.1.1 and my wifi works perfectly...
TLDR; Anyways apologize for the rant/story but basically I am stuck with using version 4.1.1 of Android and am considering flashing a custom rom to try and resolve some issues I am having with the stock rom's wifi, however the official bootloader unlock tools only say they work on version 4.0 (ICS) or version 4.2 (JB). I'm stuck on v4.1.1 so which tool should I use (or am I out of luck)? Thanks
v7 worked your JB version, but I think v8 will work as well. Just try them both - it's just an app. Either it works or not....
But that is the weirdest thing I've heard in a while (reg. WiFi).
What have you done on your router side? I cannot believe this is a problem with the tablet's wifi card.
Is this 'wifi not working' consistent on any router, any network?
Did you reset the router, change the channel?
Do you have possible interference: microwave, bluetooth speakers, bluetooth enabled or any other device that uses radio waves anywhere in the vicinity of the tablet?
berndblb said:
v7 worked your JB version, but I think v8 will work as well. Just try them both - it's just an app. Either it works or not....
But that is the weirdest thing I've heard in a while (reg. WiFi).
What have you done on your router side? I cannot believe this is a problem with the tablet's wifi card.
Is this 'wifi not working' consistent on any router, any network?
Did you reset the router, change the channel?
Do you have possible interference: microwave, bluetooth speakers, bluetooth enabled or any other device that uses radio waves anywhere in the vicinity of the tablet?
Click to expand...
Click to collapse
Thanks appreciate the reply - I just wasn't sure if using the wrong unlocker could brick my device... I'll give 8 a try first then 7 if necessary. The ironic part is that it requires a network connection to complete the unlock operation (I guess so Asus can cross your S/N forever off of their list of devices under warranty).
I agree that this is a strange problem as I have not seen anyone else report it. Basically I tried resolving this about 13 months ago with the help of this board and as mentioned I finally had to RMA it, but ASUS just rolled the version back instead of fixing anything and at that point I just wanted to enjoy using my tablet more than I wanted to fight with ASUS's customer service reps who effed up the first RMA job (the language barrier was also apparent in my interactions with them)...
Since over a year has gone by since the last time I tried an OTA, I hoped that the latest update would not have the same issues but alas, I'm not that fortunate.
As far as what I've tried - I have tried connecting to different networks and changing router channels and checking for interference, but the thing is, I'm quite certain the problem is with the tablet. When I first had the problem I lived in an apt building where I could 'see' 10+ wifi networks at any given time on all different channels with different routers/security settings etc. As soon as I applied the OTA the tablet could no longer 'see' any of them (even as I sat with my laptop/phone connected to wifi right next to it). I now live in a house (and have a different ISP, and a different router) and tablet works perfectly when on version 4.1.1. I don't have as many wifi networks visible from my house, but can still see a few of my neighbor's wifi networks both on the tablet (v4.1.1) and on other devices. But the second that I upgrade, all of them disappear from the tablet's view (but continue to be visible/work on other devices). I have turned wifi on/off, turned airplane mode on/off, tried connecting via wifi direct, rebooted, cold booted, booted into recovery, factory reset all data, etc. but nothing works because the tablet cannot see any wifi networks. And the second that I rollback to version 4.1.1 the wifi works perfectly... I have upgraded and rolled back probably at least 6 times and it is always the same result.
I do also get another weird side affect when I upgrade - the tablet refuses to turn off when I'm on any version higher than 4.1.1. So if I press "Shut Down", the tablet displays "shutting down" and the screen goes black and becomes non-responsive (as do the buttons, just as you would expect when turning off), but it does NOT actually shut down because if I come back 30 mins, an hour, 2 hours later I can feel it running very hot. The only way to truly shut it down is to let the battery drain...
So maybe a better question on my part would have been, do you think installing a custom ROM will even help resolve this issue? Or should I continue using 4.1.1 and not risk making the situation worse with custom ROMS?
WiFi problems are often kernel related..... Did you always take the update OTA?
Did you ever try to flash the latest firmware version manually? OTA updates do go wrong sometimes....
Although repeatedly???? It's weird. Maybe the server your tablet pulled the OTA from hosts a bad copy????
If you do not want to unlock, manually flashing the firmware would be one thing to try. OTA's patch the existing system, replace old files with new ones where necessary. Manually flashing the firmware replaces everything - a totally new installation of everything: bootloader, recovery, kernel, system and data.
But you cannot make it worse by flashing a custom rom. You unlock, flash a custom recovery (which does not change anything else on your system), then you make a nandroid (backup) of your current 4.1.1 system before you flash a rom. So you would always be able to go back to where you are now. On a custom rom you could even try out different kernels, which often are the root cause of wifi problems..
The thing is: If you want to flash a current custom rom like CROMi-X, based on Asus JB 4.2.2, or CROMBi-KK/CM11 which are KK roms, you always have to update your bootloader first. Your .25 bootloader is too old for any current rom.
You can easily do it once you have a custom recovery installed, but even easier would be to update to the latest Asus firmware 10.6.1.14.10 (after unlocking), then flash the custom recovery (TWRP 2.8.1.0), then flash a rom of your choosing.
Downside of this route would be you wouldn't have that 4.1.1 nandroid I mentioned earlier.....
Nahhh - thinking about it, I would recommend you go this route:
Unlock,
flash an older version of TWRP compatible with your current bootloader (TWRP 2.6.1.0 is ok)
make a nandroid of your current system
do a full wipe of cache, Dalvik and data in recovery
flash the 10.6.1.14.10 bootloader in recovery (I can talk you through it)
flash TWRP 2.8.1.0
flash a rom of your choice
Check out my guide, link in my signature, and let me know if you have questions
Thanks - I was able to successfully unlock my device with v7 of the unlock tool (v8 wouldn't even install). Thanks too for the advice on how to flash a custom rom safely. I've never flashed a custom rom before (have rooted a different android device before tho), so I appreciate any help.
I downloaded the blob file for TWRP 2.6.1.0 from here (techerrata.com/browse/twrp2/tf700t), but not sure how to proceed next, (also I don't see a link in your signature to your guide, but I am running a bunch of script blocking addins so maybe that's why) seems like all the guides I am finding say I need to get a copy of a fastboot program (but don't provide links), where can I find that? Again, I appreciate the help.
Sorry, my bad, I don't have a signature on XDA - wrong forum. LOL
My thread is here: http://forum.xda-developers.com/showthread.php?t=2688891
Ask any questions you may have in that thread, but it should cover your questions - I hope
As the title of this suggests, I messed up BIG TIME when attempting to get Cyanogenmod on my Verizon Galaxy S3.
Long story short, I tried putting CWM on my phone without looking up things about it, like whether or not the bootloader was locked for 4.4.2 Kitkat, which it was, and has been since 4.3 Jellybean, which I did not know at the time I tried screwing with my device (which was around a week ago), and I started trying to mess with the phone without knowing what the hell I was doing, since the last time I tried modding a GS3 was over two years ago.
Long story, well, long, I tried installing CWM via the ROM Manager app, and, upon installing it, I screwed up the recovery mode on the phone. It wasn't a big deal, until I decided I wanted to put the latest version of Cyanogenmod on it, instead of using the stock Touchwiz interface.
Well, a couple days ago, I stuck Safestrap on it, and was able to use that as a recovery mode, since the normal recovery mode was locked off, entirely.
I figured that, tonight, I would look up ways to stick Cyanogenmod on my GS3.
I found a couple ways to do so, downloaded the gapps file I needed, the SU binary update, as well as an unofficial version of Cyanogenmod to let me use 5.1 Lolipop.
Well, I wiped the cache on the phone, as well as the dalvik cache, and factory reset the thing, ad went to the folder I put the gapps, SU binary update, and CM files in, and tried installing them.
Well, the SU update went fine.
gapps won't install.
The CM file I'm using SAYS it's installed, but the phone doesn't have an OS, which is confusing me.
I don't know if the phone is bricked, I just know that I did something stupid, and I don't know how to put an operating system back on the phone, either through Kies or Odin (I can't install anything from the SD card in the phone, because now I can't access it, since when I boot it up, there's no OS, and I need one to access the files on the device).
Whenever I try using Odin to put either a stock firmware version on it, it fails.
My phone, in DL mode, says: "SECURE CHECK FAIL : RECOVERY"
I don't know what this means, but I think it means I'm pretty well screwed.
I need to get rid of CWM and Safestrap via my computer, THEN reinstall the stock recovery mode on my computer, too.
I NEED to know how to do this.
If there is ANYONE out there who can help me out, or direct me to some other thread, that would be amazing, and GREATLY appreciated.
Hey there!
Just ran into some troubles with my GT-N8010. I had been using stock on it for quite awhile, but have been noticing that many of the newer apps do not work with JB. I had rooted and used my Asus Transformer before, figured that it was probably about time to get some more life out of the Note 10.1.
My first option was to upgrade from JB to KitKat. Unfortunately there is not an official update in Canada, but using Odin I should have been able to upgrade it. This is where the issues came. First, it failed twice. I restarted the computer, and tried it once more. Success! It was downloading. It took a few moments, but eventually it failed as well. The download stopped and I was left looking at my tablet having 3/4 of the install complete. I left it for awhile, hoping that it would restart itself or reload. Nothing happened, and I had to restart the tablet.
Situation now: I am stuck at the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
First thing I tried was getting to the download screen, so I have that. I figured I could just flash it back to the offical JB from Canada, but now it's like the computer won't recognize the device. Even unplugging and plugging the USB back in does not even give me the PC Recognizing sound. I moved to a laptop, and it could read the device, but once I installed Samsung USB and Keis, it stopped. Odin doesn't recognize it and I am not sure where to go from here.
Is using the SD card an option? Can I somehow force the computer to read the tablet?
I have looked through the forums, but didn't really see much in the way of help.
I hope to hear from you guys! Thanks in advanced! If I need to provide more information, please ask.
Is using the SD card an option>>> NOT for stock custom rom only .
I don't mind installing a custom rom at this point. If it is still an option at this point the I don't mind at all. If there is anyway you could point me towards that option, I will definitely give it a shot.
The development threads.
You will need to flash a custom recovery tar through Odin .
https://forum.xda-developers.com/showthread.php?t=2490954
Part of the problem is that the Odin, even my PC, are not recognizing the the Tablet is connected through my USB. So I cannot flash anything right now.
I figured it out. It was all because of my cord. I went out and got a new one, flashed 4.4.2 easily. Hope that helps everyone who has issues as I did.
elevenstewart said:
I figured it out. It was all because of my cord. I went out and got a new one, flashed 4.4.2 easily. Hope that helps everyone who has issues as I did.
Click to expand...
Click to collapse
Hi, I've read your posts. Helpful.
I'm in the situation of having tried to flash a custom recovery, to then flash a custom ROM.
Started Odin, began to flash, then Odin showed failed.
Now the n8000 no longer starts, just hangs after the Samsung logo/music.
I do have two different cords, so will try that later.
Question, did you end up flashing a custom ROM later, and if so, which one?
Thanks.
Sent from my SM-N920C using Tapatalk
I have a Samsung Galaxy GT-N8010 (UK version), Android 4.1..2 - i need to get this up to KitKat 4.4.2 as BT Sport app won't run on below v4 - help?
Search this forum its well answered.
Or
Sammobile.
Updato.
Two firmware site