Database Users

[WARNING] Do not downgrade to 1.0xxxxx after root.

I should of published this notice sooner. This was discussed early on, but we didn't think anyone would downgrade to the buggy firmware after rooting.
We were wrong.
Newer hboots (like the one in stock, hboot version 1.04.0000) flash/check images in an way that prevents the phone from encountering a SECURITY WARNING mid flash. This is good, prevents us from bricking.
Older hboots, like the one in 1.03.605.10 (hboot version 0.95.0000) on the otherhand do not, and flashing over custom firmware with them can lead to the dreaded SECURITY WARNING. This firmware is from January 3rd, is buggy and well should not be used for any reason outside of initail root. Avoid it.
A tester helping develop a one click root encountered this today, he tried to downgrade from custom firmware.
So, do not downgrade below 1.12.605.6 without a reason, if you do understand how to recover. You most likely have no reason to be on old firmware at this point, outside of initial root.
If you have a SECURITY WARNING, don't freak.
Recovering from this error:
Until we have newer RUUs, you only have one maybe two chances to do this. Since you obviously know how to flash an RUU, I am not going to go through the
process again.
Flashing this firmware the stock (1.12.605.6) firmware will fix this error.
LINK: http://www.multiupload.com/JWLPZAS15T
However if you get a MAIN VERSION HIGHER error while flashing, you only have one choice to recover, by flashing the newer than stock (1.12.605.9) firmware.
LINK: http://www.multiupload.com/UF40S2HZA7
If you are having issues, or are freaked out come find me in the chat (check my signature for a link). If I help you, I expect a donation to the Boys and Girls Club in the name of REWT.
-jcase
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

bumpity bump!

hello there i got the exact thing on my TB and i downloaded the files to fix it but i get back a Main Version Older am i doin somethin wrong

you can only flash files that are newer than your firmware. what were you trying to flash,overtop of what, when you got this security warning?

scotty1223 said:
you can only flash files that are newer than your firmware. what were you trying to flash,overtop of what, when you got this security warning?
Click to expand...
Click to collapse
i was trying to flash this [ROM][TH3ORYROM] SHIFTAO5P V1.2X [AOSP/CM7] Eclipse B5 Kernel (8/26/2011) but when i was trying to flash the radio, i wasnt getting any receptions and i tried all four radio listed, so my stupid self thinkin hey let me use the radio PM05IMG from the root process and see if that would work, well as soon as the bootloader started flashin the files it pop back into bootloader with the security warning, i tried the file the jcase said to use to get out of that problem but the file never open or go thru it come back saying Main Version Older file not updated.

"Main version higher" means that the firmware you're trying to flash is older than the firmware on the phone.
Have you tried both files above? If so,the next thing I would do is try and flash the mr2 ruu(1.70.605.0) it is newer than both files above,and both of the root files(downgrade and mr1 upgrade) so that one should work for you.
Afterward,you can run revolutionary to reroot and not encounter this prollem again when you flash something that you should have researched more before flashing.
Sent from my SHIFTAO5P using XDA Premium App

scotty1223 said:
"Main version higher" means that the firmware you're trying to flash is older than the firmware on the phone.
Have you tried both files above? If so,the next thing I would do is try and flash the mr2 ruu(1.70.605.0) it is newer than both files above,and both of the root files(downgrade and mr1 upgrade) so that one should work for you.
Afterward,you can run revolutionary to reroot and not encounter this prollem again when you flash something that you should have researched more before flashing.
Sent from my SHIFTAO5P using XDA Premium App
Click to expand...
Click to collapse
Hey there Scotty i really appreciate you helping me out here, im sitting at work with my TB stuck in Bootloader, getting ready to bust out my old rooted Eris out, but ima go and try that MR2 RUU do you have a link to where i can download that. and also where you said Main Version Higher mines Said Main Version Older,
and yes i thought i did everything correctly i mean i guess since i had the rom flashed but wasnt getting any reception made me make the stupid mistakes, by the way scotty do you have a tb

i have never seen "main version older" but it means the same thing... the firmware youre trying to flash is older that what is on the phone.
you can download MR2 from here: http://forum.xda-developers.com/showthread.php?t=1160286
just put your sd card in a cardreader to transfer and rename PG05IMG and flash in hboot. let us know how it goes.
and yes,i have a TB.

scotty1223 said:
i have never seen "main version older" but it means the same thing... the firmware youre trying to flash is older that what is on the phone.
you can download MR2 from here: http://forum.xda-developers.com/showthread.php?t=1160286
just put your sd card in a cardreader to transfer and rename PG05IMG and flash in hboot. let us know how it goes.
and yes,i have a TB.
Click to expand...
Click to collapse
Ok ima download it but my other prblem is that the phone doesnt charge the battery its not enough voltage to run the files, i have no other way of charging the phone i might have to buy a battery charger or somethin

only thing i know of is to use an external charger,or swap it into a good TB. if you have to,you could take it to a store and see if they will put it in a phone and charge it for you,tho i would take some care in what you tell them as to why you need to do that
i got an external charger and 3 extra generic batterys on ebay for about $30 so i wont ever ben in that situation. i dont like charging my phone during the day so i just go until it shuts off then put in a new battery.
ive heard of people hacking up usb cables to directly power the phone,but thats not something id really reccomend.
at any rate youre good to be caustious,an hboot flash is NOT a time that you want to run out of battery

take an old pair if headphones and strip them til you have only the cooper wire and connect them to the gold connector from your phone to your eris battery and that should work

scotty1223 said:
only thing i know of is to use an external charger,or swap it into a good TB. if you have to,you could take it to a store and see if they will put it in a phone and charge it for you,tho i would take some care in what you tell them as to why you need to do that
i got an external charger and 3 extra generic batterys on ebay for about $30 so i wont ever ben in that situation. i dont like charging my phone during the day so i just go until it shuts off then put in a new battery.
ive heard of people hacking up usb cables to directly power the phone,but thats not something id really reccomend.
at any rate youre good to be caustious,an hboot flash is NOT a time that you want to run out of battery
Click to expand...
Click to collapse
Ok so today i brought an HTC dock charger with a extra slot to charge the battery alone, so i charge that puppy up, put the battery back in with the file you gave me to put on my sd card and bootloader comes on does its checking the file and loaded the update ask me to press yes and BAM it took 5 mins to do its process and rebooted itself and now back to where it was when i first brought it, damn so thx you Scotty for the help and guide, so can youo tell me a method to use to root it back,

