There does not seem to be any recent onfo on my partner phone, nor very clear if the 5360 rom is compatible
So here is the question. Is there a minimalist rom with equally good battery life. Her phone is much better than my ace
on battery life. but is full of samsung garbage.
bwizz60 said:
There does not seem to be any recent onfo on my partner phone, nor very clear if the 5360 rom is compatible
So here is the question. Is there a minimalist rom with equally good battery life. Her phone is much better than my ace
on battery life. but is full of samsung garbage.
Click to expand...
Click to collapse
As far as I'm aware the 5363 is the o2 variant of the 5360
You might be able to just unlock the phone if not already unlocked (use galaxy toolbox) & flash 5360 firmware and use 5360 roms
Anything you do you do at your own risk - neither myself or xda are responsible for damage caused
I have rooted and unlocked phone ready to install reincarnation rom. I can't boot into clockwork recovery as I get the "error in sideload zip 7 message" I have tried installing clockwork from rom manager but still same. Think it is because the GTs 5363 bt number is not recognised.
can I get around this issue? I did a google search and found a cwm clockwork bla bla that seems to work.
but I will wait for any comments/imput before I go ahead
bwizz60 said:
I have rooted and unlocked phone ready to install reincarnation rom. I can't boot into clockwork recovery as I get the "error in sideload zip 7 message" I have tried installing clockwork from rom manager but still same. Think it is because the GTs 5363 bt number is not recognised.
can I get around this issue? I did a google search and found a cwm clockwork bla bla that seems to work.
but I will wait for any comments/imput before I go ahead
Click to expand...
Click to collapse
Why would you install cwm from rom manager? It's not supported - please do some searching and some reading else you will damage your device
There are two ways to get cwm on galaxy y
1- Flash temporary cwm zip in stock recovery - see http://d-h.st/u2m
2- Flash a kernel with cwm built in
If neither work on your variant you will need to flash 5360 firmware via odin at your own risk
I thought that I read that the rom manager is the recommended way of flashing CMW? Your supplied link seems to be a windows install file
How do I activate it please.
bwizz60 said:
I thought that I read that the rom manager is the recommended way of flashing CMW? Your supplied link seems to be a windows install file
How do I activate it please.
Click to expand...
Click to collapse
Hi.
Here is the CWM link: http://forum.xda-developers.com/showthread.php?t=2649475
Please do some digging first before asking.
Also, ROM Manager is not supported on our phones, so do not use it.
bwizz60 said:
I thought that I read that the rom manager is the recommended way of flashing CMW? Your supplied link seems to be a windows install file
How do I activate it please.
Click to expand...
Click to collapse
Don't know what you are clicking on as it's a zip file
Make sure you are clicking on the right download button & not an ad - Install ad blocking software on pc or an app on phone if required
I never post exe files - all my files on dev host are Flashable zips/tars unless otherwise stated
See below Screenshot - Just press the download button as shown in Screenshot
{
"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"
}
Also you should take note of what you are reading, where you are reading it & what device it relates to - rom manager has never been a compatible way of flashing cwm on a galaxy y
The reading re my device is quite confusing. but I got the CWM installed thanks. In the interim I have soft bricked the phone. When it boots it still reads gts 5363 in the boot screen. I was expecting it to now read 5360? would it be a good idea to flash a standard 5360 onto the phone via odin .
and maybe work forward from that
bwizz60 said:
The reading re my device is quite confusing. but I got the CWM installed thanks. In the interim I have soft bricked the phone. When it boots it still reads gts 5363 in the boot screen. I was expecting it to now read 5360? would it be a good idea to flash a standard 5360 onto the phone via odin .
and maybe work forward from that
Click to expand...
Click to collapse
It would only say 5360 if you flashed 5360 firmware via odin
Iv kept telling you if you want to use 5360 kernels you will probably have to flash 5360 firmware
Feel free to do what you want at your own risk
Sorry bad info on my part I was trying to use CWM via galaxy toolbox. I hit a snag with the CWM as I it was faulty and I could not go back out of the advanced screen. to follow the rom suppliers step by step. Only way out was to reboot, and hence brick
bwizz60 said:
Sorry bad info on my part I was trying to use CWM via galaxy toolbox. I hit a snag with the CWM as I it was faulty and I could not go back out of the advanced screen. to follow the rom suppliers step by step. Only way out was to reboot, and hence brick
Click to expand...
Click to collapse
With respect Iv told you both ways to get into cwm
With the temp zip I provided by Flashing in stock rom or by Flashing a kernel with cwm built in
You have chosen to ignore all what I'm telling you & trying to do things in unconventional ways - Therefore I can no longer offer you support
Just flash stock rom via odin
I was using the cwm downloaded from the the link that kindly supplied. I was using galaxy toolbox as suggested by yourself. There is lots of reading on the XDA site !.I am sure it is your prerogative to dismiss me as an idiot but I am an enthusiastic phone tinkerer trying to find my way in an unfamiliar world of new termanology. If you don't have the patience to bear with people such as myself Then again that is your preragative
bwizz60 said:
I was using the cwm downloaded from the the link that kindly supplied. I was using galaxy toolbox as suggested by yourself. There is lots of reading on the XDA site !.I am sure it is your prerogative to dismiss me as an idiot but I am an enthusiastic phone tinkerer trying to find my way in an unfamiliar world of new termanology. If you don't have the patience to bear with people such as myself Then again that is your preragative
Click to expand...
Click to collapse
I said to use galaxy toolbox to unlock your phone - ie remove network sim lock if your phone is locked to a specific network
At no point did I say use it to flash cwm
If you can't get into recovery you need to flash stock rom via odin
I do have alot of patience but I find it annoying when people don't read things properly especially when the answers have already been written for them
I do appreciate your help. I am now following the odin info "supplied by yourself on the site"
Ta
bwizz60 said:
I am now following the odin info "supplied by yourself on the site"
Ta
Click to expand...
Click to collapse
That sounds sarcastic...
FYI, this Odin info can be found in his signature. It is also a sticky in the Android dev section.
Search, search, search.
bwizz60 said:
I am an enthusiastic phone tinkerer trying to find my way in an unfamiliar world of new termanology. If you don't have the patience to bear with people such as myself Then again that is your preragative
Click to expand...
Click to collapse
u wot m8
If you don't know what you're reading when it's filled with seemingly bizarre terminology (we've been at that stage one time or another), you do three things:
1) Read on and/or use Google.
Usually definitions will pop out after a while. If I'm not mistaken there are a few threads outlining terminology definitions and usage.
2) Follow everything that they say. And when I say follow, I mean follow 100%, by the book. Reread the instructions over and over to make sure you are actually doing it right.
3) PM another more well-informed member, and don't be afraid to ask.
As for patience, well...
He has dealt with countless people that were in about the same situation as you: thinking that they knew what they were doing and eventually getting into deep s**t with no way out. He has always tried helped them out. Problem is, some of them simply don't want to listen, even if he was correct (which he most likely was). Even then, he tries his best.
Trust me, he knows what he's doing.
Take a deep breath, reread EVERYTHING on this thread, and restart from square one: stock ROM.
If you're too lazy to find (I hope you're not) here is the link for Odin:
http://forum.xda-developers.com/showthread.php?t=2568853
Risky, but everything here is a risk, isn't it? I rarely hear of 5363 users getting stuck here, so this should be fine.
Good luck.
Why would I be sarcastic? there is volumes of stuff on the site all done by this guy.! I show appeciation of this . I can assure you I do spend hours trying to follow information. Some of the links don't work ,sometimes my Firefox security stops progress . very frustrating at times;.
Thanks Mr Smith, now unbricked. I could not find odin 3.184 "spent over an hour trying" 1.85 worked ok . Phone now wakes up as 5360! If the rom is less bloated than the 02 one .I might leave well alone! Stress level falling!
What he meant was Odin3 v1.84.
But, its nice to see things sorted out with your partner's phone.
I 've had time to have a look at the standard rom Iinstalled. Glad the phone is working etc but I still have not achieved anything .
I still need to get rid of the samsung bundled stuff and be able to use the sd card storage. I am still unable to use CWM 5.0.26 "I get the code 7 error and the phone has re un rooted . Update ,Ive now re rooted it!
bwizz60 said:
I 've had time to have a look at the standard rom Iinstalled. Glad the phone is working etc but I still have not achieved anything .
I still need to get rid of the samsung bundled stuff and be able to use the sd card storage. I am still unable to use CWM 5.0.26 "I get the code 7 error and the phone has re un rooted . Update ,Ive now re rooted it!
Click to expand...
Click to collapse
Root phone
Use Link2sd (playstore) to uninstall system apps
Use the temp cwm I posted a few pages back - place on root (not in any folder) of sd card & flash in stock recovery to get to cwm
Or use a custom recovery that has cwm built in eg hells fusion #50 for stock based roms
Can't give you any more support with this as I'm just repeating what Iv already said
Related
If you are here the odds are you are looking to take your Verzion Galaxy Tab back to the default setup for one reason or another.
Here are the steps you will need to take.
First let's make sure you have all the files and things are set up for this.
Hemdall
Download Heimdall from HERE, this is the program you are going to use to flash the needed files to your Galaxy Tab. I am putting the version I use on my sever just in case.
But here is a link to the developers page so you can download the original if you want.
http://www.glassechidna.com.au/products/heimdall/
You will also need *Microsoft C++ This also needs installed on your machine because it has .dll files Heimdall uses. (I use Windows 7 and did not need to install this [I think])
Now you will need to install the drivers the is also needed for Heimdall. unzip heimdall and go into the drivers folder where you will see zadig.exe. Run this.
At the top you see options. Click "list all devices"
Then in the dropdown select Android USB composite device (or whatever it says). (NOT*mass*storage)
Click start and let heimdall download/install the drivers.
Files You Are Going To Flash To Your Tab
HERE is where you *are going to download the files needed to flash to you tab.* There are four files in total.
DOWNLOAD
cache.rfs
param.lfs
system.rfs
zImage
Ok, Let's get to flashing over the files and getting your tab back to normal.
1: Connect your tab to your PC
2: Launch your tab into download as it is already connected to your PC.*(Do this by holding the volume down and pushing the power button)
3: Go in to the folder " heimdall" and start " heimdall-frontend.exe"
4: Set up the files you are about to flash to the tab in side of heimdall.* It should look something like this.
THIS IS THE IMPORTANT PART!!!!!! DO NOT SCREW THIS UP - -* I AM NOT RESPONSIBLE!!
DO NOT EVER EVER EVER PUT ANYTHING IN ANY OTHER LOCATION. THESE ARE THE ONLY FILES YOU NEED.
zImage goes in both the Kernel AND Recovery slot.
system.rfs goes in Factoryfs
Param.lfs goes in Param.lfs
cache goes in the cache slot.
{
"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"
}
5: After you have the files in place click start to flash. ALWAYS make sure your battery is sufficiently charged or you will have MAJOR problems. (I had to push start a few times.)
After this runs you will more than likely boot loop. Power down, wait a few seconds and hold power and up volume to boot into recovery.*(NOTE, do not hold power too long, just long enough to turn it on, then continue holding up volume till you see recovery. WIPE DATA AND CACHE. Tab should boot.
Note, if heimdall fails at the very beginning, just try unplugging and turning off the tab, close, and relaunch heimdall. it will eventually start. sometimes you just need the right combo of plugging in launching the*program.
After this is should be just like you took it out of the box, other than still having root access.
Hope this helps!
Aslo, I did not do any of the work here other than test it out and retype what is on this site to make it available to those on XDA and if you read my blog.
http://www.droidforums.net/forum/samsung-galaxy-tab/113084-how-restore-vzw-galaxy-tab-stock-dj11.html
All credit should go to mike919 at droidforums.net for putting this together!!
You can view his post here.
http://www.droidforums.net/forum/samsung-galaxy-tab/113084-how-restore-vzw-galaxy-tab-stock-dj11.html
Shameless Plug:
If this helped you out would you do me a favor and go to this site and vote/comment?
And pass it along to your friends as well.
Who Pees In The Shower?
Hope this helps some people out around here!
This should be a sticky... Just Saying
Thanks,
I tried to make sure I typed it as good as I could so people like me (mess things up often) would be able to pull it off and host all files I use so that nothing will change.
But I would like someone to look it over and make sure I did not miss something. We are all human after all.
And if there needs to be any other images people can think of to help more people out I will be more than happy to add them.
I cannot find ANY tuts like this for flashing roms, recovery, ect. You, my newfound friend, are the first. We need more exactly like this.
Sent from my SCH-I800 using XDA App
This is great stuff. I messed up a bunch of junk on my VZ galaxy tab and would like to go back to stock. Question about this guide: I've converted to ext4. Can I still follow the steps in this tutorial to return to stock or is there anything else that I need to do first? Thanks very much!
This post made even a retard like me dangerous enough to want to try flashing. Bump for the ext4 answer
Bobby Buggs said:
This post made even a retard like me dangerous enough to want to try flashing. Bump for the ext4 answer
Click to expand...
Click to collapse
Took the plunge anyway. Seems to have worked. Great tutorial!
Had previously used Koush's bootstrapper from the market to convert the file systems to ext4. Later tried to install KhasMek Voodoo Plus v3 kernel on my VZW tab and it nuked it (prob cause I did something wrong). Using these instructions, I got back to stock. Now to boot strap again and try, try again!
Thanks for the guide
fonixmunkee said:
Had previously used Koush's bootstrapper from the market to convert the file systems to ext4. Later tried to install KhasMek Voodoo Plus v3 kernel on my VZW tab and it nuked it (prob cause I did something wrong). Using these instructions, I got back to stock. Now to boot strap again and try, try again!
Thanks for the guide
Click to expand...
Click to collapse
Yeah, I think I get it wrong more than I get it right.
Last weekend I did this like 3 times in an hour.
Happy it is helping a few people out.
chaos67731, I saw in another thread you were having a hard time getting Koush's boot strapper from the market to work. Did you ever get a resolution for that?
fonixmunkee said:
chaos67731, I saw in another thread you were having a hard time getting Koush's boot strapper from the market to work. Did you ever get a resolution for that?
Click to expand...
Click to collapse
No, I tried a few times and did not have any luck. The only thing I am looking to customize with the Tab is really to have it over clocked a little.
I just got the Evo so after I am done setting that up and getting everything worked out I am going to try again.
But if I remember right when ever I run Koush's boot strapper the tab reboots and goes in to recover mode and starts to flash something. (I think, cant seem to remember 100% right now) . Then I get stuck on the Samsung screen..
At that point I am not able to boot back in to recovery mode to wipe anything, but I can boot in to download mode and restore the Tab.
I think I have to be missing something simple?
Got the bootstrapper from the market to work again on my VZW Galaxy Tab. Formatted the SD card and then tried it again...it worked great after that!
Sent from my SCH-I800 using XDA Premium App
fonixmunkee said:
Got the bootstrapper from the market to work again on my VZW Galaxy Tab. Formatted the SD card and then tried it again...it worked great after that!
Sent from my SCH-I800 using XDA Premium App
Click to expand...
Click to collapse
Maybe I am missing something?
Sent from my SCH-I800 using XDA Premium App
hi after restore to stock my screen in blank??help me
this was perfect
you wrote the directions clearer than water bro. thanks! i was dinking around for the 1st time with the tab and screwed something up. i'm back in business!
Your the best... got it first time Great work
- The Mike G.
Had a scary night last night with the old computer/phone/exclamation point error screen but this tutorial helped me out. Thanks a ton.
THANK YOU!
Thanks man! My Galaxy Tab (us cellular branded) was gone after a flash attempt gone bad (black screen and nothing more), but thanks to this tutorial it's finally back to life!!
I LOVE YOU MAN!
VZW Custom Kernel
So out of curiosity, is the Bootstrapper the only way to get a custom recovery set up for the Verizon tab? I used z4root and got the root access, but since then, I haven't had an opportunity to flash roms or kernels because of the lack of a custom recovery. Anybody think they could help ?
I didnt find any step-by-step tutorials about this on xda, which is kind of weird and because i have spare time and its 3:19am I decided to make this tutorial
EDIT: If you are coming from eclair, install a froyo ROM and make sure it has a bootloader. Remember, if you cancel an installation that changes your bootloader, or stop it in anyway, you may hardbrick your phone. MAKE SURE YOU DON'T CANCEL OR TRY TO PAUSE THE INSTALLATION, JUST LET IT FLASH SMOOTHLY. use a laptop if you can, just in case an unlucky power surge would stop the flashing process
EDIT2: Here is a good Tutorial video from xda user Tejas Ahobala (if you don't know what he is doing at the start, dont worry. He is doing a factory reset before flashing):
EDIT3: A word from one of the commenters:
VelocityJump said:
Thanks a ton for this guide. I had rooted my phone a couple of months back but wasn't really able to figure out how to use ODIN to install a custom ROM all this while. A few pointers for others noobs...
1. The tip about some custom ROMs requiring a wipe data is important.
2. If you're already using CWM, use the 'shutdown' option and not the 'reboot' option when the phone reboots during the flashing process.
Click to expand...
Click to collapse
Here we go...
______________________________________________________________
Terms and words -->
Flashing ==> means installing a new ROM
ROM ==> is the operating system, any version of modded or un-modded android
Android ==> Google made operating system!!!
ODIN ==> Here, it means the program that you can use to flash ROMs on your phone (the phone im going to use here is samsung galaxy 3)
Soft brick ==> No, not the construction brick, this means you've got no working operating system or you have one but its damaged and you can't use it, so you cant see your homescreen, you only see a boot-loop when it wants to come up. You can view your recovery and boot loader (The download screen) when soft bricked, so you can easily fix this problem by re-flashing.
Hard brick ==> Similar to the construction brick, your phone with little hope of recovery without sending to the samsung base for repairs To avoid hard bricks, open the .TAR file which contains your ROM using winRAR, and check if it contains sbl.bin and boot.bin files or not. If it does contain, and you are nervous or this is your first time flashing etc, simply go and flash Kyrillos' ROM or Kyora ROM instead. (I'm not advertising, just stating a couple of ROMs that I know are safe) these ROMs can only soft brick your phone should the worse happen and there is no chance of hard brick
______________________________________________________________
Should this guide be followed carefully, nothing harmful can happen to your phone. Yet I wont take responsibility if something happens to your phone.
______________________________________________________________
**************************************
Remember to Backup your contacts and apps!
**************************************______________________________________________________________
Stuff to download:
1) ODIN and a .OPS file, found Here, Or alternatively here.
2) The ROM, depending on what ROM you want there are different versions available. check This thread, the kitchens/ stock ROM packs part for stock ROMs, or if you want to try a custom ROM, try any other. I personally use Kyrillos' ROM, or Hillbeast's KyoraROM. Marcellusbe is praised highly by all for giving us the Cyanogenmod.
______________________________________________________________
1) Extract 'Flash tools.rar'
2) open Odin multi-downloader. This is how it's meant to look like.
{
"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"
}
NOTE: Sometimes some random error message with a korean writing pops up. dont worry, it's nothing, just press OK every time you see it
3) Press the OPS button located in the 'Select OPS' section, as shown in the image below. NOTE THAT YOU SHOULD ONLY USE THIS OPS FILE IF YOU HAVE SAMSUNG GALAXY 3. YOU MAY ENCOUNTER SERIOUS PROBLEMS IF YOU USE THIS OPS FILE WITH A DIFFERENT PHONE. (works with i5800 and i5801 as far as I know.)
4) Browse for the 'apollo_0531.ops' that came in the rar file with odin and select it.
5) Tick the One Package option located on the left side of the application.
6) The ROM that you have downloaded should have a .tar extension. If its a .rar file, open it. If it has a .tar file inside it, extract it and use it, but if it has some weird ass stuff in it that only Jesus and Chuck Norris understand the meaning of, you need to use the 'free rar extraction frog' application to turn it into a .tar file. Download it for free from here.
7) The above step was just to confirm if you have the right file, so you dont get any errors. Now just select One Package button that is highlighted in the picture and browse and select the .tar file.
8) Make sure you have ticked everything that I have ticked. Use picture from part 5.
9) Go to your phone. go to Settings->Applications->Development and tick USB debugging if its not already ticked.
10) make sure you have the device drivers, just install Samsung KIES from HERE to make sure you do have the drivers. If the page doesn't show, just Google 'download samsung KIES'
11) turn the phone off, take the USB out, and press volume up, home button (the big fat button in between the menu and back buttons) and the power button together. hold them until you see the 'FORCE UPLOAD BY KEY PRESSING' screen. Now plug the USB back in.
12) Odin will immediately recognize your phone, and there will be a yellow label, like so:
13) Double check that you haven't missed anything.
14) Press start! HERE
15) You will see a blue download screen, saying please don't interrupt. PLEASE DON'T INTERUPT IT!!!!
16) The process will finish and system will reboot one or two times. go have some tea and come back 15 minutes later. You should have the Rom of your desire working on your phone.
NOTE: Some custom ROMs require you to wipe system data and then wipe cache. don't forget to do that! restart phone after wiping the data etc. If you've flashed a custom Rom and the device is showing a stupid triangle with an exclamation mark inside it, dont panic, press the menu button and you will see the menu (This menu is called the recovery menu).
EDIT4: How to flash kernels (on galaxy3/apollo/5800/5801)
METHOD 1==>
1--> you go to the kernel thread and download their kernel. it is to be a .tar file. (eg g3mod.tar)
2--> follow steps 3 to 5 from above tutorial
3--> put phone in download mode (step 11) and connect with usb
4--> in odin, select the 'select as one package file' option and browse for the kernel .TAR file. select it.
5--> check youve done everything. YOU SHOULD HAVE DONE EVERYTHING IN THE TUTORIAL EXCEPT THIS TIME INSTEAD OF USING A ROM YOU'RE USING A KERNEL!!
6--> There is no need for wipe unless otherwise stated by the developer.
7--> congratz man, you got yourself a new kernel!!
OPTIONAL 8--> download setcpu from xda (you can also download off market and pay for it for the donation)
its really usefull, it lets you control how much your phone uses the cpu and you can undervolt the cpu etc, you will find more info on the setcpu thread.
METHOD2==> (Only works for some kernels)
1--> go to the g3mod website and download the .zip version of the kernel. (there is a .tar and .zip)
2--> put the .zip in the root of your sd card
3--> go to recovery mode by either using kyrillos' rom (press & hold power
then choose reboot into recovery) or by turning the phone off and pressing volume up and down and the power button all together. select install .zip from sdcard and then select your .zip you downloaded before.
4--> it will install. no wipe needed unless the dev says so. reboot. HAVE FUN!!
HOW TO FLASH ROMS USING SYSTEM.IMG
1) Download system.img from safe source, preferably provided by dev, or any other trusted member who knows what they are doing.
2) Flash g3mod ROM.
3) Copy the system.img and paste into this path in your sdcard:
sdcard/android/data/g3mod/roms/**there are several folders here, just paste the system.img to the folder that suits the rom's name**
4) Boot into recovery.
5) Go to Multiboot.
6) Select desired ROM.
7) Done
________________
______________________________________________________________
THE GODDAMNED END.
Very nice
This is nice bro.....
If you can think of any missing tutorials, pm me, ill make some (might even make vid)
dhirend_6d said:
This is nice bro.....
Click to expand...
Click to collapse
all it took was about two hours
i may make vids about rooting and stuff as well, but im lazy and i think rudolf already done that, so im too late
the reason i made this was that when i first got my phone, it was february last year and the phone was running the eclair (so it sucked ) an i was being pushed by my friends that why i didnt have foryo and it took me literally something like 7 hours to find a 'followable' guide on flashing the xxjpa or something... anyway i thought having a really noob proof guide will be useful too ppl like me a year ago
nicely written
i was searching for tutorial like this 9 monhs ago and never found it with such detailed description
Sent fom Galaxy
Kyorarom Ascendency
a3 powered by
G3mod test 209 OC
Thanks it can help some peoples !
Moderator Message
Thread Stuck
Well done!! Good for the newcomers
Nice guide
doneeeee! easy
vol down + home button takes it directly into download mode
eeshlikhith said:
vol down + home button takes it directly into download mode
Click to expand...
Click to collapse
yea it does. what is the difference tho?
PersianSphinx said:
yea it does. what is the difference tho?
Click to expand...
Click to collapse
Simpler anyway nice guide! Detailed enough for any newbie! When i was new to thid forum i din understand much of all the guides but wif this im sure many more ppl will understand
Sent from my GT-i5801 using XDA App
Hello there!
I tried to do that, but in the middle of instalation of the room JPX/JP4 it failure.
And now my G3 turn on but don't work. It show a picture of a cellphone and computer and a exclamation point!
I tried to downgrade for 5800L, but odin and kied didn't link with usb.
=\
Any help?
xicoo ~ said:
Hello there!
I tried to do that, but in the middle of instalation of the room JPX/JP4 it failure.
And now my G3 turn on but don't work. It show a picture of a cellphone and computer and a exclamation point!
I tried to downgrade for 5800L, but odin and kied didn't link with usb.
=\
Any help?
Click to expand...
Click to collapse
Did you cut off the power or do anything that disrupted the flashing process? Tell us what you did explicitly
Sent from my GT-I9003 using xda premium
Question
Thanks for such a great tutorial.
I have a question.
Does sd card and sim card also needs to be taken out before one start flashing?
Also how long does this procedure take (the flashing process)?
Thanks
gauravgs said:
Thanks for such a great tutorial.
I have a question.
Does sd card and sim card also needs to be taken out before one start flashing?
Also how long does this procedure take (the flashing process)?
Thanks
Click to expand...
Click to collapse
Its not necessary. Flashing takes about 3~4min for me for it to boot up
Sent from my GT-I9003 using xda premium
bscraze said:
Its not necessary. Flashing takes about 3~4min for me for it to boot up
Sent from my GT-I9003 using xda premium
Click to expand...
Click to collapse
that's great.. 3~4 mins only. after that will I be able to use my phone in regular mode (making calls and restoring my address book) or I have to configure it?
Thanks
gauravgs said:
that's great.. 3~4 mins only. after that will I be able to use my phone in regular mode (making calls and restoring my address book) or I have to configure it?
Thanks
Click to expand...
Click to collapse
after flashing it will work like newly released from factory you can restore and all but depending on if you wiped device after the flasing process you will lose data, thats why i said make a backup of your important stuff before flashing
thnx bscraze for answering peoples questions while i was away
PersianSphinx said:
after flashing it will work like newly released from factory you can restore and all but depending on if you wiped device after the flasing process you will lose data, thats why i said make a backup of your important stuff before flashing
thnx bscraze for answering peoples questions while i was away
Click to expand...
Click to collapse
Ok
so should I backup my sdcard contents also on my PC (wipe data will clear both memories sdcard as well as phone's)?
or shall I leave it as it is?
I use titanium backup. Backed up all the user apps using it.
Thanks
I bricked my sgs4 when I used Rom Toolbox Pro to flash TWRP custom recovery. every time I unplug bat it goes into Odin mode. Every reboot with removal of battery. So I held down Volume- and home and power button the phone powered on to the screen asking if I wanted to go into Odin mode or Cancel. I. cancelled and was able to reboot successfully. Do I'm not completely bricked now. but when I try to get into stock recovery I get bricked to Odin mode. and have to remove the bat then volume- plus home plus power then Cancel going into Odin mode etc. I officially have no stock recovery
this is all due to the fact I went back after trying to flash cwm recovery...I flashed safestrap then removed it but still no recovery. and I really want the 4.3 that just came out.
btw safestrap is not working for me. I downloaded the kernel flash and a Rom specific for locked sgs4 ask I get after booting passed safestrap is a blank screen for ever.
Any help is great. thanks guys
Correct me if I'm wrong someone buy I'm pretty sure If you're boot loader is locked you are NOT to flash any custom recoveries or kernels. Safestrap is the only recovery you can use. I'm on mf3 myself, you may have to odin back to stock, root, and install safestrap again. Can't flash any kernels on mf3.. it will cause your phone not to boot.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
You are going to have to odin the stock tar files. I assume you are on mf3 firmware. Look for the mf3 tar files, there on one of the threads. Google "mf3 tar xda"
I looked for a link to firmware mf3 to flag in Odin but nothing
Already the bricking the phone deal is taken care of.
I don't know why its so hard for people to find stuff I googled it with results just fine.
http://forum.xda-developers.com/showthread.php?t=2502003
Sent from my SAMSUNG-SGH-I337 using xda premium
jd1639 said:
You are going to have to odin the stock tar files. I assume you are on mf3 firmware. Look for the mf3 tar files, there on one of the threads. Google "mf3 tar xda"
Click to expand...
Click to collapse
So do u have a link AT&T I337 MF3 firmware?
Lewis_Koseck said:
So do u have a link AT&T I337 MF3 firmware?
Click to expand...
Click to collapse
Google "mf3 tar xda"
WOW!
scott14719 said:
WOW!
Click to expand...
Click to collapse
That Google stuff is complicated, lol
Obviously I did and nothing. It's great when people ask for help all we get is snobbed nosed attitudes
And here I Google the brick problem Every one on xda saying only solution is Odin. And real no I was able to pull out of the brick without it so obviously not everyone is as smart as you guys but if it's even possible to keep your attitudes in check would be great!
jd1639 said:
That Google stuff is complicated, lol
Click to expand...
Click to collapse
Yeah must be.and neither me not anyone I know will be posting in xda sense it's just gonna illicit a bunch of re,tards talking sh.t.
Lewis_Koseck said:
Yeah must be.and neither me not anyone I know will be posting in xda sense it's just gonna illicit a bunch of re,tards talking sh.t.
Click to expand...
Click to collapse
Glad you got it fixed. But you probably have no clue how you got in the situation you were in nor how you got out of it. I'd suggest you do a lot of reading of the pinned threads in the general forum. Sorry, you'll have to get your own links.
Lewis_Koseck said:
Yeah must be.and neither me not anyone I know will be posting in xda sense it's just gonna illicit a bunch of re,tards talking sh.t.
Click to expand...
Click to collapse
Post #5 in THIS thread GAVE you a link to the MF3 firmware 2 HOURS before you posting again asking for it. How much more help would have liked to receive? I suggest you evaluate your own mental state of being before you respond to others with childish name calling. At the very least, read the thread you are in before making yourself look ignorant. You will definitely not be a loss to the community with an attitude like yours.
scott14719 said:
Post #5 in THIS thread GAVE you a link to the MF3 firmware 2 HOURS before you posting again asking for it. How much more help would have liked to receive? I suggest you evaluate your own mental state of being before you respond to others with childish name calling. At the very least, read the thread you are in before making yourself look ignorant. You will definitely not be a loss to the community with an attitude like yours.
Click to expand...
Click to collapse
I swear I even gave him the link to what he needed all he had to do was read it. Does he need arrows pointing to it or pilot navigation or something? Smh... Calling people names when all we're trying to tell him is look first than read.
Sent from my SAMSUNG-SGH-I337 using xda premium
Lewis_Koseck said:
I bricked my sgs4 when I used Rom Toolbox Pro to flash TWRP custom recovery. every time I unplug bat it goes into Odin mode. Every reboot with removal of battery. So I held down Volume- and home and power button the phone powered on to the screen asking if I wanted to go into Odin mode or Cancel. I. cancelled and was able to reboot successfully. Do I'm not completely bricked now. but when I try to get into stock recovery I get bricked to Odin mode. and have to remove the bat then volume- plus home plus power then Cancel going into Odin mode etc. I officially have no stock recovery
this is all due to the fact I went back after trying to flash cwm recovery...I flashed safestrap then removed it but still no recovery. and I really want the 4.3 that just came out.
btw safestrap is not working for me. I downloaded the kernel flash and a Rom specific for locked sgs4 ask I get after booting passed safestrap is a blank screen for ever.
Any help is great. thanks guys
Click to expand...
Click to collapse
Lewis_Koseck said:
I bricked my sgs4 when I used Rom Toolbox Pro to flash TWRP custom recovery. every time I unplug bat it goes into Odin mode. Every reboot with removal of battery. So I held down Volume- and home and power button the phone powered on to the screen asking if I wanted to go into Odin mode or Cancel. I. cancelled and was able to reboot successfully. Do I'm not completely bricked now. but when I try to get into stock recovery I get bricked to Odin mode. and have to remove the bat then volume- plus home plus power then Cancel going into Odin mode etc. I officially have no stock recovery
this is all due to the fact I went back after trying to flash cwm recovery...I flashed safestrap then removed it but still no recovery. and I really want the 4.3 that just came out.
btw safestrap is not working for me. I downloaded the kernel flash and a Rom specific for locked sgs4 ask I get after booting passed safestrap is a blank screen for ever.
Any help is great. thanks guys
Click to expand...
Click to collapse
You should realy read.... All of us on MF3 know that !!... That was one of the fist ways to boot back up. Safe strap is going to be a savior for you.... Basically this has been discussed a million times..... If you are on MF3 you cannot downgrade you can only upgrade or stay on MF3, If you want 4.3 sooooo bad I will link it for you. But I suggest staying patient. There is nothing really that improved over 4.2.2. So I would advise you not to upgrade but I will post the links and tell you how to do it. One if you were smart you would have made a nandroid backup thru SS and then when you boot into that you stay on the stock rom slot. Hit then go in and write your backup just the system folder.... So you won't lose all of your data. Now if you didn't make a nandroid backup. Then you can try flashing the stock recovery and fixing the permissions thru safe strap..... IF that doesn't work well you are just up the creek.....
HAHAHAHA. JK Get odin and get the MF3 Tar.MD5 files But your phone manually into odin mode and Go back to stock MF3. Seriously read, read, read. I will make it real easy for you this time. By posting links but you are just asking for it. So first grab these files: https://mega.co.nz/#!WEEzSA7Z!aB46731_AwM7P83eMdDlmFYd1hUZfFBcQAZjc1X7wAE These are the stock MF3 files that were contributed to the community by Shockndrop: http://forum.xda-developers.com/showthread.php?t=2502003
Now grab Odin, I prefer this one: ODIN 1.85 http://forum.xda-developers.com/showthread.php?t=1262272
Now put the MD5 files in their proper places in odin and and hook your phone up with a Good **** Solid Universal Serial Bus Cable: Like pitured here:
{
"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"
}
Put her down into a coma AKA, ODIN Recovery mode manualy by holding power, home, and volume down. Then when prompt after the warning volume up to continue. Flash with Odin to restore to stock MF3. Brand Spaking new!!!!
Use your favorite root Method, New root method is the only one we support here on XDA, Which involves an SD Card,and the Terminal from the Play store. Or if you want the fast and dirty way because you are lazy do the Kingo root, I don't indorse it, but I have yet to hear anything negative about it, other than speculation. Links: http://www.kingoapp.com/android-root/download.htm - one click method Easy.
Old proper way: Quoting Jortex "HOWTO:
Use a card reader to format the micro SD card to exFAT (FAT32 or other formats does not work) in Windows. I haven't tried Linux or MacOS X, so they may not work.
Download the attached file (Root_for_ATTSG4_FM3.rar) http://forum.xda-developers.com/attachment.php?attachmentid=2165629&d=1375669716 and extract it into the root of your EXTERNAL microSD card using the card reader in Windows. (You can do the extraction using WinRAR, http://www.rarlab.com/download.htm or 7-zip, http://www.7-zip.org/download.html ).
Put the SD card back to the phone and download the Android Terminal Emulator app.
Open the Terminal Emulator app and run below 3 commands:
Code:
cd /mnt/extSdCard
./pwn
./script.sh
Then, open SuperSU and check everything looks good.
Then open a root app and it should be working properly.
Reboot your device once to confirm root is still working after reboot.
Come back to the post and press the THANKS button
Notes:
I uploaded a screenshot from the Terminal screen where the instructions are entered. Yours should be the same except you don't need to enter the "ls -l" command. It's just to show what files I have on the SD card. Ignore LOST.DIR directory.
Remove any SuperSU apps from your phone before following the above steps. script.sh installs it automatically.
You can use adb shell instead of a terminal app which is more convenient but requires Android SDK. Follow these steps only if you are about to use adb:
Download and install all Samsung Galaxy S 4 drivers from here: http://www.samsung.com/us/support/owners/product/SGH-I337ZWAATT#
Activate Developer options -> USB Debugging mode. To have the phone show the Developer options, go to Settings -> More -> About device. Tap on "Build number" 6 times.
You have to use an external SD card. No other alternative have been found yet. Using the device storage, i.e. /mnt/sdcard, or /data/local/tmp, DOES NOT work.
Warning (suggested by rushi.1986): "We have root for MF3 but we neither have a working recovery, nor an ODIN back to stock package. Be very careful what you do with your root. At this point, there is no way to recover even from a soft brick. (unless you know exactly what caused the soft brick and can correct it using adb)"
For those who do not know how to format an SD card on Windows (thanks to jee'sgalaxy):
Insert the micro SD into the computer (may have to use a reader or a micro SD adapter).
Go to "My Computer".
Right click on your SD card that showed up.
Click Format.
Choose exFAT as the format.
Click "OK".
Don't forget to press the THANKS button.
Credits:
***Exploit adapted for AT&T by Jortex***
***Original Guide by Open1Your1Eyes0 for Verizon Galaxy S 4***
***Original Exploit by DooMLoRD***
Next install your only way as of now to run custom roms period in your current situation and you should be incredibly grateful instead of saying that you want 4.3 soooooo bad....... really not tooo many benefits at all. Now 4.4 KittyKit lol is a different story..... So grab the latest and greatest version of safestrap from here: http://forum.xda-developers.com/devdb/project/dl/?id=1814&task=get
After Flashing Any Compatable Rom flash these every time Link: http://forum.xda-developers.com/devdb/project/dl/?id=508
They are the MF3 modules you will need them for wifi to work.
Transfer to sd card install just as you would a regular unknown source APK File..... Tick that in settings Security tab. Also hit your build number 20 times to unlock developer options and always have usb debugging on.
Now boot into safe-strap and dump a nandroid backup and you will be good to go. All thanks to the HashMan aka HashCode, And his sexifing SS. Okay now that you have a backup do anything of your hearts content. Just don't be fooling around with the bootloaders code.... this can really turn your cell phone into a paper weight.
Now here is a list of known compatable roms with SS:
Confirmed working ROMs Thanks to graydiggy http://forum.xda-developers.com/showthread.php?t=2428254
Google Play Edition 4.2.2
http://forum.xda-developers.com/showthread.php?t=2356276
http://forum.xda-developers.com/showthread.php?t=2341376
Deadly Venom
SHOStock
Darth Stalker
Graviton (Installs fine for some, will not install for others)
Goldeneye (May have issues)
Wicked ROM (T-Mobile) Input correct APN and change network mode to Auto LTE/GSM Will most likely lose root.
All Infamous TW Roms should work
Input correct APN settings for non AT&T ROMs (ie i9505 ROMs) to get LTE
Omega ROM i9505
Echo ROM i9505
Vision X i9505
BoBCaTROM i9505 (May not need to change APN)
Hyperdrive ROM. (May not be able to send SMS while on LTE)
Grab one create a rom slot and flash to your hearts content.
As for the 4.3 Odin files...... I think you can find them yourself it would be ignorant for me to post them for you.
@JohnMonsour I doubt he will read this he didn't even try to read the link I posted to try to help him. But great guide
Sent from my SAMSUNG-SGH-I337 using xda premium
Yeah. Unfortunately. I should re-post this guide for MF'd people though. What do you think? I think the the OP died..... LOL.
---------- Post added at 12:52 AM ---------- Previous post was at 12:51 AM ----------
[email protected] said:
Does he need arrows pointing to it or pilot navigation or something?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
This I lol'd at....... HAHAHAHAHA.
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.
Heyo, lets get started ruining this device even more! See if we can't brick it ey?
Anyways first off the battery is draining like a madman, 1% every 30 seconds or so. The thing is not getting the performance in games that it should be, using other devices with lower end hardware as a reference(1.1ghz quad core, adreno 305, 2gb ram one touch, and 1.2ghz quad core, adreno 306, 1.3gb ram kyocera), it keeps micro-stuttering while browsing chrome and doing basic actions with the UI, also when the battery is draining too(funny, sometimes while I have the charger plugged in and do basic activies such as chrome, youtube, read books, mess with menu settings the battery actually charges instead of deplete, but sometimes, seemingly always now, it depletes just as fast as though it was unplugged).
Anyways I have decided to try and customize the device with the plethora of information on here and all over the web for this device(after doing a lot more "research" of course and laying everything out for myself step by step to try to minimize failure.
First question is how much of a chance is there to brick the device installing TWRP alone? Really want to get that on there before doing anything, then install SuperSU from there with zip flash. And does it matter if I use a .tar or .img version of TWRP to flash with odin? The latest version of TWRP is in .img format and the tutorials I read say to use a .tar.
After that witch should I do try first, custom rom or custom kernel? What custom rom would be best at this point in time(5/13/2016) for this device, 100% compatible and fully tested. Also a kernel(unless overclocking can be unlocked within the custom rom, in witch case less chance of me ****ing up yet another android device).
One last thing, I really hope that even I am successful in doing all of this without ****ing up the phone that it does not turn out to be a fruitless effort, how much performance gains can I expect from all of this, custom rom, debloat after root, set sd as default storage after root(package does not belong to 2000 afterall), and then maybe a slight overclock on the cpu and gpu.
And thats all assuming that one day after getting all of this to work that one day I don't wake up and for no apparent reason boot up the phone and find its bootlooped or something without ever changing anything once all of this is done, I mean if I get the thing working as I would like it to work theres no more reason for me **** with it is there? Also I guess no reason to even have the thing if it aint gonna function how I need it to function right?
Thanks for the help though anyways, if anybody even decides to help me this time in a manner that they are not just "helping" just because the end result ****s me over.
Thanks again.
Oh one other problem I am having with the phone I was hoping a custom rom might fix, my Apps will not register as the correct size in Application manager. A 2gb game is showing up as 50mb total data, and when using "Move to SD Card" it only shows only like 200kb of data on the sd card, it does with with every single app on the phone. I know should not be like this because the last 2 phones I had were able to move every single byte of data from every one of the same exact apps to the SD card without an issue. Plus the application manager not registering the correct app size is just bugging me.
phenom2955 said:
Heyo, lets get started ruining this device even more! See if we can't brick it ey?
Anyways first off the battery is draining like a madman, 1% every 30 seconds or so. The thing is not getting the performance in games that it should be, using other devices with lower end hardware as a reference(1.1ghz quad core, adreno 305, 2gb ram one touch, and 1.2ghz quad core, adreno 306, 1.3gb ram kyocera), it keeps micro-stuttering while browsing chrome and doing basic actions with the UI, also when the battery is draining too(funny, sometimes while I have the charger plugged in and do basic activies such as chrome, youtube, read books, mess with menu settings the battery actually charges instead of deplete, but sometimes, seemingly always now, it depletes just as fast as though it was unplugged).
Anyways I have decided to try and customize the device with the plethora of information on here and all over the web for this device(after doing a lot more "research" of course and laying everything out for myself step by step to try to minimize failure.
First question is how much of a chance is there to brick the device installing TWRP alone? Really want to get that on there before doing anything, then install SuperSU from there with zip flash. And does it matter if I use a .tar or .img version of TWRP to flash with odin? The latest version of TWRP is in .img format and the tutorials I read say to use a .tar.
After that witch should I do try first, custom rom or custom kernel? What custom rom would be best at this point in time(5/13/2016) for this device, 100% compatible and fully tested. Also a kernel(unless overclocking can be unlocked within the custom rom, in witch case less chance of me ****ing up yet another android device).
One last thing, I really hope that even I am successful in doing all of this without ****ing up the phone that it does not turn out to be a fruitless effort, how much performance gains can I expect from all of this, custom rom, debloat after root, set sd as default storage after root(package does not belong to 2000 afterall), and then maybe a slight overclock on the cpu and gpu.
And thats all assuming that one day after getting all of this to work that one day I don't wake up and for no apparent reason boot up the phone and find its bootlooped or something without ever changing anything once all of this is done, I mean if I get the thing working as I would like it to work theres no more reason for me **** with it is there? Also I guess no reason to even have the thing if it aint gonna function how I need it to function right?
Thanks for the help though anyways, if anybody even decides to help me this time in a manner that they are not just "helping" just because the end result ****s me over.
Thanks again.
Click to expand...
Click to collapse
Well first it sounds like you need a new battery, I suggest having a couple and an external charger (it's great for gaming, just pop in a new fully charged battery). To install TWRP with Odin you need the tar file. The chance of Helicon with TWRP is almost zero, recovery is always overwritten when you flash a stock tar in Odin. So if something is messed up, just flash the stock tar and you are back to stock, grab it at www.sammobile.com . When you Odin TWRP make sure that you uncheck Auto Reboot in Odin. I would suggest my ROM as it is still being updated every few months, but I am biased. I use my S4 for gaming and this thing can handle PSP emulation when it is tweaked right.
Wicked X is my ROM and it's located here - http://forum.xda-developers.com/showthread.php?t=3115583
{
"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"
}
Ok thanks, a little reluctant to install an OS with the name "Wicked" though.
Any ideas why the stock Application Manager is being wacky, done several factory resets. For instance I have installed Fifa 16 about 5 times now just to see if it would fix the data readout in App manager, the Game is at least 1.5gb total data, app manager shows it as about 50-70mb, when using "Move to SD Card" it shows about 700kb of data on sd card.
Whats the deal?
Also before flashing TWRP with odin I have to unlock bootloader or something?
phenom2955 said:
Ok thanks, a little reluctant to install an OS with the name "Wicked" though.
Any ideas why the stock Application Manager is being wacky, done several factory resets. For instance I have installed Fifa 16 about 5 times now just to see if it would fix the data readout in App manager, the Game is at least 1.5gb total data, app manager shows it as about 50-70mb, when using "Move to SD Card" it shows about 700kb of data on sd card.
Whats the deal?
Also before flashing TWRP with odin I have to unlock bootloader or something?
Click to expand...
Click to collapse
No, bootloader is already unlocked. I can't tell you on the other without more information. What ROM are you on? Have you done any modifications? Have you Odined a full stock tar?
I bought this phone used on cl. Fully stock not a single mod on it as far as I am aware. The only thing I have done is factory reset.
It seems half the time as well when I Uninstall apps the data stays in misc section of storage manager. I have to go into recovery and clear cache and I get my space back. And misc section of storage manager will be back down to its normal size.
@ your comment about loader. You absolutely certain and no bs that if I attempt to flash something (even just twrp) it ain't gonna fail and go tit's up because I didn't unlock bootloader or something?
Just lost 2 phones already simply from uninstslling gltools after it failed to produce my desired results. Install went fine, but uninstslling rebooted the phones and got one caught in boot loop other just sits on manufacur er logo.
If asked why I was stupid enough to try it a second time I'll say I wasn't 100% sure it was absolutely gltools as the culprit.
Anyways this is the first device I have had with so much support with custom recoveries. Roms and kernels and even access to stock rom files. Would love to successfully apply some good stable/safe/and better running mods than the stock stuff though since I am convinced this hardware should be running better than it currently is!! But not trying anything for a while though till I've read as much as I can at least and have at least a few options for recovery should somehring go wrong.
Don't like being stuck with thumb up my ass stacking bricks, I am no mason.
Nickvanexel said:
I bought this phone used on cl. Fully stock not a single mod on it as far as I am aware. The only thing I have done is factory reset.
It seems half the time as well when I Uninstall apps the data stays in misc section of storage manager. I have to go into recovery and clear cache and I get my space back. And misc section of storage manager will be back down to its normal size.
@ your comment about loader. You absolutely certain and no bs that if I attempt to flash something (even just twrp) it ain't gonna fail and go tit's up because I didn't unlock bootloader or something?
Just lost 2 phones already simply from uninstslling gltools after it failed to produce my desired results. Install went fine, but uninstslling rebooted the phones and got one caught in boot loop other just sits on manufacur er logo.
If asked why I was stupid enough to try it a second time I'll say I wasn't 100% sure it was absolutely gltools as the culprit.
Anyways this is the first device I have had with so much support with custom recoveries. Roms and kernels and even access to stock rom files. Would love to successfully apply some good stable/safe/and better running mods than the stock stuff though since I am convinced this hardware should be running better than it currently is!! But not trying anything for a while though till I've read as much as I can at least and have at least a few options for recovery should somehring go wrong.
Don't like being stuck with thumb up my ass stacking bricks, I am no mason.
Click to expand...
Click to collapse
100%, Sprint doesn't lock bootloaders (though Samsung has started to). You may have to turn off the an option in Settings/Security, I think it's called Write Protection, it won't let you Odin anything if it is on.
I have a sprint sph-720T
I installed TWRP using ODIN
then reboot in recovery, put OCTOS-M on to internal memory and wipe the cache davik
install the OCTOS-M from zip file then install GAPPS from zip.
BOOOM! you have a rooted android 6.0.1 ! longer battery life.
EDIT: if you need direct links to the files, just ask.
Mangodreads said:
I have a sprint sph-720T
I installed TWRP using ODIN
then reboot in recovery, put OCTOS-M on to internal memory and wipe the cache davik
install the OCTOS-M from zip file then install GAPPS from zip.
BOOOM! you have a rooted android 6.0.1 ! longer battery life.
EDIT: if you need direct links to the files, just ask.
Click to expand...
Click to collapse
Have you had any issues flashing the s4 to 6.0? It would be great if you added direct links. Thanks.
ABERBER1986 said:
Have you had any issues flashing the s4 to 6.0? It would be great if you added direct links. Thanks.
Click to expand...
Click to collapse
1. Put the Custom Rom Zip and the GAPPS zip on the phones memory card and then turn off the phone
2. Put the phone in download mode, connect to the computer via usb and run ODIN
Select AP and the select the TWRP recovery file. - Click Start - Once its finished
3. Put the phone in recovery mode - go to wipe, clear cache/davik a few times
go to install and select the Custom Rom Octos 6.0.1 that you put on the phones memory.
install it and then install GAPPS zip right afterwards
once those are installed reboot the phone and you are good.
These links are for user with Sprints galaxy s4 sph-720T ONLY
This is the TWRP recovery
https://dl.twrp.me/jfltespr
This link is to 6.0.1 Custom Rom by OCTOS
https://www.teamoctos.com/download/M_release/jfltespr/OCT-M-R1-6.0.1-20160319-jfltespr.zip
This is a link for GAPPS (google apps, playstore etc) - select the "variant" you want
http://opengapps.org/?arch=arm&api=6.0&variant=micro
Mangodreads said:
1. Put the Custom Rom Zip and the GAPPS zip on the phones memory card and then turn off the phone
2. Put the phone in download mode, connect to the computer via usb and run ODIN
Select AP and the select the TWRP recovery file. - Click Start - Once its finished
3. Put the phone in recovery mode - go to wipe, clear cache/davik a few times
go to install and select the Custom Rom Octos 6.0.1 that you put on the phones memory.
install it and then install GAPPS zip right afterwards
once those are installed reboot the phone and you are good.
These links are for user with Sprints galaxy s4 sph-720T ONLY
This is the TWRP recovery
https://dl.twrp.me/jfltespr
This link is to 6.0.1 Custom Rom by OCTOS
https://www.teamoctos.com/download/M_release/jfltespr/OCT-M-R1-6.0.1-20160319-jfltespr.zip
This is a link for GAPPS (google apps, playstore etc) - select the "variant" you want
http://opengapps.org/?arch=arm&api=6.0&variant=micro
Click to expand...
Click to collapse
Please advice which version of twrp you used. Because I am unable to flash thru through odin
bump........
earthworm82 said:
Please advice which version of twrp you used. Because I am unable to flash thru through odin
Click to expand...
Click to collapse
The link for teamoctos doesn't seem to work.
vikingjerr said:
The link for teamoctos doesn't seem to work.
Click to expand...
Click to collapse
You could just go their thread in the Android Development section[emoji6]
Wicked 10.9
bilgerryan said:
You could just go their thread in the Android Development section[emoji6]
Click to expand...
Click to collapse
I just downloaded Wicked 10.9 but am not sure I have all the files needed. In the first page it mentions to load the 720t conversion file and a kernal file.
Later I saw that the kernal file was include. I don't know if I should flash one, two or three files.
vikingjerr said:
I just downloaded Wicked 10.9 but am not sure I have all the files needed. In the first page it mentions to load the 720t conversion file and a kernal file.
Later I saw that the kernal file was include. I don't know if I should flash one, two or three files.
Click to expand...
Click to collapse
Three, the v11.0 update last.