Hi, all.
I accidently wiped the system partition of my Nexus 6P in TWRP. I have a Pure Nexus ROM and gapps on my computer, that I've been trying to flash via adb sideload. The sideloading goes successfully, and it seems like the ROM is flashed. But when I go to reboot, I get a warning from TWRP: "No OS Installed". How is there no OS installed when I've flashed a ROM? Isn't that the OS?
What steps should I take to unbrick my phone? Thanks in advance.
It sounds like you're only putting the image on your phone, only the first half of the resolution?
Either use USB to move the file over to the internal storage, or ADB push the file, and then use TWRP to flash the ROM as normal.
Related
i sideloaded ubuntu onto my nexus 4.
i did ...
full wipe
adb sideload
sideloaded both zips, mako first then phablet.
now when i go to reboot it says "no os found" but theres a "sideload.zip" in my storage, do i just flash the sideload.zip or what do i do?
EDIT: just flashed the sideload.zip
thank you.
Hello XDA Developers,
I had a device that was rooted on stock rom and recovery. What happened was that an OTA was installed and it went to the "boot verify certification" screen. I had to install Ubuntu to get TWRP running again.
I'm able to boot into TWRP, and I tried installing different ROMs, using adb sideload, from Stock ROM, ParanoidAndroid, and Madri-ROM.
The first one was able to install, but when I reboot the phone, I get stuck on the LG logo. I wait for an hour and it still does not do anything.
So now I try the other two custom ROMs, and I get an error saying "E:Error executing updater binary in zip "... .zip".
Then it reads "Error flashing zip '... zip'.
My question is: What else can I do to get this phone working again? I would like stock ROM, and preferably stock recovery back (Recovery is secondary).
Thanks in advance,
DaAznMan
Note: When I use adb sideload, the .zip file that gets transferred becomes a file called 'sideload.zip'. Is that correct? If not, what do I need to do to fix it?
Hello, I have a 2012 WiFi Nexus 7. I recently read a post that has the link to the latest android lollipop 5.0 system image tgz file available which they extracted from the servers of Google, before they updated the website.
Excited, i downloaded the image, and tried to flash it via wugfresh's nexus root toolkit. (i was rooted). I extracted the tgz file and flashed the different partitions one by one via the toolkit. When i tried booting it, it stayed on the google logo. So went back to bootloader and tried to boot into recovery, but it said on the top left corner in small fonts that "could not boot"or something similar to that. worried, i flashed twrp via adb from the toolkit manually and rebooted normally into recovery. The log said it couldnt mount /system and /data. so i formatted the system and cache partition via adb and formatted /data from twrp. i somehow managed to push a slimkat ROM zip in the internal storage and install it. No gapps, no root nothing. its just like that, functioning normally. i have the original 4.4.4 tgz file. should i flash it via android sdk adb?
Can i be sure it wont give me such problems? and why did such a thing happen? please help me out
niranjan_23 said:
Hello, I have a 2012 WiFi Nexus 7. I recently read a post that has the link to the latest android lollipop 5.0 system image tgz file available which they extracted from the servers of Google, before they updated the website.
Excited, i downloaded the image, and tried to flash it via wugfresh's nexus root toolkit. (i was rooted). I extracted the tgz file and flashed the different partitions one by one via the toolkit. When i tried booting it, it stayed on the google logo. So went back to bootloader and tried to boot into recovery, but it said on the top left corner in small fonts that "could not boot"or something similar to that. worried, i flashed twrp via adb from the toolkit manually and rebooted normally into recovery. The log said it couldnt mount /system and /data. so i formatted the system and cache partition via adb and formatted /data from twrp. i somehow managed to push a slimkat ROM zip in the internal storage and install it. No gapps, no root nothing. its just like that, functioning normally. i have the original 4.4.4 tgz file. should i flash it via android sdk adb?
Can i be sure it wont give me such problems? and why did such a thing happen? please help me out
Click to expand...
Click to collapse
Don't use toolkits
Better flash the factory image from 4.4.4 and try again
GtrCraft said:
Don't use toolkits
Better flash the factory image from 4.4.4 and try again
Click to expand...
Click to collapse
So you mean i flash using the adb provided by google?
btw, i uninstalled the nexus toolkit but let the drivers be in the system. do i have to remove those too? if yes then how?
and r u sure my filesystem wont get corrupt again with stock adb? coz i never used the toolkit for my nexus 4 for as many times ive flashed; ive used stock adb.
why did this happen although?
Hey guys,
Maybe the problem was already encountered by some of you, ok here it goes.
I'm trying to flash a F2FS Slimkat rom on my laggy Nexus 7 grouper. I unlocked the bootloader, flashed TWRP 2.8.2 and rooted the tablet, everything went fine.
After that it got a little tricky, I wiped the system and changed the format partition of cache, system and data to F2FS separately but when I try to mount my Nexus to put the zipped rom and the gapps afterwards, it appears on my Desktop but the files can't be transferred on it.
So my question is, how to transfer the zip files onto the Nexus after rooting it and turning all the partitions into F2FS because afterwards I'm not able to copy anything on it.
Thanks in advance
Saltari
I always use adb push without problems (on F2FS in TWRP, too)
Thanks, using adb push worked. I was able to flash both the rom and the gapps but now I'm stuck on a bootloop with the google logo and the black screen. What did I do wrong ?
Saltari said:
Thanks, using adb push worked. I was able to flash both the rom and the gapps but now I'm stuck on a bootloop with the google logo and the black screen. What did I do wrong ?
Click to expand...
Click to collapse
I don't know, but here are some things you could try:
full wipe & flash only the rom without gapps
repair the file systems (same menu as reformat) and reflash
try other/smaller gapps (maybe the beta gapps from slimroms? they work for 4.4 although they're labeled 5.0)
try another rom
Hello there.. I normally don't have a problem figuring out what to do but I'm totally stuck here. I have a Sprint Galaxy S4 SPHL720T. I was rooted and running a custom ROM. I was having issues with the wifi so I decided to flash back to GPE 5.0.1 here from the xda forums. I am running twrp v2.8.4.0. I made a backup and wiped system/data/cache and dalvik. I went to install JFLTE-GPE-20150303 (LRX22C) from ultimarom.com via here at XDA. It said zip is corrupt. So i redownloaded on my PC and transferred it to my sd card. Still said corrupt. So I downloaded a different ROM on my PC and moved to SD. Still said corrupt. I tried to flash a GAPPS package and it worked but no ROMS I tried would. I tried to install my latest backup through recovery. It said MD5 doesn't match. If I hit reboot in twrp it prompts to install superuser because the phone doesn't appear to be rooted. If I hit that it runs the script for about 2 seconds then reboots. It won't boot into the OS as there is no OS and if I reboot into recovery it still gives me the "install su" prompt at the reboot screen. So then I hooked up into ODIN and download mode and flashed "CF-Auto-Root-jflterefreshspr-jflterefreshspr-sphl720t.tar.md5" and "openrecovery-twrp-2.8.4.0-jfltespr.tar". Still having the same issues. I have no idea what to do at this point. Any help would be GREATLY appreciated as I need my phone for work and play .
Thanks,
Aaron