Hi!
I'm a noob in all this flashing stuff but i decided to install the miui rom for xperia play (made by a user)and so i followed hus guide by entering cmw recovery ( i installed it with the auto installer app in google play) and then i wiped the chache and the dalvik chache and installer the zip file of the rom that i had on My sdcard,i then press reboot and i'm stuck at the Sony logo.... Please help! Also My model is r800i and i have a Mac but can get to a pc if there are some programs i need... Also when i have My phone turned off and then plug in the charger it boots and come to the same boring Sony logo, no battery thing. Help me please!
Did you make a backup on CWM?
Boot loop isn't being stuck at the SE screen. Boot loop is getting half way through the boot animation, then it freezes and reboots. Sounds like your ****ed. Since you can't go past the SE screen, I don't think you can go into cwn recovery. And you should have installed cwm through here, not Google Play. That's probably what bricked you. If you can, flash stock.
Sent from my locked R800x using XDA Premium
Another thing, what's your version and boot loader status( locked or unlocked )
Sent from my locked R800x using XDA Premium
oggew2 said:
Hi!
I'm a noob in all this flashing stuff but i decided to install the miui rom for xperia play (made by a user)and so i followed hus guide by entering cmw recovery ( i installed it with the auto installer app in google play) and then i wiped the chache and the dalvik chache and installer the zip file of the rom that i had on My sdcard,i then press reboot and i'm stuck at the Sony logo.... Please help! Also My model is r800i and i have a Mac but can get to a pc if there are some programs i need... Also when i have My phone turned off and then plug in the charger it boots and come to the same boring Sony logo, no battery thing. Help me please!
Click to expand...
Click to collapse
Since you installed the recovery through the installer app in the Play Store, I'm going to assume you didn't flash a new kernel, and I'm going to assume that's because you aren't unlocked. I could be wrong, as that's what happens when you assume.
What you're going to need to do, regardless of whether or not you're unlocked, is download a tool called FlashTool (it's a pinned thread in the development forum), the correct .ftf file for your device (a simple search of the development area will show you where to find such files), and reflash your device to stock. When at stock, if your bootloader is unlocked, you'll want to flash the correct kernel using Fastboot, then flash the rom file. If you don't know what Fastboot is, you're most likely not unlocked, and should research these things before you try again.
Related
What I did
1. Install unofficial CMod
2. Installed baconbits
Problem after bacon bits install on unofficial CM: i boot up the phone but it gave me an error/popup for every application i was running "google voice has encountered an error" "com.android has encountered an error" etc etc. endless popups to where i couldnt do anything on the phone other than locking and unlocking it.
what i tried to do to fix it:
3. Wipe data/factory reset
4. Tried applying Stock Recovery, thinking it would somehow help
current problem: stuck at HTC logo
please help! i just want to get it back up and running, any rom... rooted or not. i cant even get into the phone
Wow u really messed up.
Idk how to truly guide u out of this because it seems like u really don't know what ur doing. But your going to have to restore the phone. Read the thread about unrooting and returning to stock.
Also if I'm not mistaking you can fastboot flash system.img and data.img from pc10img.zip but as I said idk 100%
And flashing stock recovery is a no no because it can only read htc zips so it will block you out from flashing a new update.zip
Sent from my T-Mobile G2 using XDA App
Can you get into fastboot? Power the phone down and hold VolDown+Power.
Flashing baconbits over a non-official CM 6.1 was a mistake.... Baconbits is just an addon for a stock rom... CM 6.1 will have everything that baconbits has and more...
yes i can get into fastboot. problem is finding a htc signed rom... i think
If you are still S-OFF, you can flash clockwork mod recovery using fastboot and then just boot into recovery and install whatever rom...
http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.1.2-vision.img
dantheman_ said:
If you are still S-OFF, you can flash clockwork mod recovery using fastboot and then just boot into recovery and install whatever rom...
http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.1.2-vision.img
Click to expand...
Click to collapse
i love you, no homo
just out of curiousity, how did u install that cm rom? if u used clockwork like it required, all u had to do after u messed up flashing bacon, was wipe, and restore, or reflash the rom again. why did u flash a stock recovery?
Sent from my T-Mobile G2 using XDA App
did a wipe, stuck at htc logo. didnt know i could just flash the cm file with clockwork... thought i had to use the clockwork rom manager when the phone is booted up. flash stock recovery, for some reason, i dont know. cried for an hour. called tmobile, had them send me a replacement. now on the phone telling them to cancel first android phone so im a noob, be kind
Ok, here's the quick and the dirty: rooted Dx with bloatware removed. Read that the update won't work if I removed bloatware, so...
1. Downloaded 928droid's back to stock .zip file. Put on SDCARD root
2. Downloaded ROM manager /clockwork to install the ROM. Did not work. Phone rebooted and nothing changed.
3. Tried the update install just in case and it also (still) didn't work.
4. Tried bootstrap, mount and storage, go to format system, mount system = nothing. Phone stuck on M screen after restart.
5. Go into android recovery mode. Try to install 340update.zip (renamed to update,zip), won't work. Phone still stuck on M screen.
6. Tried wipe data cache in recovery mode. Still stuck on M screen
7. Tried restoring factory data. Still stuck on M screen.
Right now, I don't care about the update. I just want my phone working again.
Can someone please help me???
I'm not a super techie but can get through good instructions.
You have to flash an SBF, rdslite 4.8 and the gift 2 or newer... lame bootloader
Sent from my DROIDX using XDA App
I've rooted my phone, and followed these instructions here http://www.addictivetips.com/mobile/install-clockworkmod-recovery-on-samsung-continuum/ to put CWM on and these instructions here http://www.addictivetips.com/mobile/install-dl17-clean-rooted-android-2-1-rom-on-samsung-continuum/ to flash the ROM on. I also added tried adding these test kernels http://forum.xda-developers.com/showthread.php?t=926555 as well.
None of this seems to have stuck. When I reboot the phone after clearing all data and caches in CWM and installing the ROM, it boots up to the standard Samsung Continuum interface. When I go into recovery mode again, it goes back to the standard Android recovery mode instead of CWM. I have also tried CWM manager, but it does not work because the Continuum is not on its list of phones to install the recovery, and because the recovery I manually install does not stick, i can't use the interface to install the rom.
Please, can someone point me in the right direction with what I did wrong/why the ROM does not seem to be working?
Thanks!
May i ask what you mean by, "standard Samsung Continuum interface"? Once you flash a rom, it is definitely going to "stick"... You know that this is just a cleaned up rom, right? no theming or anything? so it is going to look the same (excluding the launcher)...
One thing i can think of is to ake sure that in Mount in CWM that System is mounted, just to make sure..
Also, by following those posts, you SHOULD go to the original recovery screen... Then you need to press "apply:update.zip" or whatever to get into CWM.. if that doesn't work, then do this:
use ODIN to flash the recovery and kernel, and as soon as it is done, hold in the recovery button combination (power, vol up/down)... Sometimes thats the only way to get into it for some people...
Yeah, I just meant cleaned up. When I reboot, my phone still has touchwiz interface, Bing and bloatware. I do use the update.zip to get the CWM recovery screen, which works fine, but when I try to get into the recovery screen again, i have to reload the update file, and when I try to use Rom Manager is says that CWM is not installed.
In CWM, after loading the update file, it says that the three zip files are installed, but when I exit the recovery screen via reboot, the files that were supposedly installed do not take effect.
is "Mount" an option somewhere in the CWM commands?
Yea clockwork recovery won't stick. It's not supposed to. whenever you go into recovery mode you will have to load the update.zip every time. But I have the clean ROM flashed and the peanutbutta jelly time kernel and it's working just like it's supposed to. I think imnuts is working on getting the recovery to stay
Sent from my SCH-I400 using XDA App
i just tried flashing the peanutbutta jelly time kernal and clean DL17 and the two updates, but the phone freaked out after the samsung logo on reboot, scrambling the screen and looking frozen. I pulled the battery and reinstalled adrynalyne's test kernals and but now it is just booting to the regular factory OS.
oh and the system is mounted
After you flash the kernel the boot screen should mess up. It's fine after it boots though
Sent from my SCH-I400
Ok so waited for the phone to boot, but still booting to stock Samsung OS/interface. My flashing in CWM was as follows:
Delete data
Clear cache
Clear davlik
flash peanutbutta
flash DL17
flash email update
flash social app update
reboot
samsung logo, screen messed up but still hearing booting sounds, then finally loads into the stock samsung interface.
What am I doing wrong?
The stock samsung interface WILL remain, aka touch wiz. There will be a couple verizon apps that will remain with this rom. Also what version of cwmr are you using?
oh ok, that would be where the confusion lays. It was my understanding that it was detouchwizzed as well. Does debinging remove bing as the default and only search engine in the browser? is there a mod/ROM that de touchwizzes the continuum?
Also, I feel like this is a stupid question, but if i have this ROM on here, that means I won't be able to get OTA updates, correct?
Correct....
Sent from my SCH-I400 using XDA Premium App
Hello everybody.
I have installed Swiftdroid 2.0 M6 on my GT540.
Today I would like to SIM unlock my phone. But I read that with Swiftdroid we can't access hidden menus needed to unlock the phone.
Does a solution exist to enable hidden menus ?
(Sorry for my bad english)
Mat11
Mat11 said:
Hello everybody.
I have installed Swiftdroid 2.0 M6 on my GT540.
Today I would like to SIM unlock my phone. But I read that with Swiftdroid we can't access hidden menus needed to unlock the phone.
Does a solution exist to enable hidden menus ?
(Sorry for my bad english)
Mat11
Click to expand...
Click to collapse
What i'd recommend is that you go back to 2.1, unlock your phone, and then restore back to 2.3.
Here is a simple way, it also lets you keep all of your 2.3 ROM and Data
Download my 2.1 Recovery Backup from here:
http://forum.xda-developers.com/showthread.php?t=1110537
put the V20Ebackup folder on your SDCard in the: clockworkmod>backup folder.
Boot into recovery (Home+Power) and go to Backup and Restore and press "Backup" let the backup process finish, then go to "restore" and pick the "V20Ebackup" folder let it restore then "Wipe Data/Factory reset" (Don't worry, your data is saved in the backup you made earlier) reboot your phone, and then unlock it. Boot back into recovery and then go to "Backup and Restore" and choose and choose "Restore" choose the one with the latest date, then you will be unlocked and back on 2.3
Hope it helps,
Jack
Thanks for your answer.
So, I need to come in 2.1 version.
But, I can't use the clockwork recovery because I lost it when I did my first update. I can only change my ROM with fastboot.
Is it possible to come back to official LG ROM with fastboot ?
Mat11
Mat11 said:
Thanks for your answer.
So, I need to come in 2.1 version.
But, I can't use the clockwork recovery because I lost it when I did my first update. I can only change my ROM with fastboot.
Is it possible to come back to official LG ROM with fastboot ?
Mat11
Click to expand...
Click to collapse
Just flash recovery again using fastboot or yaffsexpert.
Jack
Sorry I don't explain my problem correctly.
I think the clockwork recovery is well installed, but when I did my first update (2.1 LG official ROM), I lost my boot animation, it's a well known problem, so today I can only change my ROM with fastboot.
So does a solution exist to come back in 2.1 stock ROM ?
Hello everybody,
I tried JackG256's method but when I want to restart with the v20E backup rom, I get a boot loop on the LG logo.
How can I fix this problem ?
Thanks
Mat11
boot into recovery and do a factory reset and also wipe dalvik cache.
Sent from my GT540 using XDA Premium App
eoghan2t7 said:
boot into recovery and do a factory reset and also wipe dalvik cache.
Sent from my GT540 using XDA Premium App
Click to expand...
Click to collapse
I tried these two solutions but I still have a boot loop : LG logo appears and then the phone restarts and again...
Any others ideas ?
Do a full wipe or try different kdz version I went with v20d
Sent from my GT540 using XDA App
The problem always exists, I did a full wipe and it continues to restart after LG's logo, it doesn't want to load the ROM.
I don't understand what is the problem.
I hope someone could help me....
"Have you tried turning it off and on again?" I'm joking. Here's an idea. Try flashing a fastboot rom in download mode(no battery, no sim, nothing - plug in phone holding vol-down) , if you haven't got one already, and then go into fastboot, connect phone and execute "fastboot -w". That should wipe it right up. For the problem with the black screen recovery, and loading see here. I know G translate makes it pretty much gibberish, but it's not that hard to understand. Here are the links to mentioned files:
V20a.kdz
Out.kdz
I hope this helps.
I've fixed the backup, you should be able to restore now, just download the new version.
Jack
I have had my N7 for a week now, and have unlocked and rooted it. I flashed the jr5 rom and it worked ok, but i decided I wanted to try the pure AOSP rom, so I did a data/cache/dalvik wipe and flashed the rom. It proceeded to boot and freeze at the Google screen. I rebooted into recovery, and attempted to restore from my backup (failed), flash the jr5 rom (failed), and reflash the AOSP rom (failed). I then decided to follow the instructions on ROOTZwiki and restore back to stock (although still unlocked). I restored to the factory image, and attempted to flash the CM10 AOKP rom, and was again met with the frozen Google screen. I made sure to wipe data and both caches each time i tried to flash a rom, but I always end up stuck at the Google screen. What could be causing this? I would really like to know if anyone has any idea, because I fully plan on running the full version of CM10 when it is released.
By wipe Data you did factory reset in cwm? And what version of cwm are you using?
Sent from my Nexus 7 using XDA Premium HD app
redmonke255 said:
By wipe Data you did factory reset in cwm? And what version of cwm are you using?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
yes i did a factory data reset each time. I am currently running v5.8.0.2 of cwm
could that be the problem? that my cwm is just outdated already?
No that shouldn't be causing your problems, although I would recommend flashing TWRP recovery through goo manager.
I would first download a ROM on your computer and check the MD5. Then mount your nexus over USB and copy the new ROM over to the nexus sdcard directory and while its connected use your computer to check the MD5 on your ROM while its on the device. Then wipe data, cache, dalvic cache and system. Then install the ROM and Gapps and reboot. Make sure its only the to, and not a desperate kernel or anything for right now. When you reboot give it 10 minutes or so the first boots are often way long.
If that doesn't do it copy the stuff on your SD card over to your computer and then format the SD card.
To install TWRP, install goo manager from the play store, when you open the app just press menu, you don't need to browse for files or anything. Just press menu and then choose Install OpenRecoveryScript and when its done reboot or reboot to recovery, can't remember which did the trick, and it may take a couple of times.
Also remember that booting through boot loader to recovery requires the USB cord to be connected to a computer to avoid the Google screen looping.
Hope some of this was helpful.
Sent from my Nexus 7 using xda premium
CharliesTheMan said:
No that shouldn't be causing your problems, although I would recommend flashing TWRP recovery through goo manager.
I would first download a ROM on your computer and check the MD5. Then mount your nexus over USB and copy the new ROM over to the nexus sdcard directory and while its connected use your computer to check the MD5 on your ROM while its on the device. Then wipe data, cache, dalvic cache and system. Then install the ROM and Gapps and reboot. Make sure its only the to, and not a desperate kernel or anything for right now. When you reboot give it 10 minutes or so the first boots are often way long.
If that doesn't do it copy the stuff on your SD card over to your computer and then format the SD card.
To install TWRP, install goo manager from the play store, when you open the app just press menu, you don't need to browse for files or anything. Just press menu and then choose Install OpenRecoveryScript and when its done reboot or reboot to recovery, can't remember which did the trick, and it may take a couple of times.
Also remember that booting through boot loader to recovery requires the USB cord to be connected to a computer to avoid the Google screen looping.
Hope some of this was helpful.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thank you for taking the time to help me. Before I do the goo-manager/twrp install, are there any inherent advantages or disadvantages of using twrp as opposed to cwm? Also, I hadn't thought to check md5s after moving the roms, so I will be doing that from now on.
Twrp works just fine.
In your recovery, can you mount and unmount all your partitions without any errors?
Sent from my Nexus 7
am I finally doing it right?
I flashed EOS rom from a clean system and it worked fine. Decided to have gapps and installed via twrp. This would give me boot loop into recovery no matter wat combination of cache clearing etc used. So finally I did the counter intuitive and installed gapps zip followed by ROM zip. This seems to have worked though it seems backwards to me. Is this the correct procedure?
crache said:
am I finally doing it right?
I flashed EOS rom from a clean system and it worked fine. Decided to have gapps and installed via twrp. This would give me boot loop into recovery no matter wat combination of cache clearing etc used. So finally I did the counter intuitive and installed gapps zip followed by ROM zip. This seems to have worked though it seems backwards to me. Is this the correct procedure?
Click to expand...
Click to collapse
no. did the rom already come with gapps? the rom would wipe out whatever gapps you did flash before the rom.
simms22 said:
no. did the rom already come with gapps? the rom would wipe out whatever gapps you did flash before the rom.
Click to expand...
Click to collapse
I don't like Twrp not being able to boot into recovery from holding the buttons, especially running into these loops during installs. Had the sameresults with cwm though.Now I am having this boot loop with TeamEOS as well as Skanky (neither package gapps) I however only loop if installing gapps after the rom or wiping caches.
If caches and system are wiped, gapps installed, then the rom I get a functioning system.Can anyone shed some light on what trigers specific loops or how to review tje errors / panics?
I'm reviving this thread since I have a similar issue. I am using TWRP. I have no problem performing a wipe (I do a factory reset, plus dalvik cache wipe), or flashing a new ROM (I've tried SGT7 and PA2.11). I can boot into the ROM fine. Once I try to flash Gapps, I get stuck in a boot loop that ends up going back to recovery. I've tried different combinations of operations, with different versions of gapps, but nothing works. I've tried:
gapps-jb-20120719-signed
gapps-jb-20120726-signed
both from goo.im, MD5 checked, without success. I'm stuck using SGT7, because that one includes Google account, and Play Store, so that can get me going... Only thing, I haven't wiped the data partition, because that's a bigger hassle. Do you guys have any clues as to what I should try next?
spked said:
I'm reviving this thread since I have a similar issue. I am using TWRP. I have no problem performing a wipe (I do a factory reset, plus dalvik cache wipe), or flashing a new ROM (I've tried SGT7 and PA2.11). I can boot into the ROM fine. Once I try to flash Gapps, I get stuck in a boot loop that ends up going back to recovery. I've tried different combinations of operations, with different versions of gapps, but nothing works. I've tried:
gapps-jb-20120719-signed
gapps-jb-20120726-signed
both from goo.im, MD5 checked, without success. I'm stuck using SGT7, because that one includes Google account, and Play Store, so that can get me going... Only thing, I haven't wiped the data partition, because that's a bigger hassle. Do you guys have any clues as to what I should try next?
Click to expand...
Click to collapse
Do you flash the rom and gapps and then reboot, or flash the rom, reboot, then flash gapps?
Did anybody get out of their bootloop? I flashed paranoid droid with twrp and I didn't select "signature verification" or "md5 check" as I read before hand on another forum that it wasn't needed and to actually not tick "signature"....so now I'm in a bootloop, volume buttons and power does get me in to a few selections, "reboot", "power off" and "recovery". When I select recovery it just takes me to the black screen with "Google" on it. No idea how to get out of this loop....I'm researching now but I am not understanding much....I'm so use to Samsung devices, getting out of bootloop with those are a piece of cake, this I'm clueless and helpless on. So does anybody have a way for me to either reflash the rom or get me to where I can go back to stock? I used wugfresh to root. Thanks.
dirtyhamster73 said:
Did anybody get out of their bootloop? I flashed paranoid droid with twrp and I didn't select "signature verification" or "md5 check" as I read before hand on another forum that it wasn't needed and to actually not tick "signature"....so now I'm in a bootloop, volume buttons and power does get me in to a few selections, "reboot", "power off" and "recovery". When I select recovery it just takes me to the black screen with "Google" on it. No idea how to get out of this loop....I'm researching now but I am not understanding much....I'm so use to Samsung devices, getting out of bootloop with those are a piece of cake, this I'm clueless and helpless on. So does anybody have a way for me to either reflash the rom or get me to where I can go back to stock? I used wugfresh to root. Thanks.
Click to expand...
Click to collapse
Can you get to bootloader?
If your using an older version of cwm it will boot loop and or cuase bad flashes with new builds
Upgrade cwm or just use twrp
Sent from my Nexus 7 using Tapatalk 2
Jordanooo said:
Can you get to bootloader?
Click to expand...
Click to collapse
I finally got in, so I'm all set. Thanks! I have no idea why I was having a hard time...twrp wouldn't pop up once I was in boot loader. I must of tried like 20 times. Anyway....I'm in and I just reflashed and it was fine.
---------- Post added at 05:42 PM ---------- Previous post was at 05:40 PM ----------
armyboy11b said:
If your using an older version of cwm it will boot loop and or cuase bad flashes with new builds
Upgrade cwm or just use twrp
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I'm using twrp...for whatever reason I couldn't get it to pop up to reflash. But I'm good now. Thanks!