good,glad it worked out for you. use this to reroot: http://revolutionary.io/
its quick and easy and leaves you with a permanet hboot that wont accidentally get overwritten

scotty1223 said:
good,glad it worked out for you. use this to reroot: http://revolutionary.io/
its quick and easy and leaves you with a permanet hboot that wont accidentally get overwritten [/QUOTED]
do i need my pc to do this root process or i can do it on the phone.
Click to expand...
Click to collapse

portebr3 said:
do i need my pc to do this root process or i can do it on the phone.
Click to expand...
Click to collapse
you will need a pc

scotty1223 said:
you will need a pc
Click to expand...
Click to collapse
Ok ill need a pc, how will i know im rooted will it give me the superuser app like the other root method does

theres a video here on android forums: http://androidforums.com/thunderbolt-all-things-root/402115-thunderbolt-rooting-methods-updated.html
it will give you a permanent s-off hboot and flash clockwork recovery. tehre is a download for a superuser.zip that you will flash in recovery. then you will see the superuser app in your drawer after flashing that .zip/

scotty1223 said:
theres a video here on android forums: http://androidforums.com/thunderbolt-all-things-root/402115-thunderbolt-rooting-methods-updated.html
it will give you a permanent s-off hboot and flash clockwork recovery. tehre is a download for a superuser.zip that you will flash in recovery. then you will see the superuser app in your drawer after flashing that .zip/
Click to expand...
Click to collapse
ok Ima go go ahead and go that route and i think i should be able to download superuser from the app store, but yeaha ill keep you posted, so tell me what ROM are you using, i heard gingerbread is buggy as hell,

portebr3 said:
ok Ima go go ahead and go that route and i think i should be able to download superuser from the app store, but yeaha ill keep you posted, so tell me what ROM are you using, i heard gingerbread is buggy as hell,
Click to expand...
Click to collapse
the market will only have the superuser app,youll need the matching binary files. the superuser app is linked on revolutionarys page,you must flash that in recovery to become rooted.
from: the revolutionary website:
Does Revolutionary give me root?
No. You will need to flash this this zipfile from recovery.

jcase said:
I should of published this notice sooner. This was discussed early on, but we didn't think anyone would downgrade to the buggy firmware after rooting.
We were wrong.
Newer hboots (like the one in stock, hboot version 1.04.0000) flash/check images in an way that prevents the phone from encountering a SECURITY WARNING mid flash. This is good, prevents us from bricking.
Older hboots, like the one in 1.03.605.10 (hboot version 0.95.0000) on the otherhand do not, and flashing over custom firmware with them can lead to the dreaded SECURITY WARNING. This firmware is from January 3rd, is buggy and well should not be used for any reason outside of initail root. Avoid it.
A tester helping develop a one click root encountered this today, he tried to downgrade from custom firmware.
So, do not downgrade below 1.12.605.6 without a reason, if you do understand how to recover. You most likely have no reason to be on old firmware at this point, outside of initial root.
If you have a SECURITY WARNING, don't freak.
Recovering from this error:
Until we have newer RUUs, you only have one maybe two chances to do this. Since you obviously know how to flash an RUU, I am not going to go through the
process again.
Flashing this firmware the stock (1.12.605.6) firmware will fix this error.
LINK: http://www.multiupload.com/JWLPZAS15T
However if you get a MAIN VERSION HIGHER error while flashing, you only have one choice to recover, by flashing the newer than stock (1.12.605.9) firmware.
LINK: http://www.multiupload.com/UF40S2HZA7
If you are having issues, or are freaked out come find me in the chat (check my signature for a link). If I help you, I expect a donation to the Boys and Girls Club in the name of REWT.
-jcase
Click to expand...
Click to collapse
all multiupload.com links are non-functional and should be disabled, and refreshed with current mirror links.

[GUIDE] Comprehensive "Rooted Android 2.3.4 with unlocked bootloader" instructions

