abstrk rom fail!? - T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting

just checking if anyone else has a prob installing Abstrk rom....it installs but i keep getting android system fail an can'y go beyond the boot up screen. does anyone know if there is a fix for this? haven't seen one on the original post

Related

[Q] Little help please...Clockworkmod won't backup system

Hi...I am hoping for an answer here. I have searched everywhere. I don't know if it even matters or why I should really care to do this but I am new to this and it seems I should. I am rooted and running 1.1 update with the stock eclair and have tried to run a Nandroid backup with clockwork, but it stops at "can't mount /system". Can anybody tell me why? or How to make the backup? One answer I saw referred to Gingerbread and EXT4 incompatibility with version 3.0.0.5, but I am in eclair and am running CWM 3.0.1.0.
Also do you really think I need to back up? I have a TiBU for my apps and sys data. I figure if anything goes really wrong I know I can always just redo from stock, just some more wasted time. I guess I am basically asking if there is any real advantage to do a CWM backup anyway at the stage I am at, beside just playing around?
Thanks in advance for any help
From what I understand you get that error until you flash the kernel that came with that recovery. I had the same error until I flashed this zip made by mistar muffin http://forum.xda-developers.com/showthread.php?t=971197&page=21 its the recovery and kernel in 1.
I always nandroid backup, just in case.
I'm stuck in a bootloop and cant figure out a way to boot directly into CWR 3.0.1.0. I tried a few different combinations thinking it would be like the N button and the power but have had no luck. HELP!!!
Still need help? Please
Thanks fro your attempt to help. I flashed 3.0.1.0 from Muffin, but still get backup error, can't mount/system. I have searched for hours for an answer, but there is nothing around about this. Am i the only one with this problem, except previous reply. It doesn't make any sense. I even restored to stock, updated to 1.1 and rerooted, so I would have the simplest system. Still same result. Can anybody help? Thanks
nevermind
Don't know why, but I asked ROM manager to backup and it worked. SO if anyone else ever has this issue maybe this will help.

Nandroid Backup not working

Can some explain to me, what is MD5 when working with Nandroid. In the last month all of a sudden I can't flash my backups (5 different roms) anymore.
I keep getting the following message: MD5 mismatch.
Running ClockworkMod 2.5.0.1, I know I should update but if it ain't broke, don't fix it. Course it's broke now.
I do change the names of backups so I know which rom is which & I do reformat the date.
Nothing on the phone has changed, radio's the same, etc. Only thing I do is flash different roms. Last 1 was BeatMod's Gingerbread. Wanted to go back to HTCClay's Superfast 1.3RU, for the speed, but got the MD5 mismatch message, which comes up no matter which backup I try to reinstall.
What's going on ?
Any thoughts or suggestions would be appreciated. Been looking all over but can find no references pertaining to MD5. Can someone please enlighten me.
Thanks
Never mind, found a pretty informative page if anyone else is interested.
http://androidforums.com/htc-droid-eris/138831-verify-your-files-md5-checksums.html
I've got some reading to do.

[Q] HTC Hero looping on the boot screen. How can this be fixed?

