Related
I can't post in the VEGAn-TAB GingerEdition STABLE RC1 thread, so I have to post here, sorry.
I am trying to install VEGAn on my new G Tablet, and I keep getting into endless cycles.
First I rooted, then loaded CWM fine. Cleared data, cache, and dalvic. When I installed the ROM, it would hang on the Viewsonic boot screen. Tried several times, even tried fixing permissions, nothing.
So now I have tried the nvflash full restore, which made me lose CWM. Now I am not able to install CWM (.8) it just gives a loading bar and then reboots. Then when I use push power+volume up and release, which should boot into CWM, it just does the same thing (tries to install update.zip) then reboots.
I also can't boot into APX mode: when I hold down Power+Volume up, the screen is supposed to go black, but it never does. Just tries to load an 'update.zip' file that isn't there, and then reboots. This means that I can't use the nvflash method to install CWM.
Here is the current info from my about tablet:
Model UPC300-2.2
Tap UI version: 1.1-3389
Kernel version: 2.6.32.9.00000.10.8.2-dirty
Build Number FRF91
Any help would be extremely and much appreciated. Thanks!!
G
To go into APX mode, you have to hold Power plus Volume down. Get NVFlash, restore to stock rom, and then install CWM again and the flash your Rom. And don't forget to partition with NVFlash.
http://forum.xda-developers.com/showthread.php?t=861950
EDIT: I had the same issue. Installed CWM, then flashed CM7 and I wanted to change roms but I couldn't until I set up NVFlash and restored to stock and flashed VEGAn-TAB.
fp99 said:
To go into APX mode, you have to hold Power plus Volume down. Get NVFlash, restore to stock rom, and then install CWM again and the flash your Rom. And don't forget to partition with NVFlash.
http://forum.xda-developers.com/showthread.php?t=861950
EDIT: I had the same issue. Installed CWM, then flashed CM7 and I wanted to change roms but I couldn't until I set up NVFlash and restored to stock and flashed VEGAn-TAB.
Click to expand...
Click to collapse
Thanks! If I follow the steps here for nvflash http://forum.xda-developers.com/showthread.php?t=861950, won't that automatically repartition, or do I need to do something else beyond that?
generosity21 said:
Thanks! If I follow the steps here for nvflash http://forum.xda-developers.com/showthread.php?t=861950, won't that automatically repartition, or do I need to do something else beyond that?
Click to expand...
Click to collapse
You actually have to do that in CWM. Under the advance option -> partition SD card.
Check out step 7. http://forum.xda-developers.com/showthread.php?t=865245
EDIT: This will erase everything on the tablet. Rom files and all. After the partition. Mount the USB and copy the rom file onto the tablet via the usb cable.
Thanks for the help, one last question.
I applied the fix to Market, but now I'm not sure if it needed it, and I am not able to download any apps from the market. I can browse fine, just not download. Did applying the fix mess things up, and is there an easy way to fix? I tried rebooting, but maybe fix permissions is necessary?
Thanks
g
generosity21 said:
I can browse fine, just not download. Did applying the fix mess things up
Click to expand...
Click to collapse
No, you didn't mess things up. Do the fix again: delete the cache for the Market app, delete the data for the Google services app, reboot, and you should be able to download. Worked for me.
By reboot, I mean powering completely off, then manually turning it back on.
Working great now! I think it may have been the Wifi network I was using. I have read several posts where switching to a different wifi fixed the download issue.
Thanks for the help
-BoneZ- said:
No, you didn't mess things up. Do the fix again: delete the cache for the Market app, delete the data for the Google services app, reboot, and you should be able to download. Worked for me.
By reboot, I mean powering completely off, then manually turning it back on.
Click to expand...
Click to collapse
You guys hit it out the park with this rom. I have a question what browser is this? Also I like to save articles as I cruise the web and the stock browser let me create custom folders. What would be a good way to do it with this rom and browser?
Running 2.3.4 version 4.5.91 ATT/US SBF I believe, stock kernel, unlocked bootloader, rooted, and have Tenfar's CWM recovery.
I accidentally accepted the download for update to v4.5.141 (after hitting "Later" 1000 times), but had wifi turned off at the time and the download never started... now I can't turn back on wifi because the download will automatically start (triangle! with "Enable Wi-Fi to start download update" in notifications), and I don't want to brick the device if it runs and I can't cancel the install.
What can I do to cancel the OTA download and/or install and avoid bricking the device?
Any help is appreciated.
Hmm. I know it's possible to "freeze" the update notification (that is, either use the pro version of titanium backup, or put .bak after the appropriate system app). A few other threads have detailed how to do this.
You just accidentally downloaded it, right? It shouldn't install automatically; it would pop up another "install" vs. "later" prompt once the download finishes. I know there's another post around here (stickied?) that details how to back up your OTA update. You could probably use that thread to find your downloaded file & delete it.
Alternately, since you're unlocked you could always install another rom and skip the OTA process entirely. For example, Nottachtrix is based on the 4.5.141 build and comes with a stock Gingerbread theme if you want.
Thanks, I did see those threads you mentioned.
Before my mistake, I had already tried renaming /system/app/Upgrader.apk to .bak with root explorer, and rebooting to stop the download update popup... it didn't work, and kept prompting me, which I eventually accidentally accepted instead of hitting "Later".
I don't have the Pro version of TiBU Pro; I was thinking of upgrading it to freeze Upgrader when I was trying to stop the download update prompts, but as I mentioned I accepted the download before I could do that.
I was also considering flashing Nottachtrix since that seemed to be the only safe way I saw to update to 4.5.141 with the unlocked bootloader. can I safely flash that now, even though the update is pending?
I'll be honest and say I don't know with certainty. BUT -- I don't see why you couldn't download Nottachtrix on your computer, drop it onto your phone's SD card, and flash it from there (without ever turning your phone's wifi back on). Your phone is booted & not in the middle of an active install. It's just waiting to download a file which would requires your input to begin installing anyway.
If you're really concerned about it, you could do the Seriously Complete Wipe before flashing the new rom by using the following method (thanks CaelanT):
For the best results, when you want to flash a new ROM you should always perform a full wipe in fastboot per the following to make sure you will avoid any unforeseen complications:
reboot to recovery
wipe Dalvik
reboot to fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot (to recovery)
flash ROM
reboot
Click to expand...
Click to collapse
One more note: it looks like Tenfar's recovery is considered "old" round these parts, and most roms don't play well unless you flash them using romracer's CWM recovery. So that should probably be your first step. It's here.
thanks for the recommendations. I guess I will uninstall Tenfar's recovery, install romracer's recovery, do the Seriously Complete Wipe, and then flash Nottachrix. Let me know if any of that sounds wrong.
Will I lose my apps or my titanium backup of apps & system data by doing the Seriously Complete Wipe? If so what do I need to do to be able to restore my apps and system data after the wipe & flash?
Hey, no problem at all. (by the way, you don't need to uninstall your current recovery, just flash the new one per the instructions.)
Oh yeah, a second note: you'll need to rename two particular files before flashing the new recovery. From another stickied thread:
Anyone having issues not being able to boot into CWM recovery after flashing it (such as seeing android guy with exclamation mark):
Delete or rename /system/etc/install-recovery.sh AND /etc/install-recovery.sh I renamed mine to bkup.install-recovery.sh in case i ever wanted to use them again for some reason.
/etc/install-recovery.sh will automatically be placed in /system/etc if /system/etc/install-recovery.sh is not found on boot.
So, you must delete or rename both, THEN INSTALL CWM recovery.
rename the files using ROM Toolbox's root explorer as some file explorers will not give you the proper access levels to delete or rename the files correctly.c
Click to expand...
Click to collapse
Okay, on to apps & data. Yes, you're going to lose all your data in the wipes, but the backups you made will be intact. TiBu is fine for your apps; I use "MyBackup Root" (free on the market) for my contacts, SMS, MMS, etc. After flashing the new rom, you'll have the market pre-installed. Use it to re-download TiBu, restore your backed-up apps (NOT EVER system data. Just apps+their data.), then restore the rest from there.
I did everything, and it worked well. thanks for confirming it was safe and the extra tips!
I had already uninstalled Tenfar's recovery by the time I saw your response. I thought it may conflict, didn't know.
I didn't have to rename those 2 files to be able to boot into CWM recovery... the files weren't present before or after installing CWM recovery and it worked.
Thanks again for the tips on the seriously complete wipe and the MyBackup Root, they worked well.
Almost everything was restored after flashing the ROM except for a few minor settings. I somehow have a ton of contacts because I have all my Google contacts, my Blur contacts (a lot of dupes of Google ones), and a lot of extra old gmail e-mail contacts that I wish it didn't populate. Nothing to complain about because I would rather there be extra unnecessary contacts than missing ones.
The only issues I have is that the ROM shows the 3G img at all times... so I have to do some speed tests and troubleshooting to see if I am stuck in 3G or if it is just the known bug in the ROM where 3G is always displayed.
I have N_01.77.30P radio and I saw some people are running 36 or 37, and some people on AT&T installed an additional APN that improved performance.
If anyone has any input on the 3G, radio, or APN issues, please let me know.
atrix issues
Hello members,
i am new to android and learning to understand the jargon of experts here. Reason for joining xda is following:
I (from India) have a motorola atrix 4g that i purchased from a friend in US (it was on AT&T.)
1) when I start my phone -is says on top unlocked. Does it means it is unlocked / unrooted? and I cannot install the OTA updates from Motorola like ICS 4 coming in Q3?
2) I clicked on system update and downloaded the update over wifi. When it started the install it got failed with a triangle and ! mark. I had to remove the battery and start the phone after which it kept on rebooting . Saw in some forum that i had to do a factory reset and after doing that it worked but I lost everything. I had to reinstall all the apps. Is there a way to reinstall the latest OTA updates from Motorola with doing / playing much with ROM? if not then please let me know a simple and safe way.
3) After doing factory reset i accidentally clicked on system update and now the update is downloaded over wifi but i did not install by selecting "install later" . However the popup keeps coming up and i want to disable it. kindly advise how this notification can be stopped.
Thanks in advance
This will help anyone who keeps having flashing issues.
More detailed instructions in my GUIDE!
http://forum.xda-developers.com/showthread.php?t=2295557
THIS IS ONE QUICK/SIMPLE ERROR FREE ROM FLASHING PROCEDURE
This should eliminate a few posts saying, stuck in download mode, stuck at logo. just vibrates and them MANY other issues that somehow, everyone seems to find.
Here is my quick rom flashing process I use ALWAYS (yes always)
THINGS YOU NEED ON extSDCARD
1. Extra kernels (2 or 3 you know works for your device)
2. Optional: 2 recoveries that can be flashed (I use CWM & TWRP)
3. Optional: apps.zip (a zip created from Titantium BU, containing Root Explorer, TU Backup, Quickpic, ES File Explorer and Terminal Emulator)
Flashing the rom: TOUCHWIZ/AOSP ROMS
1. Backup current rom (to the extsdcard)
2. Complete wipe, (I do complete, some people do not) Complete = No Issues [FACTORY RESET + CLEAR CACHE + CLEAR DALVIK CACHE + CLEAR DATA]
3. Flash the rom
4. Flash the kernel (your device kernel) (I know some roms have their own kernel) this is where your problems start.
AGAIN: FLASH YOUR KERNEL, you KNOW it works. 1 more time FLASH YOUR KERNEL. (you can experiment with other kernels after you boot)
AOSP ROMS - require you to flash gapps before you boot. [This is not required for TouchWiz roms]
5. Boot the rom.
FINISHED!!!! SUCCESS!!!
Total time to flash a rom:
7-10min
Errors - NONE
This goes for every rom in my guide.
TIPS:
This flash procedure is for Touchwiz Roms, if you are flashing AOSP roms, you must flash the gapps package associated with the rom you are flashing.
**** SGH-I337M Users: Often requires flashing a different kernel than the one included in most ATT ROMS. Any GT-i9505 kernel will work and Adam kernel and Faux kernel are both confirmed working for us Canadian users.
Note: Flash KERNEL directly after ROM then reboot device.
[Special thanks to blyndfyre for this helpful tip].
The extra recovery I flash if a rom does not like the recovery I am using.
Yes, you can flash recoveries back and forth.
Apps.zip I flash after the rom is up & running. This I use to get the rom setup (like root explorer and others needed)
I am in no way responsible for anything that may do damage to any device - Use these tips at your own risk - period!
If you found this useful in any way, please hit the THANKS button for my effort.
RESERVED
TheAxman said:
Any questions? Anyone.
Click to expand...
Click to collapse
I've been running into a lot of issues when trying to flash different ROMs. For instance, right now I'm on CleanROM 1.6 - I just tried to install PureGv2.
Steps I took:
Have Goo and ROM Manager installed after clean install of CleanROM 1.6
Flash CWM from ROM Manager
Install Recovery Script from Goo
Reboot into recover from Goo
TWRP loads
Wipe data, cache, dalvik, etc
Install PureGv2
I forget the error off the top of my head but it doesn't install
In a nutshell I'm asking what am I doing wrong? Do I need to flash another kernel?
Flash your verizon kernel. Correct. I know it is a vzn rom, but do it anyway.
TheAxman said:
Flash your verizon kernel. Correct. I know it is a vzn rom, but do it anyway.
Click to expand...
Click to collapse
Was looking through Tomsgt's Youtube channel and stumbled across a video of his that showed his "About Phone". Everything was identical to mine, so I'm still a little lost as to why I can flash certain ROMs but not others. Sac/Gru's ROM soft bricked my phone, Hyperdrive5.7 didn't install, CleanROM does. It's just funky...maybe I'll just Odin back to stock, flash the MDK and start fresh.
Could the downloads be a problem? I downloaded 2 of the ROMs from work today on a 50meg pipe and they didn't work.
Do you download the ROMs to your phone or to your computer and then move them to your SD card?
If you download to your phone, do you move them to the SD card or leave them in the download folder on the internal storage?
If you do the latter, do you use a micro SD adapter or plug the phone in and move them that way?
harrytery said:
Was looking through Tomsgt's Youtube channel and stumbled across a video of his that showed his "About Phone". Everything was identical to mine, so I'm still a little lost as to why I can flash certain ROMs but not others. Sac/Gru's ROM soft bricked my phone, Hyperdrive5.7 didn't install, CleanROM does. It's just funky...maybe I'll just Odin back to stock, flash the MDK and start fresh.
Could the downloads be a problem? I downloaded 2 of the ROMs from work today on a 50meg pipe and they didn't work.
Do you download the ROMs to your phone or to your computer and then move them to your SD card?
If you download to your phone, do you move them to the SD card or leave them in the download folder on the internal storage?
If you do the latter, do you use a micro SD adapter or plug the phone in and move them that way?
Click to expand...
Click to collapse
Download to the computer,then copy to the phones extsdcard, should be ok, make sure you do a md5 check on the files to make sure they are the correct size.
TheAxman said:
Download to the computer,then copy to the phones extsdcard, should be ok, make sure you do a md5 check on the files to make sure they are the correct size.
Click to expand...
Click to collapse
Alright sounds good. Flashing back to stock later today then re-rooting
thanks for the help
Remember always do a BACKUP before you do anything.
First off, big thanks for this thread.
Now I'm running Cleanrom 1.5. If I wanted to install a new rom can someone please explain exactly what I do to go about it? As jargon free as possible would be awesome.
Sent from my SCH-I545
I certainly scared the carp outta me the other night. I'm using the Carbon ROM and while I do like it, I miss a couple of the S4s features. I picked what looked like a good modified stock ROM and proceeded to flash it.
I'm using Goo and TWRP for the job. I checked of all 3 boxes for clearing cache, davik and factory reset.
Then I chose the file and started it.
The first result, it acted like if was doing everything but nothing changed. Phone still worked fine.
On the next try, I waited for TWERP to start and I reselected the ROM I wanted and flashed it.
When it booted up, I was very happy to see the original screens come up. Then it stopped on the one with the Verizon check mark. The blue LED slowly pulsing and nothing else for about 30 min. I removed battery to try and start over. Same thing again.
Time to goto my backup and restore my phone back to Carbon.
IT FAILED.
Now my phone is stuck in a weird looking boot up loop. After a few tries I was able to get into recovery
mode. TWRP started loading, froze and crashed! Even though I am a total noob at this, I still did not panic.
I'd restart my phone by removing the battery, going into recovery mode and then wildly press every button on my phone hoping to break the loop. It worked! I chose a different save and tried it all over again. FAIL.
ON the next I wiped every bit of old data off. Chose Factory restore crossed my fiingers....it work! My phone is fine now.
Thanks to that ordeal and this thread I think I know what I did wrong even though this never happened to me. before.
1) WIPE THE DATA
2)INSTALL A COMPATABLE KERNAL FIRST
V^^^^V
Vampyre111 said:
I certainly scared the carp outta me the other night. I'm using the Carbon ROM and while I do like it, I miss a couple of the S4s features. I picked what looked like a good modified stock ROM and proceeded to flash it.
I'm using Goo and TWRP for the job. I checked of all 3 boxes for clearing cache, davik and factory reset.
Then I chose the file and started it.
The first result, it acted like if was doing everything but nothing changed. Phone still worked fine.
On the next try, I waited for TWERP to start and I reselected the ROM I wanted and flashed it.
When it booted up, I was very happy to see the original screens come up. Then it stopped on the one with the Verizon check mark. The blue LED slowly pulsing and nothing else for about 30 min. I removed battery to try and start over. Same thing again.
Time to goto my backup and restore my phone back to Carbon.
IT FAILED.
Now my phone is stuck in a weird looking boot up loop. After a few tries I was able to get into recovery
mode. TWRP started loading, froze and crashed! Even though I am a total noob at this, I still did not panic.
I'd restart my phone by removing the battery, going into recovery mode and then wildly press every button on my phone hoping to break the loop. It worked! I chose a different save and tried it all over again. FAIL.
ON the next I wiped every bit of old data off. Chose Factory restore crossed my fiingers....it work! My phone is fine now.
Thanks to that ordeal and this thread I think I know what I did wrong even though this never happened to me. before.
1) WIPE THE DATA
2)INSTALL A COMPATABLE KERNAL FIRST
V^^^^V
Click to expand...
Click to collapse
I can not stress enough HOW IMPORTANT THE KERNEL IS!
Hmm so everyone is a now a Oriental Flash Master from the far East now huh?
What recovery is everyone using?
[updated: 07-12-2013]
Flashing Questions
So, if you just need to add something, like different Kernerl, do you have to wipe and start from scratch?
Should you.
If so, and you backup apps and data in Titanium, then what you do a full wipe, flash entire rom, and reinstall the apps and data associated therewith?
Last, I have asked this but cannot seem to get an answer.
Installed Hyperdrive 7 (also had 5.7 and 6). Rom is super smooth and fast, working like a charm. but I want Verizon Visual Voice Mail.
I tried to copy the apk file to the devices system/app directory but get permission denied message....tried to install, and get failed message....
xander45 said:
So, if you just need to add something, like different Kernerl, do you have to wipe and start from scratch?
Should you.
If so, and you backup apps and data in Titanium, then what you do a full wipe, flash entire rom, and reinstall the apps and data associated therewith?
Last, I have asked this but cannot seem to get an answer.
Installed Hyperdrive 7 (also had 5.7 and 6). Rom is super smooth and fast, working like a charm. but I want Verizon Visual Voice Mail.
I tried to copy the apk file to the devices system/app directory but get permission denied message....tried to install, and get failed message....
Click to expand...
Click to collapse
did you set the permissions for the app? That should work actually. Look at one of the apps in that directory, and set the permissions the same for the voice app. Reboot and see what happens.
Good luck.
May want to post this question also in my guide thread.
http://forum.xda-developers.com/showthread.php?t=2295557
Sorry if this is dumb, but how do I know what kernels for sure work with my device and how do I get them to my external sd card? I suppose the one that is currently on my device(how to get that to sd?), but what others?
Thanks.
Painterface said:
Sorry if this is dumb, but how do I know what kernels for sure work with my device and how do I get them to my external sd card? I suppose the one that is currently on my device(how to get that to sd?), but what others?
Thanks.
Click to expand...
Click to collapse
Please bring the question over to my thread up above. It shows also what kernels to use. We will help there.
Another noob question: so you still advise flashing a kernel even if the ROM creator says that the ROM comes with the appropriate kernel and that no extra flashing is required? I've got the Verizon Galaxy S4 variant and specifically am thinking of Dubbsy's Google Play Edition ROM.
Sent from my SCH-I545 using Tapatalk 2
theoneknownasbob said:
Another noob question: so you still advise flashing a kernel even if the ROM creator says that the ROM comes with the appropriate kernel and that no extra flashing is required? I've got the Verizon Galaxy S4 variant and specifically am thinking of Dubbsy's Google Play Edition ROM.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
You would flash the rom, and after, flash your verizon kernel, simple as that.
I have a Samsung Galaxy Tab S LTE (SM-T805). When I do "adb recovery" or when I do "power+vol up" it boots into a "revovery" which says
Android system recovery <3e>
LRX22G.T805XXU1B0D1
etc
I would like to know,
1) is this part of the original/stock Samsung firmware/software, or is it something that was downloaded on the tablet by the previous owner? (I bought the tablet second hand)
2) do I need to install another bootloader if I wanted to install another ROM or is this good enough?
3) could someone please tell me how to install another bootloader?
Many thanks
1) 3e is the stock recovery.
2) You should not need a new bootloader if you are using roms based on the same firmware - LRX22G or similar
a) If you need a new bootloader, it will be mentioned by the developer of the rom you are using.
3) I believe what you are actually looking for is a custom recovery - this is needed to install roms that are not signed directly by Samsung.
http://forum.xda-developers.com/galaxy-tab-s/development/root-cf-autoroot-twrp-t800-t3079488
thanks. Another couple of qiestions please:
1) I have installed TWRP and it works really nicely. Is there a way to go back to the "official" stock recovery? Where would I get it from?
2) I have also installed and tried different ROMs, like liquid-something, ice-something, ironman-somethhing. Does this mean that my tablet now "remembers" that it has been hacked somehow?
3) I forgot to backup the stock ROM, before I installed other custom ones. Where could I get the stock ROM from? I have looked for it but I cannot really get my hands on it.
Many thanks
Zilliman said:
thanks. Another couple of qiestions please:
1) I have installed TWRP and it works really nicely. Is there a way to go back to the "official" stock recovery? Where would I get it from?
2) I have also installed and tried different ROMs, like liquid-something, ice-something, ironman-somethhing. Does this mean that my tablet now "remembers" that it has been hacked somehow?
3) I forgot to backup the stock ROM, before I installed other custom ones. Where could I get the stock ROM from? I have looked for it but I cannot really get my hands on it.
Many thanks
Click to expand...
Click to collapse
1) Sometimes developers will provide a link to the stock recovery, but I did not see one when glancing around the forums. If you use the method mentioned in step 3, then you will be back on the stock recovery.
2) No. As long as you wipe /system, /data, /cache, and /dalvik cache then nothing important will be left from any previous rom flash. (Some roms will leave folders on your internal SD card that you can delete manually).
3) You'll find the stock rom here. This would need to be done in Download Mode with Odin. This will overwrite everything on the tablet and be like it was brand new. http://forum.xda-developers.com/galaxy-tab-s/general/samsung-lollipop-range-tab-s-t3021612
es0tericcha0s said:
1) Sometimes developers will provide a link to the stock recovery, but I did not see one when glancing around the forums. If you use the method mentioned in step 3, then you will be back on the stock recovery.
2) No. As long as you wipe /system, /data, /cache, and /dalvik cache then nothing important will be left from any previous rom flash. (Some roms will leave folders on your internal SD card that you can delete manually).
3) You'll find the stock rom here. This would need to be done in Download Mode with Odin. This will overwrite everything on the tablet and be like it was brand new. http://forum.xda-developers.com/galaxy-tab-s/general/samsung-lollipop-range-tab-s-t3021612
Click to expand...
Click to collapse
Again, many thanks.
The link you provided further directs you to some weird paid-for download sites, could not get anywhere with them. I would not mind paying say 10p for a one-off file download, but they want you to pay monthly etc, seriously...
However, for UK generic ROM, I got this file "SEE-T805XXU1BOD1-20150511102748.zip" which I got off some Russian or something web site, it was uploaded to Google Drive, so it was easy to download.
A serious issue I have discovered, and am not sure what the right steps are, is when installing TWRP, the installation seems not to "catch", so after the upload you still have the old bootloader. The way I got that to work was to uncheck the "reboot" flag in Odin, waited until the download was complete, and then after a while manually switched the phone off (I think it is menu+vol down+power) and then switched on again using menu+vol up+power and that got me into TWRP at last.
Anyway now it seems I am back to the stock ROM, and stock bootloader, and as you said, if I ever returned the tablet for a service they would not be able to tell that I had flashed other ROMs?
tl;dr - Can't seem to find my way out of a software brick. Have sideloaded the stock OS from 1+ but still forever getting the spinning dots or fastboot screen, depending on which mode i boot into.
Hi all. Signed up to make this thread, but i've been lurking for years.
I have a OnePlus X that is about the least modded smartphone i've ever owned. I've never been pleased enough with a retail product that i didn't feel compelled to strip out the bloat and start over, until this phone. Other than stock, i've just got a gallery app, some apps for manipulating text files or compiling code, couple games, and social media apps.
Anyway, a few days ago i got a notification about a software update. Downloaded. Installed. Updated. No problem.
Maybe yesterday or the day before, it showed up again. This morning i downloaded, installed, and suddenly i have apps closing. It's been over 12 hours so i'm hazy on how it all started, but i was getting something like "package installer" errors when attempting to open some apps. Same deal when i went to adjust permissions of those affected apps. Every time i unfocused a box that had pulled up swype, i would get an error message saying swype crashed or closed or something.
So i started uninstalling third party apps (i don't keep many, and most i've had for years so i think they're probably trustworthy). Same deal. Started uninstalling updates to google apps. Same deal. Went to uninstall and reinstall some non stock apps that i'd kept previously. Nothing.
I went to cook breakfast while an app was reinstalling, and i came back to a red dot on my screen with two white dots chasing each other around it. From what i'm reading that's a sign of a bootloop or software brick. I've taken all steps i could find, including wiping cache and sideloading a fresh stock OS, but to no avail.
Is it that i've ruined my google apps somehow and need to restore them? How would i even go about figuring out what the problem is? Any advice or guidance is appreciated
Hi,
As your device is in bootloop state, try flashing the stock rom. Make sure you wipe data and cache. As far as after update problems, i faced it few times. After updating many app crashed and phone hangs. So i prefer clean flash over dirty flashing, to make sure everything is hazel free. For the time being i upgraded from 3.1.2 to 3.1.3 without wiping data or cache and facing no problem( of course since it was an OTA). But sometimes situation comes when after update phone act weird, so tbe option which i prefer then is clean flashing the stock rom. Hope this helps.
"A09" said:
Hi,
As your device is in bootloop state, try flashing the stock rom. Make sure you wipe data and cache. As far as after update problems, i faced it few times. After updating many app crashed and phone hangs. So i prefer clean flash over dirty flashing, to make sure everything is hazel free. For the time being i upgraded from 3.1.2 to 3.1.3 without wiping data or cache and facing no problem( of course since it was an OTA). But sometimes situation comes when after update phone act weird, so tbe option which i prefer then is clean flashing the stock rom. Hope this helps.
Click to expand...
Click to collapse
I have wiped cache, deleted data, tried a factory reset in the stock bootloader, and i have used ADB to sideload a full stock rom (not upgrade package) that i downloaded from OnePlus.
Flash old stock recovery then 2.2.3. From there you can flash any MM stock firmware.
Exodusche said:
Flash old stock recovery then 2.2.3. From there you can flash any MM stock firmware.
Click to expand...
Click to collapse
Pardon me for being nooby, but how do i do this? Do i just sideload in ADB like i did the ROM? Most instructions i'm finding assume access to the OS either normally or through fastboot. I'm just stuck in the default recovery.
Thanks for the tip, though. Looking for a copy of the old stock recovery now. Did OnePlus alter their stock recovery recently? In some threads i've seen people say that a recent update made them unable to load a non-stock ROM. Is that the new recovery blocking access to non-1+ operating systems?
jtg1984 said:
Pardon me for being nooby, but how do i do this? Do i just sideload in ADB like i did the ROM? Most instructions i'm finding assume access to the OS either normally or through fastboot. I'm just stuck in the default recovery.
Thanks for the tip, though. Looking for a copy of the old stock recovery now. Did OnePlus alter their stock recovery recently? In some threads i've seen people say that a recent update made them unable to load a non-stock ROM. Is that the new recovery blocking access to non-1+ operating systems?
Click to expand...
Click to collapse
Fastboot flash easiest way. Make sure it's the old recovery from 2.2.2. Not the new mm stock recovery.
Yes, but how do i install the old stock recovery? I dug around on the forums and found the file, but the phone rejects it when sideloading and doesn't show the .img in the filesystem when inserted on a SD card.
Have to send it off to 1+ maybe? Literally all i can access right now is the (new) stock recovery. I never modded, rooted, etc before the software update sent me into the chasing dots
jtg1984 said:
Yes, but how do i install the old stock recovery? I dug around on the forums and found the file, but the phone rejects it when sideloading and doesn't show the .img in the filesystem when inserted on a SD card.
Have to send it off to 1+ maybe? Literally all i can access right now is the (new) stock recovery. I never modded, rooted, etc before the software update sent me into the chasing dots
Click to expand...
Click to collapse
I m not a dev, i m a newbie like you. i hv done a lot of experiments with my oneplus-x, as for u the first update u got few days back should be oos 3.1.2 and the one u got 2 days before should be 3.1.3. When u upgrade from lollipop to marshmellow, even your stock recovery got upgraded to latest version, which is something different from old lollipop recovery.
You said you have access to recovery mode. thts pretty much gud, what u can do is that wipe data and cache through stock recovery and do a clean install of oos 3.1.3. I ll be providing all the necessary links down below. If you need assistance with fastboot cmds and anything feel free to ask.
Thanks to original link provider @Sachin7843
Useful Links: -
1. Stock Lollipop Recovery - https://s3.amazonaws.com/oxygenos.oneplus.net/OPX_recovery.img
2. Official TWRP Recovery - https://dl.twrp.me/onyx/
3. Blu Spark Recovery - http://forum.xda-developers.com/devdb/project/dl/?id=20236
4. SuperSU for OOS 3.x.x - https://drive.google.com/file/d/0B4K5cvm1zdldcmZpc3RuVnRjUUE/view
5. Unbrick Guide - http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
6. Official Oxygen OS 3.1.3 link - https://s3.amazonaws.com/oxygenos.o...OTA_018_all_201609291837_741146bcf28e4587.zip
7. SD Card Writable fix in MM - http://forum.xda-developers.com/android/software/fix-extsd-fix-v1-0b-2016-01-18-t3296266
8. For Stock MM Recovery - http://forum.xda-developers.com/oneplus-x/general/oxygenos-3-1-0-marshmallow-community-t3445043
Sorry for my bad english
jtg1984 said:
Yes, but how do i install the old stock recovery? I dug around on the forums and found the file, but the phone rejects it when sideloading and doesn't show the .img in the filesystem when inserted on a SD card.
Have to send it off to 1+ maybe? Literally all i can access right now is the (new) stock recovery. I never modded, rooted, etc before the software update sent me into the chasing dots
Click to expand...
Click to collapse
Don't sideload it, use fastboot to flash it. "Fastboot flash recovery name.img" - without he quotes and the image name.
Sorry for vanishing. Had a busy week.
Not sure what happened the first time i tried to put the 2.2.3 image on the SD card, because the file didn't show up in my recovery, but i tried again later (after giving up on flashing the old recovery, since i couldn't figure out how to do that in recovery) and managed to do a clean install of the older OOS version.
That did the trick, and after booting up, my phone proceeded to update again - this time without any crashes or errors with my apps afterward. The phone still does the red dot with the white dots chasing around it when it boots up, which must be the new boot screen. It also seems to stay on that screen for much longer than it stayed on the old morphing shape boot screen, but it still boots up reliably now after 30-60 seconds rather than freezing in boot forever.
I've since enabled dev mode on my phone. Is that going to be enough to enable ADB commands from recovery? I kind of like that i've kept my phone stock, so i'll leave it that way if i can, but it would have been much easier to fix this problem if i'd had access to most of my debug commands. As it was, without dev mode and in the standard recovery, it seemed that sideload was the only command i was able to use, and only when the phone was requesting a sideload over usb