Develop Bugs

Help with Nexus 7 (2013)

I have a Nexus 7 (2013) that I installed an Android 5.0 lollipop ROM on. I also had TWRP recovery installed. It was working fine. I took the OTA update for 5.0.1. It would not install with the recovery installed. Long story short, I believe I wiped something I shouldn't have. I can install the factory images using WUGS toolkit. The tablet boots and I can do the set-up. Wi-fi works, bluetooth works. I can't download files from the internet, I get a No SD card message. The play store, camera, gallery do not work. Trying to use the gallery I get a No Storage, no external storage available message. I'm not sure where to go from here. Any help would be appreciated. Thanks.

starrider1300 said:
I'm not sure where to go from here. Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
Did you try a factory reset from recovery?
You should learn how to flash manually with fastboot, as you can see toolkits are not always helpful.

meekrawb said:
Did you try a factory reset from recovery?
You should learn how to flash manually with fastboot, as you can see toolkits are not always helpful.
Click to expand...
Click to collapse
I tried flashing with fastboot with the same results. When I go to recovery, all I get is the red triangle.

starrider1300 said:
I tried flashing with fastboot with the same results. When I go to recovery, all I get is the red triangle.
Click to expand...
Click to collapse
At the red triangle screen press power button and volume up at the same time and then let them both go. That should get you into recovery.
Or you can flash a custom recovery and use that.
Hopefully the factory reset will fix your problem.

meekrawb said:
At the red triangle screen press power button and volume up at the same time and then let them both go. That should get you into recovery.
Or you can flash a custom recovery and use that.
Hopefully the factory reset will fix your problem.
Click to expand...
Click to collapse
Thanks for the help. I got into recovery and did a factory reset. Tablet booted and I went through the tablet setup. Same results, no playstore, camera, or gallery. Can't download from the internet, shows no SD card.

I would try downloading the factory images directly from Google and flashing the whole thing. Once that flashes, you can run Chainfire Auto Root (CFAR) to get root back, if desired. Or you can flash TWRP and then flash SuperSU from within TWRP.
It sounds like your partitions may have gotten FUBARed.

I would highly recommend just staying with the "full" releases of ANY OS on any smart phone, as any x.x.1/x.x.2 etc can have more bugs than what is trying to be fixed in the original (not all cases, but some)
Using NRT I would suggest dropping back to 5.0 and COMPLETELY setting it back to stock (re lock boot loader, stock recovery, no root), then doing it OTA (if thats how you prefer to update) THEN re-root, re-unlock etc
Or just stay on 5.0 until something like 5.1 comes about

fury683 said:
I would try downloading the factory images directly from Google and flashing the whole thing. Once that flashes, you can run Chainfire Auto Root (CFAR) to get root back, if desired. Or you can flash TWRP and then flash SuperSU from within TWRP.
It sounds like your partitions may have gotten FUBARed.
Click to expand...
Click to collapse
Tried all the above with the same results. Any solutions for partitions that have gotten FUBARed?

starrider1300 said:
Tried all the above with the same results. Any solutions for partitions that have gotten FUBARed?
Click to expand...
Click to collapse
Seems like the actual flash storage could have issues... is it still under warranty? May need to send it in..

i have exactly the same problem and still no solution (since september)
I tried to wipe everything, twrp, cwm, factory , CM, omnirom ... something is broken in the storage folder and nothing can repair it. wiping maybe erase the data but doesnt seems to rebuild the tree

starrider1300 said:
I have a Nexus 7 (2013) that I installed an Android 5.0 lollipop ROM on. I also had TWRP recovery installed. It was working fine. I took the OTA update for 5.0.1. It would not install with the recovery installed. Long story short, I believe I wiped something I shouldn't have. I can install the factory images using WUGS toolkit. The tablet boots and I can do the set-up. Wi-fi works, bluetooth works. I can't download files from the internet, I get a No SD card message. The play store, camera, gallery do not work. Trying to use the gallery I get a No Storage, no external storage available message. I'm not sure where to go from here. Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
check if you can pull/push some files in bootloader mode .
use android platform tools :
Code:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> <local> - copy file/dir from device

neo13oy said:
check if you can pull/push some files in bootloader mode .
use android platform tools :
Code:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> <local> - copy file/dir from device
Click to expand...
Click to collapse
My son has the same model nexus 7 tablet. Are there any files that I can pull from his and then transfer to mine to restore my partitions?