Phone: HTC Hero, CDMA
Carrier: Sprint
While others have reported of this problem, the solutions that worked for them dont work for me. Im really stuck.
I know, its an old and slow phone, but I was hoping to go to CM7 to get better performance out of it. Well, I must have done something wrong in the process. My current android version is 2.1-update1. I used z4root to root it and used the clockworkmod ROM manager to install a recent nightly after backing-up my current ROM. Installing the nightly failed, something to do with the zip, but my phone had already been wiped and rebooted in default factory mode. I tried doing the install again with the same nightly and a more recent one, but it kept failing due to a problem with the zips. After one of the reboots, the OS just wouldnt load; seems to be looping on the 'HTC quietly brilliant' screen. I am able to boot in recovery mode, but cant figure out how to get past this looping issue.
Ive tried booting using the back-up I created with no luck. Ive even tried going through the RUU process (cant post a link cause Im a new member here), which results in an error message stating that theres an incorrect bootloader.
I did figure out that I was trying to install CM7 using the wrong zip; had the GSM version. Ive tried installing CM7 with the correct zip, but, after reboot, it loops at the animation with the android on the skateboard and the blue arrow around it. Not sure what it means that the two different OSs loop at, what looks like, the same points.
I probably did something wrong, but Im hoping somebody with a better understanding of all thats involved can let me know if there is any way for me to fix this. Thanks in advance for the help.
grins1 said:
Phone: HTC Hero, CDMA
Carrier: Sprint
While others have reported of this problem, the solutions that worked for them dont work for me. Im really stuck.
I know, its an old and slow phone, but I was hoping to go to CM7 to get better performance out of it. Well, I must have done something wrong in the process. My current android version is 2.1-update1. I used z4root to root it and used the clockworkmod ROM manager to install a recent nightly after backing-up my current ROM. Installing the nightly failed, something to do with the zip, but my phone had already been wiped and rebooted in default factory mode. I tried doing the install again with the same nightly and a more recent one, but it kept failing due to a problem with the zips. After one of the reboots, the OS just wouldnt load; seems to be looping on the 'HTC quietly brilliant' screen. I am able to boot in recovery mode, but cant figure out how to get past this looping issue.
Ive tried booting using the back-up I created with no luck. Ive even tried going through the RUU process (cant post a link cause Im a new member here), which results in an error message stating that theres an incorrect bootloader.
I did figure out that I was trying to install CM7 using the wrong zip; had the GSM version. Ive tried installing CM7 with the correct zip, but, after reboot, it loops at the animation with the android on the skateboard and the blue arrow around it. Not sure what it means that the two different OSs loop at, what looks like, the same points.
I probably did something wrong, but Im hoping somebody with a better understanding of all thats involved can let me know if there is any way for me to fix this. Thanks in advance for the help.
Click to expand...
Click to collapse
I *think* your error, in general, was using a bunch of "easy" one click methods and not properly learning (READING) about what the proper steps are. Here is my advice (assuming you are still rooted) -
1.boot into recovery (power off phone, hold home button, press power)
2.wipe data/factory reset
3.mounts/storage - wipe system and boot
4.restore nand backup OR flash ROM/gapps (from the same thread)
5.reboot, and be patient, bootup could take 5-10 minutes.
Good Luck.
You are the man (or woman)! I believe the formatting of system and boot is what did it. Really appreciate the help.
grins1 said:
You are the man (or woman)! I believe the formatting of system and boot is what did it. Really appreciate the help.
Click to expand...
Click to collapse
It is important, as Il Duce said, that you definitely do a good amount of reading when you want to get involved in rooting your phone. You are opening yourself up to some great innovation and fun, but you can also cause yourself a lot of headaches.
Recovery is your friend. If you can get into that, at least you know things are ok. I like to wipe (or format) system, data, cache, and boot 3x just to make sure that clockwork recovery cleaned everything and there are no dingleberries from the last rom I was using.
Flashing the correct type of rom is even more important. Don't flash a gsm rom to a cdma phone and NEVER flash a gsm radio to a cdma phone. Once you delve into the reading aspect of XDA, you will see that is the sure way to brick your phone.
Some roms take longer than others to boot up. Let it run its course. Sometimes it will reboot right after installing. At some point, you might want to make a nandroid of the new rom you are running and go back to your stock (2.1 update 1) and update your PRL, baseband, etc. (if you haven't done an update in a while).
Have fun, that is the most important part and we seem to have a lot of it here in HeroC XDA land.
You know, I put in a fair share of reading about how to update the ROM on my phone and I was under the impression that it would be fairly simple. I figured that since this has been done for quite a while and all these tools have been developed, I wouldnt need to know what happens on the back end during a root or ROM install.
But I did get myself into a bind that I wasnt able to figure out on my own. And with the help of this forum, I was able to get past my problem. Im glad to say I now have a phone that is functioning very smoothly with CM7 and the apps I need.
Next step for me is figuring out how to save my apps to the SD card so that I can install from there if/when I update my ROM in the future.
Thanks again for the help!
Get titanium backup FTW.
BANG! from my shooter...

[Q] Tried to install BlazingDragon 1.9b...

And now my 2X won't boot. It freezes at the LG startup-screen. I've probably overlooked something, not checked for the right baseband or not updated something else - AND I've been dumb enough only to back up my setup - not my OS.
Is there any way to get out of this? I had FR8 before...
Thanks.
Backtoext3 or just flash your old rom over this
That did it, thanks.

Reboot & Wifi "error" after 2 weeks of using any ROM

Hi all,
I've been unable to find a post about this for quite some time so I decided to make a threat about it.
I have a recurring problem with my captivate. Usually after about 2 weeks of using a ROM my phone will have 2 issues pop up simultaneously. They seem to always happen together. It seems to happen after my phone shuts off and will not turn back on until I battery pull. Once I do that I am presented with these two issues:
1.) When I try and toggle Wifi it attempts to then simply says "error" underneath it. I have found a few threads about this but no answers
2.) Upon installation OR restoration of any app with Titanium Backup my phone does a soft reboot (goes to spinning CM logo or for ICS goes to the multicolored squares flying around).
Edit: On the newest MIUI it now says "insufficient storage available" instead of rebooting when I try to install an app after the issues crop up, wifi "error" is still the same
I've had these same 2 issues occur with CM7 Stable, RC, and many nightlies, MIUI, and TeamHacksung's ICS build. I believe it may have happened with cognition too but am not positive.
I do not restore any data with TB. Before each flash I wipe system, cache, dalvik, and do factory reset and still this issue occurs without fail after about 2 weeks on any ROM and the only fix I have is to flash a new one.
Nandroid backups DO fix the problem. If anyone is willing to look through logs or something and see what was different I would be eternally grateful and certainly send you something through PayPal
Any help is greatly appreciated and I am willing to try anything at this point. Thanks!
Sorry for the double post,
Is there a better forum to post this in?
spectralite said:
Sorry for the double post,
Is there a better forum to post this in?
Click to expand...
Click to collapse
Nah this is the right place. That's a very strange problem you're having though, and I don't know what the exact solution is, if there even is one for this. The only thing I can suggest is going back to stock, and then reinstalling CM7 or whatever you want
Sent from my lightning fast Glitched 1.3Ghz CM7 i897 Captivate
Thanks,
Well happened again on newest MIUI. Gonna go back to stock and start over. I'll update the thread if it does or does not happen again.
Unfortunately after using Odin to go back to stock and rerooting/flashing it happened again on the most current build of MIUI. I'm currently at a loss for what to do. Has anyone heard of or seen anything like this?
Thanks in advance
spectralite said:
Unfortunately after using Odin to go back to stock and rerooting/flashing it happened again on the most current build of MIUI. I'm currently at a loss for what to do. Has anyone heard of or seen anything like this?
Thanks in advance
Click to expand...
Click to collapse
Just curious, have you tried leaving it stock and seeing if it happens on a pure stock ROM? If so it could be a defect with the phone?
If you flash back to pure stock and the issue doesn't come back, maybe try a custom ROM that's closer to stock, not a CM or MIUI or ICS build. I haven't seen this issue, just trying to suggest some solutions.
I had this same problem with my fascinate. I flashed 1.10.21 MIUI follwed by glitch 13.1. This combination used to work, or so I thought. I flashed back to stock, 1.12.1 then a different package of glitch 13.1 and my wifi started working again. I know the captivates and fascinates are somewhat different, but try this out and see if it works.
bobbylx said:
Just curious, have you tried leaving it stock and seeing if it happens on a pure stock ROM? If so it could be a defect with the phone?
If you flash back to pure stock and the issue doesn't come back, maybe try a custom ROM that's closer to stock, not a CM or MIUI or ICS build. I haven't seen this issue, just trying to suggest some solutions.
Click to expand...
Click to collapse
I guess I could try that, I just like CM7/MIUI so much. Another thing that happens is many different applications start FCing after the problems all begin.
I tried to restore to a nandroid backup I had made before it happened this time and I received an MD5 mismatch which I believe happened last time I tried to restore...
New info:
I have not realized this before but it seems that I start getting a message that says, "Google Talk Authentication Failed", around the same time. Also FCs happen much more frequently. Is there anything I could be doing to cause this?
New Info
Just going to keep this updated with things I have tried in case anyone ever searches for this that has this issue:
Full format of SD card and odin back to stock did not prevent the issue from cropping up on the DarkKnight3 ROM with Icy Glitch. At this point I can only assume it is somehow hardware relatedl

Categories

Resources