kk so i put cyans recovery with 1 click root, im familiar with rooting i had a g1, but when i flashed cyans 4.0.1 its been on the android screen for a long itme now and its freezing and reloading ! any thing that i shud do?
I had the same problem. Tried it 2 times ans the third time I whiped it and then it went with no problem.
Related
Well, Please point me in the direction if this has been asked before but search hates me right now.
But the problem is I've recently flash Timolol's Stock Like Rom, and it's a nice rom but I am missing sense so I realise that Cap's ROM had been updated I flashed and it was successful but put me into a reset loop and so I reflash it again and it froze on the boot screen.
So I had the idea of flasing back to the original ROM (Stock like) and it's working okay, Why can't I flash to Cap's Rom again?
I had it on there before I went to try Tim's Rom...
EDIT: Forgot to mention that after both ROM flashes of Cap's I did do a hard reset
Thanks
I managed to fix it, (not quite sure what was wrong with it though)
I did a hard reset before I flashed and again afterwards
Hey there,
I have an interesting problem, and it has completely stumped me for the past couple days. I recently S-Off'd my Sensation, put cwm recovery on it, and set my CID to 11111111.
I haven't had any problems with that (except that I had to change computers to do it, Revolution didn't want to run right on my laptop or set the CID, so I had to use my desktop).
Now the problem comes when I try to flash a custom ROM. The first one I tried flashing was CM7. When it booted, I got a bootloop problem of the CM7 mod logo over and over. I decided maybe it was a problem with CM7 still being in alpha. Then I tried flashing HyperSensation 1.8, and got the same error (bootloop) on the loading screen. After trying various other ROMS, I realized that it was a common problem with all custom ROMS. Luckily I had backed up the stock setup, and was able to get into that. So it's not a problem with the hardware. I have only tried flashing gingerbread ROMS. I know that ICS ROMS need a new firmware, but I dont want to mess with that unless I can actually get a gingerbread ROM working first...
Any ideas? There was a thread or two about this (on other phones) but didn't have any solutions listed..
Thanks for any ideas people can give me!
TheLastGringo said:
Hey there,
I have an interesting problem, and it has completely stumped me for the past couple days. I recently S-Off'd my Sensation, put cwm recovery on it, and set my CID to 11111111.
I haven't had any problems with that (except that I had to change computers to do it, Revolution didn't want to run right on my laptop or set the CID, so I had to use my desktop).
Now the problem comes when I try to flash a custom ROM. The first one I tried flashing was CM7. When it booted, I got a bootloop problem of the CM7 mod logo over and over. I decided maybe it was a problem with CM7 still being in alpha. Then I tried flashing HyperSensation 1.8, and got the same error (bootloop) on the loading screen. After trying various other ROMS, I realized that it was a common problem with all custom ROMS. Luckily I had backed up the stock setup, and was able to get into that. So it's not a problem with the hardware. I have only tried flashing gingerbread ROMS. I know that ICS ROMS need a new firmware, but I dont want to mess with that unless I can actually get a gingerbread ROM working first...
Any ideas? There was a thread or two about this (on other phones) but didn't have any solutions listed..
Thanks for any ideas people can give me!
Click to expand...
Click to collapse
Hi,
Did you root your phone?
Did you flash the superwipe zip first?
Also are you getting full reboots with HTC splash screen then animation or just the animation looping? Sometimes I have to let mine loop for 5 minutes after first boot of new rom before it settles.
Sent from my Sensation XE using XDA App
I guess I hadn't done everything.. I didn't factory reset before flashing the new ROM... As soon as I did that it boot right in. That's a bit odd to me, as I didn't have to do that with my last phone.
Anywho, solved.
Sent from my Sensation using XDA App
Hi all I decided to try and run a custom ics build a couple days ago everything went smoothly, I got the lastest AOKP build running with tastymeh kernel. Well tonight I disabled the boot animations and it seems as though I'm stuck bootlooping into the latest cwm(touch). I've tried reflashing the rom/kernal/wipe dalvik/etc to no avail. And my Nandroid backup isn't showing up to make matters worse. I can't even power down my device it just keeps bootlooping. I was wander what the best method to return to complete stock rom? Thanks everyone
Brand New said:
Hi all I decided to try and run a custom ics build a couple days ago everything went smoothly, I got the lastest AOKP build running with tastymeh kernel. Well tonight I disabled the boot animations and it seems as though I'm stuck bootlooping into the latest cwm(touch). I've tried reflashing the rom/kernal/wipe dalvik/etc to no avail. And my Nandroid backup isn't showing up to make matters worse. I can't even power down my device it just keeps bootlooping. I was wander what the best method to return to complete stock rom? Thanks everyone
Click to expand...
Click to collapse
Go here for instructions on how to fix
http://forum.xda-developers.com/showthread.php?t=1530337
My problem is when I turn on the phone, the Google logo stays stuck and after unknown minutes boots in with the software animation, but very slow! First a little history of my upgrades with this phone.
My friend bought me Nexus S T-mobile version for US 6 mounts ago, and the phone was with Gingerbread 2.3.4. After reading many post from here, I decided to upgrade because I can't upgraded 2.3.6 OTA. After many hours I finally upgraded it to 2.3.6.
Then ICS came out, and again, I upgraded to 4.0.3. Then, a few weeks ago, I got the 4.0.4 OTA notification. Happily I taped yes. And then before two days ago, my phone just died. I don't know how.
I have 115 installed application, no music inside, no ROOT - just pure stock. I was in my college room and I left my phone on the desk right in front of me and after few minutes when I looked at the phone, the Google logo was there. I didn't give the phone to anyone to picks or anything. When I get home, I turn the phone on and still the Google logo just was there doing nothing and like I said before, after unknown minutes the phone boots in with very slow animation of the ICS software. I decided to install Clockwork Mod recovery 5.0.2.0 and root the phone. After reading many tutorials I installed CWM recovery successfully. Then I tried to downgrade to 2.3.4 and successfully I did that to.
Now after doing all this things to this phone, after so many hours in pain, the phone is nothing like one week ago. The booting is very slow, the animation is veryyy slow, and I don't know what to do anymore... I think this is hardware problem.
Please help me solving this problem, I really expect someone here to know what is the problem and will help me in anyway. I'm desperate, and I don't know what to write here to tell you how desperate and sad I am...
Thank you in advance.
p.s. sorry for any grammar mistakes.
http://forum.xda-developers.com/showthread.php?t=1572307&highlight=factory+images
yeah, definitely flash the factory images, you'll have to reflash cwm after though
Do you reboot that often... that this is a problem?
I don't know how much time mine takes to boot... I don't remember the last time I've rebooted it ...
That's why changing boot animations, for me, is stupid... you only get to see them once in 6 months(worst case scenario)?!
muldy said:
Do you reboot that often... that this is a problem?
I don't know how much time mine takes to boot... I don't remember the last time I've rebooted it ...
That's why changing boot animations, for me, is stupid... you only get to see them once in 6 months(worst case scenario)?!
Click to expand...
Click to collapse
not if youre a crackflasher(flash stuff often). i see my boot animation 5+ times daily, if not much more
Yeah.. I forgot that...
When I had the Htc Magic, I used to flash it a LOT
I like Stock, the auto-updates...
dewaffelhaus8 said:
yeah, definitely flash the factory images, you'll have to reflash cwm after though
Click to expand...
Click to collapse
I flash with the official images from here and I reflashed cwm.
muldy said:
Do you reboot that often... that this is a problem?
I don't know how much time mine takes to boot... I don't remember the last time I've rebooted it ...
That's why changing boot animations, for me, is stupid... you only get to see them once in 6 months(worst case scenario)?!
Click to expand...
Click to collapse
I don't reboot that often, my phone itself reboots... I need to fix that problem, the slow booting, restarting, slow software... I need to know is it a hardware problem or software, because I did everything related to software problems...
Okay so i have TWRP 3.0.2.0 modded for multirom and multirom installed on my phone and it was working okay for a long time now all of a sudden my phone randomly reboots and ALL 7 roms in mutli rom boot loop when you try to boot them. so i erased all of them and reflashed the rom, the second i flash anything other than the rom, kernel,mods, stupid files, literally ANYTHING but the rom it bootloops again and it never did this before all of these files worked together before, so i rewrote the twrp and mutlirom and all, figuring maybe that would help, it did not. so i thought okay, fine i will do an RUU and go to stock. it says the firmware is mismatched? so because of S-ON i cant restore to stock now. ( same one ive been using to RUU it for over a year anytime necessary )
literally everything i try i just end up with Bootloops. if i flash ONLY the rom it boots fine but the kernels tend to kill the battery really bad so i usually flashed a custom one and i just dont understand how the same kernel and files ive been using for like the last 8 month now are bootlooping every time. i tried looking for new roms too, nothing works. i also tried plain stock TWRP and no mutlirom, same results, bootloops if anything more than the plain rom is flashed.
also my battery seems to be dying like a rock now, unplugged it and within like 10 min i had lost 18%
universelove said:
Okay so i have TWRP 3.0.2.0 modded for multirom and multirom installed on my phone and it was working okay for a long time now all of a sudden my phone randomly reboots and ALL 7 roms in mutli rom boot loop when you try to boot them. so i erased all of them and reflashed the rom, the second i flash anything other than the rom, kernel,mods, stupid files, literally ANYTHING but the rom it bootloops again and it never did this before all of these files worked together before, so i rewrote the twrp and mutlirom and all, figuring maybe that would help, it did not. so i thought okay, fine i will do an RUU and go to stock. it says the firmware is mismatched? so because of S-ON i cant restore to stock now. ( same one ive been using to RUU it for over a year anytime necessary )
literally everything i try i just end up with Bootloops. if i flash ONLY the rom it boots fine but the kernels tend to kill the battery really bad so i usually flashed a custom one and i just dont understand how the same kernel and files ive been using for like the last 8 month now are bootlooping every time. i tried looking for new roms too, nothing works. i also tried plain stock TWRP and no mutlirom, same results, bootloops if anything more than the plain rom is flashed.
also my battery seems to be dying like a rock now, unplugged it and within like 10 min i had lost 18%
Click to expand...
Click to collapse
Try a different twrp version worked for me awhile ago when I had it
Thank you for the suggestion but as it says above i have tried that. this phone will not let me restore or use anything without google play now so im probably just going to get rid of it or smash it because ive been trying for weeks and NOTHING works.
only android 7+ roms boot, cant RUU, no home button menus, notifications or anything work without google installed so my phone has some weird new firmware on it and is forcing me to use the most up to date android/google play or it just wont work at all.
Update: charger port just quit working, probably burned up from getting so hot with all the battery over use, phone is officially dead now.