Please Help i loaded a custum ROM and it loaded but it just loops I tried taking out the battery factory reset and nothing it show a skull then droid and continues over an over until the battery is drained. How do I get it to stop?
With that total lack of useful information in your question, it's going to be very hard to help you. From what you've posted, I believe you might be using an Android phone. I can't tell anything else.
I don't know if you have a Recovery image installed, if you have taken a Nandroid Backup that you could use to restore your environment, or what steps you took to damage the OS. A valid Nandroid Backup would make recovery quick and easy.
If you can boot into the bootloader (steps to do so are depending on the specific phone), you could use Fastboot from a Windows or Linux workstation to begin steps to repair your environment. From the bootloader, you might also be able to boot into Recovery, if you have a Recovery image installed, and restore a Nandroid Backup, if you bothered to take one.
If you are unfamiliar with Fastboot, it is a desktop program that communicates with the bootloader on the phone via USB. A running Andriod system is not used. Using it, you could flash a recovery image, etc.
Fastboot is part of the Android SDK, but you can also install just Fastboot and its counterpart desktop application used when Android is running, adb, without installing the entire SDK. See http://forum.xda-developers.com/showthread.php?t=928370
You could also flash a official RUU and everything will go back to stock and you could start again, that's unless you flashed recovery and made a backup before you flashed a custom rom, then it's just a matter of a simple restore.
More information would be helpful.
Related
I rooted my HTC Desire CDMA from USCC okay, flashed a Froyo ROM with USCC stuff, and everything was okay. I made a nandroid backup, flashed CyanogenMod 7 RC4 and it seem to work okay, except I was having trouble entering my password when checking voice mail. Anyway, I decided to go back to Froyo. I used ROM Manager to restore the backup and got into ClockworkMod. However, none of the options work. If I go down to recovery, I go to the next screen, but no matter which option I select I end up with a black screen and nothing happens! I can't restore my backup! If I just try to press power on, I end up with the blue CyanogenMod screen and the arrow just goes round and round. Nothing happens. Please, if anyone has any suggestions, it would be greatly appreciated.
I remember hearing that because CM7 is a Gingerbread mod, it must use ClockworkMod v3 and to go back to your Froyo backup you'll need to downgrade to Clockwork Recovery 2.x. I'm not sure if things has changed, though, this was what I read a month or two ago.
Are you by any chance able to fastboot?
Reflash your CWM (if you are using NAND version) or get it again on your SD (if your are using SD version).
The problem is I can't do anything in ClockworkMod (version 2.5). Every option I select gives me a blank screen! I made a nandroid backup before flashing CyanogenMod, but I have no way of getting to my backup if I can't use ClockworkMod. Also, if I try to boot the phone, i just get the CyanogenMod 7 startup screen with the arrow going round and round. It will still be there 30 minutes later. I have to do a battery pull to start over with anything.
I was able to boot my phone after wiping all user data. I would like to use my nandroid backup to return to the previous ROM, but clockworkmod doesn't seem to work. I tried reflashing it in ROM manager and it only downloads a second or so and isn't really doing anything. I'm wondering if clockworkmod is defective. Is there any other way to flash it again without using ROM Manager?
If you are able to fastboot, you could try to restore a nandroid by flashing three files (boot.img, system.img, data.img) from your nandroid backup using:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata data.img
Disclaimer: I've not actually tried this procedure before! I got this info from here
You could use a similar procedure to flash a new ClockworkMod since your recovery may be corrupted: fastboot flash recovery recovery-clockwork-3.0.0.5-vision.img
You can download the image from Koush's website, under HTC G2.
This happened to me yesterday trying out the Alpha Build for the Fascinate. I was getting a dev block error and datadata would not mount. I had to go back to stock on heimdall. I don't know if this helps for your phone, but maybe somone with more knowledge can tell you if this may be happing to you and what the fix is, if that's not a fix for you.
I have the Nexus S from Telus.
It was rooted, unlocked, running CM7. However I've been having issues with it freezing and decided I want to go back to the stock rom.
I ended up downloading what I thought was stock ROM for my phone (Stock GRH78 Nandroid Backup in this Tutorial http://forum.xda-developers.com/showthread.php?t=884093) however after it flashed my phone, I ended up with a phone which was essentially stuck in Airplane mode, would not connect to Telus. I'm guessing that it has the wrong radio for my phone/carrier?
So then I ended up finding a zip file someone posted Stock-GRJ22-i9020A-unsigned which should have worked, I ended up flashing the zip file from recovery.
It said it installed fine. Rebooted, and now the phone just cycles the Samsung Loading screen endlessly.
I tried to go back to recovery, and it gives me yellow triangle with !.
Is there any way to flash the recovery image back to the phone?
I plug the phone in and the PC won't recognize a device.
I installed the Android SDK
Ran the command adb devices, no devices attached to the PC.
I tried fastboot devices - blank
I don't know how I'll be able to get files back onto the phone SD Card for flashing etc...
I had the exact problem two days ago...flashed an image that jacked my phone up. Wouldn't boot past the google logo. Sat there indefinitely.
Read this thread and see if you can get it work. In a nutshell, you need the PDA net drivers installed. Since PDA net can't install the app on your phone (because it's not booted into an OS) leave the install program in limbo and voila, fast boot will work. From there, push the recovery.img (google Clockworkmod recovery image), boot into recovery and you are off to the races.
This is, of course, assuming you already have a ROM image on your internal SD card you can flash to get back up and running. I'm not sure how to install a .zip image ROM if you can't gain access to your SD card.
http://forum.xda-developers.com/showthread.php?t=1303522
Good luck, I know the feeling. It blows.
Ah, just found out how to install a file on a phone that won't boot.
You do need to flash CWM recovery first though.
http://forum.xda-developers.com/showpost.php?p=18437305&postcount=2
Good news! I tried a factory reset/data wipe and rebooted the phone.
It doesn't hang anymore, all functions restored and the phone is working on Telus again!
I guess I had to format data, clear cache, before the flash of the rom.
So relieved.
Issue has been solved!
Hi all,
i'm stressing out a little, mainly due to what I think is a lack of understanding on my part. I have a B70 Transformer with SBKv2, which basically means flashing stock via NVFlash is right out. Now, i'm slightly OCD when it comes to my devices, and I like to know exactly how certain procedures and processes work. So, i'll detail how I think it works, and if someone could correct me, that'd be great. From what I can tell in android, their are 3 levels of factory restoring/recovery.
1) The Factory Reset
So, from what I can tell, the factory reset boots into a special recovery mode, calls upon a hidden recovery partition and simply overwrites all FILES (not partitions) in the system partitions.
2) The Firmware flash
The firmware flash (this calls from experience with samsung devices) boots into a lower level recovery mode (or the same from what I can tell on the transformer), wipes all data of all partitions and restores all files from a firmware zip file.
3) The repartition
(Again, mainly experience from samsung devices). From what I can tell with special situations like this, the OS relies on a seperate entity (IE: Odin, Heimdall) to blank out the flash memory, re-lay a new partition layout and then restore the data.
Now, to my actual question. I like to keep my devices stock, but with a B70 and SBKv2 I am basically limited to option 1 unless I root. If the system itself crashes (IE, lockups, reboots etc) is it likely to alter or damage the recovery partition in any way? I'd like to know that barring a catastrophic incident/my own stupid tinkering that I have a way to bring back a completely clean and stock system. Will the factory reset achieve this? Is there any way to flash/downgrade new/old firmware on the B70s without rooting? I have tried the ASUS methods on honeycomb and ICS zip files from their website and beyond, but it doesn't seem to work. Do ASUS tablets have a PC based reflash package similar to Odin for samsung?
Excuse the blathering, I just want to be absolutely sure I can get a completely clean, stock experience if I need to, and ASUS devices seem a little more complex then Samsung devices to achieve that goal.
Thanks for reading and answering if you do
1.Facory reset deletes system data (Not apps or anything just stuff you put in) as well as wiping other installed apps but does not touch the data on your sd card
2. all firmware flash does is whatever the dev writes in the script which is most times mounting system and framework formatting them and rewriting the new files as well as writing in a new kernel
3. Only way to do this is NVFlash which requires sbk1 so you cant do this
Factory resetting will likley solve your problems
Rooting will not mess with recovery
Only way to downgrade is through root although most times downgrading takes the root away
The Odin equivalent is NVFlash which as i said before will not work for you
You are confusing some things, and overcomplicating others.
You have three boot modes- recovery, system, and APX. APX would be similar to the download mode on a Samsung phone, where it does nothing but wait to receive instructions and data to flash over both recovery and system partitions. As you have a SBK2, this mode is practically useless because before flashing, the bootloader needs to be unlocked with the SBK, and then can restore the device- as SBK2 is a mystery, APX mode on an SBK2 device is only useful to Asus at the moment.
Recovery mode can flash itself, and system partitions, and it can also wipe and backup data, install updates, etc. Think of any CWM recovery, these functions are contained in the recovery, although in the stock recovery they are hidden from view with an animation and no UI to interact with.
You can flash both ROM (system) and recovery partitions independently of one-another, well, in a way- you can install recovery from within the OS (does require a reboot and actually uses recovery to install, but nonetheless, if you botch your recovery mode you can reflash this way IIRC). You can also flash ONLY the ROM if you wish via recovery mode, if you have CWM installed. You can flash entire packages, containing both ROM and recovery, as well in CWM, and stock packages released by Asus can be flashed via the stock recovery partition.
In order to get a better understanding though, I suggest you read my noob guide linked in my sig
WOW, thankyou so much for the prompt replies! You people are geniuses, gentlemen (gentlepeople?) and scholars. Also, reading the guide recommended by luna now. Thankyou for the clarification
Here's my understanding:
1) the factory reset- this wipes data and maybe cache. The factory reset assumes that your device is not rooted, so there are no changes to the system partition. All non-root changes are to the data partition.
2) The firmware flash- this uses the recovery to write the system partition. The OTAs are applied this way with the stock recovery. Custom recoveries also use this. There is also a staging partition that can be used to write the kernel (boot.img on other devices) and the EBT partition (bootloader on other devices).
3) the repartition- this is nvflash and can be used (if accessible) to repartition, backup, and/or flash all partitions on the device. I think this is the counterpart to Odin/Heimdall since it can be used to recover an otherwise bricked device. This is analogous to fastboot on HTC devices, although it is possible to erase the fastboot bootloader and really brick the device. As far as I know, this type of brick is not possible with nvflash or Odin/Heimdall since the bootloader is built into the device.
Now, to your question, the system and recovery are seperate systems. You can bork your system and still be able to boot into recovery, so there is a way to restore. That being said, there are a few limitations since all of the tf101 recoveries I have come across don't back up the kernel/boot.img. This can be a problem if incompatible bootloaders or kernels are flashed together. To compound the problem, some roms have kernels/boot.img's included and some do not, so it's quite possible to get into a bad situation just by flashing something and then trying to restore a backup. This seems to be a common problem here on XDA in the transformer section- flashatosis.
After all that, it is possible to go completely stock without nvflash, but you have to use the staging partition to do it.
Hello I've haven't done any rooting or roms since the samsung s3 days. I was attempting to root my google pixel and when I wiped the phone in the TWRP recovery I made the mistake of ticking every box meaning the phone now has no os on it at all. I tried installing a factory rom from googles site but I only get an error saying the zip is an invalid file type.
Any help would be greatly appreciated.
I think,,,and I am not sure but if you wiped everything you will have to fastboot flash stock image then re-install TWRP and go from there.
Unzip the factory ROM zip on your computer, have the latest drivers and ADB/Fastboot installed/downloaded from Google's site, connect the phone in whichever mode it has to be in (Bootloader?) I forget but the information is plenty available in various threads here, there are only a couple of options anyway, then run the Flash-All.bat or .sh, depending on what OS you're running (Windows, Linux/Mac?).
If you can connect via MTP while in TWRP (if that's not wiped as well, or if you did if you haven't booted out of TWRP), then maybe you can copy the files over to flash a ROM and vendor image, and TWRP RC1 too so you can flash it again, although I would opt for starting back from scratch with the fully stock ROM/firmware flashed from a PC myself.
Flash the factory image and remain stock until you learn how to use recovery/restore a phone.
Sent from my Pixel using Tapatalk
Run flash all from PC to get back to stock. Then do a lot of reading.
Sent from my Pixel using Tapatalk
Hello,
My oneplus 9 is stuck on the boot loop. I tried to switch it on recovery mode and also tried to force restart but nothing seems to work. I don't want to wipe my whole data as I do not have the backup. Please help me with this issue if someone knows about it
you can get your device back up and running by flashing certain images from the stock rom through fastboot using a pc. I can't tell you exactly what you need to flash as I dont have this device. Maybe look for a tutorial of some sort. As far as I know, you need to flash all images except for data, (i.e. system, boot, recovery, and others). Don't take my word on that, as I haven't done it in a long time, and it varies depending on your device. Proceed at your own risk!