Phone stuck before boot animation after flashing custom ROM - Galaxy S III Q&A, Help & Troubleshooting

Hi, I'm getting stuck at the black screen just before the boot animation (the one that says "samsung galaxy SIII gt-i9300"), after flashing custom rom via CWM. Maybe I'm a complete noob but I think something is wrong in my phone.
I had installed MIUI official before, then removed it to get warranty back and sent phone to samsung service to fix the my broken simcard compartment.
After getting my phone back, I tried to install MIUI again and got stuck.
The strange thing is how fast ROM is installed in CWM, less than 10 seconds...
No error message and says install is complete
have retried 7 times now, using this:
- Odin 3.04
- CF-Auto-Root (http://forum.xda-developers.com/showthread.php?t=1957273)
- CF-Root 6.4 - SuperSU+CWM5.5+CWMManager (http://forum.xda-developers.com/showthread.php?t=1695238)
- ClockworkMod Touch 6.0.3.2 (http://forum.xda-developers.com/showthread.php?t=1719744)
- ClockworkMod 6.0.3.6 - Touch and Non-Touch (http://forum.xda-developers.com/showthread.php?t=2200501)
ROMs:
- MIUI Official 3.8.16
- MIUI Official 3.7.12
- CyanogenMod 9.1.0 (stable)
what I do:
- boot to bootloader
- flash CF root with Odin (Auto reboot and F.reset Time are checked)
- reboot, then shutdown
- boot to bootloader
- flash CWM with Odin (Auto reboot and F.reset Time are checked) also tried to install with ROM manager
- reboot, then shutdown
- boot to recovery
- wipe data/ factory
- wipe cache
- wipe dalvik
- install zip from sdcard (internal) <-- strange thing here is how fast it is installed, less than 10 seconds...
- wipe data/ factory, cache, dalvik again
- reboot
- got stuck.
- flash samsung stock ROM I9300UBALE6_I9300ZTOALE7_ZTO (brazilian 4.0.4, phone was in that version when installed MIUI first time)
Don't know what to do now, please help!

Does it boot with stock roms?
Please DO NOT flash anything older than 4.1.2 stock...
If all zips opnly take 10 seconds, perhaps theyre getting corrupt on your memory. How are you getting the zips on your phone?

rootSU said:
Does it boot with stock roms?
Please DO NOT flash anything older than 4.1.2 stock...
If all zips opnly take 10 seconds, perhaps theyre getting corrupt on your memory. How are you getting the zips on your phone?
Click to expand...
Click to collapse
yes, it boot with stock rom.
I just copy/paste files from windows, always done that, but now that you say, md5 is diferent...
I'll check stock ROM and file copy.
Thanks!

It was the file copy messing with the zip...
used adb push and all OK now!
Thanks again!

Related

[Q] SGS2 - not boot - after flashing CM7 over MIUI

Hi
I first installed MIUI ROM in my SGS2.
Yesterday I try to move from MIUI to CM7.
This is what I did,
downloaded CM7 ROM for SGS2
put that in SD card
wipe data cache and dalvik cache
flash CMMOD
booted in recovery MOde
install ROM from SD card
After this, SGS2 rebooted and stuck at the logo.
I waited for a long time - hmm.. no hope!.
I turned off the mobile - removed and replaced the battery - but still no sing of booting.
I searched google abt this.., what i did is
Vol.Dwn +Pwr Butt. + Home = its shows a screen with options to rooting
Vol. UP + Pwr. butt. + Home = black screen!
Also with - Vol.Dwn + Pwr + Home, option I use Odin and flashed insecure kernel
back in my SGS2 - hoping it will boot - but never happens!
Any one of you please guide me to recover my device!
or it is possible to put stock ROM in this state?
Some users report that they have boot problems after flashing CM7 for the first time.
Did you try to flash CM7 just a second time (with a full wipe before)?
Full wipe CWM Recovery:
Main Menu - Factory reset/data reset (very important!)
Main Menu - Wipe Cache (just for sure, but already done at factory reset)
Mount/Unmount Menu - Format /System (very important!)
Advanced Menu - Wipe Davlik Cache (very important!)
This leaves internal and external SD card untouched!
Then install the ZIP image (ROM image) from the internal SD card that you have copied before.
Please do this procedure at every ROM change and you'll be fine.
If you only update the same ROM (e.g. CM7 update) it might not be necessary to do a full wipe, but if the developers recommend it, please do it.
After a ROM change you should do a battery calibration (you need root):
Install the free app "Battery Calibration" from the market.
Charge your phone to 100% (until 100% notification) at least 4 to 5 hours.
Start the app "Battery Calibraton" and initiate the calibration.
Use the phone until the battery is complete discharged (autom. shutdown).
Do not charge the phone before it has shutdown.
Then charge it completely to 100% (4 to 5 hours).
Now your battery is calibrated for that ROM.
Hi thanks for the answer!.
ya i did CM7 flash first time over the MIUI ROM.
i did all data wiping!
but still SGS2 cant able boot
any idea of glash stock rom back?
I had problems too when i flashed CM for the first time. Try to flash it again, for me it helps.
Sent from my GT-I9100 using Tapatalk
@SpaceCeph
thnks again!.
But how will i do that?
via ODIN? [I already did and flash insecure kernel - but same result!]
is i need to flash CM7 via ODIN?
i cant able to see that 'recovery' options - Vol. UP + Pwr. butt. + Home = black screen!
srry fr disturbing all of you......
i am a newbie to this, just guide me .....
Just to reset everything: I would recommend to flash a stock ROM via ODIN first, the 3 parts version of KH3 with repartition, then flash the KH3 CF-root kernel to root the device and to get CWM recovery back.
Please read the guide in the following thread carefully:
http://forum.xda-developers.com/showthread.php?t=1075278
I flashed KH3 (3-part version) with repartition (PIT file) via ODIN and after that the KH3 CF-Root kernel.
At every ROM change I do a full wipe (factory/data/cache/format system/wipe dalvik)!
I never had any problems (Litening, MIUI, Galnet MIUI, CM7, Leomar Revolution).
thnks all of you! to bring my device back!
@[email protected],@SpaceCeph - thank you for helping!
i flash XXKH3 via ODIN now phone gets booted!.
i qiuck Query - what this XXKH3 stands for ?
because first i used indian version of XXKH8 - but its fails to boot, so i tried with XXKH3 as i dont know is it support to indian version!.
so can anyone guide me wht is XXKH3 or XXKH8?
thnks again!
Good to read that you were able to "reanimate" your S2 again.
Can't say anything in detail about version numbering. What I know, the "H" stays for August.
Recommendation: If you want a rock solid but customizable ROM, try Leomar's custom based ROM with his Kitchen App.
Leomar Revolution ROM 2.6 KH3
There will be a 2.7 with KI3, Android 2.3.5 from Leomar soon.

CyanogenMod 7 Flashing Issue

About a month ago I wanted to try out CM7 and see what it's worth.
I went to this thread: http://forum.xda-developers.com/showthread.php?t=1176411
I was using a stock GB ROM and rooted with CF-root kernel.
I downloaded the stable build and followed these instructions:
Install via ClockworkMod (do not use ROMManager for initial install):
1.Make sure you're running a rooted device.
2.Root your device and install ClockworkMod Recovery (http://forum.xda-developers.com/show....php?t=1118693)
3.Do a Nandroid backup!
4.WIPE (wipe data/factory reset + wipe cache partition) - do it for real.
5.Install the ROM from internal sdcard using ClockworkMod Recovery.
6.Do not reboot! We mean it - do nothing except choose zip and continue next step (if you come back to us with permission issues in install, we will know you did not read the directions and will call you an idiot). If it just plain hangs, reboot directly back into ClockworkMod recovery and continue at the next step.
7.Install the ROM from internal sdcard using ClockworkMod Recovery, again (due to a bug in the install).
8.Reboot
9.Install the Google Addon through ROMManager which is easiest, but you can
download the gapps.zip and install via ClockworkMod recovery instead.
Click to expand...
Click to collapse
When My phone booted it got into a bootloop.
I could not boot into recovery, I could only boot into download mode.
I searched the web and on one forum website I saw that someone encountered the same problem and after he encountered the bootloop he booted into download mode and flashed Siyah Kernel via Odin and his phone booted successfully.
I followed what he did and my phone booted into CM7.
After that I went on to other ROMs.
Two days ago I was running CM9 and I wanted to flash to CM7, so I downloaded CM7 nightly build #115 and did the following:
1) My phone was rooted with CWM. (CM9)
2) Wiped data, cache and dalvik.
3) Flashed the ROM twice.
4) Flashed GAPPS.
5) Rebooted.
6) "Samsung Galaxy S II with !" Screen.
7) "Kernel Panic" screen.
8) Took battery out.
*Tried booting into CWM with no success.
9) Booted.
10) Stages 6, 7 & 8.
11) Booted into download mode.
12) Flashed siyah kernel via odin.
13) CM7 working!
So there is my story!
I have also seen other people with the same problem, so it is not just me.
And here are my questions:
1) Why did these problems happen (kernel panic or bootloop)?
2) Why does Siyah Kernel fix these problems?
3) How can I prevent the bootloop/kernel panic from happening in the future (without flashing Siyah)?
Seconding the question as well as noting that it also occurs with Arif-Ali's nightly compiles.
did you wipe cache and dalvik cache after flashing cm7?
golcheck said:
did you wipe cache and dalvik cache after flashing cm7?
Click to expand...
Click to collapse
No, you dont need.
golcheck said:
did you wipe cache and dalvik cache after flashing cm7?
Click to expand...
Click to collapse
I did. I tried "messing" with CWM any which way and even flashed a stock rom in odin (and appropriate CF root). Nothing short of flashing Siyah (and probably any other kernel that supports CM7 except the one in the update zip) lets CM7 boot.
Net.silb said:
About a month ago I wanted to try out CM7 and see what it's worth.
I went to this thread: http://forum.xda-developers.com/showthread.php?t=1176411
I was using a stock GB ROM and rooted with CF-root kernel.
I downloaded the stable build and followed these instructions:
When My phone booted it got into a bootloop.
I could not boot into recovery, I could only boot into download mode.
I searched the web and on one forum website I saw that someone encountered the same problem and after he encountered the bootloop he booted into download mode and flashed Siyah Kernel via Odin and his phone booted successfully.
I followed what he did and my phone booted into CM7.
After that I went on to other ROMs.
Two days ago I was running CM9 and I wanted to flash to CM7, so I downloaded CM7 nightly build #115 and did the following:
1) My phone was rooted with CWM. (CM9)
2) Wiped data, cache and dalvik.
3) Flashed the ROM twice.
4) Flashed GAPPS.
5) Rebooted.
6) "Samsung Galaxy S II with !" Screen.
7) "Kernel Panic" screen.
8) Took battery out.
*Tried booting into CWM with no success.
9) Booted.
10) Stages 6, 7 & 8.
11) Booted into download mode.
12) Flashed siyah kernel via odin.
13) CM7 working!
So there is my story!
I have also seen other people with the same problem, so it is not just me.
And here are my questions:
1) Why did these problems happen (kernel panic or bootloop)?
2) Why does Siyah Kernel fix these problems?
3) How can I prevent the bootloop/kernel panic from happening in the future (without flashing Siyah)?
Click to expand...
Click to collapse
I fixed it.
This is how:
1. Make a CWM Backup.
2. Use Odin to flash I9100XXKI3, including the PIT (re-partition)
3. Flash this kernel (PDA section) and the old Bootloader (Bootloader section) with Odin.
4. Boot into CWM recovery and flash cm7+gapps.
5. Use Advance Restore in CWM to restore your /data partition if you want to.
I'm 90% certain that the problem was ICS's partition layout (PIT file).

