Develop Bugs

[ODIN] ICL53F (no wipe, no recovery, no bootloaders)

Here is the stripped version of ICL53F.
FLASH AT YOUR OWN RISK
Changelogs are not fully known yet, but I do know this is Android 4.0.2 and USB host is now working
Stripped meaning no bootloaders, no recovery (so you keep your current CWM), and no wipe (so you keep your data).
IMPORTANT: No wipe is only if your device has been previously OEM unlocked. If your device is NOT OEM unlocked, this WILL wipe your data !
It does include kernel, system and modem, and it's an ODIN tar because ... just because !
YAKJU (GSM): http://www.multiupload.com/7C78MDUQG9
MYSID (LTE): http://www.multiupload.com/3ZZ79I7057
In doubt which one you want ? ADB the following commands:
adb shell getprop ro.product.name
adb shell getprop ro.build.description
adb shell getprop ro.build.fingerprint
The full original Google images can be found here:
http://groups.google.com/group/android-building/msg/2cd2b16ed56a7e84
ODIN ?!
The (Windows) software is attached. USE THE ATTACHED VERSION. DO NOT USE AN OLDER VERSION. A lot of you will be familiar with ODIN from other Samsung devices... well, it works exactly the same on this device.
Turn off your device, turn it on again by holding volume-down and power to enter ODIN download mode.
Launch the ODIN software, press the PDA button and select the .tar file you extracted from the .zip file you downloaded.
Make sure in the ODIN program "Re-Partition", "Phone EFS Clear", and "Phone Bootloader Update" are NOT checked.
Connect the Android device with your computer and you should see a yellow box in the ODIN program. Press the "Start" button, wait a minute or so, and your device will be booted with this firmware.
Also see the attached image, which has every box you need to look at circled in red

For both GSM and LTE compatibility ? ?

Nice !
Could you please tell me how to use it with Odin (used to use Odin with SII or Ace but not with Nexus version..)
Thanks for your explanations

imfloflo said:
For both GSM and LTE compatibility ? ?
Click to expand...
Click to collapse
Yeah there are two separate links in OP. One for GSM, and one for LTE.

@zephiK after OP edited #1 i found my answer thanks
@Chainfire can you add the mac OSX step by step too plz.
Thanks for sharing this

Hi Chain fire
First of all its nice to see you on the Nexus section. Don't know what I would have down without your fantastic rooted kernels on the SGS2.
Do you loose root and boot loader is locked again if you flash this 53F?
Sent from my Galaxy Nexus using xda premium

OP update now with Odin & how to answers my request,
Thank you

Hey Chainfire good to see you here!
I heard that the new bootloader might solve the charging issue...can you confirm?
Also really would like to see cf-root kernels...used them alot on my sgs1 and sgs2...always the best kernels for me.
Good to see Odin is back too...its the best thing to use to flash youre phone
Sent from my Galaxy Nexus using xda premium

Any chance that I can flash it on to yakjuux and have no problems?

imfloflo said:
@zephiK after OP edited #1 i found my answer thanks
@Chainfire can you add the mac OSX step by step too plz.
Thanks for sharing this
Click to expand...
Click to collapse
I have no idea what the steps are on Mac OSX.
schrickm5 said:
Hi Chain fire
First of all its nice to see you on the Nexus section. Don't know what I would have down without your fantastic rooted kernels on the SGS2.
Do you loose root and boot loader is locked again if you flash this 53F?
Click to expand...
Click to collapse
You will lose root. If you have CWM recovery installed you can just flash a Superuser package through recovery, as CWM is not overwritten by this flash.
This flash does not include bootloaders, and will not re-lock your bootloaders.
(It even appears ODIN will unlock your bootloader if it was locked)
D_Magic said:
Hey Chainfire good to see you here!
I heard that the new bootloader might solve the charging issue...can you confirm?
Also really would like to see cf-root kernels...used them alot on my sgs1 and sgs2...always the best kernels for me
Click to expand...
Click to collapse
Can't confirm because I don't know. I have only had the charging issue when using custom kernels, the stock kernel had no issue for me.
Not sure if I will release a CF-Root... as this device has a separate recovery partition, there is not that much need for CF-Root... It's still handy though, of course.
Should the bootloaders prove needed and/or helpful, I will release a separate bootloader package so you can flash those later.

AfzalivE said:
Any chance that I can flash it on to yakjuux and have no problems?
Click to expand...
Click to collapse
Nobody knows.
To be fair, I don't even know which model I have. I flashed the Google provided stock image of ITL41F within an hour of getting my Nexus last week, due to soft-bricking it (yeah, that quick).
It may work, it may not.

