[Q] Confused... - Transformer TF300T General

Hi Guys,
I'm just coming back to this after about half a year hiatus and I definitely had to catch up on a few things but with so many threads about using this TWRP and hardbricking due to incompatible bootloader vs ROM, I thought I'd ask if I am doing this right to clear up whatever confusion I have left.
Currently, I'm on CROMI which is a 4.1 ROM. Now, after reading for the last 3 hours, am I correct in my understanding that...
1. I have to install TWRP 2.5 via fastboot (because 2.6 has issues)
2. Flash the lastest Asus Stock Rom which will bring me from the 4.1 to 4.2 BOOTLOADER
3. Install any 4.2 Rom
Thanks!
X

Use this guide, it has all the information you need http://forum.xda-developers.com/showthread.php?t=2187982
Enviado do meu TF300T utilizando Tapatalk 4

Related

[Q] Upgrading to 4.4 from 4.2, Questions

XDA,
I am currently running PA 3.69 (Android 4.2.2) with stock PA kernel and a .48 modem, and I am looking to flash the new CM11 M3 snapshot (4.4) with franco.Kernel and put on MultiROM with Ubuntu Touch. I have been out of the custom ROM scene for a while and I would like to make sure I get this right the first time.
Do I need to flash a 4.4 modem before I update the OS? Then, do I just flash the .ZIP from CM's website from within CWM? Or should I grab a factory image from Google and start from there?
Also, should I flash the franco.Kernel immediately after rebooting into the ROM, or does it not matter? I had problems with flashing kernels on my old phone after the OS had already been running for a long time.
Thanks in advance to all of you guys, you're an awesome community to be a part of.
cpkelley94
Both kk modem and bootloader aren't mandatory but they are recommended
While you're in recovery flash the desired kernel after the rom but also you can do it after reboot
And... There are help threads here where you can start rather than opening another topic
sent from my Darkside of Nexus 4

STUCK at bootloader after flash stock ROM from CM13

