Related
it was a rutine day as usual, running the GPS with CoPilot and playing music stream via BT to the car
and all of the sudden BAMN! the scary grey Google screen with the unlocked lock shows up
I was like *** BEEP ***, in my head i though oh, it might just be that reboot bug that is plaguing everybody but me, and now it's finally catching up
but noooooo... after i got to work i tried to reboot the phone (pulling battery out), nada, nothing, zero, zip... still the same dead google screen
then the worse case scenarios flashes through me head (knowing samsung past issues ) so i'm blazing for the worse...
currently i confirmed it can go into CW recovery screen and also go into the Odin Download Mode screen
so i'll try a nandroid backup first
if that is a no go, Odin is next...
Good luck, man. I feel your pain.
Hope you don't have to resort to odin, but if you do, that safety net will have proved its utility.
Again good luck!
Sent from my Nexus S using XDA Premium App
I can almost guarantee that ODIN will work. I resurrected a Fascinate that was locked out from itself using ODIN as well as a Captivate that had this same problem you are describing. ODIN dont **** around.
AllGamer said:
it was a rutine day as usual, running the GPS with CoPilot and playing music stream via BT to the car
and all of the sudden BAMN! the scary grey Google screen with the unlocked lock shows up
I was like *** BEEP ***, in my head i though oh, it might just be that reboot bug that is plaguing everybody but me, and now it's finally catching up
but noooooo... after i got to work i tried to reboot the phone (pulling battery out), nada, nothing, zero, zip... still the same dead google screen
then the worse case scenarios flashes through me head (knowing samsung past issues ) so i'm blazing for the worse...
currently i confirmed it can go into CW recovery screen and also go into the Odin Download Mode screen
so i'll try a nandroid backup first
if that is a no go, Odin is next...
Click to expand...
Click to collapse
hey what is your "flashing" history? (i.e. roms, kernels, etc.)
serialtoon said:
I can almost guarantee that ODIN will work. I resurrected a Fascinate that was locked out from itself using ODIN as well as a Captivate that had this same problem you are describing. ODIN dont **** around.
Click to expand...
Click to collapse
Well, that's if Odin is used right, otherwise it can ruin the phone. I've used it to bring back my Vibrant a bunch. It's good knowing that these Galaxy S phones are nearly brick proof.
All is not lost, honest...
AllGamer said:
it was a rutine day as usual, running the GPS with CoPilot and playing music stream via BT to the car
and all of the sudden BAMN! the scary grey Google screen with the unlocked lock shows up
I was like *** BEEP ***, in my head i though oh, it might just be that reboot bug that is plaguing everybody but me, and now it's finally catching up
but noooooo... after i got to work i tried to reboot the phone (pulling battery out), nada, nothing, zero, zip... still the same dead google screen
then the worse case scenarios flashes through me head (knowing samsung past issues ) so i'm blazing for the worse...
currently i confirmed it can go into CW recovery screen and also go into the Odin Download Mode screen
so i'll try a nandroid backup first
if that is a no go, Odin is next...
Click to expand...
Click to collapse
Hi AllGamer.
I had a similar disaster with the black google screen, and I had the unlocked bootloader as well, first I relocked bootloader, then used odin to reflash (http://forum.xda-developers.com/showthread.php?t=947950 ) then used the e0b546c442bf.signed-soju-GRI40-from-GRH78.e0b546c4 update (http://android.clients.google.com/p...2bf.signed-soju-GRI40-from-GRH78.e0b546c4.zip) renamed it to update.zip, put it on root of memory, and ran it via the built in recovery mode after..phew.
Odin saved my life to!!
Good luck...
i guess i should have updated the post before heading out to lunch
not too long after i posted the original message, i was able to reflash any ROM, and got it to boot back to normal.
it was weird for some odd reason the ROM just got corrupted? i don't see how's that possible
I was on Bionix 1.3 beta for the longest time, and i've been on Bionix pretty much ever since December 2010/Jan 2011
I'm now back to Stock 2.3.3, but i replaced the stock recovery with CW recovery
I simply booted into the CW recovery mode, and then loaded a new ROM from zip
Yipee
AllGamer said:
i guess i should have updated the post before heading out to lunch
not too long after i posted the original message, i was able to reflash any ROM, and got it to boot back to normal.
it was weird for some odd reason the ROM just got corrupted? i don't see how's that possible
I was on Bionix 1.3 beta for the longest time, and i've been on Bionix pretty much ever since December 2010/Jan 2011
I'm now back to Stock 2.3.3, but i replaced the stock recovery with CW recovery
I simply booted into the CW recovery mode, and then loaded a new ROM from zip
Click to expand...
Click to collapse
Glad your sorted....
Question is basic; can someone with experience please give me the low-down when it comes to TWRP? I am new to Android in the sense but consider myself somewhat tech savvy. I test software and provide technical support for a living so I completely understand that people can do some dumb stuff. Just yesterday I had a man on the phone trying to connect his Pidion PDA to a McDonalds Wi-Fi by standing in his front yard and pointing it in the direction of a McDonalds two miles away. Anyhow I got the device for X-mas and have spent every day since reading about constant issues using TWRP. I’m really just trying to figure out if the blame for these issues can be pinned down on either the recovery itself or the fact that Millions of these things are in the hands of people who should probably not be doing the things they are doing at their current levels of knowledge, or a combination of both? I have owned a Moto-Triumph for a few month and have flashed Roms & Kernels out the Wahoo using CWM and have become very comfortable with its reliability but had not heard of TWRP until a few weeks ago and the association I have goes with all the stuck on Yellow Triangle posts covering just about every forum. I have TWRP installed and running CM7 and if this was my phone I would have flashed 2 Roms by lunch but for the reasons above feel like I should have a day set aside for trouble shooting before considering doing a simple thing like restoring a stock Nandroid. I lucked out with the Phone having an unlocked loader and Sudo installed out the box. Sorry I tend to rant but am basically asking that if I know my way around Roms and CWR will I be OK using TWRP or should I expect that it will have the occasional hiccup or is unstable in any way?
chairshot215 said:
Question is basic; can someone with experience please give me the low-down when it comes to TWRP? I am new to Android in the sense but consider myself somewhat tech savvy. I test software and provide technical support for a living so I completely understand that people can do some dumb stuff. Just yesterday I had a man on the phone trying to connect his Pidion PDA to a McDonalds Wi-Fi by standing in his front yard and pointing it in the direction of a McDonalds two miles away. Anyhow I got the device for X-mas and have spent every day since reading about constant issues using TWRP. I’m really just trying to figure out if the blame for these issues can be pinned down on either the recovery itself or the fact that Millions of these things are in the hands of people who should probably not be doing the things they are doing at their current levels of knowledge, or a combination of both? I have owned a Moto-Triumph for a few month and have flashed Roms & Kernels out the Wahoo using CWM and have become very comfortable with its reliability but had not heard of TWRP until a few weeks ago and the association I have goes with all the stuck on Yellow Triangle posts covering just about every forum. I have TWRP installed and running CM7 and if this was my phone I would have flashed 2 Roms by lunch but for the reasons above feel like I should have a day set aside for trouble shooting before considering doing a simple thing like restoring a stock Nandroid. I lucked out with the Phone having an unlocked loader and Sudo installed out the box. Sorry I tend to rant but am basically asking that if I know my way around Roms and CWR will I be OK using TWRP or should I expect that it will have the occasional hiccup or is unstable in any way?
Click to expand...
Click to collapse
I have had no hiccups or any other problem, backing up. restoring or flashing.
TWRP is awesome, backups and restores work great. The main issues are people getting stuck in fastboot, which is not really a TWRP issue. As long as you follow directions, you should have no issues.
Sent from my Kindle Fire (CM7) using xda premium
borborpa said:
TWRP is awesome, backups and restores work great. The main issues are people getting stuck in fastboot, which is not really a TWRP issue. As long as you follow directions, you should have no issues.
Sent from my Kindle Fire (CM7) using xda premium
Click to expand...
Click to collapse
I feel the same way as the OP. I have cwr on my phone and I have never messed up anything. I have roms backed up and I can always get up and running quickly. I have tried half assed roms just for the heck of it and no problem.
I don't think that TWRP is the same kind of program as CWM. I think it's almost impossible to brick my phone using clockword mod but I don't think the same can be said for TWRP. I have read so many posts with people who have TWRP installed and yet they manage to "brick" their device. I don't know if it's a TWRP issue or that the kindle is very sensitive. Nevertheless, I am not rooting it because of these issues, besides, I like stock (I would love swype, that's about it).
Twrp works great. They forgot to set it to change bootmodes leaving recovery so don't use apps to force into recovery. Just firefirrfire.
Most issues, are user errors. I haven't had one issue, and I test everything!
Sent from my Kindle Fire using xda premium
although I havent had any issues (that I can think of) with twrp, the constant "cannot mount /misc !" really bothers me. twrp is on several devices and from what I understand about it... the dev responsible for twrp being on the kindle fire joined twrp, got it working for the fire, they rolled out twrp 2.0 then he quit the team to make a recovery + app he plans on being paid only. so with that said... who knows if twrp will be maintained for the fire?
I hate to bash on anyones work, I didnt have any problem flashing zips with it. I dont really backup/restore much but the few times I tried, it worked. I really like the fact it can be themed easily
foxdog66 said:
although I havent had any issues (that I can think of) with twrp, the constant "cannot mount /misc !" really bothers me. twrp is on several devices and from what I understand about it... the dev responsible for twrp being on the kindle fire joined twrp, got it working for the fire, they rolled out twrp 2.0 then he quit the team to make a recovery + app he plans on being paid only. so with that said... who knows if twrp will be maintained for the fire?
I hate to bash on anyones work, I didnt have any problem flashing zips with it. I dont really backup/restore much but the few times I tried, it worked. I really like the fact it can be themed easily
Click to expand...
Click to collapse
That's a great concern. Which is why I've been Working with doomlord to bring clockworkmod to our kindle fires. We need support. Twrp does not have that. But it works.
Sent from my Kindle Fire using xda premium
Thanks for the responses; I think my fears stem from unfamiliarity. Like I said above everything was easily with my Triumph, was able to install CWM without Rooting the stock Rom and outside of doing something dumb like frying the CPU always felt comfortable knowing I could easily get back up and running no matter how bad I messed things up. I’m sure I will be fine, just need to get used to doing things a little differently and school myself on ADB and Fastboot and as recommended above avoid any apps or options for rebooting into recovery.
I haven't had any issues with twrp so far. Installing was a little tricky when i got stuck at the yellow triangle but after that everything has been good so far.
I have TWRP on both my kindle fire and my wife's and neither has had a single issue with it. My brother, who is not what I would call tech savvy, installed it onto his just a couple days ago without issue by reading the instructions and multiple threads posted around here without issue. I think a lot of the issues come from people not reading as closely as they should or just from getting overly excited about being stuck in fastboot.
Sent from my MB860 using Tapatalk
I would like to put twrp on my phone. It works great. Half of what cwm does fails on my phone. Twrp works every time. People having issues likely can't follow instructions and don't have the knowledge if adb to fix their mistakes
Sent from my SGH-I897 using xda premium
all win
TWRP is all win. If you follow directions to a T and dont frustrated it will work fine. In alot of ways TWRP is better than CWM.
The TWRP team is maintaining TWRP. Even though the head developer left, If you would have read there tweets they are taking some time off. They Even Had announced a Twrp 3 for release, But for now everything is onhold until the team is better organised.If a developer would contact the team for the source, the xda community can keep it maintained.
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
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.
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)