Chainfire said:
Nobody knows.
To be fair, I don't even know which model I have. I flashed the Google provided stock image of ITL41F within an hour of getting my Nexus last week, due to soft-bricking it (yeah, that quick).
It may work, it may not.
Click to expand...
Click to collapse
Alright then, I'll just flash the provided ICL53F images then...just to switch over to yakju.

Nice to see you here Chainfire. Thanks for this, I will flash it now as I'm looking for a stock ROM, or just stock in its own. I find custom ROM's cause too much battery drain with all the features that are adding.

Chainfire said:
Should the bootloaders prove needed and/or helpful, I will release a separate bootloader package so you can flash those later.
Click to expand...
Click to collapse
Thanks but it turns out the new bootloader doesn't fix the issue
So if i flash this with odin then i keep the unlocked bootloader and cwm but i loose root....what do you mean with flash a superuser package? ( i wanna go back to stock for now cause on every custom rom/kernel i get a really bad battery drain )
Sent from my Galaxy Nexus using xda premium

D_Magic said:
Thanks but it turns out the new bootloader doesn't fix the issue
So if i flash this with odin then i keep the unlocked bootloader and cwm but i loose root....what do you mean with flash a superuser package? ( i wanna go back to stock for now cause on every custom rom/kernel i get a really bad battery drain )
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Maybe the new bootloader fixes the RF interference (debounce time) on the volume buttons (that was only patched in the kernel in the last update)?
I guess someone who lives in a region that had that problem would have to check.

Here are the changes from 4.0.1 --> 4.0.2
Device features
Optimized Mobile Hotspot when used with VPN
Optimized 3G/4G data sessions for faster response times
Fixed an incorrect notification that “data was disconnected due to roaming”
WiFi now automatically reconnects when returning to a known Access Point
Improvements to special visual effects feature when using front-facing camcorder
Visual improvements to the lock screen
Email and Messaging
Fixed an issue where some email attachments would not open correctly
Apps and Widgets
DivX support has been removed and will be supported in a future upgrade
Improved audio volume in Google navigation turn-by-turn directions

Anyone know if I can use this tar file with Heimdall?

madj42 said:
Anyone know if I can use this tar file with Heimdall?
Click to expand...
Click to collapse
Don't know for sure, but I don't see why not ...

Chainfire said:
mysid variant has not been tested by me. Please let me know if the radio flashes properly... if not I'll update the package.
Click to expand...
Click to collapse
Radio flashed flawlessly here

Did anyone of you get the Update ota? On the gsm nexus?

[Q] Revert to stock without USB

I have been having issues with my phone not charging and being recognized in my PC. I have tried everything I can think of to fix it without success. At this point I need to send it back to Verizon, but I am currently running AOKP. So I need to revert it back to stock before I can send it.
Since the phone is not being recognized, ADB is not an option. I have tried using Mobile Odin Pro, but with v3.45 and 3.50, I get this error when I try to flash the factory image from Google: "An error occurred extracting the update script"
Any ideas how I can revert back to stock?

