Develop Bugs

[Q] Wiped data and cache, and now I can't install the ROM

Hi there,
I have TWRP Recovery v2.3.3.0, and I want to install the new Shiny rom so I can taste that sweet, sweet Kit Kat. However, after I booted into recovery and wiped my cache and data (I wiped internal storage, cache, dalvik cache, and did factory reset), I found that I didn't have the rom on my phone storage anymore (duh). I connected the phone to my laptop (Windows 7) via usb, but for some reason it's not being recognized (it's not showing up in my computer or anything). I went into device manager and deleted the drivers so that I could install them anew, but I'm not entirely sure what to install/what to do afterwards.
Usually I'm good at figuring out what to do on my own with this sort of thing, but after scouring pages on pages for hours, I'm stumped now, and kinda frustrated. Can anyone give a brief step-by-step on what to do? I just don't wanna screw up something little and have it not work.
Thanks so much for reading! (I work in tech support at school, so I know how laborious this is. )

ijrabbani said:
Hi there,
I have TWRP Recovery v2.3.3.0, and I want to install the new Shiny rom so I can taste that sweet, sweet Kit Kat. However, after I booted into recovery and wiped my cache and data (I wiped internal storage, cache, dalvik cache, and did factory reset), I found that I didn't have the rom on my phone storage anymore (duh). I connected the phone to my laptop (Windows 7) via usb, but for some reason it's not being recognized (it's not showing up in my computer or anything). I went into device manager and deleted the drivers so that I could install them anew, but I'm not entirely sure what to install/what to do afterwards.
Usually I'm good at figuring out what to do on my own with this sort of thing, but after scouring pages on pages for hours, I'm stumped now, and kinda frustrated. Can anyone give a brief step-by-step on what to do? I just don't wanna screw up something little and have it not work.
Thanks so much for reading! (I work in tech support at school, so I know how laborious this is. )
Click to expand...
Click to collapse
First of all install proper drivers using this GNex Toolkit. (Use it only to install drivers)
The boot to bootloader and flash the newest TWRP recovery by executing this command in the same folder where the file resides. Download it from here.
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.1-maguro.img
Then boot to recovery and open command window in the same folder where your ROM's zip resides and execute following command.
Code:
adb push ROM.zip /sdcard/ROM.zip
Now reboot to recovery again and you will see the ROM zip in /sdcard. Flash it!!

I'm confused. should I be running this code on my phone, or computer? from my phone, I'm booting into recovery, pressing Advanced -> Terminal Command. then I navigate to the folder where I put the file (openrecovery...img), and executing the command, only to get "fastboot: not found"
Also, after installing the Gnex toolkit, I still can't put files in my phone's storage from my computer, unless I boot into the actual system and not the recovery. Is that alright?

Don't know if sideload is supported by TWRP. If it is supported, select 'install zip from sideload' and then run the following command:-
Code:
adb sideload ROM.zip

wow, I totally forgot I had the Nexus Root Toolkit, which does all this for you....I just had it flash my stuff, so I'm all good :good:

HELP asap please, i've got nothing

Today i decided to download a new rom, something i ain't done in a long time, so everything went well, got the rom and kernal installed on my external.
I then went and wiped everything on the phone but went a bit to far and decided to go into advanced and wipe dalvik cache, cache, system, data, internal storage and external SDcard. so after this was done, i went into the SD card to install the new rom, but nothing is there, the entire folder is clear.
so now when i try to turn my phone off, i get a message come up saying 'no OS installed! are you sure you wish to reboot.
When i connect my phone to my computer so that i can transfer over the files again, my phone aint coming up anymore.
what can i do?
i prey someone knows a way around this.

MrLarner said:
Today i decided to download a new rom, something i ain't done in a long time, so everything went well, got the rom and kernal installed on my external.
I then went and wiped everything on the phone but went a bit to far and decided to go into advanced and wipe dalvik cache, cache, system, data, internal storage and external SDcard. so after this was done, i went into the SD card to install the new rom, but nothing is there, the entire folder is clear.
so now when i try to turn my phone off, i get a message come up saying 'no OS installed! are you sure you wish to reboot.
When i connect my phone to my computer so that i can transfer over the files again, my phone aint coming up anymore.
what can i do?
i prey someone knows a way around this.
Click to expand...
Click to collapse
Well, those actions did not delete the recovery you flashed so you should be able to enter it. If yes you can:
A) take the sdcard out and copy the data to it on your PC (home/work/friend/cafe?)
B) connect the phone to PC using USB cable:
- on PC start Command Prompt (cmd.exe)
- navigate to the directory where you have the new ROM stored
- enter "adb sideload ROM_filename"
- while at the same time in your recovery enter flashing menu and select Sideload
- you will be able to flash rom
C) enter "Download Mode" (power+home+vol_down) also called Odin Download Mode and use PC Odin to flash some recovery - search for Philz custom recovery, he has versions named something.md5 that are usable to Odin.

