Related
Hello all,
I have been away for half a year and have just started using my G1 again. It had a real old version of CyanogenMod on it so I updated it a few weeks ago using the CM-Updater.
But over the last few weeks I have noticed that some things on the phone are not working as I want them too.
So I want to wipe everything and start again with a clean install of the latest CyanogenMod ROM.
So I downloaded the latest version, put it on my SD and booted up the recovery mode.
Then I did these items in this order:
Made a backup.
Repaired the file system.
Pressed Alt-W to wipe.
Applied the update.
However, upon bootup the phone is pretty much in the same state as before.
My question is how do I completely wipe the phone and start again? What would the steps be?
Thanks for the help in advance.
Sorry if a thread already exists for this. I honestly did have a good search for one.
Search for latest amon ra recovery for dream and flash the recovery image. the new recovery image gives u the ability to wipe every thing.
Thanks. Giving that a go as I speak!
Hi guys,
Hoping I can get some assistance here as I'm worried my tablet is buggered!
About 3 months ago I put cyanogen 9 (cm-9-20120616-p5wifi.zip) via Clockwork Recovery on my Galaxy Tab. It has been working perfectly since, however I charged it last night and when I powered it back up it seemed to be stuck in some sort of boot loop. It goes past the normal Samsung logo, gets halfway through the cyanogen animation and then hangs for a few seconds before restarting.
I have done some Googling and tried most things people have suggested in Clockwork Recovery, including a full wipe / factory reset, deleting /data, /system partitions, tried a restore etc.. This makes no difference at all.
One thing I did notice is that if I attempt to restore /system, I get "error while restoring /system".
I notice there is an Odin download mode that I can access. I have never really used the tool before but would I be able to use that to upload another image zip file?
TIA!
bigriggers
You might have to install a stock Rom to get past the bootloop. You would use odin to do that. Odin uses a .md5 file, not zip. You can get a stock rom at sammobile.com. you'll have to extract the .md5 file from the zip you down load. Use 7-zip to do that.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
I recently changed back my build.prop to the original one that i backed up before. Then my device cannot boot anymore. It is stuck in the ASUS splash screen when i boot the device.
Then I flash the latest CWM recovery. But even the latest version it cannot do anything like factory reset or flash zip.
After that, i tried to use the "wipe data" in the bootloader, it doesn't work either (still stuck in the splash screen).
And then i tried cold boot linux and it also doesn't work. Up to this point, I cannot find anyway to fix it.
However, I found that adb is somewhat working in CWM recovery. I tried "adb push build.prop /system/build.prop" (the build.prop is extracted from the US_epaduser_10_26_1_7_UpdateLauncher.zip package from ASUS official site), it doesn't work either.
I put the US_epaduser_10_26_1_7_UpdateLauncher.zip package from asus support site in sd card and tried to flash it by CWM recovery, it doesn't work either.
AFTER ALL THESE PROCEDURE, i think the system is corrupted because of some possible dirty wipe
IS THERE ANY WAY TO WIPE EVERYTHING AND RESET THE whOLE SYSTEM?
i feel like my device is completely dead... so i need help and solution asap
my device is unlocked, rooted, and updated to 10.26.1.7 android 4.3.
it is a US version.
btw i asked ASUS support and they said they would charge CAN$330 for fixing it (replacing the main board), which is.........
bruce2662 said:
I recently changed back my build.prop to the original one that i backed up before. Then my device cannot boot anymore. It is stuck in the ASUS splash screen when i boot the device.
Then I flash the latest CWM recovery. But even the latest version it cannot do anything like factory reset or flash zip.
After that, i tried to use the "wipe data" in the bootloader, it doesn't work either (still stuck in the splash screen).
And then i tried cold boot linux and it also doesn't work. Up to this point, I cannot find anyway to fix it.
However, I found that adb is somewhat working in CWM recovery. I tried "adb push build.prop /system/build.prop" (the build.prop is extracted from the US_epaduser_10_26_1_7_UpdateLauncher.zip package from ASUS official site), it doesn't work either.
I put the US_epaduser_10_26_1_7_UpdateLauncher.zip package from asus support site in sd card and tried to flash it by CWM recovery, it doesn't work either.
AFTER ALL THESE PROCEDURE, i think the system is corrupted because of some possible dirty wipe
IS THERE ANY WAY TO WIPE EVERYTHING AND RESET THE whOLE SYSTEM?
i feel like my device is completely dead... so i need help and solution asap
my device is unlocked, rooted, and updated to 10.26.1.7 android 4.3.
it is a US version.
btw i asked ASUS support and they said they would charge CAN$330 for fixing it (replacing the main board), which is.........
Click to expand...
Click to collapse
Since it seems that cwm works did you make nandroid backup before you started fiddling with the Rom? ( basic rule nr.1)
When not go to the boot loader screen and do a factory reset there (third icon from left).
But maybe you can do that also from within cwm but I do not know if it is in there.
The official update zip you must unzip that first and then put the new zip on the sdcard, can't do that from cwm.
Let it reboot and it must start flashing.
Snah001 said:
Since it seems that cwm works did you make nandroid backup before you started fiddling with the Rom? ( basic rule nr.1)
When not go to the boot loader screen and do a factory reset there (third icon from left).
But maybe you can do that also from within cwm but I do not know if it is in there.
The official update zip you must unzip that first and then put the new zip on the sdcard, can't do that from cwm.
Let it reboot and it must start flashing.
Click to expand...
Click to collapse
So is there any ways to fix it without sending it to asus repair ccenter?
I want to make sure that
1. The wipe data function in the bootloader works
2. Does wiping data in bootloader fix the build.prop problem
Or do anyone of you have any idea of solving tthis problem?
sorry for my bad english
bruce2662 said:
So is there any ways to fix it without sending it to asus repair ccenter?
I want to make sure that
1. The wipe data function in the bootloader works
2. Does wiping data in bootloader fix the build.prop problem
Or do anyone of you have any idea of solving tthis problem?
sorry for my bad english
Click to expand...
Click to collapse
Wipe data is like factory reset.
Unzip the firmware package and put the zip on your microSD. Then reboot and let it flash.
This way you get all a clean fresh install
Snah001 said:
Wipe data is like factory reset.
Click to expand...
Click to collapse
Sorry to disagree..
I would NOT wipe from the bootloader with a custom recovery installed! People have hard bricked their tablets that way!
Unzip the firmware package and put the zip on your microSD. Then reboot and let it flash.
This way you get all a clean fresh install
Click to expand...
Click to collapse
That works only with the stock recovery, not with a custom recovery. But you should be able to flash the once unzipped firmware in CWM. That would flash you back to stock, including the stock recovery.
Next time you install CWM your first action should be to make a nandroid.
If it doesn't work please explain why and what. Just "doesn't work" is not helpful - do you get error messages?
Explain - in detail - your steps.
Since you said you flashed CWM you do have fastboot access?
Forgot that you aren't on stock recovery.
When you still get into the recovery did you unzip the factory firmware zip before you tried to flash it?
First give that a try.
Volume-up + power pressed normally would get you into apx mode but since we have no Nvflash files available you can't do anything with that.
So unpack and put the factory firmware zip on you sdcard and flash from custom (think you have cwm installed) recovery (choose install and choose the file you put on your microSdcard).
Del msg
Hi I got an issue today with my TF701T can anyone help.
I got a prompt for installing an update, downloaded it, installed and on reboot the TF701T is stuck on the ASUS Splash screen.
How do you reset this device? I'm new to this TF701T
ToneyEricsson said:
Hi I got an issue today with my TF701T can anyone help.
I got a prompt for installing an update, downloaded it, installed and on reboot the TF701T is stuck on the ASUS Splash screen.
How do you reset this device? I'm new to this TF701T
Click to expand...
Click to collapse
There are a number of users with the same issue. Asus seems to have pushed an incompatible update to WW users (Man! They are really scre*** the release of this device! Unbelievable...)
Head over to the General section, there are a couple of threads dealing with this issue. The fix seems to be to wipe data and manually re-install the 10.26.1.7. (and ignore the update notifications you'll get again!)
But read the threads before you do so...
berndblb said:
There are a number of users with the same issue. Asus seems to have pushed an incompatible update to WW users (Man! They are really scre*** the release of this device! Unbelievable...)
Head over to the General section, there are a couple of threads dealing with this issue. The fix seems to be to wipe data and manually re-install the 10.26.1.7. (and ignore the update notifications you'll get again!)
But read the threads before you do so...
Click to expand...
Click to collapse
Sure buddy I will be reading xda before installing any updates from now on!!! Thats really bad ASUS pushed this update out that gets owners of the TF701T stuck on the Splash Screen after updating.
ToneyEricsson said:
Sure buddy I will be reading xda before installing any updates from now on!!! Thats really bad ASUS pushed this update out that gets owners of the TF701T stuck on the Splash Screen after updating.
Click to expand...
Click to collapse
Haha funny :cyclops:, same problem for the UK devices too (i see you´re from London?)? OMG!
I´m a german user and a bunch of peopole here also had this kind of issue after they did the last update from 4.3 to any newer release, since 27th dezember 2013 there´s no valid reply from ASUS and (for my understanding) the invalid software update is still on the servers and get sent to the EU users (...).
@ XDA: do you know, where i could find out the local storage where on my device the *.zip (or what ever) is saved, so that i could manually delete it? To make sure i´ll receive a newer one in future? Or did this (incorrect 250,8MB file) will be replaced by the newer one?
Regards
Silver
Try the root of your internal sdcard or in the download folder.
Sent from my Asus Infinity TF700 with Dock
where can i delete this file
Hi guys,
i've got the same issue, sent the device to the service and replaced a part of it, but because they've went over the 15 days period where they should have send it back ( fixed or not) I got a new one.
i updated to 4.3 and this time again i got prompted to install the crap update, but i didn't. Now i want to delete this file but i can't find it. if my kid or someone else will accidentally say OK to the update i'm back to older version ( at the best) .
so will be highly appreciated if anybody will provide a solution to remove this file.
thx
Snah001 said:
Try the root of your internal sdcard or in the download folder.
Sent from my Asus Infinity TF700 with Dock
Click to expand...
Click to collapse
xistentz said:
Hi guys,
i've got the same issue, sent the device to the service and replaced a part of it, but because they've went over the 15 days period where they should have send it back ( fixed or not) I got a new one.
i updated to 4.3 and this time again i got prompted to install the crap update, but i didn't. Now i want to delete this file but i can't find it. if my kid or someone else will accidentally say OK to the update i'm back to older version ( at the best) .
so will be highly appreciated if anybody will provide a solution to remove this file.
thx
Click to expand...
Click to collapse
It'll be on the cache partition, which you can only access from the stock recovery - you'll need to boot to nthe boot loader, choose rck and mess around with power and volume up / down until the menu appears. Then choose wipe cache. But it will come back when you next check for an update......
So I am able to flash dynamickat, hyperdrive, & jovy's deodex stock perfectly fine and they boot up normal and everything. However, when I try darthstalker or skyfall I get bootloops on both. They flash fine but I never make it past the boot animation. It'll be on for a few minutes and then reboot itself. I tried wiping data afterwards but nothing happens. I've downloaded the roms on different pcs, my phone, the md5 was correct, I flashed from my internal sd & external, I formatted everything (even my internal sd to see if that would help for some odd reason), I flashed a different kernel & I also odin'd back to stock and I still have no luck. I am on a t-mobile note 4 & twrp 2.8.1.1. I have no clue what to do anymore & this is becoming pretty frustrating
re: try this
xoxo_xdagirl91 said:
So I am able to flash dynamickat, hyperdrive, & jovy's deodex stock perfectly fine and they boot up normal and everything. However, when I try darthstalker or skyfall I get bootloops on both. They flash fine but I never make it past the boot animation. It'll be on for a few minutes and then reboot itself. I tried wiping data afterwards but nothing happens. I've downloaded the roms on different pcs, my phone, the md5 was correct, I flashed from my internal sd & external, I formatted everything (even my internal sd to see if that would help for some odd reason), I flashed a different kernel & I also odin'd back to stock and I still have no luck. I am on a t-mobile note 4 & twrp 2.8.1.1. I have no clue what to do anymore & this is becoming pretty frustrating
Click to expand...
Click to collapse
I have read your posts in the development thread about the issue you are having.
Give this a try
#1: Do a full wipe including Wipe System, Data, Cache, Dalvik and
last but not least to a factory reset in twrp recovery.
#2: Flash Jovy23's, stock rooted deodexed rom again.
#3: Copy Darthstalker zip file rom to your computer's desktop.
#4: Open Darthstalker zip file rom and remove/delete "boot.img"
from the zip file using winrar or winzip (or other archiver).
#5: Once "boot.img" is no longer in the Darthstalker zip file rom
copy it back to your phone's internal sdcard.
#6: Flash the Darthstalker zip file rom but do NOT wipe anything this time.
If this works for you then that means that for whatever reason your
phone has issues with the original kernel file (boot.img) which was in
the darthstalker zip file before you removed/deleted it,.
Doing it using the above step by step you will be using the kernel (boot.img)
from jov23's stock rooted rom.
If it works for you can open jovy23's stock rooted zip file rom and copy
the boot.img from it to your desktop then close the zip file.
Then open darthstalker zip file rom and copy jovy23's stock boot.img
from your desktop into darthstalker zip file rom.
The darthstalker zip file rom which has no boot.img in it since you have
already deleted and removed it.
Then copy the modified darthstalker zip file rom into your internal sdcard
over-writing the one already there.
Then if you like you can do a full wipe again and flash the modified
darthstalker zip file rom which has jovy23's kernel (boot.img) in it
and it should work fine.
Good luck!
xoxo_xdagirl91 said:
So I am able to flash dynamickat, hyperdrive, & jovy's deodex stock perfectly fine and they boot up normal and everything. However, when I try darthstalker or skyfall I get bootloops on both. They flash fine but I never make it past the boot animation. It'll be on for a few minutes and then reboot itself. I tried wiping data afterwards but nothing happens. I've downloaded the roms on different pcs, my phone, the md5 was correct, I flashed from my internal sd & external, I formatted everything (even my internal sd to see if that would help for some odd reason), I flashed a different kernel & I also odin'd back to stock and I still have no luck. I am on a t-mobile note 4 & twrp 2.8.1.1. I have no clue what to do anymore & this is becoming pretty frustrating
Click to expand...
Click to collapse
When I built the N4 rom, I was having serious qmg boot animation issues, I disabled them, and the rom booted normal, we may have a issue with the new roms and the animations. Just a thought.
re:
AxAtAx said:
When I built the N4 rom, I was having serious qmg boot animation issues, I disabled them, and the rom booted normal, we may have a issue with the new roms and the animations. Just a thought.
Click to expand...
Click to collapse
If that's the case then perhaps it might be a good idea for her to
remove all the qmg files in the system/media folder just to see
if it resolves her bootloop issues before trying anything else.
(I have not had any bootloop issues)
But then why don't all the users of the rom have the bootloop issue?
Misterjunky said:
If that's the case then perhaps it might be a good idea for her to
remove all the qmg files in the system/media folder just to see
if it resolves her bootloop issues before trying anything else.
(I have not had any bootloop issues)
But then why don't all the users of the rom have the bootloop issue?
Click to expand...
Click to collapse
Thanks for trying to help! I did what you said and flashed the stock rom but got an error when flashing darthstalker afterwards when I removed the boot.img but I still went ahead and added the boot.img from the stock rom to to the darthstalker zip and that didn't work. Still bootloops. And that's what I don't understand how it works fine on everyone else's phone and not mine I mean it's not all roms but it's still very weird and I want to know why it's happening. On another note when I do flash the stockrom, hyperdrive, & dynamickat right before it boots I get android system upgrading.. optimizing app 200 out of 200 or so, does that happen with anyone else? is that suppose to happen? does that happen on darthstalker or skyfall?
re: updating apps
xoxo_xdagirl91 said:
Thanks for trying to help! I did what you said and flashed the stock rom but got an error when flashing darthstalker afterwards when I removed the boot.img but I still went ahead and added the boot.img from the stock rom to to the darthstalker zip and that didn't work. Still bootloops. And that's what I don't understand how it works fine on everyone else's phone and not mine I mean it's not all roms but it's still very weird and I want to know why it's happening. On another note when I do flash the stockrom, hyperdrive, & dynamickat right before it boots I get android system upgrading.. optimizing app 200 out of 200 or so, does that happen with anyone else? is that suppose to happen? does that happen on darthstalker or skyfall?
Click to expand...
Click to collapse
The upgrading apps is NOT supposed to happen or appear at all unless you have NOT done a FULL
and complete wipe before flashing.
It's normal for it to upgrade a lot of apps during boot if you decided or have not done a full and
complete wipe which includes Factory Reset, Wipe System, Data, Cache and Dalvik cache.
In your case you need to do a full and complete clean flash and the only way to do that is by doing
a full and complete wipe.
If you keep seeing the "updating apps" after flashing any rom it means you have not done a full wipe.
When you have finally done a full and complete wipe before flashing you will no longer see the
phone doing the "upgrading apps" counting the number of apps to be upgraded during bootup
at all when the phone is actually wiped clean before flashing any roms.
(I am assuming that you're using twrp recovery to wipe and flash roms).
Good luck!
Misterjunky said:
The upgrading apps is NOT supposed to happen or appear at all unless you have NOT done a FULL
and complete wipe before flashing.
It's normal for it to upgrade a lot of apps if you decided or have not done a full and complete wipe
including Factory Reset, Wipe System, Data, Cache and Dalvik cache.
In your case you need to do a full and complete clean flash and the only way to do that is by doing
a full and complete wipe.
If you keep seeing the "updating apps" after flashing any rom it means you have not done a full wipe.
When you have finally done a full and complete wipe before flashing you will no longer see the
phone doing the "upgrading apps" counting the number of apps to be upgraded during bootup
at all when the phone is actually wiped clean.
Good luck!
Click to expand...
Click to collapse
I am doing a full wipe though?
Before MM I was already having issues with my LP install. Lockups, crashes, etc.. I had planned on performing a fresh install of my LP ROM yesterday but was excited to see that MM was released. I was hoping that installing MM over LP would fix the issue that I was experiencing. No dice.
So, is it possible to go into TWRP, perform a factory reset (including erasing Internal Storage) and then booting into Download Mode so I can install MM fresh using Odin? Is there anything that I need to know of or missing before performing this procedure? I can then reinstall TWRP and root afterwards. I just want a fresh install and can't wait two or three days for a Flashable Zip. My system is just too unstable in its current form.
Thanks.
JC
For The Record
This is exactly what I just did. It works perfectly and now my phone is back to operating normally. And with a clean install of 6.0.1 to boot!
Now....time for TWRP and Root........
What is safe to wipe in TWRP? I did an install of MM for the 910T stock rom and unfortunately tried the encryption. I thought it would give me the option to decrypt, but that is not the case.
Wipe
Mister_E105 said:
What is safe to wipe in TWRP? I did an install of MM for the 910T stock rom and unfortunately tried the encryption. I thought it would give me the option to decrypt, but that is not the case.
Click to expand...
Click to collapse
I wiped EVERYTHING in TWRP. Powered off the phone and then booted to Download Mode. From there I pushed out a fresh copy of MM using Odin. It flashes a new stock recovery. After the phone boots up go back into Download Mode and flash TWRP using Odin. Then you can flash Beta SuperSU in TWRP for root.
But.....I wanted to follow up on this post. My Note 4 started experiencing issues last week. I was hoping a fresh OS install would fix things. Unfortunately for me during a power off to go into recovery to flash SuperSU I received the dreaded mmc_read failed error. The phone is nearly two years old and I have never seen the bug on my device. I had thought that I was one of the lucky early purchasers. I was wrong.
The device got worse and worse. To the point that now it rarely boots at all. It just sits at the "Samsung Note 4" screen. I can't even get into TWRP reliably. And the mmc screen is popping up more frequently now as well.
I had no choice but to stop by T-Mobile yesterday and (reluctantly) buy a S7 Edge. I say reluctantly for two reasons. 1. The Note 7 comes out in barely over a month 2. There is no known root for S7 (and Note 7 will probably be the same)
I have 30 days to decide if this phone is for me or not. Not having root is something that I never thought I'd have to live with. Barring some unforeseen circumstance I thought I'd have the Note 4 for a couple more years. And I didn't have the time to look for a used one as I needed a phone immediately.
Fingers crossed they get this thing roooted because it really is a pretty sexy device!
I found that the only way to clear the encryption was to load the stock recovery, it had the power to wipe the partitions and allow a clean install.