Develop Bugs

[Q] Starburst rom wont boot up.

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

Cant't flash any roms

First day I got the phone I rooted and installed clockwork mod. I downloaded and installed cm9 but now I can't flash any other roms. Every time I try and flash a new one it boots to log screen then stays on a blank black screen. Any help would be appreciated as i would like to try something else out. Also I followed the flashing instructions of each rom and even tried formatting system with no luck.

just to check, you have to format data as well as cache and dalvik when switching amongst roms. not assuming you didn't, just checking.
---------- Post added at 04:26 PM ---------- Previous post was at 04:16 PM ----------
another thought would be to try to flash via recovery, if you haven't tried that.

scott0 said:
just to check, you have to format data as well as cache and dalvik when switching amongst roms. not assuming you didn't, just checking.
---------- Post added at 04:26 PM ---------- Previous post was at 04:16 PM ----------
another thought would be to try to flash via recovery, if you haven't tried that.
Click to expand...
Click to collapse
Thanks for your reply. I have tried flashing in recovery, and just to make sure I was doing everything ok I wiped cache, wiped davlik cache and formatted the system and it still boots to lg screen, then goes to a blank black screen (but the screen is still on) and stops there. The only rom I can get to flash is CM9.

lendmeyoureers said:
Thanks for your reply. I have tried flashing in recovery, and just to make sure I was doing everything ok I wiped cache, wiped davlik cache and formatted the system and it still boots to lg screen, then goes to a blank black screen (but the screen is still on) and stops there. The only rom I can get to flash is CM9.
Click to expand...
Click to collapse
What ROMs are you attempting to flash that aren't working? Did you try to re-download them to see if the original download was corrupted?

drumist said:
What ROMs are you attempting to flash that aren't working? Did you try to re-download them to see if the original download was corrupted?
Click to expand...
Click to collapse
I have tried the kernelpan1c one and domination HD multiple times through multiple downloads.

lendmeyoureers said:
I have tried the kernelpan1c one and domination HD multiple times through multiple downloads.
Click to expand...
Click to collapse
ahh yes, i bricked my phone several months ago this very way, it looks to me like you will have to do machz' unbrick.

scott0 said:
ahh yes, i bricked my phone several months ago this very way, it looks to me like you will have to do machz' unbrick.
Click to expand...
Click to collapse
But the phone isn't bricked. I can boot and even install CM9 but no other ROM. I have tried the unbrick (post 29) but I get stuck at the lg install tool when I plug my phone in it says failed to download

lendmeyoureers said:
But the phone isn't bricked. I can boot and even install CM9 but no other ROM. I have tried the unbrick (post 29) but I get stuck at the lg install tool when I plug my phone in it says failed to download
Click to expand...
Click to collapse
i didn't say your's was bricked, i said i bricked mine doing what you did.
my point was going towards the topic of the thread, you want to fix your phone to be able to flash other ROMs and i'm figuring you will need to follow the unbricking guide to get your phone to a point to do that, even if it's not bricked, by definition.
i'm not sure what post 29 is, but i've done machz's unbricking 2x succesfully, it's the 1st post in his thread.
either way, i know how frustrating it can be, i hope you get it all sorted out.

lendmeyoureers said:
I have tried the kernelpan1c one and domination HD multiple times through multiple downloads.
Click to expand...
Click to collapse
The reason you're having the problem is because the Kernelpan1c ROM does not include a boot image. I'm guessing the Domination HD ROM didn't either, although it seems like the thread for that ROM was deleted so I can't verify that. The ROMs require that you still have the default LG Gingerbread boot image on your device for either of them to work.
Meanwhile CM9 includes a custom boot image, which is necessary since it's ICS.
Do you have a Nandroid backup from when your phone had stock LG Gingerbread installed? If so, what you should do is first restore the Nandroid backup (which will also revert your boot image), then install Kernelpan1c or DominationHD ROM.
If you don't have a nandroid backup, let me know.
---------- Post added at 10:38 AM ---------- Previous post was at 10:34 AM ----------
scott0 said:
my point was going towards the topic of the thread, you want to fix your phone to be able to flash other ROMs and i'm figuring you will need to follow the unbricking guide to get your phone to a point to do that, even if it's not bricked, by definition.
Click to expand...
Click to collapse
Unbricking is overkill. He can boot into CM9 which would give him root access already, so really all he would need to do is go into terminal emulator and push the correct boot image to his device (unless he already has a Nandroid backup, which is easier and less prone to accidentally bricking the device).