[GUIDE] Comprehensive "Rooted Android 2.3.4 with unlocked bootloader" instructions
This is a guide on how to go from Froyo to rooted Gingerbread. Also, I'm on AT&T. Others beware. I take no responsibility if you hard or soft brick your phone.
I went from a rooted install running Gingerblur v4.5, but this will likely work regardless of what you have installed, since fastboot overwrites everything.
I didn't actually discover or develop any of this, but I figured someone might like to have a comprehensive guide, instead of searching through 500 different threads like I did.​Known/potential issues:
- Fingerprint scanner not functional False alarm
- Avoid using RSDLite for *anything* if you installed the OTA 2.3.4 build
- Battery reading is sometimes inaccurate
- If you have a limited RAM issue, read here http://forum.xda-developers.com/showthread.php?t=1169409​Step 0 - BACK UP EVERYTHING. Use Titanium backup, or just copy everything off your phone, whatever. This will leave you with an unlocked, rooted, but otherwise stock Motorola phone. Once this is done, set your USB mode to "None"
Step 1 - Install moto drivers
For x64 windows, use these: http://forum.xda-developers.com/attachment.php?attachmentid=634880&d=1308872277
For x32, http://www.multiupload.com/QNFILE4F07 (I havent tested these, I run Win7 x64)
Step 2 - Unlock your bootloader Note: some have hard bricked using RSDLite to install 1.8.3 over 4.5.91. Read warning here: http://forum.xda-developers.com/showthread.php?t=1160408
Download latest moto-fastboot from here: http://forum.xda-developers.com/showthread.php?t=1138092 *the win32 version worked for me, and I run 64bit windows 7*
Follow instructions here: http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
Step 3 - Flash stock Gingerbread image (you can do this without restarting your phone from the unlock bootloader step)
Follow instructions here: http://forum.xda-developers.com/showthread.php?t=1163342
Step 4 - Flash CWM Recovery
Instructions here: http://forum.xda-developers.com/showthread.php?t=1138541
Step 5 - Install root
Instructions here: http://forum.xda-developers.com/showthread.php?t=1159572
Note: I used my phone's USB Mass Storage mode to put the .zip on my external SD card. To get to recovery mode, shut down the phone. Then hold the power and volume up buttons until you see "fastboot." Use the volume down key to cycle through until you see "Android Recovery" then press volume up again. This will get you into the CWM environment, where you can navigate the menus to install the root .zip.
Step 6 - Restore your stuff
Now you should have a factory fresh Gingerbread / MotoBlur installation (didn't you miss the bloat?), with the addition of the superuser app. For tethering, I use Barnacle (requires root). I used Titanium Backup to uninstall any apps I don't want (anything beginning with AT&T, Blockbuster, Y!, etc.) and to reinstall all of my apps.​
Feel free to make any corrections, or ask questions. Hopefully someone finds this useful. All credit to the OP of each thread I linked to.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Nice for you to localize everything, ATT users will be grateful.

I went from a rooted install running Gingerblur v4.5, but this will likely work regardless of what you have installed, since fastboot overwrites everything.
Click to expand...
Click to collapse
Does this include the official 4.5.91? So many warnings about hard bricking since people flashed it.

From what I can tell, hard bricking only occurs when you use RSDLite to flash an older motorola SBF once you've gone to gingerbread. But someone else should chime in on that one - I never got a notice for an OTA update.

humjaba said:
From what I can tell, hard bricking only occurs when you use RSDLite to flash an older motorola SBF once you've gone to gingerbread. But someone else should chime in on that one - I never got a notice for an OTA update.
Click to expand...
Click to collapse
I didn't either. I downloaded a .zip and installed via stock recovery from a thread in the General Atrix forum.

Deggy said:
Does this include the official 4.5.91? So many warnings about hard bricking since people flashed it.
Click to expand...
Click to collapse
Nope, this one is the completely safe one.
Kennethpenn said:
"These are completely safe to flash. They don't mess with your bootloader like the OTA or SBF."
In the thread.

Magnetox said:
Nope, this one is the completely safe one.
Kennethpenn said:
"These are completely safe to flash. They don't mess with your bootloader like the OTA or SBF."
In the thread.
Click to expand...
Click to collapse
Just to clarify. I can NOT proceed to unlock my BL. Is that correct?

Deggy said:
Just to clarify. I can NOT proceed to unlock my BL. Is that correct?
Click to expand...
Click to collapse
What firmware did you flash? Can you link me to the thread you downloaded from?

Magnetox said:
What firmware did you flash? Can you link me to the thread you downloaded from?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1159604

Deggy said:
http://forum.xda-developers.com/showthread.php?t=1159604
Click to expand...
Click to collapse
Ah you have the deadly firmware
You simply cannot use RSD to flash down to 1.83 or 1.26 etc.
Or you will brick.
Clarify in Q&A, make your own thread with your question.
Taken from this thread kennethpenn said:
"What if I already flashed the official 4.5.91?
If you flashed the official update from XDA or by downloading through a dev-blur server (note: this excludes this ROM), you should avoid flashing SBF files in RSD Lite. We've confirmed this problem exists when users flash the 1.8.3 build specifically. It may happen with other SBF files, though."
So it looks like you can flash 2.3.4 builds via CWM. But double check by asking in Q&A.

Check out this thread.
http://forum.xda-developers.com/showthread.php?t=1163009
Fruit cakes basically dont touch your bootloader, they're basically modified sbf files that only contain the needed files to flash stuff. There's a 1.8.3 fruitcake in there as well as a 2.3.4 fruitcake.
An HKTW fruitcake is in development.
Fruitcake is the .sbf equivalent file that is flashable via CWM.

The big question is this - can you RSDflash the unlocked bootloader SBF by itself once you have the firmware of death? Once you have the bootloader unlocked, everything is gravy.
I don't know the answer

theres the moto-fastboot file i was looking for!
much appreciated.

Now there's a guide
I just did this like 3 hours before this guide came out. Though it at least seems like I was going to all the right threads that are in this guide anyways.

humjaba said:
The big question is this - can you RSDflash the unlocked bootloader SBF by itself once you have the firmware of death? Once you have the bootloader unlocked, everything is gravy.
I don't know the answer
Click to expand...
Click to collapse
From my understanding, if you flashed the official firmware of death you CANNOT use RSD in any way. All of your flashing has to be done via CWM and fruitcakes. Full .sbfs will brick your phone. Hard brick. As in #@$% ME hard brick.

humjaba said:
Step 6 - Restore your stuff
Now you should have a factory fresh Gingerbread / MotoBlur installation (didn't you miss the bloat?), with the addition of the superuser app. For tethering, I use Barnacle (requires root). I used Titanium Backup to uninstall any apps I don't want (anything beginning with AT&T, Blockbuster, Y!, etc.) and to reinstall all of my apps.
Click to expand...
Click to collapse
Weren't there some reports of issues restoring via TB after flashing Ken's beta 4.5? I'd have to search through his thread, but I thought it presented an issue or two.

So I guess no sweet Roms for me. Still haven't found a good thread to root my phone. I'm not sure if the FOD would mess with the rooting part of it.

SoberGuy said:
Weren't there some reports of issues restoring via TB after flashing Ken's beta 4.5? I'd have to search through his thread, but I thought it presented an issue or two.
Click to expand...
Click to collapse
I chose the batch "Restore missing apps with data" option from Ti Backup and it worked flawlessly.

humjaba said:
I chose the batch "Restore missing apps with data" option from Ti Backup and it worked flawlessly.
Click to expand...
Click to collapse
Perhaps it was settings then and not apps. Appreciate the information. I'll be doing that tonight

after i unlocked the bootloader
i flashed CWM
then i use CWM to flash 2.3.4 GB beta 4 zip from kenn
i like it better my way

[Guide] Upgrade Bell phone to Bell 2.3.4

This is a rough guide to help you upgrade your Bell phone to 2.3.4. This has been tested and it works.
*Usual disclaimer: I am not responsible for any damage to your phone.
This isn't detailed but should be enough to get you going.
You must have a Bell phone and your bootloader must be unlocked. Assume you will lose all data and BACKUP!!
1) Restore Bell System
Use NFHimself's GobStopper CWM zip to restore your phone to stock Bell 2.2.2 - at this link:
http://forum.xda-developers.com/showthread.php?t=1185171
2) Install 2.3.4 and root
- Download 2.3.4 zip from this link and copy to your sdcard:
http://forum.xda-developers.com/showthread.php?t=1166362
- Download root cwm zip from this link and copy to your sdcard:
http://forum.xda-developers.com/showthread.php?t=1159572
- Install edgan's kernel if you have d100 device
http://forum.xda-developers.com/showthread.php?t=1173225
- Install faux's d1100 kernel if you have d1100 device
http://forum.xda-developers.com/showthread.php?t=1156040
- Install CWM Recovery (attachment on first post):
http://forum.xda-developers.com/showthread.php?t=1185171
- go into CWM Recovery and install 2.3.4 zip from sdcard
- install Root zip from sdcard
Done!
Thanks to NFHimself, MagentoX , y2whisper and everybody who helped with this.

