[Q] Incorrect ROM installed on i9100 - BRICKED - Galaxy S II Q&A, Help & Troubleshooting

Hi,
Another Noob bricked his phone here SGS2 UK i9100.
I spent hours and hours reading all the FAQ's, various How To's but obviously not well enough although thought I had.
Im normally quite competent at things like this, dating back to early days chipping playstation 1's etc, done all sorts over the years without a hiccup. Had to fail sometime!
After the failed attempt, I suspect I may have flashed a custom ROM not compatible with the stock Kernel????
I rooted my i9100 using Chainfire's method:
[30.10.2012][CF-Root 5.6] K**,LA*,LP-126BHJQ73SC89DEFWGKIQOTUXY,LQ-5B - su+bb+CWM4/5
All went fine, root access, SU etc..
I then tried installing a custom ROM:
[ROM][4.2.1]Slim Bean - I9100 [Beta 2]
Followed the relevant instructions:
■Download software
■Enter CWM, wipe data, format system ( in mounts and storage)
■Flash Slim-GT-I9100-4.2.1.Beta.2-OFFICIAL then flash Slim_Gapps
All seemed to go fine, after flashing each of the above phone reported succesfu in CWM.
Anyway, rebooted as per instructions, phone shut down never to power up again!
Cant access download or recovery mode, nothing. Totally dead.
Ive ordered a USB Jig but doubt this will do anything at all?
Can someone please confirm what I did wrong (Should I have flashed Kernel 1st?)
Thanks.

nufcme said:
Hi,
Another Noob bricked his phone here SGS2 UK i9100.
I spent hours and hours reading all the FAQ's, various How To's but obviously not well enough although thought I had.
Im normally quite competent at things like this, dating back to early days chipping playstation 1's etc, done all sorts over the years without a hiccup. Had to fail sometime!
After the failed attempt, I suspect I may have flashed a custom ROM not compatible with the stock Kernel????
I rooted my i9100 using Chainfire's method:
[30.10.2012][CF-Root 5.6] K**,LA*,LP-126BHJQ73SC89DEFWGKIQOTUXY,LQ-5B - su+bb+CWM4/5
All went fine, root access, SU etc..
I then tried installing a custom ROM:
[ROM][4.2.1]Slim Bean - I9100 [Beta 2]
Followed the relevant instructions:
■Download software
■Enter CWM, wipe data, format system ( in mounts and storage)
■Flash Slim-GT-I9100-4.2.1.Beta.2-OFFICIAL then flash Slim_Gapps
All seemed to go fine, after flashing each of the above phone reported succesfu in CWM.
Anyway, rebooted as per instructions, phone shut down never to power up again!
Cant access download or recovery mode, nothing. Totally dead.
Ive ordered a USB Jig but doubt this will do anything at all?
Can someone please confirm what I did wrong (Should I have flashed Kernel 1st?)
Thanks.
Click to expand...
Click to collapse
What ROM were you on?
Please don't say 4.0.4.....

You should have done a nandroid backup after rooting. That would have given you something to fall back on.
Try removing battery for at least 10 mins. Refit. Plug in to wall charger. Give it an hour or so to see if it wakes up. If not then wait for the jig to arrive.
How much battery did you have when you flashed slim? Also, I wouldn't have formatted system. Always had issues with that.
Sent from my GT-I9100 using xda premium

YES, I was on 4.0.4
I did do a nandroid backup after rooting.
After trying to install another ROM prior to SlimBean, which kept hanging at the Samsung logo, I managed to restore from the nandroid backup fine, but after this one failing I cant enter recovery or download mode to recover, the phone is just dead! :crying:

If you wiped with a 4.0.4 kernel it's sayonara. Service centre for MB replacement. Fair chance they won't be able to tell you borked it & you'll get it done under warranty (assuming your warranty is still valid to begin with).

nufcme said:
YES, I was on 4.0.4
I did do a nandroid backup after rooting.
After trying to install another ROM prior to SlimBean, which kept hanging at the Samsung logo, I managed to restore from the nandroid backup fine, but after this one failing I cant enter recovery or download mode to recover, the phone is just dead! :crying:
Click to expand...
Click to collapse
Sorry man, but I gotta show this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Thanks for confirming what I already thought!!!
The 4.0.4 brick was 1st thing I read after, the law of sod!
Well out of warranty unfortunatley, I had this phone since s2 release day.
Unfortunatley to make matters worse, this is the missus' phone now since I got my s3 so I am really in trouble!!!!!!
How much am I looking for a MB replacement at Service Centre in UK?
Would this be something I could do myself buying a spare/repair phone off ebay with broken screen or something?
Thanks again for help.

I also have one i9100 it was GB out of box.
1. I updated with kies to 4.0.4 or 4.0.3 im not 100% sure was some time ago.
2. I flashed with odin leaked 4.1.2 jb.
And leaked version have some bags and i would racher go back to ics. Is it safe to flash stock 4.0.3/4 with odin?
Sent from my GT-I9010 using xda app-developers app