starrider1300 said:
My son has the same model nexus 7 tablet. Are there any files that I can pull from his and then transfer to mine to restore my partitions?
Click to expand...
Click to collapse
No , I just suggest it to check if your internal SD card is damaged.
as you say , you can flash your partition with Nexus factory images but your data will be lost !!!

[Solved] Problems Switching Partitions (X9076)

Hello everyone,
I recently did upgrade my phones OS from 1.2.x to 2.1.5i (ColorOS) via flash, not OTA.
Afterwards I rooted it using TWRP & SuperSu.
I did return to Stock Recovery (community. oppo. com/en/forum.php?mod=viewthread&tid=17397&extra= (Sorry, I can't post links yet, you have to remove the spaces between community oppo and com)).
My problem now is, that I want to use the "Switch Partition" option, to unify my phone storage, but everytime I try the phone does only boot into recovery, as I had a custom recovery.
Do I need a newer Stock Recovery Version? And where/how can I update it?
Or is it possible to unify the storage manually and continue using ColorOS?
Thanks in advance for any help,
Carroll

Probably you need a newer version. Try this.

Sorry for the late reply.
I did already try this - it didn't help.
I will flash the 4_4 recovery manually now.
Thank you
It seems to work.
Strange, I had to update the recovery via fastboot, when I tried to use the System Update tool it didn't work - although the phone told me so.
It worked.
Another strange thing: The gApps didn't get installed (only Settings & Photos). So now I'm sitting on a phone without any browser

maj0r_tom said:
Sorry for the late reply.
I did already try this - it didn't help.
I will flash the 4_4 recovery manually now.
Thank you
It seems to work.
Strange, I had to update the recovery via fastboot, when I tried to use the System Update tool it didn't work - although the phone told me so.
It worked.
Another strange thing: The gApps didn't get installed (only Settings & Photos). So now I'm sitting on a phone without any browser
Click to expand...
Click to collapse
Did you install ColorOS 2.1.5i and you don't have gapps? It's strange ...
Perhaps you could flash TWRP again and try to flash open gapps pico, but I'm not sure this works

javier.pc said:
Did you install ColorOS 2.1.5i and you don't have gapps? It's strange ...
Perhaps you could flash TWRP again and try to flash pico, but I'm not sure this works
Click to expand...
Click to collapse
I did just download and install the PlayStore APK, which worked fine.

maj0r_tom said:
Sorry for the late reply.
I did already try this - it didn't help.
I will flash the 4_4 recovery manually now.
Thank you
It seems to work.
Strange, I had to update the recovery via fastboot, when I tried to use the System Update tool it didn't work - although the phone told me so.
It worked.
Another strange thing: The gApps didn't get installed (only Settings & Photos). So now I'm sitting on a phone without any browser
Click to expand...
Click to collapse
I'm having the same problem as you do. Could you walk me through the steps you took to solve this problem?

Hello, can you please share the stockrecovery.img for fastboot?

nizohio said:
I'm having the same problem as you do. Could you walk me through the steps you took to solve this problem?
Click to expand...
Click to collapse
I think it is not necessary to download playstore.apk.
create a folder on your PC (Linux and Mac is your top choice), copy all your downloads in this folder (downloads = custom- rom zip, open_gapps zip, SuperSu zip etc)
next you need ADB (android debugging bridge) on your PC.
connect your smartphone with usb to your PC (usb debugging enabled on your phone- you find it under developer)
boot in recovery ( I assume you got lastest TWRP for your phone installed.)
in TWRP go to WIPE / ADVANCED WIPE --> tick Cache, Internal Storage, Data, System, Dalvik/Art Cache.
With this action you are going to lose all data, except data on your external SD and your OS as well. Common sense dictates to back up your data first :good:
after you swiped go to ADVANCED /ADB Sideload --> Swipe to Start Sideload
open your terminal on your pc and cd in your newly created folder with all your zip goodies.
type
Code:
adb sideload custom-zip
Use tab completion - very handy and you know there are no typos.
repeat this command with open-gapps.zip (beware you have to activate sideload in TWRP again) Caution: Do not reboot between installation of your custom - rom and open_gapps.
same procedure with Supersu.zip and so on.
After successful sideload installation, boot your phone to system. Now you should see welcome screen from Android and you have to do a few more setup steps to enjoy your new OS.

Oneplus 3 do not boot after installing OxygenOS 4.0.2

Hello everyone!
My oneplus3 is actually running no OS and I'm having a boot loop.
I will try to explain what happened to me with the most details I can.
Before I ****ed everything up, I think I was running OxygenOS 3.28, not really sure about it but im 100% sure it was below 4.0, and it was rooted with TWRP 3.0.2 installed.
1) Today I had a pop up saying OxygenOS 4.0.2 was available (the official one that pops on the screen on boot) "Yay so coooool Nougat!"
1.1) I downloaded it, 1.4Go, then I pressed install
1.2) TWRP showed up, I didn't know what to do and that's where I ****ed up, I set my phone "factory new" in TWRP.
1.3) Phone restarted fresh new, I thought I had 4.0.2 but naaaaah would've been too easy so the official pop up showed again, I was still 3.28 I think.
1.4) Downloaded it once more, TWRP opened again, this time i was looking for the update i just downloaded in the "install" section. I browsed for quite a while and couldn't find it.
1.5) Master ****-up here: I tried to restore a backup. Then the bootloop happened. The black screen with "Oneplus" written in white. I was able to go back in TWRP by pressing power + volume down
1.6) Tried every kind of restore unsuccessfully, and tried ADB but it wouldn't load. Also TWRP said that I was running no OS when I wanted to turn off my phone for example.
2) I downloaded 4.0.2 from one plus website on my mac, and i flashed the official recovery instead of TWRP.
2.1) Transferred the update from my mac to my PC (seems important to me) and installed ADB & everything on both PC/O+3.
2.2) so adb worked in forceboot, i've been able to flash official recovery, tried once more to wipe & everything, but clearly I have no OS now, as TWRP said.
2.3) so i had the update in a folder (not a zip, probably due to the download being done from a mac), I made it a .ZIP with winrar, but "adb sideload update.zip" crashed at 0% everytime
2.4) looked at the archive then i noticed it was first a folder "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883" then inside it i had the content like "boot.img" & everything. So i zipped it again but without that first folder because I thought it was the problem, but it kept on crashing 0%.
2.5) restarted my PC, looked on several forums, but i couldn't find any fix. Now adb can't even open update.zip anymore, it fails even before 0%.. I tried naming it .zip.zip, keeping the name "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip", using a third party app to allow more RAM to the cmd app...
I've been trying hard for 4 hours but I still have a O+3 without any OS... My last idea is downloading "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip" from my PC so it downloads it directly .zip unlike on my mac...
I hope I said everything, sorry for the long post but i'm desperate.. thanks for your attention,
Valentin

