i was using Saurom ROM at 1st and it worked perfectly for my galaxy note i717(this was my 1st attempt to root my phone and install a new rom), and i saw a better ics rom ("Onlyone" ics rom) at rootmygalaxynote.com, i flashed the new ics rom into my phone and it stuck at the samsung logo. i tried to re-install the ics rom again and same thing happened. So, i go back to re-install my old Saurom ROM. But when the phone get into the main screen, it is extremely laggy and eventually freeze, most of the cases, the phone reboot itself. i m so scare that the phone is not able to read any rom now. and i am new to smart phone, can any Brother and Sister in this Forum can me get through this? i m so depress
Your issue is you forgot to wipe. No not that kind of wipe. LOL. Go into recovery (CWM) and do a "wipe data/factory reset". Then install the OnlyOne ROM again.
I responded to this thread that you duplicately created in the general section. Fyi don't create two threads in different sections anymore
Sent from my SGH-I717R using XDA
thank you very much for the reply.
Agoattamer said:
Your issue is you forgot to wipe. No not that kind of wipe. LOL. Go into recovery (CWM) and do a "wipe data/factory reset". Then install the OnlyOne ROM again.
Click to expand...
Click to collapse
when i got the cwm recovery, the 1st thing i did was wipe all data and factory reset, and then i also wipe "cashe"<---wrong spelling probably. and then i went install the rom. anything that i have missed? is there any possible data corruption during the download of the OnlyOne ROM?
Data corruption is possible. You may have also downloaded an older version. Download the ROM again from this forum in the Dev section. There is a thread for it. Do your wipes again first. Then install it again. Let it settle before restoring anything. ROM performs well.
Hey
Just remember that when flashing onlyone rom it's sit on the samsung logo for a while its ok for fist time instal of rom as long as samsung logo is flashing ur fine good luck
a250ml said:
when i got the cwm recovery, the 1st thing i did was wipe all data and factory reset, and then i also wipe "cashe"<---wrong spelling probably. and then i went install the rom. anything that i have missed? is there any possible data corruption during the download of the OnlyOne ROM?
Click to expand...
Click to collapse
U should have made a nandroid backup...and its been going around that rom bricks some users ur best bet is fjs or team perfections ucle2 objection rom...appdroid is the man!!
sent from team perfections ics rom
Related
Flashed .3 of Cherry Pi, and get stuck in a bootloop.
According to the first post on the thread, I have everything required.
Went back to my Nandroid backup of CherryBlur 1.4d.
I read one person had the problem and updated his CWM, but I'm already on the latest one from Tenfars thread, from 6/30. Is there another one I didnt see?
Thanks
ydgmms said:
Flashed .3 of Cherry Pi, and get stuck in a bootloop.
According to the first post on the thread, I have everything required.
Went back to my Nandroid backup of CherryBlur 1.4d.
I read one person had the problem and updated his CWM, but I'm already on the latest one from Tenfars thread, from 6/30. Is there another one I didnt see?
Thanks
Click to expand...
Click to collapse
Did you wipe the cache & data?
im having the same problem. just flashed cherryPi and now my phone is stuck in a bootloop. tried factory reset and still doesnt work.
Try to do a full wipe FIRST, then reflash the rom. Also, make sure you're not flashing from Rom Manager. If all else fails, PM the developer and he'll respond (or if he's not signed on try asking some other dev--they really are all eager to offer help, as long as you're patient).
~ Sent from My Unlocked, Rooted, Pie-Crusted Atrix 4g ~
Vangelis13 said:
Did you wipe the cache & data?
Click to expand...
Click to collapse
It was my understanding during the ROM flashing process, it would do all that. I'll try that again though.
Try to do a full wipe FIRST, then reflash the rom. Also, make sure you're not flashing from Rom Manager. If all else fails, PM the developer and he'll respond (or if he's not signed on try asking some other dev--they really are all eager to offer help, as long as you're patient).
~ Sent from My Unlocked, Rooted, Pie-Crusted Atrix 4g ~
Click to expand...
Click to collapse
Flashing from Tenfars CWM. I had wanted to post in the dev thread, but not enough posts yet . Especially since one other person was having this issue...he fixed it by 'updating to latest CWM' .. which I believe I am on.
Thanks. I'll do a full wipe then flash. See if htat helps any.
Coming from captivate, i used to have to one-click back to stock before i could do anything. Do i have to do the same here when going from a AOSP rom to a i777 rom?
FYI whenever i flash I ALWAYS wipe data/cache/dalvik cache (and sometimes battery stats)
Also does any kernel for the i777 work on any rom?
lourivellini said:
Coming from captivate, i used to have to one-click back to stock before i could do anything. Do i have to do the same here when going from a AOSP rom to a i777 rom?
FYI whenever i flash I ALWAYS wipe data/cache/dalvik cache (and sometimes battery stats)
Also does any kernel for the i777 work on any rom?
Click to expand...
Click to collapse
I don't and haven't run into a single problem yet. It takes the long process out of it like we used to have to do on the captivate. uber nice
this phone has different system so you flash from cm7 to a samsung with no issues.
Sent from my SGH-I777 using xda premium
As the above said it is not an issue like we had on the Cappy's. If you made a nandroid backup of any rom you were on (ie: stock rom) then just go to cwm, wipe data/factory reset, then install your nandroid backup. Much easier now. Samsung got smart and changed the partitions so CM7 doesn't have to use mtd partition any longer. So no problem switching back and forth.
Sent From My KickAss ATT SGS2 SPORTING CM7
RockRatt said:
As the above said it is not an issue like we had on the Cappy's. If you made a nandroid backup of any rom you were on (ie: stock rom) then just go to cwm, wipe data/factory reset, then install your nandroid backup. Much easier now. Samsung got smart and changed the partitions so CM7 doesn't have to use mtd partition any longer. So no problem switching back and forth.
Sent From My KickAss ATT SGS2 SPORTING CM7
Click to expand...
Click to collapse
This might seem like a dumb question, but I'm new to this (just flashed UnNamed yesterday). I'd like to try other ROMs too, so all I would need to do is download the .zip file for the ROM, put it on my sd root (like I did UnNamed), go to CWM, do a wipe data/factory reset, then proceed to install the new ROM the same way I installed UnNamed (from CWM)?
If that's correct, that sounds easy enough to switch back and forth.
Indeed. Just be sure to do a backup in cwm in case there are issues with the new rom.
Sent from my páhhōniē
KentuckyHouse said:
This might seem like a dumb question, but I'm new to this (just flashed UnNamed yesterday). I'd like to try other ROMs too, so all I would need to do is download the .zip file for the ROM, put it on my sd root (like I did UnNamed), go to CWM, do a wipe data/factory reset, then proceed to install the new ROM the same way I installed UnNamed (from CWM)?
If that's correct, that sounds easy enough to switch back and forth.
Click to expand...
Click to collapse
Yes. It is that easy. Like above commented on go into cwm recovery, choose backup and restore, choose backup, then it will create a backup of EVERYTHING, your rom, settings, apps, and everything else. So if you don't like the new rom or have an issue with the new rom and want to go back it is as easy as going back to cwm, backup and restore, choose restore, then choose whatever backed up rom/date you want to restore. MAKE SURE TO WIPE DATA/FACTORY RESET BEFORE RESTORING A NANDROID BACKUP.
Sent From My KickAss ATT SGS2 SPORTING CM7
i was using Saurom ROM at 1st and it worked perfectly for my galaxy note i717(this was my 1st attempt to root my phone and install a new rom), and i saw a better ics rom ("Onlyone" ics rom) at rootmygalaxynote.com, i flashed the new ics rom into my phone and it stuck at the samsung logo. i tried to re-install the ics rom again and same thing happened. So, i go back to re-install my old Saurom ROM. But when the phone get into the main screen, it is extremely laggy and eventually freeze, most of the cases, the phone reboot itself. i m so scare that the phone is not able to read any rom now. and i am new to smart phone, can any Brother and Sister in this Forum can me get through this. i m so
You are wiping data cache and dalvik before each flash right?
Sent from my SGH-I717R using XDA
TJBunch1228 said:
You are wiping data cache and dalvik before each flash right?
Sent from my SGH-I717R using XDA
Click to expand...
Click to collapse
^This.
Sounds like you're not wiping properly between flashings.
And don't worry OP. XDA can help you through just about anything!
When flashing a new rom you should being doing the factory reset/data wipe, then wipe cache, wipe dalvik cache. Then flash the rom zip. I would only download roms from the xda post, and the dev usually posts instructions on how to flash it.
To flash the Only1 ICS rom...you must be coming from an earlier ICS build (UCLD3 or UCLC5). If not then this is what you need to do. Flash the UCLE2 leak thru ODIN first. Let it reboot and let it settle for about 5-10 mins. Then Flash CWM via ODIN again. Once that is done...you are ok to flash the Only1 ICS Rom.
You don't have to be coming from ICS to flash OnlyOne. Truth is most Devs have some sort of wipe built in for their ROMs. OnlyOne Dev does not. All you have to do is wipe data/factory reset and then install the OnlyOne ROM. Unless I am wrong, wiping data also wipes cache. Simple as that.
sounds like paranoid anticipation not letting your dv cache and system files build. Since you said both times Samsung logo... I don't think you waited long enough... Plus use flapps first. Then if you wanna have problems to fix, try other roms... In my opinion.
Btw.. Use our development section to get the original content... Not some link from another website redirecting eventually to us anyway.
Sent from my SAMSUNG-SGH-I717 using XDA
I flashed an AOKP Jellybean Rom, just wanting to test it out. After trying another JB Rom, I decided to go back to something more stable. With the release of the Stable CM9 ICS Rom, I figured this was the perfect time to go back.
I factory reset/wiped cache etc, and flashed it. The phone reboots into clockwork mod. Battery pull. Same thing. I then try an ICS Rom I was running for almost a month without issue and the same happend - won't boot.
I then flashed the JB Rom again and it worked like a charm.
Has anyone else experienced this?
does anyone know the solution to get back to an earlier version of android?
Just make nandroid backup if you're not sure you want to keep the rom you're about to flash Restore nandroid if you didn't like the new rom. I use exactly this to go back to stock rom if ever needed. My stock nandroid backup incl. EFS backup is stored safely on different locations just in case
Boot recovery (Hold power, volume up & home), go to "mounts and storage", erase cache, system, data. Go back, go to "advanced", erase dalvic cache. Then flash a new ROM.
McMono said:
I flashed an AOKP Jellybean Rom, just wanting to test it out. After trying another JB Rom, I decided to go back to something more stable. With the release of the Stable CM9 ICS Rom, I figured this was the perfect time to go back.
I factory reset/wiped cache etc, and flashed it. The phone reboots into clockwork mod. Battery pull. Same thing. I then try an ICS Rom I was running for almost a month without issue and the same happend - won't boot.
I then flashed the JB Rom again and it worked like a charm.
Has anyone else experienced this?
does anyone know the solution to get back to an earlier version of android?
Click to expand...
Click to collapse
I have no problem flashing it back to ICS rom. Maybe you missed something. Try again.
Sent from my GT-I9300 using xda app-developers app
Arsaw said:
I have no problem flashing it back to ICS rom. Maybe you missed something. Try again.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
I tried all of the listed suggestions above, and none worked.
But, I finally got it working. For anyone else that runs into this issue in the future:
Perform a restore(doesn't matter how old), do NOT wipe anything, just flash a new rom over it.
Boot. Reboot back into Recovery. Wipe everything and then Flash the desired rom.
Not sure what this fixed, but it did.
Thanks to all for the suggestions!
To make a long story short.
I bought this phone yesterday, dedcided to root, flashed cwm through odin, got a failure so the whole night trying to figure out whats going on and still haven't figured it out yet till now. I kept getting the firmware kies upgrade issue with the yellow triangle.
I posted a help thread on the SGH-1727 section and thats where I also got my guide. The whole time I have been putting in SGH-1727 skyrocket drivers and using odin app for that phone. Since there are a few type of galaxy SII on this forum i got confuse.
My goal is to root the phone, get the nicest JB rom and also a nice kernel which I can port over to this phone. I am not going to even start which best roms or even best kernel,but i just want to get back on track on how to fix my problem first.
As of now im stuck on firmware upgrade kies screen. Which Odin should I use to flash? Should I flash a stock rom first or CWM?
First and foremost: You do NOT flash CWM on this phone, it is included in the custom kernels and each ROM is packaged with one. You can change the kernel afterwards if you so desire. Also, DO NOT use any app labeled CWM or ROM Manager... Just don't. You're likely to create problems for yourself. Nothing against you, it's just the way this phone works.
If you can get back to complete stock, I would do so. After that, read the stickies. After that, read them again. TWICE!
Once you're done with that, use Google to search any questions you may still have. End your search queries with: I777 xda - ALL the information you need is here in these forums and can be found by simply searching. Some things you may have to dig a little, but for the basics, it's easily found.
Trust me, I'm being nice. I'm trying to keep you from being flamed... not guaranteeing its gonna work.
Oh, if you don't find it on these boards, don't use the info.
Clay
Team Pirate
Sent from my Buttery Smooth PINK SGH-i777
clay101eve said:
First and foremost: You do NOT flash CWM on this phone, it is included in the custom kernels and each ROM is packaged with one. You can change the kernel afterwards if you so desire. Also, DO NOT use any app labeled CWM or ROM Manager... Just don't, your likely to create problems for yourself. Nothing against you, it's just the way this phone works.
If you can get back to complete stock, I would do so. After that, read the stickies. After that, read them again. TWICE!
Once you're done with that, use Google to search any questions you may still have. End your search queries with: I777 xda - ALL the information you need is here in these forums and can be found by simply searching. Some things you may have to dig a little, but for the basics, it's easily found.
Trust me, I'm being nice. I'm trying to keep you from being flamed... not guaranteeing its gonna work.
Oh, if you don't find it on these boards, don't use the info.
Clay
Team Pirate
Sent from my Buttery Smooth PINK SGH-i777
Click to expand...
Click to collapse
Well the ODIN 1.85 for the skyrocket stated a failure setup,but after taking the battery out of the download mode and turning it back on i keep getting the kies issue triangle error.
I'll try to go back to stock
Please do some searching for this. If you find ANYTHING with "creepyandcrawly" as the user, read it.
Clay
Team Pirate
Sent from my Buttery Smooth PINK SGH-i777
clay101eve said:
Please do some searching for this. If you find ANYTHING with "creepyandcrawly" as the user, read it.
Clay
Team Pirate
Sent from my Buttery Smooth PINK SGH-i777
Click to expand...
Click to collapse
Lesson learned. I feel bad even one of the people that helped me remote access my laptop to resolved the issue that wasn't resolved.
I managed to go back to stock thanks to creepyncrawler guides. Now basing it off a lot of what I see. This phone has a lot of one click programs. I am so used to HTC builds,but not on Samsung.
I don't even know the first step and there are so much information everywhere on here. Don't know where to start. If someone can guide me and not bag on me telling me I'm lazy and don't what to search stuff please I don't need that.
I just don't want to end up like this guy http://forum.xda-developers.com/showthread.php?t=1757972&page=2
Z33type said:
I managed to go back to stock thanks to creepyncrawler guides. Now basing it off a lot of what I see. This phone has a lot of one click programs. I am so used to HTC builds,but not on Samsung.
I don't even know the first step and there are so much information everywhere on here. Don't know where to start. If someone can guide me and not bag on me telling me I'm lazy and don't what to search stuff please I don't need that.
I just don't want to end up like this guy http://forum.xda-developers.com/showthread.php?t=1757972&page=2
Click to expand...
Click to collapse
That was the only case of confirmed emmc damage that I have seen on this forum. If you want to avoid this possibility, then from stock Gingerbread, which I assume you have if you followed my guide, then flash a custom firmware of your choice. The kernels packaged with the custom firmwares all are safe.
Read and follow the first guide linked in my signature, and you can flash custom firmware without taking weeks to study and learn.
creepyncrawly said:
That was the only case of confirmed emmc damage that I have seen on this forum. If you want to avoid this possibility, then from stock Gingerbread, which I assume you have if you followed my guide, then flash a custom firmware of your choice. The kernels packaged with the custom firmwares all are safe.
Read and follow the first guide linked in my signature, and you can flash custom firmware without taking weeks to study and learn.
Click to expand...
Click to collapse
I'm on my final step flashing a rom. I followed your guide to rooting the phone and flashing a gingebread kernel Siyah 2.6 w/ CWM SUCCESSFULLY!! Now my next question is would I able to flash this super nexus rom with my current kermel or flashing this rom overwrite it and ad their own custom kernel?
You have an awesome write up which took me 2hrs to really read read and read make sure i dont eff up
Z33type said:
I'm on my final step flashing a rom. I followed your guide to rooting the phone and flashing a gingebread kernel Siyah 2.6 w/ CWM SUCCESSFULLY!! Now my next question is would I able to flash this super nexus rom with my current kermel or flashing this rom overwrite it and ad their own custom kernel?
You have an awesome write up which took me 2hrs to really read read and read make sure i dont eff up
Click to expand...
Click to collapse
Kernels are always included when you flash a rom, which you can use to flash any other rom.
Sent from Team Pirate! Using Tapatalk 2
Nick281051 said:
Kernels are always included when you flash a rom, which you can use to flash any other rom.
Sent from Team Pirate! Using Tapatalk 2
Click to expand...
Click to collapse
I did a backup, wipe cache, dalvik cache, flashed super nexus rom and google app like im suppose to, rebooted and now im stuck on the nexus boot screen for more than 10 minutes now.
What am I missing? Should I wipe data/factory reset as well next?
Always follow the OPs instructions for installing their ROM.
Faryaab said:
Requirements:
Clockworkmod Recovery (CWM)/Any custom recovery
Wipe if coming from any other ROM
Instructions:
Copy Google Apps and SuperNexus ROM to your internal SD Card
Enter Recovery
Do a Wipe/Factory Reset (Necessary if coming from a different ROM)
Flash SuperNexus ROM
Flash Google Apps
Reboot your device!
Voila!
Click to expand...
Click to collapse
With that being said, NEVER assume that you will be able to use your phone after a flash. Not trying to deter or scare you, but always have everything backed up and anything you really want off the phone (pics etc.) - Some say a FULL WIPE us need between every flash. I agree. It GREATLY reduces your chance of having a bad flash.
So, in short, yes. You seem to be catching on, but in your spare time read up on some more helpful threads and I think you'll be a flashaholic on your S2 soon enough
Also, this device is vastly different than any other. If you have experience with other phones, that's great, but not always helpful.
Clay
Team Pirate
Sent from my Buttery Smooth PINK SGH-i777
Z33type said:
I did a backup, wipe cache, dalvik cache, flashed super nexus rom and google app like im suppose to, rebooted and now im stuck on the nexus boot screen for more than 10 minutes now.
What am I missing? Should I wipe data/factory reset as well next?
Click to expand...
Click to collapse
Always wipe data/factory reset & wipe cache when flashing a different rom than the one you currently have (sometimes when updating a rom to newer version of the same rom, some say data wipe is not needed). Go back into recovery mode by holding volume - & + and the power button and release when you see the second samsung splash screen. You will be able to wipe data and then reboot into SuperNexus if all goes well, if not then re-flash the rom and gapps. Also to prevent lock-ups on SuperNexus I recommend using Siyah 4.1.4 (in siyah thread) or Siyah 4.1.5 (in the semi thread) for a kernel. To do that just go back to recovery and flash the kernel (wiping cache & dalvik) then reboot. Also SuperNexus comes with ROM manager but do not use it, Siyah will install CWM recovery. These are the steps I followed when doing this on my I777.
You should always full wipe when switching roms. Initial boot can take awhile, though. If you hit 30, re try with full wipe
Sent from my broken screen beast machine
Cmoore0965 said:
You should always full wipe when switching roms. Initial boot can take awhile, though. If you hit 30, re try with full wipe
Sent from my broken screen beast machine
Click to expand...
Click to collapse
U don't have to wait 30 minutes. I've never had a rom take more than 5 to fully boot up. And as stated always wipe data cache and system when coming from a different rom base or upgrading to a new base.
Sent from Team Pirate Headquarters.
30 is just my "****s definitely not happening" cut off. The anticipation of potentially having screwed something up leads me to sweat the boot time. I've had a handful of 10-15 minute boots back during broken ics days. Call it fire and forget stress management lol
Sent from my broken screen beast machine