Related
I was running on a rooted 3.1 with tiamat 1.7 overclock
What I did was:
tried to follow [UPDATE][US WIFI ONLY]Android 3.2 on Xoom WiFi, Root, via ClockworkMod Recovery
then I did this: Note also if you are coming over from a custom ROM, wipe your cache partition (under main menu) and dalvik cache (under Advanced) in ClockworkMod Recovery prior to performing the following steps.
next I applied the 3.2 update
Now Im stuck in the boot animation.
From what I understand Im getting this because I was not on the stock kernel, can anybody help me fix this and get me to 3.2
Thank you
download the stock images here http://forum.xda-developers.com/showthread.php?t=1080963
and flash via fastboot, this will get you out of the boot loop, i had the same issue
should I try and flash the 3.2 or the 3.1 given my current situation?
If you made a backup in cwm just restore it. If not, I would say go back to the beginning and flash stock 3.0. If you plan on rooting unlock the bootloader right then. Setup the Xoom, connect to wifi and take the 3.1 ota update. Setup and connect to wifi again and wait a bit to see if 3.2 ota update notification appears. If it does, take it and root it (see my guide in dev section). If it does not pop up, you can update manually (see bauxite's guide in dev section) then root. This way you should have no issues. I know it sounds like a lot to do, but it all should take you less than hour. I did one for a friend and it took me 34min to do everything. After your rooted you can restore apps with titanium if you have made and saved the backups. Good luck.
Sent from my HD2
jase33 said:
If you made a backup in cwm just restore it. If not, I would say go back to the beginning and flash stock 3.0. If you plan on rooting unlock the bootloader right then. Setup the Xoom, connect to wifi and take the 3.1 ota update. Setup and connect to wifi again and wait a bit to see if 3.2 ota update notification appears. If it does, take it and root it (see my guide in dev section). If it does not pop up, you can update manually (see bauxite's guide in dev section) then root. This way you should have no issues. I know it sounds like a lot to do, but it all should take you less than hour. I did one for a friend and it took me 34min to do everything. After your rooted you can restore apps with titanium if you have made and saved the backups. Good luck.
Sent from my HD2
Click to expand...
Click to collapse
You probably should wipe user data in recovery along with the caches. That's what got me out of the bootloop and into the updated stock 3.2.
i flashed the stock images from the first link provided via fastboot and it worked perfect, the thread said you can flash from whatever to whatever by using those images so i flashed 3.2 and it fixed everything. Took about 5 minutes to do, I wonder if this way will give me problems when I try to root (pretty sure I lost root) but everything now seems to work fine
Hi,
I had the same issue. i fix by going back in cwm making factory reset and install again the same image.
after the first reboot i restored soft with titanium and all working good.
Tomate2K8 said:
Hi,
I had the same issue. i fix by going back in cwm making factory reset and install again the same image.
after the first reboot i restored soft with titanium and all working good.
Click to expand...
Click to collapse
Yep, that's the easiest solution, but whatever works!
I just tried to flash Tiamat 2.0 and the boot image with it (I followed the directions and did them in the correct order), and it's now stuck at the Motorola boot screen (not the animation). Any suggestions? I'm not sure how to get back in to CWM now.
Edit: Managed to get in to CWM, did a factory/data reset and wiped cache before re-flashing. Still stuck on the boot screen.
i updated my aussie telstra xoom 3g to tiamat 2 (3.2) and booted fine but did not see 3g, so i used a bul.prop from 3.1 and got the bootloop prob, rebooted to recovery and did wipe erase, when it booted up again tried the euro build.prob and all worked, i suspect the issue relates to buil.prop so a bit of tinkering will always win in the end, bassically these things seem to be bullet proof when it comes to screwing summin up
phekno said:
I just tried to flash Tiamat 2.0 and the boot image with it (I followed the directions and did them in the correct order), and it's now stuck at the Motorola boot screen (not the animation). Any suggestions? I'm not sure how to get back in to CWM now.
Edit: Managed to get in to CWM, did a factory/data reset and wiped cache before re-flashing. Still stuck on the boot screen.
Click to expand...
Click to collapse
What HC version were you on when you flashed 2.0? I'm just wondering if you needed to flash the boot image. It's hard to help you if we don't know what configuration you are coming from. Also Is your Xoom US wifi or 3G or Euro wifi or 3G?
zbee said:
i updated my aussie telstra xoom 3g to tiamat 2 (3.2) and booted fine but did not see 3g, so i used a bul.prop from 3.1 and got the bootloop prob, rebooted to recovery and did wipe erase, when it booted up again tried the euro build.prob and all worked, i suspect the issue relates to buil.prop so a bit of tinkering will always win in the end, bassically these things seem to be bullet proof when it comes to screwing summin up
Click to expand...
Click to collapse
Yeah, they really are almost bullet-proof. Good thing too, seeing all the abuse they have to take.
: )
okantomi said:
What HC version were you on when you flashed 2.0? I'm just wondering if you needed to flash the boot image. It's hard to help you if we don't know what configuration you are coming from. Also Is your Xoom US wifi or 3G or Euro wifi or 3G?
Click to expand...
Click to collapse
My fault, I guess some information would have been helpful. The Xoom is a US WiFi version and I was running 3.1 when I started this, which I now realize was probably really stupid. I should have probably gotten 3.2 on there before I started. Is there a way to update to 3.2 at this point? Or do I need to go back to stock and start over?
I appreciate the help.
Edit: Or should I just install another ROM per these directions.
phekno said:
My fault, I guess some information would have been helpful. The Xoom is a US WiFi version and I was running 3.1 when I started this, which I now realize was probably really stupid. I should have probably gotten 3.2 on there before I started. Is there a way to update to 3.2 at this point? Or do I need to go back to stock and start over?
I appreciate the help.
Edit: Or should I just install another ROM per these directions.
Click to expand...
Click to collapse
Are you rooted? If so, you can flash the Tiamat Xoom Rom 1.1 which is for 3.1. You don't need to flash any additional kernel. You can get it from the appropriate thread in Development. You will probably have to do a full wipe in CWM Recovery (user data, cache).
From there, you can flash the Team Tiamat Xoom Rom 2.0 Manta Ray right on top of the Rom 1.1, no wipe needed. That should get you the HC3.2 update, preserve your root, and give additional functionality. I love it. I updated in a more roundabout method...I could have done it this way if I had waited...
If you are not rooted, you need to root first..see any one of the guides to root in HC3.1.
Good luck!
okantomi said:
Are you rooted? If so, you can flash the Tiamat Xoom Rom 1.1 which is for 3.1. You don't need to flash any additional kernel. You can get it from the appropriate thread in Development. You will probably have to do a full wipe in CWM Recovery (user data, cache).
From there, you can flash the Team Tiamat Xoom Rom 2.0 Manta Ray right on top of the Rom 1.1, no wipe needed. That should get you the HC3.2 update, preserve your root, and give additional functionality. I love it. I update in a more roundabout method...I could have done it this way if I had waited...
If you are not rooted, you need to root first..see any one of the guides to root in HC3.1.
Good luck!
Click to expand...
Click to collapse
Yeah, I was rooted before all of this. I had done a full wipe in CWM and then did the boot/kernel and now I'm here. I think I should have just done the Tiamat Xoom Rom 2.0 in stead. Can I just flash the 2.0 ROM over what's on there now?
Edit: Now, I can't seem to get in to CWM. I'm not really sure how to other than using adb reboot recovery, but windows isn't picking up the device now.
Edit #2: I got back in to CWM. I'm running CWM 3.0.2.5, FYI.
I just flashed Tiamat Xoom Rom 1.1 and now it's back up and running. Thanks a ton for helping! I'll probably be putting 2.0 on there pretty quickly.
phekno said:
I just flashed Tiamat Xoom Rom 1.1 and now it's back up and running. Thanks a ton for helping! I'll probably be putting 2.0 on there pretty quickly.
Click to expand...
Click to collapse
Great! Have fun with it. I think you'll love it.
I have a problem restoring my xoom to stock.
I flashed the Katana OC kernel onto my Wifi Only US Xoom with 3.2. I oc'd to 1.5 ghz and it worked fine. Then I left it on during the night. When I woke up the next morning it was stuck in a boot loop, so I though maybe I should flash the Katana without OC instead. That I tried but It got stuck halfway through (Maybe I should have waited longer...).
After this the xoom wouldnt boot (not that surprising..) so I flashed it back to stock with the official Motorola images. However the Xoom still wont boot up, gets stuck either on Moto logo or on the Honeycomb boot screen.
When I flash the 3.2 images and a custom kernel (Tiamat 2.0) then I can get into Android but it stops responding after a few minutes.
The Xoom seems to be running good before it freezes, I cant find a solution to get my Xoom back to life.
Any ideas?
blee00 said:
I have a problem restoring my xoom to stock.
I flashed the Katana OC kernel onto my Wifi Only US Xoom with 3.2. I oc'd to 1.5 ghz and it worked fine. Then I left it on during the night. When I woke up the next morning it was stuck in a boot loop, so I though maybe I should flash the Katana without OC instead. That I tried but It got stuck halfway through (Maybe I should have waited longer...).
After this the xoom wouldnt boot (not that surprising..) so I flashed it back to stock with the official Motorola images. However the Xoom still wont boot up, gets stuck either on Moto logo or on the Honeycomb boot screen.
When I flash the 3.2 images and a custom kernel (Tiamat 2.0) then I can get into Android but it stops responding after a few minutes.
The Xoom seems to be running good before it freezes, I cant find a solution to get my Xoom back to life.
Any ideas?
Click to expand...
Click to collapse
Have you done a full wipe user data/factory reset in CWM recovery? You may need a clean slate to proceed.
Also, do you know if debugging is set to on? If you can't boot you can't get into settings but that could prevent you from accessing your Xoom from your pc.
okantomi said:
Have you done a full wipe user data/factory reset in CWM recovery? You may need a clean slate to proceed.
Also, do you know if degugging is set to on? If you can't boot you can't get into settings but that could prevent you from accessing your Xoom from your pc.
Click to expand...
Click to collapse
Thanks for your reply! =)
I have done the "Wipe user data/factory reset" in CWM, If I do that I usually can boot Honeycomb, but I rarely get past the setup wizard (although sometimes I do), but then after a few minutes it freezes again.
Also, I can access my Xoom through ADB.
I have tried to install, following instruction on this site to install ROM's. I have tried Starburst and Task650. I currently have the OTA Touchwiz installed from Samsung, and Pershoot kernel 2.6.34-4-cyanogenmod installed. Every time I try it goes through the process and successfully I reboot, it boots to the Samsung Logo (Start) and I wait like 20 minutes and it does nothing, just stay at the start Samsung logo. I have done this several times on each ROM, always having to go back to a backup I did. What am I doing wrong? Why can’t I install any ROMs? I would greatly appreciate some expert advice, because I hear so many great things about Task650 I really want to give it a shot. I am an ex-iPad owner, gave to daughter as a friend had one and let me use it; feel in love with it the moment I picked it up. I have also searched the forums, but I am doing everything to the T as outlined in instructions. Had my tab for a week, it isn’t a 10.1v or I/O series. Thanks everyone in advance for helping a complete noob when it comes to android.
Sounds like a case of missing to clear the cache.
Did you wipe the cache partition and dalvic cache in the recovery menu?
After making major changes like switching between roms or kernels thats recommended and if not done might cause such an issue.
I did
I did do those steps, did the factory wipe/reset, wiped cache, wiped dalvic. Once I did those 3 steps, installed from zip, goes through the steps successfully, but when I reboot it just stay on logo. I read, it could take 5-10 min, but I have waited up to 20 and it doesn't move past that. Just see what I am doing wrong, as the 2 roms have both done that, and I have tried several times with both. Just have the stock rom with Touchwiz OTA upgrade from Samsung, and pershoots latest kernel. Thanks in advance.
bad zip file?
Is it possible the zip files are getting corrupt? Are you downloading them on your tab or on computer and transferring them over? I would also check to see if there are any errors when you flash.
Download from computer and transfer over. How can I if there are errors as once I install a ROM it just stays at the logo. After it starts to install it end with, i cant recall exactly, but it says success. Thanks in advance
In cwm when you flash there is some text readout. That is where some error messages could be seen. That text will be there before you choose reboot on the menu.
sounds like you've had some issues bro. if you do get fed up and need some help, just let me know and we can video chat through gmail or skype to get you through it and get you a custom rom.
slice2011 said:
I have tried to install, following instruction on this site to install ROM's. I have tried Starburst and Task650. I currently have the OTA Touchwiz installed from Samsung, and Pershoot kernel 2.6.34-4-cyanogenmod installed. Every time I try it goes through the process and successfully I reboot, it boots to the Samsung Logo (Start) and I wait like 20 minutes and it does nothing, just stay at the start Samsung logo. I have done this several times on each ROM, always having to go back to a backup I did. What am I doing wrong? Why can’t I install any ROMs? I would greatly appreciate some expert advice, because I hear so many great things about Task650 I really want to give it a shot. I am an ex-iPad owner, gave to daughter as a friend had one and let me use it; feel in love with it the moment I picked it up. I have also searched the forums, but I am doing everything to the T as outlined in instructions. Had my tab for a week, it isn’t a 10.1v or I/O series. Thanks everyone in advance for helping a complete noob when it comes to android.
Click to expand...
Click to collapse
Well first...are you rooted? Do you have Clockworkmod, Superuser, and Busybox?
Oh and congrats on your switch from Apple to Android
slice2011 said:
I have tried to install, following instruction on this site to install ROM's. I have tried Starburst and Task650. I currently have the OTA Touchwiz installed from Samsung, and Pershoot kernel 2.6.34-4-cyanogenmod installed. Every time I try it goes through the process and successfully I reboot, it boots to the Samsung Logo (Start) and I wait like 20 minutes and it does nothing, just stay at the start Samsung logo. I have done this several times on each ROM, always having to go back to a backup I did. What am I doing wrong? Why can’t I install any ROMs? I would greatly appreciate some expert advice, because I hear so many great things about Task650 I really want to give it a shot. I am an ex-iPad owner, gave to daughter as a friend had one and let me use it; feel in love with it the moment I picked it up. I have also searched the forums, but I am doing everything to the T as outlined in instructions. Had my tab for a week, it isn’t a 10.1v or I/O series. Thanks everyone in advance for helping a complete noob when it comes to android.
Click to expand...
Click to collapse
Maybe try in "reverse" order
Flash kernel back to stock - flash the rom you want - if that works then flash pershoots kernel
Just a thought
hy
i installed the overcome rom on my 7500, and i'm so entusiast!
Try it it's very easy!
---------- Post added at 07:21 PM ---------- Previous post was at 07:16 PM ----------
i did it in recovery, do wipe data
Yes its is rooted, cmw, superuser, and busybox all installed. Installed both roms in recovery, hold volume down and power method. Just can't figure it out, I will do the reverse suggestion and report back later tonight or tomorrow.thanks everyone for the advice/help.
no erreor s after install, think task's says success or something to that effect.
Well it finally stuck, I knew it was going right as when it was installing system files, it took like 5 minutes, the other time I did it took like 30 seconds. As per Stinky73 went back to stock Kernel, and wipe data, clear cache partition, and wipe Dalvik Cache, Thanks a million Stinky73 u da man! HELL YEAH this Rock, it is so responsive, seems a hell of a lot smoother, and apps just snap open. Task you did one outstanding job. This is coming from a noob who has no idea how much work goes into these, I am sure a lot. So from a noob to an expert EXCELLENT JOB, love my Tab that much more!!!!! Thanks everyone for the help, I am one happy camper! Now another dilemma, I saw new versions: How do I install these now that I have Tasks650 installed and working? Do I have to do the same steps above, wipe data, cache, and Dalvik? And if so what do I do next, do I do the same: Also is the BOB_WOW_Fix installed using the same method as i read flashable, sorry for the noob question, just want to get it right.
1. install zip from sdcard.
2. choose zip from sdcard.
NEW!!!- Task650's V7.1
Once again... I forgot to add "Desktop UAstring to V7.1 so flash this update after you boot up V7.1 if you want it.
Can someone please give me the proper ateps on installing the bob_wow_fix, and the 2 7.1 updates? Thanks
slice2011 said:
Can someone please give me the proper ateps on installing the bob_wow_fix, and the 2 7.1 updates? Thanks
Click to expand...
Click to collapse
There's no complete fix for BoB and WoW, its a continuous work in progress.
bob wow fix
Are you taking about the fix task posted?
What I had to do was wipe cache first then flash the zip just like you did on the rom. And bobs your uncle.
Edit:
Oh ya I would reboot after each flash just to be sure.
So as you probably read had a hell of a time getting a rom installed, followed stink'ys advice and it worked. Installed 6.0, finally, than installed the 6.1 theme update, no issues. Than downloaded the 7.1, followed op. wiped dalvik, wiped cache, and wipe data/factory restore. No errors, but when I rebooted it got stuck once again on the Samsung logo with the Galaxy Tab 10.1 print. So i do not know what the heck I am doing wrong. I got 6.0 than 6.1 updated and now I am back to my initial problem with 7.1, no I didn't use the 7.1 update one. tried 3 times, and even downloaded the fiel again, and followed the same steps task outlined, and no go. Had to restore the 6.1 from back up.
slice2011 said:
So as you probably read had a hell of a time getting a rom installed, followed stink'ys advice and it worked. Installed 6.0, finally, than installed the 6.1 theme update, no issues. Than downloaded the 7.1, followed op. wiped dalvik, wiped cache, and wipe data/factory restore. No errors, but when I rebooted it got stuck once again on the Samsung logo with the Galaxy Tab 10.1 print. So i do not know what the heck I am doing wrong. I got 6.0 than 6.1 updated and now I am back to my initial problem with 7.1, no I didn't use the 7.1 update one. tried 3 times, and even downloaded the fiel again, and followed the same steps task outlined, and no go. Had to restore the 6.1 from back up.
Click to expand...
Click to collapse
All sounds very strange...is it definitely stuck on the boot screen? These things can take anything from 5-20 minutes on initial boot, there is no definite rule for that, seems to be device related in some strange way...how long have you left it?
I am really an OCD when it comes to upgrading and always backup (nandroid or whatever) then go back to the very start before trying something new...years of PC and Mac have taught me that even tho the manufacturers say you just apply upgrades on top of previous upgrades, sooner or later they will f**k up....
I wonder why you are passing thro all the steps you are...(going thro 6.0, 6.1 etc)
I would be inclined to try going back to stock....stock whatever it was rom when you got the tab (notice you've never stated what model you have), stock kernel, nothing installed....then go direct to Tasks 7.1 (everything needed in 6.x is incorporated in 7.1) .... then, if it boots and runs, add pershoots kernel...
What do you reckon Task?? Can you chip in on this one?
Cheers, Stinky
@ slice2011.....any news?
Drpbody said:
And bobs your uncle..
Click to expand...
Click to collapse
How'd you know Bob was my uncle?
Oh wait..everybody has an uncle bob somewhere
I, Not at 10 post yet so Here I post,
Can any one help me with SOD on the new Flexreaper 11 ROM. Acer Recovery tool indicates i have 3.01 bootloader. I Had a 3.2 Rom before that worked fine. I Wiped everything and formatted Flexrom and system. First time it went to sleep it would not wake up.
Thanks!
fayettec said:
I, Not at 10 post yet so Here I post,
Can any one help me with SOD on the new Flexreaper 11 ROM. Acer Recovery tool indicates i have 3.01 bootloader. I Had a 3.2 Rom before that worked fine. I Wiped everything and formatted Flexrom and system. First time it went to sleep it would not wake up.
Thanks!
Click to expand...
Click to collapse
Did you install the Flexreeper new bootloader? This is probably why you still have SOD. If I am not mistaken, Flexreeper has 2 or 3 different versions of bootloader that you need to use. Depending on which version of the rom you want to install.
Scary Bootloader
Moscow Desire said:
Did you install the Flexreeper new bootloader? This is probably why you still have SOD. If I am not mistaken, Flexreeper has 2 or 3 different versions of bootloader that you need to use. Depending on which version of the rom you want to install.
Click to expand...
Click to collapse
Thanks for the reply.
I thought that the img file was for people with ICS bootloaders, I thought that I had HC3.0.1
I'm afraid if i flash the ICS img file that I won't beable to get back to HC or that because I have 3.0.1 bootloader that the ICS bootimage file they have there will brick my a500
If you formatted and wiped everything as you were instructed . I am wondering if when you get to the google setup screen something is being restored from the old system.. When it gets to where you setup your google account. Uncheck the backup and restore boxes .
Do not restore any apps or settings from say TI BACKUP. Install only a few apps that you MUST HAVE and know work with google ics. run for a few days and see what happens.
if you still have a issue go back to 3.2 for a week and see if it works. it could be just coincidence that hardware fail-or at the same time as you flashed your tab. ..
just a though thou unlikey
Thanks
I went ahead and tried the ICS Boot.img file after reading some new post in the thread. It worked! Interesting side note, be fore the flash at boot up the display showed:
ACER.
After it was:
ACER ACER
Thanks again!
fayettec said:
I went ahead and tried the ICS Boot.img file after reading some new post in the thread. It worked! Interesting side note, be fore the flash at boot up the display showed:
ACER.
After it was:
ACER ACER
Thanks again!
Click to expand...
Click to collapse
You running an a500 or an a501?
Last time I saw the double Acer, was when the leak first came out. The 500 had issues, but not the 501 (except for double acer).
The double Acer is normal. Be glad you don't get the AFU screen like the rest. It's a BETA release, and it has..... issues. Hopefully Acer will release an official build that will do away with a lot of the issues in the near future.
fayettec said:
I, Not at 10 post yet so Here I post,
Can any one help me with SOD on the new Flexreaper 11 ROM. Acer Recovery tool indicates i have 3.01 bootloader. I Had a 3.2 Rom before that worked fine. I Wiped everything and formatted Flexrom and system. First time it went to sleep it would not wake up.
Thanks!
Click to expand...
Click to collapse
I came from ezterry's acer7.014.14_CUST_ROOT_BBv4_S. I just flashed Flexreaper R11 this morning. I've noticed SOD at least three times today. My bootloader version is 3.01 like in the OP. I noticed he ended up flashing the ICS bootloader. Is this the only known fix? And if so, will ICS bootloaders prevent me from restoring a HC NAND? Thanks.
How do we find our boot loader version? When I do, what does that mean for ROMs I can flash? I have flexreaper r11 and it is consistently SOD badly. :'(
Sent from my SGH-I777 using xda premium
bigwilly90210 said:
How do we find our boot loader version? When I do, what does that mean for ROMs I can flash? I have flexreaper r11 and it is consistently SOD badly. :'(
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
To me a favor and flash the kernel for ICS boot loader users.
Its in the thread , section kernels.
The rom got a auto script for installing the correct boot.img but even for some the ICS boot.img is needed.
Worst that can happen is stuck on Acer logo, if you got that just reboot into recovery and flash the boot.img or kernel for HC boot loader users.
The thing is that even for some people that got HC bootloadr they still need to flash the Kernel for ICS boot loader users, strange yes but no harm in trying.
I'm wondering if something in the cmdline for the LP0 changed in the latest leak causing the kernels packed for the old bootloader to have SoD again.
Also, some of you guys, please don't confuse bootloader with boot.img. They are not the same thing. FLEXREAPER does not contain any bootloaders. It contains 2 different boot.img's and trys to install the correct one based on the bootloader you have.
The bootloader only gets changed if you flash it via nvflash (or flash a stock leak but then it would be locked).
@someone who asked above. if you flash the ICS bootloader(0.03.11-ICS), you would not be able to run HC ROMs, unless you went back to the HC bootloader (3.01).
But apparently, the ICS boot.img is working for some on the old HC bootloader and resolving the SoD issue for them.
Ok, I just started experiencing an issue. I suddenly can't get into recovery. Here is a little back history. My N7 was running CNA 3.6.6 (I know, but...), and I was bored so I decided to try ParanoidAndroid. Well, I have that gotta try something else feeling again, and when I try to get into recovery, it will go to the google screen, then go black for about 10 seconds, then go back to the Google screen and boot up. This happens if I reboot to recovery through the power menu, or getting into recovery from the bootloader. I even tried Quick Boot, in hopes it had some magic I didn't. No luck. The same crap. I even switched from TWRP to clockwork recoveries, and the same crap happens (I tried the same things I did originally).
Also tried through other apps too, like Rom Manager, Rom Toolbox, and TiBu. Everything works, but I am bored with this rom... I have tried turning it off, plugging the N7 into a PC and trying to get into recovery. Again, I can get into the bootloader, but as soon as I select recovery, it goes black, then fully reboots...
Anyone have any ideas? Any help would be greatly appreciated.
Have you tried re-flashing a recovery image, eg TWRP 2.3, from fastboot?
Sent from my Nexus 7
BillGoss said:
Have you tried re-flashing a recovery image, eg TWRP 2.3, from fastboot?
Sent from my Nexus 7
Click to expand...
Click to collapse
Thanks for the reply. I will give this a try (gotta wait until after 10pm...or 17 minutes!). Again, thanks, hope this works.
MetalWych said:
Thanks for the reply. I will give this a try (gotta wait until after 10pm...or 17 minutes!). Again, thanks, hope this works.
Click to expand...
Click to collapse
Scheiße, I reflashed TWRP in fastboot, and I am getting the same result. I think my N7 forgot it has a recovery!? I will try flashing clockwork through fastboot and see if this works. Thanks for your help...
Edit: Clockwork does not help. There is no recovery for me. I am now at a loss. Hopefully someone will have some suggestions...
Finally got my recovery back...damn latest bootloader!
Yeah, this has sucked. I have spent several hours figuring out what the hell went wrong. It turns out its the latest bootloader. Others are having this issue. So, I had to go back to stock (which will erase EVERYTHING) and then had to re-root. Now that my bootloader is back to JRO03D, I am back up and running.
So, the first time I did this route, I decided to take the update and re-root my N7, and ran into the same issue. I could not get into recovery. So, I had to do it all over, this time not taking the update and not updating the bootloaders, and I am now back and already have a ROM running and everything installed.
If you want to go this route, here are a couple of links that will help...
http://rootzwiki.com/topic/28544-guide-nexus-7-bootloadersrecoveriesrootback-to-stock/#entry764328 and go to the Back To Stock section. The next part is for rooting (if you wish to do this yourself)...
http://www.talkandroid.com/guides/misc/how-to-unlock-and-root-the-nexus-7/
I will post this in case anyone has a need for this info...
Unable to get into Recovery after 4.1.2 upgrade... - xda-developers
Any help?
So i have the I337m, canadian model S4 on Bell Mobility network, and I"m running SlimRoms with 2.5.0.2 twrp recovery.
Every other reboot, the phone gets stuck on the splash screen, I have no problem to go into recovery mode or anything, this is simply a problem when rebooting and gets stuck on the "Galaxy S4" screen. Here's what I've tried, tried both with TWRP and CWM and TWRP seems better, I don't get stuck on the splash screen as often as CWM. I've reverted back to the "stock ROM" and rerooted and loaded the TWRP recovery, and while it seems better at first, it slowly gets stuck more and more at the splash screen.
I'm running out of ideas, no knowing what do to to improve this problem...
Anyone else having this problem? I'm positive this is not a "ROM" related problem but a recovery problem, yet maybe it's just my phone that's being the problem.
JP
I'll also add that I've never formated data on TWRP... since I've read it gives that problem.
jproy12 said:
I'll also add that I've never formated data on TWRP... since I've read it gives that problem.
Click to expand...
Click to collapse
You have to do a factory reset, wipe data, or you will get a boot loop. Do that and I'm sure you'll get past the boot loop. If you're concerned about the version of twrp you're on, update it.
http://forum.xda-developers.com/showthread.php?p=41010145
jd1639 said:
You have to do a factory reset, wipe data, or you will get a boot loop. Do that and I'm sure you'll get past the boot loop. If you're concerned about the version of twrp you're on, update it.
http://forum.xda-developers.com/showthread.php?p=41010145
Click to expand...
Click to collapse
I'm not getting boot loops actually, I get stuck on the "splash screen" and when I hold the "power" button for +/-10sec it reboots and most of the time it's fine.
When I install any roms, I always do a factory reset... So I doubt it's that
i had the same issue. im running the same s4 on koodo/telus. how i got it to work took a while but it fixed the problem. full back up through recovery but i wasnt gona use it..i only had it for safety. used titanium to back up all the apks. then grabbed a stock rom from the Canadian stock roms page and used odin to flash it. rooted and added recovery (twrp). downloaded my rom to the sd, wiped everything and installed the rom. once done then used titanium to restore the apks. im still learning the basics to all this so in no way am i an expert and theres probably a better way around all this but this is what worked for me. maybe it helps who who knows
h_khan said:
i had the same issue. im running the same s4 on koodo/telus. how i got it to work took a while but it fixed the problem. full back up through recovery but i wasnt gona use it..i only had it for safety. used titanium to back up all the apks. then grabbed a stock rom from the Canadian stock roms page and used odin to flash it. rooted and added recovery (twrp). downloaded my rom to the sd, wiped everything and installed the rom. once done then used titanium to restore the apks. im still learning the basics to all this so in no way am i an expert and theres probably a better way around all this but this is what worked for me. maybe it helps who who knows
Click to expand...
Click to collapse
Yea, I had done this before, but I'm giving it another shot tonight to see if it'll fix my problem for good...
Still having the same problem... Running out of ideas
jproy12 said:
Still having the same problem... Running out of ideas
Click to expand...
Click to collapse
I was having a similar problem to your's. I found the cause of my issue. It was TWRP 2.6.0.0. More specifically, it was using TWRP 2.6 to format my /data partition. After doing some trouble shooting, I found that my /data partition was the cause of my S4 hanging at the S4 splash screen. Like you, I was able to get into Android on the first boot, but if I tried to reboot, I was get stuck at the splash screen. So, long story short (solution), I restored one of my nandroid backups, got into Google Play, downloaded ROM Manager and installed CWM. I used CWM to format my /data partition and ONLY my /data partition. Once I did this, I rebooted my phone. Android loaded, I had to go through the initial setup process since I formatted the /data partition, but after this, I was able to reboot my phone 5 times in a row without issue and shut down twice with no problems booting back up.
Here is my thread: http://forum.xda-developers.com/showthread.php?p=45448596#post45448596
There's a bit of reading. Hope this helps.
So my issue was caused by TWRP 2.6.0.0 and using it to format my /data partition.
jproy12 said:
Still having the same problem... Running out of ideas
Click to expand...
Click to collapse
i think the rom is the cause of this issue. i myself am running goldeneye rom which is the best rom ive used so far...perfectly balanced performance and battery life. id definitely recommend it.
Talabis said:
I was having a similar problem to your's. I found the cause of my issue. It was TWRP 2.6.0.0. More specifically, it was using TWRP 2.6 to format my /data partition. After doing some trouble shooting, I found that my /data partition was the cause of my S4 hanging at the S4 splash screen. Like you, I was able to get into Android on the first boot, but if I tried to reboot, I was get stuck at the splash screen. So, long story short (solution), I restored one of my nandroid backups, got into Google Play, downloaded ROM Manager and installed CWM. I used CWM to format my /data partition and ONLY my /data partition. Once I did this, I rebooted my phone. Android loaded, I had to go through the initial setup process since I formatted the /data partition, but after this, I was able to reboot my phone 5 times in a row without issue and shut down twice with no problems booting back up.
Here is my thread: http://forum.xda-developers.com/showthread.php?p=45448596#post45448596
There's a bit of reading. Hope this helps.
So my issue was caused by TWRP 2.6.0.0 and using it to format my /data partition.
Click to expand...
Click to collapse
Thanks, I'll give that a try, but it seems like this is/was my problem, is your problem fixed for good now? No getting stuck on the "boot screen"?
h_khan said:
i think the rom is the cause of this issue. i myself am running goldeneye rom which is the best rom ive used so far...perfectly balanced performance and battery life. id definitely recommend it.
Click to expand...
Click to collapse
I've been running Slim for a year now, and won't go back to anything else, it's stable and fast, I doubt it's a ROM problem, but a recovery problem.
i think you're right. a problem with the recovery makes more sense.
jproy12 said:
Thanks, I'll give that a try, but it seems like this is/was my problem, is your problem fixed for good now? No getting stuck on the "boot screen"?
Click to expand...
Click to collapse
So it seems like this wasn't exactly my problem... I've reverted back to stock and I'm doing a couple shutdowns and reboot and see if I still get stuck at the splash screen.
I've been doing reboots and shutdowns on the "stock" rom and "stock" recovery, and all is good, so I can rule out the fact that it's the phone and it's hardware issues...
Now, just need to figure out the actual problem
jproy12 said:
Thanks, I'll give that a try, but it seems like this is/was my problem, is your problem fixed for good now? No getting stuck on the "booscreen"?
Click to expand...
Click to collapse
So far so good. I rebooted many times since I made the post in this thread. Haven't got stuck on the splash screen yet.
I'm still having the problem, being on either the TWRP, CWM or Philz recovery, so I'm really not sure what it could be. I'm on the latest modem and still have the problem, is none else having these issues?
I'm getting annoyed and really want to get this fixed.
I think any ROM built on AOSP or CyanogenMod have this issue. It's already a known issue to CM.
Use CWM and you'll have to deal with it less.
emckai said:
I think any ROM built on AOSP or CyanogenMod have this issue. It's already a known issue to CM.
Use CWM and you'll have to deal with it less.
Click to expand...
Click to collapse
I've never seen anyone really mentionning this for the Galaxy S4 from my numerous searches...
jproy12 said:
I've never seen anyone really mentionning this for the Galaxy S4...
Click to expand...
Click to collapse
If you look in the cyanogenmod thread, it's located in the known bug (post #2)
Any custom roms built on top of CM10 will probably have this issue.
emckai said:
If you look in the cyanogenmod thread, it's located in the known bug (post #2)
Any custom roms built on top of CM10 will probably have this issue.
Click to expand...
Click to collapse
You are right! I guess it's one of those bugs, just never noticed anyone really mentioning anything about it
jproy12 said:
You are right! I guess it's one of those bugs, just never noticed anyone really mentioning anything about it
Click to expand...
Click to collapse
Yeah, but I don't think its a big deal anyway. How many times do you turn off your phone and turn it back on in a day?