Plemen, thank you for your help so far. I have done everything you mentioned, and once I get to CWM installing the 2.3.4 over the Bell 2.2.2 (which I used NFHimself's script to get back to) I get the following error.
Any ideas? (Please see attached image)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

awryter said:
Plemen, thank you for your help so far. I have done everything you mentioned, and once I get to CWM installing the 2.3.4 over the Bell 2.2.2 (which I used NFHimself's script to get back to) I get the following error.
Any ideas? (Please see attached image)
Click to expand...
Click to collapse
I've had this error while upgrading and it was because the base ROM on the phone isn't "Bell enough".
Did you flash the French SBF or just use NFS script from OrangeFR (Option 1 or 2)?

Well, let's see:
I went from Bell stock to French SBF originally (via RSD) to Gingerblur. I then went back to stock French SBF and from French SBF to bootloader unlock (via IHOP) to fastboot OrangeFR (d001), though I didn't update the Webtop at all (except maybe during Gingerblur) which is where this error is originating from.
So I went from OrangeFR back to Bell stock 2.2.2 through NF's script (which went fine, no errors at all). I did a factory reset in the ROM itself (not through CWM) which was fine, and once I got back into the stock Bell 2.2.2 complete clean I did your steps.
1) Put the Bell 2.3.4 zip and CWM_root zip on the SD card.
2) Flashed IHOP with RSD
3) Flashed recovery via fastboot
4) Went into recovery and tried the .zip file.
That's where we stand. Should I wipe data/cache before flashing, or will that just put me further in the ****hole?
Thanks again.
plemen said:
I've had this error while upgrading and it was because the base ROM on the phone isn't "Bell enough".
Did you flash the French SBF or just use NFS script from OrangeFR (Option 1 or 2)?
Click to expand...
Click to collapse

What did you do, then, to make the ROM more "Bell-like"?
plemen said:
I've had this error while upgrading and it was because the base ROM on the phone isn't "Bell enough".
Did you flash the French SBF or just use NFS script from OrangeFR (Option 1 or 2)?
Click to expand...
Click to collapse

awryter said:
Plemen, thank you for your help so far. I have done everything you mentioned, and once I get to CWM installing the 2.3.4 over the Bell 2.2.2 (which I used NFHimself's script to get back to) I get the following error.
Any ideas? (Please see attached image)
Click to expand...
Click to collapse
when you did step one did it say it downloaded the files prior to updating the device? this step takes approx an hour to complete.

So it looks like one of your partitions isn't close enough to bell. When I ran into this issue I went with option 1 - I flashed the French SBF and then ran NFS script to root and then restore to install the Bell partitions and checked for OTA. Now that NFS has updated his script to restore 2.2.2 partitions, the OTA may not find any updates which is fine.
awryter said:
What did you do, then, to make the ROM more "Bell-like"?
Click to expand...
Click to collapse
awryter said:
Well, let's see:
I went from Bell stock to French SBF originally (via RSD) to Gingerblur. I then went back to stock French SBF and from French SBF to bootloader unlock (via IHOP) to fastboot OrangeFR (d001), though I didn't update the Webtop at all (except maybe during Gingerblur) which is where this error is originating from.
So I went from OrangeFR back to Bell stock 2.2.2 through NF's script (which went fine, no errors at all). I did a factory reset in the ROM itself (not through CWM) which was fine, and once I got back into the stock Bell 2.2.2 complete clean I did your steps.
1) Put the Bell 2.3.4 zip and CWM_root zip on the SD card.
2) Flashed IHOP with RSD
3) Flashed recovery via fastboot
4) Went into recovery and tried the .zip file.
That's where we stand. Should I wipe data/cache before flashing, or will that just put me further in the ****hole?
Thanks again.
Click to expand...
Click to collapse

Hi,
If you are using my restore phone option, be aware that it overwrites all the partitions except for partition 3 which is you pds partition, data, which is 2 GB and can be generated with a factory reset, and cache, which is a 600MB temp storage space which can be wiped as well. It isn't just system and boot. It restores partitions that sbfs may not write to but doesn't update any bootloaders or radios.
The only thing that the French sbf might do to make things work is to flash an older bootloader. It is also possible that some portion of your pds partition gets modified. Most likely it's a signature in the bootloader or command line options being passed to the kernel that don't apply. There have been reports of phones bricking on ATT when they go back to their older bootloader, however, there have been anecdotal reports that this isn't the case for Bell. Be careful and be prepared for the worst.
Cheers!

If I do this, will I still have an unlocked bootloader?

once the entire process is complete, yes.

y2whisper said:
once the entire process is complete, yes.
Click to expand...
Click to collapse
So then could this be a permanent fix to the RAM issue?

