Hi am having a problem after going back to telstra stock after being on rohans JB build 3. It was really bad at connecting on LTE so I wanted to go back to stock where I have less problems. So now the 4.0.4 OTA update is available which fixes the one of the main reasons I found a ROM, that stupid settings bar.
However when I reboot to install the OTA it just boots into TWRP (v 2.2.2). I cant manually apply update from within recovery. It just gives an error. If I reboot from recovery nothing is applied.
Android v 4.0.3, software version 1.89.841.9
Do I have to get rid off TWRP or find a RUU and and apply that image? Was there some boot locking thing I need to do through abd to get the OTA to work?
piscario said:
Hi am having a problem after going back to telstra stock after being on rohans JB build 3. It was really bad at connecting on LTE so I wanted to go back to stock where I have less problems. So now the 4.0.4 OTA update is available which fixes the one of the main reasons I found a ROM, that stupid settings bar.
However when I reboot to install the OTA it just boots into TWRP (v 2.2.2). I cant manually apply update from within recovery. It just gives an error. If I reboot from recovery nothing is applied.
Android v 4.0.3, software version 1.89.841.9
Do I have to get rid off TWRP or find a RUU and and apply that image? Was there some boot locking thing I need to do through abd to get the OTA to work?
Click to expand...
Click to collapse
Pretty sure you have to relock your bootloader and run an RUU to get your phone to true stock. Then OTA. Although, if the RUU was based off 4.0.4 you wouldn't have to OTA. You can always re-ulock your phone after an RUU as long as you have your unlock token and/or super CID.
Did you just flash a stock ROM?
Also, pretty sure there are 4.0.4 stock ROMs out there that you could flash so you wouldn't have to relock your phone.
Butters619 said:
Pretty sure you have to relock your bootloader and run an RUU to get your phone to true stock. Then OTA. Although, if the RUU was based off 4.0.4 you wouldn't have to OTA. You can always re-ulock your phone after an RUU as long as you have your unlock token and/or super CID.
Did you just flash a stock ROM?
Also, pretty sure there are 4.0.4 stock ROMs out there that you could flash so you wouldn't have to relock your phone.
Click to expand...
Click to collapse
Thanks I restored a backup I made before flashing the ROM. Might try and find another ROM to see how 4G goes.
Fixing a connectivity issue on one custom ROM is not a good reason to go stock. I think the OTA needs stock recovery, so that is why you are getting stuck at recovery. Even if it works, you lose root. Its a step backwards, so why would you want to do that?
Just flash a ROM based on 4.0.4 from Development. You can pick a custom ROM, or a stock rooted one (safe to flash from TWRP), if you want stock.
If you are rooted, don't install a OTA or run RUU (unless you are trying to fix a soft brick). Good rule for any Android device.
hi, can some one please help me with how to downgrade the firmware from 4.1 to 4.0, also would i be able to get ota after i do that by using odin...
if not how do i install updates for 4.0, i am confused about that will i go back to the official firmware and get future ota's or will i always have to use odin....
At the top of this section I have highlighted how to flash a firmware the same process needs to be followed for all firmware no matter what it is ICS or JB
Also read the warning there which is when you downgrade your device will not boot and may get stuck at the Samsung logo and you will need to do a complete wipe by going into recovery to make the device boot
So please back up all your data
If you install the rom (applies for JB & ICS) which belongs to the country of origin of the device you will get OTA
downgrade, manually upgrade.. Spen Pb.
samir_a said:
At the top of this section I have highlighted how to flash a firmware the same process needs to be followed for all firmware no matter what it is ICS or JB
Also read the warning there which is when you downgrade your device will not boot and may get stuck at the Samsung logo and you will need to do a complete wipe by going into recovery to make the device boot
So please back up all your data
If you install the rom (applies for JB & ICS) which belongs to the country of origin of the device you will get OTA
Click to expand...
Click to collapse
I confirm. I downgrade yesterday... loosing all data. RE installing German JB... so I still have som problems with S pen in some dead zone (top and down part around the Logo).
I've heard there was a 4.0.2 android around in the Xda forum.. I'l ll have a look.
Hello forum,
Device: tf300t Jb 4.2.2
I was trying new roms ( cm10.1 from surdu's, aokp r06a, franco kernel, CROMi-Xenogenesis DEODEX and others) and some of them work and others didn't really worked.
During the installations I used CWMR v6.0.1.3 and used all the standart procs like format wipe cache/dalvik etc.
Since I wasn't able to overclock with the roms that worked on my tf300t, I decided to install my initial functional rom cm10.1 > with perf kernel.
This time when I turn on the device it wont get past the initial bootscreen (black screen/white asus logo). It just loops and loops in an eternal cicle rebooting constantly.
I'm not sure if the tablet is bricked or not so I don't really know what procedure should I use to fix it... Could use some help please.
I don't really understand why some roms didn't work in the first place, I used the same procedure installing other roms and they worked fine....
They were compatible with device and jb 4.2.2 as far as I understand... I don't know what I'm missing.
Thank for your time and attention.
The best regards,
Absinto10
absinto10 said:
Hello forum,
Device: tf300t Jb 4.2.2
I was trying new roms ( cm10.1 from surdu's, aokp r06a, franco kernel, CROMi-Xenogenesis DEODEX and others) and some of them work and others didn't really worked.
During the installations I used CWMR v6.0.1.3 and used all the standart procs like format wipe cache/dalvik etc.
Since I wasn't able to overclock with the roms that worked on my tf300t, I decided to install my initial functional rom cm10.1 > with perf kernel.
This time when I turn on the device it wont get past the initial bootscreen (black screen/white asus logo). It just loops and loops in an eternal cicle rebooting constantly.
I'm not sure if the tablet is bricked or not so I don't really know what procedure should I use to fix it... Could use some help please.
I don't really understand why some roms didn't work in the first place, I used the same procedure installing other roms and they worked fine....
They were compatible with device and jb 4.2.2 as far as I understand... I don't know what I'm missing.
Thank for your time and attention.
The best regards,
Absinto10
Click to expand...
Click to collapse
I really need help dudes... I already tried a bunch of procedures here on Xda but I can't find a solution... Tried adb, installing firmwares etc... nothing works.
Here's more info:
Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.4.2.9-20120809" A03
absinto10 said:
I really need help dudes... I already tried a bunch of procedures here on Xda but I can't find a solution... Tried adb, installing firmwares etc... nothing works.
Here's more info:
Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.4.2.9-20120809" A03
Click to expand...
Click to collapse
The bootloader you show above is not a JB 4.2 bootloader but the very 1st asus JB 4.1 - 10.4.2.9 bootloader/firmware
You will need to upgrade your bootloader depending on which roms you would like to flash, some roms are 4.1 compliant and other are 4.2 compliant so read the rom op for info on which bootloader you need for that rom.
Have a look at my how-to in sig below for info on how to upgrade your bootloader and which recovery is safe to flash for each bootloader.
Let me know if you need any help with any steps or info.
pjc21 said:
The bootloader you show above is not a JB 4.2 bootloader but the very 1st asus JB 4.1 - 10.4.2.9 bootloader/firmware
You will need to upgrade your bootloader depending on which roms you would like to flash, some roms are 4.1 compliant and other are 4.2 compliant so read the rom op for info on which bootloader you need for that rom.
Have a look at my how-to in sig below for info on how to upgrade your bootloader and which recovery is safe to flash for each bootloader.
Let me know if you need any help with any steps or info.
Click to expand...
Click to collapse
Thank you so much. I read your how-to tutorial and I think I already understand the process. I was a little bit confused because when I first flashed my tablet I didn't have enough experience with some android slag and definitions and I forgot which bootloader I was using.
Yesterday I couldn't install nothing via fastboot protocol but when the battery died and after charging it I was able to install other firmware(oficial) via fastboot. With the frustration, I installed WW_epaduser_10_4_2_20_UpdateLauncher, then with no success booting this I installed WW_epaduser_10_4_2_9_UpdateLauncher again.
When I read your tutorial I was very optimistic and things started to make sense... but when I tried to apply it, I couldn't install nothing via fastboot again (no blue bar) --". On the terminal it only says after clicking enter: "sending 'recovery' (7766 KB) or "erasing blah blah transfering files"..." And nothing happens...
Is it fast boot bricked? I don't understand why, there's no reason for that i guess!! Well I'll wait 'till the battery dies again and attempt to apply you tutorial once more.
Meanwhile reply please and thank you very much for the assistence
pjc21 said:
The bootloader you show above is not a JB 4.2 bootloader but the very 1st asus JB 4.1 - 10.4.2.9 bootloader/firmware
You will need to upgrade your bootloader depending on which roms you would like to flash, some roms are 4.1 compliant and other are 4.2 compliant so read the rom op for info on which bootloader you need for that rom.
Have a look at my how-to in sig below for info on how to upgrade your bootloader and which recovery is safe to flash for each bootloader.
Let me know if you need any help with any steps or info.
Click to expand...
Click to collapse
I missed one thing... I have no acess to adb too.
When I type "adb devices" no devices are found.
Thank you
pjc21 said:
The bootloader you show above is not a JB 4.2 bootloader but the very 1st asus JB 4.1 - 10.4.2.9 bootloader/firmware
You will need to upgrade your bootloader depending on which roms you would like to flash, some roms are 4.1 compliant and other are 4.2 compliant so read the rom op for info on which bootloader you need for that rom.
Have a look at my how-to in sig below for info on how to upgrade your bootloader and which recovery is safe to flash for each bootloader.
Let me know if you need any help with any steps or info.
Click to expand...
Click to collapse
Hello my friend once more
So forget the last posts I figured out the problem... So I was fastboot bricked and the only way I found to fix this was it in this post http://forum.xda-developers.com/showthread.php?t=2236885.
So I used he's bootloader.bin so I could "unbrick" my tablet and the fastboot commands. Afterwards I followed your tutorial always using "WW_epad-user-10.4.2.20" (stock firmware) and "openrecovery-twrp-2.5.0.0-tf300t-JB.blob" and everything worked fine. Installed the firmware, twrp, wipe cache/dalvik etc and flashed zip from external sd card. When I rebooted the blue bar and "signature matched" appeard on the screen and loaded just fine, but when it reboots again, the bootloop starts :'(.
This time when I entered again on the bootloader, Twrp was erased of my tablet...
Installed trwp again and on my bootloader I have this current information: Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.4.2.20-20121228" A03. Fastboot commands work fine so, as far as I understand, there's still hope for poor tf300t x).
I think the problem is the bootlader.bin version but idk. Please help I'm really getting frustrated with this. I'll wait for your reply because I don't want to cause anymore damage to the device :/. Thank you
Ok from what I understand the fastboot flash brick is caused by flashing a non-4.2 version of twrp or any version of cwm on a 4.2 bootloader, but as this was not the case for you I'm not sure of why you were unable to flash via fastboot until the tab had been drained and then recharged. Sounds like similar symptoms to the fastboot flash brick but I don't think people with the fastboot flash brick are able to flash at all even after the tab has drained and been recharged.
I have not heard of anyone with the fastboot flash brick (caused by above situation) unbricking there tab with the fix you tried in the above post.
However you seem to be in a different situation - the fix you tried in your post above, I believe will flash the bootloader bin file from the fisrt ICS firmware 9.4.3.29 which I thought could not be done if you have already upgraded to a JB bootloader.
When you first flashed the bootloader.bin did you happen to take note if your bootloader had changed to 9.4.3.29?
The reason I ask this is that I have tried before to downgrade from JB to an ICS bootloader and had no luck here, I would always get a "signature mismatch" trying to go from JB to ICS - but you appear to be getting this when flashing a JB bootloader. So now thinking this may be the first breakthrough in a way to downgrade from JB to ICS.
Your device is showing that you are now on the last JB 4.1 bootloader (10.4.2.20), so first I would try and flash the system blob for 10.4.2.20 again and see if that fixes the "signature mismatch" issue.
If not I have a thoery that may or maynot work, as you are getting this "signature mismatch" issue (after flashing the bootloader.bin for ICS) when you flash a JB bootloader. You could try (at your own risk) again flashing the ICS bootloader.bin from your above post, then reboot to bootloader and check what bootloader version you then have. If your bootloader is now saying 9.4.3.29 you could then try flashing the system blob from firmware 9.4.3.29 and see if the signature mismatch issue is fixed. If so you should then be able to flash a system blob from a JB firmware.
Not sure if the above will work but try flash the JB system blob from 10.4.2.20 first and if that does not work it's up to you if you would like to try the second.
If you need a step-by-step on how to do any of this or are unsure of anything above just let me know.
pjc21 said:
Ok from what I understand the fastboot flash brick is caused by flashing a non-4.2 version of twrp or any version of cwm on a 4.2 bootloader, but as this was not the case for you I'm not sure of why you were unable to flash via fastboot until the tab had been drained and then recharged. Sounds like similar symptoms to the fastboot flash brick but I don't think people with the fastboot flash brick are able to flash at all even after the tab has drained and been recharged.
I have not heard of anyone with the fastboot flash brick (caused by above situation) unbricking there tab with the fix you tried in the above post.
However you seem to be in a different situation - the fix you tried in your post above, I believe will flash the bootloader bin file from the fisrt ICS firmware 9.4.3.29 which I thought could not be done if you have already upgraded to a JB bootloader.
When you first flashed the bootloader.bin did you happen to take note if your bootloader had changed to 9.4.3.29?
The reason I ask this is that I have tried before to downgrade from JB to an ICS bootloader and had no luck here, I would always get a "signature mismatch" trying to go from JB to ICS - but you appear to be getting this when flashing a JB bootloader. So now thinking this may be the first breakthrough in a way to downgrade from JB to ICS.
Your device is showing that you are now on the last JB 4.1 bootloader (10.4.2.20), so first I would try and flash the system blob for 10.4.2.20 again and see if that fixes the "signature mismatch" issue.
If not I have a thoery that may or maynot work, as you are getting this "signature mismatch" issue (after flashing the bootloader.bin for ICS) when you flash a JB bootloader. You could try (at your own risk) again flashing the ICS bootloader.bin from your above post, then reboot to bootloader and check what bootloader version you then have. If your bootloader is now saying 9.4.3.29 you could then try flashing the system blob from firmware 9.4.3.29 and see if the signature mismatch issue is fixed. If so you should then be able to flash a system blob from a JB firmware.
Not sure if the above will work but try flash the JB system blob from 10.4.2.20 first and if that does not work it's up to you if you would like to try the second.
If you need a step-by-step on how to do any of this or are unsure of anything above just let me know.
Click to expand...
Click to collapse
Hello once more
I just want to clarify two thing first.First, I was a little bit confused on the first reply I did. I was able to use the fastboot commands again because I used the bootloader.bin file not because the device uncharged ok? xD I made some confusion on that issue. Secondly, yes I bealive I flashed a rom only prepared for a 4.2 bootloader when I had the first jb bootlader installed (4.1 I believe). And thats what bricked my tablet.
I'm so sorry if I confused you, like I said earlier, I didn't use to understand a lot of android slag and definitions so I screwed up.
Yes I bealive it's a ICS bootloader. I'll do the proc once more and check the information on the bootloader screen and I'll let you know right away.
pjc21 said:
Ok from what I understand the fastboot flash brick is caused by flashing a non-4.2 version of twrp or any version of cwm on a 4.2 bootloader, but as this was not the case for you I'm not sure of why you were unable to flash via fastboot until the tab had been drained and then recharged. Sounds like similar symptoms to the fastboot flash brick but I don't think people with the fastboot flash brick are able to flash at all even after the tab has drained and been recharged.
I have not heard of anyone with the fastboot flash brick (caused by above situation) unbricking there tab with the fix you tried in the above post.
However you seem to be in a different situation - the fix you tried in your post above, I believe will flash the bootloader bin file from the fisrt ICS firmware 9.4.3.29 which I thought could not be done if you have already upgraded to a JB bootloader.
When you first flashed the bootloader.bin did you happen to take note if your bootloader had changed to 9.4.3.29?
The reason I ask this is that I have tried before to downgrade from JB to an ICS bootloader and had no luck here, I would always get a "signature mismatch" trying to go from JB to ICS - but you appear to be getting this when flashing a JB bootloader. So now thinking this may be the first breakthrough in a way to downgrade from JB to ICS.
Your device is showing that you are now on the last JB 4.1 bootloader (10.4.2.20), so first I would try and flash the system blob for 10.4.2.20 again and see if that fixes the "signature mismatch" issue.
If not I have a thoery that may or maynot work, as you are getting this "signature mismatch" issue (after flashing the bootloader.bin for ICS) when you flash a JB bootloader. You could try (at your own risk) again flashing the ICS bootloader.bin from your above post, then reboot to bootloader and check what bootloader version you then have. If your bootloader is now saying 9.4.3.29 you could then try flashing the system blob from firmware 9.4.3.29 and see if the signature mismatch issue is fixed. If so you should then be able to flash a system blob from a JB firmware.
Not sure if the above will work but try flash the JB system blob from 10.4.2.20 first and if that does not work it's up to you if you would like to try the second.
If you need a step-by-step on how to do any of this or are unsure of anything above just let me know.
Click to expand...
Click to collapse
I fastboot installed the bootloader.bin but I still have the following information on my bootloader: Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.4.2.20-20121228" A03.
Should I proced and install a ICS firmware like WW_epaduser9_4_3_30UpdateLauncher, TWRP for ICS and then flash the WW_epaduser9_4_3_30UpdateLauncher.zip from my ext-sd card?
absinto10 said:
I fastboot installed the bootloader.bin but I still have the following information on my bootloader: Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.4.2.20-20121228" A03.
Should I proced and install a ICS firmware like WW_epaduser9_4_3_30UpdateLauncher, TWRP for ICS and then flash the WW_epaduser9_4_3_30UpdateLauncher.zip from my ext-sd card?
Click to expand...
Click to collapse
No if the bootloader is showing 10.4.2.20 then the bootloader.bin did not flash to the tab.
Did you try flash the system blob from 10.4.2.20 again?
If yes and it did not fix the mismatch issue and bootloop then maybe you could try flashing system blob from a 4.2 firmware like 10.6.1.15.3 and see if that works
pjc21 said:
No if the bootloader is showing 10.4.2.20 then the bootloader.bin did not flash to the tab.
Did you try flash the system blob from 10.4.2.20 again?
If yes and it did not fix the mismatch issue and bootloop then maybe you could try flashing system blob from a 4.2 firmware like 10.6.1.15.3 and see if that works
Click to expand...
Click to collapse
Thank you so much my friend, we've done it, she liveeeeeeesss!!
Flashing system blob from 10.4.2.20 wasn't working. Even though, signatures were matching the bootloop started again.
So I decided following your second advice flashing system blob from a 4.2 firmware, but insted using 10.6.1.15.3, I used "TF300T-WW_epad-user-10_6_1_8UpdateLauncher". Then installed Twrp (openrecovery-twrp-2.4.4.0-tf300t-4.2.blob) and did the following steps of your tutorial (wipe/flash rom) and voila, it booted .
So let me see if I got this straight, currently I have 10_6_1_8 bootloader and 4.2.1 android right? So I can flash this rom for example:
[ROM]★●[TF300T/G/201/301][CROMi-Xenogenesis 4.6.6][ODEX/DEODEX 10.6.1.15.3]
Rom Link: http://forum.xda-developers.com/showthread.php?t=2204166
Thank you so much man!! You saved my little tablet xD
The best regards from Portugal,
Absinto10
absinto10 said:
Thank you so much my friend, we've done it, she liveeeeeeesss!!
Flashing system blob from 10.4.2.20 wasn't working. Even though, signatures were matching the bootloop started again.
So I decided following your second advice flashing system blob from a 4.2 firmware, but insted using 10.6.1.15.3, I used "TF300T-WW_epad-user-10_6_1_8UpdateLauncher". Then installed Twrp (openrecovery-twrp-2.4.4.0-tf300t-4.2.blob) and did the following steps of your tutorial (wipe/flash rom) and voila, it booted .
So let me see if I got this straight, currently I have 10_6_1_8 bootloader and 4.2.1 android right? So I can flash this rom for example:
[ROM]★●[TF300T/G/201/301][CROMi-Xenogenesis 4.6.6][ODEX/DEODEX 10.6.1.15.3]
Rom Link: http://forum.xda-developers.com/showthread.php?t=2204166
Thank you so much man!! You saved my little tablet xD
The best regards from Portugal,
Absinto10
Click to expand...
Click to collapse
Glad you got it working and happy to help. :good:
Yes with your current setup (4.2 bootloader & 4.2 twrp) you can flash CROMi-X 4.6.6
I open this topic because I need your help. I am trying to raise the n9005 filter 4.2.2 that recently.
In all cooked roms, say that you have to put first one to raise the stock bootloader mainly checking in odin "phone bootloader update". After starting, transferring the modified 4.2.2 rom, cwm to install a kikat and then make the appropriate wipes and install the new rom.
In my case I follow the process but when I install the official 4.2.2 rom does not start in the terminal. I thought the problem may be in the bootloader, but no. This marado with odin.
I tried to mater also recently leaked official rom with odin all parameters including the BL. And nothing.
Any idea?
Hi,
I have a UK Moto G (2013) running 4.4.4 KitKat and I installed CWM recovery and rooted it some time ago. Now they are pushing out Lollipop OTA I am getting nagged by the phone to update - but, it always fails when I try. Presumably this will be because of the CWM and/or root. I tried a full unroot but that didn't help as CWM kept complaining on the upgrade reboot about something (can't remember what now!). I've read that in order to get the OTA update to work, I have to get the phone completely back to stock, but I can't find a working stock recovery for it. Do I have to take it back to stock or not ? Either way, would anyone know how I can get the OTA update to work please ?
I've tried flashing a couple of stock recoveries, but one fails to flash at all and the other doesn't work - you choose recovery and it just reboots the phone.
At the moment it's back to rooted, unlocked bootloader and CWM recovery.
Any help you could offer would be very gratefully received.
Thanks!
Are you able to locate the phone's from here: http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=filename&order=ASC&show=100&page=1