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)
Related
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
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.
CURRENT STATUS -- PHONE BACK TO STOCK AND WORKING. WILL ROOT AGAIN AND PROBABLY WAIT A FOR THE FINE DEVS AT TO RELEASE THE ROMS I WANT INSTEAD OF MANUAL MODS HA!
PLEASE NOTE, AT THE TIME OF WRITING THIS THREAD, THE ROM MANAGER INSTALLATION OF CLOCKWORKMOD HAS SERIOUS ISSUES. YOU DO NOT HAVE A WORKING RECOVERY EVEN THOUGH IT FLASHES THE RECOVERY SOFTWARE. SEE XDA THREAD showthread.php?t=1695967 CHECK YOUR CLOCKWORKMOD BEFORE YOU DO ANY MODS
SUMMARY OF FIX --> USE FASTBOOT TO RELOAD WORKING RECOVERY --> ATTEMPT ROM INSTALL, FAILED --> RELOCK BOOTLOADER --> RUN APPROPRIATE RUU...PHONE IS NOW BACK TO STOCK CONDITION WORKING GREAT. XDA WILL SAVE YOU FROM YOURSELF
What happened?
-Rooted phone with regawMOD. Everything fine.
-Install rommanager -- decide to flash clockworkmod via rom manager, since I'm used to that recovery in the past.
-Use phone for 2 days.
-See thread about editing build.prop for links related to apple lawsuit.
-used root explorer file manager, backup build.prop, edit build.prop, HIT THE PERMISSIONS BUTTON ON THE FOLDER TO R/W and then back to R/O (DAMN DAMN DAMN)...reboot phone. Phone boots HTC white screen and then just black. Won't boot android.
What I tried to fix?
-Thinking sucks, but no biggie, I reboot and go to recovery clockworkmod 5.8.3.5 DOES NOT WORK...go search, find more forum posts about this version for our phone not working...DAMMIT CLOCKWORKMOD!
-Go to "Factory Reset", who cares at this point, just reset everything? Nope...white HTC screen, boots into clockworkmod v5.8.3.5 -- again, broken worthless recovery, no menus do anthing. Why did I forsake you TWRP?!?!
Now I'm gun shy on just hopping down and trying new things without consulting you guys first. What are my options? Don't want to make this worse.
Fine
TL;DR
EVO 4GLTE, rooted.
Screwed permissions and/or build.prop system folder
clockworkmod recovery version is worthless
Afraid to go forward.
If you can boot into the bootloader, maybe you can use fastboot to flash TWRP.
xxddaaohnoes said:
What happened?
-Rooted phone with regawMOD. Everything fine.
-Install rommanager -- decide to flash clockworkmod via rom manager, since I'm used to that recovery in the past.
-Use phone for 2 days.
-See thread about editing build.prop for links related to apple lawsuit.
-used root explorer file manager, backup build.prop, edit build.prop, HIT THE PERMISSIONS BUTTON ON THE FOLDER TO R/W and then back to R/O (DAMN DAMN DAMN)...reboot phone. Phone boots HTC white screen and then just black. Won't boot android.
What I tried to fix?
-Thinking sucks, but no biggie, I reboot and go to recovery clockworkmod 5.8.3.5 DOES NOT WORK...go search, find more forum posts about this version for our phone not working...DAMMIT CLOCKWORKMOD!
-Go to "Factory Reset", who cares at this point, just reset everything? Nope...white HTC screen, boots into clockworkmod v5.8.3.5 -- again, broken worthless recovery, no menus do anthing. Why did I forsake you TWRP?!?!
Now I'm gun shy on just hopping down and trying new things without consulting you guys first. What are my options? Don't want to make this worse.
Fine
TL;DR
EVO 4GLTE, rooted.
Screwed permissions and/or build.prop system folder
clockworkmod recovery version is worthless
Afraid to go forward.
Click to expand...
Click to collapse
yeah, download twrp and move it to your fastboot folder.
use the command "fastboot flash recovery (recovery name).img"
replace (recovery name) with whatever twrp is called, and remove the quotes.
husker91 said:
yeah, download twrp and move it to your fastboot folder.
use the command "fastboot flash recovery (recovery name).img"
replace (recovery name) with whatever twrp is called, and remove the quotes.
Click to expand...
Click to collapse
THANK YOU BOTH OF YOU!
For posterity, those that are reading this with a similar problem in the future, go here for the EVO LTE:
teamw.in
/project/twrp2/98
1> make sure your HTC drivers are up to date
2> download the TWRP img file
3>find fastboot.exe
4>put TWRP img file with fastboot.exe
5>run commands as on that TWRP page
I now have TWRP recovery! But not a running phone yet
The plan at this time was to wipe everything and just flash a stock ROM and count my blessings. Problems though with sd-ext and new ROM.
Wipe cache -- works.
Wipe Dalvik-cache -- /sd-ext not present, skipping
Factory Reset -- failed to mount /sd-ext (No such file or directory)
I've got the stock ROM img sitting in /sdcard via USB mount on my PC. Just copied it over.
Then I install it and everything acts like it works.
Restart phone, hangs at HTC screen for 20 minutes, never fully booting.
And now I'm here again.
When I go into the TWRP file manager I can see /sd-ext
Any thoughts?
The /sd-ext errors are normal, it's only used if you reformatted your sdcards to add it.
If the ROM you flashed is good and it still won't boot you'll want to run the RUU and bring it back to stock. All you have to do is connect it in fastboot mode and run:
fastboot oem lock
Then, once it's relocked, leave it in fastboot mode and run the RUU that can be found here.
You may need to run it twice if the phone reboots half way through, but that's fine. Just run it a second time and it should finish. When it's done your phone will be completely stock again.
fugard Dollin's
xHausx said:
The /sd-ext errors are normal, it's only used if you reformatted your sdcards to add it.
If the ROM you flashed is good and it still won't boot you'll want to run the RUU and bring it back to stock. All you have to do is connect it in fastboot mode and run:
fastboot oem lock
Then, once it's relocked, leave it in fastboot mode and run the RUU that can be found [
You may need to run it twice if the phone reboots half way through, but that's fine. Just run it a second time and it should finish. When it's done your phone will be completely stock again.
Click to expand...
Click to collapse
Will try that now and report back.
Thank you for the quick answer and vote of confidence. I know what is "supposed" to happen along this path, but this is the first time in 5 years and as many devices that I've made such a bone headed mistake rooting. So now I'm a little overly timid as to what is normal and what I caused in screwing up some permissions.
Thanks again!
WORKING! OP updated. Thanks everyone for your time and help!
xHausx said:
The /sd-ext errors are normal, it's only used if you reformatted your sdcards to add it.
If the ROM you flashed is good and it still won't boot you'll want to run the RUU and bring it back to stock. All you have to do is connect it in fastboot mode and run:
fastboot oem lock
Then, once it's relocked, leave it in fastboot mode and run the RUU that can be found here.
You may need to run it twice if the phone reboots half way through, but that's fine. Just run it a second time and it should finish. When it's done your phone will be completely stock again.
Click to expand...
Click to collapse
Haus are we lucky enough to have you join us here? Or u still rocking the 3D? Hope things are well buddy
Edit...OP glad to hear things worked out.
Sent from my EVO using Tapatalk 2
Not sure why people insist on having CW even when they know its broken. Even if it wasn't broken, just using TWRP one time, one will realize how much better it is compared to CW. Anyways dude, you're not fully bricked. You just need to find a way to get TWRP flashed.
Sent from my EVO using XDA
shook187 said:
Not sure why people insist on having CW even when they know its broken. Even if it wasn't broken, just using TWRP one time, one will realize how much better it is compared to CW. Anyways dude, you're not fully bricked. You just need to find a way to get TWRP flashed.
Sent from my EVO using XDA
Click to expand...
Click to collapse
{
"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"
}
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.
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.