Hey
I just got my replacement phone today (previous one smashed) and have been trying to put an aosp (tasks AOKP) ROM on for a while now and I can't get it to work!
I have a twrp recovery and was bone stock earlier today (4.1.1). Everytime I try to flash tasks 6/7 update I get the error in the title. Any ideas? I updated the bootloader before trying this as well. I tried reinstalling the ROM several times to no avail. Any ideas? Should I just odin stock and start fresh? Is there a quicker method of fixing this? Is it a bad recovery?
my apologies if this has been answered before. I have been searching for hours now and found a few similar problems but on other phones that I couldn't relate to my problems. any help would be much appreciated!
Thanks!!!
[EDIT] Problem solved. I was previously on TWRP 2.5 for d2can. I used odin to put on TWRP 2.3 for d2att and all is well now.
Related
hi everyone,
i use galaxy wonder and i installed ParanoidAndroid mod via CWM (6.0.1).
after a while i decided to bring back my stock rom.
so i've downloaded I8150XXLB4 version (TUR) from samsung-updates.com.
wiped system/cache/dalvik cache and flashed with ODIN 4.43.
now system starts up and all the keys working except touchscreen. i can't pass the welcome screen.
i searched the forum and found only two threads and no solution.
ANY ADVICE? thx in advance...
i finally did it!
tried stock and many custom ROMs. tried many kernels (2.6-3.0 etc); and the only one working rom was:
Koprol-GigaBread-Stable-2.3.6-XXLMI-Signed
now finally it is working. in many threads i've read, people sent their devices to service.
so before sending to servise, nothing to lose about trying this ROM i guess...
Hey guys,
So a couple of weeks ago, I got a One and I unlocked everything and put CM10.2 on it. Yesterday, while needing the navigation to try and get un-lost, I couldn't get my phone to get a GPS lock at all, even while having a clear view of the sky and everything. I am running CM10.2 and CWM 6.0.4.5. I have already tried clearing and redownloading the AGPS data and that didn't help. So I found a comment saying that I should flash back to stock and change the location settings and the preferred network setting to see if that changes anything.
I found the stock ROM .zip on this forum, 1.10.605.10 (4.2.2/5.0) and tried flashing it after checking the MD5. That ended up not working at all, it starts but then fails saying that it can't open the update .zip and also says "(bad)".
Now I am trying to download 2.10.605.1 (4.3/5.0) and I will try that tomorrow.
The reason I posted is to ask 1) if anyone was able to fix the GPS problems without having to flash back to stock and 2) what I needed to do to flash back to stock if that's the only option that I have? I don't want to mess anything up and I am still kind of inexperienced at this.
Thanks!
OctaviusMaximus said:
Hey guys,
So a couple of weeks ago, I got a One and I unlocked everything and put CM10.2 on it. Yesterday, while needing the navigation to try and get un-lost, I couldn't get my phone to get a GPS lock at all, even while having a clear view of the sky and everything. I am running CM10.2 and CWM 6.0.4.5. I have already tried clearing and redownloading the AGPS data and that didn't help. So I found a comment saying that I should flash back to stock and change the location settings and the preferred network setting to see if that changes anything.
I found the stock ROM .zip on this forum, 1.10.605.10 (4.2.2/5.0) and tried flashing it after checking the MD5. That ended up not working at all, it starts but then fails saying that it can't open the update .zip and also says "(bad)".
Now I am trying to download 2.10.605.1 (4.3/5.0) and I will try that tomorrow.
The reason I posted is to ask 1) if anyone was able to fix the GPS problems without having to flash back to stock and 2) what I needed to do to flash back to stock if that's the only option that I have? I don't want to mess anything up and I am still kind of inexperienced at this.
Thanks!
Click to expand...
Click to collapse
The only option is to flash back to Stock to fix your GPS issues. You probably need to use a different recovery either from TWRP or Clockwork depending on the one that doesn't work to flash it.
I finally decided to flash a new rom since my note 2 after year and a half started to seriously lag on me. I downloaded via goomanager the following rom Bam 2.0 rc3 20140304 kitkat l900. zip along with pa gapps stock 4.4.2 20131215 zip. I made a stupid mistake of not doing a backup since I thought that TWRP will save my last backup. When I flash the rom they seem to be working but when the rom is trying to activate my mobile data service, it just lags for a long while, and at the end says that activation can take a few minutes. After a long while it tells me that it failed to connect. I am stuck, i have tried reinstalling various stock files via odin but to no avail. Now I have also retry using the galaxy note toolkit v 4.1.0 but I can't get to the usb debugging mode since the rom won't load all the way. Does anybody now what I did wrong? Or how can I fix this problem? I have been reading all kinds of posts and try many solutions, please help. Thank you in advance.
Hi,
I had CM 10.2 running fine on my HOX. A couple of weeks ago I decided to test out CM11, since this is not my primary device, stability wasn't that big of a concern for me. The first few tries CM11 installation was a failure with some error (I can't recall) occurring when installing the zip in Recovery (if i remember correctly it had something to do with version of recovery I was using).
Anyways, I searched online, found a solution and was able to install the CM11. I have flashed the boot, erased the cache, tried wiping/factory resetting the device, in all kinds of orders (wiping/installing/flashing boot.img, flasing boot.img/installing CM11, etc). but no matter what I try my phone always stays stuck at the boot animation.
I found multiple threads on the forums with similar problems, but in most cases the OP was either missing flashing boot.img or erasing the cache helped. not so in my case.
Also, weirdly enough, now even if i try to reinstall CM 10.2 (which was working earlier), I get the same issue.
any further guidance on troubleshooting / overcoming this issue is highly appreciate
HOX International H__J15
HBOOT 1.31
CWM Touch Recovery 6.0.4.8
(btw, just tried Beanstalk ROM, same issue... I dont know what I F'd up on this phone!! )
nabeelmoeen said:
Hi,
I had CM 10.2 running fine on my HOX. A couple of weeks ago I decided to test out CM11, since this is not my primary device, stability wasn't that big of a concern for me. The first few tries CM11 installation was a failure with some error (I can't recall) occurring when installing the zip in Recovery (if i remember correctly it had something to do with version of recovery I was using).
Anyways, I searched online, found a solution and was able to install the CM11. I have flashed the boot, erased the cache, tried wiping/factory resetting the device, in all kinds of orders (wiping/installing/flashing boot.img, flasing boot.img/installing CM11, etc). but no matter what I try my phone always stays stuck at the boot animation.
I found multiple threads on the forums with similar problems, but in most cases the OP was either missing flashing boot.img or erasing the cache helped. not so in my case.
Also, weirdly enough, now even if i try to reinstall CM 10.2 (which was working earlier), I get the same issue.
any further guidance on troubleshooting / overcoming this issue is highly appreciate
HOX International H__J15
HBOOT 1.31
CWM Touch Recovery 6.0.4.8
(btw, just tried Beanstalk ROM, same issue... I dont know what I F'd up on this phone!! )
Click to expand...
Click to collapse
Your HBOOT is to low you must to upgrade ti 1.39 or 1.72 but 1.31 is tooo low and for this the CM11 don't boot
Actually I think 1.31 is the latest version which came out with jelly bean rom for the htc__15 id.
what's frustrating is that I can't even get the 10.2 version of CM working again either...which should be fine with this hboot version
nabeelmoeen said:
Actually I think 1.31 is the latest version which came out with jelly bean rom for the htc__15 id.
what's frustrating is that I can't even get the 10.2 version of CM working again either...which should be fine with this hboot version
Click to expand...
Click to collapse
try restore stock and chek for update restore nandroid and see I am not sure J15 is only 1.31
Will give it a shot tonight and report back. ...what's grinding my gears is none of the other roms including jb ones I tried are working either
i finally managed to resolve my issue. I tried changing recoveries, tried multiple ROMs and also tried to run RUU (which failed since i have a later version of the ROM vs. what's available in RUU).
finally decided to try formatting the boot, System and Cache partitions and installing CM11 again.
I had never used the 'format <partition>' feature before. Apparently this did the trick and now i am running CM11 .!!
nabeelmoeen said:
i finally managed to resolve my issue. I tried changing recoveries, tried multiple ROMs and also tried to run RUU (which failed since i have a later version of the ROM vs. what's available in RUU).
finally decided to try formatting the boot, System and Cache partitions and installing CM11 again.
I had never used the 'format <partition>' feature before. Apparently this did the trick and now i am running CM11 .!!
Click to expand...
Click to collapse
is HBOOT still the same version or did you upgrade it?
I am curious about the order in which you did things. After formatting boot, system and cache partitions, did you flash the boot image again or did you do that prior to the formatting.
Thanks
Hi, Ive not long had my m9. When i got it it updated straight away and got the charging bug.
Since then I have s-off'd and tried various roms with not too much luck.
I now have a bug that occurs when i flash a new rom. This has happened when i flashed 3 different roms. Leedroid, Viper and android revolution. the rom flashes ok, then starts to boot, and builds art. It then finishes building art and starts to complete the boot process, and then it reboots and tries to build art again.
I flash back to my stock backup and everything is fine again. (apart from the damned charging bug)
Has anyone else experienced something similar?? am i missing something??
Go in twrp and make factory reset
just tried that, didnt work
Did you update your firmware? if you're still on 1.x firmware, those 2.x roms will reboot.
yeah. have tried matching roms to firmware and still get the same result. trying viper one currently. in a massive bootloop again. It boots enough to say "nfc service has stopped working" and thats what made me think it might be firmware, but it seems to make no difference.
cant even adb whilst its booting.. getting waiting for device.
What version of twrp are you using?
2.8.6.1
philicibine said:
2.8.6.1
Click to expand...
Click to collapse
Update to 2.8.7.0 and see if it continues.
I've solved this, and my charging issue. Finally!!
I decided to flash the earliest ruu I could find and then let it do all of the ota updates itself.
I then rerooted, flashed updated firmware and am now running leedroid.
Thanks for the help guys.