Okay, I'm relatively new to Android phones in general, but recently purchased a captivate and absolutely love it. I upgraded to the unofficial leaked version of froyo and am now wanting to try out a custom rom. The issue I'm having is as follows:
I've read that before flashing a custom rom, it is recommended to flash back to the stock rom first. When I tried that, I flashed back to the stock rom (pre OTA update that fixed the 3 buttom recovery mode issue) and was not able to get into recovery mode. I then tried to do the ota update and it kept failing. I then flashed back to the leaked froyo rom via download mode and am basically stuck here. My question is two fold. Does anyone have a link to the stock rom file that has the latest update (I forget the version number) or can I just flash to a new custom rom from the leaked froyo build? Would that build be considered stock?
jcr81 said:
Okay, I'm relatively new to Android phones in general, but recently purchased a captivate and absolutely love it. I upgraded to the unofficial leaked version of froyo and am now wanting to try out a custom rom. The issue I'm having is as follows:
I've read that before flashing a custom rom, it is recommended to flash back to the stock rom first. When I tried that, I flashed back to the stock rom (pre OTA update that fixed the 3 buttom recovery mode issue) and was not able to get into recovery mode. I then tried to do the ota update and it kept failing. I then flashed back to the leaked froyo rom via download mode and am basically stuck here. My question is two fold. Does anyone have a link to the stock rom file that has the latest update (I forget the version number) or can I just flash to a new custom rom from the leaked froyo build? Would that build be considered stock?
Click to expand...
Click to collapse
Don't flash back to stock unless absolutely necessary. Otherwise, it's pointless and just creates additional opportunities for things to mess up and brick your phone. Wiping your data and cache partitions with CWM recovery should be sufficient for a clean ROM install.
As for the stock ROM you're looking for, it depends on your Captivate. If your phone came with JF6 and working button combos, and is an older build (1009 or older), this should work fine: http://forum.xda-developers.com/showthread.php?t=731989
If your button combos were disabled, either use this: http://forum.xda-developers.com/showthread.php?t=818439 -OR- the first link followed by installing the OTA update (be careful, as an incomplete OTA update can perma-brick your phone).
If your phone is a build 1010 or came with JH7, the stock ROM you need is JH2. Follow this guide: http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
need newest firmware for the sprint variant..flashed renovate rom..had lots of ui crashes..had to reflash elementalx custom kernal that i had flashed when useing mulitirom ..now seems no roms will load correctly without reflashing the elementalx kernal that another issiue..but for now thought updateing the firmware would help the latest i can find for sprint moild/op6b70000 cid/super cid ...is version 2.16.654.4...is sprirnt getting left behind or something have we not updated past 4.3???..isnt the 2.16.654.4 the 4.3 version of android??....every thread ive found never has updated firmware for sprint..untill i now i diddnt kniow the moild num..had to match up thought haveing supercid was good to flash any firmware upgrade or downgradeing ......guess not?..i spend lot of time reading everyday i hardly never ask questions..in fact this second attempt asking anything in bout 2 years..thank you for your time in advance..LOVE XDA!!!..also link to my stock kernal would be great..i made a back up of boot in recovery before flashing eleamentalx kernal but diddnt rename it..afraid to jus guess
There is no newer firmware than the version for software version 2.16.65x.4, which is Android 4.4.3.
Hi,
I had dual sim Moto G 2014 with Stock Lollipop 5.0.2. This firmware in italy with the H3G provider, has a major bug: when I call someone and he answer, after I close, in the recent calling I can see "Unknown Number" or "Private Number", and I can't see the number of my contact. I Solve this bug with the Resurrection Remix ROM (ONLY THE VERSION 5.3.8 stable with LP 5.0.2, the newer version have still the bug) and with the Quantum Rom version 3.2.1 stable. According to me, the problem is the baseband/modem, so I think that i can backup the Baseband of the Resurrection Remix that works, and restore it after falsh the last build with LP 5.1.
So I tried looking for a guide on web but I have not found. Can you help me to backup the baseband and restore it?
Thanks
that bug have no relation to the baseband.
I believe that bug is from the ROM you are using or some wrong config that you made, or a app that you installed and is causing it.
The base band file is not present in custom ROM, according to my knowledge the baseband file is ''NON-HLOS.bin'' that is inside the XML file of a stock ROM, and wen you flash a custom ROM those ROM dont have the baseband file, that way it doesn't flash it (baseband files) and the ROM can be flash to any device from any region of the planet. Of course in some cases wen you use a lollipop custom ROM you need to be, before flash it on the stock lollipop ROM in that way you have all the files necessary to run the custom ROM, that included baseband file that are using on lollipop.
If that is true you have a bug on the stock ROM noting related to the modem files.
If the ROM that you flash have only system and boot.img it doesn't contains modem files...
you can check if all that is true by flashing back the stock, take a print of ''about a phone'' that shoes baseband version, after you flash a new ROM and see if that change.
Or just find a original moto g pic from ''about a phone'' from a moto g of yours region.
I'm running an N910T with Rapture 8.2. As this ROM apparently isn't under development or support any longer, I'd like to move to another ROM that is. I'd also like to update my baseband to N910TUVU2DOK2. To update the baseband, do I need to ODIN back to stock and upgrade from there, or can I simply ODIN the baseband and move forward? I believe that I'm currently on COG1, but can't tell because I'm running a backup just now.
dmathis said:
I'm running an N910T with Rapture 8.2. As this ROM apparently isn't under development or support any longer, I'd like to move to another ROM that is. I'd also like to update my baseband to N910TUVU2DOK2. To update the baseband, do I need to ODIN back to stock and upgrade from there, or can I simply ODIN the baseband and move forward? I believe that I'm currently on COG1, but can't tell because I'm running a backup just now.
Click to expand...
Click to collapse
You always need to Odin to the full firmware that matches the ROM you want to use. Please keep in mind that once you go to 5.1.1, you'll be stuck on lollipop bootloader.
Sent from my SM-N910T using Tapatalk
Thanks! Should I ODIN to stock, or straight to the new ROM? I rooted and flashed my old note 2 gobs of times, but the note 4 I'm not that sure about.
dmathis said:
Thanks! Should I ODIN to stock, or straight to the new ROM? I rooted and flashed my old note 2 gobs of times, but the note 4 I'm not that sure about.
Click to expand...
Click to collapse
You use Odin to put stock firmware on and to root and add TWRP. You use TWRP to flash ROM's.
Sent from my SM-N910T using Tapatalk
Thanks! That's just what I needed.
You're very welcome
Sent from my SM-N910T using Tapatalk
Pick_A_Name said:
You always need to Odin to the full firmware that matches the ROM you want to use. Please keep in mind that once you go to 5.1.1, you'll be stuck on lollipop bootloader.
Click to expand...
Click to collapse
I have gone back and forth between 5.1.1, 5.0.1, and 4.4.4 roms by using odin to flash the COG2, COD6, or ANK4 firmware first, then using odin to flash autoroot and TWRP. Then use TWRP to flash the desired rom. I have no problem going from lollipop to kitkat and back. I have used the COG2 firmware for all the 5.1.1 roms, like Texxodus, Resurrection, Slim, CM12, etc. I have used COD6 for 5.0.1 like Alliance, I have used ANK4 for Firekat. I have never had a problem reverting between any of them.
Why is DOK2 different? Does it trip some kind of hardware switch, like knox? If I was on it and used odin to flash, say, the kitkat firmware, what happens? Does odin no longer work when you're on DOK? Does it crash? Does the flash appear to work but it stays on DOK? Does it flash the firmware but bootloop? Does it brick the phone? I always thought that odin flashed firmware to the lowest level so that as long as you could connect the phone to a PC and had a good firmware load, you could restore it.
I have gone back and forth between 5.1.1, 5.0.1, and 4.4.4 roms by using odin to flash the COG2, COD6, or ANK4 firmware first, then using odin to flash autoroot and TWRP. Then use TWRP to flash the desired rom. I have no problem going from lollipop to kitkat and back. I have used the COG2 firmware for all the 5.1.1 roms, like Texxodus, Resurrection, Slim, CM12, etc. I have used COD6 for 5.0.1 like Alliance, I have used ANK4 for Firekat. I have never had a problem reverting between any of them.
Why is DOK2 different? Does it trip some kind of hardware switch, like knox? If I was on it and used odin to flash, say, the kitkat firmware, what happens? Does odin no longer work when you're on DOK? Does it crash? Does the flash appear to work but it stays on DOK? Does it flash the firmware but bootloop? Does it brick the phone? I always thought that odin flashed firmware to the lowest level so that as long as you could connect the phone to a PC and had a good firmware load, you could restore it.
I am sorry to belabor this, but nothing I have read has explained this. All you get is that once you are on DOK2, you can't go back, but no one seems to know why and no one appears to have tried using Odin to flash a previous firmware and can answer the questions in the previous paragraph.
phoneturf said:
I have gone back and forth between 5.1.1, 5.0.1, and 4.4.4 roms by using odin to flash the COG2, COD6, or ANK4 firmware first, then using odin to flash autoroot and TWRP. Then use TWRP to flash the desired rom. I have no problem going from lollipop to kitkat and back. I have used the COG2 firmware for all the 5.1.1 roms, like Texxodus, Resurrection, Slim, CM12, etc. I have used COD6 for 5.0.1 like Alliance, I have used ANK4 for Firekat. I have never had a problem reverting between any of them.
Why is DOK2 different? Does it trip some kind of hardware switch, like knox? If I was on it and used odin to flash, say, the kitkat firmware, what happens? Does odin no longer work when you're on DOK? Does it crash? Does the flash appear to work but it stays on DOK? Does it flash the firmware but bootloop? Does it brick the phone? I always thought that odin flashed firmware to the lowest level so that as long as you could connect the phone to a PC and had a good firmware load, you could restore it.
I am sorry to belabor this, but nothing I have read has explained this. All you get is that once you are on DOK2, you can't go back, but no one seems to know why and no one appears to have tried using Odin to flash a previous firmware and can answer the questions in the previous paragraph.
Click to expand...
Click to collapse
Try it and report back. The bootloader can never be downgraded once it has been updated but I have heard of people odining back to kitkat from 5.1.1 and them getting it to work. Not sure how it was done but they did it.
DeeXii said:
Try it and report back. The bootloader can never be downgraded once it has been updated but I have heard of people odining back to kitkat from 5.1.1 and them getting it to work. Not sure how it was done but they did it.
Click to expand...
Click to collapse
You say the bootloader can never be downgraded once it has been updated. Okay, that's what everyone says. But is it true? No one seems to know. And if it is true, why? I find this very odd that no one knows.
My current favorite rom is Alliance since for me it has the best battery life and the least lag of the roms I have tried, so I don't want to take a chance that I can no longer run it if I flash DOK2 and don't like it.
phoneturf said:
You say the bootloader can never be downgraded once it has been updated. Okay, that's what everyone says. But is it true? No one seems to know. And if it is true, why? I find this very odd that no one knows.
My current favorite rom is Alliance since for me it has the best battery life and the least lag of the roms I have tried, so I don't want to take a chance that I can no longer run it if I flash DOK2 and don't like it.
Click to expand...
Click to collapse
go here for your answers
http://forum.xda-developers.com/not...-solution-to-emmcread-write-problems-t3281179
My understanding is that it's part of a new "security policy", I believe implemented by Tmo. My source of this info isn't related directly to my Note 4, but last month I Jumped my tablet to a new Samsung Galaxy Tab S2 that came loaded with 5.1.1. The day after picking it up I got a notification for a firmware update, still 5.1.1 (small size), screenshot of the "release notes" attached below. I didn't take the update and froze updates in TiBu. There's not a whole lot of development for that device yet and I think that I would have lost root if I had taken it.
I'm all for "security", but disabling users' ability to downgrade firmware hardly seems like much of a contribution to that end. IMO this is a disappointing development, and has much greater potential to affect "power users" vs. "regular users" as I doubt that a regular user downgrading the firmware on their device to their determent is something that even happens... ever.
jazzmachine said:
My understanding is that it's part of a new "security policy", I believe implemented by Tmo. My source of this info isn't related directly to my Note 4, but last month I Jumped my tablet to a new Samsung Galaxy Tab S2 that came loaded with 5.1.1. The day after picking it up I got a notification for a firmware update, still 5.1.1 (small size), screenshot of the "release notes" attached below. I didn't take the update and froze updates in TiBu. There's not a whole lot of development for that device yet and I think that I would have lost root if I had taken it.
I'm all for "security", but disabling users' ability to downgrade firmware hardly seems like much of a contribution to that end. IMO this is a disappointing development, and has much greater potential to affect "power users" vs. "regular users" as I doubt that a regular user downgrading the firmware on their device to their determent is something that even happens... ever.
Click to expand...
Click to collapse
Canadian note 4 dont seem to have the security lock on them since i rolled back to 5.0.1 bootloader but yes it wont let u roll back to any other 5.1.1 bootloader
U can try to download canadian BOE2 firmware and flash that since tmobile nd canada r pretty mch the same
This can be very dangerous so be cautious
phoneturf said:
I have gone back and forth between 5.1.1, 5.0.1, and 4.4.4 roms by using odin to flash the COG2, COD6, or ANK4 firmware first, then using odin to flash autoroot and TWRP. Then use TWRP to flash the desired rom. I have no problem going from lollipop to kitkat and back. I have used the COG2 firmware for all the 5.1.1 roms, like Texxodus, Resurrection, Slim, CM12, etc. I have used COD6 for 5.0.1 like Alliance, I have used ANK4 for Firekat. I have never had a problem reverting between any of them.
Why is DOK2 different? Does it trip some kind of hardware switch, like knox? If I was on it and used odin to flash, say, the kitkat firmware, what happens? Does odin no longer work when you're on DOK? Does it crash? Does the flash appear to work but it stays on DOK? Does it flash the firmware but bootloop? Does it brick the phone? I always thought that odin flashed firmware to the lowest level so that as long as you could connect the phone to a PC and had a good firmware load, you could restore it.
I am sorry to belabor this, but nothing I have read has explained this. All you get is that once you are on DOK2, you can't go back, but no one seems to know why and no one appears to have tried using Odin to flash a previous firmware and can answer the questions in the previous paragraph.
Click to expand...
Click to collapse
I have been try a lot of time for use odin to flash cog2 or cod6 from dok2. And it allway fail in odin. And you will receive a notice in the download mode screen like that o"Odin fai, binary =2>1". So you can't flash succesfull in odin.
And evething can't change. I have read 5.1.1 plicy and it also said that we can't downgrade from t mobile phone.lol
Perhaps development can recompile bootloader without tmo security and use Canadian firm to patch.
I just upgrade from COG2 to DOK2. Is there any difference? Which is better?
I have the N910T.
Dok2 has been reported to have improved performance and battery life than cog2 but cannot be downgraded.
Bruce lee roy said:
Dok2 has been reported to have improved performance and battery life than cog2 but cannot be downgraded.
Click to expand...
Click to collapse
I see. My cook ROM say use DOK2. I didnt know about the downgrade. I guess its ok and thanks for the info.