nufcme said:
Thanks for confirming what I already thought!!!
The 4.0.4 brick was 1st thing I read after, the law of sod!
Well out of warranty unfortunatley, I had this phone since s2 release day.
Unfortunatley to make matters worse, this is the missus' phone now since I got my s3 so I am really in trouble!!!!!!
How much am I looking for a MB replacement at Service Centre in UK?
Would this be something I could do myself buying a spare/repair phone off ebay with broken screen or something?
Thanks again for help.
Click to expand...
Click to collapse
You're talkin 200 euro or something like that (mobo).
And yeah, you could buy a broken SII and replace it, long shot tho.
Don't tell your wife just now, let the weekend go by (Run now, while you can!)
could try jtag too, still a long shot
---------- Post added at 10:23 AM ---------- Previous post was at 10:20 AM ----------
bg.stefan90 said:
I also have one i9100 it was GB out of box.
1. I updated with kies to 4.0.4 or 4.0.3 im not 100% sure was some time ago.
2. I flashed with odin leaked 4.1.2 jb.
And leaked version have some bags and i would racher go back to ics. Is it safe to flash stock 4.0.3/4 with odin?
Sent from my GT-I9010 using xda app-developers app
Click to expand...
Click to collapse
Go 4.0.3, learn from the OP.
Here, have a look.

HANG ON!!!!
Just realised the warranty is 24 months, got the phone on release day, this was end of April / beginning May 2011, right? That gives me 3-4 month left
Well, got to be worth a shot to save my balls!
Nothing to loose since its goosed!

nufcme said:
HANG ON!!!!
Just realised the warranty is 24 months, got the phone on release day, this was end of April / beginning May 2011, right? That gives me 3-4 month left
Well, got to be worth a shot to save my balls!
Nothing to loose since its goosed!
Click to expand...
Click to collapse
haha, time to practice "I dunno, I've just accepted an update when I was on wifi and all of a sudden, it went off, couldn't turn it on, crazy" rutine.

Related

help, odin didn't

now i'm no noob, i've odined plenty of times. but ever since i flashed eugenes 2.2.1 the first update, my phone has went crazy. i had to flash back to bionix and it worked but everytime my phone rebooted or i turned it off then on i wouldn't get service because flight mode was always active for some reason, but bionix was the only one after i unchecked it i would get service, because i flashed tons of 2.2.1 roms and other 2.2 roms and flight mode would always be checked after boot. even though bionix still worked it was acting funky sometimes so i just odined and i used the true firmware 2.1 from eugene instead of froyo but i doubt thats the deal, now after a successful odin , it passed, it keeps coming on and i flight mode is still checked but after the second media sd card scan it boot loops, everytime... the phone won't stay on past the sd card scans.. wtffffffff help pretty please
which recovery do you have? root it, get clockwork, format system, data, cache, reflash to jfd, mini kies to kb5. I just did this from a borked voodoo recovery.
Lol its been rooted. Im not a noob man. I just odined eugenes 2.2 official jk2 stock. Now phone boots and works fine. But when I reboot flight mode is always on... and some apps keep fcing over unistalled and re installed bunch of times same result. I did two odins wtf is wrong wit my phone
BTW something I forgot to mention, ever since flashing eugenes 2.2.1 under about phone my baseband version always says unknown, even after the odin twice it still says that on every rom. Everything was alwaya fine until I flashed that rom. Odins didn't fix so idk wut is up.
Sorry not to spam but ever since I flashed dead horse and the rom my IMEI always shows up as unknown, even after odin, on any rom.
Couple of things if you odin back t ostock and you still have issues then try
1. Use three button method to get into recovery mode.
2. Click delete all user data.
3. Reboot Enjoy!
Or try clearing the cache, reset phone in recovery and clear dalvik
oka1 said:
Couple of things if you odin back t ostock and you still have issues then try
1. Use three button method to get into recovery mode.
2. Click delete all user data.
3. Reboot Enjoy!
Or try clearing the cache, reset phone in recovery and clear dalvik
Click to expand...
Click to collapse
I do this before every rom flash :/
Where did you get the pit/tar for jfd?
Did you check the md5 sum?
Try my Alt Method in the noob guide (signature, bottom of post one)
Which recovery do you have?
s15274n said:
Where did you get the pit/tar for jfd?
Did you check the md5 sum?
Try my Alt Method in the noob guide (signature, bottom of post one)
Click to expand...
Click to collapse
I got the pit and pda from the eugene does not brick thread then I used the true stock 2.1 firmware after flashing eugenes does not brick. Phone turned on but after media scanning finished it went into boot loot doing the same thing. I then odined the stock official jk2 and phone works again. BUT the reasons I odined in the first place is still there. In about phone no matter what rom or modem I flash it always says unknown under baseband version , and it says unknown on my imei number too, and when I reboot the phone no matter wut rom flight mode is always on so I don't get service untill I turn it off. None of this ever happened until I flashed eugenes newest 2.2.1 rom and even after two odins it still is affected from it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
get clockwork and flash kb5 modem. then save all bytes from the sd card (internal) and wipe it. whatever is causing your problems is persistent through a full \system, \data, \sys, \etc, etc wipe, so it must be on the internal memory.
I am about to do the same to my phone right now...
1freedude said:
get clockwork and flash kb5 modem. then save all bytes from the sd card (internal) and wipe it. whatever is causing your problems is persistent through a full \system, \data, \sys, \etc, etc wipe, so it must be on the internal memory.
I am about to do the same to my phone right now...
Click to expand...
Click to collapse
Let me know of it works for u
worked
everything copied over fine except the hong kong stock rom, so i deleted it. the phone rebuilt the necessary folders and files (Android, dcim, external_sd, lost.dir, and sd).
So does it no longer say unknown for all of those things under about phone?
i didn't have that problem, i ****ed up my kernel/recovery. worse than boot loop, couldn't mount internal, voodoo wouldn't mount \system. my saving grace...odin back to stock.
firtst, i went back to ji6, but didn't have a data connection (probably had the same issue as you have now, i didn't bother to dig deeper), then tried mini kies to get updates, but kies didnt do anything so, i flashed to jfd, (im trying to find it now for you) this got me back to a shipped straight from the box state. with data.
kies (pita) updated to kb5 on its own, went wonderbar. fast data, really smooth ui, i thought it was a tweaked rom. i think i m gonna root it and keep the stock rom...
so, the moral of the story? install mini kies if you don't have it already, wait for the link when i find the jfd i used, flash it, and then upgrasde through mini kies. ou, then put the personal stuff back onto internal
here, i found it
http://www.multiupload.com/IFSJECTS3L
or this is from the source
http://forum.xda-developers.com/showpost.php?p=10871041&postcount=234

