Related
I lurked around the GlitchV13 forum for a good long time and didn't find an answer to this.. and because I've only been lurking for about a year I wasn't able to post anything, so it's about time I guess.
I'm having problems with the GlitchV13 kernel. Maybe I'm just being dumb and don't see something here. some help would be greatly appreciated.
I flashed GlitchV13 on my CM7.1 using CWM 5.0.2.7. No problems at all. Running great for two days. Suddenly, my phone won't connect to wifi. Cycled airplane mode and nothing popped up, so I did a reboot.. annnd got stuck in a bootloop between the CM splash and my lockscreen (wtf). Rebooted again, and now I'm stuck on the CM7 screen. Tried to Odin CWM4, still no bueno, and I get a "E:Can't mount recovery/log/"blahblahblah.
Admittedly, this happened one time before- I did a clean install from stock. Then I got gutsy and flashed GV13 again. Any idea why this is happening? After I flashed Glitch I didn't touch any other recoveries, nor did I try to push anything with Odin or Heimdall.
I really just don't wanna flash back to stock again, and a new solution to why this is happening would be super!
Thanks in advance.
EDIT: Got it. Glitch comes packaged with 4.x CWM, while CM7 comes packaged with 5.0.2.7. Any way to reconcile the two? Worth it to push 4.x over 5.x, flash Glitch then backup so I don't have to do a full restore to CM7?
I had the wifi problem on the stock kernel once, so I dont think that problem is with Glitch.
I also just flashed the latest kernel version and they have updated CWM to 5.0.2.7.
That being said are you sure the recovery is making this much trouble on the phone? Usually it doesn't make a difference (besides backups and whatnot).
The glitch recovery has a few extra features that the CM7 recovery does not.
one being able to wipe dalvik and cache at the same time. (very minor but its more convenient)
I personally think its worth it.
I recently installed the nightly build of ICS on my samsung vibrant. Today the phone had a error that said encryption cannot be completed phone must be erased. I let it do a factory reset . Then I got stuck in a endless boot cycle showing the vibrant logo and then the cynogen guy for a few seconds then reboot. I could still access the recovery menu but it refused to flash any roms I threw at it. I downloaded and ran odin 1 click recovery and it changed my tmobile phone to a att phone. And it lost the recovery mode. It just shows att screen first then samsung vibrant second and just reboots. I can still get into download mode and flash roms using odin 3 but no matter what rom I select or if I choose repartion or not the flash will go through successfully but then the phone reboots into same problem as before. I suspect the recovery files are gone since no button combination anymore gets me into recovery. Is there anything else I can do?
Man I am having the exact same problem. I really hope someone can figure something out soon. Did yours randomly get that error? Or did you actually try to encrypt your phone?
Sounds like you used the wrong Odin 1 Click. If it installed Captivate bootloaders, that would cause a problem.
This is your best shot I think
http://forum.xda-developers.com/showthread.php?p=24418319
Sent from my A500 using Tapatalk 2
It just happened
It happened on its own. Was working fine all day walked in my house as as soon as it hit wifi it started going crazy. I had the data plan turned off months ago. Maybe theres something to it connecting up to the net. I have found out if you install your sim you get a reduced menu of recovery options but without sim it just constantly reboots. it only gives option of reboot, reinstall packages,delete all user data, delete cache data. If you try reinstalling the packages theres nothing there. Deleting caches made no differance. ADB does work and responds while in this lesser form of recovery is there a easy way to use adb to force a full system flash?
Thanks
That link was perfect had a link to eugenes no brick froyo rom which fixed my problem. Dloaded that used its pit and tar files and repartioned and im back to stock. Going back to team whiskeys mod. If all ICS roms has bugs like that is unusable.
bfranklin1986 said:
This is your best shot I think
http://forum.xda-developers.com/showthread.php?p=24418319
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
Do you have access to BOTH your internal and external SD cards? The Encryption Bug is totally and completely random and does not discriminate. There is currently no known reason or solution. Several of us across a few different devices have been working on this for months.
Consider yourself luck if you have access to both SDs as you are the 2nd person to get in and out today. Many, many others have not been as fortunate.
If you could please pull up this thread and put as much information in there as possible, it would be greatly appreciated. Are you unlocked, what happened right before, what bootloaders are you on, what ROM were you trying to flash, what ROM did you end up getting booted,....those types of things. As much detail as you can muster together, after you catch your breath and relax a minute.
Guys DO NOT run ICS unless you have read up on the Encryption Unsuccessful bug and except the possible consequences! Every ICS T959 rom should have a warning IMO.
There is no known fix > just a work around. Odin / Heimdall / Jtag = useless
Update
I think I might have pulled the trigger to quick. While the link above did give me Eugenes rom which at least got me out of the boot cycle both internal and external sd shows 0 and I am unable to load anything on either card. I have tried differant microsd cards all of them show the same thing. So eugenes rom got me working kind of but cant store anything at all. That sucks loved my vibrant and its almost out of contract and planned on using on prepay.
Agreed 100 %
Had I of known would of stuck around on my team whiskey rom which never gave me any problems. Does this ICS bug affect amazon kindles? Ive put cynogen9 on 2 of them and am wondering if I shouldnt take it off before they turn into paper weights.
Moped_Ryder said:
Guys DO NOT run ICS unless you have read up on the Encryption Unsuccessful bug and except the possible consequences! Every ICS T959 rom should have a warning IMO.
There is no known fix > just a work around. Odin / Heimdall / Jtag = useless
Click to expand...
Click to collapse
chickenmon said:
Had I of known would of stuck around on my team whiskey rom which never gave me any problems. Does this ICS bug affect amazon kindles? Ive put cynogen9 on 2 of them and am wondering if I shouldnt take it off before they turn into paper weights.
Click to expand...
Click to collapse
I got tagged on a Nook Color with it. BUT, since the Nook Color has a feature that no others I think do (you can boot a ROM straight from an SD card and not mess with the oringinal OS at all), I was able to just pull my Microsd out and reformat it and then put CM7 on it for my wife.
So far from what I have seen and been working on:
Vibrant, Captivate, My wife's Nook Color, A few Transformers, SGSII,...
Anything I can do?
Anything I can do to get my partions right again? I can flash the twm 5.2.2 but none of the roms i throw at it including ics passion stays in a boot cycle. Only rom that works is eugenes froyo that does not brick and it doesnt allow internal or external mem to be seen.
chickenmon said:
... Only rom that works is eugenes froyo that does not brick and it doesnt allow internal or external mem to be seen.
Click to expand...
Click to collapse
You may want to bring up this issue directly in Merio90's thread. I believe Alex9090 went thru possibly similar issues and may be able to help you in that thread (unless she happens to pop in here).
I'm assuming you were trying to mount sdcard and emmc within recovery first (storage and mounts)? If you do have access to recovery again and can mount the external sdcard, maybe try repartitioning the card within recovery (using the parameters in Merio90's instructions)? Then transfer your rom zip and re-flash.
People have actually flashed Eugene's Froyo post-EU ... but without an ext sdcard. Quite an oddity. It's the only one (AFAIK) that'll fully boot up (even after losing int sdcard access due to EU) yet without an external sdcard in place.
Your assumptions are correct. I cannot mount emmc. I cannot flash any rom via 2.5 or 5.2 recovery only through odin and only eugenes rom still allows phone to boot but no mounting of internal or external sds. Ive spent about 3 days on this. There must be some hardcore adb commands to force a true factory reset partioning and all. Very annoying. Thanks for the help if I find any ways to fix it I will repost it here.
Might be bricked?
Ok, i will admit up front that I probably did something stupid and now am sending out a cry for help. Until yesterday I had ICS 4.0.3 successfully installed. I believe it was Euphoria flavor. But, I constantly had shortage of memory problems with the new force close language on apps running in bg - was laggy. Here is where it all went wrong - Decided to dl and install CM9 nightly to fix my laggy install. Recovery went fine, but rom failed, rebooted and sent error to cm. Tried new tactic - dl and installed Slim ICS - wrong, got stuck in boot loop - but could still get into download mode. Ran Odin to restore to stock. Ran fine but Failed - no explanation, just failed. Since it would not respond, finally turned it off - OFF has now become permanent! Power button does nothing. Charging does not light up screen. No download or recovery mode! Really fearful that this IS bad. Help, help, help!!
Open to suggestion. . .
JIM in FLA
Not related at all to my original problem.
tenantrep said:
Ok, i will admit up front that I probably did something stupid and now am sending out a cry for help. Until yesterday I had ICS 4.0.3 successfully installed. I believe it was Euphoria flavor. But, I constantly had shortage of memory problems with the new force close language on apps running in bg - was laggy. Here is where it all went wrong - Decided to dl and install CM9 nightly to fix my laggy install. Recovery went fine, but rom failed, rebooted and sent error to cm. Tried new tactic - dl and installed Slim ICS - wrong, got stuck in boot loop - but could still get into download mode. Ran Odin to restore to stock. Ran fine but Failed - no explanation, just failed. Since it would not respond, finally turned it off - OFF has now become permanent! Power button does nothing. Charging does not light up screen. No download or recovery mode! Really fearful that this IS bad. Help, help, help!!
Open to suggestion. . .
JIM in FLA
Click to expand...
Click to collapse
First of all, not to sound like a ****; but it's rude to hijack someone elses thread. You should've created your own thread for this.
Second; you might have fried your bootloader which in turn, yeah, that's bad and you might have bricked your phone.
Did you try to boot into recovery via the battery pull method. If not, try that and see how it works. I would link you to the instructions but I'm too lazy and tired right now to search for it and again, this is someone else's thread. Just do a search for it and you should find it.
If you need more help or guidance, create your own thread and start there.
Noticed your running Ice Cream Zenwich rc1.3. How do you like it. Ive installed slim 3 times today and twice I have gotten the encryption error within a hour. Needless to say not impressed major pain in the ass to have to do a million and half tricks with awm, adb, popping sd cards in and out etc.
Update
Also the current build of ics slim does not allow the imei information to be retrieved from sim for tmobile requiring a reflash of the modem. You have to download and install a new modem. I used csm5. The guide on the link in this post dow work but its a real pain and requires lots of trial and error. Wondering if google intentionally bricking these things knowing we all got gadget lust for the sIII now.
chickenmon said:
Noticed your running Ice Cream Zenwich rc1.3. How do you like it ...
Click to expand...
Click to collapse
ICZen_rc1.8.3 (AOKP #39, ICS 4.0.4) + subZero #144 (New Test Kernel just released in mr_pyscho's RootzWiki kernel thread) is Linaro infused ... and I've got to say the combo is THE fastest rom experience I've ever had on my Vibe. Whatever MP did in his new test kernel just blows the doors off the previous performance limits.
Btw .. you keep encountering EU again. Really odd unless possibly your external card wasn't partitioned correctly. Not a knock directly on you, but it is a common occurrence lately. FYI, I repartitioned mine directly from recovery.
Also ... Br1cK'd (ICZen) and mr_psycho (subZero) are aware of the EU situation and try to include safeguards in their builds. However, until we know the exact root cause of EU, we're all just shooting in the dark. Imo, it's at least comforting to use a rom & kernel where the dev's are at least mindful of EU.
Greetings
As the tittle points outs, I flashed the latest Androwook Rom(2.1) and it always stucks at the Intro Crawl. I re-downloaded it, flashed it again, but had had no success.
The Prime has been unlocked since May, and it was running the Cyanogen Nightly Rom, before I tried the Wook one. I wiped Cache and Delvik, and tried an older build as well with no success. I use the latest TWRP, 2.1.3. I also tried all availlable kernels and options during the installation with no success.
Can anyone give me a hint as to what is the problem? I can always go back to CM Rom, but I would feel like I accepted defeat.
Also, why does the installation always wipe my internal sd card , when no such option is selected?
drsane1984 said:
Greetings
As the tittle points outs, I flashed the latest Androwook Rom(2.1) and it always stucks at the Intro Crawl. I re-downloaded it, flashed it again, but had had no success.
The Prime has been unlocked since May, and it was running the Cyanogen Nightly Rom, before I tried the Wook one. I wiped Cache and Delvik, and tried an older build as well with no success. I use the latest TWRP, 2.1.3. I also tried all availlable kernels and options during the installation with no success.
Can anyone give me a hint as to what is the problem? I can always go back to CM Rom, but I would feel like I accepted defeat.
Also, why does the installation always wipe my internal sd card , when no such option is selected?
Click to expand...
Click to collapse
jumping from one rom to another needs a full wipe i guess... when you said wiping your internal sd card, that's the reason why you're stuck into crawling? so i guess you use adb to push the ROM, then flash again?
in my case, when i had a bootlop, i push fullwipe.zip first, flash it, then push Androwook.zip, then flash it... it all came back alive..
First of all, thank you for your reply!
Now, to adress each step
jumping from one rom to another needs a full wipe i guess.
Click to expand...
Click to collapse
Yup, did one (factory reset+system wipe) before trying to flash AW Rom.
when you said wiping your internal sd card, that's the reason why you're stuck into crawling? so i guess you use adb to push the ROM, then flash again?
Click to expand...
Click to collapse
After the first three unsuccessfull attempt to flash the ROM did I wipe my internal SD, so it isn't the crawling looping intro's problem. And yes, I push ROMs via Adb, and trying flashing.
in my case, when i had a bootlop, i push fullwipe.zip first, flash it, then push Androwook.zip, then flash it... it all came back alive..
Click to expand...
Click to collapse
That was actually the last step I tried before asking for help. Even after I typed this post, I did it again. Flashed it, pushed AW, and flashed again. No success.
*Edit: I have forgotten a primary Troubleshooting technique. Downloading AW2.1 from a different source, will update.
sorry but im not much of a help i can see... hope somebody could. don't lose hope though...
Intentions matter
Thanks for your time anyway!
After two more failed flashes, I got it to boot!
Apparently the starting animation was causing some kind of problem, which I cannot ever imagine. After I checked the option to have the uggly original boot animation, the rom booted normally and I am now using it.
I am quite happy to get it to work, but if anyone has any solution to the boot problem, I would be really glad to hear him!
drsane1984 said:
Intentions matter
Thanks for your time anyway!
After two more failed flashes, I got it to boot!
Apparently the starting animation was causing some kind of problem, which I cannot ever imagine. After I checked the option to have the uggly original boot animation, the rom booted normally and I am now using it.
I am quite happy to get it to work, but if anyone has any solution to the boot problem, I would be really glad to hear him!
Click to expand...
Click to collapse
Hello Everybody! Guys, sorry for my english!!!!!
First of all, I have to present myself, my name is Marco, I'm italian, 25 years old and I'm in the Android world since about 12 Years.
I started whit a Galaxy S2, and after I bought an Asus Transformer Prime.
After just two week, I decided to put in a Custom ROM, on my devices, and I understood how the system work better instead of a Stock ROM!
And after, I understood, how the XDA Developers Forum is important for me, and expecially for all the people who like to learn about the Android World.
So, I just want to Thanks with all of you for the support that i receive EVERY DAY to solve my problems!
One of these was with flashing the Androwook, weeks ago I flashed the Team EOS 2.0, that was really amazing, but after a While, I found some slowdowns in some action on the system, so i decided to try a rom based on the stock rom, but with improvement and tweaks, so what's better then the Androwook?
The problem was, the same explained on this post, after all wipes, the prime was not boot, and stuck in bootanimation!
I solved, checking the box "Install custom ROM" as drsane1984 have done, and now the ROM is booted perfectly!!
Thanks another time! I'am convinced that if you are able to seach, you'll find for sure the solution to your problems! If not, just ask!
Bye!
Hello all,
I have tried many things before asking for help, but nothing worked so far.
Here is the story:
I was on ICS 4.0.4, with default ROM coming from carrier.
I wanted to install CM9.1,
spent countless hours doing all backup and reading tutorial.
Tried finally yesterday and it was stuck doing "wiping data". Left it for 20min+ and nothing.
After restarting it, it is now stuck on the boot logo.
I couldn't enter anymore CWM or stock recovery (up+home+power), but could enter Download mode.
So I tried a couple of things I have read on the forum, like installing Siyah-s2-v5.0.1.tar through Odin 3.04 but I still cannot enter recovery mode.
I've read (too late) about the mmc brick bug (couldn't find anyone speaking about it in any tutorial until I reached this point... nothing on CM wiki or in other tuto... classic!).
I hope I'm not in this case though as I can still go to DL mode, and the phones having the brick bug are completely dead (blank screen or no DL mode), as per http://forum.xda-developers.com/showthread.php?t=1756242
I managed to finally get CWM working only by using GT-I9100_ICS_ClockworkMod-Recovery_5.5.0.4.tar from Odin, then tried to install CM9.1 from SD card but after reboot it is stuck on the blue cyanogenmod animation boot screen and nothing happens.
Tried also to restore from CWM my nandroid backup, but during the restore it seems to hang then restart by itself, and then I'm back to Galaxy S boot logo (the animated one with the big S).
And after this I have lost again access to recovery mode.
I can't go back to stock and I can't install CM... I was not expecting such issues, it all seemed pretty basic on paper.
I'm really stressed and don't know what to do
Flash a stock rom in Odin (download mode), re-root your phone/flash a kernel with CWM, restore your backup ?
Hi,
thanks for answering,
I have tried to locate such a rom, but I'm not sure which one... is there a specific one to try ? could you point me to it please ?
so far I have tried I9100XXLPQ_I9100OXALPQ_I9100XXLPQ_HOME.tar.md5
but no luck
you also say "re-root", at the time I used this method:
[GUIDE] ROOT/UNROOT Stock ICS Firmware without flashing unsecure kernel - xda-developers
http://forum.xda-developers.com/showthread.php?t=1501719
Do I need root to install Siyah kernel from Odin ?
I'm trying one from sammobile... let's hope :/
The bad thing is I had no Yellow triangle at the beginning since I'm stuck in this boot loop or no boot to be precise.
Now that I have tried different things to fix it, it is still not working and I have my flash counter = 10.
I cannot even go back to the shop, is there a way to reset it knowing I cannot even reach the OS, I have only DL mode or CWM...
Use a stock rom for your region/carrier (or any stock rom from any region really), it doesn't really matter as I presume you'll be restoring a backup and/or going back to a custom rom anyway won't you ?
Samfirmware & AndroidFirmwares.net have lots of stock roms.
No, you don't need root to flash an Odin version of Siyah. So yes, you can flash that after you've got stock up & running to root your phone rather than re-rooting your phone by flashing a CFRoot kernel or using another root method. Just make sure the version of Siyah you're going to flash matches up with the stock rom you've got on (I.E if you flash a GB stock rom use GB Siyah, ICS stock = use ICS Siyah, etc, etc).
thank you again, I'm downloading the rom from sammobile matching my carrier,
Would you be so kind to send me a PM with your skype username or anything to "chat" with you ? I'm really worried and I spent all night already trying to fix it with no progress at all
Don't worry about the flash counter. That's the least of your problems while your phone is borked Worry about it when it's fixed. There's nothing you can do about the triangle while your phone is cactus.
When you've got it up & running again, use Triangle Away.
But first things first.
---------- Post added at 04:02 AM ---------- Previous post was at 03:59 AM ----------
You're welcome.
Um, no. Absolutely not. Nothing personal, but if I did that for every person who's asked me for 'hands on' help since I've been here, I'd have spent my time doing nothing else. I don't do 'personal' with people from XDA (which is why I have PM's blocked except for mods).
Besides, you're going to learn much more fixing this yourself. I've given you a stack of information thus far, ball is in your court. Every answer to every question you could possibly ask is on this site. It just sometimes takes a bit of work/reading on your part to find it.
megosu said:
thank you again, I'm downloading the rom from sammobile matching my carrier,
Would you be so kind to send me a PM with your skype username or anything to "chat" with you ? I'm really worried and I spent all night already trying to fix it with no progress at all
Click to expand...
Click to collapse
ok I understand.. it is just I have literally spent more than 8 hours on it and had not make any progress at all (even worse I cannot return it to the shop because of the yellow triangle).
I appreciate your help, it gives me a bit of hope but I'm in a very bad situation and I feel I have read and do so much already with no success at all.
I will try your option of restoring the one from Sammobile, I have tried other before without any luck, maybe this one will do... (5min left to DL it).
thanks again for your support
I know where you're coming from. The first flash I tried when I got my phone in 2011 borked because I was careless, and it took me a bit over a day to get the right info/files/etc to get it fixed. I know it's frustrating/tiring/annoying & you're wondering at the start whether you can even fix it. But as long as you've got download mode 99 times out of 100 you can save it.
And as I said, it's good experience; once you've fixed it, you'll be able to handle anything that comes up in future
Let us know how you go. I'm going to bed shortly, but I'm sure someone else will step up & help if you have any further problems.
You're welcome Happy to point you in the right direction.
I have flashed the rom, the exact same one as I had before everything happened...
if it helps, I flashed it from Odin 3.04 as PDA.
I9100BVLPH_I9100TMULPH_I9100BVLPE_HOME.tar.md5
I'm now back to the Samsung GALAXY S2 GT-I9100 logo and nothing happens.
I cannot use recovery mode,
I can use DL mode (it shows 11 counts and current binary as Samsung official.)
update:
I left the phone on the first logo for about 5min and it moved to the next Samsung Galaxy S2 logo, with the big animated S.
I'm waiting but nothing else is happening.
I'm still desperate to fix it.
One thing which can be relevant, whenever I try to wipe or format /data from CWM, my phone is restarting after a few minutes or is saying it cannot be done.
I can format /cache and /system.
Could it be the root cause ? Any way of fixing it ?
Thank you
update: I cannot mount /data from CWM, it says Error mounting /data!
is it the brick bug ? :|
Easy now....your device is still good.
Those animations should take like 1-2 mins when you flash a rom.
Now, you are completly sure that you are actually flashing the right ROM for your device model?
If so, just keep flashing stock roms until you're up and running again, so you can start from scrap.
I tried, the issue is as soon as I flash a stock rom (through Odin), then I can't get into stock recovery mode anymore, I have to flash GT-I9100_ICS_ClockworkMod-Recovery_5.5.0.4.tar to get back the recovery mode.
I tried to flash several times, I think it is down to the fact I cannot mount or format /data.
Which is why I'm wondering if it is the famous brick bug.
My device is GT-I9100 and I took the stock rom from sammobile:
I9100BVLPH_I9100TMULPH_I9100BVLPE_HOME.tar.md5 which is ICS 4.0.4 (that I had before trying to move to CM9.1 and having all this mess in my hands.)
flash this:
http://www.sammobile.com/2012/11/15/i9100xxlsj-%E2%80%93-galaxy-s-ii-android-4-1-2-jelly-bean-test-firmware/.
you are on siyah kernel right?
what you wanna do know is to get to whatever rom your flashing, forget about cmw for now.
this also might help:
http://forum.xda-developers.com/showthread.php?t=1457458
So it is not lost yet ? Not the brick bug ?
just to be sure:
you want me to install through Odin: Siyah-s2-v5.0.1-CWM.zip
then going back to DL mode
I flash through Odin: I9100XXLSJ_I9100OXXLS1_OXX.zip (coming from your link).
anything I'm missing (even if it seems obvious, please let me know as I'm maybe missing something important)
?
I still cannot do Factory reset... is it a problem ?
I dunno what kernel you are using, If stock 4.0.4 kernel you should flash siyah first (safe kernel, no brick bug), and then countinue flashing the ROM. Check out the brick bug thread in general SII forum for directions if you want.
BTW, Odin recognizes your phone right? Check it out, you'll get a huge long breath.
BTW 2: you don't have any kies applications running in your pc.....am I right? if so, CLOSE THEM ALL!
I did had stock 4.0.4 kernel when I first tried to follow CM9.1 wiki, and I did a factory reset through CWM... which is why I think I might have bricked it...
I have checked the brick bug thread (too late it seems...) but so far I can't be sure if I'm in this case or not as they say they can't even reach DL mode, and I can.
Odin recognizes my phone, yes, but anything I flash is stuck on the animated logo.
I do not have Kies installed, just installed the drivers.
Hello, I'll try to explain what happened to get where I am now, and explain with details the last errors of my GT-9100.
I had a stock room jelly bean 4.1.2 installed. I had Android encrypted + SDCARD encrypted, and decided to format, but I didn't undo the encryption. As result, after master reseting it, it asked for a password do decrypt (as always asked when I turned the phone on), but it wasn't recognizing my password anymore. So I tried to clean and wipe all possible things, which ended on the device stucking at boot (doing boot loops, not asking for password anymore). I got an error on CW Recovery E: Could not load emmc (sounds like my internal storage is gone)
Later on, I tried to re-install the ROM, but got alot of trouble with windows drivers. Couldn't get any rom installed again. My device was then stuck at start, not even showing the white Samsung Galaxy S II GT9100 screen. After trying a variety of MODEMs, Kernels, I always get stuck on boot.info, zimage (kernel) on ODIN (Both 1.85 and 3.07 versions).
The only thing that has worked so far is changing the bootloader to the stock version. After doing this, my smartphone turns on on Chinese language. The ROM loaded is a jelly bean, but it has no status bar, can't open camera/folder explorer, can't do calls, can't acess internet, doesn't even show the configuration menu. And everything is chinese. BTW Calculator was working lol.
So this is the situation. Has my internal storage been gone forever? Is there a way I can flash without being stuck at boot.info or zImage when trying to flash kernel, both on Odin messages? Or is my phone really bricked? Thansk alot, I'll pay close attention to this.
EDIT: I haven't found after a day of research anyone that did data wipes in an encrypted phone, so this can be a guide for any future similar case.
gerijeb said:
Hello, I'll try to explain what happened to get where I am now, and explain with details the last errors of my GT-9100.
I had a stock room jelly bean 4.1.2 installed. I had Android encrypted + SDCARD encrypted, and decided to format, but I didn't undo the encryption. As result, after master reseting it, it asked for a password do decrypt (as always asked when I turned the phone on), but it wasn't recognizing my password anymore. So I tried to clean and wipe all possible things, which ended on the device stucking at boot (doing boot loops, not asking for password anymore). I got an error on CW Recovery E: Could not load emmc (sounds like my internal storage is gone)
Later on, I tried to re-install the ROM, but got alot of trouble with windows drivers. Couldn't get any rom installed again. My device was then stuck at start, not even showing the white Samsung Galaxy S II GT9100 screen. After trying a variety of MODEMs, Kernels, I always get stuck on boot.info, zimage (kernel) on ODIN (Both 1.85 and 3.07 versions).
The only thing that has worked so far is changing the bootloader to the stock version. After doing this, my smartphone turns on on Chinese language. The ROM loaded is a jelly bean, but it has no status bar, can't open camera/folder explorer, can't do calls, can't acess internet, doesn't even show the configuration menu. And everything is chinese. BTW Calculator was working lol.
So this is the situation. Has my internal storage been gone forever? Is there a way I can flash without being stuck at boot.info or zImage when trying to flash kernel, both on Odin messages? Or is my phone really bricked? Thansk alot, I'll pay close attention to this.
EDIT: I haven't found after a day of research anyone that did data wipes in an encrypted phone, so this can be a guide for any future similar case.
Click to expand...
Click to collapse
Tried installing Android 2.3 stock bootloader / rom ?
jiboncom said:
Tried installing Android 2.3 stock bootloader / rom ?
Click to expand...
Click to collapse
No I haven't. Is there any online link here? I couldn't find it.
Solved
After a day looking for it, I solved my problem
I tried several kernels, roms with almost all odin versions. The best one for gt-I9100 was odin 1.87.
This was the deal: After cleaning the encrypted internal storage, it got corrupted. So one of the first steps to get my phone reacting again to ODIN when installing new ROMs was installing the original GT-9100 .PIT file and re-partitioning (Even with every forum/site telling me I should never do it).
So, if you ever do the same mistake as me, try this:
Install a new kernel, then .PIT original file. Get a proper MODEM file, and finally try flashing your ROM.
I also got alot of problem with my USB cable, which is kinda damaged, so out of 10 plug-ins, only a few would work for ODIN. Try getting a brand new cable.
That's it.
gerijeb said:
After a day looking for it, I solved my problem
I tried several kernels, roms with almost all odin versions. The best one for gt-I9100 was odin 1.87.
This was the deal: After cleaning the encrypted internal storage, it got corrupted. So one of the first steps to get my phone reacting again to ODIN when installing new ROMs was installing the original GT-9100 .PIT file and re-partitioning (Even with every forum/site telling me I should never do it).
So, if you ever do the same mistake as me, try this:
Install a new kernel, then .PIT original file. Get a proper MODEM file, and finally try flashing your ROM.
I also got alot of problem with my USB cable, which is kinda damaged, so out of 10 plug-ins, only a few would work for ODIN. Try getting a brand new cable.
That's it.
Click to expand...
Click to collapse
Add [SOLVED] to the title.