mat9v said:
Well, those actions did not delete the recovery you flashed so you should be able to enter it. If yes you can:
A) take the sdcard out and copy the data to it on your PC (home/work/friend/cafe?)
B) connect the phone to PC using USB cable:
- on PC start Command Prompt (cmd.exe)
- navigate to the directory where you have the new ROM stored
- enter "adb sideload ROM_filename"
- while at the same time in your recovery enter flashing menu and select Sideload
- you will be able to flash rom
C) enter "Download Mode" (power+home+vol_down) also called Odin Download Mode and use PC Odin to flash some recovery - search for Philz custom recovery, he has versions named something.md5 that are usable to Odin.
Click to expand...
Click to collapse
My SD Card is a tiny little card, and there is nowhere on my computer to put it. how am i ment to copy the stuff across?

Need to give a HUGE thank you to mat9v on here who spent around 2 hours helping me solve all my problems on my phone.
can't thank him enough. :good::good::good:

[Q] Sony Z1 Compact - CWM-based Recovery v6.0.5.1 - BLACK SCREEN

I really need help. I'm a noob at this. I was trying to install CyanogenMod on my Z1 compact. I was following this guide; "wiki.cyanogenmod.org/w/Install_CM_for_amami" It went well after some trying. Got all the way to step 9! When I pressed Reboot system now nothing happened. The Sony logo game for some seconds, then the screen went black. I know the phone is on 'cause I can see that it is light-black, if you know what i mean. I thaught maby it would take i while. But it stayed like this for 5 hours. Nothing happens.. When I turn it off and on again, I can press the voume rockers and it takes me to the CWM-based Recovery v 6.0.5.1 page where i can do some stuff, but I'm stuck here. Please help me! Dont know what to do. Is there a way to factory-reset the phone back to Anroid? Sorry for being so noob. Need a noob friendly guide on how to fix this

Use the guides and files from this forum instead. Did you flash the CM kernel in fastboot?

at least you can boot into cwm. did you place cyanogenmod zip on your sd card?

XperienceD said:
Use the guides and files from this forum instead. Did you flash the CM kernel in fastboot?
Click to expand...
Click to collapse
"Open a terminal on the PC and enter the following:
fastboot flash boot boot.img
fastboot reboot"
- again sorry, these last 14 hours is the only experience i have with rooting etc. flash means install right?

rzlatic said:
at least you can boot into cwm. did you place cyanogenmod zip on your sd card?
Click to expand...
Click to collapse
i used this "adb push cm.zip /sdcard/0/" - and I checked now. The files is there still yes. Btw, in panic I've "wipe data/facotry reset". Dont know if this matters

"fastboot flash boot boot.img" flashes only the cwm (and kernel). wipe data/factory reset is ok, no harm done (at least now, as you want clean partitions at this point anyway).
so if your zips are on the sdcard via step 8, boot into cwm, navigate to
- install zip (swipe down, swipe right to enter)
- choose zip from /sdcard
- 0/
now you end up on your sdcard. find your zip and run the install. if you copied gapps zip too, install that zip after flashing the rom, and that's it.