Hi, so i got problem about installing to stock rom of note 4 5.1.1 . So couple days ago, i start to flash my stock ROM to other ROM such eRobot,sixperience,etc. And i change to CM12 cause i want to try the pure lollipop. So it's work like a charm using the CM12 Treltexx. Then i decide back to eRobot to test something. Then next day i decide back to CM12 because i'm much better using CyanogenMod. Then i'm searching on XDA CM13 for note 4 and i found the RaymanFX CM13 Unofficial. I start download and flash it. I Saw many bug and bored with CM13 then i decide back to eRobot. I try to flash it but it stuck on bootloader. And then i try sixperience, it same again.Ok so my next step is to Reflash it with ODIN. I start flash it again. Once it say "PASS" it start loading with SAMSUNG Boot logo, but is that succesfully go to the OS ? Nope, it's just restart and restart on Samsung boot logo and i can't do anything. I i'll ready try to wide factory reset with Stock recovery but still didn't work. So i decide to reflashing to CM13 that i already backup it on TWRP. IT'S WORK. So the conclusion is ALL ROM DOESN'T WORK EXCEPT CYANOGENMOD. Please help me i'm stuck at CM13 and i want back to the Stock ROM / eRobot, etc.
Ha ha, this is becoming a trend now, please confirm your problem is same as mine (mine is Note 3 but that's not the point),
https://www.youtube.com/watch?v=ck6e8y4S3tQ
ithehappy said:
Ha ha, this is becoming a trend now, please confirm your problem is same as mine (mine is Note 3 but that's not the point),
Click to expand...
Click to collapse
Same with you, but I got this problem after I flash from CM13 and want back to eRobot / stock ROM
That is exactly what happened with me too brother, I was wanting to go back to stock based ROM from a ported ROM.
Could you try one thing, flash the Bootloader (of the stock ROM) only via Odin at first, then do a battery pull and flash the stock ROM via Odin, see if that does anything or not.
ithehappy said:
That is exactly what happened with me too brother, I was wanting to go back to stock based ROM from a ported ROM.
Could you try one thing, flash the Bootloader (of the stock ROM) only via Odin at first, then do a battery pull and flash the stock ROM via Odin, see if that does anything or not.
Click to expand...
Click to collapse
I already try it using the WanamLite Modem + Bootloader. Still didnt work
Hmm, no idea then. If you find any solution kindly don't forget to tag me.
AlStarsKyz said:
Hi, so i got problem about installing to stock rom of note 4 5.1.1 . So couple days ago, i start to flash my stock ROM to other ROM such eRobot,sixperience,etc. And i change to CM12 cause i want to try the pure lollipop. So it's work like a charm using the CM12 Treltexx. Then i decide back to eRobot to test something. Then next day i decide back to CM12 because i'm much better using CyanogenMod. Then i'm searching on XDA CM13 for note 4 and i found the RaymanFX CM13 Unofficial. I start download and flash it. I Saw many bug and bored with CM13 then i decide back to eRobot. I try to flash it but it stuck on bootloader. And then i try sixperience, it same again.Ok so my next step is to Reflash it with ODIN. I start flash it again. Once it say "PASS" it start loading with SAMSUNG Boot logo, but is that succesfully go to the OS ? Nope, it's just restart and restart on Samsung boot logo and i can't do anything. I i'll ready try to wide factory reset with Stock recovery but still didn't work. So i decide to reflashing to CM13 that i already backup it on TWRP. IT'S WORK. So the conclusion is ALL ROM DOESN'T WORK EXCEPT CYANOGENMOD. Please help me i'm stuck at CM13 and i want back to the Stock ROM / eRobot, etc.
Click to expand...
Click to collapse
There are 3 ways to fix your problem, they are as follows;
1. Restore your EFS & Radio partition from your backed up using TWRP (if you have backed it up)
2. Go to CM 13 Discussion or CM 13 build 7 thread for more information using ADB Sideload
3. Go to your nearest Samsung Service Center and hoping they will fix it
What you have is corrupted EFS partition because, currently the highest firmware for Note 4 is 5.1.1 (Android L) and you have intentionally use 6.0.1 (Android M), and due to Samsung policy which stated, "you can't revert to your previous firmware once you have upgraded your ROM", therefore any 5.1.1 (Android L) ROM will fail to recognize your EFS. The result of this failure is, inability to load into system except Android M.
I don't know which CM 13 build that you flashed, but all CM 13 ROMs are based on 6.X.X (Android M), hence the name Unofficial Build CM 13 6.0.1 <-- this number means something not just a counter. Unfortunately, there is no cure for error that you have, only 3 ways as I have mentioned above. As fellow CM 13 user, I would suggest you to stay with CM 13 just for safety unless you know what to do if trying to use ways No. 2, the risk of using No. 2 is loosing you IMEI, which can cause your phone to be nothing but paperweight.
I use CM 13 as my daily ROM, and my phone is function smoothly asides from some bugs, but I trust the developers will resolve those with future release. Look at my replies on some CM 13 threads, I have posted some pictures as evidence how CM 13 works on my SM-N910H (Note 4 Exynos). Its lightweight, customize-able, battery friendly and no bloatware. Lots of apps to replace what you have in TW ROM or Stock, and all CM builds are able to recognize Note 4 S-Pen (Stylus).
Mengaten Kang Mas, Mugi2 Njenengan Saget Legowo, CM 13 Apik Kok... Saestu.
ghembuls said:
There are 3 ways to fix your problem, they are as follows;
1. Restore your EFS & Radio partition from your backed up using TWRP (if you have backed it up)
2. Go to CM 13 Discussion or CM 13 build 7 thread for more information using ADB Sideload
3. Go to your nearest Samsung Service Center and hoping they will fix it
What you have is corrupted EFS partition because, currently the highest firmware for Note 4 is 5.1.1 (Android L) and you have intentionally use 6.0.1 (Android M), and due to Samsung policy which stated, "you can't revert to your previous firmware once you have upgraded your ROM", therefore any 5.1.1 (Android L) ROM will fail to recognize your EFS. The result of this failure is, inability to load into system except Android M.
I don't know which CM 13 build that you flashed, but all CM 13 ROMs are based on 6.X.X (Android M), hence the name Unofficial Build CM 13 6.0.1 <-- this number means something not just a counter. Unfortunately, there is no cure for error that you have, only 3 ways as I have mentioned above. As fellow CM 13 user, I would suggest you to stay with CM 13 just for safety unless you know what to do if trying to use ways No. 2, the risk of using No. 2 is loosing you IMEI, which can cause your phone to be nothing but paperweight.
I use CM 13 as my daily ROM, and my phone is function smoothly asides from some bugs, but I trust the developers will resolve those with future release. Look at my replies on some CM 13 threads, I have posted some pictures as evidence how CM 13 works on my SM-N910H (Note 4 Exynos). Its lightweight, customize-able, battery friendly and no bloatware. Lots of apps to replace what you have in TW ROM or Stock, and all CM builds are able to recognize Note 4 S-Pen (Stylus).
Mengaten Kang Mas, Mugi2 Njenengan Saget Legowo, CM 13 Apik Kok... Saestu.
Click to expand...
Click to collapse
And when even flashing CM 13 the phone don't start ?
ghembuls said:
There are 3 ways to fix your problem, they are as follows;
1. Restore your EFS & Radio partition from your backed up using TWRP (if you have backed it up)
2. Go to CM 13 Discussion or CM 13 build 7 thread for more information using ADB Sideload
3. Go to your nearest Samsung Service Center and hoping they will fix it
What you have is corrupted EFS partition because, currently the highest firmware for Note 4 is 5.1.1 (Android L) and you have intentionally use 6.0.1 (Android M), and due to Samsung policy which stated, "you can't revert to your previous firmware once you have upgraded your ROM", therefore any 5.1.1 (Android L) ROM will fail to recognize your EFS. The result of this failure is, inability to load into system except Android M.
I don't know which CM 13 build that you flashed, but all CM 13 ROMs are based on 6.X.X (Android M), hence the name Unofficial Build CM 13 6.0.1 <-- this number means something not just a counter. Unfortunately, there is no cure for error that you have, only 3 ways as I have mentioned above. As fellow CM 13 user, I would suggest you to stay with CM 13 just for safety unless you know what to do if trying to use ways No. 2, the risk of using No. 2 is loosing you IMEI, which can cause your phone to be nothing but paperweight.
I use CM 13 as my daily ROM, and my phone is function smoothly asides from some bugs, but I trust the developers will resolve those with future release. Look at my replies on some CM 13 threads, I have posted some pictures as evidence how CM 13 works on my SM-N910H (Note 4 Exynos). Its lightweight, customize-able, battery friendly and no bloatware. Lots of apps to replace what you have in TW ROM or Stock, and all CM builds are able to recognize Note 4 S-Pen (Stylus).
Mengaten Kang Mas, Mugi2 Njenengan Saget Legowo, CM 13 Apik Kok... Saestu.
Click to expand...
Click to collapse
Yes i used CM13 and function smoothly, but there couple bugs such Spen, and 4G didn't work in my country and when i try to flashing the stock rom, it's stuck on samsung logo.
*Simpati ra kenek 4Gne mas )
i got the same issue on my note 4 n910h is frustrating there is any solution to this or just wait until Samsung release a new update of 6.0 for the note 4
Try this 4 part factory firmware it's full wipe rom https://mega.nz/#!eJIUiLQD!r-HcKWRWd...VriCeWYdNpxeTo
Or http://d-h.st/EPj8
http://forum.xda-developers.com/showthread.php?t=3312161
Try this
Sent from my HTC Desire 820s dual sim using Tapatalk
HmanA6399 said:
http://forum.xda-developers.com/showthread.php?t=3312161
Try this
Sent from my HTC Desire 820s dual sim using Tapatalk
Click to expand...
Click to collapse
Gonna try that. Thanks m8 for the help )
Hey, guys as we all know The stock marshmallow for note 4 is out. Is it possible to flash it without boot looping to famous Samsung-logo. If there is a way I would really appreciate the help.

