Related
This may "wreak of non-search" and I am sorry if it does. While I have searched, the overall panic that one experiences when you suspect a brick and cannot afford to have a brick.... (that, plus a friend purchased this Glacier for me to help me get back on my feet with respect to career/employment, etc., so a good amount of guilt is thrown into this mix)... all prevents me from rationally and methodically searching thread after thread to figure out why I am having the problem I am having.
I will be as precise as possible.
1. Back in Feb., I perm rooted with visionary... then about 2 weeks later, I read that this root was not true radio s=off perm root, so I used adb and the scripts to perm root again--using the wiki as a guide. Saved a copy of the partition 7 bin on my laptop as an added precaution. Also, BTW, I never flashed the engineering HBOOT. It didn't seem essential to do so... PLUS, in almost every guide it warned that this was the most likely chance for one to f*ck up and brick, so in the interest of erring on the side of caution, I skipped that.
2. I kept stock ROM for several weeks after that... just enjoying root and freezing bloatware with Ti, and doing other root-enabled mods... nothing too involved.
3. About 1 week ago, I finally decided to flash my ROM. I had Rom Manager (paid version), and had flashed ClockworkMod Recovery 3.0.0.5. Further, as an FYI, I had/have numerous nandroid backups on the SD, plus several Ti backups of apps/data... even sync'd this with dropbox, so I can access those now (which are not of any help obviously).
4. I first flashed a CM7 nightly build--wiped data and cache, and as far as I know followed the guides precisely. All was well...new ROM worked alright... some bugs, but it was nice to have the new features, etc.. And of course the mental gratification of having 2.3.3 (GB) instead of 2.2.1 (boring old froyo). I updated the nightly maybe 2 times... in each case, I simply flashed without backing up those ROMS or wiping data/cache as they didn't seem necessary, plus I still had all my stock rom nandroid backups on the SD.
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Since I cannot get into the phone... I am of course panicked... I have ADB on my laptop if needed, but I really am at a loss as to why this happened, and what I can do at this point....
Please, please advise. My utmost appreciation and sincerest gratitude in advance for any assistance.
Thank you!!!
syntropic
syntropic said:
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Click to expand...
Click to collapse
Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
should come up to a white screen.
take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Sent from my HTC Glacier using XDA App
Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
Click to expand...
Click to collapse
No... that is what I meant when I said tried to "boot into recovery". And I got the 3 vibrate alerts and a blank screen, and nothing........
take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Click to expand...
Click to collapse
Will do... Thank you. DO you have any idea of where I f*cked up here??
Could be a number of things. Like wipe didn't go through completely , bad download, or just random crap out like a few others. Even flashing with the wrong cwr version can less to your issues. Lol like I said could be a number of things. Sorry I couldn't be more helpful.
Sent from my HTC Glacier using XDA App
OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....
I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Sent from my HTC Glacier using XDA App
syntropic said:
OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....
Click to expand...
Click to collapse
What recovery are you using? 3.0.0.5? and you're trying to flash a 2.2 ROM. Thats where the problem lies. See my post regarding this. It's in my signature, the green one.
I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Click to expand...
Click to collapse
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
EDIT: MUSTKll20... Well, you were right... This is not ROM specific. I tried Re-Flashing RC3, which previously worked fine. Now, since I have CWModRec 3.0.0.5, I need to use a 2.3 ROM.... So I thought I would start with this idea. So, I guess, I need to get whatever is corrupt deleted... So my only question thus remains: How do I wipe everything except the SD from within CWR?
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!
syntropic said:
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!
Click to expand...
Click to collapse
You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
and android phone have a method of using a section of the SD card for their memory banks. I'm not really sure how it works either, but it does. You can wipe the internal w/o wiping the SDcard.
Wiping the phone from with in the recovery image will not touch the SDcard, it will only wipe the internal. You can format the SD card from the Recovery Image, but i'll leave that dog sleep so we do not it accidentally.
last little clean-up question.
Sorry to bump this... last LAST question...
Mustkll20: I realized that you were correct to suggest to wipe everything except the SD... Something is corrupt.
But I am not real sure exactly how to wipe EVERYTHING except the SD, from within CW recovery... Since that is the only mode I have available to me. Once I wipe, I will reinstall CM RC3, then update Clockworkmod Recovery to 3.0.0.6, and then try and download RC4 again using another method, and re-flashing.
I would trial and error this, but do not want to wipe the SD.
Thanks guys... seriously.
You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
Click to expand...
Click to collapse
I didn't see your reply... ummm. and I do need to wipe.. Because I have tried to re-flash both RC3 and RC4, and I get what must be a "bootloop": During the CM splash, it stops and then reboots---over and over. It never did that before.... so my problem is something else...
I don't know what else there is besides the SD and the ROM, but whatever it is, I need to delete it. So should I do a factory reset???
Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.
lowandbehold said:
Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.
Click to expand...
Click to collapse
Yep... I know the thread is not for thrillseekers (i.e., its boring), but I mention that I discovered this phenomenon... so I really wasn't in all that bad a spot to begin with.
I still need to figure out how to fix my current problem.... all CM RCs (I can only flash 2.3 ROMs because of CW 3.0.0.5) go into what I guess is a bootloop. In other words, they do not ever boot, just crash and restart. And the RC3 ROM I used worked fine before this... so something else is causing this problem. I need to wipe everything I guess, but I just don't know how... without touching the SD card and from within Clockwork Recovery.
Ok. Go into recovery.
1. Wipe data/factory reset
2. wipe cache partition
Both of these are on the main screen.
Go to advanced
3. Wipe Davlik Cache
Go back to main screen
Go into mounts and storage
4. format boot
5. format system
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.
lowandbehold said:
Ok. Go into recovery.
{...}
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.
Click to expand...
Click to collapse
Thank you for the concise and thorough response!!!!!!! Id thank you, but have used up my allotment. get ya tommorow!!
And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?
syntropic said:
And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?
Click to expand...
Click to collapse
You can thank the Google c&d order for that. Go to cyanogenmod.com. there is a link there for the gapps zip.
Sent from my HTC Glacier using XDA App
OK... I thoght Gapps.zip was just Google Docs. Luckily, I had that on my SD card from one of my many ROM downloads. I see why they had to make it separate.
But I am installing it, and everything is great... And I learned a lot too... Which can only mean trouble.
Thanks!
I have a (TMO) Vibrant & Rooted with super one click. Installed ROM Manager/Flashed CWM. Made a backup & Have been trying to install multiple ROMs.
I have had no luck. When I boot into Recovery it shows options of :
Reboot now
Reinstall Packages
Then delete/clear options.
I have clicked reinstall and it just keeps going back to the same screen after loading about 1/4 of the way. SO after trying about 6x in a row. I reboot and read some more. No luck. Am I missing glaring step or what? Also the bottom reads : a problem with verification signature. My phone reboot fine? I put the ROM my internal & external SD cards trying it both ways. Any help would be great.
Be gentle.
Sounds like you need to get the 2e recovery. Check the Bible for modified recovery
Sent from my SGH-T959 using xda premium
How do i install the 3e recovery? its not doing anything different. I have on my internal sdcard
http://forum.xda-developers.com/showthread.php?t=925400
follow EVERY step
the problem is the 3e recovery. You can follow the above link as a guide.
I personally prefer to odin to jfd (2.1)... it has the 2e recovery. You can then root and flash very easily. Check that link and my signature. Either way should work.
The bottom line is, you WILL be having to ODIN back at some point during your flashing career; and the sooner you do it, the better off you are. I would flash back to stock 2.1 with ODIN and root from there. Trust me..
I don't know about odin, I haven't had to yet do that after rooting, flashing bionix 1.3.1 then going to bi-winning 3 then back to bionix. However, I do know I had the same p.i.t.a. process to get CWM to work. I will tell you though, once you get it working, it stays working, so you only have to go thru the whole process once.
I've been there, and i can tell you it's frustrating, but the reward is worth it.
Well, I used 3e Recovery & it installed no problem...then I tried to flash AOSP No Frills and it was installing......Became stuck in Boot Loop with Vibrant screen & Red ??Glitch?? screen. Tried to restore. no luck. Pulled Battery & phone froze on non-moving circular pattern.
Flashed Odin with battery pulled then installed battery with volume buttons held in. I flashed it after getting the downloading screen. After about 5 tries it work. im back at stock eclair 2.1update1.
So you guys are say i should keep 2.1 / reinstall rom manager/titanium/supermanager/ make a backup then try and flash a rom.
use 2e instead of 3e recovery?
I was a little nervous at first, but XDA forums came to the rescue. I just kept reading and followed instructions from past posts. Thanks to everyone.
Well i followed the NOOB GUIDE & used manual management to install ROM. So far so good...let it set in for 10 minutes. I flashed Trigger 3.2 Final . I think messing up the first time helped me learn more & become less nervous. Waiting.....finally..Working great! Thanks again to all the XDA resources.
ok so after 3 days of trying, i keep getting stuck on a boot-loop I am asking for some help.
before I begin, I have successfully rooted and installed cm7 on 2 nooks that came factory 1.2,I have searched google and these forums but can't find anything with my specific needs.
I have followed the directions on this thread to a tee:
http://forum.xda-developers.com/showthread.php?t=1054027
i am using a bootable cwm card (2GB) (cwm version 3.0.2.8)
after installing ManualNooter-4-5-18.zip then ManualNooter-4-6-16.zip I remove the sd card and reboot and I get a boot-loop with the "n color" screen animation. It has not booted successfully yet.
I have already used the 8 failed boots method to restore to factory and re-registered the nook.
Then I redid everything again and im back at the boot-loop.
any ideas
i do not have an answer but this answers my question of whether I want to run manual nooter on my 1.3 or try cm7. the cm7 steps seems more intimidating
Well i tried several more times last night with no luck. Then i got brave and just wiped everything (data,system,cache,dalvick) then flashed cm7 and gapps straight from my cwm boot card. I somehow
Ended up with a fully functional nook. App market works. Rebooted several times to be sure. I even tried usb host with my homemade adapter. Mouse, keyboard, and sandisk cruzer all work splendidly thru a powered hub.
My only mistake was i cant find my backup of stock 1.3 rom. Is there one floating around?
Sent from my LG-VM670 using Tapatalk
If I'm understanding correctly, you're trying to go from CM to 1.3, correct?
From what you've described, I suspect Clockworkmod 3.0.2.8 is your problem. If you look carefully as you format /data in preparation for reloading the BN 1.3 firmware, I think you'll see that the format is actually failing. That version of CWM doesn't handle the partitions correctly.
You want 3.2.0.1. See the edits at the top of this thread: http://forum.xda-developers.com/showthread.php?t=987735
If you're already on CM7.1, you probably have the correct version of CWM installed. You can save yourself a step by formatting the /data and /system partitions using that, then continuing on with the rest of the procedure for restoring BN 1.3. I went through all this myself a few days ago while preparing to go to BN 1.4.1.
I forgot to mention in my last post that i realized i was using the wrong cwm image and i burned another card with cwm 3.2.01.
I was still getting a boot-loop so i wiped everything and went straight to cm7.
Sent from my LG-VM670 using Tapatalk
@bobstro
I didn't read your post correctly.
I had a stock nook that i want to install cm7 on. Not the other way around. I asked about a stock 1.3 file just in case i need to do a restore. The nook is done. Its running cm7 just fine and i have given it back to my friend.
I really need to get myself one :-(
I usually mess around with my sons but he's at his mothers for the weekend with it. After christmas im getting one. Dont know if it'll be a color or a nook tablet but im getting one for sure!
Sent from my LG-VM670 using Tapatalk
If you intended to install CM7 from beginning, then why you wasted time messing around with ManualNooter?
Im still rather new to working on nooks. I thought that it was required to use manual nooter first. Im still not sure.
Can someone clarify for mr. If i just bought a nook and i want cm7 on it, whats the best procedure?
Sent from my LG-VM670 using Tapatalk
pdrift said:
ok so after 3 days of trying, i keep getting stuck on a boot-loop I am asking for some help.
before I begin, I have successfully rooted and installed cm7 on 2 nooks that came factory 1.2,I have searched google and these forums but can't find anything with my specific needs.
I have followed the directions on this thread to a tee:
http://forum.xda-developers.com/showthread.php?t=1054027
i am using a bootable cwm card (2GB) (cwm version 3.0.2.8)
after installing ManualNooter-4-5-18.zip then ManualNooter-4-6-16.zip I remove the sd card and reboot and I get a boot-loop with the "n color" screen animation. It has not booted successfully yet.
I have already used the 8 failed boots method to restore to factory and re-registered the nook.
Then I redid everything again and im back at the boot-loop.
any ideas
Click to expand...
Click to collapse
The only boot loop issue I'm aware of is related to Adobe AIR and Flash. The fix is to uninstall them and then reinstall from Market.
Sent from my NOOKcolor using XDA Premium
pdrift said:
Im still rather new to working on nooks. I thought that it was required to use manual nooter first. Im still not sure.
Can someone clarify for mr. If i just bought a nook and i want cm7 on it, whats the best procedure?
Sent from my LG-VM670 using Tapatalk
Click to expand...
Click to collapse
I hope you do use Windows at some points.
Let's put it this way.
You bought a PC with Windows XP pre-installed, get home, you don't want XP, so you install Windows 7 on the PC. You just whack the XP.
Same theory applied here, B&N shipped their NC out with the original stock ROM, which is Froyo-based OS. You want to install CM7, which is Gingerbread-OS ROM. You just whack the stock and install CM7.
oh I get it know. so its pretty easy if you want to go straight to cm7 just wipe and flash.
After reading some posts from the nook tablet section, i guess i'm getting a nook color.
what a shame about the locked bootloader :-(
i didnt technically solve the boot loop issue, i just erased everything, but should I mark this as solved and if so how?
The current Nook Color bootloader is not locked. The Nook Tablet's is. I wouldn't necessarily rule anything out, though. The bootloader on the Motorola Droid 2 is also locked, and there's quite an active Cyanogenmod community around it. The only problem is that we're stuck with whatever kernels B&N release, so ICS may be a long way off. I suspect the NC will remain the tuner's machine of choice, but the performance on the NT is very nice. If you can live with a rooted B&N ROM, it's a nice device for now.
billingdl said:
The only boot loop issue I'm aware of is related to Adobe AIR and Flash. The fix is to uninstall them and then reinstall from Market.
Sent from my NOOKcolor using XDA Premium
Click to expand...
Click to collapse
No, it seems that some 1.3 based NC units will bootloop if 4.6.16 is used to root them. I'm not sure why. Even after repartitioning to original nook partition sizes, or using CWM 3.2.01 (which supports the new partitioning), it'll still bootloop if 4.6.16 is used. Might be because of the different kernal included, but I'm not knowledgeable enough to know for sure. They root fine with 4.5.18. Haven't tried one with the new 1.4.1 compatible nooters.
To the original poster;
I'm having the same problem here, installed 4.15 successfully, installed 4.16 and am getting stuck in boot loop at the rainbow nook color screen.
I'm not understanding the 8 boot fail procedure though. Is this when you let the boot loop run through 8 times or when you get to the point of when the boot loop starts, shut the NC off and power it back on?
Also, to install cm7, all you did was put it on your sd card, and installed it through cwm?
The 8 boot method if i recall correctly is when you boot the nook and wait until the splash screen shows up immediately hold the power button and shut it down. Repeat 7 more times. If you did it correctly it should take over and do a restore on its own.
If you want to go straight to CM7 I dont think you need to go thru with this procedure because if you create a bootable cm7 card and insert it in your nook while its off then power up, it should boot you into cwm recovery. Once in the recovery you can flash cm7.
sent from my OV CM7 IHO using tapatalk
pdrift said:
The 8 boot method if i recall correctly is when you boot the nook and wait until the splash screen shows up immediately hold the power button and shut it down. Repeat 7 more times. If you did it correctly it should take over and do a restore on its own.
If you want to go straight to CM7 I dont think you need to go thru with this procedure because if you create a bootable cm7 card and insert it in your nook while its off then power up, it should boot you into cwm recovery. Once in the recovery you can flash cm7.
sent from my OV CM7 IHO using tapatalk
Click to expand...
Click to collapse
Thank you good sir! I was stuck in boot loop forever and couldn't find a clean explanation of the 8 boot fail process. I always tried to turn it off when the rainbow nook color screen came up.
I got it reset, made a flashable CWM SD card with 3.2 and then flashed CM7 on there and it works great!!
That was very frustrating, thank you!
Dont mention it, Glad to here I was able to help you out. I felt the same way when I was in that situation. Lots of googling to get a clearer idea on what that 8 boot method entailed. CM7 really makes it feel like a totally different device.
To all the devs that work on these projects, thank you
sent from my OV CM7 IHO using tapatalk
ive recently purchased a nook color version 1.3 and did all the steps to build cm7 on sd ard inserted it into my nook it downloaded then rebot and seem to come up im cm7 but my touch screen isnt working any suggestions?
Got a sticky situation here:
Was gonna flash the SlimBean Rom, so I entered CWM, and had a braindead moment when I wiped SD card after wiping the system AND THEN HITTING REBOOT. Consequence: Stuck in Bootloader or Start-up screen, nowhere to go. I'm not a total newbie in flashing roms, it was literally 2 seconds of brainfart and POOF! Screw'd up.
So what I wanna know is, has my Nexus 7 reached the point of no return or is there ANY sort of way to restore/reboot/salvage it?!
Thanks alot in advance!
Are you able to enter recovery, remount /sdcard/ and push the ROM via ADB?
per910 said:
Got a sticky situation here:
Was gonna flash the SlimBean Rom, so I entered CWM, and had a braindead moment when I wiped SD card after wiping the system AND THEN HITTING REBOOT. Consequence: Stuck in Bootloader or Start-up screen, nowhere to go. I'm not a total newbie in flashing roms, it was literally 2 seconds of brainfart and POOF! Screw'd up.
So what I wanna know is, has my Nexus 7 reached the point of no return or is there ANY sort of way to restore/reboot/salvage it?!
Thanks alot in advance!
Click to expand...
Click to collapse
I had this happen to me too! Luckily you can get back into CWM pretty easily. Hold down all buttons down until you see the device reset then quickly release and press down all the buttons again. It might take you a few tries but if you time it right it should work.
Hope this helps
Stumbled upon some other threads here, did some "unbricking" (technically mine wasn't completely bricked since i still had access to bootloader screen) by returning to stock as per instructions here and voila! All's good in the hood! Thanks for the tips guys anyway! Cheers! :good:
Phone stuck on "Samsung - Custom" screen after creating TWRP backup. Help please?
I have an ATT S4, that has had CM 10.1 on it running flawlessly pretty much since nightlies started to get released. Decided to try going back to some TW based ROMs. Running the latest nightly, loaded up TWRP, created a backup, as I usually do before swapping roms. Created the backup fine, now it won't boot, it just sits at the Samsung screen with the lock and Custom message. Wiped cache\dalvic, even tried restoring from the backup I just created. Nothing. Tried it with the phone plugged into the computer and without being plugged in (I think I recall it being plugged into USB could cause issues in the past), and still nada. Tried pulling the battery and rebooting about 10 times. Can get into recovery and odin mode perfectly fine still. Any suggestions or ideas? Thanks
Simonzi said:
I have an ATT S4, that has had CM 10.1 on it running flawlessly pretty much since nightlies started to get released. Decided to try going back to some TW based ROMs. Running the latest nightly, loaded up TWRP, created a backup, as I usually do before swapping roms. Created the backup fine, now it won't boot, it just sits at the Samsung screen with the lock and Custom message. Wiped cache\dalvic, even tried restoring from the backup I just created. Nothing. Tried it with the phone plugged into the computer and without being plugged in (I think I recall it being plugged into USB could cause issues in the past), and still nada. Tried pulling the battery and rebooting about 10 times. Can get into recovery and odin mode perfectly fine still. Any suggestions or ideas? Thanks
Click to expand...
Click to collapse
There are no less than a dozen similar threads about similar problems already. Have you looked at those threads for a possible solution yet? You can find them by using the search function or better yet just doing a visual search of the first few pages of the "General" and "Q&A" sections. Good luck.
Sounds like a ROM and kernel issue. Try flashing a ROM with a loki'd kernel.
Tylorw1
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Tylorw1 said:
Sounds like a ROM and kernel issue. Try flashing a ROM with a loki'd kernel.
Tylorw1
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
I don't see how that could be the case. I didn't flash anything. I just loaded TWRP, created a backup, and rebooted my phone. No ROM\kernel change. Nothing more than creating a backup in TWRP.
scott14719 said:
There are no less than a dozen similar threads about similar problems already. Have you looked at those threads for a possible solution yet? You can find them by using the search function or better yet just doing a visual search of the first few pages of the "General" and "Q&A" sections. Good luck.
Click to expand...
Click to collapse
I tried searching, the closest one I could find on the first few pages was this one. I just didn't see any specific to my situation because nothing was flashed. Like my response to Tylorw1, all I did was boot into recovery, create a backup, and reboot my phone. Didn't flash a ROM, change a kernel, format anything, etc...
I has this same problem... It happened after every single reboot after flashing various ROMs or anything.. I gave up and went back to CWM and haven't had the problem since :good:
Sent from my SGH-I337 using xda app-developers app
Simonzi said:
I have an ATT S4, that has had CM 10.1 on it running flawlessly pretty much since nightlies started to get released. Decided to try going back to some TW based ROMs. Running the latest nightly, loaded up TWRP, created a backup, as I usually do before swapping roms. Created the backup fine, now it won't boot, it just sits at the Samsung screen with the lock and Custom message. Wiped cache\dalvic, even tried restoring from the backup I just created. Nothing. Tried it with the phone plugged into the computer and without being plugged in (I think I recall it being plugged into USB could cause issues in the past), and still nada. Tried pulling the battery and rebooting about 10 times. Can get into recovery and odin mode perfectly fine still. Any suggestions or ideas? Thanks
Click to expand...
Click to collapse
what version of twrp? if it is 2.6.?.? then get off of it, also, what I did was pull battery for 3min, it booted fine....go back to early version of twrp...
STVERDI said:
I has this same problem... It happened after every single reboot after flashing various ROMs or anything.. I gave up and went back to CWM and haven't had the problem since :good:
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I've wanted to go back to CWM. That's what I had on my S3. Only thing stopping me, is all my nandroid backups for my S4 are done with TWRP, and I don't want to run into a situation where I need them, and them not being compatible
TheAxman said:
what version of twrp? if it is 2.6.?.? then get off of it, also, what I did was pull battery for 3min, it booted fine....go back to early version of twrp...
Click to expand...
Click to collapse
Nope, still on 2.5.0.2. Finally, after a third complete wipe/format and restore from the back I had created (the one that started the whole issue), it works fine. Such a huge pain in the ass.
a user had to boot back into twrp and wipe data/factory reset yesterday to fix this issue.
Simonzi said:
I've wanted to go back to CWM. That's what I had on my S3. Only thing stopping me, is all my nandroid backups for my S4 are done with TWRP, and I don't want to run into a situation where I need them, and them not being compatible
Nope, still on 2.5.0.2. Finally, after a third complete wipe/format and restore from the back I had created (the one that started the whole issue), it works fine. Such a huge pain in the ass.
Click to expand...
Click to collapse
And you have to be ****ing kidding me. I rebooted into recovery while typing my initial response, just to verify I was still on the 2.5.x.x TWRP. Booted up TWRP, verified that, choose "Reboot System", and same thing. Back to sitting at the Samsung screen. Nandroid backups or not, ditching TWRP as soon as I get it able to boot back up.
Even worse off now than when I started. After my last post, where my phone was doing the same "stuck on Samsung logo" thing, just from booting into TWRP, I decided to swap to a different recovery. Searched for "switch from TWRP to CWM", and found my own post I had made a few months ago, but never went through.
Following those instructions now, I decided on the PhilZ CWM. Head over to that thread, grab the loki'd zip, load up TWRP, and flash the zip. Now I can't even boot into recovery!! It just freezes on the Samsung screen with the blue "recovery booting" text.
Can still get into download mode, so I tried using ODIN to flash PhilZ jflteatt.tar.md5 file, and it fails.
At this point, waiting for the stock 1.6 firmware package to download, so I can just ODIN that.
If anyone has any other suggestions though, they'd be great. Have an hour to try while waiting for that to download
somebody had mentioned this...
http://forum.xda-developers.com/showpost.php?p=44629460&postcount=8
make sure you have the correct firmware and proceed as you are. likely your best bet.
Simonzi said:
Even worse off now than when I started. After my last post, where my phone was doing the same "stuck on Samsung logo" thing, just from booting into TWRP, I decided to swap to a different recovery. Searched for "switch from TWRP to CWM", and found my own post I had made a few months ago, but never went through.
Following those instructions now, I decided on the PhilZ CWM. Head over to that thread, grab the loki'd zip, load up TWRP, and flash the zip. Now I can't even boot into recovery!! It just freezes on the Samsung screen with the blue "recovery booting" text.
Can still get into download mode, so I tried using ODIN to flash PhilZ jflteatt.tar.md5 file, and it fails.
At this point, waiting for the stock 1.6 firmware package to download, so I can just ODIN that.
If anyone has any other suggestions though, they'd be great. Have an hour to try while waiting for that to download
Click to expand...
Click to collapse
Stock 1.6 firmware package?
Make sure you get the correct firmware? Go to SamMobile and get the stock firmware from there or go to Adam Outlers "Stock firmware ODIN" thread in the General section (the AMDL firmware link is in that thread you just have to look for it).
scott14719 said:
Stock 1.6 firmware package?
Make sure you get the correct firmware? Go to SamMobile and get the stock firmware from there or go to Adam Outlers "Stock firmware ODIN" thread in the General section (the AMDL firmware link is in that thread you just have to look for it).
Click to expand...
Click to collapse
Yeah, I meant 1.6gb firmware package. Just forgot the "gb". That's what I'm currently downloading, but trying to recover it with Kies while waiting.
I would like to report I had the same problem.
After changing roms and making a nandroid, and then deciding to switch roms again, I ran into the stuck at Samsung Custom with a lock boot screen. Most roms would boot up once, but a restart or power down would lead to being stuck. I was flashing through TWRP.
I went into TWRP and flashed OUDHS recovery which overrode TWRP and wiped/flashed through OUDHS a new rom.
Problem solved.
S3 at&t stuck in TWRP booting screen.
xBeerdroiDx said:
a user had to boot back into twrp and wipe data/factory reset yesterday to fix this issue.
Click to expand...
Click to collapse
Im new to custom roms, I pressed ok for an update on my phone, after the update was complete my phone shut off and booted into TWRP and now I can't get back to my android screen nor make calls etc. HELPPPPPPPP PLEASSSSSEE I have been trying to fix my phone since july and I have been using this cheap phone that don't even get internet. I have an S3 1747 at&t
Lnjames said:
Im new to custom roms, I pressed ok for an update on my phone, after the update was complete my phone shut off and booted into TWRP and now I can't get back to my android screen nor make calls etc. HELPPPPPPPP PLEASSSSSEE I have been trying to fix my phone since july and I have been using this cheap phone that don't even get internet. I have an S3 1747 at&t
Click to expand...
Click to collapse
Wrong forum. Please go to the s3 section with your question.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Had this problem just now, solved it by fixing permissions.
I am running an MDL based S4, and screwed the pooch. I was going to wipe the internal storage and made the mistake of doing it through TWRP 2.5. Now, I have the same problem of being stuck on the custom boot screen. I have tried to change from TWRP to OUDHS Recovery, but still boot loops to Custom screen. I have tried fresh installs of 4.2 ROMs and 4.4.2 Google Editions. Do I need to flash via ODIN?
Flame away....I know better than this!!!!
Help would be greatly appreciated.
Sent from my GT-N8013 using Tapatalk 4