I am on Chobits Digital v2 rom and when i got to setting and software update it tells me there is an update for my mobile so if i update will i go back to stock rom or what will happen??
plz can any one tell me thanks!!
My advice would be not to update or else your phone may brick....it's an update to stock rom and not the custom rom....
Sent from my Galaxy Young
if you installed it, you will be rebooted and will have a message "cannot install software update file" or something like that
No. That doesn't work for Custom ROMS. It is for Stock ROM. Your phone will may be bricked or bootlooped when you try updating it. In my case, i didn't use that but i tried kies but kies doesn't detect my phone because i'm not using stock ROM.
Buddy i think there is a faq sticky
So plz use that
Keep our forum clean
Related
Hello all,
Today I decided to go back to stock ROM via Odin.
I was using Milestone 6 based on new cm9. I did a factory reset via settings.
Then turned off my mobile and went to download mode.
Odin recognized my mobile and started the flashing process.
It showed pass message after 5 mins.
Now my mobile is bootloop. Samsung logo just keeps appearing again and again.
I tried to access recovery but I cant access it.
What am I supposed to do.
Any help would be highly appreciated.
Thank you
Hi
I was have like your problem (the same!!)
So what I do is firstly flash the 2.3.3 via Odin, then I flash again the 2.3.6 via Odin
When I flash 2.3.6 without flash firstly 2.3.3 , it dosent work ... the samsung logo repeat it selfs ...
That's what I do..... if some one haves easy way plz help us?!!!!
Sent from my GT-S5660 using Tapatalk 2
Thanks it worked I am not flashing to 2.3.6 and will stick to 2.3.3
pranjaldixit said:
Thanks it worked I am not flashing to 2.3.6 and will stick to 2.3.3
Click to expand...
Click to collapse
'Well it's fine to stick with your 2.3.3 and if you want to go to 2.3.6 you dont have to use odin, just go to samsung's official padge, search for your phone, install samsung kais and brchause you tawe rhe official android rom for Gio you will be soon notified that a higher wersion of android is awailable, so you can update to the latest version with kais :good:
So I rooted my phone and installed the latest CWM recovery but every time I try to install any custom rom I get a status 7 error and it says something along the line of asserts failed ro.product.drvice == d2att. I've tried using TWRP, I've unrooted and installed stock, nothing seems to work. Last week I was running Jellybam fine for about 2 days, got stuck in bootloop, tried numerous ways to fix it, ended up returning to stock but now I cannot flash anything. Help me please
The status 7 error happens when the ROM ur about to flash, checks to see if the model of ur phone is compatible with said ROM. Its a good thing(safety mechanism) but can be a pain at the same time. What version of cwm are u using? Download the latest cwm recovery thru the ROM manager app and that can sometimes fix the issue. What ROM are you trying to install?
Sent from my SAMSUNG-SGH-I337 using xda premium
I think 6.0.2.3? not 100% sure though.. and I need to be rooted in order for rom manager to work... I tried using it but it kept saying the flash failed.. I'm using the root recovery. I've tried flashing CM 10.1 and RC5 as well as the latest and 3 before that Jellybam Roms
shewantsmyduck said:
I think 6.0.2.3? not 100% sure though.. and I need to be rooted in order for rom manager to work... I tried using it but it kept saying the flash failed.. I'm using the root recovery. I've tried flashing CM 10.1 and RC5 as well as the latest and 3 before that Jellybam Roms
Click to expand...
Click to collapse
Latest cwm is at 6.0.3.1
I think you're getting a little confused.
You need to be rooted to have any custom recovery installed, so right off the bat you are rooted. You shouldn't flash anything with rom manager, it can cause serious harm to your phone. Tom manager is best for just updating your recovery.
There are two main reasons for a status7 error, out of date recovery or an out of date bootloader.
Update your recovery to 6.0.3.1 and he to flash it again, if it comes back you'll need to update your bootloader a two second search in these threads will provide you with a large handful of threads where people had identical issues as you
Sent from my SGH-I747 using xda app-developers app
Checked my bootloader and it says i747UCDLK3 and I think that's the latest... I'll root and install latest CWM through rom manager once I get home
And one question though... I tried using TWRP 2.5 (the latest) and I still got the status 7 error...?
shewantsmyduck said:
So I rooted my phone and installed the latest CWM recovery but every time I try to install any custom rom I get a status 7 error and it says something along the line of asserts failed ro.product.drvice == d2att. I've tried using TWRP, I've unrooted and installed stock, nothing seems to work. Last week I was running Jellybam fine for about 2 days, got stuck in bootloop, tried numerous ways to fix it, ended up returning to stock but now I cannot flash anything. Help me please
Click to expand...
Click to collapse
Can you flash any stock modded rom's ? You state you went back to stock but what method did you use to go back to stock ?
Why oh why were you using jellybam...
My cousin has it on his Verizon GS3 and it works perfectly fine so I thought I'd give it a shot. To go back to stock I followed some unroot and return to stock I found online.. not sure of the link. It basically consisted of flashing it in Odin and returned it back to stock 4.0.4 which I then updated to 4.1.1 using att ota. I'm not sure if it was a a modded stock rom or not. And I really don't feel like going back through that mess again only to flash it and get stuck in another boot loop I want to be pretty positive that it will work :/
shewantsmyduck said:
My cousin has it on his Verizon GS3 and it works perfectly fine so I thought I'd give it a shot. To go back to stock I followed some unroot and return to stock I found online.. not sure of the link. It basically consisted of flashing it in Odin and returned it back to stock 4.0.4 which I then updated to 4.1.1 using att ota. I'm not sure if it was a a modded stock rom or not. And I really don't feel like going back through that mess again only to flash it and get stuck in another boot loop I want to be pretty positive that it will work :/
Click to expand...
Click to collapse
The ODIN flash to stock 4.0.4 probably installed the old ics bootloaders, and the ota update to 4.1.1 may not have included the new jb bootloaders.
Ok so what is the newest bootloader? I downloaded the root checker that allows you to see your bootloader version and it's on i747UCDLK3.
shewantsmyduck said:
Ok so what is the newest bootloader? I downloaded the root checker that allows you to see your bootloader version and it's on i747UCDLK3.
Click to expand...
Click to collapse
That's the right one
Sent from my SGH-I747 using xda premium
So what should I do now then :s
You're trying to flash the wrong rom for your device, or you're not using the right recovery for your device. What Galaxy S3 model do you have? On which carrier are you and where did you buy the phone?
I have an AT&T i747 that I got at an AT&T store. The Rom is correct as I've downloaded it numerous times and I've tried the latest TWRP recovery and still received the error.
I'm going to try and flash a factory image tomorrow from the development section and root afterwards. As Michael3214 pointed out in a pm, the issue may be that my phones id has changed, hopefully a factory image will fix that.
Hey All,
I have a quick question my Note 2 on straight talk is haaving a bit of a issues. it tried to do a OTA update but failed as I have a rooted device. Now I cant get the s.w update icon to go away. I try to do a force stop from running applications aslo I cant shut off the notification. Someone told me I can unroot my device run the update and then reroot the device to apply the OTA update, would that be work it? Im trying to find a 4.4.4 ROM that I can flash via odin because when i try to do it through philz it always fails
Can anyone help me or point me in the right direction?
Thanks,
Shawna
Should I unroot via super user and then reroot
It's not being rooted that causes updates to fail, it's the custom recovery that stops it.
Ok so what would you recommend. I'm looking for a romantic 4.4.4 that I can flash with odin. Rather than from philz
Because all the 4.4.4 Roms I have on my SD card fail. It odin so all flash able roms end in a .m5 type of file
Hi everyone I hope this is not a repetition of some old thread (I tried but couldn't find though).
I was using my note 2 (T889) on stock 4.3 which i previously flashed via odine. A couple of days ago i came by this good looking kitkat based rom ( eZKAT v2.0 ) and went on to try it. the rom flashed flawlessly and after flashing my modem i got the signals as well but the wifi was not working. tried using dr. ketans wifi patch but didnt get the wifi to working. Anyhow, I decided to go back to 4.3 via odine. The odine flashing completed successfully but i got stuck on T-mobiles boot screen for hours.
Is there anything called "you cant go back to 4.3 from 4.4.2"? If yes, then whats the way around? I really need to go back to the stock.
Thanks.
zetrixNoob said:
Hi everyone I hope this is not a repetition of some old thread (I tried but couldn't find though).
I was using my note 2 (T889) on stock 4.3 which i previously flashed via odine. A couple of days ago i came by this good looking kitkat based rom ( eZKAT v2.0 ) and went on to try it. the rom flashed flawlessly and after flashing my modem i got the signals as well but the wifi was not working. tried using dr. ketans wifi patch but didnt get the wifi to working. Anyhow, I decided to go back to 4.3 via odine. The odine flashing completed successfully but i got stuck on T-mobiles boot screen for hours.
Is there anything called "you cant go back to 4.3 from 4.4.2"? If yes, then whats the way around? I really need to go back to the stock.
Thanks.
Click to expand...
Click to collapse
I had this problem on my Note also. Downgrading versions of Android requires a data wipe. You will need to reflash your 4.4 ROM then backup your data if you want. Save your backup to your computer then install the 4.3 image.
Sent from my Nexus 7
EverDawn4 said:
I had this problem on my Note also. Downgrading versions of Android requires a data wipe. You will need to reflash your 4.4 ROM then backup your data if you want. Save your backup to your computer then install the 4.3 image.
Sent from my Nexus 7
Click to expand...
Click to collapse
I already tried that but still the booting stuck on the t-mobile logo. I read somewhere that locked bootloader don't let you downgrade to previous version. Is this true?
In that case. Try finding a 4.3 rom that's close to stock.
Sent from my Nexus 7
The locked bootloader is always in stock firmwares i.e 4.3 for the Note 2 but not in custom roms meaning u can even install Lollipop custom on it & downgrade smoothly, i have done that many times. The problem is 4.3 stock firmware has locked bootloader hence downgrading still keeps u in 4.3 bootloader even if u remove all the KNOX files.
Stuck trying to downgrade from custom 5.1.1 to stock 4.3
Hi, i have a problem like this, upgrade to a custom 5.1.1 and then sell the phone, the new owner wants to have it stock, i try to downgrade to 4.3 but i cant, in odin i set the phone to flash it but seems like it doesn`t recognize the phone and i dont know why, so, i decided to try in recovery mode installing from the sd card but the sistem abort, so, i don`t know what to do, i`ll appreciates any help, sorry for my english, i do my best. (i have root access before upgrated to 5.1.1).
Hey!
I just rooted my phone and installed S6 lollipop ported rom on it, but now I want to install S5 port. It says first I have to install stock rom. How do I do that? I read about downloading rom from samsung-updates, but I don't know which one is mine
Please help!
Hi,
Go to Settings - About Phone and see your baseband.
Good luck
Thanks!