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
Related
Edit: I'm not pleased with this guide yet. Below I have you going back to stock jfd (2.1) and then I have a 2.2 kernel (overstock) which I didn't use when I installed cm7... I'm probably going to change this and suggest using the alt method in the noob guide, or going to jfd and then installing Trigger... Suggestions?
Installing CyanogenMod 7 on the Vibrant is NOT difficult. The process is different, not hard. There are certain steps you need to follow. Please note, I am trying to help and am in no way responsible for your actions, your phone, etc.... I will try and assist you so please post comments/suggestions/questions below.
Is CM7 perfect? ABSOLUTELY NOT!!
Read up on it HERE and decide if you are ready to try it out.
I am not being as detailed as normal. That is because I assume you have read and KNOW the NOOB GUIDE first.
I will let POST ONE be from start to finish (stock phone > CM7). This is obviously the longest process, but it's also the cleanest install.
POST TWO will be for those who already have root/custom recovery/a custom rom and DO NOT want to go back to stock first.
Regardless which method you choose, you are going to need the files....
FILES
The Update.zip file to root your phone (this roots stock 2.1, not 2.2) > File: View attachment update.zip <
If you have eclair, root per the noob guide linked above or another method of your preference... doesn't matter.
**A kernel with CWR (here is a link to an OverStock you can use): LINK
** I didn't use this method, I believe it should work fine, feedback wanted **
** I BELIEVE the reasoning here for this are two things, could be wrong... one, you cant use stock recovery and two, this gives you the option to go from CWR directly to download mode, which is needed later. THAT SAID, I used the regular CWR that installs from Rom Manager... once I flashed the efsbackup (more on this soon) I just pulled my battery and went into download mode because (a) it was fast (b) I didn't have the option to enter download mode from recovery.
THESE THREE FILES ARE NEEDED
- vibrant-efsbackup.zip
- cm7-vibrant-initial-kernel.tar
- cm7-vibrant-initial-20110304.zip
OPTIONAL: You may want to also grab the latest NIGHTLY version of CM7. The link above is the INITIAL CM7... there is work being done in the form of updates/NIGHTLY versions.... you can find them HERE and read about them on THIS thread. These do NOT wipe your phone so really no reason to not backup/test these out as they are released in my opinion.
I would also download the following:
The latest CM7 kernel from theexel (my preference here, not needed)
The Google Apps (CM7 doesn't come with the Market, Gmail, etc.. a C&D order a few years back is to blame)
STOCK > CM7
First thing I did was move ALL of my personal FILES that were already on my phone (both the internal/external) to my pc so I had a backup of them.
I then went to Menu > SD CARD AND PHONE STORAGE and I unmounted/formatted BOTH the internal and external.
I then used ODIN to get back to stock JFD (if you are stock anything, that's fine, I wasnt so I added this step for those who want to go back to stock).
Once it has finished and rebooted, I mounted my phone to my pc. I then moved the following files (all were listed above, minus the .tar, more on that later... leave it on your PC) from my PC to my INTERNAL memory:
The update.zip file to root my phone
The OverStock kernel (option to enter download mode, not required though, see above)
The vibrant-efsbackup.zip
The cm7-vibrant-initial-20110304.zip
The CM7 most recent NIGHTLY .zip (updated CM7)
The latest CM7 kernel from theexel (my preference here, not needed)
The gapps (google apps) zip.
Hold in BOTH volume buttons and POWER (release when you see the Vibrant logo) to reboot into recovery (phone can be on or off). Select Reinstall Packages.
Your phone will reboot and you will have root.
Go to the market and download ROM MANAGER. Open it, select to flash CWR (top option) and once it's done (you got the Success popup), reboot into clockwork recovery (2nd option).
Go to install zip from sd card, choose zip from sdcard, select the overstock kernel zip if you are going to flash it. If so, once done, reboot the phone...then go BACK to CWR using the 3 button combo (should be a red recovery now)
Go to install zip from sd card, choose zip from sdcard, select the efsbackup.zip. Once it finishes you need to get into download mode. If you used the overstock kernel, there is an option.. maybe under advanced. If you kept the normal CWR via Rom Manager, you can pull your battery and go ahead and load ODIN/Download Mode.
Load ODIN on your PC (I prefer THIS version of ODIN, older versions tend to hang up more)
UNCHECK reboot phone
UNCHECK Re-Partition
Load the cm7-vibrant-initial-kernel.tar (PDA Spot)
Press Start
About 10 seconds later, it should be done.... you need to get back to recovery... no need to turn off the phone or anything, FROM DOWNLOAD MODE, SIMPLY HOLD IN BOTH VOLUME BUTTONS AND POWER UNTIL YOU SEE THE VIBRANT LOGO.
** note, in this pic, my phone is not connected yet.. you can load this up before you connect your phone **
{
"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"
}
Now, in CWR, go down to "mounts and storage" and format the following: System, data, and cache.
Still in CWR, go to install zip from sd card, choose zip from sdcard, select the cm7-vibrant-initial-20110304.zip. Once this has finished do a Factory Wipe and Reboot.
Enjoy watching your new CM7 Bootup!!
Click to expand...
Click to collapse
IMPORTANT: Allow 15 minutes of the phone being turned on for the install to settle.
At this point, I would reboot back to recovery (3 buttons, power menu option will NOT work) and i would flash the following:
The latest Nightly update (don't wipe again, not needed).
The custom kernel from theexel (OPTIONAL)
The gapps zip so you can have the Market, gmail, etc
Then reboot.. let the phone sit... drink a beer.. donate some money to the guys that make this possible IF you like... and then enjoy the latest CM7 on your phone!
On a bootup, you may not have signal until you power off and back on your screen, fyi. *thanks theexel*
CM7 BOOTUP / RUNNING ON THE VIBRANT
Reserved for future use
nice guide!
Sent from my SGH-T959 using XDA App
It's not perfect, hate I was having issues recording to my pc... the drivers for my recorder were royally effing up using ODIN so I do not have nearly the video quality I was hoping to add.
Please offer suggestions for imporoving the guide!
You said you installed overstock kernel to JFD? how was that compatible? it's a 2.2 kernel right?
Sent from my SGH-T959 using XDA App
^ no... I did not, I just used the CWR that came with rom manager.
I may need to edit the guide... good catch.
Since there seems to be great interest in Cyanogen I think this guide should be stickied. Even though this is a work in progress it's already much clearer than the Cyanogen thread's OP.
^ I appreciate it, but this is not good enough yet... and I question of this install method will be required ongoing.
I may make a big change and suggest everyone just ODIN to stock using the ALT METHOD in my noob guide since it comes pre-rooted, comes with Clockwork Recovery AND is a 2.2 rom.
I probably should have done this the first time... may start over from scratch. I need feedback from people using this guide to know how it's working.
Hey when coming from CM7 to stock, do you hit re-partition in odin?
Sent from my SGH-T959 using XDA App
If you are gonig back to stock, from CM7, the file system on CM7 is different so I remember reading that you should....
that said, when I went back to stock to redo the process for making the guide... I honestly do not recall if I checked it, and I am up and running fine...
I noticed that my brother had ICS for his droid razr maxx and so I went about updating my phone so that I could have ICS as well. During the first attempt it downloaded fine, rebooted and started the installation. During the installation though it stopped around 30-40%? ish and rebooted saying the update failed. I have had this problem before and so I thought it was because my phone didn't have some of the applications that It came with from Motorola. I recovered it to my last recovery which I saved with everything still installed but the phone still rooted. The installation didn't work so I figured that I would just factory reset and try it again, thinking the phone would update then.
Phone: Droid razr X912, stock ROM, no root, Superuser is installed but does not work, installed OTA root keeper to check if I had root but didn't work. Bootstrap doesn't work.
Where I am now:
1. Stock ROM
2. factory reset
3. Gingerbread 2.3.6
4. No root and unable to re root
5. Cannot update ICS
Where I am trying to get:
1. Either I would like to get back to one of my recoveries that I made using CMrecovery or
2. Get to ICS.
What I have read so far:
Something about locking the bootloader. Said to use some adb reboot recovery command in a command prompt? I am really new at this so I don't know what this means(should provide somewhat of a idea of how much I know) I can read articles if someone can point me in the right direction
I am unsure what to do in this situation. Thanks.
Edit: Tried Doomlords unrooting script and that didn't work, Says that the phone is in R/O mode most likely (that is my conclusion) from reading a few articles.
Ok...I'm no expert but I can tell you what I would would do and hopefully we can you all fixed up. So you're on stock Gingerbread right? Do you have the stock recovery too or a different one? Anyways try booting into recovery, wipe the cache, do a factory reset/data wipe, clear cache again. Then restart the phone to see if it boots up all good.
Now, do you have the official ICS .211 .zip update file? I'm assuming you do, make sure it's on the "external" SD card. Shut the phone down, and boot back into recovery. Select update.zip from SD card and run the update. Give it plenty of time to run. Sometimes it seems like it is hanging but it's just thinking. Might take in upwards of 10-15 minutes to run through completely so make sure you have a full battery before beginning.
Mine did hang and installation failed. This is actually common when doing a forced update in recovery. Don't worry, all you have to do is force shut it down and repeat the above steps and run the install again. It "should" install fine on the second try, mine did and many others on here too. After it's finished and you're all booted up you should be on the official .211 ICS version.
If you want to root, search for matt's utility for the .211 version (I believe it's the 1.7 version) and simply follow those instructions, works great and don't forget to donate. He's saved lots of us RAZR users. Also, if you want the .215 leaked update, get Voodoo OTA rootkeeper, run that, get the .215 .zip update file from you're external SD card in recovery.
When all is said and done. You should be on the most recent stock .215 ICS version, and rooted. Hope this helps
Edit.. .If this doesn't work, and I don't know if it will, I hope it does, you'll probably have to use RSD to flash a stock image. I think they are .fxz files, not sure. I've never used RSD on my RAZR, only my OG Droid1.
Thanks for the Reply, I do not have the .211 ICS .zip, Though if you or anyone else know where to find it? I do know how to do the force install that you recommended that I do.
http://eclipserom.com/vforum/showth...cial-4-0-4-(211-OTA)-Fastboot-Files-for-XT912
There you go
Thank you. Will try it and let you know if that worked!
Matt's utility (found in the Dev forum) is really all you need. I'm guessing that having bootstrap installed is one of the issues as well.
Oh, I will check that right now while I wait for the ics rom to download, thanks for more options, may try it first if it is all that I need.
You can get the utility at same link I posted earlier..^^^
I just wanted to let you know that I did get it working again with your help! I ended up having to use RDSLite to restore it but its back up and got it working again! Thanks so much guys!
Tried the ics t-mobile leak and worked awesomely for me! (goo.gl/aQuKS) its German but Google translates it brilliantly!
another opportunity is (like I did) installing miui which is officially supported and use Nova launcher if u like.
Nevertheless, T-Mobile leak works like a charm!
{
"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 my XT910 Miui V4 using xda premium
kadosEidetic said:
I just wanted to let you know that I did get it working again with your help! I ended up having to use RDSLite to restore it but its back up and got it working again! Thanks so much guys!
Click to expand...
Click to collapse
did you get it re-rooted again?
I was having an issue with the update also. Had to go through an arduous process but finally figured it out.
I have clockwork recovery installed.
my question is
is there *anything special* i need to do to go from this to the new ICS or JB Roms??
thanks in advance!
Yes. Make sure you flash Gingerbread bootloader. There is an easy to follow guide available. Search for Vibrant Custom GB Bootloader on Google and it should take you directly to the thread here.
It's a simple guide to follow, just follow it carefully. *a misstep can hard brick you*
After you have that you can find a suitable 4.0.4 ICS to flash. Just follow the directions in the OP and you should be fine.
Or, you could flash a JB ROM. In that case I would recommend (because I had to) flash cm9 nightly FIRST, then go to JB from there. Would probably make your life easier
As my buddy Woodrube says: read, read, read. When you've read enough, read more.
I still sit back and read about an hours worth of old solved threads and new ones alike on an everyday basis.
Note: if you for choose an ICS ROM, please read the threads titled EU bug, and Encryption Unsuccessful. It may not ever affect you, but you should become familiar with it.
You don't need to flash Gingerbread bootloaders.
theexel said:
You know, everyone always says to go to CM7 then CM10.
I ODIN'ed back to stock today, no idea why, I got bored. xD
Note: Skip steps 1, 3, 4 if you already have a custom recovery, which you do, you're running Bionix and don't want to ODIN back to stock for a complete clean install.
These are the steps I use to go to CM10 coming from stock:
1. ODIN to stock, wipe everything, you know.. clean install.
2. Download all the zips you need. (CM10, JB GAPPS, CM10 FFC support zip, update.zip that has clockworkmod recovery.) and put them on your phone.
3. Reboot into recovery, install 'update.zip' it'll reboot, do it again.
4. It should boot into CWM now, the old version.
5. Flash CM10, it should reboot or get stuck.
6. Boot into recovery (Should be new recovery from now on.), wipe data/factory reset.
7. Boot into recovery, flash twice before rebooting.
8. Reboot system and wait for it to boot up, if it doesn't boot up, flash again.
9. Once it boots, flash GAAPS.
10. Flash CM10 FFC support.
Enjoy?
Click to expand...
Click to collapse
No you don't need GBbl's anymore. Lets just say they are not "required" anymore, but are still "recommended".
OP, I have a ICS install guide in my signature if you need it. Has details about EU bug too.
Woodrube said:
No you don't need GBbl's anymore. Lets just say they are not "required" anymore, but are still "recommended".
OP, I have a ICS install guide in my signature if you need it. Has details about EU bug too.
Click to expand...
Click to collapse
so i need to install CM7 before installing these roms(ICS)? (the guide says skip to the CM7 part). is CM7 required??
if so, how to go about installing the CM7 in place of the Froyo bionix build??
and is there a custom CWR for ICS roms that I need to install?
sorry for the dumb questions. ive been knee deep in my sgs4g and havent kept up with vibrant...
You do not need to flash CM7, people just say it's safer. (Not sure on that one.)
Follow the steps I gave up and skip the ones that I said to, you should be just fine.
theexel said:
You do not need to flash CM7, people just say it's safer. (Not sure on that one.)
Follow the steps I gave up and skip the ones that I said to, you should be just fine.
Click to expand...
Click to collapse
Ive been looking for the JB GAAPS file to dl for vibrant and I cant find it any where
http://goo.im/gapps
{
"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"
}
theexel said:
http://goo.im/gapps
Click to expand...
Click to collapse
No wonder I couldnt find it, I was spelling it wrong ffs I feel like a a dip**** now lol
---------- Post added at 11:55 PM ---------- Previous post was at 11:40 PM ----------
Just trying to be thorough here. On step 7 it says "7. Boot into recovery, flash twice before rebooting." What exactly should I be flashing 2x here? Never mind I figured it out
The ROM, but you figured it out.
I suggest you just flash CM7 because it doesn't take that long and you get some practice before going onto another ROM.
FC3SRedSuns said:
I suggest you just flash CM7 because it doesn't take that long and you get some practice before going onto another ROM.
Click to expand...
Click to collapse
I had already flashed 2 other ROMs before going to CM10, 1 successful on not so successful. This time it went flawlessly. Im loving CM10 so far. I see why this is so addicting now haha
Now you guys see what I mean about steps before leaps?
If you have a bad flash on 2.2 or 2.3.x, they are fairly easy to recover from and start over. Sometimes a bad flash on ICS can cause irreparable damage, al'a EU bug. I've also seen motherboards borked, USB/PC unconnectivity and the worst of all a bootloader bad flash, hardbrick.
But yes, I as well as almost everyone here will agree, it is very addicting.
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.
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)