Related
[Q] I'mgetting "Error in /tmp/sideload/package.zip" when I try to update my Nexus S
I've searched countless times on how to fix this, yet every time I find a thread containing someone asking about this they never answer it or they're dealing with a rooted device.
My device is not, and has never been, rooted. Never manually updated anything on the phone before trying now.
I tried to manually update to 2.3.3 after never receiving the OTA. Then I tried the 2.3.4 update and I keep getting the "Error in /tmp/sideload/package.zip" message.
Can someone explain, or point me in the direction, of a non-rooted answer. Why am I getting this message to begin with?
Do you own the European version? The SLCD 19023 one?
No, it's the American version.
It's weird because I received the 2.3.2 update. But aftr that...I never got the 2.3.3 pushed to me. And now when I try to manually update to the .3 or .4 update...I keep getting that message.
Vandam500 said:
Do you own the European version? The SLCD 19023 one?
Click to expand...
Click to collapse
No, it's the American version.
It's weird because I received the 2.3.2 update. But aftr that...I never got the 2.3.3 pushed to me. And now when I try to manually update to the .3 or .4 update...I keep getting that message.
me too. the same problem with my Nexus S
And me too, Davey. Same problem. Bought the Nexus S in New York on late December and I live in Spain. My phone is unrooted.
Haven't received the OTA for 2.3.3 yet and tried both manually updates for 2.3.3 and 2.3.4, but getting the same message as you.
It's frustrating!
Same problem here with a UK-bought Nexus S. I have tried with the bootloader Locked and Unlocked. Although bought in UK there is no guarantee that it is not an American import. It was bought from Carphone Warehouse who seem to source their kit from any where they can get it.
So as other people are successfully installing it has to be something specific to this physical handset.
Hands0n said:
Same problem here with a UK-bought Nexus S. I have tried with the bootloader Locked and Unlocked. Although bought in UK there is no guarantee that it is not an American import. It was bought from Carphone Warehouse who seem to source their kit from any where they can get it.
So as other people are successfully installing it has to be something specific to this physical handset.
Click to expand...
Click to collapse
So from the few posts here it's seeming like an international device issue...but yet I'm in the States. So I don't get it.
It's just frustrating that I can't get an answer about it. Many a people are speaking on it, but nobody can explain or solve it. Sigh.
Same issue as you - error in /tmp/sideload
I have Nexus S 2.3.3 (manually updated) from US. I am trying to manually bump it to 2.3.4 -- same issue. I have rooted & unlocked the device. No Mods here.
Same error.
Baseband is I9020XXKB1
Kernerl - 2.6.35.7-g1d030a7 [email protected] #1
Build GRI40
Updated!!!
OK guys -- Finally figured out the problem for /tmp/sideload/package.zip.
If there is any change to the bootloader by any app (RomManager or has ClockWorkMod), then you won't be manually be able to upgrade to 2.3.4
Solution for those on GRI40 2.3.3
1. Flash stock 2.3.3 gingerbread again in recovery more. Do a quick search on XDA and grab it. Almost 90 MB file.
2. Once flashed - Boot it, sign in with google account and under setting, privacy - do a factory data reset. Start it clean. I DID NOT checked the SD card data.
3. Flashed 2.3.3 in recovery again.
4. Reboot it. Did not signed in once booted. Turn USB ON. Put the 2.3.4 file (around 12 MB).
5. Flash it again in recovery mode.
6. I signed in to Google account without restoring my backup.
That's it. On 2.3.4 - Unlocked state remains!
Hi there!
Finally managed to install the 2.3.4 version on my Nexus S and works perfect! Already tried the Google Talk video chat and it's fantastic.
You can find all the instructions and the update files in the following link (thanks to the impaler for that):
http://forum.xda-developers.com/showthread.php?t=1055950
i dont have the OTA on the TB i just got today, when i go to Updates it says looking, then it does nothing. i have only tried it on 3g, do i have ot check it under WIFI instead?
thanks
dvigue said:
i dont have the OTA on the TB i just got today, when i go to Updates it says looking, then it does nothing. i have only tried it on 3g, do i have ot check it under WIFI instead?
thanks
Click to expand...
Click to collapse
If you plan on rooting, then don't bother with the OTA. You'll have to wipe the phone while rooting, then update to the latest. If you don't plan on rooting, then the OTA should show up when tell it to check. What version does it currently say you are running?
Even if you don't plan on rooting, I still wouldn't update. Otherwise you may end up frustrated with reboots.
I got my TB back in May. Didn't have one issue until I did the update. Since I only had the phone for 11 days VZW told me to walk into a store and exchange for a new one. I have had no issues with the new phone and will stay clear of that update. Wait until GB comes out and hopefully that will fix what ever is wrong.
The OTA update showed up this morning. I chose to delay it because I was going to need my phone. Went to update it later and it just would not download. Did a factory reset and now when I go to system updates it says "checking for available update." for about a minute then says "check for update is not available at this time. Try again later." What am I missing here?
dwcosby said:
The OTA update showed up this morning. I chose to delay it because I was going to need my phone. Went to update it later and it just would not download. Did a factory reset and now when I go to system updates it says "checking for available update." for about a minute then says "check for update is not available at this time. Try again later." What am I missing here?
Click to expand...
Click to collapse
there have been quite a few people with this same issue. i havent seen any direct fix.
if you are locked, i would suggest you wait it out, or wait for the sbf file to get leaked. there is a way to sideload it, but its risky being locked and no sbf to save you if a problem comes up.
if you are unlocked, there are directions in the General forum to sideload the ota. there is no risk if you are unlocked.
if you are locked, the only thing i would suggest to try is re-flashing the stock 9.30.1 with rsd and see if it will pull the update afterwards. there is no guarantee this will work, but your phone will be 100% clean stock after the flash and give you the best chance to grab the ota if available.
dwcosby said:
The OTA update showed up this morning. I chose to delay it because I was going to need my phone. Went to update it later and it just would not download. Did a factory reset and now when I go to system updates it says "checking for available update." for about a minute then says "check for update is not available at this time. Try again later." What am I missing here?
Click to expand...
Click to collapse
Did you download it and then said to apply it later? If so, are you rooted? If so, hook up your phone to your PC and adb shell into it. Type "su" and hit enter to go into superuser mode.
Navigate to the /cache directory and you should see the OTA .zip file sitting in there. Copy it to your external SD card and then you can load it manually via the recovery.
If you're not rooted, then you won't be able to navigate into the /cache directory. Or, if you didn't have it download when you got the notice (or couldn't download it), then it won't be there.
More update issues
My wife & son both have the HD. My wife checked for the update this morning, said it was ready and proceeded to download. Update did as it was supposed to and when it was done, she had KitKat and that's when things went a bit wonky.
If she has Bluetooth turned on, WiFi connection drops after a few minutes. She googled possible workarounds and none really worked. As long as she is not using BT, WiFi stays up
Has anyone else seen this behavior? She refuses to let me root it and install a custom ROM as I have done on my Samsung GS4 from VZW.
In the mean time, we've told our son not to take the update until
we know more about a possible fix.
zeb carter said:
My wife & son both have the HD. My wife checked for the update this morning, said it was ready and proceeded to download. Update did as it was supposed to and when it was done, she had KitKat and that's when things went a bit wonky.
If she has Bluetooth turned on, WiFi connection drops after a few minutes. She googled possible workarounds and none really worked. As long as she is not using BT, WiFi stays up
Has anyone else seen this behavior? She refuses to let me root it and install a custom ROM as I have done on my Samsung GS4 from VZW.
In the mean time, we've told our son not to take the update until
we know more about a possible fix.
Click to expand...
Click to collapse
Fix was just posted recently. do a factory reset. It sucks, but its the only option.
Factory REst doesn't solve 4.4.2 WIFI issue on Razor MAxx HD
TXKSSnapper said:
Fix was just posted recently. do a factory reset. It sucks, but its the only option.
Click to expand...
Click to collapse
Android V 4.1.2 worked flawlessly since Nov 1023 upgrade. Decided to upgrade to KitKat via OTH. Had WIFI connection issues right away ( inability to obtain IP or lost connection, etc.) This happened with Bluetooth ON or OFF, no difference. The Signal strength was much lower than when on the previous android version and subsequent indicated connection speed was at least 1/2 of what I was getting previously.
Worked with Verizon and Motorola tech support personnel and did multiple factory resets with no improvement.
Since I wanted a factory solution and had insurance on the phone, I ordered a replacement phone. Thankfully, the new phone had 4.1.2 and worked perfectly. WIFI issues are gone.
Conclusion, KitKat is not ready for prime time yet. WIFI bug needs to be worked out before I will upgrade again.
egutwillig said:
Android V 4.1.2 worked flawlessly since Nov 1023 upgrade. Decided to upgrade to KitKat via OTH. Had WIFI connection issues right away ( inability to obtain IP or lost connection, etc.) This happened with Bluetooth ON or OFF, no difference. The Signal strength was much lower than when on the previous android version and subsequent indicated connection speed was at least 1/2 of what I was getting previously.
Worked with Verizon and Motorola tech support personnel and did multiple factory resets with no improvement.
Since I wanted a factory solution and had insurance on the phone, I ordered a replacement phone. Thankfully, the new phone had 4.1.2 and worked perfectly. WIFI issues are gone.
Conclusion, KitKat is not ready for prime time yet. WIFI bug needs to be worked out before I will upgrade again.
Click to expand...
Click to collapse
That's a shame because for me, the FDR fixed the Wifi/Blue-tooth issue as it did for many others. Might have been a hardware issue (faulty radio, etc).
Hi xdadevelopers,
I ordered a Motorola Photon Q 4G LTE (xt897c) phone from FreedomPop for $25 and 28 days later it has arrived. My experience with FreedomPop has been decidedly mixed. Lots of hassle from customer service combined with a product that is sometimes very useful and always cheap. (Unless you use over 2GB of data per month) The phone itself seems very adequate for an excellent price. I would like your assistance in putting Cyanogenmod or another appropriate ROM on it.
Here's where I am,
The phone appears to have been rooted out of the box according to "Root Checker Basic" from Google Play
I installed "Superuser" from Google Play and that seems to work correctly
Busybox seems to be present already according to "Online Nandroid" from Google Play
I have created a TWRP Backup using Online Nandroid without modifying the recovery
The phone currently has Android 4.1.2
Where I want to be
I want to install a custom recovery, preferably one I can make backups from
I want to update to a more recent version of Android such as the stable one found here DUCK RULES cyanogenmod bot org /?device=xt897c or another version where everything just works
Notes. I have ADB and Fastboot installed from "Android Studio". I have an appropriate USB cable. I do not have a microsdhc card right now. It appears "Sandisk 64GB Extreme Micro SD (SDXC) Card + Adapter 60MB/s Class 10 U3 UHS-1" at DUCK RULES amazon bot com /gp/product/B00N98QLRQ is a good choice for a good price. I have this on order and should have it within the week.
I understand this phone has a locked bootloader. The "Messaging" app from FreedomPop available in Google Play seems to control messaging and the phone dialer. I went to the official Motorola Bootloader unlock page DUCK RULES motorola-global-portal bot custhelp bot com /cc/cas/sso/redirect/standalone%2Fbootloader%2Funlock-your-device-b I booted into recover with Power and volume up and volume down held, selected fastboot, connected to the computer , ran fastboot, as described, got the code, put the code in the webpage as described, and got a blank page. This happened 2x, with no emails form Motorola. I tried a third time 6 hours later, and it loaded a page with more instructions and I had the bootloader unlock code in my email instantly (There were no preceding messages, they didn't go to spam or somewhere else). I have installed TWRP Manager by Jmz software from Google Play. The standard reboot method doesn't work I changed the settings to "Reboot using an alternate method". I attempted to the TWRP recovery with the "Install TWRP". One must select their device and the closest thing to mine was "Motorola Photon 4G" codename "sunfire". This didn't appear to be it exactly but there wasn't a better choice. The next line down says "custom recovery not installed or detected". Then I selected the recovery version to install "2.6.3.0" "openrecovery-twrp-2.6.3.0-sunfire.img appeared the most recent, then I attempted to "Install Recovery" The phone downloaded the image, and said "Ensure the partition listed below is the correct one for your device..." "/dev/block/mmcblk0p10" how do I know if that's correct or not? I said yes to the question and went ahead, the phone rebooted to an Android on it's side with a yellow triangular sign with an exclamation point above it. Thirty seconds later the phone rebooted normally and everything worked no custom recovery was flashed.
Also thanks to the xdadevelopers community for your past and future efforts. I threw in my lot with Android when the neXus One launched after watching the keynote, buying it full price and paying extra for next day air shipping. I stayed stock despite the cool stuff being done by the development community until Google fell behind in updates. Then I started with CM6 and later went to CM7. That was wonderful software, thanks everyone who was involved in that. Unfortunately way late in the life of my phone I was homeless and got robbed for it. I got a used HTC HD7 Windows Phone for free from a friend. It was great for movies and music with a great screen and touch sensor but it was very early in the life of the new Windows Phone and there wasn't a lot of quality software being developed. That, and it just wasn't Android, and I longed for freedom. The integrated Web browser IE 9 variant sucked, and T-mobile denied me the final Windows Phone 7 update. The phone has gotten less and less useful as time went by though it always sucked for web browsing. This fall I got a One Plus One, it made a wonderful Wifi phablet, but when I tried to use it as a phone I found the radio was severely deficient in range, possibly due to defective manufacture as it got better range in colder weather. I had to initiate a chargeback with my credit card company to get support to talk to me and then ultimately get a refund. That's how I got where I am now and this is the first time I've needed to register for an account here. Thanks again xdadevelopers.
What is the best way to proceed? Semi detailed logical instructions please, as while I am intelligent and not a noob, I have been out of the game since CM7
Code:
.. ("`-''-/").___..--''"`-._
.. `6_ 6 ) `-. ( ).`-.__.`)
.. (_Y_.)' ._ ) `._ `. ``-..-'
.. _..`--'_..-_/ /--'_.' ,'
.. (il),-'' (li),' ((!.-'
Holy wall of text. This seems to be the crux:
Aslan_ said:
I have installed TWRP Manager by Jmz software from Google Play. The standard reboot method doesn't work I changed the settings to "Reboot using an alternate method". I attempted to the TWRP recovery with the "Install TWRP". One must select their device and the closest thing to mine was "Motorola Photon 4G" codename "sunfire". This didn't appear to be it exactly but there wasn't a better choice. The next line down says "custom recovery not installed or detected". Then I selected the recovery version to install "2.6.3.0" "openrecovery-twrp-2.6.3.0-sunfire.img appeared the most recent, then I attempted to "Install Recovery" The phone downloaded the image, and said "Ensure the partition listed below is the correct one for your device..." "/dev/block/mmcblk0p10" how do I know if that's correct or not? I said yes to the question and went ahead, the phone rebooted to an Android on it's side with a yellow triangular sign with an exclamation point above it. Thirty seconds later the phone rebooted normally and everything worked no custom recovery was flashed.
Click to expand...
Click to collapse
Why would you flash something that is OBVIOUSLY not for your device!? I sincerely hope it did nothing because you could do some permanent damage to your device by flashing stuff that's not made for it.
Did you bother looking for any recovery threads? Say my TWRP thread?
I recommend 2.7.1.2 in that thread, which is fine for CM11. If you want CM12, grab 2.8.5.0 in that thread.
Flash it per my directions using fastboot in my TWRP thread.
Got it thanks, now which rom?
Thank you very much arrrghhh. First off I sucessfully flashed TWRP 2.7.1.2. I did see the "[recovery] TWRP 2.7.1.2" thread, but it was from 2012 and it's 2015 now, plus it was 25 pages. Now I do see that the initial post was last edited 23rd July 2014, so that's better, but that's still over six months ago, so I'd have asked the question anyway having seen that. Several things to note, GooManager has been retired since the new cdn for goo.im was implemented, so that should be removed from the post. I like apps, they make me feel like there's less risk in my actions, though after some poking around I see it's probably the opposite. People are doing so much more low level stuff in apps compared to CM7 it's amazing.
arrrghhh said:
I recommend 2.7.1.2 in that thread, which is fine for CM11. If you want CM12, grab 2.8.5.0 in that thread.
Click to expand...
Click to collapse
It would be nice to see that info in the 2.7.1.2 thread. that the newer version is recommended for CM12 and where to get it, that would show you're on top of the latest changes not to mention make the thread even more useful. Perhaps include the reason for stopping at 2.7.1.2, the SELinux split. Seeing a new version that works always makes me want to get the newer version, but in this case there's a good reason not too.
I'm always hated vague it's broken posts that don't adequately describe the problem, the hardware used and the environment, so I head in the opposite direction with mine.
Next question is which rom should I choose? I want something stable and secure with everything or just about everything working. I like Cyanogen Mod, but I'm open to other things. As new as I can get, but stable. I thought I needed something from download bod cyanogenmod bot org /?device=xt897c , but now looking around it looks like I might be able to use other sources like download bot cyanogenmod bot org /?device=xt897 I'm not sure though. Again I have the Motorola Photon Q 4G LTE which is CDMA, from FreedomPop running on the Sprint Network.
Code:
.. ("`-''-/").___..--''"`-._
.. `6_ 6 ) `-. ( ).`-.__.`)
.. (_Y_.)' ._ ) `._ `. ``-..-'
.. _..`--'_..-_/ /--'_.' ,'
.. (il),-'' (li),' ((!.-'
Aslan_ said:
Thank you very much arrrghhh. First off I sucessfully flashed TWRP 2.7.1.2. I did see the "[recovery] TWRP 2.7.1.2" thread, but it was from 2012 and it's 2015 now, plus it was 25 pages. Now I do see that the initial post was last edited 23rd July 2014, so that's better, but that's still over six months ago, so I'd have asked the question anyway having seen that. Several things to note, GooManager has been retired since the new cdn for goo.im was implemented, so that should be removed from the post.
Click to expand...
Click to collapse
I no longer use this as my primary device, so my threads are basically stagnant. fastboot always works, where apps come and go... I'll try to find some time to adjust the post.
Aslan_ said:
It would be nice to see that info in the 2.7.1.2 thread. that the newer version is recommended for CM12 and where to get it, that would show you're on top of the latest changes not to mention make the thread even more useful. Perhaps include the reason for stopping at 2.7.1.2, the SELinux split. Seeing a new version that works always makes me want to get the newer version, but in this case there's a good reason not too.
Click to expand...
Click to collapse
Reason for stopping at 2.7.1.2 was they implemented MTP in 2.8.x, and I could never get it working right for both Win & Lin. I spose my bar was too high and I should've just released it, but I hate releasing half working stuff. It was a new feature that didn't work right.
Again, this is no longer my primary device so I'm not working on it very much at all. I have to pry the thing from my roommate's hands to even play with it, I haven't flashed CM12 yet (because it's no longer my device really).
I'd like to update the official TWRP, but in the meantime the CM maintainer has taken care of updating it so F2FS can be utilized.
Aslan_ said:
Next question is which rom should I choose? I want something stable and secure with everything or just about everything working. I like Cyanogen Mod, but I'm open to other things. As new as I can get, but stable. I thought I needed something from download bod cyanogenmod bot org /?device=xt897c , but now looking around it looks like I might be able to use other sources like download bot cyanogenmod bot org /?device=xt897 I'm not sure though. Again I have the Motorola Photon Q 4G LTE which is CDMA, from FreedomPop running on the Sprint Network.
Click to expand...
Click to collapse
Well obviously some of that does go down to choice - if you want CM, it is a little confusing. The device started out in CM10 as its own device, xt897 for GSM xt897c for CDMA. Then in CM11 they merged the devices into moto_msm8960. Of course they had to split again when the new bootloaders were released for the other moto_msm8960's (Razr HD, Atrix HD, etc) and moto_msm8960_jbbl was kind of a stopgap device at the end of CM11. Again, reading is your friend here although I realize all of that history is hard to glean. At least read the OP of the CM thread:
kabaldan said:
Please note:
In CM12, the Motorola 2012 msm8960 device line has been de-unified again, so moto_msm8960/moto_msm8960_jbbl builds are dead from now on.
Please check the xt897 device link for new Photon Q builds.
Click to expand...
Click to collapse
Good luck. The device is now semi-unified (GSM & CDMA), as xt897.
Aslan_ said:
[*]I have created a TWRP Backup using Online Nandroid without modifying the recovery
Click to expand...
Click to collapse
Would you mind terribly to share this? My device shipped with a Sprint branded ROM and I'd like a proper backup.
I flashed CM 12.1 and lost data (3g/LTE) connection
I tried to flash FreedomPOP APN fix but it did not help
Anyone knows how to fix this?
How do I update PRL/Profile on CM 12.1?
turbozapekanka said:
I flashed CM 12.1 and lost data (3g/LTE) connection
I tried to flash FreedomPOP APN fix but it did not help
Anyone knows how to fix this?
How do I update PRL/Profile on CM 12.1?
Click to expand...
Click to collapse
You don't update PRL/Profile in CM, you do that on the stock ROM. Make sure EVERYTHING works on stock before flashing CM.
I found another APN fix and it worked.
So the result of the update PRL/Profile is stored somewhere in the phone and does not get lost when I flash a new ROM, is that correct?
The only way to update PRL/Profile is to flash back to stock, do update, reflash back to custom, right?
turbozapekanka said:
I found another APN fix and it worked.
So the result of the update PRL/Profile is stored somewhere in the phone and does not get lost when I flash a new ROM, is that correct?
The only way to update PRL/Profile is to flash back to stock, do update, reflash back to custom, right?
Click to expand...
Click to collapse
Correct.
turbozapekanka said:
I found another APN fix and it worked.
So the result of the update PRL/Profile is stored somewhere in the phone and does not get lost when I flash a new ROM, is that correct?
The only way to update PRL/Profile is to flash back to stock, do update, reflash back to custom, right?
Click to expand...
Click to collapse
Can you share this "another APN fix"?
already shared here http://forum.xda-developers.com/showpost.php?p=60153295&postcount=18
Anyone still have issues? I was running a June Nightly and it was working somewhat. It would randomly lose connection and I would have to flash the APN.zip. It happened again a few days ago and I decided to go up to 722 Nightly and now I haven't been able to connect. When I go to APNs the list is empty and even if I manually add one it does not seem to stick. The APN zip doesn't help either. The phone is connected but shows an exclamation mark next to the signal and I have no data.
Sort of solved my own problem
Flashed back to stock Spring using RSD lite and a modified XML that didn't flash the system.img since it kept giving me errors. Found a stock TWRP dump on the forums and flashed that. Updated PRL and Profile, reflahsed back to CM11 Snapshot and flashed the 2015 FreedomPOP APN fix. Working for 1 day now.
S8+ /S8 Global Unlocked Variants, (ie: G955FD, etc) Desperately need help w/issue After 8.0 Update...
Hi, I have a G955FD & have family members with this same model, as well as the Global unlocked regular S8-dual sim. We all have the same issue after the Samsung 8.0.0 update. The phone is no longer reliable. Randomly, these devices will not have any ring on incoming calls. If they don't leave a VM, then you have no indication of a missed phone call. In addition, random periods where text messages will also just not come thru. Difference on the texts is, when you reboot, they all populate in the message app and notifications. But the incoming calls are not known and lost forever w/o a VM left for you by caller.
I have been in contact with Samsung, although they indicate right off that I have no warranty because I didn't buy a carrier device from an authorized vendor for my local use, they were open & helpful to reveal that they are aware of '8.0 ringer issues' on the unlocked global devices. BTW, this must be a huge number of people across the world with this problem, but like my friends/family, originally think they have signal/carrier issues etc. Samsung says that it should be addressed in a patch or update..... but, WHEN? I have had a messed up phone for over 3months and counting.
The only thing that can be done to attempt having the phone work 'more often' is to do a restart every hour all day long and hope that your phone will ring when someone is calling.
I, personally, being the family tech guy, am the one working on the issue so I'm here to ask for help/input.
Been dealing with this issue for over 3 months now, here's some of what I have done and what I'd like help with please...
I have attempted 5x to install a custom ROM from XDA to alleviate this issue completely, but as of now, still unsuccessful. I've been rooting/hacking my android devices since my 1st but somehow can't get the process to work thru. At this point, using Odin, I have no issue to get my phone running TWRP and rooted. Somehow, after that point something isn't going right and my phone has to be re-odin flashed with OEM ROM and then wait 1 week for OEM unlock to re-appear to try again. So, If I could complete this process next time the OEM-unlock is back up, my problem would be over.
Now, since I am having issue with completing a custom ROM install... I thought, why not flash a previous OEM ROM (7.0 NOUGAT) and again, my problem should be over and I could wait until a 9.0 update to see how that goes. So far, any 7.0 stock ROMS I have been able to find/download, have 'failed' install in Odin. (I have standard Odin, patched and Prince Comsey) so I always try them all before I say it's a true fail.
Can anyone help me to understand why, with all the root/roms Ive done, cannot get custom ROM to complete install. I was trying for the CarHD or Batman. after rom flash, something goes wrong and the phone either goes bootloop or failed verify. (BTW, couple X I did flash the no-verify to alleviate that issue but still get bootloop or no new rom boot up)
The other thing I'd love to be able to do right now that 'should' be a piece of cake, (but hasn't been) until I figure out the custom rom install issue, is to ask for anyone that can post a link to a valid ODIN-flashable Stock 7.0 NOUGAT ROM for my S8+ G955F/FD. That would solve everything for now and I'd just disable updates for the interim. As previously mentioned, the couple I have found would only FAIL on Odin flash attempts. Seeing that this is a global, unlocked device, is it possible to flash a stock rom or flash a diff CSC that can get me North America Tmobile setup (my USA provider) I noticed that the global phone has no options to disable LTE or turn wifi calling on/off etc.
I apologize if I have jumped around in my post, not provided enough details or not written very eloquently, but I am happy to provide any other needed info to move forward if any of you have ideas here. I'm just at the end of my rope with this right now.
Any help, input here is much appreciated! TIA! mark~
Trying to be helpful here.
For some folks flashing with Odin the first run through errors/fails. That issue was a PITA. I found a post somewhere which said when you hook up the phone to flash with Odin, the first attempt will fail, but to leave the phone connected, go back into download mode, and flash again. Do not unplug the phone when you do this.
For some reason there's a kink in Odin with some folks.
That info, wish I could recall who by - they deserve the recognition, anyway it solved all my Odin errors.
JeffDC said:
Trying to be helpful here.
For some folks flashing with Odin the first run through errors/fails. That issue was a PITA. I found a post somewhere which said when you hook up the phone to flash with Odin, the first attempt will fail, but to leave the phone connected, go back into download mode, and flash again. Do not unplug the phone when you do this.
For some reason there's a kink in Odin with some folks.
That info, wish I could recall who by - they deserve the recognition, anyway it solved all my Odin errors.
Click to expand...
Click to collapse
hey jeff, thanks for checking in when the OEM unlock button returns again tomorrow, I'll keep this in mind on my next attempt. i did encounter that fail several times with some OEM firmware flashes (trying to go back to 7.0) and this should resolve that problem. overall though, my real issue seems to be when attempting a root/custom rom instead of a stock replacement... and 'after' i get TWRP completed. I'm doing something wrong with a button hold sequence or something else. maybe need flash 'do not verify' right off too. I'm gonna go extra slow/careful following each step from a great, detailed post for TWRP/ROOT/ROM procedure that i found here over weekend written by 'jesec' what i hate the most is, i only have 1 shot doing this with the oem unlock button, if messed up, have to re-flash a stock rom and wait another 7 days to try this all again.
i still cannot believe its been about 13wks and samsung says they are aware, yet still has not patched this problem. i love my samsungs but im so fed up, i almost ordered a oneplus 6 this weekend just because of this random no ring issue.
thanks much!