[Q] Stuck in boot loop after flashing - AT&T Samsung Galaxy S II SGH-I777

Hello,
I am stuck in a boot loop.
I can't access stock recovery mode ( holding +, -, and the power butoon).
I CAN access the download mode.
I CAN flash with ODIN with no trouble.
Short description of actions leading to this:
1. Tried to upgrade to the latest CyanogenMod 10.1, Kernel at that time: SGH-I777-ATTGalaxyS2RootStockZedomaxKernel
2. Upgraded successfully, but my pone SIM got locked. I panicked and loaded a backup from CWM.
3. Phone returned to stock ROM (I believe) with Zedomax Kernel. DIdn't fix the SIM lock. Managed to unlock with Galaxy S Unlock app.
4. Decided to Flash a new rom + kernel. ROM: rr_i9100_Resurrection_Remix_V4.0.7_Sep-01-13 KERNEL: AJK-v3.9-AOSP
5. Successfully installed ROM, KERNEL. Installed wrong GAPPS, wiped cache and other cahce (in Advanced), installed correct APPS.
6. Everything works perfectly. SIM locks again. Try the Samsung S Unlock app, IT FAILS. (Because i had a back up of prievious EFS from the stock andorid os and didn't delete it?)
7. Restored EFS, Deleted olf EFS back up, did all 3 steps. SIM still locked. Restored old EFS
8. Loaded backup to Cyanogen Mod 9 (i believe) with Zedomax kernel.
9. Phone doesn't load, can't access CWM, or normal recovery.
10. Flashed Odin3 One-click Downloader I-777 UCKH7 Stock + Root No Bootloaders.
11. Phone stuck in boot loop, can't access Recovery mode. (To try and factory reset, because i think i need to reset cache for everything to work)
12. Flased Zedomax KERNEL, thinking it would give me CWM, but it doesn't.
I have read A LOT of posts regarding similar problems, but i decided to ask for help, seeing as every single situation is different.
[ I think that the unwiped cache and data from the REssurection ROM and AJK KERNEL are interfering with the stock ROM, KERNEL. But i can not enter recovery mode to reset data. These are just my thoughts ]
Please help me.

First, follow just step one below and then enter recovery and perform a wipe data/factory reset.
If that does not solve the problem, continue with steps 2 to 6.
Instructions to clear nand read/write corruption.
Odin3 v1.85 is recommended.
1) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning
2) Flash the Tar.md5 of the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
3) If that is successful you are done. If it is not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning.
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.

If I may add step 7) Stay away from Zedomax/his site; his rooting method, files and information are wrong and outdated.

Problem resolved. Thank you very much for your help!

Related

[Q] Failed kernel flash, phone wont boot.

I wanted to flash the Siyah kernel, but failed. Now the phone is always stuck at the Samsung logo, and I can't even enter Recovery mode, only Download mode which implies I must use Odin.
Any advice?
Flash a stock rom in Odin, factory reset. Clean slate. Then try flashing whatever rom/kernel you want again if you're still keen.
Edit - Or...Flash stock rom, root phone, restore Nandroid backup (assuming you have one).
Any guide for using Odin to do just this?
Here. But don't let me stop you searching for it :-|

CAn't revocer I9100m

Hello
Here is short story:
I rooted i9100m, everything was fine (method entering recovery, open cwm and install busybox)
So I wanted to install cm9 and took rc2 for sgs2, boot into recovery, 1st I did wipe factory reset (took very long) and clicked on reboot phone after reseting, instead of install from sd... (no big deal I was thinking). Phone could not move from boot screen even after taking out battery and restarting.
After that we tried CM9 from cwm, CM9 with odin( version for odin of cm9). always the same, stuck in boot. I found this soft brick unbrick thread on this forum and tried flashing stock rom (bell canada) nothing....even tried stock ginger..same story. when I tried to wipe reset data I get kernel panic (after every flashing I tried to reset/wipe). Sometimes its "kernel panic" sometimes "E: /data could not be mounted or found" (something like that)
I still can enter download or recovery mode
I searched whole forum for solution but I couldn't find it
PS: there was a method with ODin using this pit and repartition but from provided download link was only stock rom nothing else.
please help

[Q] S2G Flashing Custom ROM Not Possible!

