Related
For the record, I searched several times, but did not find an answer that seemed to fit this question. Also, I hope this isn't a ridiculous noob question.
A little background. I have/had a D1 which I rooted and changed ROMs on many times. It was easy. I either used a new .zip file or ROM Manager. I now have a Fascinate that I tried to root with SuperOneClickRoot, but it didn't seem to work as none of the 'root-only' apps would work. I then tried using Odin, but still had the same problem. I successfully used Odin to return to stock, but of course that was annoying and painful. Frustration got the best of me, and I tried again with Odin and was successful. I ran Odin, got to recovery, installed and ran a SuperClean ROM using the .zip file for many days.
Here's where the trouble begins. I decided to try a different ROM, so I rebooted into recovery, backed up my current ROM (or so I thought), and tried to load another .zip ROM. The first one would not load correctly, so I tried another, and then one more. I wiped the data and the cache before each try. None of them worked, so I thought, OK forget this, I'll go back to my backup and stick with it. NO BACKUP (for this phone) was listed under Backup or Advanced Backup. So, now I'm really stuck, because the only ROM I can get to work at all is Kaoscinate (sp?), but it will NOT work with 'root only' apps, like Titanium Backup'. I read a good bit on xda and tried to change with Odin, but I still had no real luck. I was able to get a SuperDark ROM to work, but it is on Android 2.1 and the 'root only' apps still do not work on it. I'm afraid to try another ROM change because of the issues I've had before. I want to go back to the SuperClean ROM. My phone is very important as it's my business line, so monkeying around with this trial and error is taking too long and making me very uncomfortable.
I can easily get to recovery, wipe data &/or cache, and install a new .zip, but will it boot or work for me? I believe the answer is no, so what am I doing wrong?
Will I have to go through Odin to restore to stock and then REDO the Odin root and go to a ROM that way? That is time-consuming and my confidence is low in that method working to get the ROM I want.
Is there some kind of fix for the 'root only' programs to be able to see that I AM rooted? I tried updating Busybox using Titanium, but that didn't do the trick. Plus, this time, I can't even get Titanium to open, because it says I'm not rooted.
Thanks in advance.
sigmtndawg said:
For the record, I searched several times, but did not find an answer that seemed to fit this question. Also, I hope this isn't a ridiculous noob question.
A little background. I have/had a D1 which I rooted and changed ROMs on many times. It was easy. I either used a new .zip file or ROM Manager. I now have a Fascinate that I tried to root with SuperOneClickRoot, but it didn't seem to work as none of the 'root-only' apps would work. I then tried using Odin, but still had the same problem. I successfully used Odin to return to stock, but of course that was annoying and painful. Frustration got the best of me, and I tried again with Odin and was successful. I ran Odin, got to recovery, installed and ran a SuperClean ROM using the .zip file for many days.
Here's where the trouble begins. I decided to try a different ROM, so I rebooted into recovery, backed up my current ROM (or so I thought), and tried to load another .zip ROM. The first one would not load correctly, so I tried another, and then one more. I wiped the data and the cache before each try. None of them worked, so I thought, OK forget this, I'll go back to my backup and stick with it. NO BACKUP (for this phone) was listed under Backup or Advanced Backup. So, now I'm really stuck, because the only ROM I can get to work at all is Kaoscinate (sp?), but it will NOT work with 'root only' apps, like Titanium Backup'. I read a good bit on xda and tried to change with Odin, but I still had no real luck. I was able to get a SuperDark ROM to work, but it is on Android 2.1 and the 'root only' apps still do not work on it. I'm afraid to try another ROM change because of the issues I've had before. I want to go back to the SuperClean ROM. My phone is very important as it's my business line, so monkeying around with this trial and error is taking too long and making me very uncomfortable.
I can easily get to recovery, wipe data &/or cache, and install a new .zip, but will it boot or work for me? I believe the answer is no, so what am I doing wrong?
Will I have to go through Odin to restore to stock and then REDO the Odin root and go to a ROM that way? That is time-consuming and my confidence is low in that method working to get the ROM I want.
Is there some kind of fix for the 'root only' programs to be able to see that I AM rooted? I tried updating Busybox using Titanium, but that didn't do the trick. Plus, this time, I can't even get Titanium to open, because it says I'm not rooted.
Thanks in advance.
Click to expand...
Click to collapse
If it's that important, and you'd like to avoid any trial and error, simply odin your preference of ED01 roms here:
http://forum.xda-developers.com/showthread.php?t=1048380
To test root, simply open terminal emulator (free in market) and type "su" (no parentheses). It will notify you of a superuser request.
find an odin package for the baseband you want like EB01, EC01, ED01, etc (I use an all in one complete deodexed and debloated EB01 package myself) and the newest CWM 3. Odin them both, boot straight into cwm, wipe data/cache/dalvik, install the .zip rom of your choice from sd card and reboot phone. Should work fine, its the way I've done it and I've had few if any problems
edit: most roms like SuperClean, Evil, ComRom, etc are already rooted so there's no need to do anything special to gain root. the hardest part is flashing it correctly
You guys are awesome! Thanks!
If it's that important, and you'd like to avoid any trial and error, simply odin your preference of ED01 roms here:
http://forum.xda-developers.com/show....php?t=1048380
^^This one worked great for me. I seem to have the Samsung things I like (their visual voice mail, their video player, etc.) without the other bloatware.
I do have one more question. You said 'flashing the ROM correctly'. Before, with my D1, that simply meant using RM to 'Load Custom ROM' or rebooting into recovery mode and installing another .zip file. That has not seemed to work on this phone. What is the correct way to load another ROM on these phones.
Again, thanks for the help!!
sigmtndawg said:
You guys are awesome! Thanks!
If it's that important, and you'd like to avoid any trial and error, simply odin your preference of ED01 roms here:
http://forum.xda-developers.com/show....php?t=1048380
^^This one worked great for me. I seem to have the Samsung things I like (their visual voice mail, their video player, etc.) without the other bloatware.
I do have one more question. You said 'flashing the ROM correctly'. Before, with my D1, that simply meant using RM to 'Load Custom ROM' or rebooting into recovery mode and installing another .zip file. That has not seemed to work on this phone. What is the correct way to load another ROM on these phones.
Again, thanks for the help!!
Click to expand...
Click to collapse
Do not use ROM manager at all for anything on the fascinate.
The correct way to flash on fascinate: Download ROM .zip file and place on the root directory or your sd card. Boot into CWM and wipe data/cache/ dalvik cache (dalvik is under advanced) choose install zip from sd card. Install and reboot. First reboot will take 5-10 minutes, so be patient.
Hope this helps.
My apologies if this has been asked before, but I've spent hours searching and think I've done a better job of confusing myself, than answering my question.
I've rooted my wife's Samsung Fascinate, using Super One Click and removed all annoyances such as the Verizon bloat ware and got add blocker installed, etc. The point on doing so, was also to improve battery life, backup the ROM and some of the other associated advantages with rooting. One of my main goals was to also install a custom ROM on her phone, as the factory ROM is very flaky. It receives emails, then doesn't. It sends a text, then can't minutes later. It's been a great phone HW wise, but just junk as far as the OS.
Thus far, all attempts to backup the factory (modified) ROM has failed, which evidently is part of the limitation with the stock ROM. At this point, she's so frustrated (me too) with her phone, that it's time to get serious.
So, my confusion stems from varying reports regarding what the proper steps are to install a new ROM. On my Thunderbolt, I simply used CWM to install and backup/restore my ROMs as needed. This doesn't seem to be the case with the Fascinate and there's varying reports of whether this can even be done if Super One Click was used.
Has anyone had experience with flashing new ROMs after the phone was rooted and if so, by what method?
Her current ROM details are:
Firmware
2.2.2
Baseband
S:i500.04 V.ED05
Kernel
2.6.32.9
Build
SCH-I500.ED05
Thanks in advance.
stock roms,radios, and recoveries are flashed via odin. custom roms are flashed via the appropiate cwm for that specific rom.
example: lets say you want cm7
you would odin cwm4 recovery fixed for cm7(pda function only)
three finger boot into recovery
wipe data,cache,dalvik
install cm7 zip
profit
most stock roms and powewashed gingerbread rom are .tar files and need to be flashed in the pda funtion of odin.
then use odin again to flash the appropiate cwm, such as cwmall.tar, which can be found in the pwgb thread(op).
basically just remember zip files are flashed in recovery, .tar and md5 files are flashed in the pda function of odin and you will be set!
droidstyle said:
stock roms,radios, and recoveries are flashed via odin. custom roms are flashed via the appropiate cwm for that specific rom.
example: lets say you want cm7
you would odin cwm4 recovery fixed for cm7(pda function only)
three finger boot into recovery
wipe data,cache,dalvik
install cwm zip
profit
most stock roms and powewashed gingerbread rom are .tar files and need to be flashed in the pda funtion of odin.
then use odin again to flash the appropiate cwm, such as cwmall.tar, which can be found in the pwgb thread(op).
basically just remember zip files are flashed in recovery, .tar and md5 files are flashed in the pda function of odin and you will be set!
Click to expand...
Click to collapse
Okay, that makes a lot more sense now. Thanks for the quick reply.
correct me if i'm wrong but when flashing the cwm fixed for cm7, the 3 finger method does not work.
ibsk8 said:
correct me if i'm wrong but when flashing the cwm fixed for cm7, the 3 finger method does not work.
Click to expand...
Click to collapse
it does until the rom is flashed, then you have to long press the power button and select reboot recovery...at that point your no long in cwm4 fixed for cm7. once the bml to mtd conversion takes place it's converted to cwm 5.x.x.
droidstyle said:
it does until the rom is flashed, then you have to long press the power button and select reboot recovery...at that point your no long in cwm4 fixed for cm7. once the bml to mtd conversion takes place it's converted to cwm 5.x.x.
Click to expand...
Click to collapse
I never could get to the ROM flashing part. Every time I tried I got the same set of errors as when trying to backup the original ROM. I did manage to get the CWM 4 fix applied through ODIN and it said successful, but nothing really changed and my attempts to flash the new ROM still failed.
I searched around this forum and others and found another file to flash and things went very badly. The flash was moving super slow and I left the phone, so I wouldn't be tempted to do anything stupid and after an hour, it was at the same point. When I rebooted the phone, I got a sad face icon only. No Samsung logo or anything.
Luckily, I was able to re flash the stock rom, but after messing with it for 4 hours and getting nowhere, I decided the stock ROM was good enough for now. I have no idea why this phone is so pesky and read how some folks had to ref lash the stock ROM, before being able to flash a new ROM. I made one final attempt to do so and got the same error as the first time, so that was enough for that day. I don't recall exactly what the error said at this point, but I had blue text, followed by orange, which I think said something to the fact that is was unable to verify the package, followed by red text showing the failures.
Sorry there's no more detail than that for now. I may try this again in the future, but as mentioned this is the wife's phone, so I can't take nearly the liberties with it as I could my own.
If anyone has any ideas on what I may be able to try next, that would be great. If not, I may keep digging on this forum (a very helpful place indeed) and see what the options may be.
Thanks everyone for your help.
refer to section 3 of my guide and follow those steps. for some reason certain fascinates have trouble flashing mtd roms when starting from ed05. I have to start with dl09 eclair then flash cm7. look in page 2 of this section for my guide. all files needed can be found there aswell. good luck!
ok so i wouldnt say im a noob but im not as advanced as some of yous. last night i flashed a leaked ics onto my phone and loved it with one exception. i couldnt figure out how to root it. all my apps are backed up on titanium backup and i didnt want to have to get all of them manually. so i flashed back to stock using odin with a file i used back when that crappy update came out. i rooted it with super one click and and then went to put on a prerooted ics... when in recovery mode now i get this message
cant access to '/system/csc/att/system/'
i try putting on cwm and siyah and i keep getting authentication errors and the installation aborts. also recovery mode wont read my external sd card now. when the phone is booted up it works fine except i tried to do the factory ota update and it keeps failing. i tried reflashing back to stock again and did the update unrooted and it still failed.
i know you guys hate hate when people ask without researching so i did SOME forum browsing and found nothing. sorry i dont really have time to look too extensively. i just want to know how to fix it. i appreciate any help i can get
Joeyjr25 said:
ok so i wouldnt say im a noob but im not as advanced as some of yous. last night i flashed a leaked ics onto my phone and loved it with one exception. i couldnt figure out how to root it. all my apps are backed up on titanium backup and i didnt want to have to get all of them manually. so i flashed back to stock using odin with a file i used back when that crappy update came out. i rooted it with super one click and and then went to put on a prerooted ics... when in recovery mode now i get this message
cant access to '/system/csc/att/system/'
i try putting on cwm and siyah and i keep getting authentication errors and the installation aborts. also recovery mode wont read my external sd card now. when the phone is booted up it works fine except i tried to do the factory ota update and it keeps failing. i tried reflashing back to stock again and did the update unrooted and it still failed.
i know you guys hate hate when people ask without researching so i did SOME forum browsing and found nothing. sorry i dont really have time to look too extensively. i just want to know how to fix it. i appreciate any help i can get
Click to expand...
Click to collapse
Start with getting back to stock using this guide. Check for ICS bootloaders too, you probably flashed them and you have to get stock ones back (careful, flashing bootloaders can cause hardbricking). Once you're back to stock and rooted, you shouldn't need to ever use PC Odin again.
Then use this guide for rooting/flashing.
One other note: when you tried to install CWM, it sounds like you loaded an update.zip onto your phone then tried to install it using stock recovery. Stock recovery won't let you install unsigned update.zips, which is why that method for getting CWM on your phone will never work (hence the authentication error and installation abort). For our phone, CWM is only included in custom kernels, that's the only way to get it on there, and don't even think about updating or changing it via other means. Just flash a custom kernel, it'll include CWM, use it until you want to switch kernels.
Hit my thanks button, I was really nice this time. And post in Q/A next time as well.
EDIT: Skip the second guide if all you want is stock. You should be able to update OTA after following the first guide. Though even if stock is what you want, I highly recommend flashing a custom GB kernel because a) they're more stable and faster and b) you'll have CWM in case you need it.
You started off mentioning about "leak ics" which I have absolutely zero experience.
My suggestion:
1. Try to get it back to stock. Make sure it works correctly.
2. If hasn't rooted yet, do so.
3. Getting CMW into the device by flashing custom kernel.
4. From there, install any ICS ROM you want.
Hello all,
I have a question that has not been answered after many hours of searching. Hopefully I'm just dumb, and my buddy's stock firmware and data isn't hosed. I'm trying to get his stock firmware running again so I can back it up safely.
What I've done:
Tried to flash CWM's update.zip via stock recovery (signature verification failed on the three different zip's I could find in the forums and various links)
Used Heimdall to push "cmenard-T959-CWM" zImage (this worked, and I get a different screen at boot)
The phone boots to the point of the T-Mobile splash screen with the annoying shriek sound, but goes to a black screen after. If i touch any of the soft buttons, they light up and remain lit. It'll stay like that for at least 20 minutes.
Is it possible to re-flash the system partition and not the data partitions using ODIN? Is that even feasible? Like I mentioned above, I'd like to get the stock firmware running such that I can make a good backup of it with all the user data intact. I haven't been able to because the CWM+root wouldn't flash.
Any suggestions or insight would be greatly appreciated.
thanks in advance!
Well as long as you don't format the internal SD, any pictures and videos and things should remain intact.
Here is a similar thread. See if it resembles your issue.
http://forum.xda-developers.com/archive/index.php/t-794869.html
Toast6977 said:
Well as long as you don't format the internal SD, any pictures and videos and things should remain intact.
Here is a similar thread. See if it resembles your issue.
http://forum.xda-developers.com/archive/index.php/t-794869.html
Click to expand...
Click to collapse
Thanks for the suggestion, Toast. I don't believe the internal SD has been messed with, and I don't plan to mess with it either. The thread you linked is not quite related to my issue, as far as I can tell.
I am able to get into Download Mode, and the Stock Recovery mode as well. However every time I try to flash an 'update.zip' with the Stock Recovery, I get an error about Signature Verification Failure.
After stepping back from it for a day, I think I've gained some clarity. Since all I've done is flash a different Kernel with Heimdall, I'm going to try to flash a stock kernel then see what happens.
Is this phone on stock Froyo or have you got it back to JFD (eclair)?
If Froyo, that's the problem. Using Odin back to Eclair and run update.zip. It won't work from stock Froyo.
*-*- I made some assumptions in my previous post. The shrieking sound. Black screen. Lights stay lit. Sounded like a poltergeist.
Glad you can get in download mode and recovery.
The old 2E vs 3E problem. Nice catch Toast
Give this a whirl: recovery 3e modified to work like recovery 2e
Might have to ABD push it to your internal SD card though.
Toast6977 said:
Is this phone on stock Froyo or have you got it back to JFD (eclair)?
If Froyo, that's the problem. Using Odin back to Eclair and run update.zip. It won't work from stock Froyo.
*-*- I made some assumptions in my previous post. The shrieking sound. Black screen. Lights stay lit. Sounded like a poltergeist.
Glad you can get in download mode and recovery.
Click to expand...
Click to collapse
Woodrube said:
The old 2E vs 3E problem. Nice catch Toast
Give this a whirl: recovery 3e modified to work like recovery 2e
Might have to ABD push it to your internal SD card though.
Click to expand...
Click to collapse
hahaha poltergeist!
Wow, so I'm glad I asked. I wouldn't have known about this issue, as I do not have any history with this device.
I know that the ROM is currently 2.2, and the Android System Recovery is showing "3e".
If I understand correctly, once I'm ready to flash up to ICS, I'll need to ODIN back to 2.1 to get Android System Recovery "2e", which will let me flash 'update.zip' packages freely. Then I flash an 'update.zip' to get CWM, then flash CM7, then CM9 (and CM9 is my intended destination).
The things mentioned in the thread you linked do appear to apply to my situation.
However I still want to get the stock OS booted and working, then do a Nandroid backup of it. (it's the computer tech/security pro in me. Since I'm new to this device, I -tried- to read up on everything first, and didn't want to make a change without being sure it would work.)
Does anyone happen to know if flashing a stock kernel over the 'cmenard' kernel will harm anything, and hopefully get a successful boot? Again, I'm trying to get the stock ROM booting again in order to verify I have everything I need off of it, then do a nandroid backup. Flashing to CM9 will come afterwards.
Ok, here are some things for you.
Here is a kernel pack that you can use. Read the OP because there are Froyo AND Gingerbread kernels in there.
[KERNELS] Moped_Ryder SGS Kernel Pack v2 [20+ Froyo/GB Kernels]
I really suggest using something like BaliX 1.2 or BaliUV kernels to make your back up. They are smooth, fast and OC/UV-able. To flash just Wipe /cache, /dalvik -> flash kernel -> Wipe /cache, /dalvik (I also fix permissions too bc that is the way that I learned and I just do it that way all the time). Reboot and Bam!! you should be able to get to the point that you can make a backup.
Look in my signature, there are downloads and flashables that are direct download linked. There is also an ICS install guide that can help your journey. Once you have your backup, then use Odin from the Toolbox in my signature and flash back to stock JFD. From there you will be able to follow my guide.
If you need any files, just let me know and I will upload them when I get home (won't be until late though, i have plans right after work).
Using HB, can I choose any theme? I am not so acquainted with the Theme chooser and boot animation of my phone. I flashed a boot animation zip yesterday and it was stuck in "ANDROID" screen. So I have to flash again. I never used any boot animation and themes in my phone yet. I want to know about them.
Sent from my SGH-T959 using xda app-developers app
Wrong thread. Put that question in the Jelly Bean Banter thread. No need to hijack this thread until we get OP up and running.
Ugh, so I've been on vacation for a while, and since being back I've been super freaking busy =(
Finally spent some time with the phone tonight. Took some fiddling to get the right drivers working for the phone on my Win7x64 laptop.
In any case, I checked out that Kernel thread, and extracted the Bali kernel. Since I had flashed successfully(?) with Heimdall at first, and I'm becoming more familiar with it, I used it to flash the Bali_1.8.8-zImage. That appeared to work, as I get a new boot screen/animation with the Bali logo.
However, after the Bali logo disappears, the T-Mobile animation+sound plays, and then gives me a black screen. The screen is on (backlight is on) but all black. Also, if I touch a soft-button, they'll light up and the phone will remain in that state for as long as I can stand to wait. (one episode of Archer)
So, it's doing the same thing as before, but with a new boot logo/animation.
I wonder if something else in the ROM has been messed up? Should I forget trying to save it, and just use ODIN to flash a whole new rom/kernel package? I'll talk to the owner tomorrow and see if he's now willing to do that.
I also wonder if I was wrong to use Heimdall again, instead of using the CWM method. Please correct me if I'm wrong, but I think those two methods end up doing the exact same thing. Is one method more reliable than the other?
Bah, this sucks; I have more questions than answers at this point =( Any ideas, Woodrube, Toast?
maxpeet said:
Ugh, so I've been on vacation for a while, and since being back I've been super freaking busy =(
Finally spent some time with the phone tonight. Took some fiddling to get the right drivers working for the phone on my Win7x64 laptop.
In any case, I checked out that Kernel thread, and extracted the Bali kernel. Since I had flashed successfully(?) with Heimdall at first, and I'm becoming more familiar with it, I used it to flash the Bali_1.8.8-zImage. That appeared to work, as I get a new boot screen/animation with the Bali logo.
However, after the Bali logo disappears, the T-Mobile animation+sound plays, and then gives me a black screen. The screen is on (backlight is on) but all black. Also, if I touch a soft-button, they'll light up and the phone will remain in that state for as long as I can stand to wait. (one episode of Archer)
So, it's doing the same thing as before, but with a new boot logo/animation.
I wonder if something else in the ROM has been messed up? Should I forget trying to save it, and just use ODIN to flash a whole new rom/kernel package? I'll talk to the owner tomorrow and see if he's now willing to do that.
I also wonder if I was wrong to use Heimdall again, instead of using the CWM method. Please correct me if I'm wrong, but I think those two methods end up doing the exact same thing. Is one method more reliable than the other?
Bah, this sucks; I have more questions than answers at this point =( Any ideas, Woodrube, Toast?
Click to expand...
Click to collapse
Wrong they are not the same. cwm can do the work without a PC beside you can erase, back up , restore and flash, which make our life easier, heimdall or Odin ," I prefer odin "are the last option when you can't fix it with cwm
To fix your phone use Odin or heimdall and go back to stock don't worry all your files, photo, music, will be safe. Then
1 get root on you , if you don't how ask
2 get cWm
3 do a nandroid back up
4 have fun flashing all roms you want lol
Sent from my SGH-T989 using xda app-developers app
Yeah, I would just Odin back to stock JFD w/ repartition checked...
Then I'd flash something real stable for him. There are lots of stable ROMs to choose from. I used Bionix V for a long time before moving onto Jelly Bean.
Since the phone belongs to someone else, I'd stick with something lower than JB though. 911 can have/has issues.
Toast6977 said:
Yeah, I would just Odin back to stock JFD w/ repartition checked...
Then I'd flash something real stable for him. There are lots of stable ROMs to choose from. I used Bionix V for a long time before moving onto Jelly Bean.
Since the phone belongs to someone else, I'd stick with something lower than JB though. 911 can have/has issues.
Click to expand...
Click to collapse
do no check de re-partition button and use a .pit file follow this tutorial and you will be fine
http://forum.xda-developers.com/showthread.php?t=848737
hi all its been a while since ive been on the boards because ive been running rooted stock deodexed rom. i havent flashed in a year or so but just recently my settings have stopped.
i continually have been getting this message instantly after ancelling out the message. i cannot get past the select language option. theres no escape.
I couldn't even backup my current rom. so i did a battery pull and rebooted into recovery to flash different roms. I've tried dn3 which was the last rom i had saved to my sd card, and miui7. both yielded the same results of the same message about the settings has stopped. its obvious something has went bad over time. i have done nothing but use it as a phone. no flashing or anything. is there something i need to flash in order to troubleshoot this issue? i do not have the money to obtain a replacement through assurion. also my recovery wouldnt let me restore my 1 backup on my sd card. so is there anything i can do from scratch? any settings zips to flash? Odin? ive searched boards and nothing specific to my device (I605). please help
iflip said:
hi all its been a while since ive been on the boards because ive been running rooted stock deodexed rom. i havent flashed in a year or so but just recently my settings have stopped.
i continually have been getting this message instantly after ancelling out the message. i cannot get past the select language option. theres no escape.
I couldn't even backup my current rom. so i did a battery pull and rebooted into recovery to flash different roms. I've tried dn3 which was the last rom i had saved to my sd card, and miui7. both yielded the same results of the same message about the settings has stopped. its obvious something has went bad over time. i have done nothing but use it as a phone. no flashing or anything. is there something i need to flash in order to troubleshoot this issue? i do not have the money to obtain a replacement through assurion. also my recovery wouldnt let me restore my 1 backup on my sd card. so is there anything i can do from scratch? any settings zips to flash? Odin? ive searched boards and nothing specific to my device (I605). please help
Click to expand...
Click to collapse
I'm assuming you are still on the 4.1.2 bootloader, since you were able to flash miui7 and dn3.
If something has gotten corrupted, you could try Odin'ing the stock recovery back onto the device by following the directions on this thread: http://forum.xda-developers.com/showthread.php?p=53624921
After getting the stock recovery on the device, do a factory reset and wipe cache in the stock recovery. Then you can use ODIN to reinstall CWM/Philz or TWRP (whichever recovery you were using previously). Hopefully you have an old backup you could restore... or you can set up your ROM again from the start after rebooting back into the system.
If worse comes to worst and wiping in the Stock recovery doesn't fix things...sounds like you may have to Odin back to stock 4.1.2, and then reroot with CASUAL and start over again. Droidstyle put together a good guide on how to restore the phone back to stock 4.1.2... you can find his guide here: http://forum.xda-developers.com/showthread.php?p=34891181. I think the 4.1.2 firmware link is down, but you can grab it from Sammobile.com.
You probably know... but don't flash the official Stock 4.3 or 4.4.2 Firmware onto the phone because there's no current bootloader unlock methods for those..... 4.1.2 is the last Android version for our I605's that has a "do it yourself" bootloader unlock method.