Try this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
Let me know if it works.
EDIT: See FAQ #1, 2, 4, 12, 14 and 17.

dbabaev21 said:
Try this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
Let me know if it works.
EDIT: See FAQ #1, 2, 4, 12, 14 and 17.
Click to expand...
Click to collapse
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.

Try to install the new official TWRP version i think it is 3.0.3-0 through fastboot. Boot up TWRP, wipe every partiton and copy the update.zip onto the phone. You can copy it by connecting it normaly via USB(like you would do in OOS) and install the zip file afterwards.

Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
install stock recovery and then try installing official OS. Or install modded twrp 3.0.2-1.28 and then try installing Freedom OS 2.3 via sideload or through internal storage.

Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
Stop fiddling with the ROM. Download the ROM afresh directly to your Windows PC/laptop. Check the md5. Then start experimenting with the other suggestions but don't again meddle with the ROM!

Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
I read your post again and here are a few things:
* Don't update Stock OOS via "System updates" in Settings if you are rooted and have TWRP
* Back up your data before updating, wiping or doing something with your phone.
* For the ADB error, see the FAQ #17 in the guide I provided.
Now, try this:
Flash TWRP via fastboot > boot to TWRP > connect your phone to your PC and copy the full Stock OOS v4.0.2 OTA to your phone > reboot to fastboot and flash Stock Recovery.
It didn't touch the internal storage. So, try to install from internal storage when you are in Stock Recovery.
Let me know if it worked.

Can't install anything in TWRP

i cannot install anything in TWRP atm
it says "could not find ´META-INF/com/google/android/update-binary´in zip file.
Any bright ideas ?

Citroon said:
i cannot install anything in TWRP atm
it says "could not find ´META-INF/com/google/android/update-binary´in zip file.
Any bright ideas ?
Click to expand...
Click to collapse
It looks so simply but did you take a look to your rom zip? open with a zip explorer like winzip in /META-INF/com/google/android and here you must find this file

