I extracted some filed to my phone now it wont start, so I am trying to install some stock roms with odin, but will this possibly brick it? I have the bell canada version i think.
How else can i fix this?
What do you mean it wont start, does it bootloop, do you see the i9100 logo, a yellow triangle, or will it not turn on at all.
Can you get into CWM recovery or download mode? If you can only get into download mode, odin will work fine, just make sure to flash the proper roms. (If you have the i9100G, Do not flash the i9100 roms and same of the opposite)
successfully installed
I've successfully installed using odin..just use the search button for the steps and procedure of installation.
Factory reset first .
jje
Related
ok guys i odin the stock rom with root, how in the heck i get into recovery mode and install cm7? i tried rom manager and it didnt work any other ideas?
Rom manager does not work correctly on stock. (It will work once you are on cm7.) You need to install a kernel that contains ClockworkMod Recovery. If you install the kernel with Odin or Heimdall, it will increment the flash counter and cause the initial I9100 boot screen with yellow warning triangle. If this is a concern to you, use the Guide linked in my signature to avoid that.
Hi I have rooted my UK i9100 with odin and successfully installed resurrection remix previously. When trying to flash an updated version I stupidly forgot to factory wipe and now my phone wont boot, it gets stuck on the rom boot screen and i cant get into cwm.
I can get into download mode and from there have tried flashing another rom via odin (litening rom) to see if that would boot to get me into cwm but that freezes on the boot screen also. I tried to use Galaxys2recovery as shown on zedomax youtube channel but then realised that is done from gingerbread only. I tried reflashing "CF-Root-SGS2_XX_OXX_LP6-v5.2-CWM5" via odin and then the litening rom again but that still hangs when trying to boot.
Is there something obvious I should be doing? ..I am (unsuprisingly) a noob
Thank you
you could have asked at the first time itself, before various yourown attempts ?
if you are able to get CWM now, try to install the ROM after data factory reset and all the wipes + system format from Mounts & storage.
if it didnt help again go to CWM do all the wipes and format system, and switch off and get into the download mod and flash a GB stock rom from ODIN
I can get into download mode and from there have tried flashing another rom via odin (litening rom) to see if that would boot to get me into cwm but that freezes on the boot screen also
Click to expand...
Click to collapse
odin if for stock roms not custom roms / .zip files....
zaheedahmed said:
if it didnt help again go to CWM
Click to expand...
Click to collapse
that's the thing, i cant get into cwm, or at least i don't know how to. Is there a file I can install from odin that will put me straight into cwm without having a working rom?
why do you wait to boot the phone to get into the CWM,
didnt you try Vol-up+Home+Power while phone is off
Hi Everyone! just a rookie here in need of a bit of advice.
I'm a Galaxy S II I9100 owner and have my phone rooted and all setup with custom roms and been comfortable with flashing for some time now. My ROM of choice recently was Vanilla Rootbox and have to say the ROM has been fantastic with very few bugs to report. Last night i recieved the OTA update via Goo Manager for Vanilla Rootbox 3.4. I downloaded the full update over wifi and flashed with all wipes no worries. Next step was to flash the latest GAPPS and i figured there would be nothing wrong with flashing the GAPPS zip i had on my sd card that i had downloaded the last time i was notified of a GAPPS update via Goo manager as well. After flashing, wiping everything and rebooting again. My phone then booted up to a series of dialog boxes indicating that many google processes had stopped functioning. apps.google.com etc etc. A similar error has been reported in the Vanilla Rootbox thread by another user but i wasnt able to report this bug their either because my post count is too low to post in a development forum. So after seeing this error i rebooted into recovery to flash my last backup but CWM recovery came back with an error messaging stating it couldnt mount either ext or int sdcard. i did a factory reset which made no difference to the problem whatsoever. I then downloaded ODIN and the latest stock ICS Rom and flashed it via ODIN with no reported errors. My phone now boots through the optus boot animation and is stuck at the Galaxy S 2 screen with the flashing red and yellow animation over the S. If i turn off the phone with the power button, the phone turns off and immediately starts again and gets stuck at the flashing s screen. I've taken the battery sim and ext sd card out and put it all back in only for the problem to persist.
If anyone could help me there's a donation and my thanks in it!
Much appreciated
Nick
tried to re flash another stock ROM?
If so, tried factory reset the phone after the flash?
As long as you can get to DL mode, you are good to keep on flashing till you are up & running.
And then you got this
Remember to update your kies and make sure you close it all up before flashing with odin. If you are in 4.0.4 beware of the brick bug.
gastonw said:
tried to re flash another stock ROM?
If so, tried factory reset the phone after the flash?
As long as you can get to DL mode, you are good to keep on flashing till you are up & running.
And then you got this
Remember to update your kies and make sure you close it all up before flashing with odin. If you are in 4.0.4 beware of the brick bug.
Click to expand...
Click to collapse
Kies has never been installed on this computer but i did use the usb drivers mentioned in the soft brick recovery guide you linked. I used some information from the guide to flash this stock rom but i couldnt flash or wipe the partition because im unsure where to get the .PIT file required? i cant get past the boot animation so no factory reset possible and yes i can still get into download mode!
darkstar117 said:
Kies has never been installed on this computer but i did use the usb drivers mentioned in the soft brick recovery guide you linked. I used some information from the guide to flash this stock rom but i couldnt flash or wipe the partition because im unsure where to get the .PIT file required? i cant get past the boot animation so no factory reset possible and yes i can still get into download mode!
Click to expand...
Click to collapse
wow wow, leave pit files alone for now, they are nasty.
What stock ROM did you flash? 4.0.4 or 4.0.3?
You can factory reset via recovery mode.
Try installing kies anyway, it can't never hurt. Just make sure all applications are closed before you re-flash.
here's jb leak, might help:
http://www.sammobile.com/2012/11/15/i9100xxlsj-%E2%80%93-galaxy-s-ii-android-4-1-2-jelly-bean-test-firmware/
Right so i flashed I9100XWLP8 stock rom (4.0.3). Just then i flashed Siyah Kernel and attempted to use the factory reset function in recovery there, i get a message down the bottom mentioning that it can't mount my internal SD.
darkstar117 said:
Right so i flashed I9100XWLP8 stock rom (4.0.3). Just then i flashed Siyah Kernel and attempted to use the factory reset function in recovery there, i get a message down the bottom mentioning that it can't mount my internal SD.
Click to expand...
Click to collapse
Tell me your:
Model
Firmware
Country
Carrier
Always mention this
try flashing jb leak (ROM, modem & kernel package).
So I have a Sprint Galaxy Mega and it seems as though it may be semi-bricked. It will not boot past the GALAXY MEGA logo. It will just continuously power cycle to and from that logo. If I attempt to put it in recovery, it will say "RECOVERY BOOTING" in blue letters as usual, then power cycle right back to the GALAXY MEGA screen. It will boot into Odin mode and accept Odin files, but after attempting do do a typical "stock Odin" scenario, nothing has changed. I looked around for the Pit but cannot seem to find it. Does anyone has a reliable link to the latest Odin stock restore and the PIT file that matches it?
Maybe an error with your system data. So you can't reboot into recovery ? If you can try to wipe data and cache and reboot.
It may be an abnormal re-partition when flashing stock rock, and then I can't help you (have the i9205 international model). Some members of this section have the Sprint version, try to send them a PM if nobody can help you
Nope, no recovery. I was considering flashing a custom recovery to it to see what it does but I don't wanna kill the phone any more than it already is...
Yes I understand. But flashing custom recovery can solve your problem, only if you can boot on it. I think it can't make more damages to your phone, he just always stuck on boot phase like a brick, but if you don't want to try, wait for a developer making you a PIT file. More safe, the Galaxy Mega have a too poor development support for risk anything...
Well I went ahead and flashed TWRP to it. It will boot into TWRP just fine. Tried flashing the stock L900 ROM zip and it still won't boot.
Well I installed a custom ROM, SlimKat, and the phone boots. If I install the stock ROM located in the following link, OP's signature, the phone goes right back to bootlooping. ???
I need either the stock ROM or a ROM with dialer codes because this phone will be flashed to a regional carrier.
what recovry version you use bro. maybe recovery problem. try use your custom rom to flash another recovery from philz. the latest one. some time recovery dont work properly to downgrade from 4.4.2 to stock 4.2.2.
Great, so with Philz Touch Recovery, I never had problems for downgrade and I do this often for testing roms. Now it should not bootloop if you reflash stock.
I am using "CWM-based recovery 6.0.4.7"
I will try Philz recovery
After trying Philz recovery to flash the stock file I found, it once again bootlooped. Is there another stock ROM floating around somewhere or possibly a custom ROM that has dialer codes such as ##3282# enabled?
No idea... But actually the most complete stock based custom rom is MegaFire I think. Flash V5 (not V5x !) it should be enabled.
I don't see what is the problem while flashing stock rom... Oh ! Maybe you haven't enabled USB Debugging, I forgot to do that one time and I had some issues, in case you try to flash a firmware where Knox or others features are on with a modem without these, may cause bootloop. I've searched for 2 days before solve that little problem...
Have you tried another firmware ? If you can flash custom rom, something went wrong before flash... Odin folder is complete ?
Strange...once again a boot loop after flashing the MegaFire ROM
I'm almost certain I need the PIT file. I cannot find it anywhere.
Well I got the phone to boot from that rooted stock ROM FINALLY. I don't remember for sure but I think what I did was first flash TWRP, then flashed boot.img.tar that I found somewhere, it was listed for the Sprint Mega. I then booted into TWRP and flashed the stock rooted ROM(zip) I mentioned before. It now boots perfectly and everything works except one tiny little detail. No WiFi, no cellular signal at all. Baseband version: unknown in About phone.Already tried flashing the Sprint stock modem from the same download link as the ROM and it didn't work.
I'm having the same problem too dude, I
I download n flash all.the firmware I could find online, since I have no idea what the country of origin is. But most of them work, but no WiFi, Bluetoothand the sim card slot don't read
VirtueToVice said:
Well I got the phone to boot from that rooted stock ROM FINALLY. I don't remember for sure but I think what I did was first flash TWRP, then flashed boot.img.tar that I found somewhere, it was listed for the Sprint Mega. I then booted into TWRP and flashed the stock rooted ROM(zip) I mentioned before. It now boots perfectly and everything works except one tiny little detail. No WiFi, no cellular signal at all. Baseband version: unknown in About phone.Already tried flashing the Sprint stock modem from the same download link as the ROM and it didn't work.
Click to expand...
Click to collapse
I have a Verizon Note 2 running 4.4.2.
I successfully rooted it without unlocking the bootloader or flashing a custom recovery, everything was stock. Everything worked fine after and I was able to use root-requiring apps.
Then, after attempting to flash custom recovery, since the bootloader was locked, I am now stuck at the screen that says: "System software not authorized by Verizon Wireless has been found on your phone..."
I am able to enter recovery (the stock recovery) as well as go into download mode. Normally this wouldn't be a problem as I could just flash stock through Odin in download mode.
However, ever since the soft-brick Odin won't recognize my phone (the yellow COM square does not come up), which is strange because Odin recognized my Note 2 in download mode before this happened.
And even stranger is the fact that it is not a driver issue, as when I plug in my Note 2 in download mode I get a message from Windows 7 saying that the serial gadget device driver was found and installed successfully (and the phone also shows up in Device Manager in control panel as fully installed while in download mode.
Yet Odin won't recognize it.
I have spent days searching for an answer and have yet to come across an issue identical to mine (everyone seems to be able to just flash stock through Odin to fix this particular soft-brick, but Odin is not recognizing my device), so I finally decided to post here.
Any suggestions at all are welcome as I am somewhat desperate at this point. I'd just like to get it back to stock (or flash a custom rom, it does not matter as long as I can get the phone to work).
I would like to point out that I have already tried the following:
- Different USB ports
- Using different USB cables
- Uninstalling and reinstalling the drivers
- Wipe/Factory Reset in stock recovery
From what I can see, my only options are to either somehow get Odin to recognize the phone (suggestions welcome here), or somehow flash stock through the default recovery (if possible, again, any input is appreciated).
William31 said:
I have a Verizon Note 2 running 4.4.2.
I successfully rooted it without unlocking the bootloader or flashing a custom recovery, everything was stock. Everything worked fine after and I was able to use root-requiring apps.
Then, after attempting to flash custom recovery, since the bootloader was locked, I am now stuck at the screen that says: "System software not authorized by Verizon Wireless has been found on your phone..."
I am able to enter recovery (the stock recovery) as well as go into download mode. Normally this wouldn't be a problem as I could just flash stock through Odin in download mode.
However, ever since the soft-brick Odin won't recognize my phone (the yellow COM square does not come up), which is strange because Odin recognized my Note 2 in download mode before this happened.
And even stranger is the fact that it is not a driver issue, as when I plug in my Note 2 in download mode I get a message from Windows 7 saying that the serial gadget device driver was found and installed successfully (and the phone also shows up in Device Manager in control panel as fully installed while in download mode.
Yet Odin won't recognize it.
I have spent days searching for an answer and have yet to come across an issue identical to mine (everyone seems to be able to just flash stock through Odin to fix this particular soft-brick, but Odin is not recognizing my device), so I finally decided to post here.
Any suggestions at all are welcome as I am somewhat desperate at this point. I'd just like to get it back to stock (or flash a custom rom, it does not matter as long as I can get the phone to work).
I would like to point out that I have already tried the following:
- Different USB ports
- Using different USB cables
- Uninstalling and reinstalling the drivers
- Wipe/Factory Reset in stock recovery
From what I can see, my only options are to either somehow get Odin to recognize the phone (suggestions welcome here), or somehow flash stock through the default recovery (if possible, again, any input is appreciated).
Click to expand...
Click to collapse
Wow... I'm stumped too as to why Odin won't recognize the phone. What method did you use to try to flash the custom recovery and what recovery did you flash? (You probably know now, but just in case.... if you can get the phone restored to stock 4.4.2 again... then you can't flash a standard custom recovery onto the phone because of the bootloader being locked down. You can use the modified TWRP called Safestrap recovery if you root again... and can only flash 4.4.2 touchwiz roms with stock 4.4.2 kernel after you get rooted again).
When you rooted, all I can think of is that something may have corrupted the drivers somehow and that's now conflicting with ODIN. With the phone in download mode... have have you went into the PC's Device Manager and tried to delete/reinstall any Samsung related drivers, (make sure to look for hidden drivers.... click scan for hardware changes after deleting them and the computer should reinstall the correct drivers). Also... have you made sure no other conflicting programs (like Kies) are running in the background?
You might try to do a system restore to an earlier point on your PC where ODIN recognized the phone to see if that would work.
If ODIN version 3.07 isn't recognizing the phone, you could try a newer version of ODIN. Here's some links to other ODIN versions that you might try: Download link for ODIN 3.09 ; Download link for ODIN 3.10.0. ~~With the newer ODIN versions, they have replaced the "PDA" slot with "AP"--so the .tar firmware file goes into AP in the newer ODIN. ****(For reference--Here's the XDA Thread where XDA recognized contributor -CALIBAN666- posted these links to newer ODIN versions. Hit the thanks button for him ****
---------------
If you can't get the restore to work with ODIN, you could try Samsung Kies to see if it can fix the device...
Where to download Kies -- http://www.samsung.com/us/kies/
Emergency Firmware Recovery using Kies 3 -- http://www.samsung.com/us/support/faq/FAQ00059169/81100
I hope that some of this info helps and that you can get it fixed.
Good luck!
mattnmag said:
Wow... I'm stumped too as to why Odin won't recognize the phone. What method did you use to try to flash the custom recovery and what recovery did you flash? (You probably know now, but just in case.... if you can get the phone restored to stock 4.4.2 again... then you can't flash a standard custom recovery onto the phone because of the bootloader being locked down. You can use the modified TWRP called Safestrap recovery if you root again... and can only flash 4.4.2 touchwiz roms with stock 4.4.2 kernel after you get rooted again).
When you rooted, all I can think of is that something may have corrupted the drivers somehow and that's now conflicting with ODIN. With the phone in download mode... have have you went into the PC's Device Manager and tried to delete/reinstall any Samsung related drivers, (make sure to look for hidden drivers.... click scan for hardware changes after deleting them and the computer should reinstall the correct drivers). Also... have you made sure no other conflicting programs (like Kies) are running in the background?
You might try to do a system restore to an earlier point on your PC where ODIN recognized the phone to see if that would work.
If ODIN version 3.07 isn't recognizing the phone, you could try a newer version of ODIN. Here's some links to other ODIN versions that you might try: Download link for ODIN 3.09 ; Download link for ODIN 3.10.0. ~~With the newer ODIN versions, they have replaced the "PDA" slot with "AP"--so the .tar firmware file goes into AP in the newer ODIN. ****(For reference--Here's the XDA Thread where XDA recognized contributor -CALIBAN666- posted these links to newer ODIN versions. Hit the thanks button for him ****
---------------
If you can't get the restore to work with ODIN, you could try Samsung Kies to see if it can fix the device...
Where to download Kies -- http://www.samsung.com/us/kies/
Emergency Firmware Recovery using Kies 3 -- http://www.samsung.com/us/support/faq/FAQ00059169/81100
I hope that some of this info helps and that you can get it fixed.
Good luck!
Click to expand...
Click to collapse
So I tried recovering with Kies and it just kept throwing errors at me, then finally I just closed it and, am not quite sure why, but went into Odin and it worked! Apparently trying to recover with Kies somehow fixed the Odin issue and I was able to flash stock through Odin. Thanks so much!
You mentioned there was a way to flash a safestrap recovery and then flash touchwiz roms? Do you by chance have instructions on how I could do this, or links to this information...?
William31 said:
So I tried recovering with Kies and it just kept throwing errors at me, then finally I just closed it and, am not quite sure why, but went into Odin and it worked! Apparently trying to recover with Kies somehow fixed the Odin issue and I was able to flash stock through Odin. Thanks so much!
You mentioned there was a way to flash a safestrap recovery and then flash touchwiz roms? Do you by chance have instructions on how I could do this, or links to this information...?
Click to expand...
Click to collapse
Cool. Glad you got it fixed.
As you know, you can root with GhettoRoot from this thread: http://forum.xda-developers.com/showthread.php?p=57238246
Then can install Safestrap from this thread: http://forum.xda-developers.com/showthread.php?p=51616723
I've never used Safestrap because I can use regular custom recoveries like CWM and TWRP. I'm still on a 4.1.2 unlocked bootloader and currently running TrentsKKRom, Build #2...which is 4.4.2 based with stock kernel, so I think it would work with Safestrap.
I'd recommend reading through the Safestrap thread thoroughly and asking questions there to make sure you get everything installed correctly. I've read that with Safestrap, you need to make a backup of your Stock ROM first and save it somewhere safe, like to your computer and on your external sd card...so you can easily restore it if needed. (I'd also make a backup of the ESF in Safestrap if it lets you, then save it somewhere safe).
After you are rooted with Safestrap, you'll have to flash custom ROM's over the stock slot in Safestrap, as the other slots apparently don't work. Again, you're limited to only using Touchwiz ROM's with the stock kernel because of the bootloader still being locked.
Check out TrentsKKRom and Alliance build 30 . (I personally like Trent's build 2 best with the S5 clean theme). I've also found Trent's ROM to be really smooth without UI lagging, the Bluetooth works good with no stuttering, and it pairs well with my Sony Smartwatch 3. (Edit: If you do try Trent's ROM, you may need to install a couple apps.... Chainfire's Supersu app to control your root permissions (at least I needed to), and the FolderMount app to fix a KitKat internal storage mounting issue).
Have fun!!