Hey guys
I'm trying to flash my S II I9100G with cMIUI, which doesn't work. The phone gets stuck during booting right after the installation. I've been messing around with this problem for a couple of hours by now, been googling a lot and yet I have not found a solution.
What I did in order to flash the ROM:
1) I installed the latest German stock ROM (ICS) using Odin.
2) I followed this tutorial (root using SU-BB-Installer.zip and flash CWM recovery kernel 6.0.1.2 via kTool): http://forum.xda-developers.com/showthread.php?t=2065581 So far everything works fine. I have root access now.
3) Downloaded the cMIUI 2.10.19 zip from http://forum.xda-developers.com/showthread.php?t=1804619
4) When I tried to flash cMIUI from Recovery and toogle signature verification "on", it told me "signature verification failed". I ignored that message and installed it anyway.
5) Installation ran smoothly. After finishing it, the phone wanted to reboot. It now got stuck in the booting screen. I can not get the ROM booted.
I don't think it's cMIUI-caused, because I tried to flash a clean CM10 and still had the same problem (even though it didn't fail signature verification). Here are some more things I tried:
- installed clean stock ROM via Odin, again. Then followed all above steps exactly as described above, except for using Odin for flashing CWM Recovery instead of kTool
- again, clean stock ROM. After rooting, I then tried to install cMIUI via ROM Manager v5.5.2.3. Unfortunately, ROM Manager doesn't identify CWM recovery and keeps asking me to install the Recovery-System with ROM Manager. When I try that, there apparently "is no official CWM Recovery available" for my model. So, ROM Manager is no option
As described in the following thread, I can not use the ClockworkMod Recovery 6.0.1.2 kernel on aosp based ROMs like cMIUI and CM: http://forum.xda-developers.com/showthread.php?t=1631934 So that probably is the cause of my problem. Can you tell me what kernel I can use, instead? Or is there another way to flash that ROM? Via Odin, for example...
Thanks for your help in advance. Very much appreciated!!
Regards,
Daniel
What Codeworkx is saying in that thread is, that you cannot use that kernel when you are already on a aosp based rom. So you can use that recovery.
Something you didn't mention, did you do a full wipe from within the recovery? If you didn't do that, then thats probably the source of your problems.
1. Flash a stock rom true Odin.
2. Flash the recovery (you don't need to root your rom after)
3. Wipe system/factory reset
4. Wipe cache.
5. Download the rom again to make sure you the download went well.
6. Toggle signature verification off.
7. Flash Miui
8. Reboot and wait.
Lennyz1988 said:
What Codeworkx is saying in that thread is, that you cannot use that kernel when you are already on a aosp based rom. So you can use that recovery.
Something you didn't mention, did you do a full wipe from within the recovery? If you didn't do that, then thats probably the source of your problems.
1. Flash a stock rom true Odin.
2. Flash the recovery (you don't need to root your rom after)
3. Wipe system/factory reset
4. Wipe cache.
5. Download the rom again to make sure you the download went well.
6. Toggle signature verification off.
7. Flash Miui
8. Reboot and wait.
Click to expand...
Click to collapse
Thank you so much! Wiping helped. :good: Why didn't I try that before :silly:
Awesome, now I can finally enjoy cMIUI. It's really great! (except for crashing galery/camera app when starting cam from lock screen. but who cares )
Thanks dude! :highfive:

[HELP] Attempted installing paranoid, resulted in always booting to CWM instead.

I tried following this:
http://forum.xda-developers.com/showthread.php?t=1580070
"INSTRUCTIONS" part:
* RECOVERY: FACTORY RESET IF YOU WERE USING ANOTHER ROM!
* RECOVERY: Install Rom: Download
* RECOVERY: Install Gapps, ALWAYS-EVEN FOR UPDATES: Download (find the latest one that carries the "jb" tag)
* RECOVERY: Wipe Cache Partition
* RECOVERY: Wipe Dalvik Cache
* Reboot and enjoy
Click to expand...
Click to collapse
did all the above, never forgot any of the 3 wipes/resets that were necessary.
used this rom file:
http://goo.im/devs/paranoidandroid/roms/i9100g
(latest one)
for my Galaxy Samsung S II GT-i9100g.
I had CWM and also had a rooted android 2.3.
first boot it showed me the normal samsung boot screen, for 45 minutes....
so I restarted and the phone gave me the same behaviour..
so I removed the battery to turn off the phone, and attempted to reinstall the whole thing, going through this process again from scratch
not forgetting any of the wipes etc...
now every time I boot it, it leads me to CWM instead of the normal boot screen and the expected paranoid rom eventually...
I followed this path because CM 10 failed me because upgrading from 2.3 to 4.x requires going through something that is called "stock" or as I think it actually is - google's /manufacturer's original firmware/rom production line thingy
and after that it needs me to re-enable root on that stock rom all over again. And only then I may attempt to install CM10...
so I picked paranoid instead, because in it's instructions is showed me no such constraint. heck it can't give me that constraint because there is no "stock" of android 3.x for smartphones
but then this issue happened... so I need your help.
I found similar search results but couldn't figure out their solutions or how whatever triggered that same problem (which isn't mentioned in those threads) is related to what I did to my phone... (so that I will not repeat the same mistake)
your help is much appreciated as I need it so so much!
Huh?
Just flash a stock ROM, get back on your feet and go CM or paranoid.
Sent from the little guy
gastonw said:
Huh?
Just flash a stock ROM, get back on your feet and go CM or paranoid.
Sent from the little guy
Click to expand...
Click to collapse
by "flash"ing you mean the option "install from a zip file" in CWM in recovery mod?
if I have some rom, the only way for me to install another would always be by going through that middle step of also installing a 'stock' rom as well?
there is no way around it?
installing a 'stock' rom, wouldn't it make me loose my root I have on the phone and force me to root it all over again before I can continue install anything at all?
thats the reason I wanted to try out the paranoid way of doing this instead of the CM10, because I have no interest in rooting my already rooted phone and I hoped that paranoid does not need me to go to stock first....
Couple of things:
Stock: why, when in trouble, we suggest stock?
Stock is the original state of the phone.
Samsung write it for our device to work flawless, so, by flashing stock we can check if our device is fully functional.
Imagine you flash a custom ROM and you lose IMEI, you go "wtf?" right?
In order to check if your EFS folder is f&#cked up, you flash stock and check if your IMEI is still there.
We can always use stock to take a long breath "phew, we're fine" after a f*&k up.
You can flash stock via CWM (zip file), Odin (tar file, md5) and mobile Odin (tar, zip and md5).
CWM: custom recovery, you can get it by flashing a custom kernel or by flashing it via stock Recovery (generally comes with BusyBox and SuperUser app, which gives you Root).
Odin: Just download any version and follow directions.
Mobile Odin: Well, this is a hell of an app, you need Root to run it.
It does all that Odin does, plus it roots your ROM (only stock ROMs) while it's flashing it, all by itself. Costs 5 bucks, but it's damned worthwhile.
Wanna know the best scenario?
You get M.O Pro, you get a nandroid back up online app, you get CWM zip files (sitting on your SD).
With that line up, you can flash whatecer the hell you want and you will ALWAYS have root.
Sent from the little guy
some questions
ONE QUICK IMPORTANT QUESTION BEFORE THE REST:
If I use mobile odin, will I be able to use it to install stock rom and also root it at the same time?
SECOND IMPORTANT QUESTION:
you said I could flash whatever I want and still have root, but my problem was not 'not having root', it was not having the flash process complete successfully... how do I attack that?
THIRD IMPORTANT... info... :
My "BUILD" version is "GINGERBREAD.XXKL5", isn't that a 'stock' one?
If you don't have a lot of time,
then the rest of this post is not as important as the 2 questions above...
gastonw said:
Couple of things:
Stock: why, when in trouble, we suggest stock?
Stock is the original state of the phone.
Samsung write it for our device to work flawless, so, by flashing stock we can check if our device is fully functional.
Imagine you flash a custom ROM and you lose IMEI, you go "wtf?" right?
In order to check if your EFS folder is f&#cked up, you flash stock and check if your IMEI is still there.
We can always use stock to take a long breath "phew, we're fine" after a f*&k up.
You can flash stock via CWM (zip file), Odin (tar file, md5) and mobile Odin (tar, zip and md5).
CWM: custom recovery, you can get it by flashing a custom kernel or by flashing it via stock Recovery (generally comes with BusyBox and SuperUser app, which gives you Root).
Odin: Just download any version and follow directions.
Mobile Odin: Well, this is a hell of an app, you need Root to run it.
It does all that Odin does, plus it roots your ROM (only stock ROMs) while it's flashing it, all by itself. Costs 5 bucks, but it's damned worthwhile.
Wanna know the best scenario?
You get M.O Pro, you get a nandroid back up online app, you get CWM zip files (sitting on your SD).
With that line up, you can flash whatecer the hell you want and you will ALWAYS have root.
Sent from the little guy
Click to expand...
Click to collapse
the saddest part is that I couldn't figure out most of what you just said
what is 'nandroid'? 'flashing'? do you mean like dd in linux? copying to the entire flash storage device?
'IMEI'? huh..? O_O
at the moment I was able to 'get back on my feet', I restored everything back to normal with manual copying of important parts of the CWM corrupted backup from this week, and old stuff for a CWM backup made few months ago.
now that I am at a 'normal' state.. I want to install paranoid or CM10 on my GT-I9100g.
which one of those 2 does not force me going through installing stock?
I have this fear of installing stock that it will take away my root and that I will have to use adb from command line to re-enable root afterwards, which I have bad experience with.
I need to know a few things before I attempt to install stock via CWM,
will installing stock disable my root? will installing stock disable my ability to load recovery boot menu CWM?
is 'root' an attribute or state that belongs to the running rom itself after boot has been completed and to that only?
or does it also belong to the state the device is at while in the recovery boot menu CWM ?
I tried messing around with ADB in the past to see if I could root devices via that way but it wasn't very successful so thats why I'm afraid of having to attempt it again.
bumpitybump
even though a year later, I would still love some replies
resurrecting my motivation to do this once again.
copy paste from my other post;
before flashing, you will need these;
-stock rom (get it from Sammobile, sign in and select your country and phone model)
-blazing kernel for recovery (search in XDA)
-custom rom (CM, PA, Supernexus...your choice)
-backup your data
-GApps (get the latest one)
-you must know what are you doing and dont flame/blame other member if something wrong
how to flash;
-make sure you are on latest stock rom (mine is JellyBean 4.1.2), if not like the OP, flash the latest stock rom using Odin;
*reboot your phone in Download Mode
*open Odin and in PDA option select your stock rom and then Start
*if done it will display Done and disconnect your phone, it will boot up
*if bootloop, reboot into Recovery Mode, and then wipe data and cache, and then reboot normally
-after updating your phone to latest stock rom, copy your custom rom, GApps, and Blazing kernel into external SD card, then reboot into Recovery Mode
-choose "apply update from external storage" and choose Blazing kernel, wait for it to finish update
-reboot normally, and then reboot back to Recovery Mode. this time you will notice that your recovery is different from the previous one
-select install zip > choose from external storage/sdcard 1 > and then choose your custom rom. then wait for it to finish update
-repeat the above step to install GApps, and after that reboot normally
-if bootloop, reboot back to Recovery Mode and then wipe data, cache and dalvik and then reboot
-done, now you are running on custom rom
Click to expand...
Click to collapse
and about the root, i believe that almost all custom rom rooted

[SOLVED] Every ROM I flash soft bricks device

Any ideas why this could happen?
What I do everytime:
Flash XXLPB with ODIN 1.85, root with CF-Root v5.2 CWM, reboot, all fine.
Then I flash for ex. Carbon ROM Nighlty, GAPPS, reboot and it's stuck at triangle screen. Can't go to recovery, only download mode works.
I also tried "old" Carbon 1.8, and even other ROMS that worked like a charm some time ago.
All started when I tried yesterday to flash 4.3 Carbon nightly over 4.2.2 (1.8) Carbon w/o wiping...
Please help as for now I'm stuck with my 3310 xD
Back to stock via Odin/download mode (you don't really have another option), make sure you do a wipe/factory reset, try flashing the rom again.
I tried 4-5 times, and always the same is coming out! Is there any minimum requirement for flashing let's say 4.2.2? Shouldn't matter, right?
It shouldn't matter but we see cases on here all the time where for whatever reason, Odin flashes don't take on the first/second.....eighth (as an example), and for whatever reason, the ninth flash works. In other words, you need to persevere. Try different stock roms for your carrier (different Android versions, not just the recent ones - but don't use 4.0.4 in case you forget when you re-root your phone & do a wipe which will brick your phone). And keep trying. There's no easy fix for these situations unfortunately (search for Hopper8's 'Odin won't flash' thread, there's stuff in that thread you can try).
Actually the ODIN flash of the stock rom always works. But then I flash a rom through CWM and it bricks...
Is there a way to flash those roms with ODIN?
No. Almost all custom roms are CWM flashable.
OK...What I suggest you do is this...
*Clean install of stock with wipe/factory reset.
*Root your phone by flashing a custom kernel like PhilZ or Siyah (or Dorimanx).
*Do not flash a separate CWM or any other mod after you've rooted the phone.
*Read the first page of the thread devoted to the rom you want to flash very carefully. Flash the rom with CWM/follow the instructions to the letter (do not use Rom Manager or the CWM app from your homescreen; boot the phone into recovery & flash that way).
If you're seeing specific errors in CWM having done those steps (And do them again now even if you've done them previously), you need to tell us exactly what's going wrong in CWM. We're not mindreaders.
Edit - Your phone isn't bricked. Bricked phones don't boot. At all.
Thanks for the detailed answer.
Actually that's what I'm doing every time!
I'm trying to install 4.3 nightly build of carbon
I tried also stable build which was working well before...
There are no specific instructions, but I think it's pretty much standard:
1. Wipe Data/Factory Reset
2. Flash zip
3. Flash GAPPS
4. Wipe Dalvik Cache
5. Reboot
Thanks!
EDIT: After flashing the custom rom the phone doesn't boot, it gets stuck at kernel panic upload mode. Once I managed to get into CWM but there I couldn't perform any action, it was freezed.
Hi Again,
it looks like everything worked fine. Maybe I had a strange version, or the CWM was to old (5).
Now I could flash what I wanted and it's not stuck at boot anymore!
Thanks for the help!
Perseverance is a beautiful thing.

Categories

Resources