SubwayChamp said:
It looks so simply but did you take a look to your rom zip? open with a zip explorer like winzip in /META-INF/com/google/android and here you must find this file
Click to expand...
Click to collapse
it's not only with the roms, it's with everything
i've tried to flash new firmware, gapps and nothing works :/

well, what version of twrp do you use? try first with oficcial 3.0.2.0, bootloader unlocked? check usb debbugging and allow oem unlock in developer options, sometimes neccessary mount system or enable MTP in recovery

SubwayChamp said:
well, what version of twrp do you use? try first with oficcial 3.0.2.0, bootloader unlocked? check usb debbugging and allow oem unlock in developer options, sometimes neccessary mount system or enable MTP in recovery
Click to expand...
Click to collapse
im using the official 3.0.2.0, i currenly have no RoM installed so i can't boot into anything

Citroon said:
im using the official 3.0.2.0, i currenly have no RoM installed so i can't boot into anything
Click to expand...
Click to collapse
try first formatting data, wipe everything except where placed your rom zip (int or extSD), mount system and flash again

SubwayChamp said:
try first formatting data, wipe everything except where placed your rom zip (int or extSD), mount system and flash again
Click to expand...
Click to collapse
Tried that, still having the error:crying:

Citroon said:
i cannot install anything in TWRP atm
it says "could not find ´META-INF/com/google/android/update-binary´in zip file.
Any bright ideas ?
Click to expand...
Click to collapse
ok, go to format the data and then write YES, but u will lose your data, so, backup your files, and then restore them. should be working !!

StonebridgeGr said:
ok, go to format the data and then write YES, but u will lose your data, so, backup your files, and then restore them. should be working !!
Click to expand...
Click to collapse
Doesn't work either, this is really weird to me, i've been flashing for a few years now, and never encountered this issue before.
-also note that i'm not amazing at this

Citroon said:
Doesn't work either, this is really weird to me, i've been flashing for a few years now, and never encountered this issue before.
-also note that i'm not amazing at this
Click to expand...
Click to collapse
ok. which image did u flash? which guide did u followed to flash twrp ? ( because a newiest image of TWRP RECOVERY for mi max is up )

StonebridgeGr said:
ok. which image did u flash? which guide did u followed to flash twrp ? ( because a newiest image of TWRP RECOVERY for mi max is up )
Click to expand...
Click to collapse
i've tried about every RoM available.
I also want to note that i have flashed with this version of TWRP before (3.0.2.0)

StonebridgeGr said:
ok. which image did u flash? which guide did u followed to flash twrp ? ( because a newiest image of TWRP RECOVERY for mi max is up )
Click to expand...
Click to collapse
tried about every rom available, and other things just to see what would work and what wouldn't (nothing can flash)
im currently running 3.0.2.0 and have flashed with this version of TWRP before, but suddenly it stopped working

