Related
Where can i find the newest version of CWM for Evo Shift so i can use EXT 4 roms etc..
Android Development -> Evervolv
preludedrew is the only dev currently pushing it, AFAIK.
Sent from my HTC Speedy
Also if you don't want to flash to the latest CWM you can simply fast boot to it and keep your existing CWM, im not sure what the pros and cons are for either or. I gather so far some folks ROMS can only be installed via one or the other.
ok thanks.....so thers no real need for cwm 3 on the shift atm????
dmac2415 said:
ok thanks.....so thers no real need for cwm 3 on the shift atm????
Click to expand...
Click to collapse
There is if you ever want to take advantage of ext4, that's not necessarily right now though, is it?
Like the user above stated, you could simply boot into it instead via fastboot. You can probably even get away with flashing the gingerbread roms on 2.x, but when mods start coming into play, you'll need to use 3.x for the script support.
Sent from my Speedy Shift.
Hopefully the wiki is kept up to date on all the options. http://forum.xda-developers.com/wiki/index.php?title=HTC_Speedy
cwm2.5 is currently the best option untill there is a fully working and compiled cwm3. once there is an official, 3 will be the way to go. most developers have been using the rom flashing scripts(called edify scripts) that can be used in both cwm3 and 2.5. id say just hold out till an official comes out unless your rom develeper specifically tell you to.
OK I have spent about 2 weeks now looking through roms, kernels, root methods etc etc.
I have come to one conclusion. IT SUCKS owning a Verizon tab on this forum.
Most of the guides are accurate, but often miss one little detail that anyone who knows this stuff would think "duh" about, but a noob will miss, and end up reflashing stock from heimdall 10 times over because of.
Long story short, I would like to see a Verizon guide here on the development section that is kept up to date and has proper links to working roms as well as IDIOT PROOF walk throughs.
I would be willing to do this, or someone else can, I do not care. I will edit this very post so that it can serve said purpose if it gets made a sticky, or added to a sticky thread.
In this spirit I will later edit this post but I have a few questions/requests first.
1. I have never had the need to host files for large numbers. I use my own server to host things, but I know I cannot do that for this. Can someone PM me with what would be the best method to host files for people (IE It seems one service somewhere will add links through direct downloads, Megaupdload, Rapidshare etc at the same time).
2. Correct me if I am wrong. Heimdall seems to be the best root method. Heimdall + the ec02 files = the most stable and fully robust and stable rom for the VSTG (Verizon SGT).
3. The Verizon SGT Bootstrapper will convert to Ext4 and add CWM, but results in a broken camera and rotation, the latter of which I have a fix for, but not the camera. Dos any other way of adding CWM work better?
4. Sprint has a completely working update to GB, that works on the VSGT as well, minus radio function. I read somewhere what steps had to be taken to get the 3g radio working as well, but have since not been able to find it. If someone who reads this knows, could you please post or PM me where to begin fixing the radio on the sprint rom to work with the VSGT?
Morkai Almandragon said:
3. The Verizon SGT Bootstrapper will convert to Ext4 and add CWM, but results in a broken camera and rotation, the latter of which I have a fix for, but not the camera.
Click to expand...
Click to collapse
Please tell me how you fixed the rotation? I can deal with no camera, the one in my phone is better anyway.
I am not the greatest help in the world....but have a VSGT and will help where i can.
Sent from my SCH-I510 using XDA Premium App
mnpolock said:
I am not the greatest help in the world....but have a VSGT and will help where i can.
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=14954414&postcount=8
There is the thread that will fix the rotation bug... Now if I can get the camera working... LoL
Oditius said:
http://forum.xda-developers.com/showpost.php?p=14954414&postcount=8
There is the thread that will fix the rotation bug... Now if I can get the camera working... LoL
Click to expand...
Click to collapse
Do not run a kernel that requires Ext4 and both work perfectly.
IE use Heimdall and install the ec02 firmware, then stop. Everything seems to work, without any fix required.
Morkai Almandragon said:
Do not run a kernel that requires Ext4 and both work perfectly.
IE use Heimdall and install the ec02 firmware, then stop. Everything seems to work, without any fix required.
Click to expand...
Click to collapse
Man, I wish I spoke french... Because that is what the above looks like to me. My camera doesn't work, and I didn't do anything but root it, and install that Verizon Bootstrapper. Well at least the rotation works, still don't know what to do about the camera.
I used the verizon bootstrapper after restoring to completely stock ec02 and rooting with super one click. Then used heimdall to flash psirens kernel and then flash psirens rc 2.5. From here http://forum.xda-developers.com/showthread.php?t=1147277&highlight=vzw
and my camera and rotation work great after replacing the sensors.so file to fix rotation. Currently I am overclocked to 1.4ghz with voltage control and all is running flawlessly and fast.
ticklemegavin said:
I used the verizon bootstrapper after restoring to completely stock ec02 and rooting with super one click. Then used heimdall to flash psirens kernel and then flash psirens rc 2.5. From here http://forum.xda-developers.com/showthread.php?t=1147277&highlight=vzw
and my camera and rotation work great after replacing the sensors.so file to fix rotation. Currently I am overclocked to 1.4ghz with voltage control and all is running flawlessly and fast.
Click to expand...
Click to collapse
How exactly did you install the kernel and rom? can you post a step by step
?
Morkai Almandragon said:
How exactly did you install the kernel and rom? can you post a step by step
?
Click to expand...
Click to collapse
Step by step and with links on everything that you need. Written so easy to understand so a person with no experience can knock it off with no problem.
Me, I'm on a stock but rooted VSGT, and I'm fine with it really. Only thing I do wish for is a 2.3 update from VZW. I don't care about OC'ing, Tab is very snappy enough for me and battery life is very good.
I looked into flashing the Sprint update but thought against it because I need 3g.
Recently got a Nexus S4G and running MIUI on it, and boy, I wish we could get a MIUI port on our tab. Those guys are just dang good and crazy.
Sent from my SCH-I800 using Tapatalk
Ok here is what I did.
1. Get the stock un-rooted un-updated firmware from here http://forum.xda-developers.com/showthread.php?t=1136587&highlight=verizon
2. Follow this guide to flash the files you got in step 1 http://forum.xda-developers.com/showthread.php?t=967175&highlight=verizon+stock+firmware
3. After you have flashed back to stock and booted up into android then update through android to ec02.
4. Download super one click from here http://forum.xda-developers.com/showthread.php?t=803682 and follow the instructions on that page.
5. You now should be rooted. Now download the verizon bootstrapper off the market and run it.
6. After that has completed download the rom/kernal and follow the instructions on this page http://forum.xda-developers.com/showthread.php?t=1147277&highlight=vzw.
7. Alright now you should be rooted with a custom kernal and rom installed your camera should work. If your rotation doesn't work then get the sensors.default.so from here http://forum.xda-developers.com/showpost.php?p=14954414&postcount=8 and follow the guide.
That's exactly what I did and my camera/rotation work fine.
If you want to overclock use voltage control from the market.
So, I have to go back to square one, where I started. and do everything all over again?
The use SOC to root it.
Then run the program that knocked out my camera/rotation again.
So I will be right back where I am now.
Then I have to update the kernel.
Then install a new rom.
And it should work.
OK, thanks...
Never mind, if I go back to square one, I will just stop and not go any farther. My GT was fast enough without doing all that. So I will wait, maybe someone will come up with a fix for the camera that was as easy to fix as the rotation. I don't video chat and my Mesmerize has a better camera and easier to use.
Yes that is what i did after trying to flash a voodoo kernel and getting stuck at the Samsung logo many times. I flashed back to stock and started over. Not sure when the camera started working in the process, I had checked after everything was installed. Also im not sure if psirens rom even flashed or not because everything looked exactly the same and still had the Verizon bloatware installed which I just removed with titanium backup. Im not sure if i have ext4 or not would there be a way to check?
The thing is I never flashed the voodoo kernel. I rooted the GT last week. Yesterday I was reading around, obviously not as well or completely as I should have. But I was going to flash a new rom and it stated I had to do the Bootstrapped first. So I downloaded it and that was when all heck broke loose. I read later on in the thread that the camera stopped working and so did the rotation. Well the rotation had a fix, but the camera doesn't. Oh well, I will keep looking, maybe if I just start at #6 because that is where I stopped.
ok What I am finding is this. Flashing the EC02 files through Heimdall result in a rooted Froyo rom that runs stable and decent, but without CWM.
You can then use the Verizon Bootstrapper on the market which flashes a new kernel that includes CWM. The new kernel breaks the camera and rotation though. Flash the better than life kernel and camera is fixed, followed by the rotation fix and you are now back to close to stock with root, and CWM...
Here is where I lose my way though. The Psirens rom looks JUST like the EC02 Heimdall install I have. I will post the files I am using once I get a host I am happy with.
Morkai Almandragon said:
ok What I am finding is this. Flashing the EC02 files through Heimdall result in a rooted Froyo rom that runs stable and decent, but without CWM.
You can then use the Verizon Bootstrapper on the market which flashes a new kernel that includes CWM. The new kernel breaks the camera and rotation though. Flash the better than life kernel and camera is fixed, followed by the rotation fix and you are now back to close to stock with root, and CWM...
Here is where I lose my way though. The Psirens rom looks JUST like the EC02 Heimdall install I have. I will post the files I am using once I get a host I am happy with.
Click to expand...
Click to collapse
This is exactly what I think except that the ec02 files I linked will take you back to full unrooted stock where as the files from the tutorial for flashing ec02 I linked will leave it rooted but with stock ec02. I also cannot tell a difference between stock ec02 and psirens ec02 they look exactly the same. I almost wonder if cwm is not flashing the rom correctly. But even if it didn't you get a stable ec02 experience with a overclockable kernel which is all I was really looking for in the first place. I also could not get the voodoo kernal to work period I flashed it several times and always got stuck at the samsung screen on boot. My tab is much faster now and im pretty happy with it. Now if we could just get a stable gingerbread or maybe even honeycomb ill be all over that.
http://forum.xda-developers.com/showthread.php?t=1178414
Just saw this after my last post, looks like we will have gingerbread with working 3g (which I require) very soon. So we should be seeing some performance improvements whenever we get gingerbread.
If you guys want a stock ROM, converted to ext4, just ODIN Boushh's kernel then (if you're on the newest VZW update EC02) replace the file in that thread that fixes auto rotation.
Coolsaber57 said:
If you guys want a stock ROM, converted to ext4, just ODIN Boushh's kernel then (if you're on the newest VZW update EC02) replace the file in that thread that fixes auto rotation.
Click to expand...
Click to collapse
Boushh's kernel will not work for me I always get stuck at the samsung boot screen. Im flashing with heimdall though because I only use linux and i do not think there is a version of odin for linux.
Good evening all,
Basically I'm looking to root my girlfriends fathers U8800, it's currently running android 2.2. He's complained that its got major battery drain so I figure I can find a ROM here that can help that.
I've read there are 3 different types of models for this handset. How do I know which one we've got? If that's relevant?
I've found this thread that seems dead easy to follow, http://forum.xda-developers.com/showthread.php?t=1420728 , am I ok to proceed?
When I've rooted it, do I just flash a rom via CWM like I would with my galaxy s? And will I be caught out with bootloader issues or little things like that?
Thanks in advance.
If the device is the U8800 regular model(not pro or plus) you can follow the guides of the link.
And yes, you can flash a rom from cwm recovery.
Only one suggestion. If you flash the latest stock gingerbread rom(I think is the 522), search for a thread called "get your pink screen back" on developing section. The after 518 versions have the bootloader locked, and on the above thread you will find how to flash the unlocked bootloader from 518 stock rom.
Thanks for that, I'll get on it tomorrow with an operational head. I'll do the pre root checks and make sure I have everything I need in place before I get going.
dancer_69 said:
If you flash the latest stock gingerbread rom(I think is the 522)
Click to expand...
Click to collapse
It's 528
dancer_69 said:
The after 518 versions have the bootloader locked, and on the above thread you will find how to flash the unlocked bootloader from 518 stock rom.
Click to expand...
Click to collapse
*locked pink screen.
Sent from my GT-P1000 using Tapatalk 2
If the device is not yours I suggest you to do nothing. There's no better Rom, in terms of bug free than the original one.
Custom roms always have this or that and will require attention, which I'm sure your fatherin law can live better without these issues and concerns.
This devices have an high consumption and he has to get used to it.
Now if the device was yours meaning you would be using it daily, than i would advise you to install aurora. I don't like it but have to admit that is very good and stable.
:thumbup:
Sent from Odin's device!
Dave759 said:
He's complained that its got major battery drain so I figure I can find a ROM here that can help that.
Click to expand...
Click to collapse
Did you look to see what is causing the battery drain? I have a friend with a stock GT540 that had serious battery drain. Turns out it was the GoSMS program. Deleted the app and now his phone lasts 5 days between charges. Switching a rom won't help if the problem is an app.
1) Get cpu spy and see if it is going to deep sleep
2) If not sleeping, turn off running applications one by one and test via cpu spy to find out which one is causing it not to sleep.
3) Either remove the offending app or use Autorun Manager to modify the receivers (if rooted)
You can fix his problem without changing his rom. If he wants root, superoneclick can root 2.2, I just used it the other day. Also make sure he is on the latest 2.2: b138sp04 or b163. I prefer b163, even though it is the China rom, because I like the Huawei launcher better that stock.
A.C.A.B. said:
If the device is not yours I suggest you to do nothing. There's no better Rom, in terms of bug free than the original one.
Custom roms always have this or that and will require attention, which I'm sure your fatherin law can live better without these issues and concerns.
This devices have an high consumption and he has to get used to it.
Now if the device was yours meaning you would be using it daily, than i would advise you to install aurora. I don't like it but have to admit that is very good and stable.
:thumbup:
Sent from Odin's device!
Click to expand...
Click to collapse
That's not true... official 2.2 is the slowest thing in existence. If he just needs stability then Ezets CM7 is the answer. There are no bugs with it (except wifi tethering) and it's much much faster than stock...
Also he can undervoltage it to preserve battery life more than stock ROM.
Sent from my U8800
You want the best 2.2 you try Void Eridanus. Everything works.
Want the speed, OEX rom it's a Ferrari. Everything works less the mms with data off.
You can also keep the stock Rom, root it and just apply a ffranco kernel. This way you gain the speed.
3 good solutions here.
I'm don't revert to stock Rom for 2 reasons, cam quality and battery life, otherwise i would use stock Rom without a shadow of a doubt.
In terms of stability and all working it's stock 2.2 Rom and this is unquestionable!!!
I have been trying ALL roms and ALL respective versions since July 2011 therefore I do speak by personal extended experience
I repeat once again, in the conditions you mention leave the phone as it is. If you want to do something just root it and that's it.
as a matter of facts i had my phone with so many rooms that i can even say how many but if u want stability i recomend oxygen... if u want stability and good looks use miui 32...
last .32 miui that i used was from miui portugal in english and nothing to say about that...
battery for 2 days and all smoth...
but my phone is weird... he can take almost every rom and be usable...
The issue with miui pt versions it's the cam quality that is horrible. It's just this detail that it's not very good. The rest it's perfect.
Sent from Odin's device!
Hey everyone, back for an update and some other steps. basically, he got frustrated with how the battery so he went out today and bought the newer huawei. Reading eveyones comments here i think its due to the ammount of apps and being on froyo hasn't helped any thing, but anyways its now my new toy to play with. So far, followed the link i posted in the first thread, rooted and installed the latest CWM (v5). I'm now a little confused when it comes to the get the pink screen back, should i follow this thread http://forum.xda-developers.com/showthread.php?t=1457490 now before flashing a new rom or afterwards?
Again thanks for all the help, I'm almost done bothering you all for now
Edit: Reading on some ROM's and the comments above, i should install B518 stock ROM then flash the bootloader fix from the thread posted above then i can install other ROM's? If so where can i get the stock B518 ROM and how do i know which version I'm using? Sorry and thanks again.
First, which rom you have now?
You can find the version from settings -> about phone.
If you have a newer than 518 version you need to change the bootloader with the one from 518. If you have 518 you don't.
Also check which version of kernel you have(is on about phone also)
If you have a 2.6.32 version(which mean that you have froyo rom), you can flash only roms with this kernel version. If you have a 2.6.35 version, you can flash roms with 2.6.35 kernel or 3.0.8(as aurora ICS).
Basically its a stock froyo rom, im looking to get to gingerbread by the end of tonight but currently im stuck on the huawei splash screen after i did a data reset in CWM. Can still get to CWM though.
What rom you want to flash now?
A custom gingerbread based of froyo's kernel 2.6.32 like CM7.2, oxygen or miui, or the official gingerbread?
Im not particularly bothered, something that won't brick the phone and is stable. I'm more worried as to why it wont boot now after a data reset.. any suggestions for that?
You can use adb and logcat function to see where the problem is. Usually when some errors prevent device to complete the boot proccess, this piece of code loops. You need to have some knowledge of programming though, but maybe is something easy.
and now i have blue screen.. what can i do? or have i bricked it?
Where you have blue screen and what you did?
Usually blue screen instead of recovery mode, means that the recovery.img is deleted from .cust_backup/Image folder
basically, i formatted something, reboot and soon as the huawei logo appear a blue scrren rolls down. when i plug the phone into the pc it detects a folder but its empty, the phone is detected as qualcomm now..
Yes, seems that you formated the partition which has the Image folder with all system images. So, now you need to flash an official rom. You can either flash a froyo or a gingerbread rom. You can avoid this only if you previous had take a backup of this folder. In this case just put all files in (empty now) image folder.
I have sold my last Vibrant and moved onto other devices. Since I find myself reposting links and instructions, I will just go ahead and leave these links that other might find useful, especially those who plan to start rooting and flashing the Vibrant for the first time.
(Technically these links can be easily found using the search function and/or Google, but sometimes searching does not prevail.)
Remember you make these modifications to your phone at your own risk so make back up of you data. If you flash any ClockworkMod (CWM) packages, make sure you create a Nandroid backup just in case anything goes wrong. You can use ODIN images to restore your phone to stock.
BOOTLOADERS: Froyo and Gingerbread [adyscorpuis]
DRIVERS: Samsung USB Driver
DRIVERS: Vibrant's manual, drivers, Kies mini
FIX: GPS patch (CWM) [Mogranja] (for Jelly Bean ONLY, make Nandroid backup)
GUIDE: XDA's Vibrant WIKI
GUIDE: Rooting and using Odin [s15274n] (this is a sticky thread if you missed it)
GUIDE: Video Instruction to Upgrade from Stock to Jelly Bean [eddie1west]
GUIDE: GPS hardware fix
GUIDE: Retrieve files from internal storage using ADB commands while in CWM [me]
KERNEL: Stock KB5 [drhonk] (flashable via CWM or ODIN)
KERNEL: Semaphore ICS, Semaphore JellyBean [stratosk] (flashable via CWM or ODIN) (CWM included in kernel)
KERNEL (app): Semaphore Manager
MODEM / BASEBAND: KB5 modem (latest for Vibrant, flashable via CWM 2 or 3 only)
ODIN program
ODIN: Stock JFD
ODIN: JFD, KB5 and Eugene (rooted)
RECOVERY: ClockworkMod installer [untermensch]
ROM: CyanogenMod
ROM: CM10 Euroskank
ROM: AOKP
ROM (patch): Jelly Bean 4.2 Google apps [Euroskank]
ROOT: Via update.zip [justadude] (for Eclair 2.1 only, flash using CWM)
ROOT: Via SuperOneClick [CLShortFuse] (false positive by antivirus)
SIM UNLOCK: SGS Unlock PRO (Note: I am not advertising, this app works for me, that is all.)
Another "old dog" making an exit. Sad to see you go but I know you'll be popping in from time to time. Your support with the "inexperienced" and the "noobs" has been great!
Thanks buddy.
???
I installed the GPS hardware fix and my 2.2 stock can't start the gps ._. didn't realize it's for JB
kgptzac said:
I installed the GPS hardware fix and my 2.2 stock can't start the gps ._. didn't realize it's for JB
Click to expand...
Click to collapse
If you mail it to me, i'll fix it for a small payment of 89.99
***LIMITED OFFER***
If it's flashed via CWM it's not really a *hardware* fix, now is it?
FaultException said:
If it's flashed via CWM it's not really a *hardware* fix, now is it?
Click to expand...
Click to collapse
I put it together quick, mixed it up it with the hardware fix guide.
What surprised me is after performing the fixes and patching, the Vibrant gets better GPS signal than my Galaxy Nexus and the Xperia Play which has GLONASS support.
Back to watching Austin grand prix coverage....
Great post,what are U aiming at(for device)since vibrant is coming to me?
Sent from my HTC Sensation 4G using Tapatalk 2
I was going to get the Nexus 4, but I bought a Galaxy Nexus for $200 instead. I am reading on the Nexus 4 feedbacks to see any issues, it probably was the right thing to not get it right away, there seems to be build issues with the glass, breaking due to pressure while in pockets, similar to the S3. Also there are proprietary drivers especially by Qualcomm, I guess without them custom roms won't get the best performance, so I'll see about that also.
The Galaxy Nexus is so fast once you customize it anyway, so its good enough for now. I feel like I'm spoiled on small screen size, it felt strange going back to these giant screens.
First of all, I like to share I am not a stranger with rooting, flashing, granting bootloader access (not an tablets, but on HTC an SE WM phones in the past (assuming the S-off/S-on switching is somewhat comparable)). Despite not being a stranger, I am no whizzkid either, it's just that I am able to read instructions well, re-read them and carefully follow the instructions step by step. During the process I have reasonable understanding of what I am doing, but I am not someone that could have 'invented' such workflows and adjustments myself.
So, what is new for me? Installing a custom recovery. I haven't done that before. No problem, because I know there are enough techs on XDA that have the great quality to share their knowledge, something I appreciate very much and use regularly.
My story:
Asus created a situation in which you have to register your device and actively decline your warranty, whenever you want to unlock the bootloader. This is why I didn't do that yet. Now, having my TF300 for almost 6 months, reasonably comfortable with the feeling there will be no issues to need the warranty, I am willing to unlock my bootloader and void my warranty. However, shortly after the JB OTA I read a lot of messages that this was not possible with a TF300 on JB. Later I read it might be possible, but that changing the bootloader was not possible. Then I read this was possible too, but you could only install roms based on official Asus JB OTA.
Well... I guess things have evolved since the initial JB OTA, but I am not sure that I understood things well enough to just give it a try (yet). So I am looking for confirmation and a bit more in depth info. First I will summarize my TF300's history in detail and things I found so far regarding custom recovery. In this way you know what the situation is and I also hope this post becomes 'informative' for other TF300 owners too, besides being a question topic for me only.
Ok, what do I have:
- An original TF300T (no dock), bought in June 2012 with stock ICS
- Granted myself root access via 1-Click Transformer Root
- All original Asus OTA's applied, including the upgrade to JB (and succeeding OTA's)
- Still have root (kept root during all OTA's, including upgrade to JB with help from Voodoo OTA rootkeeper)
- Recently wiped/factory reset my device (still have root)
What I used in the past, but currently not running on the tablet:
- Used different Custom build.props on ICS and JB, but now have stock build.prop again
- Used SwitchMe profile manager (still want it, but waiting on decision to possibly unlock/install custom recovery first)
- Used browser2ram (don't want to need it anymore, but ability to boost performance with a custom rom will be a requirement)
What custom recovery options did I see? There are 3 of them and all seem to be safe with the TF300 JB OTA:
- TWRP 2.3.1.0
- CWM 6.0.1.3 / 5.5.0.4 (don't know why it has 2 version numbers... ICS and JB version?)
- Clockworkmod 6.0.1.4 Touch (same as CWM 6.0.1.3 but with touch functionality?)
Ok, what do I want confirmed to be sure enough to give it a shot on my TF300 without bricking?
- Is it possible to use official Asus unlock tool on a stock OTA JB TF300? If possible:
- Are above mentioned custom recovery options indeed safe to run on a (unlocked) stock OTA JB TF300? If safe:
- What is (technical) the best custom recovery option? Or are the mentioned options mostly identical and is it a matter of personal preference?
- Can I run any roms after installing a custom recovery or am I restricted to roms based on official Asus JB?
- What will happen with root access after (if possible) installing a custom recovery? And after installing a custom rom?
These are my major 'need to knows' before I dare....
Besides this information, I am curious if someone can confirm my representation of (or explain) the different parts in Android/Asus installation and how it is affected by a custom recovery. During reading along the forums, I have created this visualization of the different parts of the system:
1. Bootloader or kernel (first thing on system, somewhat comparable with a PC BIOS? Are the terms bootloader and kernel interchangeable?)
2. Asus recovery/boot options or custom recovery (custom recovery replace the standard Asus recovery/boot options, I assume)
3. Android (stock JB/ICS or custom rom)
Is this a correct representation?
Well, that was all... Hopefully my post didn't become a TLDR and some of you are willing to help me out. I am very thankful in advance!
1. Bootloader is something else then a kernel. You just have to have the right kernel for the 2 different bootloader
2. Boot options are in the bootloader. Stock Recovery has no options.
3. dont understand your question
1st if you are still on ICS I would recommend to use NVflash and create the needed NVflash files. After that your tablet is nearly unbrickable and you are able to NVflash back to the ICS bootloader (my opinion not so importent anymore, caus even CM is now compatible with the JB Bootloader)
2nd If you are still on ICS I would use the unlock app on ICS not on JB and would then flash the JB update.
The Custom Recovery is best right now would be TWRP 2.2. Its the only one with no known issues.
Hope that helps a little and hope that my explanations are correct, because I am just a flasher like you
Last but not least. The best ROMs out there in my opinion are the Clean Rom 2.5 for the TF700 with clemsyns Kernel and BlueAndroid V.1.0.
Thank you for your reply, it helps me a bit. Unfortunately it doesn't answer my major questions, but I don't blame you (not at all). Every bit of help is welcome.
mikaole said:
1. Bootloader is something else then a kernel. You just have to have the right kernel for the 2 different bootloader
Click to expand...
Click to collapse
Ok... clear... but then.. what is a kernel...? (*feeling noob*)
mikaole said:
2. Boot options are in the bootloader. Stock Recovery has no options.
Click to expand...
Click to collapse
Ok, so what happens if I install a custom recovery? Does it replace the bootloader with a different one that includes recovery options? Or does it add recovery options to the existing bootloader?
mikaole said:
3. dont understand your question
Click to expand...
Click to collapse
The numbers (1, 2 and 3) were the 'layers' I imagined on how Android is build up from boot to OS, where 3 being the final layer (Android OS presented to the user on screen).
mikaole said:
1st if you are still on ICS I would recommend to use NVflash and create the needed NVflash files. After that your tablet is nearly unbrickable and you are able to NVflash back to the ICS bootloader (my opinion not so importent anymore, caus even CM is now compatible with the JB Bootloader)
2nd If you are still on ICS I would use the unlock app on ICS not on JB and would then flash the JB update.
Click to expand...
Click to collapse
That's the point why I started this topic, I am on (stock OTA) JB already. If I was still on ICS, I would have had the guts to unlock and install custom recovery. I am hesitating because I read about issues with JB and unlocking/installing custom recovery.
mikaole said:
The Custom Recovery is best right now would be TWRP 2.2. Its the only one with no known issues.
Click to expand...
Click to collapse
Thanks for the tip, I will keep this in mind.
mikaole said:
Hope that helps a little and hope that my explanations are correct, because I am just a flasher like you
Click to expand...
Click to collapse
*shakes hands* Yes, it helped a bit.
mikaole said:
Last but not least. The best ROMs out there in my opinion are the Clean Rom 2.5 for the TF700 with clemsyns Kernel and BlueAndroid V.1.0.
Click to expand...
Click to collapse
Thank you, I will consider this when I am ready to search for custom roms.
@all: Is there someone out there that can (and is willing to) answer my 'major' questions? I will re-post them below:
Ok, what do I want confirmed to be sure enough to give it a shot on my TF300 without bricking?
- Is it possible to use official Asus unlock tool on a stock OTA JB TF300? If possible:
- Are above mentioned custom recovery options indeed safe to run on a (unlocked) stock OTA JB TF300? If safe:
- What is (technical) the best custom recovery option? Or are the mentioned options mostly identical and is it a matter of personal preference?
- Can I run any roms after installing a custom recovery or am I restricted to roms based on official Asus JB?
- What will happen with root access after (if possible) installing a custom recovery? And after installing a custom rom?
Ok, what do I want confirmed to be sure enough to give it a shot on my TF300 without bricking?
- Is it possible to use official Asus unlock tool on a stock OTA JB TF300? If possible:
- Are above mentioned custom recovery options indeed safe to run on a (unlocked) stock OTA JB TF300? If safe:
- What is (technical) the best custom recovery option? Or are the mentioned options mostly identical and is it a matter of personal preference?
- Can I run any roms after installing a custom recovery or am I restricted to roms based on official Asus JB?
- What will happen with root access after (if possible) installing a custom recovery? And after installing a custom rom?
Yes the unlock tool works on JB as well as ICS. I used it while on JB.
Recovery choose one for JB since you have said you were on JB. In fact that is how you will determine which roms you can use as well (JB).
There have been many complaints posted about problems with CWM on this device.
Safe is something I can't answer - twrp itself appears to be safe but that is relative.
One mistake can usually be overcome (or one weird issue); add a mistake to that and you are out at two strikes with this unit most of the time. That is the way I see it after reading hundreds of posts.
You must have recovery, adb, or fastboot working to recover from a problem with this unit.
Before you make any changes make sure adb and fastboot work.
When you flash a rom make sure early in the game you turn on usb debugging in developer options. Learn to get into and use the bootloader menu for adb, fastboot, and recovery access. This would be with both stock recovery and twrp.
Custom roms are usually by default rooted. With a custom recovery you can flash root at will.
It is long but I feel I touched on each of your questions, if not ask.
If your phone is a ferrari, the kernel is the "driver" ... the kernel you use can be tweaked to allow you to overclock your process. By default, overclocking is not possible (usually) on stock kernels because phone makers don't want you effing up your phone.
Other kernels can let you run "low voltage" or "ultra low voltage" settings for the processor. This allows you to send less power to the processor but still get the same amount of oomph out. The result is greater battery life, and no cost to performance. Obviously this can be dangerous to some hardware... so be careful and know what you're doing. It can be as bad as damaging hardware, or as minor as getting your phone stuck in a boot loop. DO A BACKUP with Rom Manager before installing a kernel. Always do a backup before you do anything to your phone.
moisaal said:
If your phone is a ferrari, the kernel is the "driver" ... the kernel you use can be tweaked to allow you to overclock your process. By default, overclocking is not possible (usually) on stock kernels because phone makers don't want you effing up your phone.
Other kernels can let you run "low voltage" or "ultra low voltage" settings for the processor. This allows you to send less power to the processor but still get the same amount of oomph out. The result is greater battery life, and no cost to performance. Obviously this can be dangerous to some hardware... so be careful and know what you're doing. It can be as bad as damaging hardware, or as minor as getting your phone stuck in a boot loop. DO A BACKUP with Rom Manager before installing a kernel. Always do a backup before you do anything to your phone.
Click to expand...
Click to collapse
+1
tobdaryl said:
Ok, what do I want confirmed to be sure enough to give it a shot on my TF300 without bricking?
- Is it possible to use official Asus unlock tool on a stock OTA JB TF300? If possible:
- Are above mentioned custom recovery options indeed safe to run on a (unlocked) stock OTA JB TF300? If safe:
- What is (technical) the best custom recovery option? Or are the mentioned options mostly identical and is it a matter of personal preference?
- Can I run any roms after installing a custom recovery or am I restricted to roms based on official Asus JB?
- What will happen with root access after (if possible) installing a custom recovery? And after installing a custom rom?
Yes the unlock tool works on JB as well as ICS. I used it while on JB.
Recovery choose one for JB since you have said you were on JB. In fact that is how you will determine which roms you can use as well (JB).
There have been many complaints posted about problems with CWM on this device.
Safe is something I can't answer - twrp itself appears to be safe but that is relative.
One mistake can usually be overcome (or one weird issue); add a mistake to that and you are out at two strikes with this unit most of the time. That is the way I see it after reading hundreds of posts.
You must have recovery, adb, or fastboot working to recover from a problem with this unit.
Before you make any changes make sure adb and fastboot work.
When you flash a rom make sure early in the game you turn on usb debugging in developer options. Learn to get into and use the bootloader menu for adb, fastboot, and recovery access. This would be with both stock recovery and twrp.
Custom roms are usually by default rooted. With a custom recovery you can flash root at will.
It is long but I feel I touched on each of your questions, if not ask.
Click to expand...
Click to collapse
Thank you for this clear answer. Allow me to summarize your answer (actually it is a confirmation request to see if I fully understand your answer):
- Asus unlock tool is working fine on JB, no problems
- Since my TF300 is on JB and to stay on the safe side (no guaranties) your advice is to use TWRP 2.3.1.0 for JB (to use the JB version is obvious for me, thanks for confirming)
- Once these steps are done (unlock and custom recovery) , I can flash roms at will, but have to keep in mind to use JB-based roms
Did I summarize (and thus understand) your answer correct?
Thanks for pointing out to have adb and fastboot working before making changes and to learn to get into and use bootloader menu for adb, fastboot and recovery access (with both stock recovery and twrp). I am very much aware of this, but it is always wise to make that clear to anyone whom wants to play with this stuff.
You helped me very much! To be complete sure, I'll wait for confirmation, but then I have more than enough confidence to give it a go (Yes, I will beware it won't exaggerate into over-confidence and I become sloppy . I'll stay punctual and cautious during the process.).
moisaal said:
If your phone is a ferrari, the kernel is the "driver" ... the kernel you use can be tweaked to allow you to overclock your process. By default, overclocking is not possible (usually) on stock kernels because phone makers don't want you effing up your phone.
Click to expand...
Click to collapse
Can I see the kernel somewhat equal to the bios on a pc, or is that a misinterpretation?
If I understood it correct, then it is not fully comparable to a pc bios, as on Android the kernel also determines which version of Android is able to run on your device (ICS needs another kernel than JB), right?
ralph075 said:
Can I see the kernel somewhat equal to the bios on a pc, or is that a misinterpretation?
Click to expand...
Click to collapse
BIOS (basic input-output system, or something along those lines) is loaded before the kernel! They are different. The kernel acts as a mediator between hardware and software.
Trimis de pe Motorola Defy
vap_66 said:
BIOS (basic input-output system, or something along those lines) is loaded before the kernel! They are different. The kernel acts as a mediator between hardware and software.
Click to expand...
Click to collapse
Thanks for clarifying. I found this article and read it to learn more... (I had a few questions again, but realized that there probably would be something to read in here that could answer those questions too... )
Did I summarize (and thus understand) your answer correct?
Yes that is correct.
tobdaryl said:
Did I summarize (and thus understand) your answer correct?
Yes that is correct.
Click to expand...
Click to collapse
Thanks again, now the challenge is to find some spare time this weekend
ralph075 said:
Thanks again, now the challenge is to find some spare time this weekend
Click to expand...
Click to collapse
Good Luck!
Go slow and enjoy your new tab.
tobdaryl said:
Good Luck!
Go slow and enjoy your new tab.
Click to expand...
Click to collapse
Thank you. Well, slow it will go, as last weekend didn't have any spare time...
Hopefully I will experience my new tab soon...
ralph075 said:
Thank you. Well, slow it will go, as last weekend didn't have any spare time...
Hopefully I will experience my new tab soon...
Click to expand...
Click to collapse
You're very welcome.
Yes, it seems time to play is sporadic and limited.
Life would probably be very boring if we always had time.