Hello all,
I just bought a tf300t that already came flashed with ParanoidAndroid 3.60. It shows that it has a 4.1 bootloader (10.4.2.20) but is running JB 4.2.2. From what I understand flashing a 4.2 rom on a 4.1 bootloader will brick the tablet, but I must be mistaken since it's running fine. I would like to update to the 4.2 bootloader and flash a different rom since the one currently on it is a bit sluggish and unstable. I've read around the forum but the posts I've found usually start with the tablet having a stock rom. Any help would be greatly appreciated since I don't want to brick this thing
I'm going to use this guide to get it back to stock, but i'm a bit confused on one part. It says 10.4.2.20 is supposed to be running JB 4.1 but my tablet is not. Does that make any difference?
http://forum.xda-developers.com/showthread.php?t=2195883
falcaraz said:
I'm going to use this guide to get it back to stock, but i'm a bit confused on one part. It says 10.4.2.20 is supposed to be running JB 4.1 but my tablet is not. Does that make any difference?
http://forum.xda-developers.com/showthread.php?t=2195883
Click to expand...
Click to collapse
whay not just install twrp and make a nandroid back up then flash a custom rom like cromi-x, performance will be way better and the nandroid backup will help protect your tablet (although ive never had to use it lol)
Related
Before anybody says to use the search function, I've been looking through the general topics non-stop for one that applies to my situation, and either it slipped through the cracks (likely) or it doesn't exist (not likely).
Basically, my tablet is rooted and unlocked, and I'm on ICS; the first one that had face unlock in it. I'd really like to update my tab to JB, but I need to be pointed toward directions for updating a rooted and unlocked tab. But on top of that, I also need recent instructions, because I know that earlier attempts at getting this thing updated have resulted in lots of bricked tabs.
If anybody could tell me if it's possible to update my tablet to JB right now, I'd appreciate it, and if someone has figured out how to do it, can you please point me toward that thread? I'd really appreciate it.
-Tim
I'm in the same configuration, custom-ics-rom with twrp recovery on unlocked device.
I believe the first thing to do is enabling NVFLASH, that will make things safer also in the worst cases.
I did that and now hopefully I have an unbrickable device.
I'm a bit confused on how to go forward, I know that there are two versions of twrp, maybe I should install the JB version, booting inside it and then flash the downloaded JB update from ASUS site, or use the twrp for ICS for flashing and after that install the JB version ?
Anyone knows what is the correct option ?
Giuseppe
Tim 13 said:
Before anybody says to use the search function, I've been looking through the general topics non-stop for one that applies to my situation, and either it slipped through the cracks (likely) or it doesn't exist (not likely).
Basically, my tablet is rooted and unlocked, and I'm on ICS; the first one that had face unlock in it. I'd really like to update my tab to JB, but I need to be pointed toward directions for updating a rooted and unlocked tab. But on top of that, I also need recent instructions, because I know that earlier attempts at getting this thing updated have resulted in lots of bricked tabs.
If anybody could tell me if it's possible to update my tablet to JB right now, I'd appreciate it, and if someone has figured out how to do it, can you please point me toward that thread? I'd really appreciate it.
-Tim
Click to expand...
Click to collapse
Keep ICS, as JB will cause much trouble especially if you are rooted, trying to OC and is generally slowein my opinion
I prefer to try it anyway, tomorrow I will try flashing, after all if something will go wrong I should be able to recover with nvflash.
[
QUOTE=grimsonfart;32974661]Keep ICS, as JB will cause much trouble especially if you are rooted, trying to OC and is generally slowein my opinion[/QUOTE]
Thank you, Grim. That's disappointing to hear about JB, but if you think that my current build is better than that (which makes sense considering I've seen at least one thread about downgrading from JB to ICS), then I will keep my tab on ICS for now, and thank you for your input, I appreciate it.
-Tim
If you have twrp recovery, can't you download the jb ROM from the Asus site for your region and flash it in? I'm unlocked and that's how I upgraded one version of jb to another, but my ICS to jb was ota, so in your case I can't speak from experience. There is a full upgrade, and root guide in the general section.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
I just managed to do what you re looking to achieve.
I m pretty noob so it tok me a whole day to figure it out.
So first download jb update on asus website (pick the right one for ur type of tf300)
Flash it through adb
At that point i got jb installation working but bootloop
So i flashed jb version of twrp (adb)
I then went in recovery and flashed clean rom 2.5 which worked flawlessly
Just for the fun i did factory reset afetrwards and stock jb eventually launched right
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
gst0098 said:
I'm in the same configuration, custom-ics-rom with twrp recovery on unlocked device.
I believe the first thing to do is enabling NVFLASH, that will make things safer also in the worst cases.
I did that and now hopefully I have an unbrickable device.
I'm a bit confused on how to go forward, I know that there are two versions of twrp, maybe I should install the JB version, booting inside it and then flash the downloaded JB update from ASUS site, or use the twrp for ICS for flashing and after that install the JB version ?
Anyone knows what is the correct option ?
Giuseppe
Click to expand...
Click to collapse
I successfully installed jb following the guide on this site, the only thing that was not working was the flashing of the stock rom, neither given options worked (fastboot flash recovery or fastboot flash system) , I discovered that our eepad has a partition nmed staging used for firmware installs. I then flashed with
fastboot flash staging blolb
and all went good.
Btw I find the JB better than ics, more responsive and smoother, and also if it is not yet overcooked.
Hi, I've got a Samsung Galaxy Tab 7.0 Plus (GT-P6200) which is still stuck with that unstable mess they call Honeycomb (Android 3.2), because Samsung still hasn't released their ICS upgrade in Belgium.
Is there any way to dual-boot this device with a custom ROM? I've read somewhere that it's possible, but I don't have much experience with rooting and flashing (I've done it on a few devices, but to me it seemed like it was more a matter of luck rather than skill once I found the right tutorial for the device). If so, how? I've read something about ClockWorkMod, but am a bit confused about what exactly it is.
Also, if it is possible, then which ROM would I best pick? The official ICS ROM, CyanogenMod, or something totally different? I've read this topic, so I'm a bit uncertain.
Again, if it's possible; What would be the best way to ensure I don't brick my device?
Thanks in advance.
RobinJ1995 said:
Hi, I've got a Samsung Galaxy Tab 7.0 Plus (GT-P6200) which is still stuck with that unstable mess they call Honeycomb (Android 3.2), because Samsung still hasn't released their ICS upgrade in Belgium.
Is there any way to dual-boot this device with a custom ROM? I've read somewhere that it's possible, but I don't have much experience with rooting and flashing (I've done it on a few devices, but to me it seemed like it was more a matter of luck rather than skill once I found the right tutorial for the device). If so, how? I've read something about ClockWorkMod, but am a bit confused about what exactly it is.
Also, if it is possible, then which ROM would I best pick? The official ICS ROM, CyanogenMod, or something totally different? I've read this topic, so I'm a bit uncertain.
Again, if it's possible; What would be the best way to ensure I don't brick my device?
Thanks in advance.
Click to expand...
Click to collapse
Why don't you just install a official ics rom, manualy, with odin or heimdall, you don't have to wait for kies update. You can use what ever ics you want, and flash it like that. Custom roms will void your guarantee. And it's not that hard to flash manualy just follow the steps and everything would be ok . There're many threads about flashing http://forum.xda-developers.com/showthread.php?t=1671969
and all you have to do is to find a propper rom for your device . But firs read how to flash.:good::good::good::good:
same feriern
cherven said:
Why don't you just install a official ics rom, manualy, with odin or heimdall, you don't have to wait for kies update. You can use what ever ics you want, and flash it like that. Custom roms will void your guarantee. And it's not that hard to flash manualy just follow the steps and everything would be ok . There're many threads about flashing http://forum.xda-developers.com/showthread.php?t=1671969
and all you have to do is to find a propper rom for your device . But firs read how to flash.:good::good::good::good:
Click to expand...
Click to collapse
What about this? http://forum.xda-developers.com/showthread.php?t=1807002
And I'd rather have a dual booting system, so that if the custom ROM doesn't work or is too buggy, I can still fall back to the original system.
Well just don't flash custom, flash only official, besides you can make nandbackup so if somethibg goes wrong you can easily restore your curent rom. Without any problems. Justit doesn't makesence dualbooting honeycomb and ics. You dont have kies update because of your provider, but as i said it does not matter cause youcan flash any ics region, i recomend austria britan they are stlck roms.
Sent from my GT-P6200 using Tapatalk 2
I went ahead and flashed the official 4.0.4 ROM with ODIN and appear to have been successful.
Thanks!
You should have done that a long time ago, like a few months ago, now be ready for the 22 feb. 2013 cause the jelly bean is comming to us.:victory::victory::victory::victory::victory:, no more custom roms and cyanogens.
cherven said:
You should have done that a long time ago, like a few months ago, now be ready for the 22 feb. 2013 cause the jelly bean is comming to us.:victory::victory::victory::victory::victory:, no more custom roms and cyanogens.
Click to expand...
Click to collapse
Yeah I'm sure the stock Samsung firmware will magically not be terrible (unlike previous Samsung firmware) simply because its Jellybean...
DivinityCycle said:
Yeah I'm sure the stock Samsung firmware will magically not be terrible (unlike previous Samsung firmware) simply because its Jellybean...
Click to expand...
Click to collapse
We;re pretty sure it will be impeccable just like the ICS version.
Hi,
I'm still on ICS bootloader on my TF300T, some unofficial CM based ROM and a new TWRP. How can I update my bootloader to support newest ROMs? Is it possible without ADB (ex. through terminal)? Does anyone have a ASUS ICS OFW, so it's possible to update OTA? Thanks in advance.
vegitto said:
Hi,
I'm still on ICS bootloader on my TF300T, some unofficial CM based ROM and a new TWRP. How can I update my bootloader to support newest ROMs? Is it possible without ADB (ex. through terminal)? Does anyone have a ASUS ICS OFW, so it's possible to update OTA? Thanks in advance.
Click to expand...
Click to collapse
Theres a couple ways safest i've found is normal download and update. As far as ota if your unlocked no luck there but you can download from asus website place on root of sd or internal storage and wait for triangle to come up in notification back like as if ota. I would go through each update starting from where you left of before flashing cm especially going to 10.4.2.20 to 10.6.1.8 as it uses 10.4.2.20 as base for update from there. Remember once on jb bootloader your stuck there cant downgrade back to ics and theres some major changes to 10.6.1.8 and would have to reroot once get there but with the changes becarful as to what recoveries and roms u use once on 4.2.1 u can only use roms based on that and have to use the twrp 2.4.4.0 patched recovery but there are also alot of unknowns as to asus' new update so caution read and ask before flashing because many are bricking with no fix except nvflash right now. So also i would do and nvflash back up as if something should go wrong its your best and only way outnonce on 10.6.1.8 but back up before going through all this because as of now nvflash isnt available for jb 4.2.1. Goodluck and becarful.
Heresna good thread to read and ask questions on how to go about getting to 10.6.1.8 aka 4.2.1 most of all read and ask before getting into a pickle.
http://forum.xda-developers.com/showthread.php?t=2187982
aerdely said:
Theres a couple ways safest i've found is normal download and update. As far as ota if your unlocked no luck there but you can download from asus website place on root of sd or internal storage and wait for triangle to come up in notification back like as if ota. I would go through each update starting from where you left of before flashing cm especially going to 10.4.2.20 to 10.6.1.8 as it uses 10.4.2.20 as base for update from there. Remember once on jb bootloader your stuck there cant downgrade back to ics and theres some major changes to 10.6.1.8 and would have to reroot once get there but with the changes becarful as to what recoveries and roms u use once on 4.2.1 u can only use roms based on that and have to use the twrp 2.4.4.0 patched recovery but there are also alot of unknowns as to asus' new update so caution read and ask before flashing because many are bricking with no fix except nvflash right now. So also i would do and nvflash back up as if something should go wrong its your best and only way outnonce on 10.6.1.8 but back up before going through all this because as of now nvflash isnt available for jb 4.2.1. Goodluck and becarful.
Heresna good thread to read and ask questions on how to go about getting to 10.6.1.8 aka 4.2.1 most of all read and ask before getting into a pickle.
http://forum.xda-developers.com/showthread.php?t=2187982
Click to expand...
Click to collapse
Note: Good info!
You forgot unzip once after download.
tobdaryl said:
Note: Good info!
You forgot unzip once after download.
Click to expand...
Click to collapse
Yea of course good catch. THANKS. Also in some cases may need to rename as in some times when get to 10.4.2.20 or 10.6.1.8 may have to rename. US_epad-user-10.6.1.8.zip of course not alway US could be WW for world wide or etc but as your updating may not always be the case just i've heard of some having to do this. This also works for downgrading and renaming your current firmware version as a previous version to do a reinstall had to do that once to fix a random reboot problem and works. I've heard of some downgrading as far as first jb build but thats as far as i've seen anyone can go.
Good luck as far as getting back to stock not totally sure you may know better than me or can ask some one on the thread i gave you i've never been rooted because affraid to void warranty just to safe but been doing alot of reading a research for when i decide to do so. Rooted like 10 of my passed other phones why not this one eventually just being safe from what i've seen happen to people with this new update.
aerdely said:
Theres a couple ways safest i've found is normal download and update. As far as ota if your unlocked no luck there but you can download from asus website place on root of sd or internal storage and wait for triangle to come up in notification back like as if ota. I would go through each update starting from where you left of before flashing cm especially going to 10.4.2.20 to 10.6.1.8 as it uses 10.4.2.20 as base for update from there. Remember once on jb bootloader your stuck there cant downgrade back to ics and theres some major changes to 10.6.1.8 and would have to reroot once get there but with the changes becarful as to what recoveries and roms u use once on 4.2.1 u can only use roms based on that and have to use the twrp 2.4.4.0 patched recovery but there are also alot of unknowns as to asus' new update so caution read and ask before flashing because many are bricking with no fix except nvflash right now. So also i would do and nvflash back up as if something should go wrong its your best and only way outnonce on 10.6.1.8 but back up before going through all this because as of now nvflash isnt available for jb 4.2.1. Goodluck and becarful.
Heresna good thread to read and ask questions on how to go about getting to 10.6.1.8 aka 4.2.1 most of all read and ask before getting into a pickle.
http://forum.xda-developers.com/showthread.php?t=2187982
Click to expand...
Click to collapse
I'll second this advice. I just upgraded my tablet from ICS yesterday, too, and this is exactly what I did. It worked great. I stopped at the last 4.1 update, though, because CM won't work on 4.2 yet.
And I second^2 the advice about setting up NVFlash before flashing the Jellybean update. I did that, too. Of course, I was doubly motivated by the fact that I had just recovered from a seven-month soft-brick (which was why I was still on ICS).
Anyway, good luck, and enjoy the Jellybean update.
Putting the ILLA in KILLA since 1985
Thanks, I'll NVflash first... Just where do I get androidroot.mobi bootloader from? Can't find it.
vegitto said:
Thanks, I'll NVflash first... Just where do I get androidroot.mobi bootloader from? Can't find it.
Click to expand...
Click to collapse
The NVFlash thread links to a page at androidroot.mobi about the NVFlash release. That page links to a guide. At the bottom of the guide are two things you have to download (there are many links to downloads, but you only need the two that correspond to your OS and tablet). One is the NVFlash binary. You'll know because it only contains one file called NVFlash. The other includes the specific files for your tablet, including the bootloader.
So, just follow the guide on the AndroidRoot.mobi site, and you'll be fine.
Edit: Here's the guide I'm talking about: http://androidroot.mobi/t3_nvflash/
If you're using Windows, you may actually need to download three files, the third being the drivers.
Putting the ILLA in KILLA since 1985
In windows, the android SDK/Fasrboot are more clear to me, so I'll now just download the ROMs and files for later use. Thanks everyone
Good day and thank you
I can usually find out what i want by reading the forums, but this time I need advice
my tablet is one year old and out of warranty.. and working
TF300T running 4.2.1 JOP40D.WW_epad-10.6.1.27.5-20130902
I understand that i get the unlocker from asus
but I want to unlock the bootloader , install recovery manager and make a backup
and have the ability to change the rom
on my old cell phone ICS , it was root then install CWM for backup's
I don't want to mess anything up assuming things
but from all the reading in the forums and bleeding eyes... it seems there's so many bricked devices... just terrible
did i miss a forum or walkthru on how to NOT brick the tablet
please any help would be great
thank you and take care
ttyl
Cam
aweman said:
Good day and thank you
I can usually find out what i want by reading the forums, but this time I need advice
my tablet is one year old and out of warranty.. and working
TF300T running 4.2.1 JOP40D.WW_epad-10.6.1.27.5-20130902
I understand that i get the unlocker from asus
but I want to unlock the bootloader , install recovery manager and make a backup
and have the ability to change the rom
on my old cell phone ICS , it was root then install CWM for backup's
I don't want to mess anything up assuming things
but from all the reading in the forums and bleeding eyes... it seems there's so many bricked devices... just terrible
did i miss a forum or walkthru on how to NOT brick the tablet
please any help would be great
thank you and take care
ttyl
Cam
Click to expand...
Click to collapse
"...but from all the reading in the forums and bleeding eyes..." for that?! Nah...
1. Unlock: get the apk from asus site (V8) for it. If you run into problems, downgrade to 4.1 and use ver. 7 instead. This is not an unknown issue. Once you're unlocked, it will remain so forever;
2. Recovery: if you stay on 4.2, you can't use CWM. Must install TWRP (2630-4.2 is the latest, I believe). You can use CWM on 4.1, but if you're gonna upgrade anyway, might as well flash TWRP throughout. Choose your recovery carefully: 2.6.3.0 is for 4.1 bootloader (10.4.x.xx); 2.6.3.0-4.2 is for 4.2 bootloader (10.6.x.xx - your current rom). Do it otherwise and you risk bricking your device! That done, you can change roms to your heart's content.
Basically, downgrade to 4.1 if need be, unlock, upgrade to 4.2, flash TWRP, then custom roms. Don't mix roms with incompatible bootloaders though: read the rom threads carefully, Usually, they will warn you at the beginning which bootloader is required for a particular rom. Hint: 4.3 roms definitely need 4.2 bootloader. Have fun.
Note: if you happen to upgrade to 4.2 and like it that way, you can flash Nvflash bootloader (10.6,x) and use CWM 4.2 recovery instead. Credit to Noahvt for pointing that out. A glitch in my case: I could flash, but could not back up. CMW is unreliable, and should be used only as a last resort, as in you don't have a working touchscreen.
Hello Everyone, been a long time lurker in these forums and had a question that I would really like yalls input on.
I have a Verizon Galaxy S 3 and I have it running Paranoid Android 4.6 Beta 5 that has also been encrypted. I am trying to flash a new rom on to my device but have been preceding cautiously since I know the encryption may cause problems. Currently I have teamwin recovery installed and it prompts me for the encryption code before stating, but always says I have the wrong code. If i bypass the code in the recovery, i can view files in my sd card but not off internal storage, so I don't know how this will effect flashing a rom from the sd to write over internal.
So I have a feeling I may have to odin back to stock and reroot, problem is I don't know what version to odin back to. I know that if I flash 4.3 onto the device I will not be able to unlock my bootloader again, and Im not sure if its possible for me to odin back to a previous version of stock without causing a brick.
Please throw in yalls input, I need every opinion I can get.
Is it possible for me to take my phone running on Paranoid Android 4.5 Beta 5 which says android version 4.4.4 and flash a Stock Rom thru odin at version 4.1.2 for example so i can reroot and unlock the bootloader again??
Thanks for your help in advance, and may this community live forever.
I would suggest to Odin back to 4.1.2, as 4.3 and up are locked
Sent from my Nexus 5
Thanks for the reply!
I was thinking going that route too, but needed a second opinion.
Do you think I could flash 4.1.2 over the rom if its running android version 4.4.4 .? I was hesitant to have already done cause I wasnt sure if it would cause a brick or not. I need a better understanding of Odins process of flashing the stock rom.
ajthearmo said:
Thanks for the reply!
I was thinking going that route too, but needed a second opinion.
Do you think I could flash 4.1.2 over the rom if its running android version 4.4.4 .? I was hesitant to have already done cause I wasnt sure if it would cause a brick or not. I need a better understanding of Odins process of flashing the stock rom.
Click to expand...
Click to collapse
As long as your bootloader is unlocked to can yes. But, if your on one of the locked bootloaders do not even attempt to do that
Before you attempt to flash anything what version of Android are you currently on?
Sent from my Nexus 5
That's what I needed to hear. Thank you.
I'm running 4.4.4 , its off a build of paranoid android. I also have unlocked my boot loader before I installed this ROM.