Citroon said:
Tried that, still having the error:crying:
Click to expand...
Click to collapse
Probably a bad flashing and you are needing repari partitions, for that I recommend start from beginning again:
- flash miui rom for fastboot (unpack zip rom in your adb folder for better performance, connect device to pc into mode fastboot, be sure device be recogniced typing; fastboot devices then right click mouse and execute like admin over "flash all".
- then to install rom you can flash again twrp via fastboot typing any place adb folder and placing file recovery.img this folder; fastboot flash recovery recovery.img
- then go to recovery with hardware keys and flash supersu v.2.79

SubwayChamp said:
Probably a bad flashing and you are needing repari partitions, for that I recommend start from beginning again:
- flash miui rom for fastboot (unpack zip rom in your adb folder for better performance, connect device to pc into mode fastboot, be sure device be recogniced typing; fastboot devices then right click mouse and execute like admin over "flash all".
- then to install rom you can flash again twrp via fastboot typing any place adb folder and placing file recovery.img this folder; fastboot flash recovery recovery.img
- then go to recovery with hardware keys and flash supersu v.2.79
Click to expand...
Click to collapse
oh boy, i guess im screwed for now then.
i only have access to a macbook for the next few days, tried installing fastboot on it but that's a complete nightmare

Citroon said:
oh boy, i guess im screwed for now then.
i only have access to a macbook for the next few days, tried installing fastboot on it but that's a complete nightmare
Click to expand...
Click to collapse
two things; I assume that trying to flash from extSD, if yes with file explorer of recovery copy to internal memory, maybe an issue to reading extSD, also you can to install a newer version of recovery 3.0.3.2 works sometimes for me and last here you have a reading page about install fastboot on mac (nightmare) http://www.stechguide.com/setup-adb-and-fastboot-on-mac-easy-step-by-step-guide/

SubwayChamp said:
two things; I assume that trying to flash from extSD, if yes with file explorer of recovery copy to internal memory, maybe an issue to reading extSD, also you can to install a newer version of recovery 3.0.3.2 works sometimes for me and last here you have a reading page about install fastboot on mac (nightmare) http://www.stechguide.com/setup-adb-and-fastboot-on-mac-easy-step-by-step-guide/
Click to expand...
Click to collapse
I finally got it working
I was so stubborn that I decided to install Windows Bootcamp on my mac
it was as simple as reinstalling TWRP and do a clean wipe, now i can install roms and all the other things as i please again.
-Thank you for your help!

Note 8 pro bricked

Today i installed LR recovery and rooted my phone then i installed Viper 4 android... everything went well.. at last i uninstalled xiamo sim activation apk because it bothered me every time i reboot my phone... but after uninstalling that my phone is no longer booting up.. it boots to fastboot mode only.. I can manually boot to twrp but my files are also corrupted...
anyway to recover my data? MIUI 11 indonesian rom

You can always try to reinstall the app through adb in recovery mode, maybe then it'll boot. Kind of surprised you can't access your files through recovery mode, thought data decryption worked. There's also the possibility that dirty flashing the entire image on top of your current one will restore the missing apps and allow it to boot. Might want to save that as a last resort.

wang1chung said:
You can always try to reinstall the app through adb in recovery mode, maybe then it'll boot. Kind of surprised you can't access your files through recovery mode, thought data decryption worked. There's also the possibility that dirty flashing the entire image on top of your current one will restore the missing apps and allow it to boot. Might want to save that as a last resort.
Click to expand...
Click to collapse
Unfortunately could not try that i already flashed entire rom to get my phone alived and lost all my data.. but i am still curious why it happened..
Xiaomi security is so high, i regret buying xiaomi instead of samsung..
Btw i also could not find boot from recovery.p file in system folder in LR twrp to replace recovery as instructed there.. do you have any information on that?
Thanks

n70shan said:
Unfortunately could not try that i already flashed entire rom to get my phone alived and lost all my data.. but i am still curious why it happened..
Xiaomi security is so high, i regret buying xiaomi instead of samsung..
Btw i also could not find boot from recovery.p file in system folder in LR twrp to replace recovery as instructed there.. do you have any information on that?
Thanks
Click to expand...
Click to collapse
It's just that there are apk that you should not remove. Look for XiaomiADBFastbootTools, it's a tool designed to disable/enable/uninstall/reinstall Xiaomi bloatware, it doesn't require TWRP or root, just adb, and all the apps there are safe to remove.

antony.ps said:
It's just that there are apk that you should not remove. Look for XiaomiADBFastbootTools, it's a tool designed to disable/enable/uninstall/reinstall Xiaomi bloatware, it doesn't require TWRP or root, just adb, and all the apps there are safe to remove.
Click to expand...
Click to collapse
Thanks for suggestion.. i downloaded Adb flash tools but i cant run it.. it gives error A JNI error has occured... i have latest java already installed in my windows 8.1.. what to do?
Edit: i tried version 6.7 and it opens now, will see what it does

n70shan said:
Thanks for suggestion.. i downloaded Adb flash tools but i cant run it.. it gives error A JNI error has occured... i have latest java already installed in my windows 8.1.. what to do?
Edit: i tried version 6.4 , and the problem is it opens and closes immediately.. what should i do now?
Click to expand...
Click to collapse
I'm using Linux right now, and it only runs on Java 11, maybe it's java version problem? Try to use Oracle Java 11 if Redhat or other OpenJDK distribution doesn't work.

n70shan said:
.......
Btw i also could not find boot from recovery.p file in system folder in LR twrp to replace recovery as instructed there.. do you have any information on that?
Thanks
Click to expand...
Click to collapse
You have to mount the system partition first, go to the mount tab and select system, then try the file manager and look for recovery.p, should be there.

wang1chung said:
You have to mount the system partition first, go to the mount tab and select system, then try the file manager and look for recovery.p, should be there.
Click to expand...
Click to collapse
Oh my bad i forget that.. been out of Android from months..
Anyways issues are resolved now with data lost ?
Thanks
Moderators can close the thread