Thanks for the detailed info on the scripts - it's great to get it from the horses mouth
NFHimself said:
Hi,
If you are using my restore phone option, be aware that it overwrites all the partitions except for partition 3 which is you pds partition, data, which is 2 GB and can be generated with a factory reset, and cache, which is a 600MB temp storage space which can be wiped as well. It isn't just system and boot. It restores partitions that sbfs may not write to but doesn't update any bootloaders or radios.
The only thing that the French sbf might do to make things work is to flash an older bootloader. It is also possible that some portion of your pds partition gets modified. Most likely it's a signature in the bootloader or command line options being passed to the kernel that don't apply. There have been reports of phones bricking on ATT when they go back to their older bootloader, however, there have been anecdotal reports that this isn't the case for Bell. Be careful and be prepared for the worst.
Cheers!
Click to expand...
Click to collapse

First of all...Can anyone who has been using the new 2.3.4 tell me is there any significant differences in the performance of the phone in everyday use?
Second: Will the WebTop without the Dock MOD work with this new ROM?
Third: If I do this will I be able to install Bell official OTA when it comes out officially or it will brick my phone?

I Am already on 2.3.4 on a bell Atrix, I can honestly say the upgrade does about 0 ... now with that said the real thing that we need is a market fix so we can finally play order and chaos in Canada.
I give this Guide a 1/10 because its redundant and is not as cohesive as the other guides that are already available.
Edit: no unlock in this guide?! whats the point?!
Edit2: nvm you didt write a guide... my mistake, you just posted a bunch of links for lazy people

hate when i hit thanks instead of reply.....
anyways thanks ray of sunshine for that post. the thread was created by request, but if you do have a more detailed breakdown feel free to contribute.
@sservati
I have noticed quite the difference with 2.3.4. outside of the added features like gtalk w/video, there are little tweaks like being able view your contacts by your google groups. as well as some performance tweaks live wallpaper still seems laggy but other transitions are very smooth. as long as you are comfortable with unlocking your bootloader etc, this is something I recommend. if you are overly nervous about doing that. then stick to what you have.

The most important thing to note when installing FR orange is to fastboot flash the boot.img that is appropriate for your phone (1100 / d00 ) before you flash the system.img otherwise you will boot loop! Its not clearly indicated in the linked thread from OP.
Carrion
P.S. I do like 2.3.4 more then 2.2.3 ... im just ticked cuz i lost a transparent widget, because for some ungodly reason its now incompatible?!

didn't know about the timing, but yes make sure you follow that guide as well.
ah sorry to hear that.
Did you try doing the spare parts fix? (download spare parts and turn off compatibility mode)

Why are you installing the FR Orange (2.3.4)? The 1100/d00 issue is dealt with in the unlock guides - this thread clearly notes the steps are for unlocked phones only to install Bell 2.3.4.
Anyhow, there are some great threads on unlocking international phones and folks should really consult those to unlock.
Carrion332 said:
The most important thing to note when installing FR orange is to fastboot flash the boot.img that is appropriate for your phone (1100 / d00 ) before you flash the system.img otherwise you will boot loop! Its not clearly indicated in the linked thread from OP.
Carrion
P.S. I do like 2.3.4 more then 2.2.3 ... im just ticked cuz i lost a transparent widget, because for some ungodly reason its now incompatible?!
Click to expand...
Click to collapse

Gonna try that now... thing is i don't have the apk,Ii need to download it from the market, i have already purchased it but its now no longer visable?! I have tried market enabler... this did nothing... i would really like the ability to see and use all the apps in the app market, i know this is a bit off topic though.

Carrion332 said:
Gonna try that now... thing is i don't have the apk,Ii need to download it from the market, i have already purchased it but its now no longer visable?! I have tried market enabler... this did nothing... i would really like the ability to see and use all the apps in the app market, i know this is a bit off topic though.
Click to expand...
Click to collapse
I'm having the same issue with a couple apps that i've purchased.
Anyways back on topic, I was on on cherryblur 0.5 and i managed to get to the bell GB following most of this guide. I tried to do a restore of a nandroid backup i made before going to GB, but for some reason the phone wouldn't boot. It would just stay at the moto symbol. Im assuming it was because of the boot.img. I tried for a few hours to get it to work, but then gave up and flashed the 2.1.1 french sbf, and then used NFHimselfs system restore script to get me back to the stock bell rom. It worked very well, just took a long time.
Personally I really like this Bell rom, works very well for me. Battery life has increased, its FAST, and there's no ram issues. As for the Webtop stuff, im not sure about. I rarely use it.
Just noticed that after flashing the bell_ihop.sbf to unlock the blootloader, the ram goes back down to 300mb. I wonder if someone can dig deeper into the bell_ihop bootloader and possibly fix the ram issues.

[Guide] How to use Flashtool