drumist said:
The reason you're having the problem is because the Kernelpan1c ROM does not include a boot image. I'm guessing the Domination HD ROM didn't either, although it seems like the thread for that ROM was deleted so I can't verify that. The ROMs require that you still have the default LG Gingerbread boot image on your device for either of them to work.
Meanwhile CM9 includes a custom boot image, which is necessary since it's ICS.
Do you have a Nandroid backup from when your phone had stock LG Gingerbread installed? If so, what you should do is first restore the Nandroid backup (which will also revert your boot image), then install Kernelpan1c or DominationHD ROM.
If you don't have a nandroid backup, let me know.
---------- Post added at 10:38 AM ---------- Previous post was at 10:34 AM ----------
Unbricking is overkill. He can boot into CM9 which would give him root access already, so really all he would need to do is go into terminal emulator and push the correct boot image to his device (unless he already has a Nandroid backup, which is easier and less prone to accidentally bricking the device).
Click to expand...
Click to collapse
this is good advices. but i never was able to sort out how to use terminal emulator, ugh. i kept trying to run commands from within the phone that were ....hekk can't recall exactly. it was frustrating.
but the best advice i think is the nandroid b/u of the original ROM. although nothing necc. wrong with doing a debrick, only takes <30 minutes, as long as the debricking Gods are all in a good mood at that particular moment.

If you get hono's GB rom, then flash HONO's GB kernel, you should be able to boot into GB no problem

drumist said:
The reason you're having the problem is because the Kernelpan1c ROM does not include a boot image. I'm guessing the Domination HD ROM didn't either, although it seems like the thread for that ROM was deleted so I can't verify that. The ROMs require that you still have the default LG Gingerbread boot image on your device for either of them to work.
Meanwhile CM9 includes a custom boot image, which is necessary since it's ICS.
Do you have a Nandroid backup from when your phone had stock LG Gingerbread installed? If so, what you should do is first restore the Nandroid backup (which will also revert your boot image), then install Kernelpan1c or DominationHD ROM.
If you don't have a nandroid backup, let me know.
---------- Post added at 10:38 AM ---------- Previous post was at 10:34 AM ----------
Unbricking is overkill. He can boot into CM9 which would give him root access already, so really all he would need to do is go into terminal emulator and push the correct boot image to his device (unless he already has a Nandroid backup, which is easier and less prone to accidentally bricking the device).
Click to expand...
Click to collapse
Thanks everyone for the replies. I don't have a backup of the original GB ROM, so I'm assuming the boot img is my issue. Someone mentioned flashing a boot image through CM9. Is there a specific instruction list for this? I can go forward with the unbricking procedure if you guys think its easier.

