I've been a stalker on here for a long time, as I've been interested in custom ROMs but I never pulled the trigger, until last night. My Vibrant has served me well for a many years, I bought it shortly after they came out. All I'd ever done to it was network unlock it so I could keep using it after I moved to the UK.
I've been toying with getting a new phone for a few months now so I decided why not try and flash a custom ROM and get ICS on my Vibrant, if I got the EU error and bricked it, oh well, I'd get a new phone. So I after much reading and research, studying the tutorials on here I went for it. I am vary tech and computer savvy. I build my own computers from scratch, I've flashed my routers and set up networks so I was pretty confident I could do this with the help of the forums here.
I've read every thread I can find on the EU on here and I know that the community needs as much info as possible to try and solve this bug, so I will try and be as specific as possible and list everything I did. But bear in mind, I'm new to this and this was my first time doing much of this so some things may be muddled as I was up til quite late messing with all this.
To start my phone was running 2.2 which was updated using Kies Mini. The only thing I'd ever done to it was network unlock, and for that all I did was find the file on the phone with the code and then enter it to unlock.
I decided to follow Woodrube's guide (http://forum.xda-developers.com/showthread.php?t=1464423)
I followed the guide to the "T".
1. Used Odin to flash back to stock 2.1, worked fine, phone booted back up and everything worked. Phone Data showed I was on 2.1.
2. I put Clockwork Recovery downloaded from Woodrube's sig block on my internal sdcard labeled as Update.zip
3. Created a folder called ICS on my internal sdcard. Found and downloaded CM7 from the forums here and dropped it into the ICS folder. Found and downloaded the ICS Passion ROM from the forums and dropped it into the ICS folder
4. Booted to recovery mode and did Reinstall Packages. It ran but brought me back to the blue recovery screen. so per Woodrube's guide I did it again and the second time it brought me to the green CWR recovery screen
5. I did wipe data/ factory reset
6. I did wipe cache
7. I went to advanced and did wipe dalvik cache
8. I went to mounts and storage and did format system
9. I went to install from sdcard and found the ICS folder I made and ran the CM7 fille I dropped there. It worked the first time and booted right up, I let it sit for about 5 mins waiting for the request to install my google password as Woodrube mentions, but it never appeared, so I moved on after 5-6 min of waiting.
10. I then booted back into recovery mode using the extended power button menu
11. I went to install from sdcard again and this time ran the ICS Passion file. It ran some text lines showed on the screen as id did somethings and then I sw a Random Offset error and a small hex string but then it said successfully installed but didn't leave the recovery screen. So i scrolled up to reboot system.
12. The phone rebooted, showed me the Passion splash screens and a progress bar which filled and completed, then showed a few other splash screens and then it booted up showing my signal strength bar and notifications bar. I thought YES! I did it and it worked. then the screen flashed, it showed a single multi-colored line horizontally across the middle of the screen and then flashed again and I was looking at the Encryption Unsuccessful screen.
13. I DID NOT PUSH THE RESET BUTTON, I set the phone aside and followed Woodrube's link to the Captivate Forums and read up on the error, read all of it, then searched the forums for more threads on the error and read all of those, then I Googled the error and read everything else I could find.
14. First i tried just shutting the phone down with the power button and then restarting it. I did this about 5-6 times. Every time it rebooted it showed me the Passion splash screens then boots up shows my notification bar and signal strength meter and the EU screen. That didn't work. I next tried rebooting 5 times without my external sd card installed. Same results
15. Next I decided to see if I had lost access to my internal sdcard as I had read about. I wasn't sure if I had because I had never pushed the EU screen reset button. So I booted into recovery mode, went to install from sdcard and my sdcard list popped up. I still had access to my internal sdcard.
At this point I was torn... do I stop playing with fire and just got back to stock, update with Kies Mini and go back to using the phone as I had always been and forget all this or do I try and figure this out? Well my stubborn side hating to be stumped had encountered a problem and so wanted to move forward... on i went.
16. I decided, ok, I can still see my internal sdcard so why not try reflashing the ISC Passion and see if maybe it will take this time with no EU. I ran it and exactly the same thing happened as the first time.. right down to the flash with the horizontal line and all. (I did not wipe data, cache or anything, just reflashed. Not sure if I should have or not)
17. Back to recovery mode and check... yes still see my internal sdcard. hmmm
18. Decide ok, how about it I do Woodrube's guide all over again from the start? Maybe that will work. I followed the guide again using all the same files and wound up right back at the EU screen again.
19. Hmmm, how about a different ICS ROM? Went and found ICZen and downloaded it. Hmm, how do I get this unto my internal sdcard if the phone won't boot all the way? Booted it back to the EU screen and just plugged the phone into the usb on my computer, windows recognized it, made the device plugged in noise, and both my internal and external sdcards on the phone showed up as drives. Navigated to the ICS folder in the internal sdcard and dropped the ICZen file into it.
20. Rebooted the phone into recovery mode using the power button menu
21. Used install from sdcard and flashed the ICZen. (Again, I didn't wipe anything before hand. Again not sure if I was supposed to)
22. The ROM installed and got stuck in a boot loop. I pulled the battery and rebooted to recovery and reflashed the ICZen again with no wipes. This time it worked and the phone rebooted and I got the ICZen splash screens, then the notification bar and signal strength meter showed up.. and AGAIN the weird flash with the horizontal bar and then the EU screen. SIGH
23. Booted back to recovery mode and checked if I still had access to internal sdcard. yes it was still there.
24. Shut down and booted to download mode and ran Odin and flashed back to stock 2.1
This is where I am now, It was too late to try anything else and my wife was glaring at me to go to bed so shut off the phone and went to bed.
I tried to put everything I did down with as much detail as I could. I'm sure some of you pros out there might be wincing at stuff I did, but again this is all new stuff for me and I'm slowly learning.
If you have any questions or need clarification just ask and I will try and help/explain better.
Hopefully this might help in the quest to solve this bug or it may just be a waste of time to read, dunno.
I got to:
"To start my phone was running 2.2 which was updated using Kies Mini."
and stopped there
Come back to Froyo - always welcome here
Moped_Ryder said:
I got to:
"To start my phone was running 2.2 which was updated using Kies Mini."
and stopped there
Come back to Froyo - always welcome here
Click to expand...
Click to collapse
LOL, yea I know, but up until this adventure last night, I just used the phone with the Samsung updates as it was, didn't really have a need to do otherwise.
I think that you should flash one of Moped's ROMs and make sure that it will boot up and run ok and that you did, in fact get out of the EU bug safely.
Couple of things:
I did get your PM and I thank you for the info. This post is far more detailed, which is a ton better.
You say that you were unlocked. There was a theory not too long ago about a corrupted EFS file, but AdamOutler uploaded his and someone else replaced theirs with it and it didn't work. But I am thinking that there might be a link here bc I have seen several posts over the last few months that ICS ROMs have been out where someone's data has been borked or their IMIE was gone. Wonder if there is a correlation to that? I'll have to ask some people onver in the Captivate thread and if anyone in the Vibrant thread can chime in too(?).
If you want to flash another ROM, just follw my ICS guide but where it says to install CM7, just install your shiny, new 2.2 instead and there you are.
Great Job dodging that bullet and hope that you no longer lurk, but be a part of the community at large. If your intelligence is reflected in your post, you are welcome here anytime.
Thanks Woodrube,
I was thinking the same thing about loading a 2.2 ROM and be sure I'm all good.
I know the 2.1 I loaded last thing last night seemed to work fine. But I will try a 2.2 once I get home and will update on here after I do.
Funny thing about all this is that my wife now won't let me near her Captivate ROFL.
Can you blame her ?
For the sake of the thread i can chime in on the unlock part. I'm still untouched by the EU bug "touching wood(rube)" . I'm using the i896 version of the Captivate from Rogers and there was never codes inside of it so most app were unsuccesfull at pulling them. I had to use the free SGS Unlock website where you upload your nv_data.bin and it returns you a unlocked version. I also never encountered any efs/imei issue.
hi.
I saw you have not wiped when installing the ROMs. I think maybe you should try and do the wipe before installing the ICS ROM.
Wipe system, data, cache.
Good luck
romitkin said:
hi.
I saw you have not wiped when installing the ROMs. I think maybe you should try and do the wipe before installing the ICS ROM.
Wipe system, data, cache.
Good luck
Click to expand...
Click to collapse
BINGO!
So I followed Woodrube's guide again.. started from scratch... only change I made was I wiped data factory reset, wiped cache, wiped Dalvik cache, and under mounts and storage I format system BEFORE flashing the ICS Passion.
Logged into Google Account and set up phone and now I'm rockin' ICS
Not sure how or why this worked but it did.
Thoughts?
Related
Ok i was on ICS passion then all of a sudden my phone said something about encryption an that it had failed an only option was to reset phone so i hit reset then it went to recovery mode an green android came up with chest open then error message happened an so i booted in to recovery then i try to go in sd an it would not allow me to so i then tried to odin an flashed then i powered on it gies to vibrant screen then it just shuts off so i then flashed Eugene froyo that does not brick then it takes me to stock recovery an says an i cant click on anything in recovery can only move -- movi_checking done!...
update media, please wait
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E:copy_dbdata_media:Can't mount SDCARD:
your storage not prepared yet, please use UI me
nu for format and reboot actions.
Here are instructions i have followed an no luck http://forum.xda-developers.com/showthread.php?t=1043892
Ok I think you got some extra cache or some other piece of data that did not get wiped. either way, do this in this sequence and you should be ok
1. Download Eugenes 'Froyo that does not brick' file.
2. Extract the files.
3. Open Odin, plug in your phone, then put it into download mode.
4. load the PIT file in appropriate area.
5. load the .tar file in the PDA area.
6. DO NOT check 're-partition'.
7. Click start, let it finish. Your phone will load and reboot into stock recovery. It will error out again. DONT panic! This is what's supposed to happen.
8. Now, pull your battery.
9. Load the JFD rom for the vibrant'.
10. Extract the files.
11. Once again, open Odin, plug in your phone, put into download mode.
12. Load the PIT file into the appropriate area and the .tar in the PDA area.
13. THIS TIME you want to check the 're-partition' box.
14. Now click start, let it finish, and this time your phone will load up just fine!
15. Then, root the phone and you can flash your new Rom.
doing this method will get everything back to normal and the phone will work just like it did right out of the box
It is #7 that is important when it reboots into recovery after froyo that does not brick then pull the battery and go back into download mode and flash the JFD, This will clear everything out and put you back into stock
Good luck
Got it started
I got it booted though a very hard process an now i cant get my sd card to mount it says when i go into anything media related it says "Your phone does not have a SD card inserted" an Externel dont mount either
Which sd card isnt working... internal sd, or external sd?
kf7strng said:
Which sd card isnt working... internal sd, or external sd?
Click to expand...
Click to collapse
Both of them aren't working
Jasonhunterx said:
Both of them aren't working
Click to expand...
Click to collapse
Don't use eugene's rom, since you were using an ICS rom follow these steps
flash froyo bootloaders
flash regular jfd and TICK REPARTITION ( ICS/CM7/CM9 change the partition layout and you need to flash correct partition table for stock rom to work )
back in bussiness.
http://forum.xda-developers.com/showthread.php?t=848737
jrafael said:
Don't use eugene's rom, since you were using an ICS rom follow these steps
flash froyo bootloaders
flash regular jfd and TICK REPARTITION ( ICS/CM7/CM9 change the partition layout and you need to flash correct partition table for stock rom to work )
back in bussiness.
http://forum.xda-developers.com/showthread.php?t=848737
Click to expand...
Click to collapse
it never booted on Eugene rom it just went to recovery an gave me an error the one time i got it booted was on 2.1 Stock all the phone does is go to vibrant screen then shut down an no boot loop just off it has done this before an i fixed but Sd was not working an first time apps worked but then 2nd time no apps worked besides browser messenger
Jasonhunterx said:
it never booted on Eugene rom it just went to recovery an gave me an error the one time i got it booted was on 2.1 Stock all the phone does is go to vibrant screen then shut down an no boot loop just off it has done this before an i fixed but Sd was not working an first time apps worked but then 2nd time no apps worked besides browser messenger
Click to expand...
Click to collapse
Hey Jason. I'm in the exact situation you're in. Loaded Passion for about 1 week, got the encryption screen and was forced to reset. Now my SD cards (internal and external) won't load. Have you found a work around for it yet? Cheers Mate.
nope nothing
either of you find a solution? Im having same issue
In the same boat
I am in the same boat. I was using the Euphoria ROM. Yesterday things slowed down on the phone. I rebooted a few times and it crashed. The last couple of times it told me about the encrypted data. That was when I tried to take it back to stock and it won't do anything now other than boot to the vibrant logo and shutdown. Searching for a way to odin a ROM/Kernel that has a CWM recovery so I can go in and manually format the SDcard.
Do what I did, sell it to someone as a wifi hotspot and buy yourself a hercules. You'll never look back
Sent from my SAMSUNG-SGH-T989 using XDA
BUMP
BUMP!
I have had a paper weight for three weeks now because of this partition issue.
there has to be a way to fix this.
webstas said:
BUMP!
I have had a paper weight for three weeks now because of this partition issue.
there has to be a way to fix this.
Click to expand...
Click to collapse
Try this one.
http://forum.xda-developers.com/showthread.php?t=1580902
Sent from my Vibrant using Tapatalk 2
Webstas- Just out of curiousity, were you trying to mount your phone to your computer while on ICs when this happened? I have a theory that I believe I know why this is happening. Just need you to see if you remember a few weeks ago and if you had any problems mounting to your PC and then your next reboot you got the Ecnryption Error.
Woodrube said:
Webstas- Just out of curiousity, were you trying to mount your phone to your computer while on ICs when this happened? I have a theory that I believe I know why this is happening. Just need you to see if you remember a few weeks ago and if you had any problems mounting to your PC and then your next reboot you got the Ecnryption Error.
Click to expand...
Click to collapse
no i got up an took a shower then came back it gave me an encryption error then i odin back an more trouble odined a couple more times an now it boot loop an also wont start with eugenes froyo
I know it has been awhile but think back. Were you mounted to your PC at anytime between your last reboot and the Encryption Error? Doesn't have to be right before, the error gets throw on your "next" reboot. And as you know, reboots can happen manually or for something as simple as wrong UV settings.
Looking back in this thread, I saw that you got it to boot up. See if you can do that again and then mount your External via ADB and you should to push the proper commands then. Pretty much your internal is hosed, but me and a few others are working on that too.
Can't get it to boot it makes it to Vibrant screen an shut off an on Eugene"s froyo it gives me a couple of errors an I just can't get it to start anymore it there anyone who has encountered this an got it fixed like I really need this fix I am using a blackberry please save me
YAY
I got it fixed but now im on step 13 of that guide where you have to use ADB an i cant get the phone to show up on my PC what drivers do i need i already have Vibrant drivers but still nothing an the usb works its a samsung USB so can anyone help me with ADB
I am having a similar problem. Was running ICS 4.0.3 w/Euphoria without issue until this morning. Got a couple of errors after a normal recharge. Pulled battery and rebooted, but is stuck in boot loop. Cannot access either recovery or fastboot screen. Vibrant logo flashes and release buttons, but never enters mode. Then cycles to Android screen and would likely stay there until battery died. This is primary phone and need to put back into service quickly. Any assistance will be greatly appreciated. Thanks.
JIM in FLA
Go back to stock 2.1
Sent from my SGH-T959 using XDA
Hi guys. I seem to have outdone myself and am now stuck with a phone that plain refuses to boot any more. Let me give you some history so you get the full story.
Not long after I got my U8800 (18 months ago, 'ish) I decided to change my ROM to MIUI because I wanted to get rid of Froyo and Huawei were being incredibly slow to update officially. I did this with minimal troubles and ran it for a long time, updating etc. as needed to be done. Then along came ICS ports and I admit it, I had to fiddle once more...
I downloaded Aurora and read up in here on how to get it on my phone. It seemed before I did anything I needed to set my phone back to the defaults I had and this involved installing Froyo then the latest stock ROM for the U8800. I did all this without hassle and then tried to get the ICS on.
I don't know if it was me, bad reading, something built into the new stock ROM or what, but I could not get the ICS ROM on my phone no matter what I tried. It seemed to have issues deciding if it was rooted or not, it said it was but then failed to work when I needed it to, plus CWM Recovery completely failed to work for me and I just kept getting the stock recovery when trying to boot into it. ROM Manager was also being a pain and kept insisting my phone was a U8160 when previously it had worked as a U8800 (I may have flashed to the U8160 and having thought this I assumed this was my mistake).
I tried various methods of getting to my cust_ folders and manually changing the recovery.img but everything I tried ran into the same "is it or isn't it rooted" problem.
At this point I gave up and stayed with the official stock ROM from Huawei for a bit.
Two days ago I decided I couldn't hack the defaults any more, my phone was slower and I missed the MIUI way of doing things. I decided to have another go!
Ok, we are up to date, thanks for reading so far if you have.
I decided to try getting to the recovery.img again by doing the pink screen and connecting to my PC, problem was when I did this nothing ever showed on my PC, so I looked for other methods.
I uninstalled ROM Manager, because it still insisted I had the wrong phone and found the app, Root Explorer, it worked! Wish I'd have found it weeks ago. I instantly had access to the folders I needed and could mount them etc to overwrite/backup my recovery.img and as I was a little worried about the rooting thing again, despite Root Explorer working I though what harm can it do to overwrite the boot.img too. I did both by copying the originals to my SD Card and pasting the new ones that I had previously placed on my SD Card through the USB connection. I used the files recommended here: http://android.modaco.com/topic/340...-and-then-some-for-the-huawei-u8800-ideos-x5/ and here: http://forum.xda-developers.com/showthread.php?p=14870348
I rebooted the phone and again failed to get into CWM Recovery, just the default Android one.
I then hunted down another recovery and found this: http://www.androidxpert.com/2011/08...k-work-mod-recovery-on-huawei-u8800-ideos-x5/
It worked! I could finally get into CWM Recovery and figured I was home free.
Not so
I then downloaded the same stockwell MIUI I had used previously as I knew that worked, his latest stable version, and dropped the zip on my SD Card. Went to install it and found that CWM Recovery refused to mount my SD Card (16 gig sandisc). Tried a couple more times because I had issues with this card before and then the card ended up corrupted or something because it just refused to work now on anything I had. This was fairly major because I had backed up to this SD Card and forgot to take the backup off and into my PC for safer storage... I know... I do have the back up of recovery and boot.img though on my PC.
It was at this point I noticed I had a boot loop but could still get into CWM Recovery.
Not panicking too much, I tried my old 4gig SD Card, it mounted! I copied the MIUI Rom across to this card, booted into recovery and selected it. It stated it was installing etc but seemed to go pretty quickly. It said it was done so I rebooted as is the norm. Boot Loop. Damnit! Tried this a couple more times, made sure I once again wiped cache, dalvik etc, all of the things it states to do on the ultimate guides etc. Nothing.
Again, still not panicking I thought, fine, I will go back to stock rom. Downloaded the correct one, dropped dload into root, booted using vol + and - and up comes the unpacking screen. Trouble is it refuses to unpack. I quickly look on the net and find that some say if you take the battery out and connect just using the USB it will install it that way, maybe it does for them but it doesn't for me, it just boot loops again.
I am now at my wits end.
I have the feeling its something to do with my changing of the boot.img and I have the original should it be that but I cannot access the insides of my phone through Windows to change anything, plus of course I can't boot the phone due to the loop to change it back using Root Explorer (otherwise it would work anyway).
Is there anything you guys can help me with?
I can install Linux if needed, I read that it lets you view the phones file system better compared to Windows and with my slight knowledge of Linux Id quite expect this but even so, I am not sure what to do.
Any advice/solutions are extremely welcome.
Sorry for the long post, figured I should give as much info as possible.
So what was the latest Huawei official firmware you had on your phone?
What version of CWM are you trying to use?
What version of the huawei official rom did you have on the phone when you tried to install aurora?
What was the last huawei stock rom you tried to install?
Try and get a 2.2 froyo stock rom and flash it using the vol+and- method. This should hopefully get your pink screen back and access to recovery and boot.img. You can then use any recovery earlier then 5.0.2.6 and install stockwells miui.
It sounds like you have a Gingerbread based official rom flashed which you would have needed to flash aurora and are dropping bits into it like boot.img, roms and recoveries which are for froyo.
If this is the case and you can still get into recovery, I would try flash another rom like sbasils miui or wipe everything and format /system and then flash aurora again.
Ok, not sure what changed but, I figured whilst I wait for a reply I may as well keep playing and try to fix it myself still. So I stick my battery back in, was out all night, plug it in the USB as I wasn't sure what juice it had left and turn it on with vol + and - down for that one last try at the default install.
It starts unpacking!
I have no idea what changed, I did nothing different bar having left the battery out all night. Can it have had something in the residual memory?
Anyway, short version. Installed the default froyo, updated to the beta gingerbread (stock and latest).
Back up everything to internal storage this time, just incase and went to superclick to see if I could root it again, it did so. Used Root Explorer to copy CWM Recovery.img over, backed up it all again using CWM to internal, rebooted, worked.
At this point I got silly again and having it all backed up a few ways now decided to try Aurora again, 2.4 this time. It works.
Again, no idea what changed but its going again and after an initial mess with the SC Card again, that works too now.
Sorry to have wasted any ones time with this, though I still really appreciate the reply even if it seems to have fixed itself.
I just wish I was sure what fixed it so It could help others who have the same issue, unfortunately I don't
great stuff, seems upgrades are just a bit hit and miss on this phone. glad it all worked out.
A story you might find some useful morsels in . If you are impatient, yes, a happy ending.
Monday night I opened the case on my tablet and it was booting. I figured that was strange and after a few minutes realized it was just stuck booting. So I rebooted it. Came up... and then suddenly during the everything loading up phase, rebooted. This repeated several more times.
Uh oh. Working quickly between boots I unset the default on Apex launcher (since it updates frequently) and turned off the live wallpaper. I also shut off Wifi. No effect.
Next stop recovery. Cleared caches, etc. Nope. I had a fairly recent backup but took another one and it worked (whew). Decided that I would do a data wipe from recovery. Uh oh. Any attempt to format /data causes a crash.
I go to Odin to see if I can repartition flash. I can't find a PIT file for the P5113 but did find one for a 16K 7 inch model. Odin repartitioned it but still no joy. Wiping data causes a reboot. So does trying to restore a backup to /data.
Next stop Kies. You can tell it to reload firmware but you need your serial number which is written on the back of your tab (yes it is, it is about the height of a carbon atom). However, it asks you to enter "recovery" mode by pressing buttons that aren't on the tablet. I tried Odin mode but it couldn't connect. Using CWM recovery didn't work either.
So I decided I needed stock recovery. I could not find a P5113 stock recovery that wasn't bundled with an entire update package. So I unpacked an update package to get recovery.img. Flash_image didn't work (seems like it never works on this tablet, and now that I think about it, I think I wrote a thread on how to do it with dd that I forgot about last night! Duh: http://forum.xda-developers.com/showpost.php?p=31293383&postcount=32). Instead, I repacked just recovery.img with tar. Odin was able to flash this and I was back in the ugly stock recovery.
I never did try Kies though because I asked the stock recovery to reformat /data and it worked! Back to Odin to reflash CWM and then the backup I made Monday night rolled back on and I was back in business.
Restore my screen saver, redefault (is that a word?) Apex, and turn Wifi back on. Oh yeah, and run Triangle Away
So I'm not sure what to make of all this. Open questions:
1) Did I need to repartition? What's the right PIT file to use? I sure wish Odin could dump a clean image, but if it can, I don't know how.
2) What mode does Kies want? This could have been a VirtualBox problem but I got it to work before I got Kies installed on my wife's real Windows box (man Kies is slow!).
3) Why could stock recovery reformat /data but CWM could not?
4) Would it have been sufficient to just reflash the stock recovery, do the data wipe? I suspect so, but don't know.
Anyway.... things are back to normal. Love the tab, but sure wish these big companies wouldn't assume we don't know how to fix our own stuff and muck things up with "simplified" tools. By the way, this is the "touch" CWM that seemed to fail to fix /data. I did not try the normal one.
wd5gnr said:
A story you might find some useful morsels in . If you are impatient, yes, a happy ending.
Monday night I opened the case on my tablet and it was booting. I figured that was strange and after a few minutes realized it was just stuck booting. So I rebooted it. Came up... and then suddenly during the everything loading up phase, rebooted. This repeated several more times.
Click to expand...
Click to collapse
Here we go again. Same problem but I'm not even getting into the boot. Does anyone know how to actually reformat and rescan flash for bad blocks? I have a feeling I have a bad flash block that is doing something evil.
Sigh.
Tried a different approach this time.
Booted to recovery and did an fsck on /data since it seemed to have the problem.
It did a lot of clean up and now I'm back up. Not sure what got damaged if anything though. Time will tell.
Good to hear that it is a happy ending, bro!
Sent from my AT1S0 using xda app-developers app
Can someone please help me? I have a Samsung focus that was recently acting up.. Games wouldn't open etc.. so I decided to reset it.. After I reset it.. Its now stuck at the Samsung logo after resetting.. I am guessing that I need to reflash it.. If so, I need to make sure my battery isn't dead. Does the Phone charge while showing the Samsung boot logo?? Help Please..
I dont have a focus but with a Google search looks bout the same as I wud do on my epic ..found this if it helps http://forums.androidcentral.com/dr...ks/130642-help-stuck-samsung-boot-screen.html
Alright, heres what I did.1. Rebooted in*CWM2. Wiped data/factory reset3. Wiped cache partition4. Wiped dalvik cacheAt this point I couldn't reflash because I forgot I couldn't access my SD card, I kept getting the "e:can't mount /sdcard" message whenver I went to install zip from sd card.5. Took off the back and pooped out the SD card and put it right back in. Seemed to work6. Flashed 2.07. Flashed kejar's sd card fix8. Rebooted through*CWMPhone starts up, do all the set up stuff, but still can't access my sd card or anything. Booted back into*CWM*just to see and was getting the "e:can't mount /sdcard" error again and couldnt reflash anything, so back to step 1.Here's a list of other things I have done since the original crap out a few days ago that might be affecting this.*1. Yesterday I tried reflashing 2.0 and it seemed to be boot looping again. So I just wiped data and cache partition and flashed 1.9.1 that I had on my SD card. Was having the same problems so that was the only time I tried it. Not sure if built in kernels might affect anything or whatever.2. After it seemed like I had a stable 2.0 again last night. I flashed blue*CWM*because I've had yellow this whole time. I also flashed EP1 radios through ODIN because I was planning on going to GG 2.1 (I was following your video dave! its awesome btw*).I'm not sure at what point I lost access to my SD card. Ive read a lot this morning about voodoo lag fix affecting things. Could this be a problem with what I've done?
Sent from my SPH-D710 using Tapatalk 2
jpeclf said:
I dont have a focus but with a Google search looks bout the same as I wud do on my epic ..found this if it helps http://forums.androidcentral.com/dr...ks/130642-help-stuck-samsung-boot-screen.html
Alright, heres what I did.1. Rebooted in*CWM2. Wiped data/factory reset3. Wiped cache partition4. Wiped dalvik cacheAt this point I couldn't reflash because I forgot I couldn't access my SD card, I kept getting the "e:can't mount /sdcard" message whenver I went to install zip from sd card.5. Took off the back and pooped out the SD card and put it right back in. Seemed to work6. Flashed 2.07. Flashed kejar's sd card fix8. Rebooted through*CWMPhone starts up, do all the set up stuff, but still can't access my sd card or anything. Booted back into*CWM*just to see and was getting the "e:can't mount /sdcard" error again and couldnt reflash anything, so back to step 1.Here's a list of other things I have done since the original crap out a few days ago that might be affecting this.*1. Yesterday I tried reflashing 2.0 and it seemed to be boot looping again. So I just wiped data and cache partition and flashed 1.9.1 that I had on my SD card. Was having the same problems so that was the only time I tried it. Not sure if built in kernels might affect anything or whatever.2. After it seemed like I had a stable 2.0 again last night. I flashed blue*CWM*because I've had yellow this whole time. I also flashed EP1 radios through ODIN because I was planning on going to GG 2.1 (I was following your video dave! its awesome btw*).I'm not sure at what point I lost access to my SD card. Ive read a lot this morning about voodoo lag fix affecting things. Could this be a problem with what I've done?
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for your help but seeing as your phone is an Android phone, I don't think the same process applies. But thanks for the effort, I have this baby up and running now.. I just had to reflash the ROM.. Thanks again :good:
FocusHelp said:
Can someone please help me? I have a Samsung focus that was recently acting up.. Games wouldn't open etc.. so I decided to reset it.. After I reset it.. Its now stuck at the Samsung logo after resetting.. I am guessing that I need to reflash it.. If so, I need to make sure my battery isn't dead. Does the Phone charge while showing the Samsung boot logo?? Help Please..
Click to expand...
Click to collapse
If you have decided to reflash then use ROM provided by 'voluptuary' (3.10a). And moreover, to flash, it would not matter if your battery is getting charged. Just plug the device to your PC using the USB cable and flash the device.
Be VERY sure you flash the correct ROM for your phone. If you have a version 1.3, then ONLY flash 1.3 ROMs to it. If you have a version 1.4, then ONLY flash 1.4 ROMs to it. You can find the version number under the battery on the sticker. If you flash the wrong version of ROM to it, you will end up with a brick.
When having problems like this, I would recommend flashing the Stock ROM to it first to set everything back to normal. Then, if that works fine, go to custom ROMs if desired. Stock flashing will replace everything back to new settings, including spl, radio, etc... Some of the custom ROMs are truly worth flashing, FASTER, stable, nice features.
Unokashi01 said:
If you have decided to reflash then use ROM provided by 'voluptuary' (3.10a). And moreover, to flash, it would not matter if your battery is getting charged. Just plug the device to your PC using the USB cable and flash the device.
Click to expand...
Click to collapse
I know I had 3.05a and reflashed 3.10a Clean Rom.. It works great now... I remember I use to have problems with the 3g but not after reflashing it works great
This is my first time posting a thread, so I'm very sorry if its in the wrong place.
I've had my Nexus 4 for over a year now and over the past 1-2 weeks it has kept on randomly rebooting and freezing, so I decided to install a custom rom on it (prior to this I had not modified my phone in any way), this was something which i've wanted to do for a long time.
The last time I installed a custom rom and rooted a phone was on the samsung galaxy ace around 2-3 years ago.
the first thing I did was backup the data which I needed. Then I turned on USB debugging and unlocked my bootloader and rooted my phone (my phone is running android 4.4.2) this all went without a hitch. I turned on my phone and superuser ( the version of superuser was chainfire's 0.99) was there. Then I downloaded Paranoid Android, it was the third one down in the mako section of paranoid android. Then I downloaded gapps.
I watched a tutorial on how to flash a rom via cwm but the tutorial forgot to mention making a backup, and me being a bit of a noob it didn't occur to me. When I was installing Paranoid android it said something like "no folder context" and then it said installation aborted ( I had done a factory reset,wiped dalvik cache and wiped cache) gapps installed perfectly but my phone was now in a bootloop. It would turn on and get to the Google logo, where it would stay for a few minutes and then turn off again and do the whole thing again or it would turn on and go straight to cwm.
then I read a tutorial on how to flash the stock rom and followed it word for word but that ended up unmounting my sd card.
Then I read this tutorial:http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312 and made sure I followed it word for word but at one point it said that there wasnt enough space but the installation still finished but did nothing, I tried again today with my phone in safe boot mode ( the one where you press volume down and power together) and it was all going fine until I got to step D.9 (fastboot flash system system.img) at this point my computer froze and cmd stopped working, I could not type anything into it even when my PC unfroze.
I tried this tutorial a number of times before and sometimes it would fail on some parts and keep going and on others it would fail and then say press any key to exit.
I hope I've provided enough information here and would be extremely grateful if someone would help me out as I really need my phone because I have exams coming up and i use my phone to plan my revision and to talk to people about the work etc. If anyone can help, please do, thank you very much for reading.
Have a look at these to put the rom in the sdcard partition and then flash it by recovery
http://forum.xda-developers.com/showthread.php?t=1392310
http://forum.xda-developers.com/galaxy-nexus/help/files-to-sd-card-fastboot-mode-t1542980
Sent from my Nexus 4 using Tapatalk