My 2 cents..
I was using ICSSGS from 1st RC. But it becomes very laggy after 3-4 weeks, so factory reset every month was necessary. I decided to change ROM.
I installed DOC's v12 ( I assume is is the same Doc that was cooking ROMs for my Omnia, and I was werry pleased with those ROMs). Did wipe, cleaned cache, cleaned Dalvik, formatted /system, flashed ROM, wipe again and it was working. But after two days it was still very laggy (talking about waiting for response for 3-5 seconds) so I wanted something faster. I had choose this Openkang milestone 6.
And then the fun begins.
Downloaded, copied to sd, booted to CWM, all wipes, flashed ROM, flashed gapps and went to bootloop. 3 button combo worked only for download mode, not for entering CWM. There was no way I could access CWM. I even could not enter Android boot (don't know exactly how it is called, but it saved my TF101 more than once.)
So after 1/2 hour of unsuccessful trying to get to CWM, phone just shows logo for icyglitch kernel and went to boot again, I have seen that only option to do anything was Odin. I downloaded Odin, downloaded some 2.3.6 ROM and downloaded CWM for that rom.
First I had to find driver for phone. I remembered phone on ICS wants nexus drivers so I installed those, booted phone to download mode and flashed 2.3.6 rom with Odin.
Phone booted, boot animation was on screen, but it did not boot to working Android. I didn't care too much, just booted to download mode again, flashed CWM and now I had at least access to my sd card. Did all wipes again, flashed DOC again and went to bootloop (Icyglitch kernel logo) again.
....
So I repeated Odin procedure, and when I had working CWM I flashed good old ICSSGS 4.02. This one worked.
I had spent 4 hours to solve this problem mostly because I was not full prepared to flash.
-I had no working USB driver on PC
-I did not had Odin
-I do not have ADB installed. Even if I had it, I don't know much how to use it.
-I did not have any working 2.3.6 ROM WITH bootloader
-Nandroid backup... hmmmm... what is that? Bah, don't need it...
Luckily I flashed my phone so many times I already roughly know what to do, but I still have experienced my share of "OMGOMGOMGOMG".
My advice to new and seasoned flashers:
Don't be cocky. After million of successful flashes once will go wrong. If nothing else Murphy will kick in. And when something goes wrong, be sure that all that you need to rescue phone is on your HDD and you know WHERE it is and how to use it. And read guides. And when you finish reading read them again, then go to sleep and flash next day.
Now I'm even more satisfied with myself because I do not flash other people's phones. If it happens that I create a 400€ brick, it will be at least mine.
If this helps anyone to restore phone, click Thanks button :good:
Thankyou for being man enough to share this, I hope all noobs read this and start getting the message!
slaphead20 said:
Thankyou for being man enough to share this, I hope all noobs read this and start getting the message!
Click to expand...
Click to collapse
Lol you were faster .
I had the same problem today trying to flash aokp m6...
Got bootloop and then Odin was hanging at various points when I tried going back to stock GB.
I thought I was goosed but the good old SGS came through in the end!
Sent from my GT-I9000 using xda premium
Flashing can be frightful. I'm sure every seasoned flasher here on XDA has had their fair share of OMG moments. I know I sure have.
Future advice: after you lost recovery, you didn't need to go back to GB. Stratosk (of Semaphore Kernel) has a .tar version of his ICS kernel that can be flashed with Odin, which will then restore your CWM. This would have been a faster, simpler fix for you. Keep that in mind for next time.
I would suggest you try SlimICS the next time you get sickend of (laggy) ROM. I for one, absolutely love SlimICS, and as all, it does have some drawbacks (no lag, though) when you're pimping it out too much.
upichie said:
Flashing can be frightful. I'm sure every seasoned flasher here on XDA has had their fair share of OMG moments. I know I sure have.
Future advice: after you lost recovery, you didn't need to go back to GB. Sratosk (of Semaphore Kernel) has a .tar version of his ICS kernel that can be flashed with Odin, which will then restore your CWM. This would have been a faster, simpler fix for you. Keep that in mind for next time.
Click to expand...
Click to collapse
Too bad I didn't know that. Somehow I was convinced that no ICS rom or kernel is flashable via Odin. But Later when everything worked and I finally had time to breathe I thought that I didn't need to go to GB. I think maybe only to flash any GB CWM with Odin would be enough. All I needed was working CWM, not entire rom.
Anyway, I'll try Slim now, let's hope I won't need to rescue phone again.
I bricked my phone twice yesterday, trying to install a CM9. It was my first attempt to modify a phone. Nice start.
bpp9 said:
I bricked my phone twice yesterday, trying to install a CM9. It was my first attempt to modify a phone. Nice start.
Click to expand...
Click to collapse
Happens to everyone! 2years in and I accidentally wiped my sd card yesterday! Was a long night! It's a fast learning curve but fun when you get the hang of it!
Always brick my phone in the past, nearly one time a day
Well some tips for flashing:
- On stock ROMs, try flashing all partition firmware (i.e. 3 files in Odin) with re-partition checked before finding for help.
- Always backup you data with apps like Titanium backup, I don't usually use nandroid because it is not so flexible.
- Get GB bootloader before going to CM based ROMs, and go back to froyo bootloader if you want to have froyo back (search EzBoot for this).
- CM based ROMs and stock ROMs use a different filesystem, so flash all partition firmware before going back from CM to stock.
- Same reason, you will mostly get bootloops when going to CM ROMs. In this case, just hold the 3-button combo to enter recovery and flash it again.
- Same reason again, don't use CWM2 recovery to flash CM.
In case that anyone don't know, CM means CyanogenMod.
Hope this helps!
Sent from my GT-I9000 using xda app-developers app
tt0204 said:
Always brick my phone in the past, nearly one time a day
Click to expand...
Click to collapse
Uauuu, and you still didn't have heart attack?
I'm not sure if the fact that I managed to rescue my phone is good. Now I still don't have reason to buy SGS II.
And yes, Slim is woking, you can see my new signature. :highfive:
Managed to flash properly before I did
Wait at least until we get a working jelly bean before getting a new phone!
Sent from my GT-I9000 using xda app-developers app
slaphead20 said:
Happens to everyone! 2years in and I accidentally wiped my sd card yesterday! Was a long night! It's a fast learning curve but fun when you get the hang of it!
Click to expand...
Click to collapse
Ahaha, I did the exact same thing the day before yesterday!
Using GT-I9000 my sent Tapatalk 2 from.
First time i flashed my phone was a heart in mouth moment when it boot looped for the first 2 or 3 times.
Swore I'd never flash my phone again. Over a year later and my phone has gone through countless changes and still going strong.
The only other issue I've had with customizing my phone is telling my flatmate about it. Problem being that he doesn't quite understand the concept of 'rooting' or 'flashing'. At least not in the geek sense of the words.
Yesterday,i was reverting to stock from ics you know...And rooted JW4 with cf.then i wanted to flash semaphore's 2.7.4.I am %100 sure that there was nothing wrong.Just semaphore over cf.Did that ten times!... so here it is;
when flashing process started odin gave fail WHILE flashing zImage.not after or before.Just at the middle of flashing zImage.
I dunno why maybe that one was a random error of odin who nows....
Anyway after it said fail,phone shutted down itself from download mode..First thing that i tried,entering to recovery.But phone was not responding.No boot logo or..just black screen.
I took a deep breath.Restarted my pc while it is restarting i put out the battery from phone wait for 30sec.
Then after pc started up ,i opened odin and put the files etc etc.
Then magical thing happened
I tried directly to the d.mode it worked and flashed JVQ then got JW4 from kies
This was my story...
GT-I9000 cihazımdan Tapatalk 2 ile gönderildi
dreamer94 said:
Yesterday,i was reverting to stock from ics you know...And rooted JW4 with cf.then i wanted to flash semaphore's 2.7.4.I am %100 sure that there was nothing wrong.Just semaphore over cf.Did that ten times!... so here it is;
when flashing process started odin gave fail WHILE flashing zImage.not after or before.Just at the middle of flashing zImage.
I dunno why maybe that one was a random error of odin who nows....
Anyway after it said fail,phone shutted down itself from download mode..First thing that i tried,entering to recovery.But phone was not responding.No boot logo or..just black screen.
I took a deep breath.Restarted my pc while it is restarting i put out the battery from phone wait for 30sec.
Then after pc started up ,i opened odin and put the files etc etc.
Then magical thing happened
I tried directly to the d.mode it worked and flashed JVQ then got JW4 from kies
This was my story...
GT-I9000 cihazımdan Tapatalk 2 ile gönderildi
Click to expand...
Click to collapse
Actually boot directly into download mode without rebooting computer/phone will work
i know but wanted to live with that action,adrenaline
GT-I9000 cihazımdan Tapatalk 2 ile gönderildi
I think we should start a membership here. Anyone who wants to join must expirience "OMG" factor for at least 20 min. I had it 4-5 times, if I count my hassling with Omnia too.
Isn't something interesting? I mean, look at us. We flash phones, sometimes we manage to make it useless, we spend hours for rescuing them, all that time we swear to god that we will never do that again, but 5 minutes after we manage to make our phones work we are ready for next flashing. Here in Slovenia we use to say that even donkey goes on ice only once, but looks like we newer learn...
My current favorite thread, it's refreshingly honest to see people laughing at themselves, and sharing their disasters, we all do it, in fact that's why we do it! Nice to see so much humility
About not bricking other people's phones....
Right now I'm in the process of bricking my boss's phone. He wants ICS on his Dell Streak 5, even if it is only pre-alpha ... Wish me luck.
Related
This is a case of "I have no idea what I'm doing. I shouldn't have messed with crap I don't understand."
I have an Epic 4g that I've rooted previously and, using Odin, installed a custom ROM (forget which one). Yesterday, I attempted to flash Legendary ROM, following the directions in the How-to video linked in the Legendary post. I have an earlier version of CWM (v2.5.1.0 if that makes a difference) than what was on the video. I wiped the data, the Dalvik cache, and the battery stats before I began the flash.
The flash consisted of downloading the zip file of the ROM to my phone, booting into CWM, and installing the zip file from the SD card. The screen said that it installed correctly, but I got an error "E: Can't open /cache/recovery/log". When I went to reboot, it got stuck at the Samsung screen permanently.
I tried to flash again the same way - same thing happened. I read on a forum post somewhere that the SD card partition may not have enough space to flash the ROM, so I partitioned my SD card. Yup, I'm that dumb. Now, when I boot it up, it goes to the Samsung screen for a few seconds, then directly to CWM screen. It even goes to CWM when I plug the phone in without turning it on.
I've searched the forums here and elsewhere for this problem and specifically the error message (E: Can't open ...) and can't really make heads or tails of anything. The replies are over my head as far as my knowledge of my phone and these processes. I don't know what the exact problem is nor how to fix it. If you could help an idiot through the steps, I would greatly appreciate. If you live around the Philly area, I could offer you $50 to fix my phone and install the Legendary ROM.
Thank you for your time in reading this.
as long as it turns on and you get some kinda life you are still good couple things you can try
1 since you are on a older version of CWM wipe data 3 times cache 3 times and dalvic 3 time then try installing your ROM again give it a shot wont hurt anything
2 if that doesnt work you will have to Odin back to stock and re-root...i know it sounda like a pain in the ass but its the best option ill find you a how to for this if you need it
http://forum.xda-developers.com/showthread.php?t=1461337
ajt167 said:
This is a case of "I have no idea what I'm doing. I shouldn't have messed with crap I don't understand."
I have an Epic 4g that I've rooted previously and, using Odin, installed a custom ROM (forget which one). Yesterday, I attempted to flash Legendary ROM, following the directions in the How-to video linked in the Legendary post. I have an earlier version of CWM (v2.5.1.0 if that makes a difference) than what was on the video. I wiped the data, the Dalvik cache, and the battery stats before I began the flash.
The flash consisted of downloading the zip file of the ROM to my phone, booting into CWM, and installing the zip file from the SD card. The screen said that it installed correctly, but I got an error "E: Can't open /cache/recovery/log". When I went to reboot, it got stuck at the Samsung screen permanently.
I tried to flash again the same way - same thing happened. I read on a forum post somewhere that the SD card partition may not have enough space to flash the ROM, so I partitioned my SD card. Yup, I'm that dumb. Now, when I boot it up, it goes to the Samsung screen for a few seconds, then directly to CWM screen. It even goes to CWM when I plug the phone in without turning it on.
I've searched the forums here and elsewhere for this problem and specifically the error message (E: Can't open ...) and can't really make heads or tails of anything. The replies are over my head as far as my knowledge of my phone and these processes. I don't know what the exact problem is nor how to fix it. If you could help an idiot through the steps, I would greatly appreciate. If you live around the Philly area, I could offer you $50 to fix my phone and install the Legendary ROM.
Thank you for your time in reading this.
Click to expand...
Click to collapse
I can fix your phone remotely do you have teamviewer?
Go download and install teamviewer and pm me your id and password and ill fix it.
Sent From My Thugnificent SPH-D700 because its more than Magnificent
Sounds like you bricked it. Search the epic development subforum for thread with the guide on how to odin back to stock and go from there. It should have all the files you need to get everything working.
Sent from my SPH-D700 using XDA App
K3VlN said:
as long as it turns on and you get some kinda life you are still good couple things you can try
1 since you are on a older version of CWM wipe data 3 times cache 3 times and dalvic 3 time then try installing your ROM again give it a shot wont hurt anything
2 if that doesnt work you will have to Odin back to stock and re-root...i know it sounda like a pain in the ass but its the best option ill find you a how to for this if you need it
Click to expand...
Click to collapse
Thank you. I'll try the first when I get home this evening. I'm curious as to why each of those should be wiped 3 times. I'm not arguing your method, just honestly curious.
I don't really know how to get the stock ROM back on there with Odin. Is there a stock file I could download somewhere, or would the file still be on my phone? A how-to would be helpful if you could provide one.
You need to flash CWM5 for correct conversions
Sent from my SPH-D700 using Tapatalk
brooksyx said:
Sounds like you bricked it. Search the epic development subforum for thread with the guide on how to odin back to stock and go from there. It should have all the files you need to get everything working.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
no he just sponged it "bricked" is un-fixable
---------- Post added at 11:11 AM ---------- Previous post was at 11:06 AM ----------
ajt167 said:
Thank you. I'll try the first when I get home this evening. I'm curious as to why each of those should be wiped 3 times. I'm not arguing your method, just honestly curious.
I don't really know how to get the stock ROM back on there with Odin. Is there a stock file I could download somewhere, or would the file still be on my phone? A how-to would be helpful if you could provide one.
Click to expand...
Click to collapse
The link i sent you has everything Toadlife put together awesome packages for us
doing the 3 wipe on older versions is just to ensure you completey wiped everything on some older versions it was mandatory to do it 3 times i believe because not all info would be cleared resulting is bad flashes
On the other had Biggoron is good at what he does and he really can fix your pohone remotely hes a good guy you can trust him.... i think in this case it might be the way to go and im sure he will explain to you everything he is doing
K3VlN said:
no he just sponged it "bricked" is un-fixable
---------- Post added at 11:11 AM ---------- Previous post was at 11:06 AM ----------
The link i sent you has everything Toadlife put together awesome packages for us
doing the 3 wipe on older versions is just to ensure you completey wiped everything on some older versions it was mandatory to do it 3 times i believe because not all info would be cleared resulting is bad flashes
On the other had Biggron is good at what he does and he really can fix your pohone remotely hes a good guy you can trust him i think in this case it might be the way to go and im sure he will explain to you everything he is doing
Click to expand...
Click to collapse
Yep yep I've done this quite a few times now
My record for unbricking flashing to stock and rerooting and restoring a backup is like 10 minutes xD
Sent From My Thugnificent SPH-D700 because its more than Magnificent
brooksyx said:
Sounds like you bricked it. Search the epic development subforum for thread with the guide on how to odin back to stock and go from there. It should have all the files you need to get everything working.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Its not bricked if it turns on! And you don't have to wipe 3 times... only 1 time each on all 3 things! Update your cwm and try to flash again, if that doesn't work odin to stock and start over... this time don't use an old version of cwm use the newest (5.0.2.7)
Sent from my SPH-D700 using Tapatalk
ajt167 said:
Thank you. I'll try the first when I get home this evening. I'm curious as to why each of those should be wiped 3 times. I'm not arguing your method, just honestly curious.
I don't really know how to get the stock ROM back on there with Odin. Is there a stock file I could download somewhere, or would the file still be on my phone? A how-to would be helpful if you could provide one.
Click to expand...
Click to collapse
here is a link for qbking77 with a tutorial for ODINing back to stock...
http://www.youtube.com/watch?v=YQ2g6J1JgjU
the links for the software are under the video.
hope this helps.
bigron is da man and can help u, but if you want to play more with ur phone, BigRon might be with one of his "Honies" and you can't disturb da playa.
K3VlN said:
no he just sponged it "bricked" is un-fixable
---------- Post added at 11:11 AM ---------- Previous post was at 11:06 AM ----------
The link i sent you has everything Toadlife put together awesome packages for us
doing the 3 wipe on older versions is just to ensure you completey wiped everything on some older versions it was mandatory to do it 3 times i believe because not all info would be cleared resulting is bad flashes
On the other had Biggoron is good at what he does and he really can fix your pohone remotely hes a good guy you can trust him.... i think in this case it might be the way to go and im sure he will explain to you everything he is doing
Click to expand...
Click to collapse
Just so you know, bricked isn't unfixabe... I have unbricked a couple epics... it involves a jig and hooking directly to the motherboard... kinda complicated but doable... so no a brick is not unfixable...
Sent from my SPH-D700 using Tapatalk
flastnoles11 said:
Just so you know, bricked isn't unfixabe... I have unbricked a couple epics... it involves a jig and hooking directly to the motherboard... kinda complicated but doable... so no a brick is not unfixable...
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I always heard it was good to know that there is a way to fix it thanks for the info
ajt167 said:
Thank you. I'll try the first when I get home this evening. I'm curious as to why each of those should be wiped 3 times. I'm not arguing your method, just honestly curious.
I don't really know how to get the stock ROM back on there with Odin. Is there a stock file I could download somewhere, or would the file still be on my phone? A how-to would be helpful if you could provide one.
Click to expand...
Click to collapse
http://files.devphone.org/epic4g/SPH-D700-EC05-8gb-REL.tar
MD5SUM: 4ea4dfea809c1a6d59b9fccf9e939f35
That's the file you'll have to use with Odin to flash your phone back to stock 2.2. That file will go in the PDA slot of Odin. Don't bother with a PIT or repartitioning (probably not needed in your case).
Once you boot with stock 2.2, let the phone OTA to EI22 and EL30 to get to stock gingerbread with the updated modem. From there you can start the root/rom flash process again.
flastnoles11 said:
Just so you know, bricked isn't unfixabe... I have unbricked a couple epics... it involves a jig and hooking directly to the motherboard... kinda complicated but doable... so no a brick is not unfixable...
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I'm just glad no one has suggested the good o'l magical restore button anymore xD
Sent From My Thugnificent SPH-D700 because its more than Magnificent
Thank you all for your help. Man, you guys are awesome! I'm going to try to reload stock using Odin this evening. If I'm unable to do this, I'm going to get Biggoron to help me via teamviewer.
Thank you all again. It seems that the only way I'm able to learn about things is by breaking them.
ajt167 said:
Thank you all again. It seems that the only way I'm able to learn about things is by breaking them.
Click to expand...
Click to collapse
Dont sweat that... most of it is all through trial and error. Truthfully, that's how I really got to know my phone better and the stuff I can do w/ it. That and this community. That's why trying a new rom isn't no big thing. If it doesn't take... it doesn't take. That's why we have "nandroid backup" and in "bad" situations, we have ODIN...
wscott9903 said:
Dont sweat that... most of it is all through trial and error. Truthfully, that's how I really got to know my phone better and the stuff I can do w/ it. That and this community. That's why trying a new rom isn't no big thing. If it doesn't take... it doesn't take. That's why we have "nandroid backup" and in "bad" situations, we have ODIN...
Click to expand...
Click to collapse
Welcome to the Sponge club and also the halls of Asgard to visit Odin or heimdall.
It worked!
I was able to successfully set my phone back to stock 2.2 and just received the OTA updates.
Before I left work last night, my wife called and told me that I locked the cat in the office the night before and she chewed up the USB cable for the phone (I'm so "internet"). I stopped at the Sprint store on the way home and got a new USB cable. I was using Odin for the process, following the video, using my new cable, and Odin couldn't see my phone. The guy in the video was completely right about Sprint/Samsung cables being crap. The chewed cable was originally from a Blackberry. I tried the chewed cable, having to hold it stretched out and tilted to the left, and Odin saw my phone. It went smoothly from there, though my arm got a bit sore.
When I get a chance within the next few days, I'm going to root and try again to install Legendary.
You guys are fantastic. Thank you all for your help. It's obvious that the people here know a lot about this stuff, but it's especially great that you're able to explain this stuff to people who don't know much at all. That's a talent.
ajt167 said:
I was able to successfully set my phone back to stock 2.2 and just received the OTA updates.
Before I left work last night, my wife called and told me that I locked the cat in the office the night before and she chewed up the USB cable for the phone (I'm so "internet"). I stopped at the Sprint store on the way home and got a new USB cable. I was using Odin for the process, following the video, using my new cable, and Odin couldn't see my phone. The guy in the video was completely right about Sprint/Samsung cables being crap. The chewed cable was originally from a Blackberry. I tried the chewed cable, having to hold it stretched out and tilted to the left, and Odin saw my phone. It went smoothly from there, though my arm got a bit sore.
When I get a chance within the next few days, I'm going to root and try again to install Legendary.
You guys are fantastic. Thank you all for your help. It's obvious that the people here know a lot about this stuff, but it's especially great that you're able to explain this stuff to people who don't know much at all. That's a talent.
Click to expand...
Click to collapse
Replace that cable ASAP, if you had lost connection in the middle of Odin'ing to stock you could have really bricked your phone! You might need to use Odin again soon..when learning my phone I had to Odin to stock probably 15 times, especially when you start flashing between MTD and BML ROMs (if you don't know what that is, just keep reading on here you will figure it out soon)
luna_c666 said:
Replace that cable ASAP, if you had lost connection in the middle of Odin'ing to stock you could have really bricked your phone! You might need to use Odin again soon..when learning my phone I had to Odin to stock probably 15 times, especially when you start flashing between MTD and BML ROMs (if you don't know what that is, just keep reading on here you will figure it out soon)
Click to expand...
Click to collapse
I have a good cable that I'm planning on using, I just left it at work last night. I'll read up on those types of ROMs. Thank you.
My galaxy 3 (apollo) came with 2.1, so I thought I would update to 2.2. I downloaded JPU from hotfile, the one that uses sampro.pl as password. Had odin set up with .ops, one package, nothing else checked. It flashes it and restarts a few times, then gets to the samsung logo which flashes, then it just freezes.
I have tried wiping the cache and factory reset. I tried JPS too (which I knew worked on my other phone - but that I upgraded from 2.2 to 2.2) but nothing seems to work.
Have I done something wrong?
I would suggest to flash your mobile once again
by following the instructions in the below link.
http://forum.xda-developewjrs.com/showthread.php?t=1372414
I hope it helps.
Somehow I got it working, I flashed Cyanogenmod and it worked, then wiped all including dalvik cache with cwm, still didn't work when I flashed froyo. So I removed sbl.bin and boot.bin from the .tar, tried and still nothing, then wiped data and cache one last time and on reboot it started up!
I had wiped the data and cache tens of times before and after flashing before, so it was either removing the bootloader or wiping the dalvik cache that made a difference. Only took all day to update my phone!
Try to get some different source for froyo....
I'm Glad you got it working again! next time you need stock firmware, use the one available in this forum by searching "stock jpu" the dev has removed the bootloaders and therefore it is much safer, and yeh as you've discovered, when it doubt, wipe the dalvik!
Hi
Yeah I did come across a thread where someone had removed the bootloaders, but all the files were either removed because they were on megaupload, or linked to JPI. I could have used that, infact I did connect it to kies at the start of the day and it said it could upgrade me to JPU. I wanted to do it by odin though! Then 12 hours later and trying countless other firmwares it worked. I just opened the .tar with 7zip and deleted boot.bin and sbl.bin, I had no idea if that would work or not!
It wasn't stuck in a boot loop so the bootloader couldn't have been corrupt? Perhaps it was the dalvik cache needed to be wiped from 2.1 to 2.2? I couldn't see anyway to wipe it with the stock samsung recovery.
Is CWM available for this phone? (without having to flash Cyanogen!)
mike_1983 said:
Hi
Yeah I did come across a thread where someone had removed the bootloaders, but all the files were either removed because they were on megaupload, or linked to JPI. I could have used that, infact I did connect it to kies at the start of the day and it said it could upgrade me to JPU. I wanted to do it by odin though! Then 12 hours later and trying countless other firmwares it worked. I just opened the .tar with 7zip and deleted boot.bin and sbl.bin, I had no idea if that would work or not!
It wasn't stuck in a boot loop so the bootloader couldn't have been corrupt? Perhaps it was the dalvik cache needed to be wiped from 2.1 to 2.2? I couldn't see anyway to wipe it with the stock samsung recovery.
Is CWM available for this phone? (without having to flash Cyanogen!)
Click to expand...
Click to collapse
CM7 is a aftermarket firmware, so it wont be available in the updates....and also, samsung wont give us this kind of good looking ROM anyways, flashing a ROM is a whole lot faster than updating through Kies or others...
J.Purungrit said:
CM7 is a aftermarket firmware, so it wont be available in the updates....and also, samsung wont give us this kind of good looking ROM anyways, flashing a ROM is a whole lot faster than updating through Kies or others...
Click to expand...
Click to collapse
Hi
I just meant is ClockworkMod available for the Galaxy 3. I noticed it was on my phone when I flashed Cyanogen Mod.
I have a Galaxy 5, the CM7 for that seems more complete, I noticed the camera doesn't work on the Galaxy 3 CM7. I thought they would both be about the same functionality.
In my case flashing a rom was slower as it gave me a bunch of problems, but yeah flashing is usually faster
mike_1983 said:
Hi
I just meant is ClockworkMod available for the Galaxy 3. I noticed it was on my phone when I flashed Cyanogen Mod.
I have a Galaxy 5, the CM7 for that seems more complete, I noticed the camera doesn't work on the Galaxy 3 CM7. I thought they would both be about the same functionality.
In my case flashing a rom was slower as it gave me a bunch of problems, but yeah flashing is usually faster
Click to expand...
Click to collapse
Camera has been mostly fixed in CM7 and Galaxy 5 has been out for longer so devs have had more time. Anyway, all custom ROM's come with CWM Recovery.
I think you can install cwm for stock Roms..I have seen similar question in some thread posted here..which says your phone should be initially rooted to do this..
I am not sure abt the process..but as far as I know..you have to follow these steps :
download an app called as z4root..search in Google..its not available in market..
root your phone..it will ask two options to either root permanently or temporarily..go permanently..(you can unroot it I think so don't worry)
and finally you can try several custom kernals.. head over to development thread for that.I prefer fugumod kernal..take the tar file and flash it via Odin (safer side wipe dalvik as well as cache and reboot)
since its a stock rom ..you will not be having dedicated option to go for recovery, use volume keys,power button and the center button together..
bit of headache..
try at your own risk..or if I am wrong, please advice
Smonic said:
Camera has been mostly fixed in CM7 and Galaxy 5 has been out for longer so devs have had more time. Anyway, all custom ROM's come with CWM Recovery.
Click to expand...
Click to collapse
Ah I didnt know the Galaxy 5 had been out longer. The camera didn't work when I used the latest CM7 for the Galaxy 3, when it took a picture it looked like a commodore loading screen But I didn't check gallery thinking about it, perhaps they came out alright
prabhuthelegend said:
I think you can install cwm for stock Roms..I have seen similar question in some thread posted here..which says your phone should be initially rooted to do this..
I am not sure abt the process..but as far as I know..you have to follow these steps :
download an app called as z4root..search in Google..its not available in market..
root your phone..it will ask two options to either root permanently or temporarily..go permanently..(you can unroot it I think so don't worry)
and finally you can try several custom kernals.. head over to development thread for that.I prefer fugumod kernal..take the tar file and flash it via Odin (safer side wipe dalvik as well as cache and reboot)
since its a stock rom ..you will not be having dedicated option to go for recovery, use volume keys,power button and the center button together..
bit of headache..
try at your own risk..or if I am wrong, please advice
Click to expand...
Click to collapse
I rooted the phone with SuperOneClick, I think it worked! Anyway I gave the phone to my brother now and hes just interested in a working phone, not messing about with roms! I may get the phone again when it comes down in price again (you can get them refurbished in brand new condition here in UK)
Thanks!
Okay, so first off, I'm literally about to light this fking thing on fire.
This damn phone has been the death of me. I have a Tbolt and Galaxy Tab, and NEITHER have been as much of a pain in my ass.
This seems impossible because since I got the phone, I've had nothing but problems.
1. Unlocked bootloader via fastboot. K, done.
2. Flash AmonRa Recovery (I did this before AND after using CWM recovery, having custom rom, etc, it never worked) Always sat in a loop at the google X with unlock symbol, or just reboots into normal (and yes, the MD5s are correct) 3. I've had the phone get into the rom both with SIM and without, and randomly reboot, from using anything from market, to file explorer, to hitting the lock screen.
Honestly, I'm tempted to just sell it again (since I bought it off ebay) and buy something different, though that's a pain to do, and I need it for a trip to europe in a week, so I would love to have a phone I'm not pissed off at. And yea, already got mad enough I threw it.
I've literally spent HOURS looking through Google results on all the issues. And have YET to make this lil pos stable enough for me to use like I do my tbolt. nice 100 battery pulls. Seriously. Heeelllpp on this, :-/
hkbladelawhk said:
Okay, so first off, I'm literally about to light this fking thing on fire.
This damn phone has been the death of me. I have a Tbolt and Galaxy Tab, and NEITHER have been as much of a pain in my ass.
This seems impossible because since I got the phone, I've had nothing but problems.
1. Unlocked bootloader via fastboot. K, done.
2. Flash AmonRa Recovery (I did this before AND after using CWM recovery, having custom rom, etc, it never worked) Always sat in a loop at the google X with unlock symbol, or just reboots into normal (and yes, the MD5s are correct) 3. I've had the phone get into the rom both with SIM and without, and randomly reboot, from using anything from market, to file explorer, to hitting the lock screen.
Honestly, I'm tempted to just sell it again (since I bought it off ebay) and buy something different, though that's a pain to do, and I need it for a trip to europe in a week, so I would love to have a phone I'm not pissed off at. And yea, already got mad enough I threw it.
I've literally spent HOURS looking through Google results on all the issues. And have YET to make this lil pos stable enough for me to use like I do my tbolt. nice 100 battery pulls. Seriously. Heeelllpp on this, :-/
Click to expand...
Click to collapse
try
fastboot erase cache
fastboot erase userdata
fastboot erase system
and then flash via fastboot the AmonRa recovery again.
BTW, which ROM are you trying to flash? ICS or Gingerbread? And do you have Blackrose installed?
taodan said:
try
fastboot erase cache
fastboot erase userdata
fastboot erase system
and then flash via fastboot the AmonRa recovery again.
BTW, which ROM are you trying to flash? ICS or Gingerbread? And do you have Blackrose installed?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=872441 << Flashed this.
So far, I've knocked my network to 2g and it's been fine. though not really much of a fix. And I had cleared all of the above using CWM prior to the attempted flash. I'd rather not have to wipe everything again just to get AmonRa. I've wiped quite a few times. Though did get something about /sd-ext missing when erasing via CWM. Also, I tried erasing recovery, and got this: "erasing 'recovery'... FAILED (remote: not allowed)". Not sure if that matters. Just seems that flashing via Fastboot has failed everytime. I flashed CWM via fastboot and that failed too, I ended up getting it working via RomManager.
I had the same problem. After i dropped my phone on the floor everything worked fine
Sent from my GT-I9001 using Tapatalk
jojogangsta said:
I had the same problem. After i dropped my phone on the floor everything worked fine
Sent from my GT-I9001 using Tapatalk
Click to expand...
Click to collapse
Yea, though I still feel like I'm getting intermittent reboots. IT's not an everyday use phone, so I'll have to see how it fares when I'm overseas.
flash 4ext touch via 4ext recovery control app
Then install a different rom like miui or cm7 or hypersense nova
Sent from my Nexus One using XDA
joelshawdow said:
flash 4ext touch via 4ext recovery control app
Then install a different rom like miui or cm7 or hypersense nova
Sent from my Nexus One using XDA
Click to expand...
Click to collapse
Done and done. Still have a problem with boot looping. Google X with vibration, then goes black and does it again, and it loops like that indefinitely. Though this isn't new, been since I unlocked it....POS.
Deleted
Leave it in a freezer for a day no joke
Sent from My Samsung Galaxy S2 running Paranoidandroid Rom.What else if not?=P
First of all any ROM you find here for an update is going to have bugs. So have to prepared for reboots, and/or no boots.
On the other hand, you have to verify to see if you have any hardware issues. In order to do so, you have to flash to a stock ROM to see if the issue continues. If stock ROM is just fine, then its the custom ROM that is causing grief! So try another custom ROM, until the one that suits your needs.
my sugestion 2 u - use cm7.2. use 4ext touch recov, wipe all ur stuff, flash blackrose hboot with no repartitioning, flash cm7.2 rom, finally, stop b!tching!
ai6908 said:
First of all any ROM you find here for an update is going to have bugs. So have to prepared for reboots, and/or no boots.
On the other hand, you have to verify to see if you have any hardware issues. In order to do so, you have to flash to a stock ROM to see if the issue continues. If stock ROM is just fine, then its the custom ROM that is causing grief! So try another custom ROM, until the one that suits your needs.
Click to expand...
Click to collapse
Did it when it went back to stock. And Whoever said put it in the freezer, I did, and worked on it with AC on it, and it worked better . Though for some reason, never been able to flash recoveries via fastboot. Oh well. 4ext rocks.
hkbladelawhk said:
Did it when it went back to stock. And Whoever said put it in the freezer, I did, and worked on it with AC on it, and it worked better . Though for some reason, never been able to flash recoveries via fastboot. Oh well. 4ext rocks.
Click to expand...
Click to collapse
I never had any luck flashing recovery using fastboot either. Anyhow, it sounds like a motherboard issue to me. Sorry pal!
ai6908 said:
Anyhow, it sounds like a motherboard issue to me. Sorry pal!
Click to expand...
Click to collapse
This. The description fits overheating and overly sensitive to temperature CPU.
yon can flash another rom
yon can flash another rom
Still having bootup problems
Okay, sorry to bring this back up, but I am still having an issue with the phone booting. If I get the phone on, it's fine, doesn't randomly turn off or anything. However, if I try to reboot, power off and power back on for any reason....it becomes a pain to get back up and running. I usually have to do a couple battery pulls before it comes back up. Does the same thing. Hits the X, vibrates once like it's gonna turn on. Then a few seconds to a min later, goes black, then flashes the x and vibrates once again. It loops like this until I pull the battery and try again. Sometimes it takes a couple times to work. Its not the ROM either, because this is the issue I had when I first got the phone and did fastboot oem unlock. It would hang on stock. It's done it on all 3 ROMs I've tried. I don't wanna say fully it's a CPU issue, because I don't have issues once it's on.
Any new idears?
PS. I tried CM7, and I didn't like it. Not a fan of AOSP ironically enough.
The Nexus One will give off 7 Vibrations to indicate a hardware issue, we will just have to wait and see
Title says it all guys blowing of the dust of this thing can anyone point me to the most stable ROMs out there CM10 prefer
Sent from my HTC6435LVW using Tapatalk 2
I'd like to know this too. I often have to turn wifi off then on to reconnect.
Team EOS4 & KatKernel are by far the most stable ROM and Kernel combination available from my experience, also it is JB 4.2.2, the latest Android available atm
No wifi issues at all, wifi works after sleep, never disconnects during use for me, and works first time after a full boot, just remember to set the correct wifi location in settings
Team EOS 4, Katkernel here too, make sure you reboot a few times after installing it. follow the guide in this forum, install it like it directs you to.
FULL wipe(cache, dalvik, factory, system), install ROM, cache/dalvik wipe, install gapps, cache/dalvik wipe, install Kernel, cache/dalvik wipe, reboot.
Get Kat apk to boost volume and GPS fix.
I was having systemUI issues, reinstalled everything a few times and now it's running great. Keep it under 1400mhz, 1200mhz seems to work well for me. Nightly 109 was eating up my battery too quickly, 111 is doing better, I hope they can improve more if possible, great ROM either way, I'm very grateful.
Sent from my Transformer TF101 using xda app-developers app
I cant write to developer threads (including TeamEos ROM) since I didn't write 10 post yet, but...
I love TeamEOS. One and half year I've used 4.1 compilation and now I use 4.2 #112 build....
What can I say? Stable WIFI, fast GPS as hell, marvelous performance.... Try it!
And big thanks for Developers of TeamEos and KAT Kernel. You should be owners of ASUS! or companies like this.
Astania said:
I cant write to developer threads (including TeamEos ROM) since I didn't write 10 post yet, but...
I love TeamEOS. One and half year I've used 4.1 compilation and now I use 4.2 #112 build....
What can I say? Stable WIFI, fast GPS as hell, marvelous performance.... Try it!
And big thanks for Developers of TeamEos and KAT Kernel. You should be owners of ASUS! or companies like this.
Click to expand...
Click to collapse
Just reply to a few other threads, XDA has thousands
+1 for EOS4/KAT kernel. No-name is pretty good as well if you like CM 10.1.
EOS is amazing running 4.2.2 with my cpu overclocked to 1400 is amazing
+1
talman26 said:
EOS is amazing running 4.2.2 with my cpu overclocked to 1400 is amazing
Click to expand...
Click to collapse
Aye...EOS 4.2.2 (v109) + 1400, very stable, no big issues, suitable for daily drive tab
+1
Team EOS4, Been using it for months and not a WiFi hicup.
*Detection* said:
Team EOS4 & KatKernel are by far the most stable ROM and Kernel combination available from my experience, also it is JB 4.2.2, the latest Android available atm
No wifi issues at all, wifi works after sleep, never disconnects during use for me, and works first time after a full boot, just remember to set the correct wifi location in settings
Click to expand...
Click to collapse
Dude, I did that update and crashed! I was using Stock ICS4.0 ASUS version and using [recovery-clockwork-touch-5.8.1.8-tf101-repack]. Happens that ended Succesfully, but it did not REBOOT. Bricked at the ASUS logo screen...I don´t know what to do, nothing works. Tried to unBrick from APX mode but can´t run into it. :crying:
danilimpsy said:
Dude, I did that update and crashed! I was using Stock ICS4.0 ASUS version and using [recovery-clockwork-touch-5.8.1.8-tf101-repack]. Happens that ended Succesfully, but it did not REBOOT. Bricked at the ASUS logo screen...I don´t know what to do, nothing works. Tried to unBrick from APX mode but can´t run into it. :crying:
Click to expand...
Click to collapse
Can you still get into recovery? If so, can you flash from the microSD?
danilimpsy said:
Dude, I did that update and crashed! I was using Stock ICS4.0 ASUS version and using [recovery-clockwork-touch-5.8.1.8-tf101-repack]. Happens that ended Succesfully, but it did not REBOOT. Bricked at the ASUS logo screen...I don´t know what to do, nothing works. Tried to unBrick from APX mode but can´t run into it. :crying:
Click to expand...
Click to collapse
That's because your running CWM recovery, I know its not easy to read every thread going, but if I had £1 for every person I've said the same thing to over the past 2 weeks I'd easily have £7.39 by now
Use Easyflasher to unbrick and flash TWRP recovery, then you can flash Jellybean ROMs without bricking
http://forum.xda-developers.com/showthread.php?t=1688012
APX Mode will not show anything on the TF screen, just plug the TF into the PC USB, then turn off the TF, then hold power and volume up until you hear the USB connect sound, that tells you that it is in APX mode, then you can run Easyflasher to unbrick
There should really be a sticky made about CWM, it doesn't play nice with JB ROMs
Team EOS 4 + Kat Kernel = FAST and STABLE :victory:
PS: If you wish to use Phablet UI i suggest you use Trebuchet from CM 10.1
*Detection* said:
That's because your running CWM recovery, I know its not easy to read every thread going, but if I had £1 for every person I've said the same thing to over the past 2 weeks I'd easily have £7.39 by now
Use Easyflasher to unbrick and flash TWRP recovery, then you can flash Jellybean ROMs without bricking
http://forum.xda-developers.com/showthread.php?t=1688012
APX Mode will not show anything on the TF screen, just plug the TF into the PC USB, then turn off the TF, then hold power and volume up until you hear the USB connect sound, that tells you that it is in APX mode, then you can run Easyflasher to unbrick
There should really be a sticky made about CWM, it doesn't play nice with JB ROMs
Click to expand...
Click to collapse
Ok, but to use Easyflasher I have to go into APX and I CAN´T (maybe driver issue, but I reinstlaled and nothing!
I DO can go into TWRP Recovery (to be straight it´s the only thing that workED) but flashing ROMs FAILED over 5 times. So, to get a lil worse, I was clearing cache and Dalvik and suddenly I miss-touched SYSTEM...and now I think that I did MESS with it. I reboot and I get nothing but [Eee Pad ASUS] screen...not even get to loading dots!!
Last try was LINUX Coldboot...nothing succesfull at all!
I gonna kill myself....BRB!
danilimpsy said:
Ok, but to use Easyflasher I have to go into APX and I CAN´T (maybe driver issue, but I reinstlaled and nothing!
I DO can go into TWRP Recovery (to be straight it´s the only thing that workED) but flashing ROMs FAILED over 5 times. So, to get a lil worse, I was clearing cache and Dalvik and suddenly I miss-touched SYSTEM...and now I think that I did MESS with it. I reboot and I get nothing but [Eee Pad ASUS] screen...not even get to loading dots!!
Last try was LINUX Coldboot...nothing succesfull at all!
I gonna kill myself....BRB!
Click to expand...
Click to collapse
Of course it won't boot; wiping system means deleting the ROM. Just re-flash the ROM now and see if that works. You are supposed to wipe system before flashing a new ROM anyway (to clear out remnants of the old ROM), so it's no big deal.
Sent from my Transformer TF101
zAlbee said:
Of course it won't boot; wiping system means deleting the ROM. Just re-flash the ROM now and see if that works. You are supposed to wipe system before flashing a new ROM anyway (to clear out remnants of the old ROM), so it's no big deal.
Click to expand...
Click to collapse
As I already said...flashing ROM FAILED over 5 to 7 times...and I CAN´T get to APX...i´m stucked at NO SYSTEM...just can get to Recovery, but NO flashing!
Try a different PC, or reinstall APX drivers
99% that APX mode does work, either you are doing something wrong, or your PC is struggling with the APX drivers
APX mode is volume up & power from powered off state while already plugged into PC, the only notification for entering APX mode is USB connect sound, nothing will appear on TF screen
I tried EOS4 recently and although the release looks good I experienced so many crash/reboots/freeze that it would make the worst build of the stock ROM look fantastic.
There are lots of update but nothing about fixing the important stuff like reboots, freeze no return from sleep
I would strongly advise on staying with stock ROM at the moment
hulk69 said:
I tried EOS4 recently and although the release looks good I experienced so many crash/reboots/freeze that it would make the worst build of the stock ROM look fantastic.
There are lots of update but nothing about fixing the important stuff like reboots, freeze no return from sleep
I would strongly advise on staying with stock ROM at the moment
Click to expand...
Click to collapse
Have to ask, what recovery did you use and did you do a full wipe before installing?
I find EOS 4 to be MUCH more stable on WiFi than any ICS ROM (including Stock and stock based ROMs)
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.