[Q] Can't flash any new ROM/zips through CWM

Apologies this is my first post and am asking for help but this is driving me crazy now!
I don't seem to be able to flash ANY ROM zip files through CWM. When I try to install a Rom it loads for about 20seconds, says "finding update zip" "installing update zip" then "zip installed " then when it reboots it is stuck in a loop on the Samsung logo start up screen (one with the yellow triangle to say it is rooted).
Only thing I can do to get it working is to flash a ROM (new stock ICS one) through Odin, then root and restore from my backup - the only backup that will work is my backup of the ICS ROM none of my other backups work CM7 / CM9 if I try and restore them I just get in to the same loop.
I have tried this loads of times now - factory reset, wipe cache, wipe Dalvik cache, format system partition. I have tried installing ROM zip files twice etc etc.
This went wrong when I flashed the new stock ICS ROM in odin then tried to do a restore to CM7 not sure what I have managed to do to get it like this.
Anyone any ideas of what I can do to get it so I can install ROM's via CWM again so I can get back to CM7 or CM9?
Any help much appreciated - thanks.
Flash a new CWM and root kernel.
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
jje
Hi, thanks for the reply. I have tried flashing a new kernel a few times now but still get the same thing when I try and flash a new ROM in CWM, the install takes about 20 seconds then the phone is stuck in a loop at the first boot screen.
Any more ideas on what I can do?
:edit:
aha fixed this now, I followed this excellent guide http://forum.xda-developers.com/showthread.php?t=1457458 on Fix an unflashable or soft bricked GSII had to do the bootloader to get it to work.

