Related
I installed the rom 6 times. different ways to try and install. redownloaded the file but no matter how i try it, after the boot animation screen, the screen goes blank like it shut off.
im on CWM 5.0.2.3
What version of starburst did you flash?
Sent from my SPH-D710 using XDA App
sleshepic said:
What version of starburst did you flash?
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
1.9 then 1.9.5
If you continue to hit walls you can always try going back to stock and starting over. Some on the starburst forum have had luck with that. And you didn't wipe data or format system between 1.9 and 1.9.5? Only cache and dalvik?
Sent from my SPH-D710 using XDA App
kyhassen said:
1.9 then 1.9.5
Click to expand...
Click to collapse
Do you have a mirror for the 1.9?........deleted by accident.
yang704 said:
Do you have a mirror for the 1.9?........deleted by accident.
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=G7bC9qXqpg4&feature=youtu.be
have both 1.9 and 1.9.5
also i did wipe everything. after i did 1.9 booted up. went back to recovery and wiped Dcache and cache and still bugged.
an now with other roms i cant install kernals.. any idea?
kyhassen said:
I installed the rom 6 times. different ways to try and install. redownloaded the file but no matter how i try it, after the boot animation screen, the screen goes blank like it shut off.
im on CWM 5.0.2.3
Click to expand...
Click to collapse
Having the same issue
epic touch (loading starburst rom) shows the galaxy S boot like it should, then the screen seems to just go blakc, doesnt go into a boot cycle. I formatted the system , wipe data, wipe cache, wipe dalvik , in that order.
My procedure. Load odin, wipe the current zedomax kernal.tar with the root.
Root works great. Then flash the 6.1 zedo max ( for CM5 ). After that, i try to flash the staburst rom and it wont boot back up. i tried using the Lost kernal too.
I'm familiar with recovering it, so i'm able to get back to my backup and unroot the device no problem, just need help fixing the root. On my old EPIC, i had to do the one click root my self, then roms would load fine. please help!
---------- Post added at 10:47 PM ---------- Previous post was at 10:19 PM ----------
also on the video link from qbking77 on how to flash this rom
quite a few epic touch users are having the same problem =\
did u format the system before you wiped?
Same thing here. All I get.is boot animation then black screen. Bunk rom or something because ive tried everything. I've given up on this rom bit I really was looking forwatd to having tbis rom on my phone
If somebody finds a solution please post!
HELP...
Im having the same issue... i tried the starburst rom and once past the boot animation it goes black so i booted into recovery and tried to restore my nand and it isnt there like it was wiped during rom install... ok so after that i stayed in recorery downloaded the latest viper rom, flashed and the same thing happened.. i wiped\factory reset wiped dcache and cache every time i try a new rom... PLEASE HELP i just bought this phone from a freind and decided to root and now i cant even make my first call on it...
1. Boot into CWM recovery and make a Nandroid backup.
2. Format system under mounts and storage.
3. Wipe data/factory reset.
4. Wipe cache partition.
5. Wipe Dalvik cache under advanced.
6. Install StarburstROM. IF COMING FROM 1.8 YOU MUST FOLLOW THE ABOVE STEPS EACH TIME THEN INSTALL 1.9. THEN DO THE SAME AND INSTALL 1.9.5.
7. Wiping data may not be necessary but I would do it anyways then reboot, let it run for a few minutes, boot back into CWM and from the advanced restore menu restore just your data from the Nandriod backup you made.
---------- Post added at 01:00 PM ---------- Previous post was at 12:48 PM ----------
tobiasunruh said:
Im having the same issue... i tried the starburst rom and once past the boot animation it goes black so i booted into recovery and tried to restore my nand and it isnt there like it was wiped during rom install... ok so after that i stayed in recorery downloaded the latest viper rom, flashed and the same thing happened.. i wiped\factory reset wiped dcache and cache every time i try a new rom... PLEASE HELP i just bought this phone from a freind and decided to root and now i cant even make my first call on it...
Click to expand...
Click to collapse
Your Nandroid is still there it's just on your internal SD card. If you were using a kernel with an early version of CWM it backed up to the internal SD card. The latest version the dev's are incorporating into their ROMs now backs up to the external SD card. Just Odin back to whatever previous ROM/kernel you were on then boot up and copy the Clockwork folder to your external SD card. Then follow the directions I posted above for flashing StarburstROM.
IA-32e said:
1. Boot into CWM recovery and make a Nandroid backup.
2. Format system under mounts and storage.
3. Wipe data/factory reset.
4. Wipe cache partition.
5. Wipe Dalvik cache under advanced.
6. Install StarburstROM. IF COMING FROM 1.8 YOU MUST FOLLOW THE ABOVE STEPS EACH TIME THEN INSTALL 1.9. THEN DO THE SAME AND INSTALL 1.9.5.
7. Wiping data may not be necessary but I would do it anyways then reboot, let it run for a few minutes, boot back into CWM and from the advanced restore menu restore just your data from the Nandriod backup you made.
---------- Post added at 01:00 PM ---------- Previous post was at 12:48 PM ----------
Your Nandroid is still there it's just on your internal SD card. If you were using a kernel with an early version of CWM it backed up to the internal SD card. The latest version the dev's are incorporating into their ROMs now backs up to the external SD card. Just Odin back to whatever previous ROM/kernel you were on then boot up and copy the Clockwork folder to your external SD card. Then follow the directions I posted above for flashing StarburstROM.
Click to expand...
Click to collapse
Thanks for the help but I'm new to Samsung devices... Can you give instructions on how to restore with Odin?
Edit... I just check my external and it has a clock work folder on it.. The only thing in it is a file named ".salted_hash" and that's it..
Sent from my PG86100 using xda premium
tobiasunruh said:
Thanks for the help but I'm new to Samsung devices... Can you give instructions on how to restore with Odin?
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Here's an excellent tutorial. This is my first Samsung device as well and the directions are pretty clear cut. I used Windows 7 64 Bit.
http://forum.xda-developers.com/showthread.php?t=1274337
---------- Post added at 01:38 PM ---------- Previous post was at 01:20 PM ----------
tobiasunruh said:
Edit... I just check my external and it has a clock work folder on it.. The only thing in it is a file named ".salted_hash" and that's it..
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Bummer man. Not sure how that happened unless you formatted your SD card accidentally.
IA-32e said:
Here's an excellent tutorial. This is my first Samsung device as well and the directions are pretty clear cut. I used Windows 7 64 Bit.
http://forum.xda-developers.com/showthread.php?t=1274337
---------- Post added at 01:38 PM ---------- Previous post was at 01:20 PM ----------
Bummer man. Not sure how that happened unless you formatted your SD card accidentally.
Click to expand...
Click to collapse
Do you think you could point me in the right direction to start over from stock? Like a tutorial on how to start over with a new boot image or a way to get past the boot animation?
Sent from my PG86100 using xda premium
tobiasunruh said:
Do you think you could point me in the right direction to start over from stock? Like a tutorial on how to start over with a new boot image or a way to get past the boot animation?
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Everything you need is in the Android Development section.
http://forum.xda-developers.com/showthread.php?t=1282420
IA-32e said:
Everything you need is in the Android Development section.
http://forum.xda-developers.com/showthread.php?t=1282420
Click to expand...
Click to collapse
Thanks I'll give it a try.. Let you know what happens..
Edit...
That worked.. I'm back to stock with no root.. Thanks for the help greatly appreciated...
Sent from my PG86100 using xda premium
well i finally got my starburst rom working... but why does the media not. i cant play music, veiw pictures, or play videos.
Is that v1.9.5? If so what version did you upgrade from? People are having some problems when upgrading to 1.9.5.
Same issue. Tried multiple times, followed instructions to a T. Phone just goes black after flashing Starburst. Now I can only go to recovery or download mode. I couldn't install my nandroid backup (don't know why, based on filename it seemed like an old one from a different phone, not the one I did today).
Trying to go back to stock following
http://forum.xda-developers.com/show....php?t=1274337
but I'm on a MAC, and can't figure out how to heimdall a ROM. I can flash a kernel using heimdall, but don't know the commands and flashing order for the stockEG30.tar in terminal using heimdall. I also downloaded the frontend suites for heimdall, but can't figure out where to place stockeg30.tar files.
Any help? I have no windows machines.
in order to install starburst v1.9.5 you must have v1.9 installed first (recommended w/ flashing zedomax kernal or lost kernal in CWM after reboot), make sure phone is rooted properly and CWM is installed if not already (can be done via download mode w/ odin)
download v1.9 here:
http://dev-host.org/z1jsf3k9lh44/stable_epic_starburst_10.27.11_v1.9_.zip
to get this on your sdcard you will have to mount through usb on cwm via mounts and storage and connect to your pc
follow rom flash instructions as usual in cwm:
format system through mounts and storage
wipe data
wipe cache
wipe dalvik through advanced
install zip from sdcard
reboot
wait a few minutes booted
then set up your phone
next flash/install either zedomax kernal or LOSt kernal via CWM
forums and downloads found here:
http://forum.xda-developers.com/forumdisplay.php?f=1284
wipe cache and dalvik before for flashing through cwm
reboot
next download v1.9.5 here:
http://forum.xda-developers.com/showthread.php?t=1276320
make sure it is saved to the root of your sdcard from which you want to install
next all you have to do is flash v1.9.5 over v1.9
do not format system
do not wipe data
do not wipe cache
do not wipe dalvik
install from sdcard
reboot
video to flash v1.9.5 found here found here:
http://www.youtube.com/watch?v=G7bC9qXqpg4&feature=youtu.be
I was running Strongsteve's blue rom and wanted to update to his latest version, so I wiped my cache and delvik and used CWM to install. When I rebooted, the phone never got past the SGS2 boot screen. I took out the battery and rebooted a bunch of times with no luck. I was able to get back in to CWM by holding pwr and up, and I reflashed the rom with no luck. I had Blazer's rom on the internal drive already and flashed that, but it still hung at the SGS2 boot screen. Now, I can't get back in to CWM and I can't charge my phone. I can still get in to USB mode but i've never used it before.
I rooted using auto-root, and i'm going to try using ODIN but i'm not sure what i should flash on there if i can even get my computer to connect to my phone...another ROM, the stock ROM, zedomax root? any advice?
i think i'm gonna go with the stock rom (http://forum.xda-developers.com/showthread.php?t=1479677) but not sure if there's other steps or things i should be doing instead...please help!
If you hold the power button + power down, can you boot into download mode?
yes...
i'm going to try odin but i'm not sure what file to flash...any thoughts?
Find the stock tar file in the epic 4g touch development. Someone just posted one not too lon ago. When you flashed the update did you follow all instructions to a t? I have run into similar problems because i thought skipling a step wouldnt matter.
Sent from my SPH-D710 using XDA App
As long as you can get into download mode, you're good.
Use this: http://forum.xda-developers.com/showthread.php?t=1383678
yeah i followed the instructions but something must have gone wrong. i'm going to try odin when i get home...i'll let you guys know how it goes. thanks!
one more question...do i need to flash the kernel too?
Keep in mind, if you flash the EL29 listed earlier, it will disable the reset ability of the USB jig (will still get you to ODIN D/L mode, just won't reset ODIN flash stats)
I suggest you flash the pre-rooted EL29 ODIN One-Click in my signature, but it is up to you.
mistatwo said:
one more question...do i need to flash the kernel too?
Click to expand...
Click to collapse
No, not if u odin. The kernels in there
Sent from the future
fixed! used the el29 odin root method (http://forum.xda-developers.com/showthread.php?t=1433101)
THANK YOU GUYS FOR ALL YOUR HELP!
Just a quick question..
Can you avoid all the above steps if you do a nandroid restore? I thought if I just did a nandroid restore and reflash from scratch I should be goodl. I did a nandroid back up when I rooted with the stock ROM and figured if I ever ran into problems I could retore and start fresh? Am I thinking about this the right way or do I need to go through the steps above when/if I get stuck a the boot screen..thx
For all who like to flash. Get md5checker from the market.Use it love it. Never flash a bad ROM again. Saves alot of headaches and time. Not to mention clutter.
---------- Post added at 09:03 PM ---------- Previous post was at 09:03 PM ----------
pawmbi1 said:
Just a quick question..
Can you avoid all the above steps if you do a nandroid restore? I thought if I just did a nandroid restore and reflash from scratch I should be goodl. I did a nandroid back up when I rooted with the stock ROM and figured if I ever ran into problems I could retore and start fresh? Am I thinking about this the right way or do I need to go through the steps above when/if I get stuck a the boot screen..thx
Click to expand...
Click to collapse
You are correct. As long as you have custom recovery.
btw it might have been a bad download. grab the md5 checker from the market like the guy above me a couple posts said. also redownload the rom if it is.
Phone stuck at logo screen
Hi, pls help..
Yesterday i have try to root my phone and today i have decided to restore to stock firmware.
As i didnt backup my files, and i try to restore by following this website from cnet.co.uk
after restore, my phone stuck at logo screen...
I can't turn off my phone nor entering download mode and boot screen.
:crying:
I am running v6.0.1.4 and it won't do anything.
It wont backup, restore, or install, it just freezes.
If I try to run a factory reset or a dalvic cache wipe it freezes too.
Nothing is working and I can't even start my phone because I tried to restore it and again, it froze.
Can anyone help me out here at all? I have no clue what to do, and I really would appreciate the help.
spuzwuzzel said:
I am running v6.0.1.4 and it won't do anything.
It wont backup, restore, or install, it just freezes.
If I try to run a factory reset or a dalvic cache wipe it freezes too.
Nothing is working and I can't even start my phone because I tried to restore it and again, it froze.
Can anyone help me out here at all? I have no clue what to do, and I really would appreciate the help.
Click to expand...
Click to collapse
Odin back to stock, or flash twrp and try that. Also this should not be in this section bud. Prepare to be flamed by the community
Sent from my SGH-T989 using xda app-developers app
I had the same thing happen to me when I updated to the latest one, it would freeze at either restoring, or wiping cache. Luckily I was able to just reboot, and everything was fine on the phone, I then downgraded to 5.XXX
I've been having the same issue on stock recovery, where it sometimes it freezes at wiping, then flash the one from rom manager and its all good. by the way mods please move the thread to Q/A
Wrong section bro. Please see the noob video.
Sent from my SGH-T989 using xda premium
You don't have to Odin stock or any of that stuff, just fastboot flash the 6.0.0.5 version (or that last one that worked for you) and you should be fine.
spuzwuzzel said:
I am running v6.0.1.4 and it won't do anything.
It wont backup, restore, or install, it just freezes.
If I try to run a factory reset or a dalvic cache wipe it freezes too.
Nothing is working and I can't even start my phone because I tried to restore it and again, it froze.
Can anyone help me out here at all? I have no clue what to do, and I really would appreciate the help.
Click to expand...
Click to collapse
Ok, don't panic. I've been having this twice a day every day for the past little while. I first started having this problem when I flashed MIUI JB, but very soon after every JB ROM out there started hanging on me, or killing my recovery in this fashion. It's fixable, though for the life of me I can't tell you what causes it.
Don't ODIN back to stock. Not yet anyway.
ODIN your very first recovery, just as if you are about to root your phone for the first time. ODIN CWM 5.0.2.7, not 6.0.1.4. Yes, it's ancient, I know. Catch your phone as it's rebooting after the flash, and get it to enter recovery. Don't let it boot into whichever ROM you have installed. Then go to MOUNT > MOUNT USB and attach your phone to the computer. Copy Darkside Superwipe over. Unmount from the computer and unmount from the phone. Then get CWM to run the script. You must superwipe your phone, so if you have something important, hope you have a backup. This time around it won't hang on you.
Your phone is recovered, you can now flash anything you want and it will work. You can restore your nondroid backup as well and this will also work. If your nandroid back is in the new CWM format, you will want to flash CWM v6 first. Feel free to flash whichever recovery works for you, but CWM 5.0.2.7 is your fallback recovery in case you need to recover your phone again. It is the only one that does not seem to get corrupted in this way.
You can ODIN back to stock now if you want to make absolutely sure everything is wiped clean, but in my experience this does not contribute much to the overall cleanliness of things: it's not called Superwipe for nothing. It doesn't hurt, though: as long as you do it AFTER you have superwiped, or not even ODIN will recover your phone. It really scared me once when I skipped the superwipe step and was left with a 100% stock phone which wouldn't boot.
---------- Post added at 10:28 PM ---------- Previous post was at 10:12 PM ----------
Careful with ODIN: Make sure you have NO PIT file selected, or you will kill your phone! Been there, done that, and I don't recommend it. Do it by the book!
kangelov said:
Ok, don't panic. I've been having this twice a day every day for the past little while. I first started having this problem when I flashed MIUI JB, but very soon after every JB ROM out there started hanging on me, or killing my recovery in this fashion. It's fixable, though for the life of me I can't tell you what causes it.
Don't ODIN back to stock. Not yet anyway.
ODIN your very first recovery, just as if you are about to root your phone for the first time. ODIN CWM 5.0.2.7, not 6.0.1.4. Yes, it's ancient, I know. Catch your phone as it's rebooting after the flash, and get it to enter recovery. Don't let it boot into whichever ROM you have installed. Then go to MOUNT > MOUNT USB and attach your phone to the computer. Copy Darkside Superwipe over. Unmount from the computer and unmount from the phone. Then get CWM to run the script. You must superwipe your phone, so if you have something important, hope you have a backup. This time around it won't hang on you.
Your phone is recovered, you can now flash anything you want and it will work. You can restore your nondroid backup as well and this will also work. If your nandroid back is in the new CWM format, you will want to flash CWM v6 first. Feel free to flash whichever recovery works for you, but CWM 5.0.2.7 is your fallback recovery in case you need to recover your phone again. It is the only one that does not seem to get corrupted in this way.
You can ODIN back to stock now if you want to make absolutely sure everything is wiped clean, but in my experience this does not contribute much to the overall cleanliness of things: it's not called Superwipe for nothing. It doesn't hurt, though: as long as you do it AFTER you have superwiped, or not even ODIN will recover your phone. It really scared me once when I skipped the superwipe step and was left with a 100% stock phone which wouldn't boot.
---------- Post added at 10:28 PM ---------- Previous post was at 10:12 PM ----------
Careful with ODIN: Make sure you have NO PIT file selected, or you will kill your phone! Been there, done that, and I don't recommend it. Do it by the book!
Click to expand...
Click to collapse
what do you mean my very first recovery? Also, I'm not familiar with Odin, I just install it on my pc right?
Miui JB is what I did too. Love me some Miui, but too many bugs. I can't even find the ICS Miui anymore...
spuzwuzzel said:
what do you mean my very first recovery? Also, I'm not familiar with Odin, I just install it on my pc right?
Miui JB is what I did too. Love me some Miui, but too many bugs. I can't even find the ICS Miui anymore...
Click to expand...
Click to collapse
Look, I'm sorry for your troubles but there is a good reason why we have four different sections. This thread being in DEVELOPMENT is only causing clutter. You will get much better help if its moved to its proper place, Q&A or general. Please PM a Mod to move this.
Sent from my SGH-T989 using xda premium
spuzwuzzel said:
what do you mean my very first recovery? Also, I'm not familiar with Odin, I just install it on my pc right?
Miui JB is what I did too. Love me some Miui, but too many bugs. I can't even find the ICS Miui anymore...
Click to expand...
Click to collapse
I am referring to the process you followed to install CWM on a stock phone. It didn't come with CWM already loaded, so you must have loaded it somehow. If not with ODIN, then what did you use?
kangelov said:
I am referring to the process you followed to install CWM on a stock phone. It didn't come with CWM already loaded, so you must have loaded it somehow. If not with ODIN, then what did you use?
Click to expand...
Click to collapse
I dont really know where to find 5.0.2.7. the website doesnt seem to have it. I used revolutionary
Thank you for your contribution to the development of the gs2.
Sent from my SGH-T989 using xda premium
Download the clock work mod app from playstore. Then your first choice after opening the apk, your first possible choice is flash cwm, do that. Pm me after that if you need help. he should be good now thanks
Sent from my SGH-T989 using xda app-developers app
Rushing said:
Download the clock work mod app from playstore. Then your first choice after opening the apk, your first possible choice is flash cwm, do that. Pm me after that if you need help. he should be good now thanks
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
There is no clockworkmod app, unless you mean rom manager. At least, I can't find any. Also, I can't even get my rom to load at all
spuzwuzzel said:
There is no clockworkmod app, unless you mean rom manager. At least, I can't find any. Also, I can't even get my rom to load at all
Click to expand...
Click to collapse
Now that you are in the right place, I will help you. It looks like you flashed a corrupted recovery. What you need to is Odin flash CWM. Go here
http://forum.xda-developers.com/showthread.php?p=27290471
Download Odin and recovery.tar, and Odin flash it. Will boot up just fine after. Don't fear Odin. Its safe as long as you are careful and READ!!
Sent from my SGH-T989 using xda premium
LoopDoGG79 said:
Now that you are in the right place, I will help you. It looks like you flashed a corrupted recovery. What you need to is Odin flash CWM. Go here
http://forum.xda-developers.com/showthread.php?p=27290471
Download Odin and recovery.tar, and Odin flash it. Will boot up just fine after. Don't fear Odin. Its safe as long as you are careful and READ!!
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Ya Odin flash the recovery tar is probably the easiest way to go
Sent from my Galaxy Nexus using xda app-developers app
Odin is a tool used internally by Samsung. As such, you can't expect Samsung to write you a manual. Be very careful, you can cause a lot of damage with it. It is powerful, though: it can bring your phone back from the brink of death. Or it can take a healthy phone and send it over the edge. What you are doing now is something every rooter does on day 1, and only after days and days of research. I am uncomfortable with what you are going to do now given that you have never done this before, but you have no choice: it's this or a useless phone.
Here's the rundown:
A PIT file is something like the Master Boot Record of your harddisk. Problem is, the first partition is something like your computer's BIOS: it tells your phone how to bootstrap. It can bootstrap into the normal mode, which runs Android, or it can initiate Download mode. Download mode is what ODIN needs to replace parts or all of your phone's software. If something goes wrong with that bootloader, your phone is something called a hard brick: it won't power on, it won't even run Download mode so that you can recover it back to stock. It is dead. If that ever happens, you need something called a JTAG flash: you send your phone out somewhere, and someone takes it apart, hopefully carefully, plugs a programmer into an engineering port on your phone's logic board, and reprograms the bootloader back again). Now with PIT file having the major potential to trash things completely, you really have to pay attention you don't load the wrong one. Problem is, the ODIN you just downloaded DOES come with a PIT file, and that PIT file is WRONG for your device. Follow the instructions! Follow the instructions really really carefully. Don't check off extra things! Don't uncheck things that should be checked! Don't add PIT files! Make sure you load the right file to the right place in ODIN. Your phone depends on it.
ODIN will program your phone from scratch, but you wouldn't want to use it too often. It's a dangerous tool, as you can imagine, and it is meant to replace your phone's software, not maintain it! That's why we have Recovery. Recovery is what you use to do basic maintenance to Android, such as factory reset and clean cache and stuff. With those custom recoveries out there, you gain the added ability to flash custom ROMs and a few other things as well, which is what this forum is all about. So, step one in anyone seeking to root their phone is, flash a custom recovery using ODIN, since you need Download mode for that. In an ideal world, you will never need to use ODIN again after you flash your custom recovery. Well, in the real world, you should needed it only very infrequently.
Your phone first got its custom recovery from a tool designed to automate things for you, and sent you flashing without ever giving you an idea how your phone works. Now you don't know how to recover your phone from a flash gone wrong: in the long run that tool did not do any favours to you. The steps I gave you will bring your phone back to life, it brought mine several times already. Something about those new JB ROMs corrupts every recovery I have tried. I don't know why, I don't know how, but it does it. To make matters worse, ODIN without a proper PIT file cannot repartition your phone and fix whatever mess caused the problem to begin with, so restoring stock directly won't do the trick, you need to flash custom recovery, to fix recovery, and then Superwipe to recreate and realign your system, data and cache partitions: that's a good chunk of your phone. So, after you do this, you should be back in business. From beginning to end, if you know what you are doing, the entire process should not take more than 30 minutes, but don't rush. Take your time: take hours, take days. Take all the time you need.
Read before you do anything, and ask if you don't understand.
I have this issue every now and then when I use the stock recovery (the one i use to root) with ODIN, where it get stuck on everytime i try to wipe or flash, What I used to do is factory stock with Odin, then realize the even though it froze on wiping factory data, the rom wiped!! so what i do know is install rom manager and flash their recovery and problem solve,
this thread is very useful thanks guys.
by the way i dont flash JB roms yet until I they completely fix the call issues so. do you think its not only JB roms?
gypsy214 said:
I have this issue every now and then when I use the stock recovery (the one i use to root) with ODIN, where it get stuck on everytime i try to wipe or flash, What I used to do is factory stock with Odin, then realize the even though it froze on wiping factory data, the rom wiped!! so what i do know is install rom manager and flash their recovery and problem solve,
this thread is very useful thanks guys.
by the way i dont flash JB roms yet until I they completely fix the call issues so. do you think its not only JB roms?
Click to expand...
Click to collapse
I have had the problem you describe as well. Some ROMs like certain recoveries better than others and if you end up with the wrong combo, they don't boot. Flashing the right recovery after that fixes it instantly, without even a need to reflash the ROM. No, this is a different problem.
We are talking about a problem where flashing a ROM corrupts your recovery so it will stop working on you completely: it just hangs, it won't restore, it won't flash anything. Also, one or more of the ROM partitions on your phone get corrupted somehow so that even ODIN back to stock doesn't get your phone working again (you end up with a fully stock phone that doesn't boot). Maybe the two are related, but I will let those who know more speak. I am just a regular guy who fiddles with his phone a lot more than he should.
As for the problem being on JB only: I've only had it when flashing JB ROMs. I first noticed it with MIUI, but then AOKP started acting up, and when I finally dared to flash a CM10 unofficial nightly for the first time, it happened too... And then I noticed it doesn't happen always, only sometimes, and other times it just leaves me with a JB ROM that doesn't boot, and in some rare occasions: it works without a hitch. Go figure.
So I was looking at vines when my rom (newest liquidsmooth) froze and hard booted. It got stuck at kernel splash screen (newest att kt747). Rebooted into recovery (Twrp 2.6.0.0) and it's asking for a password. I have never set a password and I can't see/install anything. Just empty folders.
Naturesretard said:
So I was looking at vines when my rom (newest liquidsmooth) froze and hard booted. It got stuck at kernel splash screen (newest att kt747). Rebooted into recovery (Twrp 2.6.0.0) and it's asking for a password. I have never set a password and I can't see/install anything. Just empty folders.
Click to expand...
Click to collapse
I cannot wipe any partitions or perform any actions. My phone also refuses to boot.
No download mode?
Sent from my SGH-T999 using Tapatalk
Try this If TWRP is asking for a password and not booting do this: Re odin recovery twrp 2.4.4.0, wipe ALL data, odin twrp 2.6.1.0 back on to the device, reboot recovery, re-wipe data, flash desired COMPATIBLE rom.
---------- Post added at 05:39 AM ---------- Previous post was at 05:24 AM ----------
ssingh0247 said:
Try this If TWRP is asking for a password and not booting do this: Re odin recovery twrp 2.4.4.0, wipe ALL data, odin twrp 2.6.1.0 back on to the device, reboot recovery, re-wipe data, flash desired COMPATIBLE rom.
Click to expand...
Click to collapse
22
ssingh0247 said:
Try this If TWRP is asking for a password and not booting do this: Re odin recovery twrp 2.4.4.0, wipe ALL data, odin twrp 2.6.1.0 back on to the device, reboot recovery, re-wipe data, flash desired COMPATIBLE rom.
---------- Post added at 05:39 AM ---------- Previous post was at 05:24 AM ----------
22
Click to expand...
Click to collapse
I am in the exact same situation, from the random reboot, non-booting phone, and password in TWRP on my d2vzw. I'll try the above and let you know what I come up with.
On a different note, if I take my SD card out and reinstall it, TWRP 2.6.1.0 reads it. I will try putting a ROM and GAPPS package on it, reflashing from the SD and using GOOManager to fix my recovery. This might be a viable option B.
Hopefully one of these will do the trick.
scubamike said:
I am in the exact same situation, from the random reboot, non-booting phone, and password in TWRP on my d2vzw. I'll try the above and let you know what I come up with.
On a different note, if I take my SD card out and reinstall it, TWRP 2.6.1.0 reads it. I will try putting a ROM and GAPPS package on it, reflashing from the SD and using GOOManager to fix my recovery. This might be a viable option B.
Hopefully one of these will do the trick.
Click to expand...
Click to collapse
To all besieged by the TWRP 2.6.x.x problems, it has a bug in reading or even mounting internal SD Partition. That may cause this or other issues for you. Strongly suggest reverting to 2.5.0.0
scubamike said:
I am in the exact same situation, from the random reboot, non-booting phone, and password in TWRP on my d2vzw. I'll try the above and let you know what I come up with.
On a different note, if I take my SD card out and reinstall it, TWRP 2.6.1.0 reads it. I will try putting a ROM and GAPPS package on it, reflashing from the SD and using GOOManager to fix my recovery. This might be a viable option B.
Hopefully one of these will do the trick.
Click to expand...
Click to collapse
try that and let me know how it goes. and a word of advice don't flash ROM's to often because you can brick your phone and don't flash random kernals like i did so now my phone is hard bricked meaning it wont do anything but i bought a jig so it should work again
No go so far...
I've tried reflashing the PacMan Rom, which started this whole problem, from the ext-SD. It will not get past the Samsung boot screen. I tried reflashing an older, AOKP ROM with the same result.
I Odined back to TWRP 2.4.4.0, but I could not wipe any data because I still can't mount anything other than the ext-SD. I went all the way to 2.6.3.0 without success. So far, I've settled on TWRP 2.5.0.0.
I've also tried restoring an old nandroid that I had on the SD card, but it failed at "Wiping Data". At this point, I'm planning on Odin back to stock and see where that leaves me. I'd really like to access some of the data on the internal storage, but I will settle for a phone that makes calls for now. My factory image is almost downloaded. I may get to it tonight.
Again, I'll keep you posted.
---------- Post added at 02:49 AM ---------- Previous post was at 02:43 AM ----------
I also tried flashing the newest version of CWM recovery, but it couldn't mount the internal storage either.
Has my internal data actually been physically changed to an unreadable format, or is the way it is being read from recovery(s).
Where did the encryption come from? I've flashed literally over 100 roms between my GNex and my S3 with zero issues. This is baffling.
Lastly, if I Odin back to 4.1.2, will my data be decrypted by the ROM, or could I do more harm than good?
---------- Post added at 03:21 AM ---------- Previous post was at 02:49 AM ----------
Odined back to VRBMB1. Rebooted. Wouldn't boot. I booted into stock recovery and did a factory reset. I was finally able to boot into stock Samsung software.
I don't know how many of you are praying people, but this was an answer to my prayers!
Thread cleaned
Either help the OP or do not post
Disrespect of other members will not be tolerated
Also please refrain from disrespecting developers and ROMs
Thank you for your cooperation
Friendly Neighborhood Moderator
Sorry. Been away. Managed to fix my own problem. Let me explain:
Crashed while watching video in ROM. Rebooted into recovery to clean cache and dalvik just to see if it would fix. Asked for password.
Odined 2.5 and same problem. The only way to fix was flash my t999l back to stock. Weird as hell... but I'm running better on stockorama.
Sent from my SGH-T999 using xda app-developers app
I'm totally stuck, help out a newbie?
Verizon Galaxy Note II
Running CM10.1
Here is my story:
I installed perceus kernal, Jelly Beans 19, seemed straight forward enough, so decided to install CM10. I was more than I really wanted to do, so tried to reverse and re-install stock firmware.
I followed the instructions to the letter. Did a full wipe. Flashed the PIT file and the firmware in ODIN as directed. Now I'm in a boot loop hell, can get out of it. Don't have CMW loaded. I thought TWRP would work, but isn't loading. Tried to re-flash the file again, and a few different versions, but am not getting failures. Tried to boot to recovery and clear the cache, but it won't start with UP/HOME/POWER (is there another method?). Tried to flash CWM6 in Odin, but get a failure.
Trying everything I can find, but I'm totally stuck. Any tips would be much appreciated.
I got it!!!!
Ewizzle27 said:
I'm totally stuck, help out a newbie?
Verizon Galaxy Note II
Running CM10.1
Here is my story:
I installed perceus kernal, Jelly Beans 19, seemed straight forward enough, so decided to install CM10. I was more than I really wanted to do, so tried to reverse and re-install stock firmware.
I followed the instructions to the letter. Did a full wipe. Flashed the PIT file and the firmware in ODIN as directed. Now I'm in a boot loop hell, can get out of it. Don't have CMW loaded. I thought TWRP would work, but isn't loading. Tried to re-flash the file again, and a few different versions, but am not getting failures. Tried to boot to recovery and clear the cache, but it won't start with UP/HOME/POWER (is there another method?). Tried to flash CWM6 in Odin, but get a failure.
Trying everything I can find, but I'm totally stuck. Any tips would be much appreciated.
Click to expand...
Click to collapse
So NEVERMIND! I re-flashed the fireware (without the SD card installed), and got it to boot to recovery. Cleared the cache, did a factory reset, rebooted a couple more times and the loop stopped. All good! Back to square one,
http://forum.xda-developers.com/showthread.php?t=1896696 read the Original Post. Follow the number 1. Stock rom installation.
And remember. Dont tick repartition when flashing in odin. Do you have your stock firmware?
Remember also that STOCK KERNEL is the most stable kernel. Hehe.
Sent from my GT-N7100 using XDA Premium 4 mobile app
---------- Post added at 05:50 PM ---------- Previous post was at 05:49 PM ----------
Good. Self solution. Good job man.
Sent from my GT-N7100 using XDA Premium 4 mobile app