Related
I've noticed that not all roms put what spl we should have, so is it safe to assume that 1.33.2005 good for the rom?
The rom I'm looking at is http://forum.xda-developers.com/showthread.php?t=574526
Yes! Tried it myself
I think it's good for all roms, actually it might even be a prerequisite for all hero roms except micro hero.
Not 100 % sure of the latter though.
I just tried flashing the hero rom and it flashed just fine but after it got passed the mt3g splash it just repeated the hero and htc splash, I'm back on cyanogen, any ideas on how to get it working?
Did you wipe before you flashed? Also, the first boot can take a few minutes.
If it's neither lack of wipe or lack of patience I have no idea
It's lack of patience lol. I'll try flashing it again and wait this time.
Okay, well it's not lack of patience unless waiting 1 hour isn't long enough. Any body else have some ideas to get this working?
Kaptur mentioned it, but did you wipe before applying the update.zip ?
Yes I did.
Then I recommend you try another ROM, maybe evil D:'s sense/nano sense as apparently thats quick/stable.
it has to be a bad download or you need to wipe a couple more times I've wiped and it still did a boot loop before so try wiping at least3 times and /or try a new rom
I flashed 2 different heros after that, 1 of them i got the splash loop and evil's worked.
I usually find if a wipe then flash doesnt work, I just repeat the same procedure i.e pull battery, wipe and reflash then boot does the trick.
If all else fails repartition card and then flash, and if that doesnt work, i guess that rom isnt for you.
Im having this problem with nano sense.
I always wipe completely and recreate all partitions if im running a hero rom
Wouldn't recreating the partitions get rid of my apps? If not, I might try that.
Alrigt, I randomly get reboots and I just rooted using Revolutionary last night. I'm using TWRP as my recovery and I want feedback as to if this is a normal issue or if it's just my handset. I hate sense and want rid of this garbage. >=( I appreciate all feedback, just don't be a jerk about it. I'm not new, and this isn't a noob question. I'm asking specifically about Revolutionary root with twrp then flashing CM7 as the rom and if it has bootlooping issues coming from stock.
I haven't tried TWRP, but you might want to try the usual recoveries, and try wiping everything once and and a fresh install. Just a thought. I have never had issues with any cyanogenmod. Oh another thing, might want to partition your SD card.
It's stuck in a bootloop right now. I actually already tried CWM and just did Amon_ra's recovery...it seems to be a CM7 issue with my phone? I'll try MIUI and then switch to CM7
So, you're afraid to ask for getting shot down.
I'm afraid to post an idea for getting shot down. But, I'll venture forth and probably be wrong. Do you still have PC136.img on your SD? If so, I think you're supposed to remove it. I could be wrong and probably am. I'm 70% sure I'll hear about it if so.
MIUI was bootlooping as well. I think this might be an issue with me flashing my splash screen after acquiring root?
Common issue: make sure you are wiping the SYSTEM partition. The "factory reset" wipe option does not do this. Or find one of those automated "super wipe" scripts to flash in recovery that does it all for you.
Others had bootloops and such and later posted back that it was a wipe issue.
Also, provide a logcat if you can.
Actually, I found that I had to wipe the boot partition for some reason. It worked and I hope this thread helps people get past boot loops. I also need to restore my Wimax keys now lol.
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'm running an S4 and have this very weird issue where after installing a custom rom, the phone would reboot and load the rom successfully, but if I ever reboot it, it never wants to go past the Samsung logo.
If I try entering TWRP and fixing permissions or factory reset, it just comes up with errors and fails. The only way around it is to format data, then reflash the rom.
But now I have a nandroid backup so everytime I reboot, I basically have to reflash the rom.. It's happened on at least 2 roms!
I've used the search function on the forums and found a thread was inconclusive so I've made this thread.
Thanks in advance
(This is my first Android phone too, so I'm not 100% familiar with all the different software and techniques, but I can definitely learn!)
Try flashing the ROM with the latest stock CWM. TWRP can cause issues.
Kesh09 said:
I'm running an S4 and have this very weird issue where after installing a custom rom, the phone would reboot and load the rom successfully, but if I ever reboot it, it never wants to go past the Samsung logo.
If I try entering TWRP and fixing permissions or factory reset, it just comes up with errors and fails. The only way around it is to format data, then reflash the rom.
But now I have a nandroid backup so everytime I reboot, I basically have to reflash the rom.. It's happened on at least 2 roms!
I've used the search function on the forums and found a thread was inconclusive so I've made this thread.
Thanks in advance
(This is my first Android phone too, so I'm not 100% familiar with all the different software and techniques, but I can definitely learn!)
Click to expand...
Click to collapse
go into the wipe options on twrp - go to advanced and select - cache, dalvik, system, data - swipe
then do a normal full wipe
reflash the chosen rom
power off rather than reboot
then power up
something gets fracked with the wipes somewhere and thats how i fixed it.
either that or flash philz recovery through odin and do a "new rom" wipe
Gotcher said:
Try flashing the ROM with the latest stock CWM. TWRP can cause issues.
Click to expand...
Click to collapse
For some reason, whenever I install CWM, it keeps getting stuck at "recovery booting" and once in maybe 30 times it works, haven't got it to work in a while.. Not sure what's happening, but if I flash TWRP again, it boots up fine. Am I doing anything wrong? Using Philz touch..
scottyf79 said:
go into the wipe options on twrp - go to advanced and select - cache, dalvik, system, data - swipe
then do a normal full wipe
reflash the chosen rom
power off rather than reboot
then power up
something gets fracked with the wipes somewhere and thats how i fixed it.
either that or flash philz recovery through odin and do a "new rom" wipe
Click to expand...
Click to collapse
This hasn't worked for me, and yeah, I can't seem to get CWM to like my phone..
Kesh09 said:
For some reason, whenever I install CWM, it keeps getting stuck at "recovery booting" and once in maybe 30 times it works, haven't got it to work in a while.. Not sure what's happening, but if I flash TWRP again, it boots up fine. Am I doing anything wrong? Using Philz touch..
This hasn't worked for me, and yeah, I can't seem to get CWM to like my phone..
Click to expand...
Click to collapse
try flashing the rom twice in succession. it will stick eventually but its just getting the right combo. these S4's are a right pain in the ass just now.
also another option would be downloading a rom with Aroma installer onto a micro sd and see if that gets you out of the problem. ive found on other devices ive had that a rom with Aroma can sometimes get you moving (id suggest Omega rom as a good solid base)
scottyf79 said:
try flashing the rom twice in succession. it will stick eventually but its just getting the right combo. these S4's are a right pain in the ass just now.
also another option would be downloading a rom with Aroma installer onto a micro sd and see if that gets you out of the problem. ive found on other devices ive had that a rom with Aroma can sometimes get you moving (id suggest Omega rom as a good solid base)
Click to expand...
Click to collapse
The rom I'm flashing (twice) now is Omega actually!
I'll see how this goes! Hoping it's okay!
..
try to install another rom clean & stable and do full wipe or trust me the best to turn the phone to default firmware.
Kesh09 said:
The rom I'm flashing (twice) now is Omega actually!
So are you suggesting I install Omega, get it run, then install Aroma installer and reinstall it?
Click to expand...
Click to collapse
no i just meant flash the rom twice IF it didnt have Aroma.
try GoldenEye rom from micro sd (obviously downloaded and placed on the card through a pc and put back in the phone).
Or as above - you might have to start from scratch and use Odin to revert back to stock and re-root etc again.
Although i said Aroma sometimes helps, being honest it was a rom with Aroma that started causing me a similar issue in the first place (Not Omega or Foxhound though)
No luck guys... I think I'd rather start from a stock rom too. When I created my stock rom backup, it was through nandroid and an CWM format, but CWM did work, it froze when it was checking for MD5 or something...
But now I'm trying to find the right firmware for my phone, is there any thing I need to look out for? Gt-i9505 from Australia?
http://forum.xda-developers.com/showthread.php?t=2265477
In that thread, there's two of them, I'm downloading the one closest to when I bought it which was June
Hi all,
Recently I've had a few troubles with flashing ROMS, to the point where I cant start my phone without it rebooting. I've been using CWM PhilZ 6.0.4.4, GT-I9505 and I did a full wipe everytime.
Originally I was on Omega 10 and decided to try out a new ROM (phone kept dying at 15% for some reason as well). Flashed PACman ROMs latest nightly and had some troubles getting past the set up as it froze every time, and when I tried rebooting it, it would simply not start. It was suggested to upgrade my recovery, so I did so from PhilZ CWM 3.0.3.3 to 3.0.4.4. Tried it again and it worked fine, but due to my own clumsiness I accidentally restored system data from Omega to PACman. Obviously it wouldn't start properly after that, reflashed again and was very careful to only restore apps (restored SMS as well as .xml). Everything was fine except a few bugs here and there, but then I rebooted it and it just wouldn't start.
After that I tried cyanogenmod, as I thought it would be more stable. Pretty much same thing happened, less bugs but when I tried rebooting it just wouldn't start.
Given up by this point, I tried reflashing Omega v10. It worked perfectly for a few hours, flashed the latest 3minit framework and ausdim kernel. The next day, my phone suddenly died at 42% and when I try to start it up it gets stuck at the Omega logo. Went into recovery, tried doing full wipe again and cant get past setup without it turning off. Furthermore, when I try to reflash, it just unpacks the zip but turns off randomly.
I'm not quite sure what to do next, I'm thinking it's my recovery not doing wipes properly since when I try to wipe dalvik it says "path not found", and if I try to reboot with recovery it says "root may have been lost, would you like to root?"
Sorry for the whole wall of text, just thought all the information would be better than not enough! If anyone could help it would be greatly appreciated as I cant even access my phone currently
Sent from my GT-N5110 using Tapatalk
Battery
Williamharv said:
Hi all,
Recently I've had a few troubles with flashing ROMS, to the point where I cant start my phone without it rebooting. I've been using CWM PhilZ 6.0.4.4, GT-I9505 and I did a full wipe everytime.
Originally I was on Omega 10 and decided to try out a new ROM (phone kept dying at 15% for some reason as well). Flashed PACman ROMs latest nightly and had some troubles getting past the set up as it froze every time, and when I tried rebooting it, it would simply not start. It was suggested to upgrade my recovery, so I did so from PhilZ CWM 3.0.3.3 to 3.0.4.4. Tried it again and it worked fine, but due to my own clumsiness I accidentally restored system data from Omega to PACman. Obviously it wouldn't start properly after that, reflashed again and was very careful to only restore apps (restored SMS as well as .xml). Everything was fine except a few bugs here and there, but then I rebooted it and it just wouldn't start.
After that I tried cyanogenmod, as I thought it would be more stable. Pretty much same thing happened, less bugs but when I tried rebooting it just wouldn't start.
Given up by this point, I tried reflashing Omega v10. It worked perfectly for a few hours, flashed the latest 3minit framework and ausdim kernel. The next day, my phone suddenly died at 42% and when I try to start it up it gets stuck at the Omega logo. Went into recovery, tried doing full wipe again and cant get past setup without it turning off. Furthermore, when I try to reflash, it just unpacks the zip but turns off randomly.
I'm not quite sure what to do next, I'm thinking it's my recovery not doing wipes properly since when I try to wipe dalvik it says "path not found", and if I try to reboot with recovery it says "root may have been lost, would you like to root?"
Sorry for the whole wall of text, just thought all the information would be better than not enough! If anyone could help it would be greatly appreciated as I cant even access my phone currently
Sent from my GT-N5110 using Tapatalk
Click to expand...
Click to collapse
Seems to me that you are having battery issues. You might need to get a replacement. If that doesn't work you could try flashing a pre-knox ROM though ODIN 3.04. This would mean starting from scratch, but it could be your solution.
Quick question. Are you downloading the ROMs with your phone or downloading them with your computer then moving them to your phone via usb? because it might be your pc's/usb fault.
I also think there's a problem with your battery, it might need to be replaced.
ebahena said:
Seems to me that you are having battery issues. You might need to get a replacement. If that doesn't work you could try flashing a pre-knox ROM though ODIN 3.04. This would mean starting from scratch, but it could be your solution.
Quick question. Are you downloading the ROMs with your phone or downloading them with your computer then moving them to your phone via usb? because it might be your pc's/usb fault.
Click to expand...
Click to collapse
Thanks for the quick reply! Would the battery explain why my ROMS wouldn't start though? Such as how Omega got stuck at the logo. I will try using my friend's battery, or just keeping the phone on charge whilst doing it and see how that works.
Im sending them through Usb currently, is there any other way to get it on my phone as I can't turn it on to send it over wifi :/
Sent from my GT-N5110 using Tapatalk
Whenever you flash stock tar through Odin, the phone will restart by itself and wipe cache. After it does this, you should factory wipe and no more bootloop, or soft bricks. I would start from scratch if i were you. If you have working custom recovery installed., I would go in and do a format, not a wipe, but format the sdcard and restart into download mode and flash stock tar, cf auto root, and then flash a custom recovery. And then decide what rom to flash.
norml said:
Whenever you flash stock tar through Odin, the phone will restart by itself and wipe cache. After it does this, you should factory wipe and no more bootloop, or soft bricks. I would start from scratch if i were you. If you have working custom recovery installed., I would go in and do a format, not a wipe, but format the sdcard and restart into download mode and flash stock tar, cf auto root, and then flash a custom recovery. And then decide what rom to flash.
Click to expand...
Click to collapse
Thank you for the reply i just got home so I'll try this soon, would it be risky though since my battery and/or cable may be damaged, meaning if it turns off during flashing stock, I'll get a hard brick?
Update: just reflashed Omega whilst it was on a charger and it actually worked.
Does this suggest that the battery is damaged?
Sounds to me like a definite battery problem.
Samsung recalled batteries with a serial number starting with BD. have a look and check your battery mate.
Also check it's not swollen
Sent from my GT-I9505 using XDA Premium HD app
Obagleyfreer said:
Sounds to me like a definite battery problem.
Samsung recalled batteries with a serial number starting with BD. have a look and check your battery mate.
Also check it's not swollen
Sent from my GT-I9505 using XDA Premium HD app
Click to expand...
Click to collapse
I just checked my battery, it does start with BD, and it does appear to be somewhat swollen.. I haven't noticed it before :l Could I just return it to Samsung for a replacement, without going back to stock ROM? I'm currently in Australia, haven't really seen a Samsung support center anywhere nearby.
Update: got my hands on a new battery, everything seems to be working great now. Flashed paranoid android, no reboots or any other problems.
Thank you so much to everyone who helped