As above Gents. I was given it as a broken phone. I had a go at it some time ago. Ive put the Clockwork mod recovery on the memory card (which I can get to) and also have flashed a rom but, whenever it reboots it goes straight back to the stock android recovery screen. Does anyone know a fix for this (if there is one)
I thought id revisit it (with the opening of a thread)!
Cheers to anyone that chips in.
Comfy
Same Problem
Im having the same problem too. After i flashed CWM 6.0.5.0 tortoro, it jsut keeps booting into recovery only. Also tried wiping cache, still fails to boot system. Help
Related
Okay I've never read such a weird explanation on any thread in this forum.
Btw, I recently flashed InDroid 4.3. Less than a week ago.
My phone was running perfectly, but my google account linked with my phone was not what I wanted it to be. So I added another account and my phone said that to delete my previous account I had to do a factory reset.
So I deleted my older backup that I had created using Titanium Backup (when I was using stock ROM) and I created a new backup.
So I held down the power button and tried to get into recovery. But my phone just got stuck at the "samsung i5801" screen. I let it be for 10-15 minutes but it won't go beyond that. So I re-inserted the battery, and tried to get into recovery again. Didn't work.
Then I tried to just start my phone in normal mode, but still it just got stuck at the i5801 screen. I removed the sim card, SD card and tried, still stuck at the same screen.
Then I tried to get into downloading mode, which (thank god) worked.
Now I know the logical thing to do is just to flash a new ROM but my questions are :
a- WTF happened?!??!?!?!
b- since I can't get into recovery or normal mode, how do I reset factory settings / clear cache? And if I don't do all that, will flashing be successful? and safe?
btw, I'd like to continue with InDroid until Kyrillos 6.0 is perfectly stable.
-That happens frequently with indroid.. main cause could be the filesystems..
-flash kyrillos v6 its pretty much stable..
-Once you flash a new rom you'll be able to boot into recovery..
-Remove sdcard while flashing once done insert sdcard and wipe data n cache from recovery..
Hi all,
I'm having a little problem. I have researched but everything I've found leads me back to square one...
So I followed this guide to installing CM7 on my M2. Please note that I have in the past successfully rooted my phone, installed the Argenstone ROM and one other basic Great Britain Rom. So I'm not a total nub. However at this stage I have a phone that's is useless to me...
My phone is rooted. I have Droid2Bootstapper installed and I managed to get the CWM 3.X installed. I downloaded the all-in-one.zip file from the CM7 ROM thread (the zip is actually called EndlessCM7-110901-nightly_build.zip - hope that's not an issue?)
I booted into CWM and applied the EndlessCM7-110901-nightly_build.zip and after (without a reboot) wiped everything (I had backed it up previously).
I rebooted the phone and...well I get the Google logo with the Motorola M and the Cyanogen bot as the 2 'O' characters. Then after a while a 3D rotating 'square' and the android writing and logo 'shimmering' in and out but that just goes on forever. I left it for an hour at one point and just gave up.
Now I can't even get past the Google logo. I've tried restoring my previous back up but that won't work either. I can't boot into the OS to actually use RSD lite to flash a known working ROM over the top.
When the LED turns blue and I hit the volume key it displays "Android BootMenu <v1.0.3>" which is different to the CWM 3.X that I was getting prior to applying the EndlessCM7-110901-nightly_build.zip file.
From here I can select to recover the last 'latest recovery' which when done loads into CWM-based Recovery v4.0.1.6-defy.
Basically I'm at this point where I seem to be able to load just about every boot menu under the sun and do everything but actually launch the damn OS.
How can I get out of this hole? Preferably I'd like to get everything back to the stock ROM the phone came with so that I can start from scratch again.
Any bodies help would be more than appreciated.
Cheers,
- Matt
EDIT: I have even used CWM 4.X+ to try and restore the Argenstone ROM. it goes through the whole process of checking the MD5 sums, restoring the system and boot images etc and seems to work without any issues. I then wipe all data and reboot. Nothing - still the same cyanogen Google logo and the only thing I can do is boot into all the CWM menus.
*sigh*
Argh feel like a true idiot now. It took me about an hour of searching earlier but I've only just found/remembered how to get RSD lite to see my phone (pwr+volume+camera) and I'm wiping the whole thing to the factory (vodafone) ROM. Might take the opportunity to take it to Vodafone and tell them it never gets a damn 3G connection lol...provided this flash works (touch wood).
I have been running the kanged builds of CM9 for a while, but it began to get bogged down recently and would freeze up almost daily forcing a hard shutdown and reboot.
Sometime yesterday, it began to boot only into recovery no matter what option I tried in the Cyanoboot menu. From there I tried a factory reset and wipe dalvik to hopefully get back into CM9 and here's where the strangeness really kicked off.
Clockwork (which was running off emmc) would freeze in the middle of the factory reset just like it would when CM9 was running (the graphics would degrade slightly upon inspection of the screen).
So, I grabbed my old sdcard with clockwork recovery on it to boot from sd, and I run into the same problem again. Freezing before a wipe, factory reset, or install from sd can complete.
Now, after each failed attempt in clockwork (sd and emmc) it sticks at a backlit black screen and after a hard shutdown refuses to boot (sd or emmc) for about an hour, only to repeat the madness again.
Does anyone have any ideas what I can try from here or familiar with a similar situation?
My sd clockwork version is 3.2.something and I've also tried 3.0.1.something.
UPDATE: For reasons unknown, my Nook seems to be booting regularly as of this morning. However, I am still unable to get a successful flash out of any rom. The closest I've gotten to success is stuck in a boot loop. I think from here I'll likely be able to figure it out, but just as before...
Any help is welcome and appreciated!
I had the same problem with the black screen when trying to install different roms on mine. I just kept clicking the power button and after a few minutes it would kick back on every time.
There is an entire thread specifically on this
http://forum.xda-developers.com/showthread.php?t=949699
As far as CM9 I can't help you much there. I would just try to install a different rom, and hope that works.
Thanks!
I had seen that thread, but I thought my experience was a different; either way, I've managed past that problem using a method similar to yours.
If this helps any, I have been trying to to 7.2 RC1 for a while as well, but it will not get me any further than the stuck boot screen same as the CM9.
Have you tried to follow the tread on returning it to stock ?? I would reformat and repartition it and return it to stock ... then make sure it runs. After that I would try to reinstall the new roms ...
Just my 2 cents
Tinpau
INFO: I rooted my device last night and installed TWRP using GooManger. I tried tested two different Roms. The first one was Google Edition 4.2.2 - v1.3 & the second was GoldenEye. Both Roms Seem to function properly. My Device is SGH-1337M ROGERS
PROBLEM: When i reset my device, even after a clean install, my device gets stuck during boot. I've tried going into recovery and restoring backups from this point and they all fail. The only possible way to get out of this boot freeze is to Wipe entire internal storage. At that point, the phone will reboot. This does not appear to be a boot loop as It just shows "Samsung Galaxy S4" and won't budge (seems frozen). I have no idea what the issue is but i suspect it may have something to do with the kernels provided with the Roms? Any help would be much appreciated!
Pharonic said:
INFO: I rooted my device last night and installed TWRP using GooManger. I tried tested two different Roms. The first one was Google Edition 4.2.2 - v1.3 & the second was GoldenEye. Both Roms Seem to function properly. My Device is SGH-1337M ROGERS
PROBLEM: When i reset my device, even after a clean install, my device gets stuck during boot. I've tried going into recovery and restoring backups from this point and they all fail. The only possible way to get out of this boot freeze is to Wipe entire internal storage. At that point, the phone will reboot. This does not appear to be a boot loop as It just shows "Samsung Galaxy S4" and won't budge (seems frozen). I have no idea what the issue is but i suspect it may have something to do with the kernels provided with the Roms? Any help would be much appreciated!
Click to expand...
Click to collapse
Which ROMs are you installing? On I337M your best bet is T-Mobile ROMs and Kernels. I have Bell I337M and have no issues.
Pharonic said:
INFO: I rooted my device last night and installed TWRP using GooManger. I tried tested two different Roms. The first one was Google Edition 4.2.2 - v1.3 & the second was GoldenEye. Both Roms Seem to function properly. My Device is SGH-1337M ROGERS
PROBLEM: When i reset my device, even after a clean install, my device gets stuck during boot. I've tried going into recovery and restoring backups from this point and they all fail. The only possible way to get out of this boot freeze is to Wipe entire internal storage. At that point, the phone will reboot. This does not appear to be a boot loop as It just shows "Samsung Galaxy S4" and won't budge (seems frozen). I have no idea what the issue is but i suspect it may have something to do with the kernels provided with the Roms? Any help would be much appreciated!
Click to expand...
Click to collapse
Are you wiping with TWRP? I heard there are issues with using it to wipe and restore or loading a new rom after wipe. Just restore using Odin and then load a new rom (or restore a backup) without wiping. See if that solves your problem of bootlooping
kiru said:
Are you wiping with TWRP? I heard there are issues with using it to wipe and restore or loading a new rom after wipe. Just restore using Odin and then load a new rom (or restore a backup) without wiping. See if that solves your problem of bootlooping
Click to expand...
Click to collapse
i just went through this all last night what a pita , problem is twrp , if you do a full wipe when you type the word yes , you can only bootup 1 time then it gets stuck next time you boot , theres no way to fix it , even going back to old version of twrp wont do it , you have to compleatlly remove root and return to stock , re root and install twrp again , then if your luck your nandropid backup will work , it took me 5 hrs to fuger this all out , stupid twrp drove me nuts .,...
in short , return to stock and reroot , then never do a full wipe where you have to type yes
Pharonic said:
INFO: I rooted my device last night and installed TWRP using GooManger. I tried tested two different Roms. The first one was Google Edition 4.2.2 - v1.3 & the second was GoldenEye. Both Roms Seem to function properly. My Device is SGH-1337M ROGERS
PROBLEM: When i reset my device, even after a clean install, my device gets stuck during boot. I've tried going into recovery and restoring backups from this point and they all fail. The only possible way to get out of this boot freeze is to Wipe entire internal storage. At that point, the phone will reboot. This does not appear to be a boot loop as It just shows "Samsung Galaxy S4" and won't budge (seems frozen). I have no idea what the issue is but i suspect it may have something to do with the kernels provided with the Roms? Any help would be much appreciated!
Click to expand...
Click to collapse
i had the same problem, im with rogers so i downloaded the rogers rom 4.2 and i cant make any phone calls or listen to music or watch videos. my phone came with 4.3 does anyone have any ideas to help me?
I restarted my S4 this evening and now it won't boot past the SAMSUNG logo. I have tried a variety of things to get it going but none have worked.
1) Soft boot
2) Pulled battery and let it sit awhile
3) Tried to boot into Safe Mode (stuck on the same spot with no indication of going into safe mode)
4) Wipe cache from CWM recovery mode
5) Reboot from CWM recovery mode
Everything is pretty well backed up but after looking at my sdcard it appears that my camera reverted to internal memory about a month ago so I am after any ideas to get those images.
My phone is rooted and running an old 4.2.2 stock Android OS with USB debugging enabled. I was wondering if by re-flashing the OS it might fix the boot issue and be able to recover the images. Or maybe even flash CM. Or maybe some other thing. I found something about adb but I don't want to do anything else yet until someone more savvy than me weighs in.
Unless it's a hardware issue, then flashing a ROM might work.
The other option is to try a reflow. Reflow means heating your phone up so that the solder becomes liquid and any cracks in the solder (which can cause a bad contact), or any piece that isn't seated right, will be remedied.
did u tried to flash stock firmware using odin?
Deleted
I got it going. I first spent a number of hours getting to know adb which was a dead end because I couldn't get it to see beyond the base directory. I then just flashed the stock rom and everything was there including things that shouldn't be like apps, contacts and texts. The phone is back exactly where it was before it boot locked without having to mess with a single thing. I am grateful but a bit confused.