AOSP / JB features / mods in ICS - RAZR i General

Hi guys,
so I'm currently switching from my Defy to the Razr I.
I already browsed the forum but still have some questions.
As I am used to have all the great CM features on my Defy, I'd like to have as much modification for my Razr I as possible.
But of course I'm well aware that the dev is not that big for the Razr I...
1st of all, I do NOT want to unlock my BL for warranty issues (I mean, who would like to unlock a brand new phone and void the 2year warranty?)
So I'm planning on staying on ICS but I'd like to get as much AOSP / JB features as possible on my phone (rooted with the motofail2go)
I was thinking that instead of flashing the zips in CWM I'd just replace the system apks with a root explorer manually...
So is there any chance, I can implement features from the [KERNEL][ROM][MOD]infiniROM to ICS?
What I'd really like to have:
2G setting, flashplayer, brightness settings, better batter life, and any way that brings back a power bar or whatever it is called to have settings like brightness, wifi AP on/off, GPS on/off;flashlight in the notification bar

As Razr i has unlockable bootloader, there is nobody who had played with second init like with defy (I had defy before razr i too) as there wasn't a reason to.
As you may know, there is official update to JB, which at least for me meant much better battery life than I had on ICS and this gets even better on Omar's ROM.
See this thread, there is link for root tool for locked bootloader but that works on ICS only. With root you should be able at least to change brightness and some other thinghs. For power bar search "power toggle" on the play store.
To be honest I was a little worried to unlock my bootloader too but after couple of days when I was sure the phone works well I took the risk as many other users here. And if you'll lock bootloader again there is possibility that shop where you bought your phone won't even dig if you unlocked it or not and you might be just fine with possible warranty claim.

thanks for the reply, I am however not going to unlock the BL.
So what is possible with ICS besides power toggle?
Can I install the AIO kernel on my ICS?

dagoban said:
thanks for the reply, I am however not going to unlock the BL.
So what is possible with ICS besides power toggle?
Can I install the AIO kernel on my ICS?
Click to expand...
Click to collapse
Sorry, but if you want a new kernel, or the roms here, i recommend you 100% unlock the booloader to avoid bricks, without that, you will have to not prove things without freedom of bricks
Intel device - Razr i Owner
Hit thanks if i help you or you like my style

OK, seems like nobody has tried flashing the kernel with a locked BL...
But what about the systemui.apk? Can I just replace that with the one from the mod? That should work, right?

Why should one flash a wrong Kernel or SystemUI?
Deal with ICS, stay on JB stock or try yourself if you want to see bootloops. Good luck...

Well I thought before I get bootloops I would just ask here if someone tried that out before?
Nothing wrong with that I think...

And it could be possible to flash a different kernel than the rom.
On my Defy I have a froyo Kernel with GB, and froyo Kernel with JB...

dagoban said:
And it could be possible to flash a different kernel than the rom.
On my Defy I have a froyo Kernel with GB, and froyo Kernel with JB...
Click to expand...
Click to collapse
Yes, that's right but all kernels used in defy are signed by motorola otherwise it won't be possible to use them since bootloader is not unlockable. Plus due to x86 architecture it'd be complicated try to port jb or newer (in future) to work on ics as everything would have to be done from sctrach - no point do that.
I just hope we won't see new topic "help, I bricked my phone" created by you...

dara85 said:
I just hope we won't see new topic "help, I bricked my phone" created by you...
Click to expand...
Click to collapse
lol, me neither
So, no different kernel, but what about the systemui.apk? I mean, I can copy any modded google app to my phone, so does that mean I can also use the modded systemui?

Man, sorry for sounding rude (truth is sometimes uncomfortable), but as SystemUI is dependent on the framework (of either ICS or JB), there's no chance to switch between them.
You don't want to unlock? So there are two options: Stay at ICS rooted or JB stock unrooted.
The more you ask, the less you get another or better truth.
If you don't believe, try it. Why not? The chance for curing a boot loop with ADB enabled in developer options is 99% (if you are fit with command line) - otherwise you flash ICS stock with RSDlite again, then you are 100% safe.
But DO NOT flash a JB kernel over ICS!

shaftenberg said:
Man, sorry for sounding rude (truth is sometimes uncomfortable), but as SystemUI is dependent on the framework (of either ICS or JB), there's no chance to switch between them.
Click to expand...
Click to collapse
OK, didn't know that the systemUI is part of the framework, I thought its a regular apk like any other apk, like the clock or regular gapps...

Related

[Q] K1 support?

