Related
Hey guys,
when I tried flashing CWM on my new HTC One it just booted in normal mode over and over.
I tried every recovery-image available and it nerver worked.
While playing around I finally got it working without flashing the recovery image to the boot partition!
No need to copy root files and CFW files before flashing the recovery!
Instructions
Unlock your device at http://www.htcdev.com/bootloader/
Reboot into bootloader
> fastboot flash boot boot.img - thanx to Paul O'Brien
> fastboot reboot-bootloader
> fastboot flash recovery recovery.img - thanks to Flyhalf205
> fastboot erase cache
After this you should be able to enter recovery via bootloader or 'adb reboot recovery'.
The recovery image is CWM Touch 6.0.2.8 which worked great for me, didn't try the other ones right now.
I hope I could help
I had issues booting recovery if I used the All in One kit to flash recovery.
So people should flash it manually instead to avoid problems.
Nekromantik said:
I had issues booting recovery if I used the All in One kit to flash recovery.
So people should flash it manually instead to avoid problems.
Click to expand...
Click to collapse
I had problems with AiO-Kit and doing it manually, too.
Only this method worked for me.
zantekk said:
I had problems with AiO-Kit and doing it manually, too.
Only this method worked for me.
Click to expand...
Click to collapse
Ah ok.
only issue for me now is aroma freeze issues.
Nekromantik said:
Ah ok.
only issue for me now is aroma freeze issues.
Click to expand...
Click to collapse
Didn't have that on my One until now.
I flashed my friend's One and it froze 3 times...then it worked.
I think it's recovery-related. Maybe wait for a fix.
zantekk said:
Didn't have that on my One until now.
I flashed my friend's One and it froze 3 times...then it worked.
I think it's recovery-related. Maybe wait for a fix.
Click to expand...
Click to collapse
It is AROMA related, amarullz have to update the binary
You can flash it 3 times or more, should work.
You can also use Hardware Buttons instead of Touch.. will help as well.
Device still rebooting
Can't flash recovery
same here - no access to recovery so far
Same for me too
Why ?
Got a HTC One from Orange france, and NO RECOVERY seems to stick. That thing boots, but i cannot enter recovery
I've tried using the AiO-Kit to flash CWM touch and normal as well as TWRP as well as the two CWMs manually and then this method. Still can't get access to recovery though
Try this? http://forum.xda-developers.com/showthread.php?t=2208029
Sent from my Nexus 4 using xda premium
Lothaen said:
Try this? http://forum.xda-developers.com/showthread.php?t=2208029
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
If you mean clearing the cache as mentioned in that thread I've tried it with no success
SoLdieR9312 said:
It is AROMA related, amarullz have to update the binary
You can flash it 3 times or more, should work.
You can also use Hardware Buttons instead of Touch.. will help as well.
Click to expand...
Click to collapse
Had the same problem again and again flashing TrickDroid on my HTC One (M7). Can confirm, that avoiding touch will relieve things but freezes can still occur. A few times I even could not reset the phone long-pressing the power + volume up buttons, means I was completely stuck on the frozen aroma screen (since a battery pull is not possible with this device). For anybody who may be in the same situation, try the "[FONT="Courier New]fastboot reboot[/FONT] command, this still came through and rebooted the device.
has this method worked for anyone else?
i'd like to try, but since i currently can't access recovery, i'm afraid to flash a new boot.img
pwr2wh8 said:
has this method worked for anyone else?
i'd like to try, but since i currently can't access recovery, i'm afraid to flash a new boot.img
Click to expand...
Click to collapse
Yes, worked for me. I had the same issue. While flashing Renovate rom, Aroma crapped out right at the end where it was installing the kernel. I was then stuck on boot image until i found this thread.
Also, for what it's worth, i thought I'd flash the boot image again after i got my device running again but it killed my wifi. I had to reflash the rom as wifi in settings was `out of order`....
//edit: okay. i've been able to reproduce the crashing. seems it's an aroma/rom issue (i couldn't tell one way or the other). what matters here is flashing boot image with the provided image does the trick. whatever magic it does, i'm able to flash cwm recovery 6.0.3.1 but I have to flash boot image before, else flashing recovery is fruitless.
anyways, thanks. this thread help me solve what i thought was `bricked` device.
Sometimes when I boot in recovery I get a "no OS installed error". I have to reboot the recovery in order to fix it. Does that happen to anyone else? If so, do you know what causes it? It seems to have only started happening recently? Maybe it's the 4.2.2 roms?
SkizzMcNizz said:
Sometimes when I boot in recovery I get a "no OS installed error". I have to reboot the recovery in order to fix it. Does that happen to anyone else? If so, do you know what causes it? It seems to have only started happening recently? Maybe it's the 4.2.2 roms?
Click to expand...
Click to collapse
I haven't seen that before, sounds odd. Try reflashing recovery and wiping cache, also make sure you're updated to the latest CWM
MacHackz said:
I haven't seen that before, sounds odd. Try reflashing recovery and wiping cache, also make sure you're updated to the latest CWM
Click to expand...
Click to collapse
I use TWRP.
SkizzMcNizz said:
I use TWRP.
Click to expand...
Click to collapse
Well then... use CWM and see if the issue goes away
Many of us are facing this problem where after flashing a 10.2 ROM and rebooting, the device is stuck at boot screen- the Samsung N7000 screen!
This is a strange problem which seems to be affecting only some n7000 handsets as others can keep flashing the ROMs without any issues...wiping, reflashing ROM, etc doesn't work!
I myself faced this problem on almost all custom CM 10.2 Roms and am sharing the solution which worked for me. At the onset, this solution was suggested to me by another member @Super Prince in one of my posts and it worked!!
1. Reboot into recovery
2. Flash the correct gapps once again
3. Reboot
The problem should be gone now and no more stuck-iness for you...
Sent from my GT-N7000 using XDA Premium 4 mobile app
I tried that, and it did not work.
I'm not using the regular Gapps package, but this one:
http://forum.xda-developers.com/showthread.php?t=2012857
What package do you use?
knedge said:
Many of us are facing this problem where after flashing a 10.2 ROM and rebooting, the device is stuck at boot screen- the Samsung N7000 screen!
This is a strange problem which seems to be affecting only some n7000 handsets as others can keep flashing the ROMs without any issues...wiping, reflashing ROM, etc doesn't work!
I myself faced this problem on almost all custom CM 10.2 Roms and am sharing the solution which worked for me. At the onset, this solution was suggested to me by another member @Super Prince in one of my posts and it worked!!
1. Reboot into recovery
2. Flash the correct gapps once again
3. Reboot
The problem should be gone now and no more stuck-iness for you...
Sent from my GT-N7000 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Really? I'll try it next time when I flash some CM based ROM and will get this problem.
I hope it is really the reason.
SirRhor said:
I tried that, and it did not work.
I'm not using the regular Gapps package, but this one:
http://forum.xda-developers.com/showthread.php?t=2012857
What package do you use?
Click to expand...
Click to collapse
Which CM version are you on? This method has worked for me every time on CM 10.2 roms and official CM 10.2 gapps (the one dated 13/08/2013)
I used to get stuck on the GT N7000 screen after every reboot and resorted to all sort of stuff like reflashing, formatting and stuff but to no avail.
The only solution that worked for me was re-flashing the gapps!
Maybe you should try once again with the official gapps..and post your results.
jakuburban said:
Really? I'll try it next time when I flash some CM based ROM and will get this problem.
I hope it is really the reason.
Click to expand...
Click to collapse
The 'Reason', my friend, remains a mystery...
This solution, though worked!
Experienced developers might like to comment on this as to what might be the reason
knedge said:
Which CM version are you on? This method has worked for me every time on CM 10.2 roms and official CM 10.2 gapps (the one dated 13/08/2013)
I used to get stuck on the GT N7000 screen after every reboot and resorted to all sort of stuff like reflashing, formatting and stuff but to no avail.
The only solution that worked for me was re-flashing the gapps!
Maybe you should try once again with the official gapps..and post your results.
Click to expand...
Click to collapse
I'm on Carbon, but I tried another CM based ROM as well and it did not work.
I will try it with the official Gapps and Slim Gapps then report back.
EDIT 1: Well. I tried the lastest Carbon nightly 10/17, with both Slim Gapps and normal regular Gapps and the same result, stuck on boot logo.
Both times I flashed a clean install. I'm out of options now.
EDIT 2: When I'm using a kernel from 4.3 and I'm on CWM trying to format Preload, I always get this message:
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p12
Error formatting /preload
Could that be a possible reason?, does anyone else have that same message?
No suggestions?
Am I'm stuck on 4.2?
Sent from my GT-N7000
It's the same for all on the new Cwm. Preload cannot be formatted in Cwm 10.2.
What happens when you clean install a rom without gapps. And boot it.?
nokiamodeln91 said:
It's the same for all on the new Cwm. Preload cannot be formatted in Cwm 10.2.
What happens when you clean install a rom without gapps. And boot it.?
Click to expand...
Click to collapse
I tried that last night actually, clean flash and no Gapps and the same result, stuck on boot screen.
What I've tried so far:
- Flashing different 4.3 ROMs with three different Gapps combinations.
- Flashing Carbon with no Gapps.
Thank you in advance for any ideas you can provide.
I have never encountered such an issue after a clean flash ever. So not sure what's going on there.
When a clean install, do you format system, data and cache and then install the new rom?
nokiamodeln91 said:
I have never encountered such an issue after a clean flash ever. So not sure what's going on there.
When a clean install, do you format system, data and cache and then install the new rom?
Click to expand...
Click to collapse
Yeah, what I do is to do a factory reset twice, then clear cache, then preload twice, data once, system twice and dalvik twice, and only then I flash the ROM and then Gapps.
I let it settle for one hour and then I start the configuration.
It is weird, because if I leave it to boot up normally for the first time, without opening any apps or configurations, it reboots normally. And only when I open Settings or an app, and then I reboot the phone, it gets stuck on the boot logo.
I've even tried to format the SD Card and no difference.
tried without the external SD card inserted?
nokiamodeln91 said:
tried without the external SD card inserted?
Click to expand...
Click to collapse
No, gonna try that tonight.
EDIT 1: Tried lastest Carbon nightly with NO Gapps and no External SD Card. Same crap.
EDIT 2: I found this thread and it basically says that I have to flash Stock, then root it and then do a factory reset.
http://forum.xda-developers.com/showthread.php?t=2427569
Sent from my GT-N7000
SirRhor said:
No, gonna try that tonight.
EDIT 1: Tried lastest Carbon nightly with NO Gapps and no External SD Card. Same crap.
EDIT 2: I found this thread and it basically says that I have to flash Stock, then root it and then do a factory reset.
http://forum.xda-developers.com/showthread.php?t=2427569
Sent from my GT-N7000
Click to expand...
Click to collapse
@SirRhor Please try anothjer work-around before you do anything else:
1. Do all the wipes from a safe kernel
2. Flash Rom (only rom and no gapps)
3. Reboot the system without gapps
4. Now, reboot into recovery (I prefer to leave the system for 10-15 minutes to settle down before rebooting)
5. Flash the correct gapps
6. Reboot and set up ur google account etc.Restore apps or whatever u need from the play store. Dabble with rom settings
7. Reboot!
Did it work now?
knedge said:
@SirRhor Please try anothjer work-around before you do anything else:
1. Do all the wipes from a safe kernel
2. Flash Rom (only rom and no gapps)
3. Reboot the system without gapps
4. Now, reboot into recovery (I prefer to leave the system for 10-15 minutes to settle down before rebooting)
5. Flash the correct gapps
6. Reboot and set up ur google account etc.Restore apps or whatever u need from the play store. Dabble with rom settings
7. Reboot!
Did it work now?
Click to expand...
Click to collapse
I haven't tried that yet, I'll do it tomorrow, but I really doubt it's going to work. I think this whole problem it's caused by errors located on some blocks of memory.
Sent from my GT-N7000
SirRhor said:
I haven't tried that yet, I'll do it tomorrow, but I really doubt it's going to work. I think this whole problem it's caused by errors located on some blocks of memory.
Sent from my GT-N7000
Click to expand...
Click to collapse
Well, can be!
Much abused handset...and much loved too!
But do give it a try!
SirRhor said:
No, gonna try that tonight.
EDIT 1: Tried lastest Carbon nightly with NO Gapps and no External SD Card. Same crap.
EDIT 2: I found this thread and it basically says that I have to flash Stock, then root it and then do a factory reset.
http://forum.xda-developers.com/showthread.php?t=2427569
Sent from my GT-N7000
Click to expand...
Click to collapse
maybe your bootloader corrupted already. Reflash the bootloader only or whole stock rom using ODIN may help ..
I'm glad to inform you that I was able to solve my problem following this guide:
http://forum.xda-developers.com/showthread.php?t=2427569
But instead of flashing the Stock Rooted ROM using Odin, I just flashed it within Philz Recovery.
Right now I'm changing settings and restarting on Carbon 4.3, and so far I have not had any problems.
To anyone experiencing this, just read this thread so you will not waste your time trying ALL the bullcrap I did and instead just try the guide above.
Thank you for everyone who helped me out.
EDIT: Maybe the OP can change the title of this thread to "FIXED" or "SOLVED".
So...which Stock Rooted ROM using to flash?...
heihei123 said:
So...which Stock Rooted ROM using to flash?...
Click to expand...
Click to collapse
Actually, I found a better more permanent solution.
Follow this guide to check for errors on the different partitions:
http://forum.xda-developers.com/showthread.php?t=1396366
Let me know if it helps.
And to answer your question, I flashed a stock ROM from Hungary I think, no problems.
EDIT: Forgot to mention, instead of using the switches described on that guide, I used -f and -y at same time.
Sent from my GT-N7000
Hi everyone,
I've intslled the Android Revolution HD 40.3 on my HTC One.
The process went well. But when it finished the phone keep rebooting, entering recovery mode and exiting and re-rebooting again and again and again ...
I do not have any idea about what to do !!
Help please !!!
Medarioth said:
Hi everyone,
I've intslled the Android Revolution HD 40.3 on my HTC One.
The process went well. But when it finished the phone keep rebooting, entering recovery mode and exiting and re-rebooting again and again and again ...
I do not have any idea about what to do !!
Help please !!!
Click to expand...
Click to collapse
This happened to me a lot on my old Desire HD. Have you tried re-flashing the rom or trying a different one? Also did you clean flash?
JasSingh93 said:
This happened to me a lot on my old Desire HD. Have you tried re-flashing the rom or trying a different one? Also did you clean flash?
Click to expand...
Click to collapse
I can't access the recovery mode to re-flash the rom or try another one.
What exactly do you mean by "clean flash" ? I'm quite a nweebie with HTC and english is not my usual language ^^
Medarioth said:
I can't access the recovery mode to re-flash the rom or try another one.
What exactly do you mean by "clean flash" ? I'm quite a nweebie with HTC and english is not my usual language ^^
Click to expand...
Click to collapse
Ah okay. I would then flash a custom recovery. You can access the bootloader correct? What method did you use to install the rom? Clean flash or wipe is when you erase all the phone's system files, leaving a blank slate for a new rom to be installed on, and should be done before installing a brand new rom to avoid any issues.
http://forum.xda-developers.com/showthread.php?t=2568662
This is the link to the recovery image I used, it's the latest clockwordmod touch recovery. Very easy to flash as long as you have fast boot setup correctly. Once you have a working recovery you should be able to try a re-flash.
JasSingh93 said:
Ah okay. I would then flash a custom recovery. You can access the bootloader correct? What method did you use to install the rom? Clean flash or wipe is when you erase all the phone's system files, leaving a blank slate for a new rom to be installed on, and should be done before installing a brand new rom to avoid any issues.
http://forum.xda-developers.com/showthread.php?t=2568662
This is the link to the recovery image I used, it's the latest clockwordmod touch recovery. Very easy to flash as long as you have fast boot setup correctly. Once you have a working recovery you should be able to try a re-flash.
Click to expand...
Click to collapse
Well I entered Recovery mode through Rom Manager[/URL]clokworkmod () then used "install zip from sdcard".
I chose to keep my old data and don't make a factory reset.
The link you gave redirect me for a post of yours.
Medarioth said:
Well I entered Recovery mode through Rom Manager[/URL]clokworkmod () then used "install zip from sdcard".
I chose to keep my old data and don't make a factory reset.
Click to expand...
Click to collapse
Was the recovery still stock or was a custom one flashed? Which process did you follow to root the phone? Since you can't access the recovery at the moment is suggesting it is stock. A failed rom install shouldn't corrupt recovery
JasSingh93 said:
Was the recovery still stock or was a custom one flashed? Which process did you follow to root the phone? Since you can't access the recovery at the moment is suggesting it is stock. A failed rom install shouldn't corrupt recovery
Click to expand...
Click to collapse
I remember I've unlocked the bootloader.
I used the method described on this french website : phonandroid.com/tutoriel-comment-rooter-son-htc-one.html
On the bootloader now, i can do a factory reset. Can it be a solution ? will it or not delete the root ?
Medarioth said:
I remember I've unlocked the bootloader.
I used the method described on this french website : phonandroid.com/tutoriel-comment-rooter-son-htc-one.html
On the bootloader now, i can do a factory reset. Can it be a solution ? will it or not delete the root ?
Click to expand...
Click to collapse
I'm not sure, since you have tried to flash another rom, a factory reset might not solve the issue. Trying shouldn't brick the phone but I can't say for sure, sorry!
The method looks similar to the one I used. Could you try following from step 6? but using a different recovery.img. I used the clockwokmod touch from http://forum.xda-developers.com/showthread.php?t=2173863
JasSingh93 said:
I'm not sure, since you have tried to flash another rom, a factory reset might not solve the issue. Trying shouldn't brick the phone but I can't say for sure, sorry!
The method looks similar to the one I used. Could you try following from step 6? but using a different recovery.img. I used the clockwokmod touch from http://forum.xda-developers.com/showthread.php?t=2173863
Click to expand...
Click to collapse
yehaaaa! I can now access the ClockworkMod Recovery
Should I try to re-install the rom ? a simple reboot ? ^^
Medarioth said:
yehaaaa! I can now access the ClockworkMod Recovery
Should I try to re-install the rom ? a simple reboot ? ^^
Click to expand...
Click to collapse
Nice! Glad you have working recovery. Yes I would reinstall the rom now, and I would recommend that you wipe the system files, (except SD Card partition of course) to reduce the chance of boot loops etc
JasSingh93 said:
Nice! Glad you have working recovery. Yes I would reinstall the rom now, and I would recommend that you wipe the system files, (except SD Card partition of course) to reduce the chance of boot loops etc
Click to expand...
Click to collapse
ok will try and keep you updated
Medarioth said:
ok will try and keep you updated
Click to expand...
Click to collapse
Ok, you shouldn't have any problems anymore :fingers-crossed:
Medarioth said:
ok will try and keep you updated
Click to expand...
Click to collapse
doesn't work :/ after finishing the installation the phone reboot but it's stuck on the boot logo
Medarioth said:
doesn't work :/ after finishing the installation the phone reboot but it's stuck on the boot logo
Click to expand...
Click to collapse
Could you send me a link to the rom you flashed? Try downloading a different rom. As you can't boot a ROM your only option may be to use ADB to push a new ROM onto your phone's storage.
See this: http://forum.xda-developers.com/showthread.php?t=2317989
EDIT: Sorry, that link is for the other recovery. Use this one instead http://forum.xda-developers.com/showthread.php?t=1667929
My bad
JasSingh93 said:
Could you send me a link to the rom you flashed? Try downloading a different rom. As you can't boot a ROM your only option may be to use ADB to push a new ROM onto your phone's storage.
See this: http://forum.xda-developers.com/showthread.php?t=2317989
EDIT: Sorry, that link is for the other recovery. Use this one instead http://forum.xda-developers.com/showthread.php?t=1667929
My bad
Click to expand...
Click to collapse
I used the rom on this link : androidrevolution.nl/downloader/download.php?file=Android_Revolution_HD-One_40.3.zip
Medarioth said:
I used the rom on this link : androidrevolution.nl/downloader/download.php?file=Android_Revolution_HD-One_40.3.zip
Click to expand...
Click to collapse
It may have been a bad download. There isn't really any reason for it to not work, although it does say on the page it "You need TRWP 2.6.3.3 custom recovery!"
Not to worry, you can flash it in no-time. Ok so just as before, just flash a new recovery (again) and use the latest image from here: http://techerrata.com/browse/twrp2/m7/
This should allow you to install the rom as the developers intend. It is strange though, i've never encountered a rom where a specific recovery was needed.
JasSingh93 said:
It may have been a bad download. There isn't really any reason for it to not work, although it does say on the page it "You need TRWP 2.6.3.3 custom recovery!"
Not to worry, you can flash it in no-time. Ok so just as before, just flash a new recovery (again) and use the latest image from here: http://techerrata.com/browse/twrp2/m7/
This should allow you to install the rom as the developers intend. It is strange though, i've never encountered a rom where a specific recovery was needed.
Click to expand...
Click to collapse
done. waiting in progress ....... :fingers-crossed:
Medarioth said:
done. waiting in progress ....... :fingers-crossed:
Click to expand...
Click to collapse
It should definitely work this time! I've actually just flashed TWRP recovery, and I can already say I prefer it over ClockWorkMod!
Medarioth said:
done. waiting in progress ....... :fingers-crossed:
Click to expand...
Click to collapse
Hallelujah after 5 min for rebooting
Just have to reconfigur and reinstal all the apps
thx for your help bro :good:
Medarioth said:
Hallelujah after 5 min for rebooting
Just have to reconfigur and reinstal all the apps
thx for your help bro :good:
Click to expand...
Click to collapse
Yayyy!!! Nice one! Good teamwork we got there in the end! Happy to help
Have fun!!
Im trying to flash a nightly build of CM 11/GAPPS on my Samsung Galaxy S3 (i9305t) it's running TWRP v2.6.3.0 which is the latest version on the TWRP site and this is the error I'm getting. I've wiped dalvik cache and cache and also did a factory reset before flashing CM and GAPPS this is the error I get while trying to flash CM..
Code:
set_metadata_recursive: some changes failed
E: error executing updater binary in zip '/external .......
Error flashing zip '/external_sd/CM/cm-11- ...........
Updating partition details .......
[COLOR="Red"]Failed[/COLOR]
Hopefully someone can help me out with this, there is really no way I can update my TWRP because I'm on the newest version, there's another TWRP for the i9305 which is v2.7.0.0 but my phone is a i9305t..
Thanks for the help guys
Try flashing a different nightly maybe. You could also try flashing it from your internal SD.
ArkThompson said:
Try flashing a different nightly maybe. You could also try flashing it from your internal SD.
Click to expand...
Click to collapse
I tried flashing a different nightly and I also tried flashing from my internal storage. I still get the same error. Can anybody help me please?
Emre1994 said:
I tried flashing a different nightly and I also tried flashing from my internal storage. I still get the same error. Can anybody help me please?
Click to expand...
Click to collapse
Hmm, you should probably make a thread asking if it is safe to flash i9305 recoveries on your i9305t. If it is, then try flashing Philz recovery (http://forum.xda-developers.com/galaxy-s3/orig-development/i93xx-philz-touch-t2002953) and installing CM with that.
ArkThompson said:
Hmm, you should probably make a thread asking if it is safe to flash i9305 recoveries on your i9305t. If it is, then try flashing Philz recovery (http://forum.xda-developers.com/galaxy-s3/orig-development/i93xx-philz-touch-t2002953) and installing CM with that.
Click to expand...
Click to collapse
I kind of prefer TWRP I've used CWM and I don't really like it that much. It's taken me nearly 3 days to flash CM it shouldn't really take this long. I'm just trying to find a way to successfully flash it I don't really want to use another different recovery now.
Emre1994 said:
I kind of prefer TWRP I've used CWM and I don't really like it that much. It's taken me nearly 3 days to flash CM it shouldn't really take this long. I'm just trying to find a way to successfully flash it I don't really want to use another different recovery now.
Click to expand...
Click to collapse
You used CWM on your i9305t? I don't really see why it matters which recovery you use so long as it works, they all pretty much do the same thing.
ArkThompson said:
You used CWM on your i9305t? I don't really see why it matters which recovery you use so long as it works, they all pretty much do the same thing.
Click to expand...
Click to collapse
CWM gave me the same error, I'm not that fussed about recoveries at the moment. I'm trying to find out why it has taken me so long to flash something as simple as CM and why is it giving me these errors.
Thank you.
Emre1994 said:
CWM gave me the same error, I'm not that fussed about recoveries at the moment. I'm trying to find out why it has taken me so long to flash something as simple as CM and why is it giving me these errors.
Thank you.
Click to expand...
Click to collapse
The problem is definitely recovery related. Like I said before, try and find out whether you can flash i9305 recoveries on it and if so flash Philz. You could also try putting older versions of TWRP on it until you find one that works.
ArkThompson said:
The problem is definitely recovery related. Like I said before, try and find out whether you can flash i9305 recoveries on it and if so flash Philz. You could also try putting older versions of TWRP on it until you find one that works.
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-s3/help-i9305/twrp-v2-6-3-0-i9305t-t2874745
I'm still waiting for a reply. And how would I downgrade TWRP to a older version? Just flash the file through odin?
Thanks.
ArkThompson said:
The problem is definitely recovery related. Like I said before, try and find out whether you can flash i9305 recoveries on it and if so flash Philz. You could also try putting older versions of TWRP on it until you find one that works.
Click to expand...
Click to collapse
I've just tried 3 previous versions of TWRP and I'm still getting the same error..
Emre1994 said:
I've just tried 3 previous versions of TWRP and I'm still getting the same error..
Click to expand...
Click to collapse
Which version of cwm did you try earlier?
ArkThompson said:
Which version of cwm did you try earlier?
Click to expand...
Click to collapse
I honestly forget but it was the version without the touch feature and it gave me a similar or exact error as what I'm getting now.