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
The last thing I remember doing is going to flash a new ROM.
I went into recovery then pushed "factory reset" in CWM.
Ever since then I have not been able to mount /data or /cache so I cannot restore a backup or flash a new ROM. I've tried a lot of different things, NOW I cannot even get a Recovery to start up. (flashed and deleted different versions of different Recoveries (TWRP and CWM).
Was wondering what other solutions there might be.
Right now I am currently using an older booloader with the yellow triangle. Any help is appreciated. Thank you so much!
Well start by putting twrp back on if at all possible go to mount and make sure there are no checks in the boxes of data in system and try to flash another rom or do a restore if you still have issues something far worse has gone wrong post back when and if you can get to that point
---------- Post added at 08:45 PM ---------- Previous post was at 08:41 PM ----------
Also read the first post then maybe through this thread and make sure this is not your case http://forum.xda-developers.com/showthread.php?t=1651413
I accidently deleted my back-up and now I'm left with TWRP 2.2 and everytime I try to install a tom it fails halfway through. So I looked and most say ignore and wipe Dalvik cache, so I do. Reboot, then it just boots to TWRP.
Kindle Fire Utility will not detect my Fire either.
I'm at a loss, please help.. :\
In twrp go to mount and then mount the drive. Then download a rom from the development section and transfer it to your kindle. Then flash the rom.
---------- Post added at 11:21 PM ---------- Previous post was at 11:21 PM ----------
veeman said:
In twrp go to mount and then mount the drive. Then download a rom from the development section and transfer it to your kindle. Then flash the rom.
Click to expand...
Click to collapse
Do a factory reset again and then flash.
veeman said:
In twrp go to mount and then mount the drive. Then download a rom from the development section and transfer it to your kindle. Then flash the rom.
---------- Post added at 11:21 PM ---------- Previous post was at 11:21 PM ----------
Do a factory reset again and then flash.
Click to expand...
Click to collapse
I followed your instructions explicitly and they were to no avail, as they relinquished the same results in my latter post.
I've been inactive here over the last month, but from what I've seen the over last couple of days, it seems there's a new version of TWRP (2.2.0? am I seeing this correctly?) that is causing problems. Try an earlier version.
soupmagnet said:
I've been inactive here over the last month, but from what I've seen the over last couple of days, it seems there's a new version of TWRP (2.2.0? am I seeing this correctly?) that is causing problems. Try an earlier version.
Click to expand...
Click to collapse
I had first tried 2.0 then updated to 2.2.
Thanks
Then I would say, since you know you can restore from a backup, try requesting one (minus personal data of course) from someone and see if you can restore from it.
It's very strange some of the things going on lately. I'd hate to think Amazon's hardware has something to do with it, although, I wouldn't put it past them.
soupmagnet said:
Then I would say, since you know you can restore from a backup, try requesting one (minus personal data of course) from someone and see if you can restore from it.
It's very strange some of the things going on lately. I'd hate to think Amazon's hardware has something to do with it, although, I wouldn't put it past them.
Click to expand...
Click to collapse
Any idea where I'd look for a back-up?
The idea has merit, I just googled it and nothing came up.
maybe you'd volunteer to send me a back up?
Thanks
JerzyLW said:
Any idea where I'd look for a back-up?
The idea has merit, I just googled it and nothing came up.
maybe you'd volunteer to send me a back up?
Thanks
Click to expand...
Click to collapse
Lemme see what I can do...
---------- Post added at 12:17 AM ---------- Previous post was at 12:12 AM ----------
Gimme time to flash something create a backup and upload it stick around It won't be posted for long...
Thepooch said:
Lemme see what I can do...
Click to expand...
Click to collapse
It is much appreciated! :highfive:
Check your pm
---------- Post added at 12:52 AM ---------- Previous post was at 12:44 AM ----------
I was thinking more direct upload but since your not here that's kinda difficult lol yea restoring a borrowed backup is probably your best bet once you have a working system replacing twrp would probably be a good idea I have a simple solution for that that really doesn't require much just placing a folder on your SD card and using file browser to run a script... but I really can tell you whether this will remedy your problem if it still exists it could be more than meets the eye..
Maybe your just doing it wrong.
1. Factory reset
2. Wipe cache
3. Wipe dalvik
4. Wipe system
5. Flash rom zip (in zip form)
6. Flash gapps zip (in zip form)
7. Reboot then system if prompted....
If your doing all this and it fails make sure you have zip signature verification and md5 verification unchecked, still failing sounds like a twrp problem..
Also twrp should be throwing you some errors would be nice to know what they are?
Thepooch said:
Check your pm
---------- Post added at 12:52 AM ---------- Previous post was at 12:44 AM ----------
I was thinking more direct upload but since your not here that's kinda difficult lol yea restoring a borrowed backup is probably your best bet once you have a working system replacing twrp would probably be a good idea I have a simple solution for that that really doesn't require much just placing a folder on your SD card and using file browser to run a script... but I really can tell you whether this will remedy your problem if it still exists it could be more than meets the eye..
Click to expand...
Click to collapse
The restore was successful. I am now stuck in a boot loop with TWRP.
And I still cannot get KFU to recognize my Fire either.
JerzyLW said:
The restore was successful. I am now stuck in a boot loop with TWRP.
And I still cannot get KFU to recognize my Fire either.
Click to expand...
Click to collapse
Install a newer version of TWRP (2.1.1 or greater). Reboot to system does not work properly in earlier versions. Otherwise, use "adb shell idme bootmode 4000" to set the bootmode to normal manually. If you are unfamiliar with adb/fastboot, read this guide...
http://forum.xda-developers.com/showthread.php?t=1552547
The third post has explanations of adb/fastboot commands and how to use them, but the entire guide will probably be useful to you.
kinfauns said:
Install a newer version of TWRP (2.1.1 or greater). Reboot to system does not work properly in earlier versions. Otherwise, use "adb shell idme bootmode 4000" to set the bootmode to normal manually. If you are unfamiliar with adb/fastboot, read this guide...
http://forum.xda-developers.com/showthread.php?t=1552547
The third post has explanations of adb/fastboot commands and how to use them, but the entire guide will probably be useful to you.
Click to expand...
Click to collapse
Thanks I'll take a look.
JerzyLW said:
Thanks I'll take a look.
Click to expand...
Click to collapse
No matter what I do, I cannot get my computer to recognize my Kindle. In device manager it says it is there with a yellow triangle, so I click update it doesn't work, I check my Android SDK downloader and it says I have the drivers downloaded so I manually searched for them in the extras folder in the sdk folder, still no go. I get an error. I am now at ends I have no idea what to do, and it is very aggravating to say the least.
Thanks for your help guys!
Instead of letting it boot by itself manually select normal boot in the boot menu if that doesn't work rewipe restore the backup again this time skip the dalvik and cache wipe after the restore...
My computer can't find my kindle fire and it's mounted on twrp
make sure there are no checks in the boxes of system and data then hit the big button that says mount..... the only things that should have checks in them are sdcard and cache...
Thepooch said:
make sure there are no checks in the boxes of system and data then hit the big button that says mount..... the only things that should have checks in them are sdcard and cache...
Click to expand...
Click to collapse
Yes they are but the computer wont find it. Do you know how to get the computer to find the kindle via adb?
if you cant mount your sdcard there is more at play than meets the eye look at this thread http://forum.xda-developers.com/showthread.php?t=1877567
I'm having an issue with the latest liquidsmooth ROM. I updated my kernel, cleared my cache and my dalvik. This is a dirty flash. But I'm stuck at the Liquidsmooth loading animation. It has sat here for a good 10 minutes so far. Is this normal for the first time? I had this issue before so I just flashed back to my old rom and it was fine after that.
Anyone please? I can't use my phone and have no back ups or another rom to flash to. And my computer wont install the drivers in order to push a rom onto my phone..
What did you dirty flash from? Dirty flashes are generally a bad idea, unless you are flashing from an update for a rom. But even then, you need to make sure the OP says its ok to dirty flash because the nature of some update can require a full wipe
Sent from my PG06100
---------- Post added at 11:41 PM ---------- Previous post was at 11:40 PM ----------
And you dont need the drivers to get a rom on your phone. Just mount the sdcard through recovery and it should show as a usb mass storage device
Sent from my PG06100
CNexus said:
What did you dirty flash from? Dirty flashes are generally a bad idea, unless you are flashing from an update for a rom. But even then, you need to make sure the OP says its ok to dirty flash because the nature of some update can require a full wipe
Sent from my PG06100
---------- Post added at 11:41 PM ---------- Previous post was at 11:40 PM ----------
And you dont need the drivers to get a rom on your phone. Just mount the sdcard through recovery and it should show as a usb mass storage device
Sent from my PG06100
Click to expand...
Click to collapse
I did a dirty flash from JellyBomb. And it wont allow me to mount the sdcard, I choose it and it just stays at "mount sdcard". I have mounted the extsdcard but when I plug my phone into my computer, it makes 3 beeps and doesn't display anything. Also, I appreciate all the help.
Edit: After doing a wipe installing liquidsmooth works now I have lost eveyrthing though
Theminatar said:
I did a dirty flash from JellyBomb. And it wont allow me to mount the sdcard, I choose it and it just stays at "mount sdcard". I have mounted the extsdcard but when I plug my phone into my computer, it makes 3 beeps and doesn't display anything. Also, I appreciate all the help.
Edit: After doing a wipe installing liquidsmooth works now I have lost eveyrthing though
Click to expand...
Click to collapse
You shouldve made a nandroid, then you couldve done advanced restore > data only....
Sent from my PG06100
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