Hi everybody welcome to my tutorial about Flashing with Flashtool. This thread is for those who want to reflash their device back to Sony Stock. See below for last details about this thread and the last build by Sony.
Note: I DO NOT OWN THIS DEVICE ANYMORE. PICTURES ARE REMOVED FROM MY DROPBOX AND THUS NOT VISEBLE. FOR NOW JUST RELY ON THE EXPLANATION PLEASE. ANY QUESTION CAN BE ASKED HERE. I DO NOT RESPOND TO TECHMAIL!
Created: 23-02-2014
Updated: 05-07-2014
Latest Android build released by Sony: 12.1.A.1.205
Let's begin shall we.. We shall!
First you need to download the correct ftf file for your device/operator or needs. This can be done here: http://forum.xda-developers.com/showthread.php?t=2311964 In there you can share and download firmware files in .ftf format..
You alsol need a program called Flashtool. You can download this here: http://forum.xda-developers.com/showthread.php?t=920746
For Windows 8 and 8.1 users I also recommend you to read this thread: http://forum.xda-developers.com/showthread.php?t=2095087 Microsoft has enhanced the security in Windows 8/8.1 and Windows won't install proper signed drivers.
When you are done with that you need to move your downloaded firmware file to the proper location for flashtool to be found:
C:\Flashtool\Firmwares
After that you are good to go, just remember the following:
Bootloader locked? If not you wont have BE2/OTA/PCC etc (for unlocking and relocking: http://forum.xda-developers.com/showthread.php?t=2354721 )
I've made backups of my important files that are stored on my phone?
Battery at atleast 50%?
I have patience?
I got something to do meanwhile?
The last two things are very important
Let's get started:
1: Open Flashtool:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Flashtool(.exe) for 32Bits systems and Flashtool64(.exe) for 64Bits systems
2: Press the Lightningbolt picture and select Flashmode
This will give another screen.
3: Select the downloaded ftf. (In this case 2.254)
Make sure that all the wipes are checked and the others are unchecked. This is to prevent any bootloops or other problems after downgrading.
4: Press Flash and the next two lines will be added to the flashtool log
The files are being prepared and checked. Have a bit of patience please.
5: Turn off your phone and turn it back on into Flashmode
After this the process will start.
After flashing you can disconnect your phone and boot it up.
Via Flashtool you can also reset your system after. For example:
You are running the latest ExistenZe ROM from our beloved Niaboc79 and you want to go back to stock for a reason WITHOUT losing data! Just flash the last Stock ROM and untick the following boxes:
Untick DATA and APPSLOG!! But keep CACHE to wipe the /cache (is the same as a wipe cache via CWM).
FAQ​
- My Phone wont stay into flashmode
> Turn it off, wait a few minutes and turn it back into flashmode
- Flashtool wont recognise my phone
> Make sure you have the proper drivers installed. See C://Flashtool/Drivers
- Flashing failed
> Problem depends on the error code given by Flashtool. Post the problem here and perhaps we can help
- Got a bootloop
> Reflash again
- Even after reflash I got into a bootloop
> Turn off your phone via the small button behind the batterycover and wait a few minutes. Then try again. If that doesnt work you need to flash again.
- Booting takes ages
> This is normal. The entire cache needs to be rebuild. Patience my dear..
- After flashing and booting my phone is laggy.
> Reboot device and wait a bit. The phone needs to fully reset and boot itself. Have some patience dear.
- Do I need to unlock my bootloader to use flashtool
> NO!
- Can I unlock my bootloader with flashtool?
> NO!
- Can I relock my bootloader with flashtool?
> Yes

> Reserved by me

downgrade to root?
first, thanks! Very nice guide. I'm new to the experia world, my previous phone was a Desire S.
I have a question:
I have a problem with all stock roms with the mediaserver process. It is always running while I listen to music (which is a lot of time) and drains a lot of battery (up to 65%). Though I use poweramp player which is totally independent of the process (own library and decoder). On my Desire S on CM11 I don't have the issue this is why I want to move to a custom rom. I'm on 4.3 now (was hoping this would fix the issue) and want to root and full backup with keys for warranty purposes and then move to a custom rom.
Is it right that I have to downgrade first, since there is no root for 4.3 yet? If yes, what ROM? I have a C5303 and don't know what version I had previously. I bought it in Switzerland without SIMlock or any branding. Is there a way I can find out what my previous version was or can I basically just use any generic C5303 version?
Would you recommend 12.0.A.1.284 in order to be able to use DoomLords rootkit: http://forum.xda-developers.com/showthread.php?p=42701183#post42701183 ?
It's just that I don't know if I ever was on this version, also regarding warranty...
I know, many questions, but I just reached a point where I don't seem to get further without asking. Hope someone can clarify some of them.
Thanks in advance!
EDIT: And also I was wondering: In the picture says flashmode is reached by pressing the back button while connection, but there are softkeys. Is it not done with volume down?

mrjraider said:
Small changes.. @ moderators Is it possible this can become a sticky?
Click to expand...
Click to collapse
+1 for a sticky!
Nice done!

TheMorpheus said:
+1 for a sticky!
Nice done!
Click to expand...
Click to collapse
after flashing done
i have to turn on phone & make usb debugging & unknown source option check
but whenever i am going to boot it again reboot after colour bootscreen
i had tried number of times flashing again & again
i am attaching my flashtool log file also
Azhar

According to the log you attached everything went fine. So I dont understand the problem.
Perhaps an idea to redownload it? Sometimes it wont work properly because the ftf file is somewhat damaged..

I have to relock the bootloader before restore?
Edit
No, it's not needed!

reflashig stock rom
Thanks for this nice guide. Im having a lot of issues with the 4.3 rom.
I flashed via SUS, editing build.prop to let the phone detect the new version, because my phone is carrier locked, and they didnt released the update yet.
I have a lot of lag, and I must force reset lots of times, so I want to make a clean install, because last time I only updated.
So my question is, if I do a factory reset, my build.prop is going to change to the original file (Orange's rom) or ill keep with my modified file? (Stock center Europe)
What do you recommend to me? If I reflash a stock European ftf via flashtool, I'll have the stock's build.prop, and I'll receive those Ota updates without problem?
Thanks for your work!

No if you have a TA backup you need to reflash your ROM and Restore TA partition

mrjraider said:
No if you have a TA backup you need to reflash your ROM and Restore TA partition
Click to expand...
Click to collapse
I don't have the backup, because my phone has the bootloader locked, and the only thing I have done is root and editing build.prop to be able to upgrade to European 4.3. Everything is working for me, track id and BE. (btw I have a backup of my build.prop in the computer)
I only want to do a fresh install of 4.3, not my carriers rom, because is on 4.1.2
So can I reflash any Stock 4.3 rom? The rom has it's own build.prop?
Thanks for your help Mrjraider

diolo said:
I don't have the backup, because my phone has the bootloader locked, and the only thing I have done is root and editing build.prop to be able to upgrade to European 4.3. Everything is working for me, track id and BE. (btw I have a backup of my build.prop in the computer)
I only want to do a fresh install of 4.3, not my carriers rom, because is on 4.1.2
So can I reflash any Stock 4.3 rom? The rom has it's own build.prop?
Thanks for your help Mrjraider
Click to expand...
Click to collapse
Yes you can. Simply download the ftf file and follow the steps in the OP

Hi mrjraider,
Many thanks for the guide!
A quick question. I am now in 4.3, bootloader locked. If I downgrade to 4.1.2 (.254 for example) my bootloader is still locked, correct?
Thanks!

Yes

I want to go back to stock from AOSP ROM and I don't know what's the right .ftf file for 12.1.A.0.266 but I think I know the right file for 12.0.A.2.254 (German branded C5303) (I'm from Germany ). If I would flash the 12.0.A.2.254 .ftf file would the Update Center show me the 4.3 OTA update and everything would work like on stock before? And would I lose root even with Voodoo OTA RootKeeper and the option enabled to try keeping Superuser access in SuperSU?

You need to look in the thread I linked to. There you can find many FTF files.

mrjraider said:
You need to look in the thread I linked to. There you can find many FTF files.
Click to expand...
Click to collapse
I know I already looked there but I'm not sure which one is right, because I didn't see a generic one for all C5303 and I don't want do have a foreign branding
Edit: found it, sorry
Gesendet von meinem Sony Xperia SP C5303

hey bro, am looking for Sony C5303_12.0.A.2​.254 tft generic global or CE version also UK version ,am unable to find them . I have being searching xda and a found a link that is broken,so please if any one can help.Thanks in advance.:fingers-crossed:

desmond462 said:
hey bro, am looking for Sony C5303_12.0.A.2​.254 tft generic global or CE version also UK version ,am unable to find them . I have being searching xda and a found a link that is broken,so please if any one can help.Thanks in advance.:fingers-crossed:
Click to expand...
Click to collapse
Do not ask for ftf files in here. There is a proper thread for this
Normaly I would help but the chances of getting an older update is decreasing every day since the update of Sony has rolled out a few weeks ago

Well done ! Rollback firmware 4.3 to 4.1
Hi guys ! thanks for guide. I got successfull revert my phone from update 266 to 254.

hi sir, i'm on .254 rooted and just want to go back to stock because i want to update it to 4.3, is it the safest way? if so, what will happen to my apps like greenify, Titanium backup, and those apps that was already transferred to sd card? should i have to uninstall these aps? does it have remaining unwiped data to be cleaned if flashing the stock rom?
thank you..

[GUIDE] Baseband/Radio "stuck" and not updating? Here's how to fix it!

Okay, so I've had this issue for a few months now where no matter what I tried, I could not update my Baseband. I tried everything I could think of - flashed the full stock Rom, used mobile ODIN, flashed twice, etc. but no matter what, the baseband would stick to the old one. I tried googling and looking around but the same tricks as above were posted again and again to no avail.
I eventually found the answer, it was a single post buried in a thread on here. As I keep seeing posts from other users with the same issue, I figured I'd write a quick guide so that hopefully those searching for the problem will find it.
So to reiterate - you've just updated to a new firmware (custom or otherwise) but your radio (aka baseband) has not changed. You then try to flash the radio directly but it still won't change. What gives?
Well to fix it, you're going to need the following:
Odin 3.07
Triangle Away (Thanks to Chainfire, as always)
A Method of rooting your device (I'm leaving this up to you as it's a warranty voiding experience and I presume you know how to do that by this point).
An official Samsung firmware containing the radio you want to update to
If you're currently on an AOSP based ROM, then I have bad news - you'll need to flash back to touchwiz to do this. Once you're done, you can flash back though.
Remember to make a backup of all your data, as you will be doing a lot of flashing here.
Note: You may be able to fix your stuck radio problem without flashing back to a completely stock firmware and cutting corners elsewhere, however I wanted this guide to be bulletproof, deviating slightly may produce different results. If all else fails, follow each step below exactly!
Remember: This guide is specifically for those of you who have tried other methods and are still stuck on an old baseband. If you're just looking how to flash your radio, there are easier and less involved methods that don't require any wiping - I strongly advise you to try those first.
Okay, by this point I'm going to assume you've done all your backups and are ready to start flashing.
Step 1: Reboot your phone into DOWNLOAD mode (aka Odin). To do this, hold down POWER, VOL-DOWN and HOME at the same time until you see the following screens:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Remember to let go of the above buttons and press "volume up" to continue.
Step 2: Open up Odin 3.07, click on the "PDA" button and select the stock firmware file you have downloaded (file should have a ".tar.md5" extension, if you downloaded a .zip file you'll need to extract it but DO NOT EXTRACT MORE THAN THIS, you want a single .tar.md5 file).
Step 3: With your phone connected to your PC running ODIN, click "start". This will take a few mins, so be patient.
Step 4: Root. Now your phone should be rebooting into some pretty awful stock Samsung firmware. Boo. However this is a necessary evil. Here you need to root your phone. CF-Auto-Root is my preferred method but this trips Knox so do what you feel is best.
Step 5: Install and run Triangle Away. Triangle Away requires a Stock samsung kernel, which is why you've just flashed a full Samsung firmware. Triangle away requires root, which is why you've just performed Step 4.
Step 6: Install the Stock Firmware. Again.
That's right, repeat steps 2 and 3 once more to flash that stock Samsung firmware all over again. Except this time, your system is reporting that it's "official" and TriangleAway has cleared some flags that were preventing the updated radio from installing. When your phone reboots, your radio should have updated.
You're done! From here, you can do whatever you like - flash another custom ROM (you're still rooted at this point), wipe and restore a backup you made earlier, switch to AOSP or whatever. Personally, I would go buy Chainfire a beer as TriangleAway is what makes this all possible.

Nice....it helped me :good:
Thanks :highfive:

neoKushan said:
Okay, so I've had this issue for a few months now where no matter what I tried, I could not update my Baseband. I tried everything I could think of - flashed the full stock Rom, used mobile ODIN, flashed twice, etc. but no matter what, the baseband would stick to the old one. I tried googling and looking around but the same tricks as above were posted again and again to no avail.
I eventually found the answer, it was a single post buried in a thread on here. As I keep seeing posts from other users with the same issue, I figured I'd write a quick guide so that hopefully those searching for the problem will find it.
So to reiterate - you've just updated to a new firmware (custom or otherwise) but your radio (aka baseband) has not changed. You then try to flash the radio directly but it still won't change. What gives?
Well to fix it, you're going to need the following:
Odin 3.07
Triangle Away (Thanks to Chainfire, as always)
A Method of rooting your device (I'm leaving this up to you as it's a warranty voiding experience and I presume you know how to do that by this point).
An official Samsung firmware containing the radio you want to update to
If you're currently on an AOSP based ROM, then I have bad news - you'll need to flash back to touchwiz to do this. Once you're done, you can flash back though.
Remember to make a backup of all your data, as you will be doing a lot of flashing here.
Note: You may be able to fix your stuck radio problem without flashing back to a completely stock firmware and cutting corners elsewhere, however I wanted this guide to be bulletproof, deviating slightly may produce different results. If all else fails, follow each step below exactly!
Okay, by this point I'm going to assume you've done all your backups and are ready to start flashing.
Step 1: Reboot your phone into DOWNLOAD mode (aka Odin). To do this, hold down POWER, VOL-DOWN and HOME at the same time until you see the following screens:
Remember to let go of the above buttons and press "volume up" to continue.
Step 2: Open up Odin 3.07, click on the "PDA" button and select the stock firmware file you have downloaded (file should have a ".tar.md5" extension, if you downloaded a .zip file you'll need to extract it but DO NOT EXTRACT MORE THAN THIS, you want a single .tar.md5 file).
Step 3: With your phone connected to your PC running ODIN, click "start". This will take a few mins, so be patient.
Step 4: Root. Now your phone should be rebooting into some pretty awful stock Samsung firmware. Boo. However this is a necessary evil. Here you need to root your phone. CF-Auto-Root is my preferred method but this trips Knox so do what you feel is best.
Step 5: Install and run Triangle Away. Triangle Away requires a Stock samsung kernel, which is why you've just flashed a full Samsung firmware. Triangle away requires root, which is why you've just performed Step 4.
Step 6: Install the Stock Firmware. Again.
That's right, repeat steps 2 and 3 once more to flash that stock Samsung firmware all over again. Except this time, your system is reporting that it's "official" and TriangleAway has cleared some flags that were preventing the updated radio from installing. When your phone reboots, your radio should have updated.
You're done! From here, you can do whatever you like - flash another custom ROM (you're still rooted at this point), wipe and restore a backup you made earlier, switch to AOSP or whatever. Personally, I would go buy Chainfire a beer as TriangleAway is what makes this all possible.
Click to expand...
Click to collapse
No need this，too complicated。
Only turn off the phone, then remove the battery ,
install it
and get into download model ,
Flash the radio.
that you can update the baseband

nforce4 said:
No need this，too complicated。
Only turn off the phone, then remove the battery ,
install it
and get into download model ,
Flash the radio.
that you can update the baseband
Click to expand...
Click to collapse
Thanks, but unfortunately that didn't work for me.

neoKushan said:
Thanks, but unfortunately that didn't work for me.
Click to expand...
Click to collapse
Turn off your phone manually. Leave it for 10 sec, dont need to remove battery, Put the modem on Phone, NOT PDA connect your phone and flash it. It is simple.

IzArsha said:
Turn off your phone manually. Leave it for 10 sec, dont need to remove battery, Put the modem on Phone, NOT PDA connect your phone and flash it. It is simple.
Click to expand...
Click to collapse
Believe me when I say that I tried that, I tried just about everything before it would finally stick. Removing battery, leaving it off for 10s+ (I did this numerous times as TriangleAway demands it due to the risk if bricking your phone and one time left it off/unplugged for a good 20mins to no avail). There was some kind of write protection in place, Mobile ODIN (yeah tried that as well) mentioned it when trying to flash the Radio - hence why TriangleAway is needed.
Before it got "Stuck", I had manually updated my Modem a few times without issue. I've had the Note 3 since launch and voided Knox within about 2 days of getting it - believe me, I've been there and done that

Nothing worked for me also until I tried this method...
Sent from my SM-N9005 using XDA Premium 4 mobile app

Here's what I don't like, and what I "Do" Like...
Like....
1) A post in the proper forum that seems to help a few people fix their issue when other methods didn't seem to work.
Dislike...
1) Somebody coming in touting their own method (which may or may not work for a particular user). This, believe it or not, only adds to confusion when a person looks for an answer. Now there are different methods in the same thread topic.
2) 2 pages of back and forth arguing as a result of the above ^^^
So, I'll delete all posts concerning this debate on procedures.
Folks, don't go poaching other users threads please. If they provide a solution that helps a few users, then that is GREAT!!! Not all normal solutions work for all users. Stick around long and you will discover this on your own one day.
Cleaned thread, please don't make me come back and do it again.
MD