llgr said:
"Open a terminal on the PC and enter the following:
fastboot flash boot boot.img
fastboot reboot"
- again sorry, these last 14 hours is the only experience i have with rooting etc. flash means install right?
Click to expand...
Click to collapse
Yes install, I prefer to flash the kernel in fastboot then flash the zip.

rzlatic said:
"fastboot flash boot boot.img" flashes only the cwm (and kernel). wipe data/factory reset is ok, no harm done (at least now, as you want clean partitions at this point anyway).
so if your zips are on the sdcard via step 8, boot into cwm, navigate to
- install zip (swipe down, swipe right to enter)
- choose zip from /sdcard
- 0/
now you end up on your sdcard. find your zip and run the install. if you copied gapps zip too, install that zip after flashing the rom, and that's it.
Click to expand...
Click to collapse
Yes I've come this far. Now I have installed the file i had at the sdcard. "installation complete!" "Good Apps for Android 4.3.3" it says.
Now ive found the cm-11-20140922-NIGHTLY-amami.zip and installed it via sideload.
"opening adbd...
finding update package..
opening updage package.
installing update..."
Dont know how long this take, doesnt say its finished, but i can navigate through the menu at the top, does this means it finished? what to i do now to get i work? just "reboot system now"?

llgr said:
Dont know how long this take, doesnt say its finished, but i can navigate through the menu at the top, does this means it finished? what to i do now to get i work? just "reboot system now"?
Click to expand...
Click to collapse
yes. reboot. see what happens. you should boot into cm already.
you didn't need using so much adb, it's all doable via cwm (except initial flashing of boot.img which is cwm itself).
next time: just download the zip, reboot into recovery, flash the zips there and reboot. it's that simple you don't need to wipe anything between flashing nightlies, but you do between nightlies and M build - or if you migrate to some other aosp/aokp/kang rom. anyhow, have fun.

You want to instal cm right? But do you know that you need to unlocked your bootloader to install any other rom than stok right? So if tou want to have CM you must unlock your bootloader

Please help me

I PHONE to Aafath me only TWRP
I want to uninstall TWRp from my phone and Restore settings
PLEASE HELP ME

http://forum.xda-developers.com/showthread.php?t=2636231
I used this a couple of times hasn't failed me yet

SORRY
I cant connect my mobile to computer
show my twrp only and no thing

