...and now my phone works except the screen never turns on.
I remember exactly what I changed, I backed up /system/bin/samsungani and tried replacing it (stupid, I know, I didn't think I'd get a pseudo softbrick).
It's fully operational except I can't see anything.
Are there no options besides reflashing a rom?
If you did a nandroid backup then you can just restore back.
But incase you cant see the screen in recovery then your only option is to reflash through odin.
Sent from my GT-I9300 using xda premium
Related
I tried upgrading my girlfriend's Vibrant to one of the new 2.2 ROMs and she didn't like it, so I disabled voodoo, booted into recovery and attempted to restore the backup I made in nandroid. After 30 minutes of hanging on 'restoring data', I gave up and tried to reboot. Phone is now stuck in the vibrant logo and will not boot into recovery. Tried pulling the battery and it just reboots back to the Vibrant logo.
I know there is a way to fix this with something called Odin? (not sure if that's the name). My only problem is I don't want to delete any of her non-restorable stuff. Is there any way to fix this without deleting anything that can't be restored? Also, any idea why the nandroid backup didn't work? I'm afraid that even if I can get back into recovery, the restore will just freeze again.
I did notice when it was wiping to install the ROM originally, it also froze on deleting data, but a reboot fixed that. So maybe a reboot will fix that too but I'm not sure. Any help?
do you reboot when you have disabled voodoo and hear linda say 'convertion successful' ? sometime it will not work proper if you disable and flash something without reboot
Sent from my SGH-T959 using XDA App
Yeah I used the flashable disable zip thru rom manager.
velocity92c said:
Yeah I used the flashable disable zip thru rom manager.
Click to expand...
Click to collapse
*edit* it is because kernel i think
BTW post wrong section..
Sent from my SGH-T959 using XDA App
I made this same mistake the first time I flashed. What it is, its that nandroid does not backup the kernel, so you have to flash one with the same version of android. At this point you will have to use odin to do it then once you have you can do a nandroid restore.
Sent from my SGH-T959 using XDA App
o i'v just got what your problem is！ you should flash a 2.1kernel before nand restore. because it will not restore your kernel
Sent from my SGH-T959 using XDA App
oiiboy said:
I made this same mistake the first time I flashed. What it is, its that nandroid does not backup the kernel, so you have to flash one with the same version of android. At this point you will have to use odin to do it then once you have you can do a nandroid restore.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I think maybe he can get into recovery and flash a new 2.1 kernel. Will this work?
Sent from my SGH-T959 using XDA App
Post in the right forum and you will get the answer to how to fix it.
Moved to Q&A as not development
look at the bright side... at least ur Vibrant isnt stuck on the Captivate screen....
I'm sorry about posting in the wrong forum, honest mistake but it won't happen again. Can someone exolain to me what I need to do, in order, to fix this? I need to use odin, then flash a 2.1 kernel, then run nandroid restore? Which 2.1 kernel should I use?
So I installed Cyanogenmod 9 but now ive decided to go back to gingerbread. The only problem is whenever you i do that, everything flashes perfectly but when the ROM boots up, therrs always a PIN (screen lock)!!! i have noooo idea what this pin is.
I call myself and then press home after hanging up which means im actually in the phone. BUT i cant remove the pin still!!!!!
Ive tried plain flashing, clearing memory/cache etc, doing it through ODIN but they all result in the same thing!
can anyone provide any suggestions? thanks.
So is phone or sim locked with pin?
Sent from my sgs2 running cm9 using xda app
Have you tried entering any random numbers?
Sent from my GT-I9100 using Tapatalk
That is because the pin info is stored in the efs partition which is untouched during flashes and ignored by AOSP roms like CyanogenMod which use a different pin storage method.
So that is why it came back after you went back to stock. It will be the same pin you set it as last time you were stock.
I've tried all my old pins none of them work. Is there any way to reset this completely?
Sent from my GT-I9100 using XDA App
You could try figuring out what files on the efs have to be deleted and delete them.
MAKE A EFS BACKUP FIRST if you are going to try that though so you can always restore it if you lose your IMEI
I am not sure what files you would have to get rid of but with a good backup you should be safe to play around.
Decided I better ask for help before digging a deeper hole...
I had rooted my Vibrant around September 2010 and tried some ROM at the time, don't remember which one. I didn't keep it for very long...I accepted one or two stock OTA updates thereafter, ending up with 2.1-update1/KA6.
Fast forward to yesterday, when I decided to try to go to Gingerbread so as to be able to install an app I wanted. I chose CM7.2. I presumed I wasn't rooted anymore after the OTA's, so used CWM to run the update.zip that I still had on the SD card from 2010. I did a Titanium backup. I started following the abbreviated directions, then went to the full directions here:http://wiki.cyanogenmod.com/wiki/Samsung_Vibrant:_Full_Update_Guide
So I actually made two nandroid backups as a result of switching between the two sets of directions and getting distracted after I made the first one.
All went well, except after CM7.2 was booted and everything restored from Titanium, I had the following issues:
1. Messaging was broken
2. Most contacts were missing
3. GPS wouldn't lock
I poked around for fixes and tried some, but it was not looking promising. I decided I didn't really need that new app after all, and today tried to revert to stock. I supposed it would be a simple matter of a nandroid restore followed by a Titanium restore. Unfortunately the nandroid restore failed.
Research revealed this is a known issue with "different hboots".
I then compounded the issue by accidentally pressing the power button while in Recovery. The phone rebooted but stuck on the "Vibrant" splash screen, because of the corrupted restore attempt. No amount of 3-button resets got me back to Recovery. The phone is now connected to my laptop in Download mode.
I think what I now need to do is odin, per http://forum.xda-developers.com/showthread.php?p=13132341#post13132341
I will then be able to do a nandroid restore and Titanium restore and be back where I started? Any additional hints, warnings, etc?
Thanks in advance.
Be careful about what you backup with Titanium on stock and then restore on CM. Did you backup your Messaging app or any system data? If you restored system apps or data from a TI backup onto CM from stock, that could cause issues.
And about the contacts, where did you store them before? On Google, SIM, or in memory?
I may have clicked, in Titanium, "restore app and data" rather than just "data" for the messaging app. Thinking that may have been the case, I thought that reinstalling the ROM or Google apps zip files might fix it. It didn't. (this was before I soft-bricked)
Since I needed a working phone this afternoon, I went ahead and did the Odin thing. That went well. I am back to JFD and my contacts are back.
If I do a nandroid restore now, followed by a Titanium restore, it should get me back to where I was before starting the move to CM7.2, right? Except I would still have a JFD radio? (because nandroid does not touch that, as I recall)
In that case, finding a KA6 to install with odin would be best? And would there be any point to the nandroid restore if I did that?
GPS took a very long time to lock after going back to JFD, too. I think perhaps I need to try the antenna fix.
Maybe I will give CM7.2 another go...
m3rb said:
I may have clicked, in Titanium, "restore app and data" rather than just "data" for the messaging app. Thinking that may have been the case, I thought that reinstalling the ROM or Google apps zip files might fix it. It didn't. (this was before I soft-bricked)
Since I needed a working phone this afternoon, I went ahead and did the Odin thing. That went well. I am back to JFD and my contacts are back.
If I do a nandroid restore now, followed by a Titanium restore, it should get me back to where I was before starting the move to CM7.2, right? Except I would still have a JFD radio? (because nandroid does not touch that, as I recall)
In that case, finding a KA6 to install with odin would be best? And would there be any point to the nandroid restore if I did that?
GPS took a very long time to lock after going back to JFD, too. I think perhaps I need to try the antenna fix.
Maybe I will give CM7.2 another go...
Click to expand...
Click to collapse
If you do a nandroid restore you don't need to do a TI restore as nandroid will restore all your apps and data. (Even down to which wallpaper you're using and Wifi networks)
If the KA6 modem works best for you then go for it.
Where you rooted before you flashed the CWM update.zip? I didn't see that you were...
Sent from my SGH-T959 using xda app-developers app
whatiznt said:
Where you rooted before you flashed the CWM update.zip? I didn't see that you were...
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
You don't need to be rooted, you just need a way to install. For example when you install from stock, you don't need to root it, only flash the custom kernel that has CWM, and then flash, since root is a state of the ROM.
Sent from my SGH-T959 using xda premium
Huh. Always thought you needed root to flash CWM.
Sent from my SGH-T959 using xda app-developers app
whatiznt said:
Huh. Always thought you needed root to flash CWM.
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
Well, in our case we can use download mode + heimdall to flash a kernel that has the CWM recovery included.
Sent from my SGH-T959 using xda premium
Hi
Since a few weeks my phone turnes itself off accidentally, during any operation or just lying lazy on the desk. I had ARHD 6.5 since 6 months or so and I replaced it with 6.7 like 3 days ago, hoping this will solve the problem but it didn't. So I wanna try the stock rom and see whether it helps or not, and if it won't I'll send it to rma. My question is how to recover original soft from nandroid backup, cause I tried and got stuck with bootloop. Do I have to recover the old firmware as well? I found some thread on how to remove clockwork and root, put the phone back S-ON and so on but I would have to recover stock rom first, right? I know I can also flash the stock rom, but the only one I found is not matching perfectly my original one, so I would rather get it back from backup. This phone is just so freaking annoying...
Thanks in advance
You have to boot into custom recovery, be it clockworkmod or another one, then go into "backups and recovery", and from there, restore from backup, then you have to choose your nandroid backup, provided that you have performed it, and select restore (all).
That's it, good luck.
Sent from my MB525 using xda app-developers app
dagomez99 said:
You have to boot into custom recovery, be it clockworkmod or another one, then go into "backups and recovery", and from there, restore from backup, then you have to choose your nandroid backup, provided that you have performed it, and select restore (all).
That's it, good luck.
Sent from my MB525 using xda app-developers app
Click to expand...
Click to collapse
I've done it already but as I wrote before I ended up in bootloop. I think it might be caused by firmware which I flashed in order to install ARHD (Firmware from 3.33.401.6 & 3.33.401.106 RUU). But I don't have any info about the version of previous FW and don't really know if this is the issue.
Anyone? Please have mercy, I'm getting killed by this phone. Help
i guess it doesnt really matter now, other than id like to understand what went wrong so it doesnt happen again. last night i made a backup of the current rom i was running, and restored a backup to a different rom. after doing so i remembered i had notes on the 1st rom that i needed. so i flashed back to the rom i started the night with, and it failed. i tried a few times and this backup just wasnt going to restore. so i rebooted phone and i saw something flash about being in factory mode, and there was yellow writing on the screen with all info about my device. anyways the end result, i booted into recovery and restored a different backup, and now everything is fine
You probably entered download mode which is activated by holding down power home and down volume key
Sent from my SCH-I605 using Tapatalk
I figured out it was "factory mode" and from what I can tell and I could be of here but has something to do with twrp I think. when flashing to a tw ROM from twrp 2.6.3 I end up in factory mode. If I restore my stock ROM which used twrp 2.5 I'm good. Now if I'm on a tw ROM and try to restore an aosp ROM that was backed up with 2.6.3 it fails and I end up back in factory mode, which forces me to do a clean install of a ROM
Sent from my SCH-I605 using Tapatalk
Definitely wasn't download mode though. I'm familiar with that and how to get into it. This here I can access and use all apps and everything seems normal aside from black box and gold letters in middle of screen
Sent from my SCH-I605 using Tapatalk