Would like to pay someone for help

Hi,
I hope this is allowed,
Ive got a Zenfone 2 that i only uised for 3 months, and now im about to give the phone away and would like to install the latest CM on it and have a fresh start for the new user,
Now - ive got some experience in rooting and flashing firmware and all that stuff, but its been so long and dont want to spend hours reading and stuffing around
Details:
Asus_Z00AD
Android version 5.0
its running SUperzen 2.20.50.90
Anyway
I can pay using something like paypal and am prepared to pay $10USD
I assume if you know what your doing and can walk me through it using an app like whatsapp , or facebook messenger etc.
Please send me a pm with a wayh for me to contact you!
ill be up for a few more hours.
Thanks
I think it's not wise to put"I will pay foe someone to help me".
Just share your problem at the right place and you will find help.
Just unlock the bootloader via http://forum.xda-developers.com/zenfone2/general/tool-one-click-bootloader-unlock-root-t3155884
Now with bootloader unlocked reboot into fastboot - and flash twrp. (fastboot flash recovery twrp.img)
With twrp installed reboot into recovery and flash cm13.
simple stuff saved you 10$
Heck, since you said you have superzen installed. That means you are already unlocked, and i assume have twrp installed. All you need to do is download the latest cm and open gapps (x86 nano version)). Then wipe and flash in twrp
Sent from my ASUS_Z00A using Tapatalk
You saved $10 now. Well, I recommend ResurrectionRemix 5.7 + Holo Kernel to daily driver. I'm enjoying the combo. I will backup it (TWRP) and try Asus MM to see the future improvements. Well, at the end of the night my phone can evolve into a brick or a happy MM phone.
A tip: if you dont consider yourself a experienced user, dont try to flash beta Asus MM firmware.
A tip2: If you like the stock experience, try the RussiaNBear ROM 7.3 with BORETS24 kernel. Its really smooth, and comes rooted, with Viper4Android and debloated.

