Related
I've been using liquid smooth since rc3 and have had no issues upgrading until the most current version--rc7. I downloaded the ROM several times to ensure there wasn't any issues with my download, but I encounter the same issue after a clean flash which is the inability to get past the black screen after the Samsung logo. I've performed factory/data resets prior to flashing rc7 but to no avail. I even flashed the latest cm10 nightly build with no issues. I've restored my rc5 nandroid but really want rc7. Any suggestions will be appreciated.
BTW, I posted this here because I'm not allowed to post in the liquid smooth developers forum
try formatting system after the data wipe, then flash rc7.
dmalikyar said:
I've been using liquid smooth since rc3 and have had no issues upgrading until the most current version--rc7. I downloaded the ROM several times to ensure there wasn't any issues with my download, but I encounter the same issue after a clean flash which is the inability to get past the black screen after the Samsung logo. I've performed factory/data resets prior to flashing rc7 but to no avail. I even flashed the latest cm10 nightly build with no issues. I've restored my rc5 nandroid but really want rc7. Any suggestions will be appreciated.
BTW, I posted this here because I'm not allowed to post in the liquid smooth developers forum
Click to expand...
Click to collapse
wipe before flashing, and after flashing again just to make sure, and if that doesn't work, you can always odin back to stock rooted and drop the rc7 files back on your sd card (or unless you drop them on your external sd card, you can flash it immediately after getting the pass notification from odin)
droidstyle said:
try formatting system after the data wipe, then flash rc7.
Click to expand...
Click to collapse
Tried that and it made no difference.
dmalikyar said:
Tried that and it made no difference.
Click to expand...
Click to collapse
try using odin......just remember after you odin back to the root66 image, you have to reinstall CWM and doesn't hurt to make sure ur bootloader is unlocked using the 1.2 version of the ez unlock then flash again
digitalsynner85 said:
wipe before flashing, and after flashing again just to make sure, and if that doesn't work, you can always odin back to stock rooted and drop the rc7 files back on your sd card (or unless you drop them on your external sd card, you can flash it immediately after getting the pass notification from odin)
Click to expand...
Click to collapse
I'll try the Odin route. I'll go back to root66 and try it from there.
dmalikyar said:
I'll try the Odin route. I'll go back to root66 and try it from there.
Click to expand...
Click to collapse
i was having issues with nfc not working and a few other items that other people weren't having and decided that after approximately 500 different flashes that something i flashed for nfc fixes on jellybean or ics roms that didn't support the libs for nfc could've borked something up and just wasn't noticeable until i went to an aosp based rom, and sure enough it worked, so if anything you'll have a nice crispy fresh stock device to play with again if the same issue shows up w/ liquid
digitalsynner85 said:
i was having issues with nfc not working and a few other items that other people weren't having and decided that after approximately 500 different flashes that something i flashed for nfc fixes on jellybean or ics roms that didn't support the libs for nfc could've borked something up and just wasn't noticeable until i went to an aosp based rom, and sure enough it worked, so if anything you'll have a nice crispy fresh stock device to play with again if the same issue shows up w/ liquid
Click to expand...
Click to collapse
now the truth comes out...if you would of gave this information from the get go I too would of said to simply flash back to stock and start fresh. its all in the details folks.
imklaho your
droidstyle said:
now the truth comes out...if you would of gave this information from the get go I too would of said to simply flash back to stock and start fresh. its all in the details folks.
Click to expand...
Click to collapse
I Odin'd root66 and installed the ez unlocker as well as clockworkmod via rom manager. I went into recovery and wiped data/factory reset/wiped cache/wiped dalvik cache. I then installed LS RC7. It went through the installation and indicated that it completed. After I reboot, I briefly see the Samsung logo, then the screen is completely black. No boot animation. I let it set for over 20 mins. and nothing happens. This is absolutely bizarre. I've tried 3 different downloads. I'm at a loss. Is there a way to convert the zip to an img and odin it on?
KT747-Kernel-AOSP-JB-VZW-10-31-2012.zip
I'm still unable to install RC7. However, when I try the KT747 Kernel, I get the same symptoms (black screen after flash). I'm wondering if the symptoms are related. Anyone have this issue flashing KT747?
dmalikyar said:
I'm still unable to install RC7. However, when I try the KT747 Kernel, I get the same symptoms (black screen after flash). I'm wondering if the symptoms are related. Anyone have this issue flashing KT747?
Click to expand...
Click to collapse
I've had a similar situation. I flashed RC7 and afterwards it booted to the liquid not animation and afterwards just went black, I had never experienced that before so I left it for 10 mins and the hit the power button and got no response. I finally did a battery pull and then booted into CWM and fixed permissions, yet again, and it finally booted. I don't know if this will help you any but I hope so. Honestly the way it boots and then stops and starts over reminds me of kexec. Also after having this problem on RC7 I decided to flash PA 2.52 and had the same issue with it and had to do the same steps to make it boot the first time. I am going to odin completely back to stock tonight because I am experiencing a crap load of issues after I flashed RC7.
And yes I clean flash everything, even when I just go to a newer release of what I'm currently running.
Sent by one of my many Anthromorphic Personifications
shangrila500 said:
I've had a similar situation. I flashed RC7 and afterwards it booted to the liquid not animation and afterwards just went black, I had never experienced that before so I left it for 10 mins and the hit the power button and got no response. I finally did a battery pull and then booted into CWM and fixed permissions, yet again, and it finally booted. I don't know if this will help you any but I hope so. Honestly the way it boots and then stops and starts over reminds me of kexec. Also after having this problem on RC7 I decided to flash PA 2.52 and had the same issue with it and had to do the same steps to make it boot the first time. I am going to odin completely back to stock tonight because I am experiencing a crap load of issues after I flashed RC7.
And yes I clean flash everything, even when I just go to a newer release of what I'm currently running.
Sent by one of my many Anthromorphic Personifications
Click to expand...
Click to collapse
Thanks for the tip. I did as you instructed by fixing the permissions after a failed boot but to no avail. I've gone through the process of odin and root66 and then installing ez unlock and CWM but it just won't boot into RC7. I had no issues with RC3 and RC5. I'm at a loss.
dmalikyar said:
Thanks for the tip. I did as you instructed by fixing the permissions after a failed boot but to no avail. I've gone through the process of odin and root66 and then installing ez unlock and CWM but it just won't boot into RC7. I had no issues with RC3 and RC5. I'm at a loss.
Click to expand...
Click to collapse
Have you tried TWRP recovery as opposed to CWM?
shangrila500 said:
Have you tried TWRP recovery as opposed to CWM?
Click to expand...
Click to collapse
I installed twrp and I really like the interface but it didn't resolve the issue of flashing RC7. I've installed paranoid android and can install aokp and cm10 with no problems. I can't install RC7 or slim beans.
Cannot install Liquid Smooth
Yah the guy at Liquid Smooth is kind of a butt wipe. I understand the desire to have a screen capture and a logcat but if the user can't even install the flash how is a screen capture going to help. Maybe a logcat could. But either way why be an A hole about it.
I am having the same issue, I even formatted my system and still LiquidSmooth says it flashed but it just refuses to boot. I have used Odin to install the stock JB 4.1.1 from Poland but I still get the same problem. I do believe it has something to do with having tried CaponMod4NSS_3.0 the day before. Still I would think formatting the system would resolve that.
Any ideas? I will try to install the Samsung 4.1 ROM with Odin to see if that helps.
I much prefer AOSP over TW; however, it is hard to tolerate due to random reboots. What exactly can be causing this? I tried different CPU governors and everything. To my knowledge, this started occuring after I got my new battery, the gorilla gadgets 4500 mah.
If you only started seeing the reboots after the battery then I would look at that if I were you.
Also, what AOSP roms are you using? I've been on CM 10.1, both official and builds I have compiled myself and haven't had a random reboot in months. Last one I remember having was a few weeks after the switchover to the 3.4 kernel.
Chris123NT said:
If you only started seeing the reboots after the battery then I would look at that if I were you.
Also, what AOSP roms are you using? I've been on CM 10.1, both official and builds I have compiled myself and haven't had a random reboot in months. Last one I remember having was a few weeks after the switchover to the 3.4 kernel.
Click to expand...
Click to collapse
I reverted to stock battery. I had a random reboot again. The roms I used are XenonHD, CM10.1, PAC Man, LiquidSmooth. Reboots on all of them.
LegoFarmer said:
I reverted to stock battery. I had a random reboot again. The roms I used are XenonHD, CM10.1, PAC Man, LiquidSmooth. Reboots on all of them.
Click to expand...
Click to collapse
Should I try updating my bootloader? This was rooted and unlocked back in October, so it may not flash modern (4.2.2) roms correctly. What do you think?
Flash the MF1 firmware in recovery, get it here:
http://invisiblek.org/sch-i535/firmware/d2vzw_VRBMF1_firmware.zip
that's more than likely the cause of your reboots, CM doesn't like being on the earlier firmware anymore.
Chris123NT said:
Flash the MF1 firmware in recovery, get it here:
http://invisiblek.org/sch-i535/firmware/d2vzw_VRBMF1_firmware.zip
that's more than likely the cause of your reboots, CM doesn't like being on the earlier firmware anymore.
Click to expand...
Click to collapse
Thanks, I have a bigger problem now, though. I wiped and just tried to re-do everything. I installed jellybean factory and get bootlooped. Used this guide, cannot enter recovery either.
http://forum.xda-developers.com/showthread.php?p=43850592#post43850592
LegoFarmer said:
Thanks, I have a bigger problem now, though. I wiped and just tried to re-do everything. I installed jellybean factory and get bootlooped. Used this guide, cannot enter recovery either.
http://forum.xda-developers.com/showthread.php?p=43850592#post43850592
Click to expand...
Click to collapse
Can you get into download mode? If so try to ODIN back to stock, re-unlock, re-root, and flash back to CM.
Why did you try flashing that anyway?
Chris123NT said:
Can you get into download mode? If so try to ODIN back to stock, re-unlock, re-root, and flash back to CM.
Why did you try flashing that anyway?
Click to expand...
Click to collapse
That's what I tried doing. I had my aosp rom running and decided to start from scratch. I tried using odin to go back to the jellybean ota, when it boots, I stay at boot animation, I can get in download mode though. If I go in recovery, it is just black.
LegoFarmer said:
Thanks, I have a bigger problem now, though. I wiped and just tried to re-do everything. I installed jellybean factory and get bootlooped. Used this guide, cannot enter recovery either.
http://forum.xda-developers.com/showthread.php?p=43850592#post43850592
Click to expand...
Click to collapse
LegoFarmer said:
That's what I tried doing. I had my aosp rom running and decided to start from scratch. I tried using odin to go back to the jellybean ota, when it boots, I stay at boot animation, I can get in download mode though. If I go in recovery, it is just black.
Click to expand...
Click to collapse
Get back into download mode and ODIN again. Once you finish ODIN you're gonna have to get into recovery to wipe data/clear cache so the stock ROM will boot, otherwise it will get stuck at the boot screen.
Chris123NT said:
Get back into download mode and ODIN again. Once you finish ODIN you're gonna have to get into recovery to wipe data/clear cache so the stock ROM will boot, otherwise it will get stuck at the boot screen.
Click to expand...
Click to collapse
What happens is I use the recovery hotkeys, but the screen is black unless I release the hotkeys, in which it just boots normally
Fixed lol. I had to let go of the power button after it vibrated. I can take it from here, thanks, man!!!
Hi guys! I just had got the Photon Q today and successfully got it rooted and successfully got a custom recovery installed on it. The problem is with EVERY ROM i've tried flash, it fails to install properly and aborts the installation. I've tried on both CWM and TWRP, but the result is the same and wont install. Does this have to do with the fact that the ROMs got unified for the multiple Motorola devices? I'm about to try older nightly builds i've found, just so I can have my phone on KitKat. Anyone have any ideas why every ROM is failing to install??
Well, CWM might fail if you are using an older version... However, the latest TWRP should work fine.
What's the error message? Are yo using the latest version?
arrrghhh said:
Well, CWM might fail if you are using an older version... However, the latest TWRP should work fine.
What's the error message? Are yo using the latest version?
Click to expand...
Click to collapse
Yup, i'm using the latest version, 2.7. Anyway, I got it figured out and realized it was my SD card, so I just flashed the ROMs from internal storage instead and it worked fine.
But now i'm having a new problem. Now i'm not getting any service and wifi wont come on. I've flashed custom roms on other phones before and i've never had this problem. It's like this on Carbon, Mokee, and now Cyanogen. I'm gonna keep browsing the forum for some ideas, do you have any idea by any chance?
KoolBurnX8 said:
Now i'm not getting any service and wifi wont come on. I've flashed custom roms on other phones before and i've never had this problem. It's like this on Carbon, Mokee, and now Cyanogen. I'm gonna keep browsing the forum for some ideas, do you have any idea by any chance?
Click to expand...
Click to collapse
This sounds like a result of deleted or formatted /persist partition.
Have you done it? Do you have a backup?
kabaldan said:
This sounds like a result of deleted or formatted /persist partition.
Have you done it? Do you have a backup?
Click to expand...
Click to collapse
Yup, I had a back up, but it failed to restore. I had to go back to stock because I couldn't figure out how to get back my service and wifi for the life of me. I still want to use Carbon, but i'm afraid it'll just go back to no service and no wifi again. Good thing about the stock rom, it seems to update your network profile and PRL for you.
KoolBurnX8 said:
Yup, I had a back up, but it failed to restore. I had to go back to stock because I couldn't figure out how to get back my service and wifi for the life of me. I still want to use Carbon, but i'm afraid it'll just go back to no service and no wifi again. Good thing about the stock rom, it seems to update your network profile and PRL for you.
Click to expand...
Click to collapse
You must be on the stock ROM to update the PRL. Make sure everything works & is updated before flashing a custom ROM.
arrrghhh said:
You must be on the stock ROM to update the PRL. Make sure everything works & is updated before flashing a custom ROM.
Click to expand...
Click to collapse
So I got it back to stock, then just tried the nightly of Pac man rom. It flashed fine, and my data and service are working. It's just my wifi is blacked out now and wont let me turn it on. Any ideas?
KoolBurnX8 said:
So I got it back to stock, then just tried the nightly of Pac man rom. It flashed fine, and my data and service are working. It's just my wifi is blacked out now and wont let me turn it on. Any ideas?
Click to expand...
Click to collapse
Which nightly are you running of PAC? Any logs?
arrrghhh said:
Which nightly are you running of PAC? Any logs?
Click to expand...
Click to collapse
pac_moto_msm8960_4.4.Alpha-1_20140409-051845
The ROM is great I don't wanna go back to stock
Hopefully you mean my recovery log
KoolBurnX8 said:
pac_moto_msm8960_4.4.Alpha-1_20140409-051845
The ROM is great I don't wanna go back to stock
Hopefully you mean my recovery log
Click to expand...
Click to collapse
Is that from flashing PAC...? I don't see anything there from being flashed.
I assume the ROM boots fine if you say data and service are working. I mean logs from Android, like logcat and dmesg.
arrrghhh said:
Is that from flashing PAC...? I don't see anything there from being flashed.
I assume the ROM boots fine if you say data and service are working. I mean logs from Android, like logcat and dmesg.
Click to expand...
Click to collapse
Yeah that was after flashing PAC ROM. I was finally able to do a good wipe of everything and finally got PAC running smoothly. The newest TWRP 2.7.0.1 wont let me do a good wipe, so I had to use 2.3.3.1 to do the wipe. Those versions wouldnt flash the ROMs properly and would fail, so I installed the newest TWRP 2.7.0.1 (again) and now all the ROMs i've flashed work great.
KoolBurnX8 said:
Yeah that was after flashing PAC ROM. I was finally able to do a good wipe of everything and finally got PAC running smoothly. The newest TWRP 2.7.0.1 wont let me do a good wipe, so I had to use 2.3.3.1 to do the wipe. Those versions wouldnt flash the ROMs properly and would fail, so I installed the newest TWRP 2.7.0.1 (again) and now all the ROMs i've flashed work great.
Click to expand...
Click to collapse
I read your other post, that is odd. Not sure why you would have to revert to an older version of TWRP... Actually I'm a bit behind, I'm still on 2.6.3.1 I think. Not sure upgrading my phone would be a good test, since you proved moving from an older to newer version works...
Hmmm. I might just RSD Lite back to stock to see if I can recreate this.
ok guys, stupid question time. i have been out of the hacking game for a while and havent been keeping up with the S3 since i was running a pretty stable version of cyanogenmod. i picked up a S5 last month and the S3 has just been sitting but the wifes phone is on its last leg so i figured i would update the S3 and give it to her since it would be an upgrade to what she has now. i was running CM 4.1.2 and tried to flash the 4.3 AllianceRom. did my usual, updated CWM, downloaded the rom, checked the MD5, flashed the new modem and rom using CWM and everything looked good. then it happened. stuck at the "galaxy SIII" logo screen. nothing got me out of it. wiped everything, tried a reinstall, downloaded the rom again and did an install, nothing. tried another rom and the install failed, tried another rom and again, install failed. so i had a copy of cleanrom 5.6 which is a 4.1.1 rom and damn if that didnt hand as well. so i did a battery pull and luckly it had installed and the phone actually booted up and into android. the only downside is for some reason i cant connect to wifi with the rom. so, i still want to try either 4.3 or 4.4 on this phone so the question is, WTF am i doing wrong that it wont boot? shouldnt i be able to go from 4.1.1 to 4.3 or 4.4 by just using CWM? help a brother out.
Make sure u cwm is the most recent
Sent from my SCH-I535 using XDA Premium 4 mobile app
Mylt1 said:
ok guys, stupid question time. i have been out of the hacking game for a while and havent been keeping up with the S3 since i was running a pretty stable version of cyanogenmod. i picked up a S5 last month and the S3 has just been sitting but the wifes phone is on its last leg so i figured i would update the S3 and give it to her since it would be an upgrade to what she has now. i was running CM 4.1.2 and tried to flash the 4.3 AllianceRom. did my usual, updated CWM, downloaded the rom, checked the MD5, flashed the new modem and rom using CWM and everything looked good. then it happened. stuck at the "galaxy SIII" logo screen. nothing got me out of it. wiped everything, tried a reinstall, downloaded the rom again and did an install, nothing. tried another rom and the install failed, tried another rom and again, install failed. so i had a copy of cleanrom 5.6 which is a 4.1.1 rom and damn if that didnt hand as well. so i did a battery pull and luckly it had installed and the phone actually booted up and into android. the only downside is for some reason i cant connect to wifi with the rom. so, i still want to try either 4.3 or 4.4 on this phone so the question is, WTF am i doing wrong that it wont boot? shouldnt i be able to go from 4.1.1 to 4.3 or 4.4 by just using CWM? help a brother out.
Click to expand...
Click to collapse
You need to use the latest PhilZ Touch Recovery (https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/) (just flash it in your current recovery). It is the best, and it works great. I would first go to "Wipe Data/Factory Reset" and choose to "Clean to Install a New ROM." Then I would go into "Advanced" and wipe dalvik cache. Then I would go into "Mounts and Storage" and format boot and modem. Then I would flash the newest modem (http://www.mediafire.com/download/v0als76t6nmtpbo/DNE1.modem.zip). Then finally install your ROM and then GApps.
yes, CWM was updated just before flashing. i installed the recommended modem for the rom i was installing. not sure why it was stuck at the logo on 4.3 when i flashed a 4.1.1 rom and it booted right up just fine.
resolved. thanks guys.
Mylt1 said:
resolved. thanks guys.
Click to expand...
Click to collapse
Curious to know what you had to do to get it working?
I have two (2) S3's that I need to update and they're both running 4.1.1 ROMs.
Any info would be much appreciated.
CenFlo said:
Curious to know what you had to do to get it working?
I have two (2) S3's that I need to update and they're both running 4.1.1 ROMs.
Any info would be much appreciated.
Click to expand...
Click to collapse
i used the Philz touch CWM found here, http://forum.xda-developers.com/showthread.php?t=2201860 worked like a charm.
jonny30bass said:
You need to use the latest PhilZ Touch Recovery (https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/) (just flash it in your current recovery). It is the best, and it works great. I would first go to "Wipe Data/Factory Reset" and choose to "Clean to Install a New ROM." Then I would go into "Advanced" and wipe dalvik cache. Then I would go into "Mounts and Storage" and format boot and modem. Then I would flash the newest modem (http://www.mediafire.com/download/v0als76t6nmtpbo/DNE1.modem.zip). Then finally install your ROM and then GApps.
Click to expand...
Click to collapse
I did all of the above and I can't get anything to work....
I updated to Philz, updated the modem and went to install a new ROM and it's error'ing out every time?
This phone was rooted from way back and it appears that I may have lost root... It's stuck at the Samsung Galaxy S III boot screen and I'm trying to get it to boot in to recovery at this time.
Edit: Was able to get in to recovery and restoring a backup now. Somethings not right when trying to go to a newer ROM.
CenFlo said:
I did all of the above and I can't get anything to work....
I updated to Philz, updated the modem and went to install a new ROM and it's error'ing out every time?
This phone was rooted from way back and it appears that I may have lost root... It's stuck at the Samsung Galaxy S III boot screen and I'm trying to get it to boot in to recovery at this time.
Edit: Was able to get in to recovery and restoring a backup now. Somethings not right when trying to go to a newer ROM.
Click to expand...
Click to collapse
Did you update to the latest version? If your on an old version and attempt to flash a 4.4 rom you will get a status 7 error everytime
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
ShapesBlue said:
Did you update to the latest version? If your on an old version and attempt to flash a 4.4 rom you will get a status 7 error everytime
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
I thought I updated to the latest Phliz and I do believe that's the error I was getting when I tried to load the ROM.
I'll check again Monday.
I appreciate the info.
The issue was with Philz.
I upgraded to the latest TWRP and loaded the new ROM fine.
I've been using Temasek's UNOFFICIAL Build, for his last 3 build updates with TYR kernel. I decided I wanted to try out AK, or Render Kernel with Tamasek. Flashed new UKM update from AK, flashed new kernel. Restarted the phone and it constantly reboots on One+ logo. Never loads boot animation. Decided to fully wipe the phone, including system and reflash Tamesek. Then tried flashing AK. Same problem. Tried full wiping again and flashing a different rom and AK kernel or Render kernel and same issue. Reflashed TYR kernel and it works perfectly fine.
I have no idea what's going on. But, I don't want to be stuck using only 1 kernel. Any ideas?
garz said:
I've been using Temasek's UNOFFICIAL Build, for his last 3 build updates with TYR kernel. I decided I wanted to try out AK, or Render Kernel with Tamasek. Flashed new UKM update from AK, flashed new kernel. Restarted the phone and it constantly reboots on One+ logo. Never loads boot animation. Decided to fully wipe the phone, including system and reflash Tamesek. Then tried flashing AK. Same problem. Tried full wiping again and flashing a different rom and AK kernel or Render kernel and same issue. Reflashed TYR kernel and it works perfectly fine.
I have no idea what's going on. But, I don't want to be stuck using only 1 kernel. Any ideas?
Click to expand...
Click to collapse
Better ask your question in AK or Temasek thread
A friend of mine is having touch issues with his opo! It's unresponsive sometimes! He is on stock unrooted 05q. Will flashing a custom kernel help?
If yes please suggest a good one
garz said:
I've been using Temasek's UNOFFICIAL Build, for his last 3 build updates with TYR kernel. I decided I wanted to try out AK, or Render Kernel with Tamasek. Flashed new UKM update from AK, flashed new kernel. Restarted the phone and it constantly reboots on One+ logo. Never loads boot animation. Decided to fully wipe the phone, including system and reflash Tamesek. Then tried flashing AK. Same problem. Tried full wiping again and flashing a different rom and AK kernel or Render kernel and same issue. Reflashed TYR kernel and it works perfectly fine.
I have no idea what's going on. But, I don't want to be stuck using only 1 kernel. Any ideas?
Click to expand...
Click to collapse
Dirty flash the ROM first to get the stock kernel back, then try flashing another kernel.
Flash latest twrp.
Sent from my bacon!!!!!
Use twrp recovery
loridoo said:
Use twrp recovery
Click to expand...
Click to collapse
What a useful answer.
Sent from my bacon!!!!!
timmaaa said:
Dirty flash the ROM first to get the stock kernel back, then try flashing another kernel.
Click to expand...
Click to collapse
I tried this, I now tried 3 different roms. SlimSaber unnofficial, Robbie's CM12, and Euphoria and all of them do now allow me to flash AK kernel or any other kernel. I think something borked on one of TYR's kernel flashes. May I should reset the phone completely. Is there an option to do this with ODIN that someone can point me into?
NickosD said:
Flash latest twrp.
Sent from my bacon!!!!!
Click to expand...
Click to collapse
Duh...
garz said:
Is there an option to do this with ODIN that someone can point me into?
Duh...
Click to expand...
Click to collapse
Odin is just for Samsung phone
We use fastboot instead
waterdaan said:
Odin is just for Samsung phone
We use fastboot instead
Click to expand...
Click to collapse
Right, just wiped/restored my phone to stock/factory all the way back to CM11S30R. Unlocked bootloader, rerooted, upgraded firmware and reflashed Euphoria and still can't flash AK without bootloopingon the ONE+ logo. I then clean wiped, and flashed Euphoria and same issue. I am at a loss, I have no idea what else to do.
garz said:
Right, just wiped/restored my phone to stock/factory all the way back to CM11S30R. Unlocked bootloader, rerooted, upgraded firmware and reflashed Euphoria and still can't flash AK without bootloopingon the ONE+ logo. I then clean wiped, and flashed Euphoria and same issue. I am at a loss, I have no idea what else to do.
Click to expand...
Click to collapse
No need to flash back to 30R
I'd flash the 05Q stock using fastboot
That comes with latest modem etc
Then if you'd like flash custom rom in recovery
Unlock bootloader?? Did you lock it after unlocking it?
What version of recovery are you using?
waterdaan said:
No need to flash back to 30R
I'd flash the 05Q stock using fastboot
That comes with latest modem etc
Then if you'd like flash custom rom in recovery
Unlock bootloader?? Did you lock it after unlocking it?
What version of recovery are you using?
Click to expand...
Click to collapse
I am using TWRP 2.8.5.1.. I just figured I'd redo everything from scratch. Nothing is working. I can only flash TYR with all the roms I've tried, where it successfully boots. I'm also flashing UKM 3.8.1.
garz said:
I am using TWRP 2.8.5.1.. I just figured I'd redo everything from scratch. Nothing is working. I can only flash TYR with all the roms I've tried, where it successfully boots. I'm also flashing UKM 3.8.1.
Click to expand...
Click to collapse
try to redownload AK kernel, Maybe a bad download
Anyway good luck
waterdaan said:
try to redownload AK kernel, Maybe a bad download
Anyway good luck
Click to expand...
Click to collapse
Did that twice. Installs perfectly every time.