I'm another owner of the K1. I've had it for a while now since xmas and I do like it, but I cant get over the locked bootloader. I was hoping to be able to overclock it so apps for school would run nice and smooth but it doesnt seem to be happening.
Do you guys think I should hold onto it and wait for a root with recovery and hopefully some mods? Or just sell it and try to get a tegra 3?
I'm torn between this man because I have a beefy laptop so I dont need a quad core tablet, I just want it to be smooth. Kernels, overclocking and custom roms always did it for me in prior phones, now its like we're forced to upgrade every year
shoot me some advice
manooti said:
I'm another owner of the K1. I've had it for a while now since xmas and I do like it, but I cant get over the locked bootloader. I was hoping to be able to overclock it so apps for school would run nice and smooth but it doesnt seem to be happening.
Do you guys think I should hold onto it and wait for a root with recovery and hopefully some mods? Or just sell it and try to get a tegra 3?
I'm torn between this man because I have a beefy laptop so I dont need a quad core tablet, I just want it to be smooth. Kernels, overclocking and custom roms always did it for me in prior phones, now its like we're forced to upgrade every year
shoot me some advice
Click to expand...
Click to collapse
It has already been rooted. Once rooted you can OC all you want.
Thanks for the reply. Just wanted to make sure because the K1 doesnt even have its own category in xda.
So, this wont need a kernel to oc?
manooti said:
Thanks for the reply. Just wanted to make sure because the K1 doesnt even have its own category in xda.
So, this wont need a kernel to oc?
Click to expand...
Click to collapse
I do not OC, but have read links saying there are OC tools and all you need is root. So, you'll have to Google it knowing that you can get root and see if that's correct.
TD
timmyDean,
Thanks. Im just hoping to not run into any problems with overclocking it. Ive rooted a lot of phones and overclocked them all.. even overclocked my pc. Since I started I cant stop lol. Its compulsive, i know, but there is a difference in responsiveness so it's not all my my head lol
I'm on A301_13_13_111209_US
Kernel 2.6.36.3
Do you know which method I should run?
Sort of confused in your development thread about using different blobs and updating with OTA.
Yup, http://forum.xda-developers.com/showpost.php?p=21309379&postcount=50
This will flash you directly to 13_13US rooted!
You're the man! I'll be attempting this tonight. Hopefully all goes well.
One question tho, if someone manages to port over cwm, will there be custom roms and so on for this tablet? I saw someone working on porting cwm, but doesnt look too promising.
manooti said:
You're the man! I'll be attempting this tonight. Hopefully all goes well.
One question tho, if someone manages to port over cwm, will there be custom roms and so on for this tablet? I saw someone working on porting cwm, but doesnt look too promising.
Click to expand...
Click to collapse
CWM is already ported. I haven't tried it, but according to the developer it works. I have no reason to use it because there's nothing I want to load. I suspect it's just being used to make backups because I haven't seen any chatter on custom ROMS. As far as custom ROM development, who knows. In my opinion these Lenovo are 'junk'. Again, my opinion. Lenovo doesn't want you to modify their devices, so they make it hard to root. They want you to go to them for a custom ROM. We've tried that and it's a joke. We develop drivers and special drivers for hardware and develop several applications for vertical markets. Chances are, if you have a HC tablet you've got a driver buried in there that we wrote (our NDA keeps me from saying who, but I would say every make listed in these forums --if I were to guess). Our vertical applications cannot be sold as a solution to a fortune 500 company with us demanding they buy a custom Lenovo hardware. That has only worked with Government sales because the Lenovo suits convinced them that they are super secure.
Anyway, good luck
TD
Thats some good info man. Now I'm thinking of rooting and throwing it up for sale as rooted and buying a transformer prime
manooti said:
Thats some good info man. Now I'm thinking of rooting and throwing it up for sale as rooted and buying a transformer prime
Click to expand...
Click to collapse
Also, might I add they seem to want to restrict you and feed you a bunch of their 'bloatware'. A few months back, when they were in talking with our management team they said they were offering a complete solution hardware and software. They want to make money on their Marketplace applications, etc etc. I sort of got the impression they thought that was where the real money was and not in just selling tablets.
TD
Now that makes sense. Theyll never release an unlocked boot
This sucks man..
Going to root after ghost adventures
One question before I go all the way with it, whats the procedure for updating with new releases? Best to wait for your releases?
manooti said:
Now that makes sense. Theyll never release an unlocked boot
This sucks man..
Going to root after ghost adventures
One question before I go all the way with it, whats the procedure for updating with new releases? Best to wait for your releases?
Click to expand...
Click to collapse
New releases, go for it:
This is what I do:
1. Backup my apps because if the OTA knocks out root(#), you have to flash it.
2. I install the backdoor
3. I backup the su
4. I lock the su and backup su so updates HOPEFULLY don't break root(#)
5. Then I take the OTA.
6. After OTA, I reconnect and see if root(#) is still working. If not, I try the backup root(#). If they are both gone, then I hope the backdoor still works. If not then I flash back to where I was. I then ***** at Lenovo and look for a way to hack it.
Anyway, the backdoor and locking of su are in a script file you can run as long as you have adb working. 99% of the time su stays (because you lock it) or the backdoor works. Also, before taking the OTA you can usually download and see what they are changing. If it breaks root and the back door then what I usually do is pull it apart and build a custom system.img. Inside the OTA zip will be the boot.img. You can actually take it and 'cook' it in your kitchen adding root. Then you take the system.img from a prior release, mount it, and replace all the files with the ones inside your OTA. Make sure you account for blob changes if they are in the OTA. If there's a blob, then put it in the blob tool folder, extract it, and add it to the flash and replace bootloader.bin. Swear some more at Lenovo, and flash in your custom ROM. Now ad su and busybox, and superuser.apk. Use the dump tools in dump folder to build a new system.img. Replace your cooked boot.img with the original OTA boot.img and you're done.
TD.
Then ***** at Lenovo some more lol.
Thanks for the tips, Ill try the script if there is a reasonable update for it ie ICS.
For now the root worked.. flawlessly. Thanks for your work man.

[Q] Rooting a U8800 that's currently on 2.2...

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.

Worth to Root + New Rom my Tab.

Hey everybody I was just wondering if it was worth to do it...
Will the overall performance of my tablet be affected to better?
I have some small experience with rooting and installing new roms on my phone, (epic 4g touch) but i know nothing of rooting and installing new roms to tablets.
Thanks
Sent from my A500 using XDA Premium HD app
No answer? Helloooo somebody out there lol?
Sent from my Epic 4G Touch on Codename JoyRide using xda Premium.
Hi, and welcome!
First sorry that you waited so long for a response. It's been a slow Sunday at XDA as far as I can tell.
And it's kinda difficult to give you an answer that everyone would agree with. But I'll give you my take on it. You could change out the words "Why do I" for "Is it worth it" in the following if you like.
Why do I root my tablet? Mainly for bootanimations, system tweaks, like the gps fix we used to have to use to get the gps even marginally functional (That's not an issue anymore, so no worries). I also like to mess with very noobish mod attempts. Noobish, but it makes me smile when I do something neat. Things like that. There are plenty more reasons but I think that should reflect the gist of it.
Why do I unlock my devices (read; install custom bootloader in this case.) and install custom roms? Mainly because of neat features that are above and beyond what the manufacturer includes. For instance the Acer Ring (Some like it, some don't.). as well as tweaks already performed by the chef, like that gps fix I mentioned. Then there is overclocking and the custom kernels.
I'm sure that you probably already know all of this, and while our tablet is really great stock and will do just fine. I think that it is improved using a custom rom. Plus, since it is a tablet rather than a phone, it isn't as critical if something goes wrong when you are goofing around installing the rom or unlocking. No one wants a brick. But it's gotta be a little less of a major problem on a tablet than a phone.
The only real downside of installing the custom bootloader that I know of would be that some users (including myself.) report a flicker and the homescreen going blank on rare occasion and the icons dissapear, but restarting the launcher fixes it. Just put a shortcut in the lockscreen to a home switcher. Thanks to loth77 for that tip. But it isn't something that everyone gets and it's not that big of a drag. I can't really think of any other negatives.
Here's probably the most important thing that you should remember. Get your CPUID in case something goes wrong. The tab is bulletproof if you have that. Here's a link to help understand the whys and hows.http://forum.xda-developers.com/showthread.php?t=1624645. Remember to get the drivers from acer, and if something doesn't work try changing usb ports, usb cable, or even the pc.
That should pretty much be the long and short of it. Hope it helps. And good luck.
Hey thanks a lot, I think I might root it, Im familiar with flashing roms but the Bootloaders are new to me, can you tell me why do I need to unlock it to install a rom?
Sent from my Epic 4G Touch on Codename JoyRide using xda Premium.
If I understand the process correctly it is something about the way that the bootloader does its security checks. If you have a stock bootloader it looks for the stock rom only. If it doesn't find a rom/kernel that it expects you get to see the android on it's back. The custom bootloader doesn't mind a custom rom. If you want a technical answer maybe someone smarter than myself could explain it better. But I think that is pretty close.
JdgM3NT4L said:
If I understand the process correctly it is something about the way that the bootloader does its security checks. If you have a stock bootloader it looks for the stock rom only. If it doesn't find a rom/kernel that it expects you get to see the android on it's back. The custom bootloader doesn't mind a custom rom. If you want a technical answer maybe someone smarter than myself could explain it better. But I think that is pretty close.
Click to expand...
Click to collapse
And you said it, more or less
With ICS, the bootloader and boot.img communicate. A lot. Neither wish to run properly as they should. In the beginning, we hacked the ICS kernel to run on an HC bootloader. It worked and gave system somewhat RW, but is was crappy to say the least, and caused display irregularities on boot, and sometimes during operation. But when Skrilax_CZ started working on the ICS Bootloader, we could run an ICS kernel, and still get somewhat root and /system RW. But the RW was crappy, and required re-mounting /system all the time.
Having root, without /system RW, is like having a hamburger without the burger. Yeah, it kinda looks like it, but still....
Thus the "tweaked" ICS boot.img came out. Basically the same kernel, but the Zimage has some mods to it. Namely changing the part that prevented RW. And thus, the fully unlocked, fully RW system came out. And technically, you don't need busybox. Just SU. But busy box has to be there for other deals.
So now, to get the full unhindered benefit of both worlds, it's required to change bootloaders. We can do this via NVFlash, because we have the Secured Bootloader Key algorithm (SBK).
Also, HC based Roms WILL NOT run on the ICS bootloader, locked or unlocked. So if ya wanna play ball in our park, ya hafta play by our rules.
You can get your root under a stock ICS bootloader, but, you will have issues with system RW. This I promise.
Also with the unlocked bootloader, you get "fastboot" functions. Consider it your last line of defense. But for those that know how to use it, it's better than flashing certain things.
MD
For what this is worth, as a total noob to all this I decided to try the custom bootloader. Knowing from bricking a Wii once, I made a nand and a rom backup, got my CPUID using blackthund3r's ACER manager for those using ICS (just an incredible thing), and got to work.
I made an error and got hung in APX mode and initially I had at least three heart attacks when I thought I'd bricked; however I figured there had to be a way out as tablet still came on and I had done all the above. Reran Acer manager, changed my previous decision, and soon (within 5 mins) boatloader patched. I've since tried so many roms I've lost count.
Regrets? Not one. It's faster and better. Reading this thread, however, and learning that with a CPUID the tablet is bulletproof makes me feel even better! If you're a noob like me, it's a little scary, but backup, get a nand and the CPUID, Acer Mgr, follow the directions and go for it. After all I went through, if I can do it, so can you!
Yeah I flashed a rom already seens to be working great, i dont have much time right now to mess around with it but its definally better fellows, thanks
Sent from my Epic 4G Touch on Codename JoyRide using xda Premium.

Stock JB unlock and custom recovery considerations

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.

Cyanogenmod mod ?

Is their a cyanogenmod version that works for non developers editions of the verizon note. I just got my note 3 and without cyanogenmod it would stink.. has the bootloader been unlocked ?
No, still can't flash custom kernels
mjh68 said:
No, still can't flash custom kernels
Click to expand...
Click to collapse
there are may subjects and threads on this matter. I realized that not everyone understands everything, but if you know enough to register on this site, you must know how to use the search function.
to sum up:
search before posting
for the time being s4 and above on verizon wont be able to run aosp roms*
*besides developers edition. (if you have to ask, you don't have one)
dogenut said:
Is their a cyanogenmod version that works for non developers editions of the verizon note. I just got my note 3 and without cyanogenmod it would stink.. has the bootloader been unlocked ?
Click to expand...
Click to collapse
i did the same thing back in January and i'm kicking myself in the ass for not doing a lot more research first. samsung software has got to be the worst, thats why this phone has 3 gb ram. use towel root and at least get root access to shut half the ****ty software off. the custom roms for this phone are just rework versions of bloatwiz.
That blows... has anyone been working on it ?
dogenut said:
That blows... has anyone been working on it ?
Click to expand...
Click to collapse
The likelihood that our bootloader will even be unlocked or that any real development will go into kexec allowing us to flash custom kernels is probably close to 0%, meaning there will not be a cyanogenmod for retail N3.
However, if you are looking for a closer to AOSP rom check out Eclipse Rom. The dev has put much coding into the rom to make it feel like AOSP, it's not without its faults but what rom is perfect?
Also the devs for Alliance Rom have said they will be releasing an AOSP version in the future and many people are looking forward to that.
With practically any rom you will find yourself uninstalling a lot of bloatware unless you are one of the few who bought a Samsung device to use the proprietary software.
Either way, have fun.

Categories

Resources