I think I Brick My G-tablet

My G tab doesn't go pass the boot animation.
When i do the Vol + plus power botton. It doesnt go into recovery mode.
I did Root the device and i was running
[ROM] VEGAn-TAB GingerEdition STABLE RC1.
How i got here
Last night i was a little drunk and i decided to play with my G-tablet. In my drunkenness i uninstall Rom manger and did a factory reset on the device. I want it to take it back to stock so i can return it and preorder an asus transformer. I only have today to return the device any help will be wonderfull
Start Here:
http://forum.xda-developers.com/showthread.php?t=861950
Use Bekit's 1105 image (nvflash_gtablet_2010110500.zip) do a factory data wipe as soon as it boots up. That should get you back to stock.
Thanks i will look into it
I did the NVFlash but it won't get pass the boot animation. The good thing is that the boot animation is the stock one that came with the phone.
Sent from my Droid using XDA App
thats a mighty big phone you have there.....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
jk
If your returning it, now you have the best excuse "it won't boot"
im having a similar problem. ive been stuck in a bootloop for days now. i managed to get it back to the "3 birds" but thats about as far as i can get.
it feels like im pretty close to getting this thing back up and running i just need to flash a new rom. the problem im having with this is i cant find the rom to flash. i put the rom on the sd card, but when i put it back in and boot up i cant find it anywhere in clockwork. (says no files found when trying to install zip from sd card.
So my question, is there a way to mount my device to the computer through clockworkmod so i can finaly flash a new rom.
or can anyone point me into the direction where i can find the files on the sd card
thanks in advance!
Lol I mean tablet.. omw to return the device..using the excuse that I updated the device and this happen. Can't wait till the 26th...Transformer FTW
Sent from my Droid using XDA App
Classic example why the G Tablet is getting a bad rep from the retail chains. If people would take the time to read the instructions that people have posted on these forums, all this could be prevented. If you don't understand them, ask a question. Nvflash is your friend when some thing goes wrong. Just saying.
jhreid1969 I agree 100% and was experiencing the same problem the user was above just a few weeks ago right after I bought my G Tab and began to play around with it. All one has to do is read the comments at the bottom of Roebeet's post on nvflash using bekit and they will find a post from Sprdtyf350 explaining that you must install and use clockwork mod to reformant after using nvflash and then it works fine !
Kartiel,
If you read the comments under Roebeet post for nvflash using bekit you will see a comment from a user named Sprdtyf350, he explains what you have to do using the clockwork mod to partion AFTER using nvflash !
What I did was install nvflash onto an external sd card then put it in my GTab and installed it. I then went throgh the process to format my sd card which if you are not familiar with can be found in the directions for installing clockwork mod.
After you format the card reboot and all should be well !
Yes... After nvflashing to get out of the loop you must clear cache and data and then in most cases repartition the device.
jhreid1969 said:
Classic example why the G Tablet is getting a bad rep from the retail chains. If people would take the time to read the instructions that people have posted on these forums, all this could be prevented. If you don't understand them, ask a question. Nvflash is your friend when some thing goes wrong. Just saying.
Click to expand...
Click to collapse
You are to quick to assume, sometimes issues arise even when instructions and steps are followed to the T.
Citi said:
You are to quick to assume, sometimes issues arise even when instructions and steps are followed to the T.
Click to expand...
Click to collapse
Yes on this particular issue I am. I have read on the forums about your problems Citi and you and others have gone in great depths trying to repair it. This person hardly tried and is going to blame the product for his mistake. My thoughts are you have a faulty unit and probably will not be repairable by flashing alone. This other person, probably used other conventional means to install ROMs which were not made to work with the G Tablet without maybe causing some serious problems, such as a ROM manager and didn't bother to learn how to do it safely by reading some facts first here on the furoms. If I have seen where he tried to get some help, or said he tried this and thar to repair it and not openly admitted to using a ROM manager, I would probably have a different oplnion about it.

[Q] Trying to flash ClockWork Recovery onto Galaxy Vibrant - QUITE FRUSTRATED

First off, I wanted to say that the XDA developers "Video for Noobs" was absolutely hillarious and informative at the same time. Great idea. NOW, on to the source of my infinite frustration.
I decided today that I wanted to root my Galaxy Vibrant that I got yesterday, and install a ICS ROM on it. I had no clue how to do anything as regards this, but I'm fluent with computers and I have a very good knowledge of Android in general. I don't know details on the coding side, but I have a good base of background knowledge. So, I started work around 3:00EST today. I've been working constantly SINCE THAT TIME (now 9:30 EST) trying to get root and install ClockWork Mod. But it will not work.
So, the details. I'm running Windows 8, 64-bit by the way. The first thing I tried, after looking up many guides and tutorials, was to install the Samsung USB Drivers and to get root and ROM manager. After some trial and error using SuperOneClick (2.3.3.0), I achieved root access, but I didn't have SU so I installed the app from the Play store. Then, I tried installing ClockWork Recovery from the ROM Manager, and I tried rebooting into CWR through the ROM manager. No dice, I got the standard "Android System Recovery" software. e3 variant (I've read up a bit on the different types, but I'm not too fluent in them yet). I tried the "Reinstall Packages" option so I could flash CWR, but that led to a certification error. No clue how to get around it.
I then figured out that I needed to have the DDM (Dalvik Debug Monitor) running to get proper root access. So I did that, and tried EVERYTHING again. I have wiped my phone about 5 times by this time. I went through a bunch of crap and eventually got it so that I CWR would TRY to flash once I got into the recovery screen. Basically, when I hit the "Reinstall Packages" button it goes through a few steps, a progress bar appears, and it says something along the lines of "Replacing stock recovery manager with ClockWork recovery". After just over a second of this, the phone restarts into the plain old recovery screen with no progress whatsoever.
I have ClockWorkMod 2.5.1.2 downloaded through ROM manager.
I have left it alone at this point.
I've tried using ADB, but there are no real guides that are up-to-date with the latest software and manually flashing an image from ClockWork Mod doesn't seem to work as they don't have image files anymore, just .zips with a bunch of single files and folders. I have no clue about Odin.
The ROM I'm trying to flash is Ice Cream Zenwich, which looks to be pretty promising. But I haven't even been able to get any kind of recovery manager working, so that doesn't help much.
Link: (add www) rootzwiki.com/topic/21742-romimm76i-iczen-rc18-the-hammer-of-buddha-5-26-12-deficient-development
I have tried manually flashing, but I haven't really made any progress in that area. I've tried ABD, I've tried CWR, and nothing I've been able to think of seems to work. SO I NEED HELP!
Just to state my system specs and software:
PC:
Windows 8 Consumer Preview, 64-bit
Android SDK and tools
Java JDK 6u29 ]______will this cause problems? Version 6 and 7 Java?
JRE Version 7 ]
Ice Cream Zenwich ROM (RC 1.8)
Phone:
Samsung Galaxy Vibrant, running Android 2.2
ROM Manager, ClockWork Mod Recovery 2.5.1.2 Downloaded
SuperUser
Titanium Backup
Root Tester
Absolutely ANY help would be insanely appreciated, I just can't work at this anymore.
Thanks in advance!
I know this is a bit early to bump, but I really need help with this still. Haven't made any progress.
Sent from my Vibrant using XDA
what instructions were you following? I believe Woodrube's instructions go over this, I'll check though. Here!
Also, get the AIO toolbox. Everything you need in one program. Very convenient. It's also linked in the instructions above. Flashing to stock, rooting, CWR, all just by clicking a button on your computer. AIO
If you get stuck again then just odin lindroid from http://forum.xda-developers.com/showthread.php?t=1057187&highlight=lindroid
It will give you everything ready for flashing ICS roms
dpaul007 said:
what instructions were you following? I believe Woodrube's instructions go over this, I'll check though. Here!
Also, get the AIO toolbox. Everything you need in one program. Very convenient. It's also linked in the instructions above. Flashing to stock, rooting, CWR, all just by clicking a button on your computer. AIO
Click to expand...
Click to collapse
Yep. I do believe all this is covered in there. Hardest part is finding the files (but they are out there). My guide's OP is short but comprehensive, so you should be able to go back to Eclair to ICS in under an hour (and that is a heavy handed time estimate). I can usually get it from 2.1 to ICZen in about 20 minutes and most of that time is waiting for the ROMs to settle down before I flash over them. Oh and since I have used GB bootloaders for some time, I am reminded of my Noob-i-ness when I have to get into Recovery on a Froyo bootloader. Last time it took me about 8 times to get there.
I understand it is frustrating, believe me I do, but it is all out there for the taking. Your OP is a good example of trying to dagnose a problem, not getting the answer and putting out as much info as you can to get help. Nice job on that.
Thanks for all the help
dpaul007 said:
what instructions were you following? I believe Woodrube's instructions go over this, I'll check though. Here!
Also, get the AIO toolbox. Everything you need in one program. Very convenient. It's also linked in the instructions above. Flashing to stock, rooting, CWR, all just by clicking a button on your computer. AIO
Click to expand...
Click to collapse
Thanks for that, I'll definitely take a look at this. I was pretty sure I was overthinking things, I think this might be a simpler solution.
I was following general instructions from various places (the ICZen page, etc), and at first I was following guides from all over the place. After I got my legs, this was the main rooting guide that I followed:
(add www) forum.xda-developers.com/showthread.php?t=1438478
And I was loosely following this guide for the ROM manager, CWR, etc:
(add www) androidauthority.com/vibrant-t959-ice-cream-sandwich-install-56729/
Woodrube said:
Yep. I do believe all this is covered in there. Hardest part is finding the files (but they are out there). My guide's OP is short but comprehensive, so you should be able to go back to Eclair to ICS in under an hour (and that is a heavy handed time estimate). I can usually get it from 2.1 to ICZen in about 20 minutes and most of that time is waiting for the ROMs to settle down before I flash over them. Oh and since I have used GB bootloaders for some time, I am reminded of my Noob-i-ness when I have to get into Recovery on a Froyo bootloader. Last time it took me about 8 times to get there.
I understand it is frustrating, believe me I do, but it is all out there for the taking. Your OP is a good example of trying to dagnose a problem, not getting the answer and putting out as much info as you can to get help. Nice job on that.
Click to expand...
Click to collapse
Thanks a lot for that, it does help a lot. I'm taking a look at that guide right now. Hopefully I can get through it without as much trouble as I had this time around (and without as much frustration). Also, I appreciate it that the author of the guide in question took the time to post here. Thanks again.
And in response to your comment on my OP, yes - I don't like it myself when people leave out information that may be critical to diagnosing their issue. It just prolongs things, makes the situation difficult, and its simply annoying. So I didn't want to be that guy. It looks like it worked!
mohitmoudgil said:
If you get stuck again then just odin lindroid from http://forum.xda-developers.com/showthread.php?t=1057187&highlight=lindroid
It will give you everything ready for flashing ICS roms
Click to expand...
Click to collapse
Thanks, if I do get stuck again I'll give this a try.
I appreciate all the help. I'll report on my progress soon. Hopefully, my next post will be about how happy I am to have ICS (or ICZen, rather) on my Vibrant!
Im probably late to the party but the way i get CWM is simply that i run the recovery 3e to 2e batch file (google 3e to 2e recovery) from my computer and then flash the CWM update.zip (its inside the clockworkmod folder ththat should be in the root of your sd) using reinstall packages, sometimes twice.. this should take you to CWM mod, after which i can flash the root package pretty easily
sent from the xda app on my android smartphone.
CWalkop said:
Also, I appreciate it that the author of the guide in question took the time to post here. Thanks again.
...Snip...
Hopefully, my next post will be about how happy I am to have ICS (or ICZen, rather) on my Vibrant!
Click to expand...
Click to collapse
No problems man. I am usually scanning the General and Q&A sections during the days to see if anyone needs help. At night I turn it over to others to troubleshoot.
I do have to tell you about a certain caveat in the ICZen flashing that is different than the others and almost everyone misses it on the first time they try.
Steps
-Download ICZen and place it on your internal sd
-Reboot to Clockwork Recovery
-Perform a wipedata/factory reset <---You must do this
-Go to mounts and storage and format the system partition
-Flash your downloaded ICZ rom file
-From the main menu of recovery, perform a wipedata/factory reset again <---AND this
-Reboot
-On bootup, give it a few minutes to settle in, reboot and use as normal.
-Enjoy your ICZen!
Click to expand...
Click to collapse
Most of the other ICS ROMs only have you Factory Reset once but you'll need to do it twice in ICZen, otherwise you'll get stuck in a bootloop.
W00T
Good timing with that post. I just came back here to report that I had got Odin, CyanogenMod, a Gingerbread Bootloader, and flashed back to 2.1, flashed Cyanogen mod and was JUST starting my ICZen flash. Interesting how booting into Recovery is built right into Cyanogenmod, I like that.
Anyway, I just performed a factory reset from the prompt that popped up right after I tried to flash ICZen (Deficient Touch Recovery, 5.5.0.4). I remember from the ICZen page that they told you to make SURE you had a CLEAN phone to start from, but I missed the second wipe step. Thanks for reminding me. I'm rebooting now, hopefully this'll work!
Edit: strange, I had to flash the ICZen ROM twice before I could get it to boot! I'm on the ICZen boot page as we speak, here we go...
Thanks for all your help. I'll post screenshots afterwards
CWalkop said:
Good timing with that post. I just came back here to report that I had got Odin, CyanogenMod, a Gingerbread Bootloader, and flashed back to 2.1, flashed Cyanogen mod and was JUST starting my ICZen flash.
Edit: strange, I had to flash the ICZen ROM twice before I could get it to boot! I'm on the ICZen boot page as we speak, here we go...
Click to expand...
Click to collapse
Noticed that you list GB bl's but not that you flashed them. If you did then no worries.
Re: your edit. If you got to the ICZen bootanimation and it still doesn't boot up, try wiping and factory reset again. Should work out after that. Good luck.
Woodrube said:
Noticed that you list GB bl's but not that you flashed them. If you did then no worries.
Click to expand...
Click to collapse
Ah, sorry for the confusion. I did in fact flash the GB bootloader, and it worked fine. I was confused for a bit because I thought I needed to choose a specific bootloader from the page you provided, but then I just chose one and it went through fine.
Re: your edit. If you got to the ICZen bootanimation and it still doesn't boot up, try wiping and factory reset again. Should work out after that. Good luck.
Click to expand...
Click to collapse
That's not exactly what happened; it just rebooted into the recovery manager again after I told it to reboot normally.
But...as you probably garnered from this post, everything worked perfectly after that! I booted into ICZen, setup the phone (no bloatware is nice), and started using it! Its even compatible with some apps that it wasn't before, which is great!
I attached some screenshots. It felt like the right thing to do.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
*cheers*
Thanks for all the help! You were great. I have over locked a bit; now I'm trying to set up Chainfire 3D so I can run the Tegra apps I bought for my previous tablet (ASUS Transformer, sold to save for the Infinity). I can probably find a guide of some kind online.
Sent from my SGH-T959 using XDA
Kind of random, but I find it really interesting that you can adjust the display color balance on ICZen. That's an absolutely incredible feature; I was actually hoping to find an app that would accomplish this but the built-in control seems to work great! Tweaked to my hearts desire.
Sent from my SGH-T959 using XDA

