Related
Hopefully I have an easy one.
I am trying to flash the stock rom back to my S3. My usb port is broken and I need to send it in for service. I have the the stock recovery back on, and when I try to flash the stock rom from the sd card I keep getting verification error, and after some research it seems its because the image I have is not signed by Samsung. I have tried searching for awhile now trying to get some information on how to get the stock rom flashed back via the stock recovery and I have hit a wall. Can anyone give me some pointers on how I can get this loaded up?
Thank you!
You cannot flash firmware from within stock recovery. Reinstall cwm, flash stock touchwiz firmware and then proceed with resetting/unrooting your device
Or Odin flash a stock ROM.
mrhaley30705 said:
Or Odin flash a stock ROM.
Click to expand...
Click to collapse
His usb port is broken.
If you are still rooted and can get into your device, mobile odin is an option
xBeerdroiDx said:
His usb port is broken.
If you are still rooted and can get into your device, mobile odin is an option
Click to expand...
Click to collapse
I was still rooted. I downloaded the official rom and put it on the sd card. Was able to flash with Mobile Odin Pro and it worked great.
Thanks!
That app is awesome.
mvjunkie said:
I was still rooted. I downloaded the official rom and put it on the sd card. Was able to flash with Mobile Odin Pro and it worked great.
Thanks!
That app is awesome.
Click to expand...
Click to collapse
Yes it is. Glad you're sorted out and on your way. Cheers buddy
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.
Hi,
I just got my Galaxy S III and decided to root it. I had done it before. I made a mistake and it wouldn't reboot, so, I had to put the stock rom on the device again. I found the stock rom, which was a 4.0.4 version and flashed it with no problem. But, then, the automatic update installed the 4.1.1 version. Here is when the problem starts: after installation, when I try to go into the recovery mode to clear the cache, the android is dead with a read triangle above it. I don't know what to do since I want to flash a custom rom.
Oh, a small detail that might be important. The stock rom is flashed using ODIN, but the reboot process is so lengthy, I have to remove the battery and then clear the cache before it fully reboots. At this stage (still 4.0.4) there is no problem with recovery mode and everything is fine. It is only after the update to 4.1.1 that the problem starts.
Your helps are much appreciated.:angel:
rezaasl2000 said:
Hi,
I just got my Galaxy S III and decided to root it. I had done it before. I made a mistake and it wouldn't reboot, so, I had to put the stock rom on the device again. I found the stock rom, which was a 4.0.4 version and flashed it with no problem. But, then, the automatic update installed the 4.1.1 version. Here is when the problem starts: after installation, when I try to go into the recovery mode to clear the cache, the android is dead with a read triangle above it. I don't know what to do since I want to flash a custom rom.
Oh, a small detail that might be important. The stock rom is flashed using ODIN, but the reboot process is so lengthy, I have to remove the battery and then clear the cache before it fully reboots. At this stage (still 4.0.4) there is no problem with recovery mode and everything is fine. It is only after the update to 4.1.1 that the problem starts.
Your helps are much appreciated.:angel:
Click to expand...
Click to collapse
So you can esily flash 4.0.4 with no hiccup but then you get the update (kies I assume) and it fails ?
Do you want to be rooted ?
if not just flash the stock 4.1.1 from Sammobile in Odin and update that way to avoid that Kies garbage
hednik said:
So you can esily flash 4.0.4 with no hiccup but then you get the update (kies I assume) and it fails ?
Do you want to be rooted ?
if not just flash the stock 4.1.1 from Sammobile in Odin and update that way to avoid that Kies garbage
Click to expand...
Click to collapse
Thanks for the reply. I do want to be rooted. Mine is an i747. Can you attach the link so I don't download the wrong one?
rezaasl2000 said:
Thanks for the reply. I do want to be rooted. Mine is an i747. Can you attach the link so I don't download the wrong one?
Click to expand...
Click to collapse
Find your carrier and flash one of these in Odin as they are pre-rooted.
http://forum.xda-developers.com/showthread.php?t=1739426
hednik said:
Find your carrier and flash one of these in Odin as they are pre-rooted.
http://forum.xda-developers.com/showthread.php?t=1739426
Click to expand...
Click to collapse
Thank you so much for the reply. After purchasing my g3 from AT&T, I used the same link you just sent me to flash the device. But it didn't work even though I changed the USB port. It installs SuperSU, but the recovery fails. I will try it one more time before and report back to you.
thanks again.
rezaasl2000 said:
Thank you so much for the reply. After purchasing my g3 from AT&T, I used the same link you just sent me to flash the device. But it didn't work even though I changed the USB port. It installs SuperSU, but the recovery fails. I will try it one more time before and report back to you.
thanks again.
Click to expand...
Click to collapse
It failed again (dead android with a red triangle above it). I have checked the ODIN version, whether the md5 file was downloaded correctly. I'm very frustrated.
rezaasl2000 said:
It failed again (dead android with a red triangle above it). I have checked the ODIN version, whether the md5 file was downloaded correctly. I'm very frustrated.
Click to expand...
Click to collapse
So you can't flash anything 4.1.1 or 4.1.2 ? That's odd that only 4.0.4 works. Does it fail with Kies too ?
What about just rooting using CF-auto root or casual and then flashing a rom ?
hednik said:
So you can't flash anything 4.1.1 or 4.1.2 ? That's odd that only 4.0.4 works. Does it fail with Kies too ?
What about just rooting using CF-auto root or casual and then flashing a rom ?
Click to expand...
Click to collapse
Okay, so, this method didn't work either. I went back to the link you sent me with the pre-rooted version and flashed it. Now, it has the same problem (dead android with red triangle), but RootChecker says that I'm rooted. I don't know what difference that makes.
Any thoughts?
rezaasl2000 said:
Okay, so, this method didn't work either. I went back to the link you sent me with the pre-rooted version and flashed it. Now, it has the same problem (dead android with red triangle), but RootChecker says that I'm rooted. I don't know what difference that makes.
Any thoughts?
Click to expand...
Click to collapse
So cf auto root worked but you can't flash ? You need to install a recovery. Can you flash a custom recovery in Odin or mobile Odin ?
Sent from my SGH-I747 using xda premium
hednik said:
So cf auto root worked but you can't flash ? You need to install a recovery. Can you flash a custom recovery in Odin or mobile Odin ?
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
So, I finally figured it out. I used the samsung galaxy s3 toolkit to install the stock firmware and then I updated it on the phone. Next, I went back to the toolkit and installed the most recent version of CWM on it and everything just worked beautifully. I have LiquidSmooth installed and it works just great.
thank you for the help hendik.
:good:
so i have a rooted at&T galaxy s3 on the latest stock firmware which i guess is 4.3. i tried flashing resurrection rom which was kit kat and it failed. so i restored my back up and the phone would get stuck on the splash screen. so i formated the whole phone and forgot to save my backup to my sdcard. twrp now says that i have no OS installed and also says i am not rooted anymore. im scared and need a little assistance. i just want to get it going.
Just flash the latest TWRP, copy a custom ROM to your phone, boot into TWRP, and flash it.
audit13 said:
Just flash the latest TWRP, copy a custom ROM to your phone, boot into TWRP, and flash it.
Click to expand...
Click to collapse
i bought a micro sc card reader and transfered a superuser zip and an old 4.3 beanstalk rom. it flashed fine last night. i used my phone all day and downloaded the latest 4.3 beanstalk rom and just tried to flash it and it FAILED. This is the second time i had a flash fail. I tried flashing that old beanstalk rom again and it failed too! what the heck???? my battery is a little low.....does twrp have some kind of safety built in where it wont flash if bettery is low?
ok...so i flashed cwm because im more familiar it than twrp. then i flashed an old slimbean 4.3 rom i had. everything worked fine and the phone booted up perfectly. i dont want slim bean so i rebooted into cwm and tried to flash the newest 4.3 beanstalk rom and it failed.....why?
scorey03 said:
ok...so i flashed cwm because im more familiar it than twrp. then i flashed an old slimbean 4.3 rom i had. everything worked fine and the phone booted up perfectly. i dont want slim bean so i rebooted into cwm and tried to flash the newest 4.3 beanstalk rom and it failed.....why?
Click to expand...
Click to collapse
Did you install the latest CWM? Is the 4.3 Beanstalk based on Kit Kat?
audit13 said:
Did you install the latest CWM? Is the 4.3 Beanstalk based on Kit Kat?
Click to expand...
Click to collapse
no its not based on kitkat. i flashed an older version of cwm via odin. i figured i could just update it with rom manager. i tried to update cwm to the latest verion and it fails everytime. so...i downloaded root checker from the play store and it says im not rooted. i need to fix this lol
im running a custom rom but yet root checker says its not rooted...hmm
Flash the latest Philz and. Validus as I know that is a rooted ROM. Personally, I don't use ROM manager.
scorey03 said:
im running a custom rom but yet root checker says its not rooted...hmm
Click to expand...
Click to collapse
What custom Rom is this?
Sent from my HTC One using Tapatalk
I'm on slimbean 4.3 and I've lost root. I want root back so I can get rid of this ROM. Ive flashed supersu multiple times with cwm..but I still do not have root access.
So I guess my question now is.....how do I get back to stock rooted? Im on slimbean 4.3 without root access.
scorey03 said:
I'm on slimbean 4.3 and I've lost root. I want root back so I can get rid of this ROM. Ive flashed supersu multiple times with cwm..but I still do not have root access.
Click to expand...
Click to collapse
Rooting is not needed to flash another ROM. Just boot into recovery, wipe, and flash another ROM.
audit13 said:
Rooting is not needed to flash another ROM. Just boot into recovery, wipe, and flash another ROM.
Click to expand...
Click to collapse
I tried and it failed......
scorey03 said:
I tried and it failed......
Click to expand...
Click to collapse
What rom and which recovery did you try?
I suggest you Odin to stock and try all this again
Sent from my ATT Samsung Galaxy SIII using TapaTalk
crazymonkey05 said:
I suggest you Odin to stock and try all this again
Sent from my ATT Samsung Galaxy SIII using TapaTalk
Click to expand...
Click to collapse
I agree 100%. Can you tell me where I can get stock 4.3 firmware?
Here is a repository with a lot of stock firmwares http://forum.xda-developers.com/showthread.php?t=1968625
Sent from my ATT Samsung Galaxy SIII using TapaTalk
scorey03 said:
I agree 100%. Can you tell me where I can get stock 4.3 firmware?
Click to expand...
Click to collapse
There is no stock ATT 4.3 ROM because ATT only released 4.3 as an OTA update. Do not flash any 4.3 firmware (even from sammmobile.com) unless it has been compiled for installation via Odin. Check the development threads for firmware that can be flashed via Odin.
crazymonkey05 said:
Here is a repository with a lot of stock firmwares http://forum.xda-developers.com/showthread.php?t=1968625
Sent from my ATT Samsung Galaxy SIII using TapaTalk
Click to expand...
Click to collapse
ok. im going to flash I747UCUEMJ2.7z which came from that link/thread you posted via odin.
If you got the phone on 4.3 you need to flash mjb or else you will brick the device
Sent from my ATT Samsung Galaxy SIII using TapaTalk
Ok, A long story:
Whenever I try to flash a lollipop ROM I get an unknown IMEI..
I solve this by flashing a stock 4.4.2 (I get the right IMEI but not registered in network) I solve this by flashing a patched modem and everything is fine..
But when I try to flash a lollipop ROM I still get an unknown IMEI again..
Also, I have efs backup, When I restore efs, Nothing happen.. IMEI is still unknown..
So, I want to try lollipop ROMs (like, ValidusLP ROM for example).. How to solve this problem?? Is there like a patched modem for lillipop??
Thanks in advance for anyone who will try to help.
Try some other lollipop ROM and see if issue solves
dineshjumani said:
Try some other lollipop ROM and see if issue solves
Click to expand...
Click to collapse
Actually, I tried many ROMs, Problem is the same in them all.
FawzyUsama said:
Actually, I tried many ROMs, Problem is the same in them all.
Click to expand...
Click to collapse
try installing latest full stock rom using odin and than try installing lolipop rom it might work as i solved problem in this war you can get latest stock firmware from sammobile or samsung-updates.com
dineshjumani said:
try installing latest full stock rom using odin and than try installing lolipop rom it might work as i solved problem in this war you can get latest stock firmware from sammobile or samsung-updates.com
Click to expand...
Click to collapse
Yeah, As I mentioned above, When I flash a stock 4.4.2, I can fix the problem, But then when I try to flash Lollipop ROM, Problem is back.
you flashed stock rom using odin or from recovery
dineshjumani said:
you flashed stock rom using odin or from recovery
Click to expand...
Click to collapse
ODIN.. I connected my device with my laptop and used ODIN.
FawzyUsama said:
Actually, I tried many ROMs, Problem is the same in them all.
Click to expand...
Click to collapse
FawzyUsama said:
ODIN.. I connected my device with my laptop and used ODIN.
Click to expand...
Click to collapse
what method you used to flash custom lolipop rom please tell and which recovery and which rom please tell
dineshjumani said:
what method you used to flash custom lolipop rom please tell and which recovery and which rom please tell
Click to expand...
Click to collapse
Tried both TWRP and Philiz touch recoveries, Both latest versions...
I flash the recovery using ODIN, Then flash the ROM using the recovery.
Exactly the same issue.
1) Was on stock Kit Kat 4.4.2 2 days back. Connected to Kies and got the update for Lollipop.Update the phone in few hours but no IMEI,nothing.
2)Downloaded the latest Stock Lollipop from SamMobile and flashed this using Odin and same issue.
3) Flashed the Kit Kat 4.4.2 and everything is fine with modem restored and IMEI visible.
4) Downloaded using OTA on stock 4..4.2 still same issue and IMEI blanks out.
I am sure there is some problem with this Update and waiting for a stable version.
From India
SM-N900
---------- Post added at 10:28 PM ---------- Previous post was at 10:20 PM ----------
On another note : Lollipop looks gorgeous though and has a good interface. Want to stick to stock as heavily use Spen features.
Please let me know if there is a modem that could be flashed with Odin to Stock lollipop ROM ? Else will have to go back to Kit Kat.
Thanks
kooldudegaurav said:
On another note : Lollipop looks gorgeous though and has a good interface. Want to stick to stock as heavily use Spen features.
Please let me know if there is a modem that could be flashed with Odin to Stock lollipop ROM ? Else will have to go back to Kit Kat.
Thanks
Click to expand...
Click to collapse
I already went back to 4.4.2
Ok fixed this issue.
Just download the previous ROM for Kitkat for your region model. Extract the Tar file and then what ever is the extracted file again open it using WinRar. Get the modem.bin out of it.
Once you have loaded lollipop: Open Odin again and flash the modem.bin from previous rom using Odin. Got to work for india .
Yey I am on lollipop.
kooldudegaurav said:
Ok fixed this issue.
Just download the previous ROM for Kitkat for your region model. Extract the Tar file and then what ever is the extracted file again open it using WinRar. Get the modem.bin out of it.
Once you have loaded lollipop: Open Odin again and flash the modem.bin from previous rom using Odin. Got to work for india .
Yey I am on lollipop.
Click to expand...
Click to collapse
Hi, I'm facing the same issue.. Did you extract modem.bin from last official kitkat rom for you country?
----------------------------------------------------------EDIT------------------------------------------------------------
Thank you! I extracted the modem.bin file from latest official ROM for my country and flashed it via ODIN
Now all works perfectly!!! Thank you very much!!!