New to Zenfone 5 Scene at XDA

Hello,
I've been using my Asus Zenfone 5 for last 3 years. It came with Jelly bean and got updated till Lollipop. After the Lollipop upgrade there were a lot of issues including battery, signaling, storage and apps crashing.
I followed some tuts and recently downgraded to KitKat. Having no issues for now.
I get an on-screen time of 4 hours and 11 minutes. Not sure if it's supposed to be bad or not. I'm looking to flash an AOSP ROM, preferably KitKat or Lollipop based as I'm tired of ZenUI and the poor battery backup.
I've previously used a Moto E, Galaxy SIII and Moto E2. I kept the Zenfone instead because of the better hardware and features it offers.
Also if you link me to a ROM, be sure to link the flashing instructions as well. I'm using dual SIM.
Thanks.
Kitkat and Lollipop cooked rom has quite lot of issues. If I were you, I would pick a Nougat rom
Nougat ROM is more stable than KitKat? Interesting. This is the first time I'm hearing of it. Can you link me to a good ROM?
Sent from my Zenfone 5 using XDA Labs
Here's one : https://forum.xda-developers.com/ze...-resurrection-remix-n-5-8-0-tank0412-t3548135
Of course u must know the basic, flash recovery, rom,..
The only issue that every Asus devices must accept when install a custom ROM is can't use GPS and fmradio. (A-Gps still ok).
I used RR Android 6 rom for a few months. After boring issues etc. I went back to the modded Stock Android 5 but after a few months of usage i realised its worse and yesterday I installed Android 7 RR rom. It's perfect, just like a new phone.

[Solved] Most Stable rom for Mi A1 Tissot and some other relevant questions.

Hi,
Its been a long time since I last rommed any phone. Last Was my beloved 'Bacon' (Oneplus One) which I rommed till it died.
I am trying to install a custom rom on my wife's Mi A1. Have a few questions.
Which is the most stable rom (Android 11 preferred but if android 11 isn't stable then android 10 will do). Trying to replace the boring stock rom with some much needed features. but don't need a super tweaked up rom. Stability is most important. : edit: installed lineage 18.1.
Can I directly flash TWRP 3.6.0_9-0-tissot over stock? As with Bacon, I needed to flash One recovery then another to get a version jump. like I cant directly flash twrp 3.x over stock. I needed to flash TWRP 2.xy and then 3.0. (example, not real version numbers.)
I don't need root. But I do need the device to pass SafetyNet as I need it to operate apps like Gpay (which does not work if device fails SafetyNet).
Can I re lock the bootloader after flashing TWRP? Would it help with SafetyNet situation?
OpenGapps still good?
xeltos said:
Hi,
Its been a long time since I last rommed any phone. Last Was my beloved 'Bacon' (Oneplus One) which I rommed till it died.
I am trying to install a custom rom on my wife's Mi A1. Have a few questions.
Which is the most stable rom (Android 11 preferred but if android 11 isn't stable then android 10 will do). Trying to replace the boring stock rom with some much needed features. but don't need a super tweaked up rom. Stability is most important.
Can I directly flash TWRP 3.6.0_9-0-tissot over stock? As with Bacon, I needed to flash One recovery then another to get a version jump. like I cant directly flash twrp 3.x over stock. I needed to flash TWRP 2.xy and then 3.0. (example, not real version numbers.)
I don't need root. But I do need the device to pass SafetyNet as I need it to operate apps like Gpay (which does not work if device fails SafetyNet).
Can I re lock the bootloader after flashing TWRP? Would it help with SafetyNet situation?
OpenGapps still good?
Click to expand...
Click to collapse
1. There are plenty of stable roms, you can look at Xiaomi Mi A1 ROMs section to check them.
2. You can directly flash TWRP on stock rom.
3. ?
4. No
5. I use roms with pre-installed GApps for stablity.
mahyarmo said:
1. There are plenty of stable roms, you can look at Xiaomi Mi A1 ROMs section to check them.
2. You can directly flash TWRP on stock rom.
3. ?
4. No
5. I use roms with pre-installed GApps for stablity.
Click to expand...
Click to collapse
Installed lineage 18.1 with opengapps micro.

Categories

Resources