[Q]Does my GT-I9100 got bricked? Need help

Hello everyone! ^^
My phone now can not boot up when i press and hold power button. Here is my work before that:
- First, i use Odin to flash stock ICS I9100DXLPF
- Then, reboot to stock recovery, flash cwm (on sdcard) and use cwm flash superuser for root the phone and remove yeallow icon
- When completed, i reset the phone -> all worked
- Next, i reboot to stock recovery and flash cwm (on sdcard) again and wipe data/factory reset (i want flash custom ROM)
-> I wait for 10' but this cwm can't wipe
- Then, i press and hold power button for reboot -> And the phone poweroff, and never boot up again
Some questions:
- Does my phone got bricked? And how do it can brick, when i don't wipe system, only wipe factory/reset?
I need your help, friends
- I have efsbackup, if i change the motherboard, can i use my backed up efs for apply old imei? ^^
- If i buy a new s2 phone (but lost IMEI, so that dont hear the SIM), can i use efsbackup to apply my old imei for new phone?
Krensii said:
Hello everyone! ^^
My phone now can not boot up when i press and hold power button. Here is my work before that:
- First, i use Odin to flash stock ICS I9100DXLPF
- Then, reboot to stock recovery, flash cwm (on sdcard) and use cwm flash superuser for root the phone and remove yeallow icon
- When completed, i reset the phone -> all worked
- Next, i reboot to stock recovery and flash cwm (on sdcard) again and wipe data/factory reset (i want flash custom ROM)
-> I wait for 10' but this cwm can't wipe
- Then, i press and hold power button for reboot -> And the phone poweroff, and never boot up again
A question: Does my phone got bricked? And how do it can brick, when i don't wipe system, only wipe factory/reset?
I need your help, friends
Click to expand...
Click to collapse
Sounds like you may have had the unfortunate eMMC superbrick bug which hard-bricks your phone beyond saving (even by JTAG) this happens if you were one of the unfortunate ones (like me). If you running stock 4.0.4 kernal then this is certainly what has happened as you tried to wipe... give me a few mins i will get you thread
edit: couldnt find thread but i am 99% sure. What kernal were you running?
rsr1 said:
Sounds like you may have had the unfortunate eMMC superbrick bug which hard-bricks your phone beyond saving (even by JTAG) this happens if you were one of the unfortunate ones (like me). If you running stock 4.0.4 kernal then this is certainly what has happened as you tried to wipe... give me a few mins i will get you thread
edit: couldnt find thread but i am 99% sure. What kernal were you running?
Click to expand...
Click to collapse
Im using stock kernel of Stock ICS ROM (4.0.4). I just rooted, removed yellow icon...by cwm only, on sdcard
(This cwm independent work, and dont need custom kernel )
What can i do for save my phone? Thank bro
Krensii said:
Im using stock kernel of Stock ICS ROM (4.0.4). I just rooted, removed yellow icon...by cwm only, on sdcard
(This cwm independent work, and dont need custom kernel )
What can i do for save my phone? Thank bro
Click to expand...
Click to collapse
thanks for the quick reply..
i had same problem and didn't realize at first and sent it in for JTAG but it cannot be fixed..
ONLY option now is motherboard replacement.. if you still have Samsung warranty you will be fine as they cannot tell if you modified the phone because they change the whole board
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from the little guy
i have been monitoring many of your posts lately and they are all garbage. stop commenting useless stuff for post count moron
Are you stalking me?
Lol, why would I want to increase my post count? Think about it...WHY?
Nothing good comes to mind?
Let me spell it for you:
I.A.M.H.A.V.I.N.G.F.U.N.
And trying helping while I'm at it too.
Now go read something funny.
Sent from the little guy
rsr1 said:
thanks for the quick reply..
i had same problem and didn't realize at first and sent it in for JTAG but it cannot be fixed..
ONLY option now is motherboard replacement.. if you still have Samsung warranty you will be fine as they cannot tell if you modified the phone because they change the whole board
Click to expand...
Click to collapse
I have efsbackup, if i change the motherboard, can i use my backed up efs for apply old imei? ^^
Update some questions in #1
No, you can't. Your device should have the same IMEI if it's done by an authorised repairer. If it's done by someone who isn't an authorised repairer, who knows what will happen. One thing is for certain tho, if you try and restore your EFS backup when you get your phone fixed, there's a fair chance you'll bork it.
Don't try it.
Edit - No you cannot restore an EFS backup from one phone to another phone. The IMEI is a unique identifier that identifies a specific (one) device. Changing IMEI's is illegal in most countries, I suggest you stop talking about same or mods will close your thread (Per XDA rule "Don't do/say anything that gets us 'in trouble'")
Extra edit - @OP:- I've done a bit more rummaging through my SGS2 bookmarks, so far as whether you keep your existing IMEI or whether you get a new one when the board is replaced, it seems to vary a bit. Most old examples I could dig up where the person posted after they got the phone back kept their existing IMEI's, and a couple say they got new ones. Hard to say whether it's a country to country thing (seems that way) or whether it varies even amongst individual authorised repairers in the same country (less likely).
Regardless of what happens in your case, why would it matter whether you had the existing IMEI or a new one ? It makes absolutely no difference to you as a phone user, and would only make a difference to someone if there was some dodginess or 'shenanigans' going on. Rest assured, if your phone is fixed by an authorised repair, it will work exactly as it did before you borked it (minus the data you had in the internal storage, obviously).
Extra extra edit () - Tho if you get a board from a 'donor' phone & replace it yourself/get a local mobile shop to do it, you'll end up with the IMEI on that board. Again, I don't really recommend attempting to restore an EFS backup from another phone (And talking about same on here is nada).
MistahBungle said:
No, you can't. Your device should have the same IMEI if it's done by an authorised repairer. If it's done by someone who isn't an authorised repairer, who knows what will happen. One thing is for certain tho, if you try and restore your EFS backup when you get your phone fixed, there's a fair chance you'll bork it.
Don't try it.
Edit - No you cannot restore an EFS backup from one phone to another phone. The IMEI is a unique identifier that identifies a specific (one) device. Changing IMEI's is illegal in most countries, I suggest you stop talking about same or mods will close your thread (Per XDA rule "Don't do/say anything that gets us 'in trouble'")
Extra edit - @OP:- I've done a bit more rummaging through my SGS2 bookmarks, so far as whether you keep your existing IMEI or whether you get a new one when the board is replaced, it seems to vary a bit. Most old examples I could dig up where the person posted after they got the phone back kept their existing IMEI's, and a couple say they got new ones. Hard to say whether it's a country to country thing (seems that way) or whether it varies even amongst individual authorised repairers in the same country (less likely).
Regardless of what happens in your case, why would it matter whether you had the existing IMEI or a new one ? It makes absolutely no difference to you as a phone user, and would only make a difference to someone if there was some dodginess or 'shenanigans' going on. Rest assured, if your phone is fixed by an authorised repair, it will work exactly as it did before you borked it (minus the data you had in the internal storage, obviously).
Click to expand...
Click to collapse
Thank you sir, now i know that is not good thing. I'll dont talk about it again
You're welcome I hope having it repaired goes smoothly/quickly for you.