Thanks Moscow. I apologise for what happened, I didn't mean to cause a fuss.
To show there's no hard feelings, I've updated the OP with a warning that this is specifically for those who are still stuck after trying out other methods. Hopefully that's enough to keep everyone happy.

neoKushan said:
Thanks Moscow. I apologise for what happened, I didn't mean to cause a fuss.
To show there's no hard feelings, I've updated the OP with a warning that this is specifically for those who are still stuck after trying out other methods. Hopefully that's enough to keep everyone happy.
Click to expand...
Click to collapse
Much better. I didn't mean to start an argument... But it happened somehow.
Good detailed guide however. See you around XDA.

I'm having Baseband: Unknown issue, and flashing different modems are not changing it.
Can this method help ?
thanks

MuhammadZeeshan7 said:
I'm having Baseband: Unknown issue, and flashing different modems are not changing it.
Can this method help ?
thanks
Click to expand...
Click to collapse
Hmm, I really don't know man. I've not seen that error before so I can't comment. Perhaps this can help?

neoKushan said:
Hmm, I really don't know man. I've not seen that error before so I can't comment. Perhaps this can help?
Click to expand...
Click to collapse
I've done almost every method, but not yours. BTW I don't have any other triangle icon except the yellow triangle at the start of Download mode.

MuhammadZeeshan7 said:
I'm having Baseband: Unknown issue, and flashing different modems are not changing it.
Can this method help ?
thanks
Click to expand...
Click to collapse
Unpack the tar file, and flash just the modem.bin into phone (not pda) in Odin.

not working on SM-N900w8
Didn't work on my note 3 sm-n900w8, modem still previous version :crying:
any other suggestion please?

jsecruzvalencia said:
Didn't work on my note 3 sm-n900w8, modem still previous version :crying:
any other suggestion please?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=53632129&postcount=1
In the first box.