Related
So I'm currently running Cyanogenmod version 10.2.0 .. Android 4.3.1.
I've updated to the newest version of TWRP.
I factory wipe, then try to install a different ROM.. for example I've tried PA & AOKP.
Every time I try this it fails within 1 second and I have to restore a backup and go back to Cyanogenmod.
EDIT: I have a T-Mobile Galaxy S3
I have attached an image of when I get an error when I try to flash.
UPDATE:
Alright so I was able to get past that error by going into advanced wipe and selecting "System". Now when I flash I get a new error. I am attaching a new picture.
You need to give more info on the error
Sent from my SGH-M919 using Tapatalk
serio22 said:
You need to give more info on the error
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I'm at work now. I'll post and update with the error later.
Do you have a t-mobile s3? If you are from a different carrier such as wind mobile I could know the problem. I also had a problem flashing 4.3 Roms with my t999v wind s3.
Sent from my SGH-T999 using xda app-developers app
spartan268 said:
Do you have a t-mobile s3? If you are from a different carrier such as wind mobile I could know the problem. I also had a problem flashing 4.3 Roms with my t999v wind s3.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Mine is T-Mobile. I'm still at work til 2AM EST. I'll probably post my error tomorrow.
Alright guys, I attached a screenshot (picture lol) of my phone and the error I am getting when I try to flash different ROMs. Any help?
Alright guys.. I was able to get past that other error but now I have a new one when trying to install a new ROM.
Here is a screenshot of the error.
Shallwhat said:
Alright guys.. I was able to get past that other error but now I have a new one when trying to install a new ROM.
Here is a screenshot of the error.
Click to expand...
Click to collapse
Update your recovery. You're using TWRP 2.5.5.0 when the latest one is 2.6.3.1. If you can't boot into Android, Odin the TWRP recovery. Also, make sure you completely wipe your internal storage before flashing a custom ROM. If that custom ROM isn't working for you, try another one to see if that flashes since that would indicate that the custom ROM you're trying to flash could potentially be a bad download.
You also need to post more information about your phone.
Which custom ROM are you using?
Which kernel are you using or trying to use?
etc etc.
Noobiologist said:
Update your recovery. You're using TWRP 2.5.5.0 when the latest one is 2.6.3.1. If you can't boot into Android, Odin the TWRP recovery. Also, make sure you completely wipe your internal storage before flashing a custom ROM. If that custom ROM isn't working for you, try another one to see if that flashes since that would indicate that the custom ROM you're trying to flash could potentially be a bad download.
You also need to post more information about your phone.
Which custom ROM are you using?
Which kernel are you using or trying to use?
etc etc.
Click to expand...
Click to collapse
I've tried flashing multiple ROMS.. Slimbeam.. AOKP.. ParanoidAndroid.. I've downloaded from GOOManager and I've also downloaded from external links and put on my external SD card. Nothing works. Like I said in the OP I am running Cyanogenmod 10.2.. Android 4.3.1. I'm using the Ktweaker kernel.
I updated my TWRP from Goomanager and it only updated to 2.5.5.0. How do I get it to update to 2.6.3.1?
So I just went to update TWRP from goomanager again and when it went to download it failed because "invaid MD5 sum".
Edit: So I tried updating again and it said it was successful. I rebooted into recovery and it still says 2.5.0.0
I'm lost.
Same problem happened to me last night, I tried to install the modem again but the same error keep coming up.
To everyone with issues updating recovery. Goo has a openrecovery script issue. Your best bet is to flash latest Recovery using Odin. You may choose to use Mobile Odin if you feel like it.
Can't restore anything except Kitkat
I keep getting the same error, except I can't flash or restore any rom that isn't kitkat (all the kitkat roms are buggy so i want 4.3 back). I reflashed twrp 2.6.3.1 with odin but its still not letting me flash anything.
Also if it helps I can't copy anything from the internal SD to the external SD using twrp file manager.
Older Rom's backups can't be restored due to file system changes. You will have to wipe everything and flash fresh if you want 4.3
I tried the latest version of TWRP, and I'm on StockROM by TeamInferno. I got V7 and I saw an update on it last night (V8) so I downloaded it and tried to install it fom Clockworkmod recovery and it didn't work so I tried TWRP and the same thing happened. Do I have to wipe everything to update my ROM?
Nothing will flash except Kitkat
Perseus71 said:
Older Rom's backups can't be restored due to file system changes. You will have to wipe everything and flash fresh if you want 4.3
Click to expand...
Click to collapse
Ive tried that multiple times. once the Odin flashable tw 4.3 downloads, I'm going to try that but I can't flash any fresh roms using twrp except 4.4 (Jellybam to be specific).
I tried Stockorama 4.3 tw, but it would just reboot after getting past the "samsung galaxy sIII" screen (tried insecure kernal too). I'm wondering if I'm in a weird soft brick or something
Shallwhat said:
So I just went to update TWRP from goomanager again and when it went to download it failed because "invaid MD5 sum".
Edit: So I tried updating again and it said it was successful. I rebooted into recovery and it still says 2.5.0.0
I'm lost.
Click to expand...
Click to collapse
Did odin flash of the most current recovery take care of your issue?
Hastily spouted for your befuddlement
GodLik3 said:
I tried the latest version of TWRP, and I'm on StockROM by TeamInferno. I got V7 and I saw an update on it last night (V8) so I downloaded it and tried to install it fom Clockworkmod recovery and it didn't work so I tried TWRP and the same thing happened. Do I have to wipe everything to update my ROM?
Click to expand...
Click to collapse
What was the specific error message when flashing ?
QuatroQuatro said:
Ive tried that multiple times. once the Odin flashable tw 4.3 downloads, I'm going to try that but I can't flash any fresh roms using twrp except 4.4 (Jellybam to be specific).
I tried Stockorama 4.3 tw, but it would just reboot after getting past the "samsung galaxy sIII" screen (tried insecure kernal too). I'm wondering if I'm in a weird soft brick or something
Click to expand...
Click to collapse
What is your TWRP Version ? Also what is your Bootloader version ? (No its not the baseband)
My bootloader is T999UVUEMJC
My baseband is uvuemjc
TWRP is version 2.6.3.1 (I've also tried 2.6.3.0)
I think it got updated bootloader/baseband when I odin flashed stock tw 4.3 (the only jellybean ROM that works)
I also made a backup of my 4.4, but it wouldn't let me restore even that.
You have been talking about 2 different things.
1. Flash a New Rom - Either Touchwiz or AOSP. $.3 or newer.
2. Restore a Rom - I think you are talking about a Nandroid Restore.
If you are referring to Point 1 as "Restore Rom" then you need to change terminology in order to help us understand your problem correctly. Re-Flashing a rom that you used to have is still Flashing not "Restore".
With that UVUEMJC Bootloader, you can completely forget about flashing previous Touchwiz Firmwares such as UVDMD5 or UVDLJC. If you tried them, you WILL brick your phone. If you tried Custom Touchwiz Roms based on those 2 firmwares, it may or may not work.
Now if you are trying to flash a AOSP Rom, either 4.3 or Kitkat 4.4, and you do have latest TWRP, (2.6.3.1), please specify the error message in detail.
You must do Factory Reset and Wipe Dalvik + Cache in the Recovery before flashing the AOSP Roms.
My I747 is currently running Carbon Rom nightly 20131102 (4.3.1), it's quite old and I want to upgrade to 4.4.
So last night I nandroid backup , format system, data, flashed Carbon KK on it, then gapps, data, cache, delvik, reboot. But it stayed at the CM alien. I reflashed several times but still stuck at there. But I can nandroid back so I'm kind of fine now. But anyone know why?
Second, I notice my \0\ folder is under sdcard\download\0\ than usual sdcard\0\, I must have done something wrong when I first flash the carbon but I don't know what it is. I usually put my .zip in download, could that be why? Could that cause the bricking I have with KK?
Last, I know there's a flash counter and when I first root/flash last year, I went thru many things to avoid that&IMEI, instead of directly flashing a recovery. I think that could be the source of the problems above??? Now 1 year is up and my warranty is already over so I don't have to worry about the counter anymore. If I want to redo everything, and have to noobiest/simpliest method to flash to KK, what should I do?
Sorry if I lack any essential information. I'd be happy to find it to help.
Did you update to the latest CWM before flashing the ROM? Is your current bootloader supported by the ROM?
Not the latest but 6.0.4.3
I'll update it to 6.0.4.7 and try again.
Unfortunately I don't know if my bootloader is supported. I don't really know how to find mine.
I would update to the latest CWM and then try to flash a 4.4.2 custom ROM. If it doesn't install, it should generate an error message.
Most custom ROMs will look for a particular bootloader. If the bootloader is not found, CWM will give you get prop errors.
audit13 said:
I would update to the latest CWM and then try to flash a 4.4.2 custom ROM. If it doesn't install, it should generate an error message.
Most custom ROMs will look for a particular bootloader. If the bootloader is not found, CWM will give you get prop errors.
Click to expand...
Click to collapse
Thanks, I'll try when I get home.
I installed the ROM fine last night without any error. So I believe the bootloader is supported then.
afyaff said:
Thanks, I'll try when I get home.
I installed the ROM fine last night without any error. So I believe the bootloader is supported then.
Click to expand...
Click to collapse
To be sure, look at the bootloaders mentioned in the ROM's updater script.
Phone: Samgsun Galazy SIII
Model: SPH-I710
Carrier Sprint
Originally rooted 4.2 with ClockworkMod bootloader and SuperUser
Updated to 4.3 without issue.
Sometime in the past 6 months, lost root access, but wasn't needing it, so no biggie.
Today: Saw system update for android 4.4
ClockworkMod boot loader startup in the update process, and did as I always have, installing the unknown zip (which is su) and fixing root and boom.
Boot looped at the blue glowy samgsung screen.
I have tried wiping the cache's and now have even toasted my user data so I have to rebuild everything again ANYWAY, but that damn phone still won't boot!!!!
Where is (not through rapidgator bull****) the stock rom I need to ODIN transfer to get this paperweight to be a phone again?
thanks
Jaeden "Sifo Dyas" al'Raec Ruiner
JaedenRuiner said:
Phone: Samgsun Galazy SIII
Model: SPH-I710
Carrier Sprint
Originally rooted 4.2 with ClockworkMod bootloader and SuperUser
Updated to 4.3 without issue.
Sometime in the past 6 months, lost root access, but wasn't needing it, so no biggie.
Today: Saw system update for android 4.4
ClockworkMod boot loader startup in the update process, and did as I always have, installing the unknown zip (which is su) and fixing root and boom.
Boot looped at the blue glowy samgsung screen.
I have tried wiping the cache's and now have even toasted my user data so I have to rebuild everything again ANYWAY, but that damn phone still won't boot!!!!
Where is (not through rapidgator bull****) the stock rom I need to ODIN transfer to get this paperweight to be a phone again?
thanks
Jaeden "Sifo Dyas" al'Raec Ruiner
Click to expand...
Click to collapse
Seems strange that this happened. Since you have a custom recovery, the OTA should have failed. This will put you on 4.4: http://forum.xda-developers.com/showthread.php?t=2738533 . If you are bootlooping, you could try to flash another rom. I would go with an MK3 zip though like the stock one, moar, wicked, project X...but make sure it is 4.3 (MK3).
lvpre said:
Seems strange that this happened. Since you have a custom recovery, the OTA should have failed. This will put you on 4.4: http://forum.xda-developers.com/showthread.php?t=2738533 . If you are bootlooping, you could try to flash another rom. I would go with an MK3 zip though like the stock one, moar, wicked, project X...but make sure it is 4.3 (MK3).
Click to expand...
Click to collapse
I eventually found a 4.4.2 full stock ROM and was able to get that over. Of course this wasn't until after some sight suggested a wipe user data could help, so I'm re-building the phone from the base...*sigh* It happens. I'm about due for an upgrade anyway, so I can make due.
Thanks for the response,
J"SD"a'RR
Not sure what happened, but this is what's going' on. I'm working with SM-T210R / updated to the 4.4.2 - Did not like the issues with Custom Recoveries, so I got into TWRP - Restored my stock rom backup and everything restored fine and as expected. I went to Root the device, using RootJunky's TWRP recovery and root on YouTube (which I've done many times and never had an issue - I'm not a noob, but, still have a lot to learn) Anyways - when you go swipe to reboot the system, TWRP asks you about installing Supersu for Root access, and of course, you go with it. Well, since that swipe - it keeps rebooting into TWRP - I cant get to the system. I used Odin to install Philz and same thing, kept rebooting into Philz. I've tried re-restoring my back up and now it wont .... it acts like it is, but then it keeps throwing me back into the custom recovery being used ... any ideas or help is greatly appreciated!
PS - Thank you to gr8nole and RootJunky - I'm always using your guys' methods and suggestions.
jonstowe78 said:
Not sure what happened, but this is what's going' on. I'm working with SM-T210R / updated to the 4.4.2 - Did not like the issues with Custom Recoveries, so I got into TWRP - Restored my stock rom backup and everything restored fine and as expected. I went to Root the device, using RootJunky's TWRP recovery and root on YouTube (which I've done many times and never had an issue - I'm not a noob, but, still have a lot to learn) Anyways - when you go swipe to reboot the system, TWRP asks you about installing Supersu for Root access, and of course, you go with it. Well, since that swipe - it keeps rebooting into TWRP - I cant get to the system. I used Odin to install Philz and same thing, kept rebooting into Philz. I've tried re-restoring my back up and now it wont .... it acts like it is, but then it keeps throwing me back into the custom recovery being used ... any ideas or help is greatly appreciated!
PS - Thank you to gr8nole and RootJunky - I'm always using your guys' methods and suggestions.
Click to expand...
Click to collapse
Install stock recovery from Odin to get out of recovery bootloop
Sent from my SM-T211 using XDA Free mobile app
sscsps said:
Install stock recovery from Odin to get out of recovery bootloop
Sent from my SM-T211 using XDA Free mobile app
Click to expand...
Click to collapse
ok I will try that now ... I hope youre right!
If you reboot to recovery using any method other than the three button reboot, you'll be stuck in recovery.
Sent from my ATRIX HD using XDA Free mobile app
bmatney said:
If you reboot to recovery using any method other than the three button reboot, you'll be stuck in recovery.
Sent from my ATRIX HD using XDA Free mobile app
Click to expand...
Click to collapse
Well, yeah, that's the reason,
According to gr8nole, bootloader is responsible for this, the updated version of bootloader have this problem
Sent from my SM-T211 using XDA Free mobile app
bmatney said:
If you reboot to recovery using any method other than the three button reboot, you'll be stuck in recovery.
Sent from my ATRIX HD using XDA Free mobile app
Click to expand...
Click to collapse
That's IF you are using the Stock 4.4.2 ... I restored my Stock 4.1.2 before all this started happening ... Regardless, thank you guys for your suggestions, but its all good now. After work I came home and decided to give it one more try, using Odin to put Philz on and go from there, and this time it took. Once I got Philz on, I was able to (again) restore my 4.1.2 stock backup (fix the flickering screen of course) and the get back to Nolekat v1.9 - thank GOD!
jonstowe78 said:
That's IF you are using the Stock 4.4.2 ... I restored my Stock 4.1.2 before all this started happening ... Regardless, thank you guys for your suggestions, but its all good now. After work I came home and decided to give it one more try, using Odin to put Philz on and go from there, and this time it took. Once I got Philz on, I was able to (again) restore my 4.1.2 stock backup (fix the flickering screen of course) and the get back to Nolekat v1.9 - thank GOD!
Click to expand...
Click to collapse
No, it can happen if you are on 4.1.2 too, it happened to me on my SM-T211 while running 4.1.2 and I did used a software method to reboot to recovery and was stuck in recovery bootloop
Sent from my SM-T211 using XDA Free mobile app
jonstowe78 said:
That's IF you are using the Stock 4.4.2 ... I restored my Stock 4.1.2 before all this started happening ... Regardless, thank you guys for your suggestions, but its all good now. After work I came home and decided to give it one more try, using Odin to put Philz on and go from there, and this time it took. Once I got Philz on, I was able to (again) restore my 4.1.2 stock backup (fix the flickering screen of course) and the get back to Nolekat v1.9 - thank GOD!
Click to expand...
Click to collapse
It will happen if you ever updated the firmware once, no matter if you revert back to previous version later
Sent from my SM-T211 using XDA Free mobile app
sscsps said:
It will happen if you ever updated the firmware once, no matter if you revert back to previous version later
Sent from my SM-T211 using XDA Free mobile app
Click to expand...
Click to collapse
Good to know ... GREAT, so since I updated that ONE time, from now on I can NEVER boot into recovery via software? It'll always be the 3B method .... that sucks! lol
jonstowe78 said:
Good to know ... GREAT, so since I updated that ONE time, from now on I can NEVER boot into recovery via software? It'll always be the 3B method .... that sucks! lol
Click to expand...
Click to collapse
Yes
Unless someone makes a fix for that!
Sent from my SM-T211 using XDA Free mobile app
jonstowe78 said:
That's IF you are using the Stock 4.4.2 ... I restored my Stock 4.1.2 before all this started happening ... Regardless, thank you guys for your suggestions, but its all good now. After work I came home and decided to give it one more try, using Odin to put Philz on and go from there, and this time it took. Once I got Philz on, I was able to (again) restore my 4.1.2 stock backup (fix the flickering screen of course) and the get back to Nolekat v1.9 - thank GOD!
Click to expand...
Click to collapse
I've been trying to find a way to downgrade back to 4.1.2 after finding out about kitkat's flaws. After I installed it, I noticed three things:
- NO extSD card permission
- FASTER battery drainage (it takes a whole day to charge it back from 0)
- Games like Temple Run can no longer be played cause tilt sensor malfunctions - accelerometer issues)
The first two are a major let down. If I had known about this prior the upgrade, I would have kept JB 4.1.2.
Now I'm looking for ways to safely downgrade back to Jelly Bean. From what I'd read, people are getting stuck in custom recovery because the kitkat bootloader or whatever is not compatible (or something like that)? Also, those who have successfully managed to get back to JB now have the issue of not being able to charge their sm-t210R unless it's turned ON. So if we fix one issue, we still got the other.
@jonstowe78, are you having any issues with charging while your device is turned off?
I read about flashing Philz custom recovery for sm-t20R, and after a (failed) attempt to root my tab 3 (which put me off from rooting), I know a bit about the 3B method to reboot. I flashed a custom 4.1.2 JB stock rom using Odin and that's how I got rid of the messed up screen that happened after I rooted.
I would LIKE to root to NoleKat, but like I said, one bad experience with rooting, forever leery of it. Unless someone can help me, please?
sscsps said:
Install stock recovery from Odin to get out of recovery bootloop
Sent from my SM-T211 using XDA Free mobile app
Click to expand...
Click to collapse
Ditto that. I got the firmware from sammobile.com & flashed (AP mode in Odin 3.09) and I was no longer stuck. At that point, I had stock 4.4.2. I then flashed phil via Odin 3.09 (AP) - the gr8nole version (check the nolekat thread) and was able to install any ROM I wanted.
Good luck
ameva said:
I've been trying to find a way to downgrade back to 4.1.2 after finding out about kitkat's flaws. After I installed it, I noticed three things:
- NO extSD card permission
- FASTER battery drainage (it takes a whole day to charge it back from 0)
- Games like Temple Run can no longer be played cause tilt sensor malfunctions - accelerometer issues)
The first two are a major let down. If I had known about this prior the upgrade, I would have kept JB 4.1.2.
Now I'm looking for ways to safely downgrade back to Jelly Bean. From what I'd read, people are getting stuck in custom recovery because the kitkat bootloader or whatever is not compatible (or something like that)? Also, those who have successfully managed to get back to JB now have the issue of not being able to charge their sm-t210R unless it's turned ON. So if we fix one issue, we still got the other.
@jonstowe78, are you having any issues with charging while your device is turned off?
I read about flashing Philz custom recovery for sm-t20R, and after a (failed) attempt to root my tab 3 (which put me off from rooting), I know a bit about the 3B method to reboot. I flashed a custom 4.1.2 JB stock rom using Odin and that's how I got rid of the messed up screen that happened after I rooted.
I would LIKE to root to NoleKat, but like I said, one bad experience with rooting, forever leery of it. Unless someone can help me, please?
Click to expand...
Click to collapse
Download stock md5 of 4.1.2 for your country from sammobile.com and flash it from Odin to downgrade to 4.1.2,
For rooting, take a look at this:
http://forum.xda-developers.com/showthread.php?t=2822307
How to root any android device, easy, Noob friendly!
Sent from my SM-T211 using XDA Free mobile app
sscsps said:
Download stock md5 of 4.1.2 for your country from sammobile.com and flash it from Odin to downgrade to 4.1.2,
For rooting, take a look at this:
http://forum.xda-developers.com/showthread.php?t=2822307
How to root any android device, easy, Noob friendly!
Sent from my SM-T211 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you for your feedback!
The truth is, after I made that post, I did a lot of reading on custom recovery like TWRP, Philz Touch, and CWM, and then I read some more about NoleKat v2.0, and how it basically is like KK but it gives you root access and sd card rights back, so now I've decided to not downgrade. I've learned a lot from when I first tried to root (which ended in failure and a dim screen with flickering colors), so I'm more confident in how the process goes.
I was wondering though. If I install custom recovery (from any of those three), will they wipe my data? I know you can back up your data using the custom recovery, but which one do you think is the least likely to have issues with KK bootloader (assuming the custom recovs have all been updated to 'play nicely' with the KK so people won't get stuck in custom recov bootloop?)
ameva said:
Thank you for your feedback!
The truth is, after I made that post, I did a lot of reading on custom recovery like TWRP, Philz Touch, and CWM, and then I read some more about NoleKat v2.0, and how it basically is like KK but it gives you root access and sd card rights back, so now I've decided to not downgrade. I've learned a lot from when I first tried to root (which ended in failure and a dim screen with flickering colors), so I'm more confident in how the process goes.
I was wondering though. If I install custom recovery (from any of those three), will they wipe my data? I know you can back up your data using the custom recovery, but which one do you think is the least likely to have issues with KK bootloader (assuming the custom recovs have all been updated to 'play nicely' with the KK so people won't get stuck in custom recov bootloop?)
Click to expand...
Click to collapse
Gr8nole have updated the recovery for SM-T210 to not stuck in recovery bootloop(it used to happen only and only if you use any software method to enter in to recovery mode) download cwm for SM-T210 and you are good to go,
And none of the recovery will wipe your data, even if you select factory wipe from custom recovery, it will only delete all the installed applications,
And of you flash(install) a recovery, it won't delete any data/app
Sent from my SM-T211 using XDA Free mobile app
@gr8nole Please prepare two PARAM image from JB and KitKat firmware. Try both PARAM on your device, maybe one of it is the solution of this recovery bootloop issue.
To create Odin flashable param:
Code:
tar -H ustar -c param.bin > param.tar
md5sum -t param.tar >> param.tar
mv param.tar param.tar.md5
sscsps said:
Gr8nole have updated the recovery for SM-T210 to not stuck in recovery bootloop(it used to happen only and only if you use any software method to enter in to recovery mode) download cwm for SM-T210 and you are good to go,
And none of the recovery will wipe your data, even if you select factory wipe from custom recovery, it will only delete all the installed applications,
And of you flash(install) a recovery, it won't delete any data/app
Sent from my SM-T211 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks again for your feedback!
Wait, you mean the installed apps that came pre-installed with KK? Because that's what it sounds like if you say that the recovery will not wipe my data like game progress, rss feeds, recordings, etc?
So if that's true, should I still create a backup through the custom recovery?
Would that be called a dirty flash? Or a full wipe?
I've spent nearly this whole day reading through the NoleKat thread from v0.1 to v.2. I can see it's come a long way. Gr8nole is truly an amazing developer! I've seen issues like charging offline, recovery bootloop, boot animation issues fixed as each new update gets better and better.
ameva said:
Thanks again for your feedback!
Wait, you mean the installed apps that came pre-installed with KK? Because that's what it sounds like if you say that the recovery will not wipe my data like game progress, rss feeds, recordings, etc?
So if that's true, should I still create a backup through the custom recovery?
Would that be called a dirty flash? Or a full wipe?
I've spent nearly this whole day reading through the NoleKat thread from v0.1 to v.2. I can see it's come a long way. Gr8nole is truly an amazing developer! I've seen issues like charging offline, recovery bootloop, boot animation issues fixed as each new update gets better and better.
Click to expand...
Click to collapse
No, not the pre-installed apps, but the apps you installed will be uninstalled is you perform a wipe operation from recovery(custom)
It's just a apps wipe, it will leave only personal data like photos, songs, etc.
Sent from my SM-T211 using XDA Free mobile app
Hmm, I guess I'm just going to have to do a dirty flash then, mainly because I have this one game app, and even though it stores my game info in a folder, if I delete the app, I lose my account, and it's huge hassle to get it back.
So just to be clear, dirty flashing is basically no factory wipe/reset at all, right? Then what does the davlik or wiping cache do? I think we're still suppose to do that after flashing custom rom.
ameva said:
Hmm, I guess I'm just going to have to do a dirty flash then, mainly because I have this one game app, and even though it stores my game info in a folder, if I delete the app, I lose my account, and it's huge hassle to get it back.
So just to be clear, dirty flashing is basically no factory wipe/reset at all, right? Then what does the davlik or wiping cache do? I think we're still suppose to do that after flashing custom rom.
Click to expand...
Click to collapse
You can flash it without any risk of anything being deleted, flashing recovery won't delete anything (neither any app)
Cache memory stores dynamic things which helps apps to run smoothly, if you wipe that, your apps will have to make that memory again(when it runs for the first time/first time after you clear cache) to run smoothly in future, but Delvik cache helps android to run smoothly, every rom need different things to run smoothly, so we need to clear previous rom's Delvik cache in order to allow new rom to create is own Delvik cache of its own, this is the reason the first boot takes a bit longer time to compleat because it takes time to write is own Delvik cache, sometimes, different roms' Delvik cache conflicts, so it can be like you get stuck on boot screen, just clear Delvik cache to fix it
Hope it is clear, I might be wrong, but this is what I think it is!
Sent from my SM-T211 using XDA Free mobile app
Maybe it's me missing something, I downloaded and installed PA 5.1, build from 20th May which I do not think is an Alpha that I would need to factory reset to do an OTA over.
However today OTA popped up with a update to the 28th May build, the upgrade seems to work but the phone then will not boot up instead I get the initial S3 screen twice with a blank screen in between then it drops in to recovery?
Think I am doing the update right i.e. download in OTA app, click install, phone reboots in to recovery runs install, reboots -- then in theory it should boot back up but at this point I have the above loop and back to recovery...
The recovery that I an using is Philz recovery - added it a couple of nights ago to install the original build of 5.1 and Gapps so that seems to work, there no errors with the OTA as its installed, the caches are being cleared first by the install script everything looks fine until the phone tries to boot back up. Have tried it 3 times now downloading a new copy of the OTA each time in case of corruption and restoring from a good backup on each failure.
Any ideas appreciated?
... and thank you in advance
paped said:
Maybe it's me missing something, I downloaded and installed PA 5.1, build from 20th May which I do not think is an Alpha that I would need to factory reset to do an OTA over.
However today OTA popped up with a update to the 28th May build, the upgrade seems to work but the phone then will not boot up instead I get the initial S3 screen twice with a blank screen in between then it drops in to recovery?
Think I am doing the update right i.e. download in OTA app, click install, phone reboots in to recovery runs install, reboots -- then in theory it should boot back up but at this point I have the above loop and back to recovery...
The recovery that I an using is Philz recovery - added it a couple of nights ago to install the original build of 5.1 and Gapps so that seems to work, there no errors with the OTA as its installed, the caches are being cleared first by the install script everything looks fine until the phone tries to boot back up. Have tried it 3 times now downloading a new copy of the OTA each time in case of corruption and restoring from a good backup on each failure.
Any ideas appreciated?
... and thank you in advance
Click to expand...
Click to collapse
Well, i'm on I9300 and all i can tell you is that i have the same exact problem with the same release, so you're not alone.
I was hoping this new release would work since the one of the 20 may didn't, but this one won't even boot.
I guess I9300 doesn't get love anymore...
You are not alone in this. It is happening with me too since the stable build of 28th May. I tried the on on June 12th too ...but even that is failing as well
How come it is a stable build when it has a bug like this and crashes the phone? Are we making a mistake? Does it require a different kernel or what can I do to make it work?!
~ Manthravadi
I'm stuck with this I have tried the last 3 ota updates with CWM, TWRP and Philz recovery all fail as above. Even tried downloading the full versions and doing a clean install with gapps and they fail. Could be a kernel issue but cannot find anything that states a dependency, is the kernel not part of the download like in a Linux OS? As never upgraded a kernel separately, how would you do that, is it another zip file, any ideas where to get it from?
paped said:
I'm stuck with this I have tried the last 3 ota updates with CWM, TWRP and Philz recovery all fail as above. Even tried downloading the full versions and doing a clean install with gapps and they fail. Could be a kernel issue but cannot find anything that states a dependency, is the kernel not part of the download like in a Linux OS? As never upgraded a kernel separately, how would you do that, is it another zip file, any ideas where to get it from?
Click to expand...
Click to collapse
I actually got it working finally a few days back.
You need to install boeffla kernel version 4 alpha 3 in order get the latest pa rom up and running. Go to boeffla-kernel website. In downloads select the device GT-I 9300. You will find CM12.1 NG version which is not yet stable. In that select version 4 alpha 3. Alpha 6 is latest but does not work too :/ Download Alpha 3 .. a .zip file which can be flashed using TWRP or Philz or CWM.
Wipe cache/dalvik-cache → flash boeffla → flash pa latest → flash pa gapps latest for 5.1
~ Manthravadi
Sent from my GT-I9300 using Tapatalk
I also have problem but thankfully when I did the steps above, it did finally boot but now I have another problem. My S3 boots properly and I can use it for a while then after a few mins it suddenly reboots with boot animation and all and I dunno what to do. It just keeps rebooting after a certain amount of mins.
@Aledresin: glad that I was able to help you. I am not experiencing any such issues at the moment. When the next PA build is released, try to flash it with boeffla 4 alpha 6.
Afaik ..some memory issues were fixed in alpha 6 and as you are using alpha 3..perhaps you are experiencing those issues.
~ Manthravadi
Sent from my GT-I9300 using Tapatalk
Manthravadi said:
I actually got it working finally a few days back.
You need to install boeffla kernel version 4 alpha 3 in order get the latest pa rom up and running. Go to boeffla-kernel website. In downloads select the device GT-I 9300. You will find CM12.1 NG version which is not yet stable. In that select version 4 alpha 3. Alpha 6 is latest but does not work too :/ Download Alpha 3 .. a .zip file which can be flashed using TWRP or Philz or CWM.
Wipe cache/dalvik-cache → flash boeffla → flash pa latest → flash pa gapps latest for 5.1
~ Manthravadi
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Do you happen to have a copy/mirror of "boeffla-kernel-4.0-alpha3-CM12.1-NG-i9300.recovery.zip"
I've been searching for a few days and can't find it anywhere. The official boeffla site no longer hosts this file and a lot of i9300 users need it to run the latest Paranoid OTA.
EDIT: Found it! It's available here: http://boeffla.df-kunde.de/sgs3/boef...load/Test/old/
Thanks to user Hawaiihemd for the info.
paped said:
Think I am doing the update right i.e. download in OTA app, click install, phone reboots in to recovery runs install, reboots -- then in theory it should boot back up but at this point I have the above loop and back to recovery...
Click to expand...
Click to collapse
I had a very similar problem and found that if I let it automatically reboot after flashing, then I was stuck just rebooting to recovery. If I manually shut down after flashing and manually booted, then everything worked fine. You may have the same thing happening here. I also used PhilzTouch and like it a lot. Thanks to the devs!