So, I went to use the OpenRecoveryScript feature earlier today... and upon restarting it booted into Paranoid Android, but just hung at the flashing fish screen... any idea why that would happen? At this point all I can do is boot in recovery, and have tried wiping and reflashing the ROM (PA 3.69) several times, fix permissions... and still the same result. Any suggestions would be very appreciated.
I have a problem with latest TWRP for N4(2.6.3.3)
I could not mount sd-card in TWRP mode because i did not see the Mount button, so i could not copy the rom file to my phone. Rightnow my phone is empty, it doesnt have rom. So what can i do rightnow? Please help T_T
I could not mount sd-card in TWRP mode because i did not see the Mount button, so i could not copy the rom file to my phone. Rightnow my phone is empty, it doesnt have rom. So what can i do rightnow? Please help T_T
Use the sideload feature. Drop your ROM in your adb/fastboot folder on your computer. Connect your device, go to advanced in the recovery menu and hit adb sideload.
Swipe to start it, then open a terminal window on your computer and type "adb sideload addyourfilename.zip", just make sure you either rename it to something simple or copy/paste the ROM file name exactly. And you're done.
For more info http://teamw.in/ADBSideload
sent via mako
Anybody experience the phone booting into twrp instead of rom. Anytime I turn on the phone it boots into twrp and then I have to reboot to system and boots normally.
Sent from my Nexus 4 using Tapatalk
Sent from my Nexus 4 using Tapatalk
I think that is rom issue because I used to have it when I was using Overstock rom. After changing rom, no more issues.
yes it's on ROM issue, back then i encoutered on cwm too
On new 2.6.3.3 has anybody had a problem with it failing due to partition error? I can't flash anything because of the partition error
Sent from my Nexus 4 using xda app-developers app
Sent from my Nexus 4 using xda app-developers app
Had the same Problem. So i flashed stock 4.3 and then flashed twrp. That fixed the error for me.
Edit: dont forget to do a factory reset after flashing stock. Otherwise u propebly get a Problem with your infernal storage. If u habe the 16 GB Variante.
Gesendet von meinem Nexus 4 mit Tapatalk
Edit: dont forget to do a factory reset after flashing stock. Otherwise u propebly get a Problem with your infernal storage. If u habe the 16 GB Variante.
Gesendet von meinem Nexus 4 mit Tapatalk
Last edited:
Well I figured it out. I had to use philz recovery at first. And I had the 8gb variant but I still factory reset it. Now I'm back on twrp I'm gonna see if it will flash today
Sent from my Nexus 4 using xda app-developers app
---------- Post added at 09:35 AM ---------- Previous post was at 08:54 AM ----------
Although I would still like to use twrp. I just noticed though, the backup I created still had the build number of stock at the end. And I'm still getting the error when I try to flash it on twrp
Sent from my Nexus 4 using xda app-developers app
Sent from my Nexus 4 using xda app-developers app
---------- Post added at 09:35 AM ---------- Previous post was at 08:54 AM ----------
Although I would still like to use twrp. I just noticed though, the backup I created still had the build number of stock at the end. And I'm still getting the error when I try to flash it on twrp
Sent from my Nexus 4 using xda app-developers app
Also figured out that apparently the Recovery's don't have access to /recovery and /boot. How do I fix that?
Sent from my Nexus 4 using xda app-developers app
Sent from my Nexus 4 using xda app-developers app
I already tried that but ITT sort of resolved itself. I went back and redid the IMG flash to 2.6.3.3 backed up my rom_, flashed the 4g lte radio and it passed. Then I flashed the ROM and all of a sudden it started working
Sent from my Nexus 4 using xda app-developers app
Sent from my Nexus 4 using xda app-developers app
Yet now ROM won't pass until I flash something else that's not a rom
Sent from my Nexus 4 using xda app-developers app
Sent from my Nexus 4 using xda app-developers app
Any chance i can set a password to enter recovery? Thanks
The TWRP recovery has been updated to version 2.7.0.0:
http://techerrata.com/browse/twrp2/mako
As usual, update by flashing it in fastboot mode
or flash in any custom recovery using the flashable zips below
j.mp/n4twrp for TWRP
j.mp/n4cwm for CWM Touch and normal
Flash it in recovery and you are all done. You can revert back to either recoveries by flashing the version you want to.
all zips have been tested on my N4. recovery img files are sourced from clockworkmod.com for CWM and goo.im or techerrata.com for TWRP.
Sent from my Nexus 4 using Tapatalk 4
http://techerrata.com/browse/twrp2/mako
As usual, update by flashing it in fastboot mode
or flash in any custom recovery using the flashable zips below
j.mp/n4twrp for TWRP
j.mp/n4cwm for CWM Touch and normal
Flash it in recovery and you are all done. You can revert back to either recoveries by flashing the version you want to.
all zips have been tested on my N4. recovery img files are sourced from clockworkmod.com for CWM and goo.im or techerrata.com for TWRP.
Sent from my Nexus 4 using Tapatalk 4
Changelog v2.7.0.0:
Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to TassadarAllow sideloading from /tmp on encrypted devicesCheck for a crypto footer before asking for a password to prevent user confusionAdditional checks for validity to auto generated*backupnamesText wrap in the console outputProper caps lock support in the keyboardMouse support via USB OTG for devices with a broken digitizerImprove scanning of storage locations for OpenRecoveryScriptHaptic feedback for buttons, keyboard, and vibration at the end of longer running actionsFixed ext4 wiping when no selinux contexts are defined for that partition (e.g.*sd-ext)Update SuperSU to 1.93 and improve installation processAdded selinux contexts restoration to fix permissionsLoad RTC offset on Qualcomm devices to fix the date/time in recoveryUSB Mass Storage fixes Add SELinux support checkingAdd Disk Usage class to better handle excluded folders (e.g. Google Music cache)Add 4.4 decrypt supportAdd some toolbox utilities to TWRP (namely to support SELinux functions not supported in*busybox)Various SELinux fixes and bug fixesNote: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts. We don't own most of the devices that we support so we depend on outside testers and developers to help us update devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button (the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say "Full SELinux support" in the console, then your device still needs some work. Help us help you.
Proper*backup*and restore of SELinux contexts (thanks to Tassadar)Pull in some ROM information for*backup*name generationMerge all recent patches from*AOSP*bringing TWRP up to date with Android 4.3Add 1200x1920 theme (thanks to Tassadar)A few other fixes and tweaks
Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to TassadarAllow sideloading from /tmp on encrypted devicesCheck for a crypto footer before asking for a password to prevent user confusionAdditional checks for validity to auto generated*backupnamesText wrap in the console outputProper caps lock support in the keyboardMouse support via USB OTG for devices with a broken digitizerImprove scanning of storage locations for OpenRecoveryScriptHaptic feedback for buttons, keyboard, and vibration at the end of longer running actionsFixed ext4 wiping when no selinux contexts are defined for that partition (e.g.*sd-ext)Update SuperSU to 1.93 and improve installation processAdded selinux contexts restoration to fix permissionsLoad RTC offset on Qualcomm devices to fix the date/time in recoveryUSB Mass Storage fixes Add SELinux support checkingAdd Disk Usage class to better handle excluded folders (e.g. Google Music cache)Add 4.4 decrypt supportAdd some toolbox utilities to TWRP (namely to support SELinux functions not supported in*busybox)Various SELinux fixes and bug fixesNote: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts. We don't own most of the devices that we support so we depend on outside testers and developers to help us update devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button (the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say "Full SELinux support" in the console, then your device still needs some work. Help us help you.
Proper*backup*and restore of SELinux contexts (thanks to Tassadar)Pull in some ROM information for*backup*name generationMerge all recent patches from*AOSP*bringing TWRP up to date with Android 4.3Add 1200x1920 theme (thanks to Tassadar)A few other fixes and tweaks
I think the sweetest feature ever to add to recoveries would be the ABILITY to install ROM's from cloud storage. That would be a game changer! I know not everyone would use it cause of their god awfully slow internet and absolute refusal to use cloud storage. But for those of us with some real internet speeds, it would be perfect. As well the ability to restore nandroids from the cloud and backup to the cloud. Just my two cents and thoughts.
Is OTG limited to just mouse and keyboard? What about usb storage?
-------------------------------------------------------------------------
[DEVICE : N⁴] [ROM : crDROID] [KERNEL : FK.203-OTG]
[LAUNCHER : NOVA] [CARRIER : T-MOBILE]
[SCREENSHOT : MAR.07.2014]
-------------------------------------------------------------------------
[DEVICE : N⁴] [ROM : crDROID] [KERNEL : FK.203-OTG]
[LAUNCHER : NOVA] [CARRIER : T-MOBILE]
[SCREENSHOT : MAR.07.2014]
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone