Lost wifi again! was doing the normal backup and return to stock again to get the wifi back and it packed up on me, no longer accepting touch input. So I am stuck can't try to reload it, in the hope its software. right now its version 2.0.5 or something like that. Can't use the recovery since the touch is not working. Is there any working non-touch recoverys or is there a stock like firmware that can be loaded with out twrp touch. I still can fastboot flash the recoveries none work I have tried all the twrp version I could find.
I can plug a mouse in with a usbtg adapter but that is not useable in twrp.
I have opened it up to make sure a cable was not loose on the screen, and it was not dropped or broken in anyway.
Anyone who can hear my call HELP!
theskyisoutthere said:
Lost wifi again! was doing the normal backup and return to stock again to get the wifi back and it packed up on me, no longer accepting touch input. So I am stuck can't try to reload it, in the hope its software. right now its version 2.0.5 or something like that. Can't use the recovery since the touch is not working. Is there any working non-touch recoverys or is there a stock like firmware that can be loaded with out twrp touch. I still can fastboot flash the recoveries none work I have tried all the twrp version I could find.
I can plug a mouse in with a usbtg adapter but that is not useable in twrp.
I have opened it up to make sure a cable was not loose on the screen, and it was not dropped or broken in anyway.
Anyone who can hear my call HELP!
Click to expand...
Click to collapse
You can use open recovery script to still use TWRP without touch. So you are saying you have no touch in Android or TWRP right? What happened right before the touch stopped working?
attempted to unroot
aicjofs said:
You can use open recovery script to still use TWRP without touch. So you are saying you have no touch in Android or TWRP right? What happened right before the touch stopped working?
Click to expand...
Click to collapse
I attempted unroot as I have had to do before to get wifi back working. I did a wipe and restore the factory firmware then reset to do that whole wifi issue fix process and poof no more touch in either place but I can hook up a mouse in the android system. I can go in to twrp but the only twrp for this is touch. I am almost positive that my restore to factory backup was bad /corrupt because that's when it happened. Also the firmware verson also the apps and all were not removed so I am assuming it went bad doing the firmware. I don't care about loosing things. I have stock firmwares but can't load it. IF I had a non touch way to replace the firmware I think that would fix it all.
Anyideas how to push a firmware for that nabi 2 deal. or a place I can get the .win image to push it (if that would even work) I have a 19. something .win one but I tried to push it and it writes but does not apply it even after factory reset following that. Just stuck here now.
theskyisoutthere said:
I attempted unroot as I have had to do before to get wifi back working. I did a wipe and restore the factory firmware then reset to do that whole wifi issue fix process and poof no more touch in either place but I can hook up a mouse in the android system. I can go in to twrp but the only twrp for this is touch. I am almost positive that my restore to factory backup was bad /corrupt because that's when it happened. Also the firmware verson also the apps and all were not removed so I am assuming it went bad doing the firmware. I don't care about loosing things. I have stock firmwares but can't load it. IF I had a non touch way to replace the firmware I think that would fix it all.
Anyideas how to push a firmware for that nabi 2 deal. or a place I can get the .win image to push it (if that would even work) I have a 19. something .win one but I tried to push it and it writes but does not apply it even after factory reset following that. Just stuck here now.
Click to expand...
Click to collapse
If you have touch in Android install this https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager push your backup and use the program to make the open recovery script for you.
no touch anywhere. and no wifi!
Like I said no wifi and no touch at all anywhere So going online Iis a no go. I can use a mouse on the android system. Also I beleve my backup firmware is what caused the issue with the touch. Again this is a nabi 2 so now its been reset no file manager either access a apk from the sdcard if I could get the apk for that.
update
browser loaded the twrpmanager apk with that installed stock image now wifi works but no touch still what am I missing with the touch? Trying the stock update to see if that corrects anything I doubt it though
over post sorry
I know I am over posting on my own thread... sorry about that.
Had a thought. Since I am not great at describing what I need to accomplish here, try to work with me on this.
I need to just complete start over GO FOR BROKE format and push out the rom with adb How can I get started to do this and what do I need?
I feel that something in the touch input is not working based on some part of the rom is hosed. even tried the original recovery gives that android error icon thingy and I see nothing till she restarts nothing changes.
OK if you want to go for broke... You have to have an external SD card for this. TWRP must be installed
Hook Nabi up via USB can be in Android or TWRP
1) Download this: Nabi 2 stock
2) Unzip the NABI2STOCK.zip
3) Go here: http://forum.xda-developers.com/wiki/Fuhu_nabi_2
4) Grab either the 2.0.5 or 2.1.27 stock rom
5) Put the downloaded ROM zip in the "install" folder that was made in #2. Dont unzip, just download it straight to the install folder
6) Run 205.bat or 2127.bat depending on which ROM you chose.
The script will extract the ROM from the zip, copy the stock ROM to your external SD card, create an openrecoveryscript that will format system, format data, and restore Boot and System partition. Data will be left blank. This erases everything, except hidden partitions and recovery partition.
downloading will update when its done
downloading now will update when I run it. I hope things fixes it. as I have hosed it so far.
I get an error
I get an error
mkdir: can't create directory /external_sd card/twrp/backups/015d2a50211c1a19/abcdstock or something like says directory does not exist odd error it went thought its cycle and exited after that.
I do have an external sd card in it and it is working. did not know if that was an sd card error or what
no touch still
sadly no touch still.
Should I assume its hardware now? or do I have any hope its software?
The version and all changed so I know it did something but no touch
theskyisoutthere said:
sadly no touch still.
Should I assume its hardware now? or do I have any hope its software?
The version and all changed so I know it did something but no touch
Click to expand...
Click to collapse
It seems hardware now, but it is odd that touch went out when you were doing things to it. Still under warranty? Have you taken it apart and seen if anything is wrong?
Related
I had done the original root/gapps install on this. Then had problems with gapps. So I went back into TWRP and I had a restore called stockunrooted. I restore it, and when I go to reboot it says "Warning, No OS installed". Sure enough, it boots to a little Nabi logo with no motion. And just sits there. I used TWRP file manager and don't see any files in /boot after I do a restore. /boot and /system seem to restore instantly. I'm good with PC's, Networks, and Linux, but not Android hacks. Is there something I can download, push with ADB, then load with TWRP that will fix me up? I think that's how I got the STOCKUNROOTED that is already there though
Got Nabi2
Rooted with jmz?? method and also installed his gapps
Nabi wouldn't power on right without reset hole after a week or 2
Restored stockunrooted, worked fine, no more power on problem, but no root or gapps
Rooted per jmz method, worked, no gapps.
Wanted to install gapps, so restored stockunrooted again, now nothing
At least TWRP works. It's wifes though, and she isn't into just using it for TWRP.
- Joe
JoeLansing said:
I had done the original root/gapps install on this. Then had problems with gapps. So I went back into TWRP and I had a restore called stockunrooted. I restore it, and when I go to reboot it says "Warning, No OS installed". Sure enough, it boots to a little Nabi logo with no motion. And just sits there. I used TWRP file manager and don't see any files in /boot after I do a restore. /boot and /system seem to restore instantly. I'm good with PC's, Networks, and Linux, but not Android hacks. Is there something I can download, push with ADB, then load with TWRP that will fix me up? I think that's how I got the STOCKUNROOTED that is already there though
Got Nabi2
Rooted with jmz?? method and also installed his gapps
Nabi wouldn't power on right without reset hole after a week or 2
Restored stockunrooted, worked fine, no more power on problem, but no root or gapps
Rooted per jmz method, worked, no gapps.
Wanted to install gapps, so restored stockunrooted again, now nothing
At least TWRP works. It's wifes though, and she isn't into just using it for TWRP.
- Joe
Click to expand...
Click to collapse
Flash this in twrp:
http://www.androidfiles.org/securekey.php?file=Nabi2/JmzNabi2Stock_OLD.zip
Sent from my One X using xda app-developers app
GuyIncognito721 said:
Flash this in twrp:
http://www.androidfiles.org/securekey.php?file=Nabi2/JmzNabi2Stock_OLD.zip
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Ok, I got that. Having problems getting TWRP to see it. I tried from SD card, tried copying it into sd-ext, sdcard, external_sdcard, sdcard/twrp/backups. No luck. If I click Install from sdcard it shows me /sdcard/root.zip so I tried putting it in there but no luck when I click recovery. I tried setting permissions on the zip to 777. What on earth am I doing wrong. I spent about an hour with google searching before I came back here. I'm on TWRP v2.2.2.1
- Joe
JoeLansing said:
I had done the original root/gapps install on this. Then had problems with gapps. So I went back into TWRP and I had a restore called stockunrooted. I restore it, and when I go to reboot it says "Warning, No OS installed". Sure enough, it boots to a little Nabi logo with no motion. And just sits there. I used TWRP file manager and don't see any files in /boot after I do a restore. /boot and /system seem to restore instantly. I'm good with PC's, Networks, and Linux, but not Android hacks. Is there something I can download, push with ADB, then load with TWRP that will fix me up? I think that's how I got the STOCKUNROOTED that is already there though
Got Nabi2
Rooted with jmz?? method and also installed his gapps
Nabi wouldn't power on right without reset hole after a week or 2
Restored stockunrooted, worked fine, no more power on problem, but no root or gapps
Rooted per jmz method, worked, no gapps.
Wanted to install gapps, so restored stockunrooted again, now nothing
At least TWRP works. It's wifes though, and she isn't into just using it for TWRP.
- Joe
Click to expand...
Click to collapse
i hope ya wasnt using the mic hole on the bottom of the Unit
http://www.nabitablet.com/specs/nabi2
IF i were you i would Search the forum "nabi 2"
you will find a lot of post with downloads and things that people have done to help get their nabi 2 up and running.
HTH
I used the reset hole and I've already downloaded all the jmz files and a few more. I've read about Nabi here for hours. My last try was restoring JMZ_OLD to get back to factory. Still no WiFI. Then I tried installing the WiFI_Fix. Now it just shows a spinning Nabi logo. I rooted my 4th one today using the new Nabi Lab which I really like! My wife's is the only one that is a problem child. Funny thing is the other 3 were bought at Walmart, hers was bought at GameStop. I think from reading the Cannot Turn on WiFi is a version problem between the drivers and the kernel, but not sure. I really want to try Nabi Lab on it but I think it is old Nabi software at this point, and Nabi Lab says I should be fully updated to run it. But I can't update it without WiFi...grrrrrrrrr. Is there anything I can do to restore it to stock including stock kernel and drivers? Who knows, maybe the WiFI has a hardware problem? But I doubt it. If I use JMZ_Old, then the 2 OTA update files, then ??? I'm not sure I've tried that yet. I wipe everything between attempts. 3 more posts and I can go thank the gentelman that made Nabi Lab in that thread and tell him I tested it and it worked fine.
- Joe
I wonder if you have a Different Nabi 2 then i do ?
coz the only hole I have that looks like a reset hole is for the mic
http://forum.xda-developers.com/showthread.php?t=2050365&highlight=nabi
has a few different downloads like a striped rom a full untouched version and a full de-odexed version.
maybe try that one
.---UPDATE---
New Rom available.
Completely stock.
Not even De-Odexed.
Update 37.
SHOULD fix WiFi issues.
Flash using directions at top of post substituting this zip for the one used in the directions.
PureStockU37.zip
that is the updated 1.9.37 Current at the time of this post
Ok, I'm a moron. My reset hole is the mic, which is now pretty dead...:crying: The good news is Nabi Lab fixed my WiFi and soft brick problems. I had tried about every image out there including that one you suggested. Using Nabi Lab and flashing the hmm All Original - Won't Boot or something like that fixed it. Since I never use the mic I'm ok. I could probably replace it if I wanted to, but I'll give it a rest before I break it again.. I have 3 Nabi's, and 2 Uniden tablets. I killed one of the Unidens. The screen got worse and worse. I popped it apart and tried to reattach the 2 wires to the screen half. It started smoking and doesn't power on.. Now I might take the battery off it and see if I can solder it into the other Uniden to get longer life. I hope it doesn't get hot.
Eric Karz said:
I wonder if you have a Different Nabi 2 then i do ?
coz the only hole I have that looks like a reset hole is for the mic
http://forum.xda-developers.com/showthread.php?t=2050365&highlight=nabi
has a few different downloads like a striped rom a full untouched version and a full de-odexed version.
maybe try that one
.---UPDATE---
New Rom available.
Completely stock.
Not even De-Odexed.
Update 37.
SHOULD fix WiFi issues.
Flash using directions at top of post substituting this zip for the one used in the directions.
PureStockU37.zip
that is the updated 1.9.37 Current at the time of this post
Click to expand...
Click to collapse
that's good you got the nabi working
Now that nabi with the bad speaker ... i wonder if you can use the speakers from the dead Uniden in the nabi 2 ?
here is a thread where the nabi 2 was open up
http://forum.xda-developers.com/showthread.php?t=2024105&highlight=nabi
If you try the battery project or the speaker replacement - be neat to see pictres of it....lol
Speaker was a beer typo.. I meant the mic. I'm an old man and have no use for croaking at people over the interweb with a microphone so I'm ok.. I started a thread someplace about the Uniden tablets. I checked back and it's like 9 pages long with geeks installing Ubuntu and everything else on them. I was amazed! I'm going to get real and get an Onda V972 soon I hope. Now that I have enough posts here I will probably start a thread about buying one of them.
- Joe
Eric Karz said:
that's good you got the nabi working
Now that nabi with the bad speaker ... i wonder if you can use the speakers from the dead Uniden in the nabi 2 ?
here is a thread where the nabi 2 was open up
http://forum.xda-developers.com/showthread.php?t=2024105&highlight=nabi
If you try the battery project or the speaker replacement - be neat to see pictres of it....lol
Click to expand...
Click to collapse
Help brick
Sorry my english.
I was trying to install the GAPPS on nabi2 and messed up.
The kernel recovery screen appears with a exclamation android open.
In normal boot the screen is locked in logo nabi.
I do not have TWRP installed.
When I select fastboot protocol recognizes the PdaNet and appears as a device in windows mtp unknown.
Is there any chance to recover? Could guide me the way?
There is some recovery via APX?
RegisRicci said:
Sorry my english.
I was trying to install the GAPPS on nabi2 and messed up.
The kernel recovery screen appears with a exclamation android open.
In normal boot the screen is locked in logo nabi.
I do not have TWRP installed.
When I select fastboot protocol recognizes the PdaNet and appears as a device in windows mtp unknown.
Is there any chance to recover? Could guide me the way?
There is some recovery via APX?
Click to expand...
Click to collapse
Need to reinstall TWRP with fastboot.
Download a ROM image and restore it in TWRP.
There is an APX way but so far untested and not needed for where you are at.
Thanks for the help, after a snack could reconfigure.
I'm trying to install Freedom but is difficult. There is not enough system memory.
I updated to 2.1, but I think I'll go back to 2.05.
Trying to install MeanBean...I updated the Firmware to the latest, have the phone unlocked and rooted (it says TAMPERED and UNLOCKED in the recovery screen) and did a factory reset. I have TWRP installed and can still get to the TEAMWIN RECOVERY project interface...
I was installing MeanBean and it just stuck on about 75% and stayed there. I waited for about ten minutes and figured something must have gone wrong so I didn't really have a choice but to shut it down. After starting back up when I tried to install again it said "FAILED" in red letters. I decided to re-download the ROM but now when I mount the SD CARD from within the recovery menu (to transfer the new file) my computer says that I must format the drive before I can use it and won't let me see the contents of the sd-card. I didn't want to do that for fear of bricking...so I don't really know what to do from here. I should add that I don't have a backup made in TWRP (I got the phone yesterday and hadn't installed or done anything to the OS)
Anyone know what should be done at this point?
thx
I'm updating this for anyone else who runs into issues like this: I went ahead and formatted the SD card from within windows, then relocked the phone, reinstalled the RUU and I'm back in a workable mode
itsmattgw said:
Trying to install MeanBean...I updated the Firmware to the latest, have the phone unlocked and rooted (it says TAMPERED and UNLOCKED in the recovery screen) and did a factory reset. I have TWRP installed and can still get to the TEAMWIN RECOVERY project interface...
I was installing MeanBean and it just stuck on about 75% and stayed there. I waited for about ten minutes and figured something must have gone wrong so I didn't really have a choice but to shut it down. After starting back up when I tried to install again it said "FAILED" in red letters. I decided to re-download the ROM but now when I mount the SD CARD from within the recovery menu (to transfer the new file) my computer says that I must format the drive before I can use it and won't let me see the contents of the sd-card. I didn't want to do that for fear of bricking...so I don't really know what to do from here. I should add that I don't have a backup made in TWRP (I got the phone yesterday and hadn't installed or done anything to the OS)
Anyone know what should be done at this point?
thx
Click to expand...
Click to collapse
I had the exact same problem. I just reformatted the internal storage and that fixed a lot of my issues. I can't however get the RUU to work. Can't seem to find my phone, neither can HTC Sync. Is this just a problem caused by MeanBean? I use to run MeanBean but then switched to CM10 for a few months and was going to switch back. Never had an issue like this before.
Hi,
I have an lg c800 -- mytouch q by lg
I rooted it yesterday and removed all the bloat. I also installed several root only apps to optimize the phone.
It ran smoother than even right out of the box.
So, I figured it be a good idea to backup the rom, and maybe later try cyanogenmod... So I installed Rom Manager by clockworkmod
It said i needed to install clockwork recovery rom. I went in there but it said my device was unsupported (only like 12 were) so I backed out,
and stupidly hit TWRP listed under "Recovery Already Installed". (thinking that meant what options I had to SETUP a recovery/backup)
I hit backup rom. almost instantly the phone restarted. After the bios, but before android it went to a screen with a box, and an arrow pointing from the inside of the box to the little android man. Then went to the regular android boot screen.
It does this every reboot now. The SuperSU is still there, whenever Rom Manager (which I have to reinstall each reboot) asks for root access I get that dialog box, so it hasn't actually hard reset the phone I don't think. But all the user data, contacts, apps, wifi passwords, google id "(to access Play) get wiped out.
I understand what I did wrong. I think I understand what its doing (booting to the factory rom as it was, and I can't set it to stop doing it each reboot)
What I need help with is getting back, if possible, to what I had previously, among other things, I had a bunch of tasker profiles and notes that will be time consuming to replace.
Thank you for your help.
EDIT: SuperSU is now listed among the factory installed apps. This is unchanged each reboot.
Question: If I unroot the phone what that invalidate Rom Managers ability to run before android boots?
where the people at?
dosmastr said:
where the people at?
Click to expand...
Click to collapse
going off of this page:
http://forum.xda-developers.com/showthread.php?t=1752704
for cwm recovery
drivers are all installed (I was able to root phone)
but the adb devices command comes up empty.
what gives?
dosmastr said:
going off of this page:
http://forum.xda-developers.com/showthread.php?t=1752704
for cwm recovery
drivers are all installed (I was able to root phone)
but the adb devices command comes up empty.
what gives?
Click to expand...
Click to collapse
OK so its not in the guide, but one is to exit the shell BEFORE keying adb devices. it does show.
but sadly I don't think this gets me closer to fixing what is broken.
Can anybody at least tell me if my stuff is still there or gone?
I have the impression that the boot loader is grabbing the stock rom and just expanding it and running it each boot, but that the old functional rom is still there but being unused --- like a dual boot type thing.
Am I off in left field here or?
dosmastr said:
Can anybody at least tell me if my stuff is still there or gone?
I have the impression that the boot loader is grabbing the stock rom and just expanding it and running it each boot, but that the old functional rom is still there but being unused --- like a dual boot type thing.
Am I off in left field here or?
Click to expand...
Click to collapse
more info: the bloat from the original rom is still gone, and SuperSU is intact and functional
Chui says its some flag in CWM that isn't getting cleared when the device boots.
I'm just trying to get the data my apps help at this point.
cmon phone nerds i still need some help!
no help.
The original ROM of your phone got modified after you rooted, hence no bloat and SuperSU intact even after many wipes.
I suggest re installing the factory ROM again, including the bootloader, radio and other stuff. That ought to fix the issue.
What phone do you have ?
So when it was modifying the rom that was running at the time, also the recovery rom was modified?
how do you reinstall factory rom if the phone never enters fastboot?
I'm all about wiping the bootloader (so it STOPS running recovery) but I have only made a little progress in finding how to do that without fastboot.
What I can do is run a root viewing file manager. I even found the log for the recovery it keeps running. But not what to kill so that it STOPS recovering.
Phone is LG C800DG
The LG rom update software has a recovery option but that didn't work.
One youtube video
http://www.youtube.com/watch?v=nDFO6H1XObI
Says I can get around this by using a flash utility the installs as an apk. I doubt I'll find one compatible with this phone though as support is very limited.
looks like everything out there says I need a 3rd party recovery already flashed...so that I can flash a stock rom.
sounds like the damn chicken and egg to me, to get stock fixed you need 3rd party but since you have stock you cant get 3rd party
It seems to be a general problem with your set as many others too have posted the same issue.
For stock ROM this should work.
http://forum.xda-developers.com/showthread.php?t=1825818
And a flashing guide
http://blog.androidia.net/8/how-to-flash-stock-lg-rom/
You can also see these for CM9
http://wiki.cyanogenmod.org/w/C800_Info
and
http://forum.xda-developers.com/showthread.php?t=1801622
Dumb e3 recovery. There been any updates on the cwm recovery? Thing takes forever to backup and restore rom
I am rooted and S-Off. I am using the ViperOne custom ROM for my phone.
The end goal is for me to update my firmware, because my phone has an over 10 minutes boot time normally. (Not an exaggeration. I have actually timed it with a timer.) I read that in order to fix this, I should try to update the firmware by going to stock recovery and doing an OTA update.
My TWRP has worked flawlessly for me over the years, but for some reason it won't work anymore. It will hang on the boot screen for over an hour. After that hour, I assumed it's not slowly booting. (As a bit of background, recovery would boot quickly while my phone still had problems with 10 minute boot times).
Another piece of information is that the last time TWRP worked was when I used it to install .zip files from Titanium to get all my apps working. That worked perfectly fine, my apps got updated, and no trouble. I wish I could say what happened between then and now, but from what I can remember, I just used my phone normally, such as using web browsers and games. I don't remember messing with any system files.
I do know that ClockWorkMod recovery DOES work if I flash that, but my nandroids are all on TWRP. I have tried to flash different version of TWRP as well. It doesn't seem to matter which one I flash, my phone reacts exactly the same.
Another thing to note, I'm not sure if it's significant or not, is that when I got into hboot, I get the following message for a split second. I can't read the file names exactly, but I got the extensions. Then I get the normal screen with the vol instructions and choices to go to fastboot, recovery, etc... The message reads:
SD Checking...
Loading [(something).zip]
No Image!
Loading [(something).nbh]
No Image or wrong image!
Loading [(something).zip]
Loading [(something).nbh]
No Image or wrong image!
I hope this is a decent amount of information. I tried to include as much as I could, but if I'm missing any critical details, let me know and I will GREATLY appreciate your help!
have u tried to rewrite the image, download the new TWRP and load it via adb
Bradl79 said:
have u tried to rewrite the image, download the new TWRP and load it via adb
Click to expand...
Click to collapse
Well, I did do that. I rewrote different versions of the image and none worked.
Sadly, my solution was to completely wipe my phone. More than the default factory reset.
I'm so it has been solved, but probably not in the most practical way for others with a similar problem.
Battletooth said:
Well, I did do that. I rewrote different versions of the image and none worked.
Sadly, my solution was to completely wipe my phone. More than the default factory reset.
I'm so it has been solved, but probably not in the most practical way for others with a similar problem.
Click to expand...
Click to collapse
Having the exact same issue. Attempted to install twrp-2.8.6.0-m8.img using adb, but TWRP never loads. I can load prior versions but same results. Going to HBOOT I get a bunch of messages related to 0P6BDIAG.zip, 0P6BIMG.zip
and some .nbh. I think it's looking on my SDCARD for those.
If you're looking to update your firmware, you can use an official RUU to change the firmware of your phone. You can read more about it in this stickied thread in the general forum to see if it fits your needs. If you decide to do this, your phone will be completely stock after the RUU finishes running so use fastboot to flash TWRP (or whichever recovery you prefer).
Regarding the messages you see in hboot, it will always check for those files if you have an external sdcard mounted. If they are present, you will be given the option to flash the update. If not, you will get regular hboot access after the check. It is completely normal and nothing to worry about.
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