HI all,
I flashed CWM recovery to my Tegra Note 7 tablet and it's upside down. Is there a way to invert it right side up or is there an updated version that fixes that issue?
On a side note: I'm new to development, but I would like to learn how to pull the bootloader from the device and edit it so that the red warning is removed and the device can be sent back under warranty if needed. Does anyone know which partition the bootloader is located in?
Thanks for any help you can provide.
You are just holding the tablet the wrong way around
but no, no fix yet. its normal.
I would recommend not even touching the boot loader. Changing any code in the boot loader can lead to the device not even turning on. I don't think even apx mode can save you if the boot loader is messed up.
Sent from my TegraNote-P1640 using XDA Premium 4 mobile app
Heh, too late! Already installed the CWM recovery, but I can restore the original recovery quite easily though. The bigger question is whether I can keep root with a stock recovery. Then again I might as well as go ahead and find out in the morning.
EDIT: I flashed stock recovery back and root still works. Can also boot into stock recovery without a problem.
Related
I recently came across an issue where TWRP recovery would hang and then cause the bootloader to be stuck trying to boot into a broken recovery. The only way I could fix it was to reflash the recovery.img with fastboot, boot into the freshly flashed android recovery through VOL- method, and then power-off device from within recovery menus.
No other method I tried broke the bootloader-looping-while-trying-to-unsuccessfully-initialize-recovery cycle.
Only downside is that I am really not sure actions cause(d) TWRP to hang on init (the "curtain" logo never began to raise to the top of the screen) the three times I have caused it.
Just a little helpful info for people that experience(d) this.
disynthetic said:
I recently came across an issue where TWRP recovery would hang and then cause the bootloader to be stuck trying to boot into a broken recovery. The only way I could fix it was to reflash the recovery.img with fastboot, boot into the freshly flashed android recovery through VOL- method, and then power-off device from within recovery menus.
No other method I tried broke the bootloader-looping-while-trying-to-unsuccessfully-initialize-recovery cycle.
Only downside is that I am really not sure actions cause(d) TWRP to hang on init (the "curtain" logo never began to raise to the top of the screen) the three times I have caused it.
Just a little helpful info for people that experience(d) this.
Click to expand...
Click to collapse
It could be a bad memory sector.
Has this happened with any other recovery?
Sent from my MB860 using xda premium
d3athsd00r said:
Has this happened with any other recovery?
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Not in my extensive cowboy-flashing (aka potentially jacking things up). I have used multiple versions of Clockwork, TWRP, and Clockwork touch.
It was mostly a puzzle about how to proceed and I wanted to share it with others. I say that because I see a lot of "is my device bricked?!?"-type posts. It seems to me that the only way to actually brick most devices is during direct firmware flashes using RSD (in the case of the Atrix) or some other equivalent like you see with NVidia Tegra interfaces.
The first time I experienced it I did have an "oh ****" moment or two, mostly because of having to reboot without having a functioning recovery partition.
In short I would say that touch-type recoveries carry an additional level of risk over hardware-key recoveries like CWM. The moral of the story for newbies is to RTFM and follow directions, especially when flashing a .sbf on the Atrix through RSD.
So I've heard that when rooting, there's a bug that stops us from going into the cwm with the physical buttons and are forced to use the software to do it. My question is that when this bug is adressed will we just need to download the newer cw, from the play store and within that app just click flash clockwork mod? Or will we need to roof and do everything again?
Sent from my Nexus 7
Okaay said:
So I've heard that when rooting, there's a bug that stops us from going into the cwm with the physical buttons and are forced to use the software to do it. My question is that when this bug is adressed will we just need to download the newer cw, from the play store and within that app just click flash clockwork mod? Or will we need to roof and do everything again?
Sent from my Nexus 7
Click to expand...
Click to collapse
root the tablet
then install ROM manager and flash the official recovery from there
works perfect
The bug is that you cannot boot into any recovery (cwm/twrp/stock) from bootloader unless you are plugged into you computer via a usb cable. The only other way to boot is to use a script but that requires a working system partition.
Sent from my Nexus 7
I have the same problem and I flashed the official CWM from Rom Manager. I made a nandroid before I messed with it and when I went to change the LCD Density, I don't know what happened but now it won't boot. I can't get into CWM either. I figure I'll use ADB when I get home to try and reboot into recovery, if not I'll search the forums for the stock image and reflash. If there is a HW workaround to get booted into it from the device itself that would be awesome. I had to do a battery pull to keep it from rebooting itself and killing the battery.
I've always had Rom Manager Pro and immediately after rooting, used it to flash backups, update to 6.0 cwm, etc. If your rooted you must have that or Goo Manager for TWRP flashing anyway. Might as well start immediately.
There is a thread somewhere here dealing with changing density. The Nexus7 has problems when you simply use a density changing app.. You must change density by modifying prop.build. You can do this using a root explorer app, or by using Rom Toolbox Pro. I use Rom Toolbox and it worked perfect.
Once I get it up and running again around lunch time, I'll do that. Probably bring my laptop back to work with me. One question I had is will I be able to access CWM recovery by using ADB commands or will it just put me on the Google screen with the padlock?
chrisjm00 said:
Once I get it up and running again around lunch time, I'll do that. Probably bring my laptop back to work with me. One question I had is will I be able to access CWM recovery by using ADB commands or will it just put me on the Google screen with the padlock?
Click to expand...
Click to collapse
You can do fastboot boot recovery.img', or whatnot, even though it can't boot the recovery from the bootloader, at least you won't bork the device if /system gets messed up. 'adb reboot recovery' should work from android too.
I am stuck at the Google screen with the padlock and can't use ADB as it won't even recognize the device.
Is this a 6.0.0.6 issue? 6.0.0.4 worked just fine. I had a bad feeling when I hit upgrade through ROM Manager.
jmhalder said:
You can do fastboot boot recovery.img', or whatnot, even though it can't boot the recovery from the bootloader, at least you won't bork the device if /system gets messed up. 'adb reboot recovery' should work from android too.
Click to expand...
Click to collapse
Will that command allow me to access recovery to restore my backup?
---------- Post added at 02:55 PM ---------- Previous post was at 02:53 PM ----------
yeahthatsme said:
I am stuck at the Google screen with the padlock and can't use ADB as it won't even recognize the device.
Is this a 6.0.0.6 issue? 6.0.0.4 worked just fine. I had a bad feeling when I hit upgrade through ROM Manager.
Click to expand...
Click to collapse
I believe you need to be on the bootloader screen? I haven't flashed anything from Asus in a while, not since my original Transformer.
chrisjm00 said:
Will that command allow me to access recovery to restore my backup?
Click to expand...
Click to collapse
Code:
fastboot boot recovery.img
where recovery.img is a CWM image, should allow you to get into the recovery to fix whatever you messed up. Note that ADB is only functional if you already have CWM or Android booted... in the bootloader, fastboot is all that's available.
I have the same issue. Stuck at the Google logo with a padlock at the bottom. I didn't flash anything with ROM Manager just the recovery.img through fastboot, then did a fastboot reboot. Now I'm lucky if I can get the thing to stay off when I hold the power button it just pops back up to the padlock with Google logo.
When going to recovery from bootloader - freeze at google logo
It works by rebooting into recovery via ROM Manager. Also by the way, can anyone give me a link to the mod for the nexus 7 on jelly bean for the extended power menu?
CooLoserTech said:
When going to recovery from bootloader - freeze at google logo
It works by rebooting into recovery via ROM Manager. Also by the way, can anyone give me a link to the mod for the nexus 7 on jelly bean for the extended power menu?
Click to expand...
Click to collapse
Has anyone figured a way to access recovery using the buttons only? I've tried TWRP 2.2 and the newest cwm, and on a cold start from power off, it sticks at the Google logo. During a bootloop you are screwed unless you have a laptop within arms reach. Until this is rectified I'm leery of flashing anything. The whole point is being able to restore a nandroid in a crisis. I haven't found that ability yet. If anyone knows a way, please educate me!
Guess we can just wait. Besides there's not much development yet anyways. Would love to use AdFree and root explorer though.
Sent from my Nexus 7
chrisjm00 said:
Once I get it up and running again around lunch time, I'll do that. Probably bring my laptop back to work with me. One question I had is will I be able to access CWM recovery by using ADB commands or will it just put me on the Google screen with the padlock?
Click to expand...
Click to collapse
Recommend downloading quickboot. It is a paid app but it boots you to recovery no hassles with the buttons
Sent from my Nexus 7 using Tapatalk 2
Ya i have tried several version of CWM and TWRP and manually reinstalled cwm via adb. but all of them don't let me boot from the bootloader, i get the google logo like everyone else. Not sure what else to try, need to not take any risks until there is a fix i guess ^_^ hope someone gets some ideas
Yes i know. I ****ed up. But somehow i was tinkering and managed to delete the entire internal storage. I can still get into fast boot and.twrp. Can someone please help me?
What was i trying to fix? Check my other thread about the headphone jack.
Edit:Also. Twrp says i dont have an os above every swipe screen...
AW: [Q] Nexus 7 stuck on google screen boot
Have you tried reflashing stock?
Sent from my Nexus 7 running Android 4.2.1
If you have an OTG cable and a USB key you should be able to make ROMs or other backups which you preserved OFF THE TABLET available to TWRP.
If not, take the above poster's advice and install pure stock to copy stuff (ROMs, recovery images, etc) back on to the tab via MTP.
I too blew away all of /data once with that "format data" button in the touch version of TWRP; I feel your pain.
Um.....I may have made a mistake and swiped on all the clear screens...including internal memory...so...T_T Am i screwed???
JoshuaXedos said:
Um.....I may have made a mistake and swiped on all the clear screens...including internal memory...so...T_T Am i screwed???
Click to expand...
Click to collapse
You're not really screwed, you should be able to flash another ROM from recovery.
As long as you can get into fastboot, you'll be fine. The easiest way is to download and install Nexus Root Toolkit, then use the "back to stock" part to flash the factory image following the instruction.
I have got something even worse
My nexus 7 tab started freezing during use and then after booting in safe mode and wiping cache in recovery mode it now doesn't even go past the google screen. I haven't even flashed anything to it at all and it's showing these crazy symptoms (The bootloader is still locked and the device is not even rooted). I still have access to the adb sideload mode and fastboot but I am confused af as to what has happened
Any ideas guys?
Hello guys
For some reason I decided to test out the CM and Slim 4.4 roms, but did not see that there were issues flashing with TWRP... so flashing failed with both these ROMS. I did not read the ops on Slim and did not see any warning about TWRP on the CM, so began wiping stuff to try make the flash happen, eventually wiped too much, and now I cannot boot the tablet. Worse is I have also wiped the zip files from the tablet so now I have PhilZ Touch CMW recovery but nothing to flash and this Recovery does not suppot OTG memory, so I have nothing to flash.
SO, tried my full version of Nexus 10 Toolkit to sideload the zip, but Toolkit never gets past "Toolkit Waiting for ADB mode".
I don't know the manual commands to try flash one of these roms, but at this point, I would be happy to just go back to stock, and cant figure how to get to Download mode, there is no home button on an N10.
It seems my safest bet, if possible, would be to get to download and flash a rom there.
Any ideas, much appreciated,
Mark.
fredphoesh said:
Hello guys
For some reason I decided to test out the CM and Slim 4.4 roms, but did not see that there were issues flashing with TWRP... so flashing failed with both these ROMS. I did not read the ops on Slim and did not see any warning about TWRP on the CM, so began wiping stuff to try make the flash happen, eventually wiped too much, and now I cannot boot the tablet. Worse is I have also wiped the zip files from the tablet so now I have PhilZ Touch CMW recovery but nothing to flash and this Recovery does not suppot OTG memory, so I have nothing to flash.
SO, tried my full version of Nexus 10 Toolkit to sideload the zip, but Toolkit never gets past "Toolkit Waiting for ADB mode".
I don't know the manual commands to try flash one of these roms, but at this point, I would be happy to just go back to stock, and cant figure how to get to Download mode, there is no home button on an N10.
It seems my safest bet, if possible, would be to get to download and flash a rom there.
Any ideas, much appreciated,
Mark.
Click to expand...
Click to collapse
From recovery power down your tablet and get into fastboot by holding volume buttons and power buttons at the same time. If this works then you'll be fine because from there you can get back to stock. Download wugfreshs nexus toolkit. Use the option to return to stock and check the one that says stuck in bootloop but can access fastboot (or something like that) then plug your tablet in while its in fastboot mode and go through the steps. It'll have to download stock factory image unless you already have it and browse to it but the toolkit will do everything and get your tablet working again. Don't worry too much its usually not as bad as it seems. The same thing happened to me and I panicked and it turned out to be an easy fix. If you need any more help or more detail on what to do just ask
Sent from my Nexus 10 using xda app-developers app
Thanks Abdel, that worked fine... though I did spend about an hour on Wugfresh last night, it kept on starting to do stuff, then got to recovery mode and it stopped with wufgresh saying waiting for device or something... maybe shutting computer helped too... anyway, thanks for the advice, somehow it worked!
Cheers
Mark.
abdel12345 said:
From recovery power down your tablet and get into fastboot by holding volume buttons and power buttons at the same time. If this works then you'll be fine because from there you can get back to stock. Download wugfreshs nexus toolkit. Use the option to return to stock and check the one that says stuck in bootloop but can access fastboot (or something like that) then plug your tablet in while its in fastboot mode and go through the steps. It'll have to download stock factory image unless you already have it and browse to it but the toolkit will do everything and get your tablet working again. Don't worry too much its usually not as bad as it seems. The same thing happened to me and I panicked and it turned out to be an easy fix. If you need any more help or more detail on what to do just ask
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
fredphoesh said:
Thanks Abdel, that worked fine... though I did spend about an hour on Wugfresh last night, it kept on starting to do stuff, then got to recovery mode and it stopped with wufgresh saying waiting for device or something... maybe shutting computer helped too... anyway, thanks for the advice, somehow it worked!
Cheers
Mark.
Click to expand...
Click to collapse
Your welcome I'm glad you got it working. Make sure to that k wugfresh as well for his awesome tool
Sent from my Nexus 10 using xda app-developers app
Ok, I'm new at this, here's what I've got, hopefully someone can shed some light:
-My RAZR M is fully encrypted
-It is successfully rooted
-I have installed Rom Manager with CWM 6 as the custom recovery
-I want to make a NANDROID backup (to eventually install Carbon), but whenever I try to reboot into the backup/recovery mode, it won't, it goes to what I think is the ADB screen? Not sure tho, this screen says "Connect data USB." Then, when I do, it just changes state and says USB connected, nothing else happens. Then I just reboot the phone normally and everything still works.
So after googling and researching a lot, I'm assuming since my phone is encrypted it won't access the CWM because it never asks me for my password to decrypt the internal storage. Ok cool, but here's my question now tho; if I perform a Factory Reset from the settings menu, will it actually do the reset and reinstall itself since I have CWM installed??
Thanks for any help.
Anyone got any ideas??
Is your bootloader unlocked?
Sent from my XT907 using xda app-developers app
Hmm. Is this screen where it says "Device is LOCKED" mean that my bootloader is locked? Btw, this is the screen that I referred to in my first post. It comes up whenever I try to select "Recovery"
Your bootloader is locked and on that version it can not be unlocked... So... unfortunately you can not install a custom recovery... Well you can use safestrap but the ROM selection is very limited...
Sent from my XT907 using xda app-developers app
So you say I cannot install a custom recovery, do you mean a different ROM that I would "recover" to install it? Or do you mean ClockworkMod (and its various counterparts)? Because in the ROM Manager app, it says I have CWM 6.0.4.4 as my "current recovery" (see attached screenshot)
Please forgive me if this is a dumb question lol but like I said, I'm new at this whole thing
It does say that huh unsure as to why... i do have a locked M around here somewhere ill see if it does the same thing to it...When I say custom recovery I do refer to cmw n twrp... With a locked bootloader you can not install those... we have for safestrap as a recovery for locked bootloaders it's been a year since I used it but I believe you can make backups on it... I would just sit tight and.wait on kit kat it shouldn't be to much longer... till then just freeze all the bloat and use xpossed to your liking... When kk comes out I'm sure development will pick up for locked bootloaders again..anyone else with more experience care to provide more in depth assistance..
Sent from my XT907 using xda app-developers app
So any further advice on what I can or can't do?
I would like to perform a factory reset on my device to get rid of this stupid encryption (it slows everything down), but with CWM installed (supposedly?), can I still do a factory reset? I guess what I'm trying to get at is what does the factory reset option use to re-flash everything from? The recovery partition where CWM is now supposedly installed? Will that affect the factory reset?
I hope this makes sense, I don't want to brick my phone...
Alrighty, for anyone interested:
I never tried the factory reset. What I did do is try the OTA KitKat update just like 2 hours ago. That was a mistake; upon downloading and automatically rebooting to start the upgrade, my phone would not reboot, it got stuck at the AP Fastboot screen with the error code 0x56 (see attached picture).
So, I powered off and powered on my phone, at which point it powered up normally, until after about 2 minutes on the home screen, it automatically rebooted itself (to presumably "continue" trying to install the OTA). Then it got stuck again on the AP Fastboot screen. This continued over and over and I soon realized I soft bricked my phone.
Did some further research, found the House of Moto program (http://www.droidrzr.com/index.php/topic/28162-house-of-moto-22/) which saved my life. If anyone is having any issues similar to the situation I was having, or just issues with the KitKat OTA, this House of Moto program will restore your phone to completely stock. Just follow the instructions on that web page exactly. Kudos to the dude who developed that.