There ARE other ways to do it. Read the stickies.
For odin, you need compatible images with ODIN, which is not supported by Google/Samsung (just be reminded of that); the ones we get from Google are to be flashed with fastboot.
Quick tip: i believe you need to relock bootloader with the app before going back to stock completely (since you'll loose root).
Sent from my i9250

I looked at all the stickies, and I can't find anything. Am i just missing it?

this may be a shot in the dark but I had a problem with my usb port not working on my gsm gnex, and thought i needed to send it in to sammy. Then i found a thread where a guy talked about pushing the tip of a razer blade(carefully) in between the tab in the middle of the usb port and the rear of phone. I tried it and since have had no charging problems. As a matter of fact I had forgotten about it until reading this thread.
Or mabye someone with a verizon gnex can upload a stock nandroid for you. As for bootloader unlocked..

3oudreaux said:
this may be a shot in the dark but I had a problem with my usb port not working on my gsm gnex, and thought i needed to send it in to sammy. Then i found a thread where a guy talked about pushing the tip of a razer blade(carefully) in between the tab in the middle of the usb port and the rear of phone. I tried it and since have had no charging problems. As a matter of fact I had forgotten about it until reading this thread.
Or mabye someone with a verizon gnex can upload a stock nandroid for you. As for bootloader unlocked..
Click to expand...
Click to collapse
This could be. Worth a shot, IMO.
zeppelin_one said:
I looked at all the stickies, and I can't find anything. Am i just missing it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1731993

Really, all you need is flashable radio image, flashable bootloader image, stock zip file from Google, and custom recovery (such as Clockworkmod or twrp)
Swyped on my Galaxy Nexus running AOKP with Franco Kernel

kyokeun1234 said:
Really, all you need is flashable radio image, flashable bootloader image, stock zip file from Google, and custom recovery (such as Clockworkmod or twrp)
Swyped on my Galaxy Nexus running AOKP with Franco Kernel
Click to expand...
Click to collapse
Have you read the thread...? Op is trying to return the device, bad usb port.
Sent from my i9250

Restore factory (unroot, stock recovery) without USB connection
I've read through all the threads that I can find on this an other forums regarding this challenge. Basically I have an locked bootloader rooted Galaxy Nexux Toro that has a slightly tweeked rooted JRO03O system and the Jelly Bean bootloader.
I want to restore stock recovery and stock system but the USB port is totally fried. (It actually smoked last time I plugged it in).
I have Odin Mobile Pro downloaded and a tarball for 4.0.4 (VzW-PDA-ODIN-I515EL03_ICL53F_signed.tar) ready to inject using ODIN. However I'm afraid to go ahead with this because I've read that ICS can't handle the Jelly Bean bootloader that is on my phone. As far as I see it I have 4 options:
1. Go ahead and flash the ICS tarball and hope that it works with the JB bootloader but potentially be screwed if it messes up the recovery partition with no way to reflash it as I have no USB.
2. Use the tarball that was in the google release mysid-jro03o-factory-f17426e6.tgz that the toolkit extracted when it unpacked the tgz (it's called mysid-jro03o-factory-f17426e6.tar and the toolkit pulled it from the tgz along with the zip and all the other bits and pieces)
4. Flash the tarball that I created using the GNex toolkit (Wug's) that I made using the img files for system, recovery, kernel and userdata that I pulled out of mysid-jro03o-factory-f17426e6.tgz after allowing the toolkit to unpack the TGZ
4. Try and reflash the ICS bootloader and hope the phone reboots ok into my current ROM and allows me to flash the ICF53F tarball using ODIN.
Any advice on which of these options (or another not listed) stands the best chance of success from those more knowledgeable would be greatly appreciated.
Thanks!

juscoll said:
that ICS can't handle the Jelly Bean bootloader that is on my phone.
Click to expand...
Click to collapse
True, only earlier versions support older bootloaders, not the other way round. Some of it could work, maybe doesnt boot at all (it may be a bit extreme for the device not to, but maybe there's the chance.)
juscoll said:
4. Try and reflash the ICS bootloader and hope the phone reboots ok into my current ROM and allows me to flash the ICF53F tarball using ODIN.
Click to expand...
Click to collapse
Not sure how to flash ICS bootloader on the phone... I assume you're relying on Odin Mobile for this task? Anyways, if you manage to do it, then go ahead and use odin again to restore to factory.
juscoll said:
Any advice on which of these options (or another not listed) stands the best chance of success from those more knowledgeable would be greatly appreciated.
Thanks!
Click to expand...
Click to collapse
Yes, just return the device. Its got a freaking bad usb port. Even if they can see you modded the rom/updated system etc, and they give you trouble, just ask them to restore the device to its factory state, without USB!! "It's a developers phone people!!!" Personally, i think they will only look at unlocked/locked boot screen.
Sent from my i9250

Can't get 4.2 OTA on Yakju Gnex, help please, going mad!

Hi all,
I'm new here so please go easy on me. I've had my Gnex for about 4 months now, and totally love it. But right now I'm still waiting for 4.2 or 4.2.1 to turn up, and getting increasingly annoyed with it's no show.
I've tries checking for the OTA update, and I've tried deleting the Google Services Framework Data to kick start it, but so far, still no update.
Last night I tried sideloading the update using ADB on Mac OSX and a ROM I downloaded from Google. After slowly figuring out what I was doing I managed to get the update to transfer via ADB but then for some reason I kept getting "Installation Aborted" reported on the Screen of my Gnex.
I'm losing it now. I have 4.2.1 on my Nexus 7 and love it, and I really wish my Gnex was in sync, features wise. But the update just isn't showing up.
It's a Yakju international Gnex, I'm in the UK on O2 network. Previous OS updates have come through as they should (on 4.1.1 now, never got 4.1.2) but I just can't get 4.2 on there.
Any help would be hugely welcomed, thanks a lot.

Download the factory image from here: https://developers.google.com/android/nexus/images#takjujop40d
Just flash that manually and you will be on stock Android 4.2.1 for Galaxy Nexus Yakju.

That's what I said I did and it reported "Installation Aborted" any ideas why that happened? I tried numerous times.

davidpye said:
That's what I said I did and it reported "Installation Aborted" any ideas why that happened? I tried numerous times.
Click to expand...
Click to collapse
No, you tried the OTA update. The link I gave contains the full factory image (system,data,kernel,recovery etc).
You need fastboot to flash it.

Aerys said:
No, you tried the OTA update. The link I gave contains the full factory image (system,data,kernel,recovery etc).
You need fastboot to flash it.
Click to expand...
Click to collapse
No, I downloaded the 4.2.1 ROM you linked to and use ADB to Side load it. Is that the wrong way to do it?

davidpye said:
Is that the wrong way to do it?
Click to expand...
Click to collapse
Yes.
Aerys said:
... You need fastboot to flash it.
Click to expand...
Click to collapse
Follow these instructions to flash the factory image: http://forum.xda-developers.com/showthread.php?t=1626895

Hi,
I followed those instructions to a T, I get to:
"9) Flash the system partition: fastboot flash system system.img"
And the commands no longer do anything, they just report "File Not Found" or words to that effect.
I do appear to have unlocked the Bootloader, but still the update will not install when I sideload with ADB.
What am I doing wrong?
gokpog said:
Yes.
Follow these instructions to flash the factory image: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse

I've just tried sideloading these images from this thread: http://forum.xda-developers.com/showthread.php?t=1419170
yakju JZO54K from JRO03C
yakju JOP40C from JZO54K
and
yakju JOP40D from JOP40C
and all report "Installation Aborted".

what version are you even on?

I said in my first post, 4.1.1.
I think I'm getting somewhere now, I know no one is likely to care that much, but the single thing that makes this so hard for a n00b like me is that there are so many different sites with conflicting or differing information on how to do this, some say use ADB, some say use CWM (which is what I'm doing now). NONE explain even briefly what these things are.
Anyway, I'll let you know how I get on now, using CWM to install the OTA updates in order.

the smartest thing u can do is get galaxy nexus toolkit 10.1.0 for your Mac. It will allow you to flash whichever factory image u want and also unlock your bootloader and root your phone if you want. You can find a thread for the tool kit on xda itself. My friend and I did this to update to 4.2 the day it released. If it helps please press the thanks button.
Sent from my Galaxy Nexus using xda premium

[email protected] said:
the smartest thing u can do is get galaxy nexus toolkit 10.1.0 for your Mac. It will allow you to flash whichever factory image u want and also unlock your bootloader and root your phone if you want. You can find a thread for the tool kit on xda itself. My friend and I did this to update to 4.2 the day it released. If it helps please press the thanks button.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
good. god. no.
dont use a toolkit.

So I just tried using CWM to install the JRO03C -> JZO54K, and I get this error:
asset failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/yakju/maguro:4.1.1/JRO03C/398337:user/release-keys" || file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/yakju/maguro"4.1.2'JZ054K/485486:user/release-keys"
E: Erros in /sdcard/----- filename.zip ------
(Status 7)
Installation Aborted

Using a toolkit is very inviting when I know nothing about what I'm doing and no one appears to be able to help.
Why should I NOT use a toolkit.

are you sure you're on yakju and downloading the OTA update to yakju?
did you previously root your phone and modify anything?

Zepius said:
are you sure you're on yakju and downloading the OTA update to yakju?
did you previously root your phone and modify anything?
Click to expand...
Click to collapse
No I've never rooted it (I think my lack of knowledge here proves I'd be unlikely to manage that myself) it's a Yakju phone, running JRO03C for sure, its what it says on the screen.
Anyway, I THINK I'm managing to get the Fastbook Flash technique working now. I hadn't fully unzipped the Image for 4.2, now I have and have the system.img files etc to work with.
I'll let you know how I get on.

davidpye said:
No I've never rooted it (I think my lack of knowledge here proves I'd be unlikely to manage that myself) it's a Yakju phone, running JRO03C for sure, its what it says on the screen.
Anyway, I THINK I'm managing to get the Fastbook Flash technique working now. I hadn't fully unzipped the Image for 4.2, now I have and have the system.img files etc to work with.
I'll let you know how I get on.
Click to expand...
Click to collapse
YES! I've done it.
I managed to flash using the Fastboot method, my mistake was not fully unzipping the .zip I downloaded from Google, I had got confused with the ADB route for sideloading the device and didn't realise the Fastbook method required full unzipping the file.
Thanks all of you who helped me, sorry for being such a confused noob!
Dave

davidpye said:
YES! I've done it.
I managed to flash using the Fastboot method, my mistake was not fully unzipping the .zip I downloaded from Google, I had got confused with the ADB route for sideloading the device and didn't realise the Fastbook method required full unzipping the file.
Thanks all of you who helped me, sorry for being such a confused noob!
Dave
Click to expand...
Click to collapse
at least you've managed to flash it// i got confused and decided to wait for ota.

Why would you say don't use a toolkit? It is really easy and does everything for you I rooted my phone with it.
Sent from my Galaxy Nexus using xda premium

davidpye said:
YES! I've done it.
I managed to flash using the Fastboot method, my mistake was not fully unzipping the .zip I downloaded from Google, I had got confused with the ADB route for sideloading the device and didn't realise the Fastbook method required full unzipping the file.
Thanks all of you who helped me, sorry for being such a confused noob!
Dave
Click to expand...
Click to collapse
Now, if you look back on the procedure you did with fastboot... you know how to restore your device to factory state, step by step. No toolkits, no scripts.
Sent from my i9250

[Q] Can I realy just flash to CM10.1 or do I still need to root first?

I've been reading these forums in my spare time for the last week or so but I'm still a bit confused or just overlooking something. According to the CM 10.1 thread install instructions are
Install instructions:
1. Install ClockworkMod Recovery for "I927". Sorry, CM cannot provide support for other recoveries, although they may work fine.
3. Reboot into recovery and install
Click to expand...
Click to collapse
and a few people in some of the guide threads have basically stated the same. Is it really this simple now or do I still need to follow the guide from a year ago or the one in this thread http://forum.xda-developers.com/showthread.php?t=1962633 ?
So far all I have done is install CWMR Touch 6.0.1.2 Recovery and run backup in both blob and tar formats. Actually does this even work properly without rooting first?

You don't need root, but you can't quite go straight either. The current SOP is:
Flash TW-ICS, meaning UCLG9 or UCLH2 or UCLJ3, using the respective OneClick
Flash CWMR using Odin (the previous step overwrites recovery so you will have to do this again even if you flashed CWM previously)
Boot into CWM
Flash your AOSP-JB ROM of choice
Flash the correct gapps for your ROM
Format /data (aka factory reset)
Reboot into ROM and enjoy
Step 1 may or may not be necessary -- nobody's tried going from TW-GB straight to AOSP-JB yet. If you're feeling adventurous, try it and let us know how it goes.
Once you've flashed a TW-ICS once, you won't need to do it again -- at that point flashing a new TW-ICS or AOSP-JB ROM is as simple as flash-format-boot.

Thanks for the updated info, I didn't think it would be that simple.
Not sure what TW stands for since I haven't seen that abbreviation yet.
But basically for step one I can grab the UCLG9 from this thread http://forum.xda-developers.com/showthread.php?t=1841502
and flash it with CWM and then follow on from step 2? Or would I be better off grabbing the newer UCLJ3 from SamMobile and using Odin?

Bram Skull said:
Thanks for the updated info, I didn't think it would be that simple.
Not sure what TW stands for since I haven't seen that abbreviation yet.
But basically for step one I can grab the UCLG9 from this thread http://forum.xda-developers.com/showthread.php?t=1841502
and flash it with CWM and then follow on from step 2? Or would I be better off grabbing the newer UCLJ3 from SamMobile and using Odin?
Click to expand...
Click to collapse
Nope no zips or Odin just use one click the first time. So for step 1 above follow this http://www.theandroidsoul.com/android-4-0-4-ice-cream-sandwich-update-for-att-captivate-glide-i927uclg9/. Can't get easier then this.

Bram Skull said:
Thanks for the updated info, I didn't think it would be that simple.
Not sure what TW stands for since I haven't seen that abbreviation yet.
Click to expand...
Click to collapse
TW == TouchWiz. Basically official Samsung stuff and ROMs based directly on such.
But basically for step one I can grab the UCLG9 from this thread http://forum.xda-developers.com/showthread.php?t=1841502
and flash it with CWM and then follow on from step 2? Or would I be better off grabbing the newer UCLJ3 from SamMobile and using Odin?
Click to expand...
Click to collapse
I would get the full EXE, just to be sure. The CWM zips generally don't include bootloader or baseband and that's the important stuff.

I would get the full EXE, just to be sure. The CWM zips generally don't include bootloader or baseband and that's the important stuff.
Click to expand...
Click to collapse
I used the CWM flash and can confirm the no updated baseband since it still had the stock Rogers one on AT&T-ICS and in CM-10.1. Not sure about ICS but in CM-10.1 I could get voice but no data and haven't tested txt.
Going to flash back to stock with the backup I made for now while I research solutions to a few personal gripes I have with CM-10.1.
And would the UCLJ3 from SamMobile with odin or kies be as effective as the EXE version since I already have it downloaded?
Thanks for helping a total noob and to be honest this is my first Android phone.

Bram Skull said:
I used the CWM flash and can confirm the no updated baseband since it still had the stock Rogers one on AT&T-ICS and in CM-10.1. Not sure about ICS but in CM-10.1 I could get voice but no data and haven't tested txt.
Going to flash back to stock with the backup I made for now while I research solutions to a few personal gripes I have with CM-10.1.
And would the UCLJ3 from SamMobile with odin or kies be as effective as the EXE version since I already have it downloaded?
Thanks for helping a total noob and to be honest this is my first Android phone.
Click to expand...
Click to collapse
I just took a peek... ooh. Looks like pretty much everything is in there. You should be good.

Can't power up my phone

Hi guys, please help me
I was trying to flash my S3 tmobile with CM 11, but I got an error "assert failed: getprop("ro.bootloader")"
I search on xda and flash the bootloader then I turn off the phone.
Now I cannot power up my phone, can't get into recovery mode or anything.

westlife2206 said:
Hi guys, please help me
I was trying to flash my S3 tmobile with CM 11, but I got an error "assert failed: getprop("ro.bootloader")"
I search on xda and flash the bootloader then I turn off the phone.
Now I cannot power up my phone, can't get into recovery mode or anything.
Click to expand...
Click to collapse
What Firmware were you running before you flashed CM 11?

FcHsChilD said:
What Firmware were you running before you flashed CM 11?
Click to expand...
Click to collapse
I don't remember. Before flashing CM 11, I didn't touch anything except rooting it by using this guide on android central (sorry, I can't post the link)
I think it will be the original

What exactly did ypu you flash? You can copy the link on your post, just put a few spaces in it. I have a feeling I know what happened but I cant be certain without knowing exactly what you flashed.
Did you ever update by taking any of the OTA's?

DocHoliday77 said:
What exactly did ypu you flash? You can copy the link on your post, just put a few spaces in it. I have a feeling I know what happened but I cant be certain without knowing exactly what you flashed.
Did you ever update by taking any of the OTA's?
Click to expand...
Click to collapse
Yes I did update to 4.3 from T-mobile OTA
I rooted though this guide http://androidcentral .us/2014/04/root-t-mobile-samsung-galaxy-s3/
I flash this firmware http://forum .xda-developers.com/showthread.php?t=2282603

westlife2206 said:
Hi guys, please help me
I was trying to flash my S3 tmobile with CM 11, but I got an error "assert failed: getprop("ro.bootloader")"
I search on xda and flash the bootloader then I turn off the phone.
Now I cannot power up my phone, can't get into recovery mode or anything.
Click to expand...
Click to collapse
westlife2206 said:
Yes I did update to 4.3 from T-mobile OTA
I rooted though this guide http://androidcentral .us/2014/04/root-t-mobile-samsung-galaxy-s3/
I flash this firmware http://forum .xda-developers.com/showthread.php?t=2282603
Click to expand...
Click to collapse
I don't consider myself an expert but did you read that post for what you flashed and how it says in big bold red letters DO NOT flash this if you are running latest 4.3.If I can make any assumptions on it you bricked due to flashing a previous bootloader(Doc correct me if I'm wrong..still learning)

Yup. If you flash those MD5 bootloaders on 4.3 you're bricked. You'll need to use the debrick thread stickied in development.

Okay thank you, I will try this thread http://forum.xda-developers.com/showthread.php?t=2439367
Btw, how can I fix the error "assert failed: getprop("ro.bootloader")" ?

You first need to know what firmware build you are on. Then edit the updater-script and replace one of the ones listed in the assert lines with yours.
Use caution though. There are reasons for these and only fo this if you are 100% certain it is safe to flash.