[Q] Upgrading from cm 9.1.0 to 10.1 nightly

I haven't had much time to play around with my phone since cm 9.1.0 stable and have been out of it for a while.
I would like to confirm a couple of things about upgrading to the latest 10.1 nightly.
I currently have CWM 5.5.0.4 loaded. What is the procedure to update to the latest CWM Touch? Is the procedure the same as installing it on an unmodified phone?
Is my checklist for upgrading cm9.1.0 to the latest 10.1 nightly accurate?:
- Boot into Recovery
- Flash CM10.1 zip from SDCard
- Flash GApps zip from SDCard
- Reboot
- Wipe data of clock app
- Reset everything under Settings -> Date & Time otherwise editing alarms might cause FCs
Do let me know if I'm missing any steps.
just flash the recovery via Odin or recovery.
you're missing the fact that you have to wipe data before you flash
Well this is what I did to upgrade in case anyone wants to know:
- boot into download mode, flash cwm touch via odin
- ooot into recovery mode, flash cm10.1, gapps
- data wipe/factory reset
done!
still gets stuck on reboot after flashing the new rom. just remove battery and power on and ur good to go!
yes, that's what I said

GT-P5110 Softbrick, boot's only to recovery or download

Hi
Got a GT-P5110.
- boots to stock recovery (or other recovery) insted to system
- buttons are not stuck
- Original GT-P5110ZWAXEO (from file in efs), on case, on box
- Can flash CWM, philz, twrp recovery, it will boot the recovery
- After installing any custom rom (lineageos13, cm10, cm12, cm13, omni etc) it will boot to the recovery
- Choosing reboot in the recovery will power off the device, not reboot
- flashing factory rom (P5110XXDNH2 and some other) with odin works, after reboot it shows "Installing system update..", the blue bar goes to about half, after it will show "Erasing..." and power off after a second. Power on again it will boot to facotry recovery, in this place wipe data will work, wipe cache will give error.
- wiping the partitions work with custom recovery, chcecked from shell, partitions are writable, no errors
- flashed new PITfile with repartitioning, still no change.
- if i install a custom ROM, the battery charge screen will come from the custom rom.
So i can not get any OS working on this tab. Any ideas?
The 4-file ROM for odin i only found for GT-P5100, should i try to flash it?
I found the bootloader for P5110, should i flash it?
Thx
So i found my problem.
It was the like here, i missed this thread before. The dock/charge connector was faulty (looks like new) and prevents the tab from booting.
https://forum.xda-developers.com/galaxy-tab-2/help/gt-p5100-boot-recovery-download-mode-t3246322

Categories

Resources