Database Users

Openfire ROM Problem

Apologies for the double post but I'm dying to get my wildfire back working.
Rooted it yesterday with unrevoked, attempted to add the Openfire ROM this morning with everything going fine untill the reboot. I'm now stuck on the white HTC screen and have been for the last hour. Any help would be great, cheers.

did u do nandriod back up first
Sent from my Archos5 using the XDA mobile application powered by Tapatalk

I backed up the stock firmware I already had manually, before it prompted on the flash.

did you do a full wipe before flashing the rom?

No i didn't, thought it would be safer incase something went wrong?

run your restore then I couldn't get it to work either
Sent from my Archos5 using the XDA mobile application powered by Tapatalk

if you did a nandroid backup of your stock rom then you should be fine to wipe, since you did not wipe and flashed the new rom over your stock rom, apps and settings will conflict, therefore not work...

Right I see, I'm currently going through what I'm guessing is the restore....recovery - Nandroid, I'll let you know how I get on.
Thanks again.

Nope I seem to be getting nowhere here, can someone point me in the direction of the restore?

you didn't do nandroid backup did you haha, you'll have to install an RUU file to return to stock rom, or just do a full wipe and flash a new rom like openfire or wildpuzzle.

Where can I find the RUU file and how do I access my SD card? USB won't let me get to it, I'm guessing the phone is in charge mode?

go into recovery - partitons menu - mount sd card (or somthing like that) to open your memory card

Spot on, I'm on downloading an ruu file now, going to load it up with a stock rom then try flashing it again, but wiping it this time.

Infact how do I do a full wipe? I'm after the easiest way to get the phone booting up so I can flash it properly?

Anyone?
I'm still no further than I was three hours ago!
EDIT:
BREAKTHROUGH!!! =D
Restored it to before I flashed it incorrectly. Nearly threw the phone across the room in excitement.

go into clockwork recovery and click the title "wipe data/factory reset" and then flash the ROM you want to use.. to install a ROM:
- "install zip from sdcard"
- "Choose zip from sdcard"
- "click the zipfile"
- "yes"
- "reboot"
and if you want to install RUU dont ask me never done that

Reggie24 said:
Anyone?
I'm still no further than I was three hours ago!
EDIT:
BREAKTHROUGH!!! =D
Restored it to before I flashed it incorrectly. Nearly threw the phone across the room in excitement.
Click to expand...
Click to collapse
How did u restored it .....????

sunny_16977 said:
How did u restored it .....????
Click to expand...
Click to collapse
From the HBOOT screen go to recovery, then nandroid, restore, and to the appropriate time/date.
I've still had no luck with actually flashing the phone though. Back to Android 2.1 for me.

I'm 99% percent sure you have the OC issue some ppl incl myself on here have - try reinstalling openfire if thats what you wanna use - and then go to wildpuzzle thread - dl 0050 and flash it. If i'm correct phone will be fine and use openfire - but will NOT be overclockable. I wish Jacob had my phone or got hold of a phone w that problem...