[Q] Xperia P only boots once(wat?)[SOLVED!]

Hey.
I have managed to get a really funny issue with, sadly, my moms Xperia P.
The P is running Nemesis kernel v6.3 and Honami MW v8, and of course unlocked BL, and have been working okay-ish(I cant say I particularly like the P).
Since its my mom's phone, and shes... well, not the youngest nor most tech-savvy person around, Ive done what I can to make it as 'user friendly' as possible.
But this time I mustve fked up badly...
Heres what I did: I was checking if I could get the AOSP incoming call screen in the same manner as the lock screen, so I tried renaming semcPhone.apk to something else, thinking the worst thing that could happen was a boot loop... Boy was I wrong...
Not only did the phone not start(no surprise there), but it even froze before the first "vibrate", making it impossible to enter recovery
Okay, no worries, I can still enter fastboot... So I went into fastboot and reflashed the boot - nope, still froze right away...
After much struggle to no avail, I tried a 'fastboot erase system' and lo' and behold! The stupid thing didnt freeze right away anymore and I could enter recovery!
Once In recovery I restored a backup I made a couple of weeks ago, and finally the phone started again! yay! :victory:
All is good then, right? .... nope...
Did a reboot, and it did the exact. same. thing. again. And I had to erase the system and restore the backup for the phone to boot again... wtf...
Okay, maybe erasing the system wasnt enough, right? So I did a factory reset, formatted system, data and cache, and went ahead of installing a fresh copy of Honami MW.......... Phone froze right away.... back to square 1...
Okay, so I repeated the process, but instead of installing a fresh MW, I restored the backup - phone booted fine Restarted the phone and back to square one again...
I tried installing a fresh copy a few more times, and it refused to boot each time. But restoring the backup boots the phone fine every time... whaaat?
The phone works perfectly fine once its booted, and I cant see anything wrong in the system at all, yet everytime I do a reboot it freezes right away and I have to erase system through fastboot(to get into recovery at all) and restore my ~2 week old backup. Its even enough to just do an "advanced restore" and chose system, leaving data and cache alone.
Ok so.. TL;DR: Phone freezes right away on first reboot, a fresh install of the ROM doesnt work - only restoring a backup do(it makes no sense!!)
I am completely out of ideas as to what can be the issue here... I have never experienced this kind of issue - especially not just by renaming "wrong" file(which gets restored during the reinstallation processes anyway)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Try flashing stock ftf completely and see if the issue persists(I guess it shouldn't)
Cheers,
AJ
Mm yes, flashing it back to stock ftf is the only thing I havent tried yet... But it still makes no sense. Why does it behave like this, regardless of complete wipes? And why is only a backup working, and not a clean install :s... My head's gonna explode over this >_<
Same here, have never been able to restore nandroid backup, always boots oince then its dead.
Anyone else have any bright ideas? I havent tried stock ftf yet(dont have access to the phone yet ), but somehow I have my doubts it will work...
I get the feeling the phone fails to mount the various partitions upon boot, but when checking permissions everything is exactly as it should be. Obviously Ive tried running 'fix permissions' in CWM, but that only results in a "/bin/sh: fix_permissions not found" which I also noticed my ZTE Blade says(which works fine despite all the cruel experiments Ive done on it lol).
Ive also tried to do a fresh install of BB and SU, as well as the whole rooting process(even though the ROM is already rooted) to no avail. (edit: also reinstalled recovery several times...)
Anyway, is there any app that can do a fix_permissions? Might be worth a shot...
Goatshocker said:
Anyone else have any bright ideas? I havent tried stock ftf yet(dont have access to the phone yet ), but somehow I have my doubts it will work...
I get the feeling the phone fails to mount the various partitions upon boot, but when checking permissions everything is exactly as it should be. Obviously Ive tried running 'fix permissions' in CWM, but that only results in a "/bin/sh: fix_permissions not found" which I also noticed my ZTE Blade says(which works fine despite all the cruel experiments Ive done on it lol).
Ive also tried to do a fresh install of BB and SU, as well as the whole rooting process(even though the ROM is already rooted) to no avail. (edit: also reinstalled recovery several times...)
Anyway, is there any app that can do a fix_permissions? Might be worth a shot...
Click to expand...
Click to collapse
Boot it wait 5-10 mins and then shut it down,do it again,and again until phone Boots needed to do it three times on Xperia U.
It only related to stock custom roms od 4.1.2.
Sent from my Xperia U using Tapatalk
XperianPro said:
Boot it wait 5-10 mins and then shut it down,do it again,and again until phone Boots needed to do it three times on Xperia U.
It only related to stock custom roms od 4.1.2.
Sent from my Xperia U using Tapatalk
Click to expand...
Click to collapse
You mean boot it to where it freezes(right away) and wait 10mins, or boot into system and wait 10mins? If the first, I think Ive tried that a few times. Doesnt hurt to try again though...
Do you have to do this every boot or just once after a flash?
Still makes no sense why it just started doing this "out of the blue"(If we ignore the fact I renamed a file, cause I seriously doubt that that specific action could cause this issue).
Edit: Dude.... That **** actually worked! I didnt wait 10mins, but maybe 2-3... Forced shutdowned it and started it roughly 5 times, the 6th time it started! Im currently rebooting it all the time(3 times so far... 4 now lol.. ok 5..) and it has started every time!!
Thank you for your tip (I should make some more accounts so I can hit 'thanks' a few more times lol)

Categories

Resources