Related
As the title says. I uploaded the tf300 firmware while rooted and an unlocked bootloader. I had twrp
I've heard that flashing the 'update' removes root and relocks the bootloader.
I really have no idea how to go back to ICS but i've read that theres a way. I just can't find any clear directions.
just download the new rom from asus and flash it in recovery.
when it reboots you will be back to stock with new bootloader.
I thought the bootloader went untouched by reflashing the stock ROM? (I might be mistaken here, but isn't that the entire issue with not being able to get back to the ICS bootloader after flashing the JB bootloader?)
New ROM has a new boot loader which will flash over jb.
lafester said:
New ROM has a new boot loader which will flash over jb.
Click to expand...
Click to collapse
However. there's no way to relock the bootloader as the OP had heard, correct?
okantomi said:
However. there's no way to relock the bootloader as the OP had heard, correct?
Click to expand...
Click to collapse
No you can't relock. Not sure where the op may have heard that as I have not seen it posted anywhere.
Might be confused with losing root?
lafester said:
just download the new rom from asus and flash it in recovery.
when it reboots you will be back to stock with new bootloader.
Click to expand...
Click to collapse
It was removed from the asus site, could you provide a link?
Also....do I need to rename it to anything and place it anywhere specific? Because I have already tried and it doesnt work for me. When i go into recovery i get the android with the exclamation point in red. So....idk....
its there i just looked.
you do need to unzip it since it is double zipped for some reason.
then flash as usual.
I have a me301t, basically the same as a tf300t right? (there is no me301t forum right now). I am on 4.2.1 stock (root), but the Bluetooth isn't working, so I am wanting to reflash the stock firmware. I want to keep a locked bootloader, so I can still have warranty if I please. I've looked up a couple of videos of how to, but I am wondering if root will mess up the flashing process. I've also been wondering if I can keep root after flash with Voodoo root keeper. Any advice?
majj7698 said:
I have a me301t, basically the same as a tf300t right? (there is no me301t forum right now). I am on 4.2.1 stock (root), but the Bluetooth isn't working, so I am wanting to reflash the stock firmware. I want to keep a locked bootloader, so I can still have warranty if I please. I've looked up a couple of videos of how to, but I am wondering if root will mess up the flashing process. I've also been wondering if I can keep root after flash with Voodoo root keeper. Any advice?
Click to expand...
Click to collapse
Edited Quote:
manikkumar20 said:
Dear all users of TF300T.
If you are using Stock ROM (Rooted/Non Rooted) and are bricked or stuck on ASUS boot screen. Then this guide is for you.
As i was using stock ROM (ROOTED) with Locked boot loader without custom recovery and my tf300t was Sofbricked due to wrong configurations at Display Pixel scaling and also reformat did not work for me.!
So i thought to create this guide which may help people out here It worked for me Try your LUCK.
Sorry if i am re posting i did not got any guides out here...
If this helped you please give me a Thumbs up.!
Steps:-
1. Download the latest ROM from ASUS website Which matches your SKU.(Important).
It would look somehing like this (TF300T-TW_epad-10_6_1_15_3-UpdateLauncher . zip)
2. Extract it and rename that file to ( EP201_768_SDUPDATE.zip )
3. Now copy this new renamed file to SDCARD (Root of sd card). Put the SDcard into tablet.
4. Now Press and hold Volume Down + Power for a few seconds. Then you will see the ASUS recovery options.
5. 3 icons will appear: RCK, Android, and Wipe Data. The RCK should be flashing green. Press the UP Volume Key Once.
Now wait for a few minutes. It will flash the ROM.
And wola! Your TF300T will again work fine!!
Click to expand...
Click to collapse
Use a compatible ROM though.
Already figured out.
cmendonc2 said:
Edited Quote:
Use a compatible ROM though.
Click to expand...
Click to collapse
Thanks, but I already figured it out, by looking on another forum. I didn't know that you could install a non-stock rom locked though
majj7698 said:
Thanks, but I already figured it out, by looking on another forum. I didn't know that you could install a non-stock rom locked though
Click to expand...
Click to collapse
You can't without unlocking. He means a compatible Asus ROM.
The ROM has to be signed by Asus, so that method I quoted will only work for Stock ROMS
cmendonc2 said:
The ROM has to be signed by Asus, so that method I quoted will only work for Stock ROMS
Click to expand...
Click to collapse
Oh, Okay, silly me
Hey guys, posted in a few threads but starting a separate thread to keep my issues out of them.
Anyways, my tablet is out up date and I havent kept up to speed on the last 2 years worth of developments. So im looking to upgrade my rooted and unlocked tablet on 4.1 to the 5.0 rom. My twrp version is 2.3.3.0.
How would i go about updating to a 4.4/5.0 compatible bootloader and recovery?
Ive been advised to update the bootloader, but should i flash the boot before the updated twrp or the other way around? While we're at it, I've noticed the nvflash tools. I'm assuming doing the nvflash stuff would help me recover from any possible bricks?
Any help would be appreciated.
jaydotelloh said:
Hey guys, posted in a few threads but starting a separate thread to keep my issues out of them.
Anyways, my tablet is out up date and I havent kept up to speed on the last 2 years worth of developments. So im looking to upgrade my rooted and unlocked tablet on 4.1 to the 5.0 rom. My twrp version is 2.3.3.0.
How would i go about updating to a 4.4/5.0 compatible bootloader and recovery?
Ive been advised to update the bootloader, but should i flash the boot before the updated twrp or the other way around? While we're at it, I've noticed the nvflash tools. I'm assuming doing the nvflash stuff would help me recover from any possible bricks?
Any help would be appreciated.
Click to expand...
Click to collapse
Yes here you are ....
Get the SKU from your bootloader screen .....
Then go to the Asus website and get the firmware for your SKU ending in 27.5 ...
Then unpack the zip and there will be another zip unzip it you will find a file called blob ....
Flash this blob from fastboot ...
Let me know if you need any help along the way..
Thx Josh
lj50036 said:
Yes here you are ....
Get the SKU from your bootloader screen .....
Then go to the Asus website and get the firmware for your SKU ending in 27.5 ...
Then unpack the zip and there will be another zip unzip it you will find a file called blob ....
Flash this blob from fastboot ...
Let me know if you need any help along the way..
Thx Josh
Click to expand...
Click to collapse
Thanks for following me around my 3 posts, lol.
Quick questions:
1. Should I flash the bootloader BEFORE flashing the updated TWRP? Or does the new TWRP get flashed before the bootloader.
2. When I flash the new bootloader, will i still be able to run 4.1 on the tablet (i.e. is the new bootloader backwords compatible?)
3. Will the NVFLASH stuff help me in the event that I do mess something up? Seems like it supposed to be a brick-proof safety net in case something goes wrong.
thanks for the help man!
jaydotelloh said:
Thanks for following me around my 3 posts, lol.
Quick questions:
1. Should I flash the bootloader BEFORE flashing the updated TWRP? Or does the new TWRP get flashed before the bootloader.
2. When I flash the new bootloader, will i still be able to run 4.1 on the tablet (i.e. is the new bootloader backwords compatible?)
3. Will the NVFLASH stuff help me in the event that I do mess something up? Seems like it supposed to be a brick-proof safety net in case something goes wrong.
thanks for the help man!
Click to expand...
Click to collapse
1. The blob file contains the SOS which is the stock recovery, so flash TWRP after ....
2. No you would have to revert back to a 4.1 bootloader to do that ...
3. Yes I would highly recommend doing this ......
4. If you need any help ever shoot me an email we can hangouts [email protected]
Thx Josh
lj50036 said:
1. The blob file contains the SOS which is the stock recovery, so flash TWRP after ....
2. No you would have to revert back to a 4.1 bootloader to do that ...
3. Yes I would highly recommend doing this ......
4. If you need any help ever shoot me an email we can hangouts [email protected]
Thx Josh
Click to expand...
Click to collapse
Thanks Josh, I think I know what to do now:
Step 1: Set up NVFLASH and get my backup files.
Step 2: Flash the 27.5 Bootloader using fastboot.
Step 3: Flash TWRP openrecovery-twrp-2.8.1.0-tf300t.blob
Step 4: Wipe system/cache, etc
Step 5: Flash Katkiss 5.0
Is this correct? Am i missing any steps in there?
Looks like you're not on hangouts right now, shoot me a message if we can chat. [email protected]
So, Josh TOTALLY hooked me up on this issue. Not only offer his help, he actually walked me through the entire process watching my screen through screenshare. I'm now up and running on Kitkass 5.0.... sweet sweet lollipop goodness.
Not sure how to edit the title to solved, but maybe a mod could do that?
jaydotelloh said:
So, Josh TOTALLY hooked me up on this issue. Not only offer his help, he actually walked me through the entire process watching my screen through screenshare. I'm now up and running on Kitkass 5.0.... sweet sweet lollipop goodness.
Not sure how to edit the title to solved, but maybe a mod could do that?
Click to expand...
Click to collapse
If you go to edit your first post and then go to adv edit, there you can add 'SOLVED'
Thx Josh
Hi! My question is lame, i know.. But here it goes anyway, i couldn't find a simple and direct answer..
Is less than a week that i have this phone, and i've been reading a lot of guides of how to rollback to cm11s.. the thing is i've flashed the latest CM12S signed zip ota through CM Recovery, everything is fine as i'm testing it right now..
My question is: if i want to go back to CM11S (in the case that i don't like CM12S or have some bugs), can i just wipe data / factory reset and cache in CM Recovery, and then flash the cm11s signed zip?
I haven't rooted or unlocked bootloader, is it relatively easy from what i read around here.. but i wondered if i had to go through all those steps (unlock bootloader, custom recovery, and then flash) or just doing the steps mentioned before will work just fine..
Is it better to fastboot flash or through custom recovery is fine also?
Thanks in advance!
PD: I'm also asking what do you think about some other 5.1.1 Lollipop ROM, custom kernel, etc.. I'm kind of a flashaholic and i would be able to install the custom recovery if would be really worth it
PD2: sorry for the bad english, i'm from argentina
cesarp3791 said:
Hi! My question is lame, i know.. But here it goes anyway, i couldn't find a simple and direct answer..
Is less than a week that i have this phone, and i've been reading a lot of guides of how to rollback to cm11s.. the thing is i've flashed the latest CM12S signed zip ota through CM Recovery, everything is fine as i'm testing it right now..
My question is: if i want to go back to CM11S (in the case that i don't like CM12S or have some bugs), can i just wipe data / factory reset and cache in CM Recovery, and then flash the cm11s signed zip?
I haven't rooted or unlocked bootloader, is it relatively easy from what i read around here.. but i wondered if i had to go through all those steps (unlock bootloader, custom recovery, and then flash) or just doing the steps mentioned before will work just fine..
Is it better to fastboot flash or through custom recovery is fine also?
Thanks in advance!
PD: I'm also asking what do you think about some other 5.1.1 Lollipop ROM, custom kernel, etc.. I'm kind of a flashaholic and i would be able to install the custom recovery if would be really worth it
PD2: sorry for the bad english, i'm from argentina
Click to expand...
Click to collapse
Just unlock your bootloader now, the longer you leave it the more difficult it'll be to backup your internal storage beforehand. You should really have it unlocked anyway as insurance against anything going wrong with your phone. Once you have unlocked it you can flash TWRP recovery, then the correct procedure to go back to CM11S would be to perform a full wipe (system, data, cache, dalvik cache) and then just flash the zip. As far as custom ROMs for this device go, there are many excellent options to choose from that offer extra customisation that you won't find on the stock ROM.
Don't we have to flash the firmware prior to flashing back to CM11s to prevent a hardbrick? I'm looking into doing this as well, so I'm just asking for my own clarity.
uansari1 said:
Don't we have to flash the firmware prior to flashing back to CM11s to prevent a hardbrick? I'm looking into doing this as well, so I'm just asking for my own clarity.
Click to expand...
Click to collapse
The firmware is contained in the official zip.
Heisenberg said:
The firmware is contained in the official zip.
Click to expand...
Click to collapse
Thanks! Stupid question, but can you please link me to the official zip? I already have TWRP installed, so it would be nice to revert sooner than later.
uansari1 said:
Thanks! Stupid question, but can you please link me to the official zip? I already have TWRP installed, so it would be nice to revert sooner than later.
Click to expand...
Click to collapse
You'll find them all here:
http://forum.xda-developers.com/showthread.php?t=2906746
Thanks!
Thank you both, i believe that this week i'll have some time and unlock the bootloader and flashing the TWRP recovery right away.. Then i'll see which ROM suits my use (i'm looking to battery friendly and high screen on time, will see the forums accordingly) and start the journey on this beautiful and well supported device
Also, thanks for the clarification of the modems.. Will be looking after that and make sure not to miss that step if required :good:
cesarp3791 said:
Thank you both, i believe that this week i'll have some time and unlock the bootloader and flashing the TWRP recovery right away.. Then i'll see which ROM suits my use (i'm looking to battery friendly and high screen on time, will see the forums accordingly) and start the journey on this beautiful and well supported device
Also, thanks for the clarification of the modems.. Will be looking after that and make sure not to miss that step if required :good:
Click to expand...
Click to collapse
Once you've flashed the ROM, please do share your results. I am still unsure if reverting from a Lollipop ROM to CM11S will cause issues with the radio and/or a softbrick of the device, as I've read that this "can" happen.
uansari1 said:
Once you've flashed the ROM, please do share your results. I am still unsure if reverting from a Lollipop ROM to CM11S will cause issues with the radio and/or a softbrick of the device, as I've read that this "can" happen.
Click to expand...
Click to collapse
Reverting from Lollipop to KitKat won't brick your device, whoever said that is wrong, and would have caused a brick because they didn't know what they were doing. You do need to make sure you flash a KitKat modem though, otherwise you'll have issues with the prox sensor.
Heisenberg said:
Reverting from Lollipop to KitKat won't brick your device, whoever said that is wrong, and would have caused a brick because they didn't know what they were doing. You do need to make sure you flash a KitKat modem though, otherwise you'll have issues with the prox sensor.
Click to expand...
Click to collapse
Thanks Timaaa...last question, I'm downloading the latest modem from this thread http://forum.xda-developers.com/oneplus-one/development/rom-stock-rooted-xnph05q-t3027033.
Is this the correct flashable modem file to use, or do you recommend another for XNPH05Q?
uansari1 said:
Thanks Timaaa...last question, I'm downloading the latest modem from this thread http://forum.xda-developers.com/oneplus-one/development/rom-stock-rooted-xnph05q-t3027033.
Is this the correct flashable modem file to use, or do you recommend another for XNPH05Q?
Click to expand...
Click to collapse
That modem should be fine.
Hi. I have an Indian variant Motorola turbo. I am on a custom ROM(forgot the name acually) and thougt everything was working till my phone rebooted suddenly and went into recovery mode. Since then I have been trying to resurrect the phone but failing. Could someone here can help me to resurrect my phone back? I would reward you for your help..
Note : Tried all possible ways to get my phone back but its staying only in bootloader No matter what i do.
Update August 2020 : While taking out my things, I found my moto maxx, and after looking at it i wanted to give a try once again. If someone can help in bringing my mobile back to life. Attacing the images of the logs on the screen. Only bootloader is seen always. Please help me. I can pay more to someone who could help me.
was this on a fresh install? was this working for like a week or longer and then **** the bed? is it charged fully? can you reinstall the ROM fresh and have it boot? might have to brush up on mfastboot commands and getting access to push files to the memory so you can flash the ROM again.......
Did you somehow get your bootloader from unlocked state to relocked?
linuxsociety said:
Did you somehow get your bootloader from unlocked state to relocked?
Click to expand...
Click to collapse
Dont know. How to check it when in fastboot mode? Any command?
Is the issue resolved?If not I can help you
gauthamkithu said:
Is the issue resolved?If not I can help you
Click to expand...
Click to collapse
If you could help me, I will be really happy
krishna13 said:
If you could help me, I will be really happy
Click to expand...
Click to collapse
Ok tell me a few things,
1) were you on the latest firmware while unlocking bootloader?i.e, were you on the latest update of Android 6.0 while unlocking bootloader?
2) Have you tried flashing the stock rom ? While flashing stock rom you must edit the update script and remove the line which flashes the partition.
3) Was the custom rom working fine? Or did the issue start as soon as you flashed the ROM?
4)Can you go to recovery? If no what is happening when you try to go to recovery?
gauthamkithu said:
Ok tell me a few things,
1) were you on the latest firmware while unlocking bootloader?i.e, were you on the latest update of Android 6.0 while unlocking bootloader?
2) Have you tried flashing the stock rom ? While flashing stock rom you must edit the update script and remove the line which flashes the partition.
3) Was the custom rom working fine? Or did the issue start as soon as you flashed the ROM?
4)Can you go to recovery? If no what is happening when you try to go to recovery?
Click to expand...
Click to collapse
Thanks for your reply bro. I will DM my number or you DM yours. I will give you a call and will explain things.
gauthamkithu said:
Ok tell me a few things,
1) were you on the latest firmware while unlocking bootloader?i.e, were you on the latest update of Android 6.0 while unlocking bootloader?
2) Have you tried flashing the stock rom ? While flashing stock rom you must edit the update script and remove the line which flashes the partition.
3) Was the custom rom working fine? Or did the issue start as soon as you flashed the ROM?
4)Can you go to recovery? If no what is happening when you try to go to recovery?
Click to expand...
Click to collapse
Bro. I have messaged you my number. Please text your number too so that I could explain the issue clearly. But If you dont want to help me out, just say me so that I could find other way for help. Its been more than 5 days since i sent a message to you but i have not received any response from you.
gauthamkithu said:
Ok tell me a few things,
1) were you on the latest firmware while unlocking bootloader?i.e, were you on the latest update of Android 6.0 while unlocking bootloader?
2) Have you tried flashing the stock rom ? While flashing stock rom you must edit the update script and remove the line which flashes the partition.
3) Was the custom rom working fine? Or did the issue start as soon as you flashed the ROM?
4)Can you go to recovery? If no what is happening when you try to go to recovery?
Click to expand...
Click to collapse
Can someone tell me what is the name of the script file(2nd point) , where can I find in the firmware package and what lines should I need to edit?