I had problems with the Wildpuzzle 8.0.11 ROM, it would just sit there (did a ADB logcat on it, but I've lost the actual log... sorry! ) ignoring a duplicate entry (yeah, I did a full wipe . Removed WP and put on the latest OpenFire ROM... omg... what a difference to the stock ROM! Soooo much faster, even before I overclocked it.
I'd say, if you have boot issues with WP give OpenFire a go. Certainly worked a treat on my Wildfire.

[Q] Can't boot... have been meticulous... Help please?

This may "wreak of non-search" and I am sorry if it does. While I have searched, the overall panic that one experiences when you suspect a brick and cannot afford to have a brick.... (that, plus a friend purchased this Glacier for me to help me get back on my feet with respect to career/employment, etc., so a good amount of guilt is thrown into this mix)... all prevents me from rationally and methodically searching thread after thread to figure out why I am having the problem I am having.
I will be as precise as possible.
1. Back in Feb., I perm rooted with visionary... then about 2 weeks later, I read that this root was not true radio s=off perm root, so I used adb and the scripts to perm root again--using the wiki as a guide. Saved a copy of the partition 7 bin on my laptop as an added precaution. Also, BTW, I never flashed the engineering HBOOT. It didn't seem essential to do so... PLUS, in almost every guide it warned that this was the most likely chance for one to f*ck up and brick, so in the interest of erring on the side of caution, I skipped that.
2. I kept stock ROM for several weeks after that... just enjoying root and freezing bloatware with Ti, and doing other root-enabled mods... nothing too involved.
3. About 1 week ago, I finally decided to flash my ROM. I had Rom Manager (paid version), and had flashed ClockworkMod Recovery 3.0.0.5. Further, as an FYI, I had/have numerous nandroid backups on the SD, plus several Ti backups of apps/data... even sync'd this with dropbox, so I can access those now (which are not of any help obviously).
4. I first flashed a CM7 nightly build--wiped data and cache, and as far as I know followed the guides precisely. All was well...new ROM worked alright... some bugs, but it was nice to have the new features, etc.. And of course the mental gratification of having 2.3.3 (GB) instead of 2.2.1 (boring old froyo). I updated the nightly maybe 2 times... in each case, I simply flashed without backing up those ROMS or wiping data/cache as they didn't seem necessary, plus I still had all my stock rom nandroid backups on the SD.
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Since I cannot get into the phone... I am of course panicked... I have ADB on my laptop if needed, but I really am at a loss as to why this happened, and what I can do at this point....
Please, please advise. My utmost appreciation and sincerest gratitude in advance for any assistance.
Thank you!!!
syntropic

syntropic said:
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Click to expand...
Click to collapse
Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
should come up to a white screen.

take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Sent from my HTC Glacier using XDA App

Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
Click to expand...
Click to collapse
No... that is what I meant when I said tried to "boot into recovery". And I got the 3 vibrate alerts and a blank screen, and nothing........

take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Click to expand...
Click to collapse
Will do... Thank you. DO you have any idea of where I f*cked up here??

Could be a number of things. Like wipe didn't go through completely , bad download, or just random crap out like a few others. Even flashing with the wrong cwr version can less to your issues. Lol like I said could be a number of things. Sorry I couldn't be more helpful.
Sent from my HTC Glacier using XDA App

OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....

I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Sent from my HTC Glacier using XDA App

syntropic said:
OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....
Click to expand...
Click to collapse
What recovery are you using? 3.0.0.5? and you're trying to flash a 2.2 ROM. Thats where the problem lies. See my post regarding this. It's in my signature, the green one.

I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Click to expand...
Click to collapse
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
EDIT: MUSTKll20... Well, you were right... This is not ROM specific. I tried Re-Flashing RC3, which previously worked fine. Now, since I have CWModRec 3.0.0.5, I need to use a 2.3 ROM.... So I thought I would start with this idea. So, I guess, I need to get whatever is corrupt deleted... So my only question thus remains: How do I wipe everything except the SD from within CWR?
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!

syntropic said:
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!
Click to expand...
Click to collapse
You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
and android phone have a method of using a section of the SD card for their memory banks. I'm not really sure how it works either, but it does. You can wipe the internal w/o wiping the SDcard.
Wiping the phone from with in the recovery image will not touch the SDcard, it will only wipe the internal. You can format the SD card from the Recovery Image, but i'll leave that dog sleep so we do not it accidentally.

last little clean-up question.
Sorry to bump this... last LAST question...
Mustkll20: I realized that you were correct to suggest to wipe everything except the SD... Something is corrupt.
But I am not real sure exactly how to wipe EVERYTHING except the SD, from within CW recovery... Since that is the only mode I have available to me. Once I wipe, I will reinstall CM RC3, then update Clockworkmod Recovery to 3.0.0.6, and then try and download RC4 again using another method, and re-flashing.
I would trial and error this, but do not want to wipe the SD.
Thanks guys... seriously.

You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
Click to expand...
Click to collapse
I didn't see your reply... ummm. and I do need to wipe.. Because I have tried to re-flash both RC3 and RC4, and I get what must be a "bootloop": During the CM splash, it stops and then reboots---over and over. It never did that before.... so my problem is something else...
I don't know what else there is besides the SD and the ROM, but whatever it is, I need to delete it. So should I do a factory reset???

Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.

lowandbehold said:
Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.
Click to expand...
Click to collapse
Yep... I know the thread is not for thrillseekers (i.e., its boring), but I mention that I discovered this phenomenon... so I really wasn't in all that bad a spot to begin with.
I still need to figure out how to fix my current problem.... all CM RCs (I can only flash 2.3 ROMs because of CW 3.0.0.5) go into what I guess is a bootloop. In other words, they do not ever boot, just crash and restart. And the RC3 ROM I used worked fine before this... so something else is causing this problem. I need to wipe everything I guess, but I just don't know how... without touching the SD card and from within Clockwork Recovery.

Ok. Go into recovery.
1. Wipe data/factory reset
2. wipe cache partition
Both of these are on the main screen.
Go to advanced
3. Wipe Davlik Cache
Go back to main screen
Go into mounts and storage
4. format boot
5. format system
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.

lowandbehold said:
Ok. Go into recovery.
{...}
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.
Click to expand...
Click to collapse
Thank you for the concise and thorough response!!!!!!! Id thank you, but have used up my allotment. get ya tommorow!!

And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?

syntropic said:
And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?
Click to expand...
Click to collapse
You can thank the Google c&d order for that. Go to cyanogenmod.com. there is a link there for the gapps zip.
Sent from my HTC Glacier using XDA App

OK... I thoght Gapps.zip was just Google Docs. Luckily, I had that on my SD card from one of my many ROM downloads. I see why they had to make it separate.
But I am installing it, and everything is great... And I learned a lot too... Which can only mean trouble.
Thanks!

Noobie Rom ?

I have tried to install, following instruction on this site to install ROM's. I have tried Starburst and Task650. I currently have the OTA Touchwiz installed from Samsung, and Pershoot kernel 2.6.34-4-cyanogenmod installed. Every time I try it goes through the process and successfully I reboot, it boots to the Samsung Logo (Start) and I wait like 20 minutes and it does nothing, just stay at the start Samsung logo. I have done this several times on each ROM, always having to go back to a backup I did. What am I doing wrong? Why can’t I install any ROMs? I would greatly appreciate some expert advice, because I hear so many great things about Task650 I really want to give it a shot. I am an ex-iPad owner, gave to daughter as a friend had one and let me use it; feel in love with it the moment I picked it up. I have also searched the forums, but I am doing everything to the T as outlined in instructions. Had my tab for a week, it isn’t a 10.1v or I/O series. Thanks everyone in advance for helping a complete noob when it comes to android.

Sounds like a case of missing to clear the cache.
Did you wipe the cache partition and dalvic cache in the recovery menu?
After making major changes like switching between roms or kernels thats recommended and if not done might cause such an issue.

I did
I did do those steps, did the factory wipe/reset, wiped cache, wiped dalvic. Once I did those 3 steps, installed from zip, goes through the steps successfully, but when I reboot it just stay on logo. I read, it could take 5-10 min, but I have waited up to 20 and it doesn't move past that. Just see what I am doing wrong, as the 2 roms have both done that, and I have tried several times with both. Just have the stock rom with Touchwiz OTA upgrade from Samsung, and pershoots latest kernel. Thanks in advance.

bad zip file?
Is it possible the zip files are getting corrupt? Are you downloading them on your tab or on computer and transferring them over? I would also check to see if there are any errors when you flash.

Download from computer and transfer over. How can I if there are errors as once I install a ROM it just stays at the logo. After it starts to install it end with, i cant recall exactly, but it says success. Thanks in advance

In cwm when you flash there is some text readout. That is where some error messages could be seen. That text will be there before you choose reboot on the menu.

sounds like you've had some issues bro. if you do get fed up and need some help, just let me know and we can video chat through gmail or skype to get you through it and get you a custom rom.

slice2011 said:
I have tried to install, following instruction on this site to install ROM's. I have tried Starburst and Task650. I currently have the OTA Touchwiz installed from Samsung, and Pershoot kernel 2.6.34-4-cyanogenmod installed. Every time I try it goes through the process and successfully I reboot, it boots to the Samsung Logo (Start) and I wait like 20 minutes and it does nothing, just stay at the start Samsung logo. I have done this several times on each ROM, always having to go back to a backup I did. What am I doing wrong? Why can’t I install any ROMs? I would greatly appreciate some expert advice, because I hear so many great things about Task650 I really want to give it a shot. I am an ex-iPad owner, gave to daughter as a friend had one and let me use it; feel in love with it the moment I picked it up. I have also searched the forums, but I am doing everything to the T as outlined in instructions. Had my tab for a week, it isn’t a 10.1v or I/O series. Thanks everyone in advance for helping a complete noob when it comes to android.
Click to expand...
Click to collapse
Well first...are you rooted? Do you have Clockworkmod, Superuser, and Busybox?
Oh and congrats on your switch from Apple to Android

slice2011 said:
I have tried to install, following instruction on this site to install ROM's. I have tried Starburst and Task650. I currently have the OTA Touchwiz installed from Samsung, and Pershoot kernel 2.6.34-4-cyanogenmod installed. Every time I try it goes through the process and successfully I reboot, it boots to the Samsung Logo (Start) and I wait like 20 minutes and it does nothing, just stay at the start Samsung logo. I have done this several times on each ROM, always having to go back to a backup I did. What am I doing wrong? Why can’t I install any ROMs? I would greatly appreciate some expert advice, because I hear so many great things about Task650 I really want to give it a shot. I am an ex-iPad owner, gave to daughter as a friend had one and let me use it; feel in love with it the moment I picked it up. I have also searched the forums, but I am doing everything to the T as outlined in instructions. Had my tab for a week, it isn’t a 10.1v or I/O series. Thanks everyone in advance for helping a complete noob when it comes to android.
Click to expand...
Click to collapse
Maybe try in "reverse" order
Flash kernel back to stock - flash the rom you want - if that works then flash pershoots kernel
Just a thought

hy
i installed the overcome rom on my 7500, and i'm so entusiast!
Try it it's very easy!
---------- Post added at 07:21 PM ---------- Previous post was at 07:16 PM ----------
i did it in recovery, do wipe data

Yes its is rooted, cmw, superuser, and busybox all installed. Installed both roms in recovery, hold volume down and power method. Just can't figure it out, I will do the reverse suggestion and report back later tonight or tomorrow.thanks everyone for the advice/help.

no erreor s after install, think task's says success or something to that effect.

Well it finally stuck, I knew it was going right as when it was installing system files, it took like 5 minutes, the other time I did it took like 30 seconds. As per Stinky73 went back to stock Kernel, and wipe data, clear cache partition, and wipe Dalvik Cache, Thanks a million Stinky73 u da man! HELL YEAH this Rock, it is so responsive, seems a hell of a lot smoother, and apps just snap open. Task you did one outstanding job. This is coming from a noob who has no idea how much work goes into these, I am sure a lot. So from a noob to an expert EXCELLENT JOB, love my Tab that much more!!!!! Thanks everyone for the help, I am one happy camper! Now another dilemma, I saw new versions: How do I install these now that I have Tasks650 installed and working? Do I have to do the same steps above, wipe data, cache, and Dalvik? And if so what do I do next, do I do the same: Also is the BOB_WOW_Fix installed using the same method as i read flashable, sorry for the noob question, just want to get it right.
1. install zip from sdcard.
2. choose zip from sdcard.
NEW!!!- Task650's V7.1
Once again... I forgot to add "Desktop UAstring to V7.1 so flash this update after you boot up V7.1 if you want it.

Can someone please give me the proper ateps on installing the bob_wow_fix, and the 2 7.1 updates? Thanks

slice2011 said:
Can someone please give me the proper ateps on installing the bob_wow_fix, and the 2 7.1 updates? Thanks
Click to expand...
Click to collapse
There's no complete fix for BoB and WoW, its a continuous work in progress.

bob wow fix
Are you taking about the fix task posted?
What I had to do was wipe cache first then flash the zip just like you did on the rom. And bobs your uncle.
Edit:
Oh ya I would reboot after each flash just to be sure.

So as you probably read had a hell of a time getting a rom installed, followed stink'ys advice and it worked. Installed 6.0, finally, than installed the 6.1 theme update, no issues. Than downloaded the 7.1, followed op. wiped dalvik, wiped cache, and wipe data/factory restore. No errors, but when I rebooted it got stuck once again on the Samsung logo with the Galaxy Tab 10.1 print. So i do not know what the heck I am doing wrong. I got 6.0 than 6.1 updated and now I am back to my initial problem with 7.1, no I didn't use the 7.1 update one. tried 3 times, and even downloaded the fiel again, and followed the same steps task outlined, and no go. Had to restore the 6.1 from back up.

slice2011 said:
So as you probably read had a hell of a time getting a rom installed, followed stink'ys advice and it worked. Installed 6.0, finally, than installed the 6.1 theme update, no issues. Than downloaded the 7.1, followed op. wiped dalvik, wiped cache, and wipe data/factory restore. No errors, but when I rebooted it got stuck once again on the Samsung logo with the Galaxy Tab 10.1 print. So i do not know what the heck I am doing wrong. I got 6.0 than 6.1 updated and now I am back to my initial problem with 7.1, no I didn't use the 7.1 update one. tried 3 times, and even downloaded the fiel again, and followed the same steps task outlined, and no go. Had to restore the 6.1 from back up.
Click to expand...
Click to collapse
All sounds very strange...is it definitely stuck on the boot screen? These things can take anything from 5-20 minutes on initial boot, there is no definite rule for that, seems to be device related in some strange way...how long have you left it?
I am really an OCD when it comes to upgrading and always backup (nandroid or whatever) then go back to the very start before trying something new...years of PC and Mac have taught me that even tho the manufacturers say you just apply upgrades on top of previous upgrades, sooner or later they will f**k up....
I wonder why you are passing thro all the steps you are...(going thro 6.0, 6.1 etc)
I would be inclined to try going back to stock....stock whatever it was rom when you got the tab (notice you've never stated what model you have), stock kernel, nothing installed....then go direct to Tasks 7.1 (everything needed in 6.x is incorporated in 7.1) .... then, if it boots and runs, add pershoots kernel...
What do you reckon Task?? Can you chip in on this one?
Cheers, Stinky

@ slice2011.....any news?

Drpbody said:
And bobs your uncle..
Click to expand...
Click to collapse
How'd you know Bob was my uncle?
Oh wait..everybody has an uncle bob somewhere

[Q] Help a noob, cannot boot after trying to flash stock rom

So I'm pretty desperate and I apologize if similar info was posted somewhere else. I've been researching several hours but couldn't find anything.
I originally installed CM11 and decided to experiment with a different rom TriForce ROM [TouchWiz]. I put the zip file on my SD card and booted into clockworkmod it gave an error of bad zip. I tried different usb port to transfer the zip, downloaded it multiple times with no result. So I decided to try a different rom Stock_Rooted_Deodexed_MF9_Rom.zip. The installation finished but the phone would not boot.
Recently I flashed the stock rom from odin, it finished successfully but still not boot, Galaxy sreen lights up quickly and that's it.

rmngorelov said:
So I'm pretty desperate and I apologize if similar info was posted somewhere else. I've been researching several hours but couldn't find anything.
I originally installed CM11 and decided to experiment with a different rom TriForce ROM [TouchWiz]. I put the zip file on my SD card and booted into clockworkmod it gave an error of bad zip. I tried different usb port to transfer the zip, downloaded it multiple times with no result. So I decided to try a different rom Stock_Rooted_Deodexed_MF9_Rom.zip. The installation finished but the phone would not boot.
Recently I flashed the stock rom from odin, it finished successfully but still not boot, Galaxy sreen lights up quickly and that's it.
Click to expand...
Click to collapse
Restore from nandroid backup. I hope you made one. Try going into recovery do a factory reset and wipe all cache and data and what not and then install a ROM from Odin.

rmngorelov said:
So I'm pretty desperate and I apologize if similar info was posted somewhere else. I've been researching several hours but couldn't find anything.
I originally installed CM11 and decided to experiment with a different rom TriForce ROM [TouchWiz]. I put the zip file on my SD card and booted into clockworkmod it gave an error of bad zip. I tried different usb port to transfer the zip, downloaded it multiple times with no result. So I decided to try a different rom Stock_Rooted_Deodexed_MF9_Rom.zip. The installation finished but the phone would not boot.
Recently I flashed the stock rom from odin, it finished successfully but still not boot, Galaxy sreen lights up quickly and that's it.
Click to expand...
Click to collapse
Make sure you're using roms for your version of your phone. the MF9 bootloader is really old and probably wont install anymore. My phone did this before and I thought I bricked it, but I kid you not I took the battery out and removed the SIM card and rebooted and it booted up just fine. May not work for you, but I suggest you go back to update stock firmware then try again. If you're using the triband model, there's a post around here somewhere with confirmed roms that wont brick your device. I'm currently using the Google Play Edition Stock ROM and it's working GREAT.
Link for new firmware (NG5 Firmware): https://mega.co.nz/#F!0JdRkIZR!AqqKdbvba_Hpg5VrCmrbPw

i7vSa7vi7y said:
Restore from nandroid backup. I hope you made one. Try going into recovery do a factory reset and wipe all cache and data and what not and then install a ROM from Odin.
Click to expand...
Click to collapse
I restored to this stock ROM before and everything worked well. Currently I can't boot into recovery, Samsung flashes once and that's it, that's why I'm desperate the only thing I can do is boot in to download mode for odin.

silentdeath631 said:
Make sure you're using roms for your version of your phone. the MF9 bootloader is really old and probably wont install anymore. My phone did this before and I thought I bricked it, but I kid you not I took the battery out and removed the SIM card and rebooted and it booted up just fine. May not work for you, but I suggest you go back to update stock firmware then try again. If you're using the triband model, there's a post around here somewhere with confirmed roms that wont brick your device. I'm currently using the Google Play Edition Stock ROM and it's working GREAT.
Link for new firmware (NG5 Firmware):
Click to expand...
Click to collapse
Does it matter that I can't get into recovery to clear the cache first before trying new roms?

silentdeath631 said:
Make sure you're using roms for your version of your phone. the MF9 bootloader is really old and probably wont install anymore. My phone did this before and I thought I bricked it, but I kid you not I took the battery out and removed the SIM card and rebooted and it booted up just fine. May not work for you, but I suggest you go back to update stock firmware then try again. If you're using the triband model, there's a post around here somewhere with confirmed roms that wont brick your device. I'm currently using the Google Play Edition Stock ROM and it's working GREAT.
Link for new firmware (NG5 Firmware):
Click to expand...
Click to collapse
Maybe I'm doing something foolish but every time I try to download files from the link you gave I get a decryption error so I can't download them zip or original.

rmngorelov said:
I restored to this stock ROM before and everything worked well. Currently I can't boot into recovery, Samsung flashes once and that's it, that's why I'm desperate the only thing I can do is boot in to download mode for odin.
Click to expand...
Click to collapse
Just hold home power and volume up. Right when you see text at the top left let go. You have to have the right timing

i7vSa7vi7y said:
Just hold home power and volume up. Right when you see text at the top left let go. You have to have the right timing
Click to expand...
Click to collapse
After almost eight hours of troubleshooting I finally got it to work.
I've tried flashing clockworkmod several times to see if I could get into recovery with no result so I gave up on that and I flashed the newest stock rom I could find L720VPUFNG2_L720SPTFNG2_SPR and it was still not booting. Than I thought maybe twerp would make a difference and god almighty it finally booted! I felt as if I gave birth to a child after eight hours of labor!
Now I'm extremely paranoid about touching anything because it took me forever to do this. Does anyone know why flashing twerp would make such a difference? I know this sort of stuff can get extremely complicated but I'd like to try to understand.
I hope my foolish agony contributed to this community if not in any other way except by the comedic relief caused by my ignorance.

rmngorelov said:
After almost eight hours of troubleshooting I finally got it to work.
I've tried flashing clockworkmod several times to see if I could get into recovery with no result so I gave up on that and I flashed the newest stock rom I could find L720VPUFNG2_L720SPTFNG2_SPR and it was still not booting. Than I thought maybe twerp would make a difference and god almighty it finally booted! I felt as if I gave birth to a child after eight hours of labor!
Now I'm extremely paranoid about touching anything because it took me forever to do this. Does anyone know why flashing twerp would make such a difference? I know this sort of stuff can get extremely complicated but I'd like to try to understand.
I hope my foolish agony contributed to this community if not in any other way except by the comedic relief caused by my ignorance.
Click to expand...
Click to collapse
Depends what recovery you had and what version. I personally like Philz touch recovery but TWRP is good. Now wipe and flash a ROM my friend or restore a backup

rmngorelov said:
After almost eight hours of troubleshooting I finally got it to work.
I've tried flashing clockworkmod several times to see if I could get into recovery with no result so I gave up on that and I flashed the newest stock rom I could find L720VPUFNG2_L720SPTFNG2_SPR and it was still not booting. Than I thought maybe twerp would make a difference and god almighty it finally booted! I felt as if I gave birth to a child after eight hours of labor!
Now I'm extremely paranoid about touching anything because it took me forever to do this. Does anyone know why flashing twerp would make such a difference? I know this sort of stuff can get extremely complicated but I'd like to try to understand.
I hope my foolish agony contributed to this community if not in any other way except by the comedic relief caused by my ignorance.
Click to expand...
Click to collapse
im having similar issues. which version of TWRP worked for you?
thank you

fearthemarchx said:
im having similar issues. which version of TWRP worked for you?
thank you
Click to expand...
Click to collapse
I recommend flashing the newest one here using odin
http://teamw.in/project/twrp2
Then once you are able to boot into recovery go to wipe and perform both factory reset and format data. Then install whatever rom you like, I used Sprint Galaxy S4 SPH-L720 VPUFNAE (Androdi 4.4.2) found here
http://galaxys4root.com/galaxy-s4-stock-firmware/ (or maybe find a newer stock rom if this one gives you errors)
Just copy the zip file to the phone, boot into twrp, do wipe factory reset again, select install then select the zip in whatever directory and you should be good to go. Make sure you do a back up in twrp once you get the phone to boot so you can always revert to stock.
I hope I was thorough enough that some of the information was useful. Let me know if you need any more help.

only certain recoveries will stick. ive tried the most recent twrp, with no luck. only a few versions of philztouch work.
Sent from my LGL34C using XDA Free mobile app

fearthemarchx said:
only certain recoveries will stick. ive tried the most recent twrp, with no luck. only a few versions of philztouch work.
Sent from my LGL34C using XDA Free mobile app
Click to expand...
Click to collapse
Format with philztouch that works then try flashing a new stock rom with odin. That should bring everything back to stock including the recovery.

ive tried. when i flash rom via odin i only get a blue "recovery booting" at the top of boot screen. even when i only power on, not into recovery. im going to attempt to flash rom provided in previous post via philz.
Sent from my LGL34C using XDA Free mobile app

fearthemarchx said:
ive tried. when i flash rom via odin i only get a blue "recovery booting" at the top of boot screen. even when i only power on, not into recovery. im going to attempt to flash rom provided in previous post via philz.
Sent from my LGL34C using XDA Free mobile app
Click to expand...
Click to collapse
You're in download mode when you flash from odin right? If you your getting an error flashing, try a different stock rom after reformating/resetting to factory (it's crucial to clear the cache before trying a different rom). I had to try a few roms before I found one that worked.

Got Stucked at Bootloader screen

I was rooting my device and was successful l in that. I flashed TWRP and Magisk and after that I decided to install a custom ROM. While going for it I again wiped the - Delvik Cache, System, Data and Cache. And when I tried installing that ROM it doesn't gets install. Moreover I can't boot into System anymore and now I'm stucked at the screen saying "Your device has been unlocked and can't be trusted." Also the screen is showing "ID:N/A"
So please please please help me with this problem ASAP. I can't use my phone now please and I regret for what I've done.

Try booting into fastboot mode. Hold down volume down and power for several seconds. If you can get there, you can flash the stock ROM and hopefully get back to normal. There are other threads that show you how to install. Make sure you use a version that is greater than or equal to what you last had installed.

NZedPred said:
Try booting into fastboot mode. Hold down volume down and power for several seconds. If you can get there, you can flash the stock ROM and hopefully get back to normal. There are other threads that show you how to install. Make sure you use a version that is greater than or equal to what you last had installed.
Click to expand...
Click to collapse
So this means my Stock ROM is gone? and I've to install it again? Can u explain me what my problem is?

engtika said:
So this means my Stock ROM is gone? and I've to install it again? Can u explain me what my problem is?
Click to expand...
Click to collapse
When you installed a custom ROM your stock ROM was gone. That's how it works. But the reason you're stuck at the screen you're at, I don't know.
Restoring back to stock is the first thing I'd try to see if you can actually use your phone

NZedPred said:
When you installed a custom ROM your stock ROM was gone. That's how it works. But the reason you're stuck at the screen you're at, I don't know.
Restoring back to stock is the first thing I'd try to see if you can actually use your phone
Click to expand...
Click to collapse
Thanks for the information you provided regarding my problem. Now I've installed the Stock ROM and my dead phone is back to life. ?