TRANSMITAR said:
I cant connect my mobile to computer
show my twrp only and no thing
Click to expand...
Click to collapse
On Your phone, when it's in TWRP recovery, you need to select (click on) "reboot" and than click on "system". Than it should restart into system (UI).
There is one tool on this forum for windows which helps you to install TWRP or normal recovery. And after that you can put ROM on SD Card and recover system. (in that case, you should choose "reboot into ADB). I did not try this but i think it should work.
Have you maybe wipe all memory (internal, etc.)? Because you should not wipe anything if you're not shure what this wiping means!
EDIT;
With this tool you can edit recovery;
http://forum.xda-developers.com/showthread.php?p=52973530#post52973530

TWRP Can't Mount /System - OP3 Bricks When Trying to Flash New ROM??

I'm currently running my OP3 on Resurrection Remix 5.7.4 (MM 6.01), the phone has the latest version of TWRP and I've flashed other ROMs in the past without any issue
RR has proven to be quite unstable for me, the system UI keeps crashing, which renders the phone unusable until after a reboot so I wanted to flash Freedom OS as that worked quite well for me previously. When I tried to flash the ROM in TWRP the ROM seemed to flash successfully but when I rebooted, only the boot logo showed and then the screen went black and the phone refused to respond at all for about two hours, after that exactly the same thing happened. I managed to boot into recovery and tried flashing a different ROM but the result was the same every time, the only way to get the phone to work normally was to flash RR again/restore from a Nandroid backup, either way, the result is the same, I'm stuck on an unstable ROM and I don't know why, the last time I flashed these ROMs they worked fine, I followed all of the instructions for flashing said ROMs to the letter, I have the latest version of TWRP, etc.
Also it seems TWRP can't mount /system, in TWRP under "mount", system is unchecked, I checked it and tried again but found that whenever I rebooted the phone or attempted to flash a new ROM, it would always uncheck itself and flashing the ROM would fail, however strangely flashing the same version of RR was always successful. Is this why the flashing keeps failing and does anyone know what the problem could be?
Thanks!

bronderb said:
Go into your bootloader and format system, cache, and userdata (This will wipe EVERYTHING so be sure to backup). Then latest official flash stock rom and reboot. This should fix it. If this helped hit thanks!
Click to expand...
Click to collapse
Bootloader? There is no option in the bootloader to delete everything as far as I can see, do you mean in recovery? And if I wipe everything off the phone, how do I get the stock ROM onto the phone to flash it? When you say wipe userdata do you mean wipe internal storage or am I misunderstanding and you're telling me to wipe the usual dalvik, cache and data as you would for a normal clean flash?

bronderb said:
No, go into fastboot and plug into pc. Open cmd and type "fastboot format userdata" "fastboot format cache" "fastboot format system"
Click to expand...
Click to collapse
Okay, thanks, and then what? Do I flash TWRP then push the stock ROM to the phone and flash that? And exactly how do I do that?

bronderb said:
You just go into twrp (no need to reflash) then adb sideload oxygen os
Click to expand...
Click to collapse
Thank you, I am now running OOS, hopefully everything else will go smoothly now, planning to go back to FOS again
I didn't even have to use the fastboot commands to format, just sideloading the OOS file wiped everything anyway

Turns out the issue isn't actually fixed, "system" still appears unchecked in TWRP. Could the fact that I didn't actually format everything first have made a difference, given everything was wiped in the process anyway?
Looks like I'm going to be living the sideloading life...
Edit: Sideloading freedom OS failed, ended up having to restore from my TWRP backup. I don't know what I'm going to do, my main reason for using custom ROMs is installing a black theme, and OOS doesn't support Layers or Substratum fully so I can't stay on that

Is the thing that says "mount system as read-only" enabled in the mounts menu? /System isn't ever mounted when TWRP starts, you have to manually mount it, but as long as the updater-script tells /system to mount, it will. However, if that option to make it read-only is enabled, then nothing will ever write to /system. Last resort is deleting the .twrps file from /sdcard/TWRP folder to remove current TWRP preferences and then when you boot into TWRP, that first screen has the swiper to allow modifications, and you'll swipe that

frickinjerms said:
Is the thing that says "mount system as read-only" enabled in the mounts menu? /System isn't ever mounted when TWRP starts, you have to manually mount it, but as long as the updater-script tells /system to mount, it will. However, if that option to make it read-only is enabled, then nothing will ever write to /system. Last resort is deleting the .twrps file from /sdcard/TWRP folder to remove current TWRP preferences and then when you boot into TWRP, that first screen has the swiper to allow modifications, and you'll swipe that
Click to expand...
Click to collapse
It isn't set to read only, I have tried updating and resetting TWRP but nothing has helped, in fact it's got worse, I managed to sideload OOS but my attempted install of FOS failed so I tried to restore from a backup and that also failed, something which didn't happen back when I was on RR.

evilkitty69 said:
It isn't set to read only, I have tried updating and resetting TWRP but nothing has helped, in fact it's got worse, I managed to sideload OOS but my attempted install of FOS failed so I tried to restore from a backup and that also failed, something which didn't happen back when I was on RR.
Click to expand...
Click to collapse
Which version of TWRP are you running? The official 3.1.0-0 is good for OOS and OOS based ROMs only. Try eng.stk's version.

Use the latest eng-stk twrp.
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
In recovery go to Wipe > Format data (this will wipe ALL in youre phone).
It's youre Data in F2FS? If yes you must change it to ext4, in recovery Wipe > Change file system. Reboot recovery. Check if it's changed.
Reboot to Bootloader (Fastboot). From PC reflash recovery.
Now copy Oos rom to the phone memory. Flash rom. Reflash recovery (the rom will overwrite the recovery). Reboot to recovery to see if it works. If not do it again.
I sugest to NOT restore old data. This way you'll have all new in youre phone.

tnsmani said:
Which version of TWRP are you running? The official 3.1.0-0 is good for OOS and OOS based ROMs only. Try eng.stk's version.
Click to expand...
Click to collapse
I was running 3.0.2-2 when the issue started, I updated to 3.0.3 and 3.1.0-0 but nothing changed. Thanks for the suggestion, I will give it a try

null0seven said:
Use the latest eng-stk twrp.
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
In recovery go to Wipe > Format data (this will wipe ALL in youre phone).
It's youre Data in F2FS? If yes you must change it to ext4, in recovery Wipe > Change file system. Reboot recovery. Check if it's changed.
Reboot to Bootloader (Fastboot). From PC reflash recovery.
Now copy Oos rom to the phone memory. Flash rom. Reflash recovery (the rom will overwrite the recovery). Reboot to recovery to see if it works. If not do it again.
I sugest to NOT restore old data. This way you'll have all new in youre phone.
Click to expand...
Click to collapse
Help! I attempted to do this and the process failed, I didn't manage to wipe data because "/data could not be mounted as device or resource is busy"
Edit: Device now has nothing but TWRP and fastboot, no OS, no ADB, no data, no internal storage

If you can reflash twrp from PC. If not reflash recovery from twrp recovery : Instal > Image > Select Recovery (you must have TWRP.img in youre phone memory )

I managed to get hold of a few factory images and attempted to flash system.img through fastboot, resulting error was
"target reported max download size of 536,870,912 bytes" (system image is 3080 MB)
"invalid sparse file format at header magi"

null0seven said:
If you can reflash twrp from PC. If not reflash recovery from twrp recovery : Instal > Image > Select Recovery (you must have TWRP.img in youre phone memory )
Click to expand...
Click to collapse
I reflashed the modified TWRP successfully. The second suggestion wouldn't have worked, given my phone has no internal storage

You can't see internal storage because of the recovery does not work write.
If you have a working recovery you can do all you want.

null0seven said:
You can't see internal storage because of the recovery does not work write.
If you have a working recovery you can do all you want.
Click to expand...
Click to collapse
The recovery was working at this point, the issue turned out to be the data partition, system was formatted to ext4 but I didn't realise data was in f2fs which caused the problem in the first place. I formatted to ext4 and everything worked, I was able to install paranoid android and everything worked...
...until I flashed the wrong firmware and now I've hard bricked it! I'm going to try the hard brick toolkit
Edit: After 12 hours of being an unresponsive brick, the phone suddenly booted, system doesn't work but it has recovery. Unfortunately I seem to be back to square one, if I try to flash something it appears to succeed but then the phone doesn't boot up into system

So I am now back to the original issue of system not mounting, in terminal if I type "mount /system" I get following error:
"mounting /dev/block/sde20 on /system failed: Device or resource is busy"
Anyone know how to solve this?

I formatted everything, reflashed recovery and tried to flash OOS, got following error:
Code:
[FONT="Courier New"]"This package is for OnePlus3 devices, this is a oneplus3t" (it isn't)
"Updater process ended with ERROR: 7
Error installing zip file /sdcard/OOS3.2.6.zip" [/FONT]

Issue was "solved" by flashing PA, GApps and the correct firmware
Hopefully that's the end of all this drama, thanks to everyone for their suggestions

Hi, I'm pretty new at rooting and I seem to have a similar error. I'm getting the "can't mount /system" error in TWRP. I am able to boot into OOS 4.1.3 and run the nandroid backup but, I keep getting the same error and am unable to select "system" when choosing the mount option in TWRP.
Do I need to have all partitions in f2fs? My system partition is in ext4. Is this what solved your issue?
It seems my phone is functional even with the error active but, I've been trying to get systemless SuperSU and MagiskHide working and I think that's what is preventing me from doing so.