lendmeyoureers said:
Thanks everyone for the replies. I don't have a backup of the original GB ROM, so I'm assuming the boot img is my issue. Someone mentioned flashing a boot image through CM9. Is there a specific instruction list for this? I can go forward with the unbricking procedure if you guys think its easier.
Click to expand...
Click to collapse
Go to the unbricking guide thread and download the boot.img file and place it on your SD card. You don't need any other file.
Next from CM9, open terminal emulator (may have to install it) and type:
Code:
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
Be extra careful that you type this exactly! It's a zero, not an 'o', following 'mmcblk', and it must all be lowercase.
Next turn the device off. If it won't turn off, just pull the battery. Don't try to boot back into CM9 because the phone won't boot up properly at this point in time.
Next use volume down + power to get into CWM again. From there, do factory reset/wipe data and install the ROM you want like normal. It should boot up fine now.
(If it doesn't, you can reflash CM9.)

drumist said:
Go to the unbricking guide thread and download the boot.img file and place it on your SD card. You don't need any other file.
Next from CM9, open terminal emulator (may have to install it) and type:
Code:
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
Be extra careful that you type this exactly! It's a zero, not an 'o', following 'mmcblk', and it must all be lowercase.
Next turn the device off. If it won't turn off, just pull the battery. Don't try to boot back into CM9 because the phone won't boot up properly at this point in time.
Next use volume down + power to get into CWM again. From there, do factory reset/wipe data and install the ROM you want like normal. It should boot up fine now.
(If it doesn't, you can reflash CM9.)
Click to expand...
Click to collapse
THIS WORKED! Thanks so much! Now if there were only more then 1 ROM whose download links worked...

hah, yeah, that command reminded me of what i was doing wrong, i was mistakenly trying to run shell commands from the emulator.

lendmeyoureers said:
THIS WORKED! Thanks so much! Now if there were only more then 1 ROM whose download links worked...
Click to expand...
Click to collapse
Awesome. Now make a Nandroid backup BEFORE you install another ROM, so you have an easier way to revert to your current boot image. That way you can install CM9 again later if you want without worrying about going through this again if you want to install something else.

please help...bootloop

fixed...sorry...

Thanks for starting this thread. When i do a search for "bootloop" all threads have at least 500 postings and i really don't want to spend all day trying to find the part that pertains to this.
I've tried and tried to flash an ics rom (any ics rom) and today decided to flash cm9 stable. Still the same problem...stuck in a bootloop.
Btw. I always clear all 3 caches 3-5 times.
I would assume my problem is with ROM Manager/ because when I go back and load my backup, it says the md5 sum is missing or doesn't match. I'm a;lways able to find one of my backups that match. Any suggestions?
T-Mobile
CWM Recovery 5.0.2.7
Dewizzed V2.5.2
Kernel Version 2.6.35.14
Android2.3.6

If you have access to a computer, download the ROM you want to flash, and if you can boot into recovery on your phone do that and mount your sd card. You should be able to move the file via USB to your phone and flash it.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

...
Estimated Prophet Hawk said:
Thanks for starting this thread. When i do a search for "bootloop" all threads have at least 500 postings and i really don't want to spend all day trying to find the part that pertains to this.
I've tried and tried to flash an ics rom (any ics rom) and today decided to flash cm9 stable. Still the same problem...stuck in a bootloop.
Btw. I always clear all 3 caches 3-5 times.
I would assume my problem is with ROM Manager/ because when I go back and load my backup, it says the md5 sum is missing or doesn't match. I'm a;lways able to find one of my backups that match. Any suggestions?
T-Mobile
CWM Recovery 5.0.2.7
Dewizzed V2.5.2
Kernel Version 2.6.35.14
Android2.3.6
Click to expand...
Click to collapse
You should just backup ur phone up using ur recovery...thats what people mean when they say nandroid...

phordych05 said:
You should just backup ur phone up using ur recovery...thats what people mean when they say nandroid...
Click to expand...
Click to collapse
Unfortunately CWM won't do a reliable backup. With my Nexus One I never had these problems. I flashed countless ROM's from ROM Manager.
---------- Post added at 06:46 PM ---------- Previous post was at 06:27 PM ----------
RTFOP said:
If you have access to a computer, download the ROM you want to flash, and if you can boot into recovery on your phone do that and mount your sd card. You should be able to move the file via USB to your phone and flash it.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Downloaded CM 9.0.0 to PC, Rebooted into Recovery, connected to PC, Mounted USB, Dragged and dropped zip to SD card, wiped all three caches 3 times, installed zip from SD Card via CWM (should I use amon ra?), rebooted phone.....bootloop.

Estimated Prophet Hawk said:
Unfortunately CWM won't do a reliable backup. With my Nexus One I never had these problems. I flashed countless ROM's from ROM Manager.
Click to expand...
Click to collapse
so you think rom manager is better then cwm....really...?... ive never had a problem and im a flashaholic... but did you try a different kernel...?and you did a cache wipe after you rebooted the first time...?

phordych05 said:
so you think rom manager is better then cwm....really...?... ive never had a problem and im a flashaholic... but did you try a different kernel...?and you did a cache wipe after you rebooted the first time...?
Click to expand...
Click to collapse
I Thanks for the input. Not sure what the question is inferring. CWM is a recovery. Rom Manager isn't, but it only works (to my knowlege) with CWM.
Anyway. I'm looking for help.

Estimated Prophet Hawk said:
I Thanks for the input. Not sure what the question is inferring. CWM is a recovery. Rom Manager isn't, but it only works (to my knowlege) with CWM.
Anyway. I'm looking for help.
Click to expand...
Click to collapse
What recovery are you using? It is a known issue when flashing CM9, if you use non-touch recovery and you use it to wipe your cache partition, you will hang during boot. Download TDJ,s cache wipe script to the same sd card as your ROM. After your done flashing CM9 & Gaaps, flash his cache wipe script as your last step, and you should be able to boot up. His scripts are stickied. Some say they don't have this issue, but a lot do and can't get past the booty screen. Good luck and let us know.

Thanks for the help. I just flashed CWM Touch and it solved the problem. I'm now rockin' CM 9.0!

[Q] S3 freezes and basically dies at random times despite battery near full

So weird phenomenon started happening yesterday. I was on cm10.1 RC5 and hadn't done anything new to my phone but randomly throughout the day it would just go black and not respond to unlock and basically looked like it was in power off mode. Only way to get it back up is to reboot but then it will freeze in 5 mins to an hour and power off again.
I thought it was a rom issue at first so I flashed to cm10.2 the most stable one right now but it happened again. So I tried to restore to stock and after I fianlly got it to stock on android 4.12 and then when I was setting up the phone it happned again.
One thing though, I booted phone into recovery and kept it on for more than 2 hours without any random shutoffs or freezes which leads me to believe its still a software issue. Any help?

Ftwpker said:
So weird phenomenon started happening yesterday. I was on cm10.1 RC5 and hadn't done anything new to my phone but randomly throughout the day it would just go black and not respond to unlock and basically looked like it was in power off mode. Only way to get it back up is to reboot but then it will freeze in 5 mins to an hour and power off again.
I thought it was a rom issue at first so I flashed to cm10.2 the most stable one right now but it happened again. So I tried to restore to stock and after I fianlly got it to stock on android 4.12 and then when I was setting up the phone it happned again.
One thing though, I booted phone into recovery and kept it on for more than 2 hours without any random shutoffs or freezes which leads me to believe its still a software issue. Any help?
Click to expand...
Click to collapse
How are you wiping the phone? Which recovery are you using? it does sound ROM related, because you say it stays up in recovery. It could be what edfunkycold talked about before, Sudden Death Syndrome

joeyhdownsouth said:
How are you wiping the phone? Which recovery are you using? it does sound ROM related, because you say it stays up in recovery.
Click to expand...
Click to collapse
I'm wiping the phone through TWRP recovery. Cleaned out the cache,data,storage,system, factory reset basically.

Ftwpker said:
I'm wiping the phone through TWRP recovery. Cleaned out the cache,data,storage,system, factory reset basically.
Click to expand...
Click to collapse
When you say storage are you talking about internal or external? You should not wipe internal storage, some of these files are needed for the Operating System. It's not sudden death syndrome.

joeyhdownsouth said:
When you say storage are you talking about internal or external?
Click to expand...
Click to collapse
Its all internal. I only just put in an external sd card to flash the rom from. I flashed the stock using this method: http://forum.xda-developers.com/showthread.php?t=1904099. Don't know if that makes any different then say restoring from another method.

Ftwpker said:
Its all internal. I only just put in an external sd card to flash the rom from. I flashed the stock using this method: http://forum.xda-developers.com/showthread.php?t=1904099. Don't know if that makes any different then say restoring from another method.
Click to expand...
Click to collapse
I added info to pervious post, in case you didn't see it, do not wipe internal storage, Operating System uses some of those files. Everything else your wiping is correct.

joeyhdownsouth said:
I added info to pervious post, in case you didn't see it, do not wipe internal storage, Operating System uses some of those files. Everything else your wiping is correct.
Click to expand...
Click to collapse
mm shoot I didn't know that. Since its already wiped does that effect anything? I dont think wiping internal created the problem though since it was present before I started flashing to stock.

Ftwpker said:
mm shoot I didn't know that. Since its already wiped does that effect anything? I dont think wiping internal created the problem though since it was present before I started flashing to stock.
Click to expand...
Click to collapse
Before you flashed to stock, were you wiping internal, like when you flashed CM?

joeyhdownsouth said:
I added info to pervious post, in case you didn't see it, do not wipe internal storage, Operating System uses some of those files. Everything else your wiping is correct.
Click to expand...
Click to collapse
joeyhdownsouth said:
Before you flashed to stock, were you wiping internal, like when you flashed CM?
Click to expand...
Click to collapse
Ya i did wipe the internal at least two times when I was flashing different CM roms.

Ftwpker said:
Ya i did wipe the internal at least two times when I was flashing different CM roms.
Click to expand...
Click to collapse
Theres the problem. Theres a thread around here about reformatting internal storage somewhere, I'll see if I can find it, if some1 doesn't beat me to it.
---------- Post added at 07:09 PM ---------- Previous post was at 06:58 PM ----------
joeyhdownsouth said:
Theres the problem. Theres a thread around here about reformatting internal storage somewhere, I'll see if I can find it, if some1 doesn't beat me to it.
Click to expand...
Click to collapse
When you flashed billiard's OTA stock, did you keep stock or you flashed custom recovery, and did you keep root? From my understanding, only stock recovery will erase and rewrite internal storage. I would try it again, and do not flash custom recovery or root access. Let the phone boot up without flashing root or custom recovery. If it boots, and doesn't freeze and die for awhile, then proceed with rerooting and installing custom recovery again.

joeyhdownsouth said:
Theres the problem. Theres a thread around here about reformatting internal storage somewhere, I'll see if I can find it, if some1 doesn't beat me to it.
Are you saying that is causing the phone to randomly die? Or do you mean its another problem?
---------- Post added at 07:09 PM ---------- Previous post was at 06:58 PM ----------
When you flashed billiard's OTA stock, did you keep stock or you flashed custom recovery, and did you keep root? From my understanding, only stock recovery will erase and rewrite internal storage. I would try it again, and do not flash custom recovery or root access file.
Click to expand...
Click to collapse
I flashed custom recovery because I wasn't sure if I would be able to reflash or go into recovery again if the stock rom didnt work. Also I didn't root either.

Ftwpker said:
I flashed custom recovery because I wasn't sure if I would be able to reflash or go into recovery again if the stock rom didnt work. Also I didn't root either.
Click to expand...
Click to collapse
The only thing I can tell you is to try flashing again, without custom recovery, it should wipe and reformat internal storage for you. I don't think custom recovery allows internal storage to be rewritten. As long as you can get into download mode, you can always use ODIN to reflash stock image, should anything happen and the stock ROM didn't work. If your not familiar with ODIN, you can try mskip's toolbox here.

joeyhdownsouth said:
The only thing I can tell you is to try flashing again, without custom recovery, it should wipe and reformat internal storage for you. I don't think custom recovery allows internal storage to be rewritten. As long as you can get into download mode, you can always use ODIN to reflash stock image, should anything happen and the stock ROM didn't work. If your not familiar with ODIN, you can try mskip's toolbox here.
Click to expand...
Click to collapse
Do you have a link on how to use odin to reflash? Want to have it handy in case I get stuck in a bootloop again.

Ftwpker said:
Do you have a link on how to use odin to reflash? Want to have it handy in case I get stuck in a bootloop again.
Click to expand...
Click to collapse
Try the toolbox I posted above. It will open ODIN and flash the needed files for you. YOU MUST FOLLOW DIRECTIONS VERY CAREFULLY. The thing most people miss when using this toolbox, is make sure your phone's serial number shows up, before trying anything else this toolbox will do.

Or you can watch this video from QBKING77 https://www.youtube.com/watch?v=nHpqK6D3P_Y&feature=youtube_gdata_player
Sent from the future via Tapatalk 4

edfunkycold said:
Or you can watch this video from QBKING77 https://www.youtube.com/watch?v=nHpqK6D3P_Y&feature=youtube_gdata_player
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
Totally forgot about this

joeyhdownsouth said:
Totally forgot about this
Click to expand...
Click to collapse
Alright thanks. Will try if needed. Can i install custom recovery if everything woks?

Ftwpker said:
Alright thanks. Will try if needed. Can i install custom recovery if everything woks?
Click to expand...
Click to collapse
Yes, root 1st, then custom recovery. But, to me, the easier way, toolbox will do all these things for you. Let me know how it goes!

joeyhdownsouth said:
I added info to pervious post, in case you didn't see it, do not wipe internal storage, Operating System uses some of those files. Everything else your wiping is correct.
Click to expand...
Click to collapse
Incorrect, nothing that the OS uses gets stored on the internal storage, it all goes to system... It is completely safe to wipe your internal storage when moving between ROMs, I and many others do it with every flash

flastnoles11 said:
Incorrect, nothing important that the OS uses gets stored on the internal storage, it all goes to system... It is completely safe to wipe your internal storage when moving between ROMs, I and many others do it with every flash
Click to expand...
Click to collapse
I fixed your post for you

[please close]Can't flash any other rom after flashing the Android 6.0 gpe rom

Hey guys, hope someone can help me. A few days ago i've flashed the new android m gpe rom and everything was fine. Then somehow i lost root access and tried to fix it. Unfortunately, i'm not even able to flash the fixed rom that was posted a few days later, so i decided to come back to the skydragon sense rom. And for some reason i can't. I try to flash the .zip, it opens in aroma installer, everything goes fine until the installation itself starts. The rom starts to flash, comes to ~20% and then the system just reboots. I've tried both twrp and filz touch, nothing helps.Also supersu doesn't flash properly. I'm not really professional in this, so i might just do somethng wrong, hope someone can help:crying:
Btw i'm s-on.
UPD: I've made an advanced wipe and the everything works now, so if you have the same problem then just try to do the same, see if works.

Did you flash (via TWRP) the GPE ROM, or do the full conversion via RUU?

redpoint73 said:
Did you flash (via TWRP) the GPE ROM, or do the full conversion via RUU?
Click to expand...
Click to collapse
I just flashed the GPE ROM, i'm s-on as i said.

Would this ROM work on Verizon HTC One M8
Hi all,
I've tried to just flash the 6.0 mm rom on my Verizon device, it is s-off with latest firmware, but it just bootloops to the bootloader, then I tried installing the 6.0 firmware and re-flashing the rom but still the same, after that I tried the full conversion and it did not work got same issue, after that just tried to go back to sense installing back the sense firmware and a different rom and I got same problems as fellow above,
My solution was to install RUU from external sd-card from bootloader by renaming the zip file to 0p6bimg.
If someone made this Rom to work with a verizon device I would appreciate the help

Are you still able to go into TWRP recovery and are you also rooted?

crispinsaro said:
Are you still able to go into TWRP recovery and are you also rooted?
Click to expand...
Click to collapse
Who was this question adreed to? If you asked me, then i am able to get into recovery, but the supersu doesn't seem to flash, at least i don't get the root.

Miramontes said:
Hi all,
I've tried to just flash the 6.0 mm rom on my Verizon device, it is s-off with latest firmware, but it just bootloops to the bootloader, then I tried installing the 6.0 firmware and re-flashing the rom but still the same, after that I tried the full conversion and it did not work got same issue, after that just tried to go back to sense installing back the sense firmware and a different rom and I got same problems as fellow above,
My solution was to install RUU from external sd-card from bootloader by renaming the zip file to 0p6bimg.
If someone made this Rom to work with a verizon device I would appreciate the help
Click to expand...
Click to collapse
Well, the problem is that i'm s-on, so i hope there is any other solution for this

Just read your edited post, this is a weird issue, I am sure you factory reset through recovery before installing the new ROM, I normally go on advanced wipe and tick all the boxes and my installs go through perfectly, I also installed GPE 6.0 but I realised it wasn't rooted so I just went back to 5.1- sky dragon, does TWRP say anything just before it reboots? e.g. Failed or something else?

paulmartyn said:
I've tried both twrp and filz touch, nothing helps.
Click to expand...
Click to collapse
This is a big red flag here. Philz hasn't been updated in ages, and older versions of TWRP won't work on Lollipop firmware (if you tried an older recovery like Philz, it occurs to me you may be using an old version TWRP as well).
What is your hboot number and baseband number?
You said "can't flash any other ROMs" in your title; but then only reference Skydragon. Did you try any other ROMs; if so, which ones?
---------- Post added at 01:39 PM ---------- Previous post was at 01:37 PM ----------
Miramontes said:
I've tried to just flash the 6.0 mm rom on my Verizon device, it is s-off with latest firmware, but it just bootloops to the bootloader, then I tried installing the 6.0 firmware and re-flashing the rom but still the same, after that I tried the full conversion and it did not work got same issue
Click to expand...
Click to collapse
ROMs won't work on Verizon, unless they specifically support Verizon (or else you need to change kernel and jump through some other hoops to get it to work).
The partitioning on the Verizon M8 is different from all the others. You're lucky you didn't brick the phone with the GPE RUU.

crispinsaro said:
Just read your edited post, this is a weird issue, I am sure you factory reset through recovery before installing the new ROM, I normally go on advanced wipe and tick all the boxes and my installs go through perfectly, I also installed GPE 6.0 but I realised it wasn't rooted so I just went back to 5.1- sky dragon, does TWRP say anything just before it reboots? e.g. Failed or something else?
Click to expand...
Click to collapse
Will try to erase everything later,maybe tomorrow. Twrp says everything's fine, and aroma doesn't say about any issues, just reboots. Well, when i try to flash supersu for example, it goes fine, but the part when twrp places files(or what it does i don't remember), goes just a few secs, when usually it takes much longer on that stage, so i don't know what the problem is. Anyway, thanks for an advice, will try that and tell if it helps or not

redpoint73 said:
This is a big red flag here. Philz hasn't been updated in ages, and older versions of TWRP won't work on Lollipop firmware (if you tried an older recovery like Philz, it occurs to me you may be using an old version TWRP as well).
What is your hboot number and baseband number?
You said "can't flash any other ROMs" in your title; but then only reference Skydragon. Did you try any other ROMs; if so, which ones?
---------- Post added at 01:39 PM ---------- Previous post was at 01:37 PM ----------
ROMs won't work on Verizon, unless they specifically support Verizon (or else you need to change kernel and jump through some other hoops to get it to work).
The partitioning on the Verizon M8 is different from all the others. You're lucky you didn't brick the phone with the GPE RUU.
Click to expand...
Click to collapse
I tried filz just to check, because on skydragon everything was fine.
I use twrp 2.8.7.0
hboot 3.19.0.0000
radio 1.25.21331147a1.o6g(if that's what baseband is)
tomorrow i'll try everything you guys advised, see if there is a solution. thanks for the support man

Yeah, it is normally recommended to do a full wipe or factory reset through TWRP before installing a new ROM (back up your stuff through google), never led me into any issues.
I don't know if this is related but when I was on 6.0 GPE, TWRP notified me to install SUPERSU, i had a test to see if it would work, but ended up with boot loop, a simple factory reset fixed it and I went back to 5.1.
Let me know how it goes when you wipe or reset and then try installing!

crispinsaro said:
Just read your edited post, this is a weird issue, I am sure you factory reset through recovery before installing the new ROM, I normally go on advanced wipe and tick all the boxes and my installs go through perfectly, I also installed GPE 6.0 but I realised it wasn't rooted so I just went back to 5.1- sky dragon, does TWRP say anything just before it reboots? e.g. Failed or something else?
Click to expand...
Click to collapse
well, i've tried to make an adwanced wipe as you advised and it worked thanks man, i thought i'll stay on that rom 4ever.
flashing skydragon now:victory:

crispinsaro said:
Yeah, it is normally recommended to do a full wipe or factory reset through TWRP before installing a new ROM (back up your stuff through google), never led me into any issues.
I don't know if this is related but when I was on 6.0 GPE, TWRP notified me to install SUPERSU, i had a test to see if it would work, but ended up with boot loop, a simple factory reset fixed it and I went back to 5.1.
Let me know how it goes when you wipe or reset and then try installing!
Click to expand...
Click to collapse
guess the problem was caused by different android versions

redpoint73 said:
This is a big red flag here. Philz hasn't been updated in ages, and older versions of TWRP won't work on Lollipop firmware (if you tried an older recovery like Philz, it occurs to me you may be using an old version TWRP as well).
What is your hboot number and baseband number?
You said "can't flash any other ROMs" in your title; but then only reference Skydragon. Did you try any other ROMs; if so, which ones?
---------- Post added at 01:39 PM ---------- Previous post was at 01:37 PM ----------
ROMs won't work on Verizon, unless they specifically support Verizon (or else you need to change kernel and jump through some other hoops to get it to work).
The partitioning on the Verizon M8 is different from all the others. You're lucky you didn't brick the phone with the GPE RUU.
Click to expand...
Click to collapse
So i've tried to make a FULL wipe and finally it worked, everithing works fine now, installin' skydragon and waiting for a better 6.0 ROM

Guess i can close the thread now as my problem is resolved.

paulmartyn said:
Guess i can close the thread now as my problem is resolved.
Click to expand...
Click to collapse
Happy that solved your issue, it is normally said that to install a new rom you have to do a full wipe before hand, glad it worked for you though

paulmartyn said:
Well, when i try to flash supersu for example, it goes fine, but the part when twrp places files(or what it does i don't remember), goes just a few secs, when usually it takes much longer on that stage, so i don't know what the problem is.
Click to expand...
Click to collapse
You mean flashing SuperSU after Skydragon (you don't specify)? If so, its not necessary, as all custom ROMs are pre-rooted unless explicitly noted.
Also, older versions of SuperSU won't work on Lollipop, so depending on what version SuperSU you tried (again, you don't specify), that may have been the reason for failure.
---------- Post added at 10:18 AM ---------- Previous post was at 10:05 AM ----------
crispinsaro said:
I am sure you factory reset through recovery before installing the new ROM
Click to expand...
Click to collapse
I wouldn't be so sure, if the OP didn't state it.
crispinsaro said:
I normally go on advanced wipe and tick all the boxes
Click to expand...
Click to collapse
I would caution users about following this device literally. It is not necessary to wipe internal storage and/or SD card when flashing a ROM (although particular users may have reason to do so for specific reasons). And if the user has their nandroid or ROM.zip on that partition (and they must have the ROM on one of those, unless they intend to sideload it), its going to get wiped out; causing some confusion and probably panic.
The advice I normally give is: Its called "Advanced" for a reason, and don't wipe it unless you know what the result will be; and you have a legitimate reason to do so.
For instance, I've lost count of the times folks have posted that they wiped system, and don't understand why the phone will no longer boot into OS. Or they wiped internal storage or SD card; and didn't know that it would wipe out their nandroids.
The TWRP default wipe (data, cache and Dalvik) says "most of the time, this is the only wipe you will ever need" and it says that for a reason. If one runs into problems flashing a ROM, they might elect to wipe system. So like I said, a legitimate reason to wipe a particular partition.
But on the other hand, I've done a countless number of ROM flashes on a number of devices (including Skydragon), and never wiped any partition outside the "default wipe", and never had any such issues. Even wiping system (which many swear by) I suspect is often a placebo. When you flash a ROM, system will be wiped by definition, so doing it manually is redundant.
I suspect the failure by the OP was not wiping data and/or cache (they never specified they did that originally or not).

Thats true yes, i dont think I made it clear to do the default TWRP wipe first to see if it would solve anything and then try advanced wipe if all fails, but again with caution.

After reading a litte I've got one question...So if I want GPE rom do I need to convert my phone to GPE or just to flash the rom ?!