Database Develop

[Q] Start from Scratch....

I have flashed my Hero with many ROMS, mostly the Cyanogen nightly's. I have seen recently a huge lag no matter which build I use. I think there may be a corrupt file left behind that is causing the problems.
How can I erase everything and start completely from scratch? I have already done a wipse and re-imaged from there and it doesn't seem to help.

Run the officail RUU, then re-root again. that is all you need to do.
Sent from my HERO200 using XDA App

fowen said:
I have already done a wipse and re-imaged from there and it doesn't seem to help.
Click to expand...
Click to collapse
What all did you wipe? Make sure to wipe everything. You shouldn't have to go back to an official Sprint ROM and reroot. Just wipe everything and reflash the ROM you want.

ranger61878 said:
What all did you wipe? Make sure to wipe everything. You shouldn't have to go back to an official Sprint ROM and reroot. Just wipe everything and reflash the ROM you want.
Click to expand...
Click to collapse
I tried to wipe everything but I got errors asking me to do it through ADP. Since I am a newb with all of this I was hoping there was an easy way to do it.

fowen said:
I tried to wipe everything but I got errors asking me to do it through ADP. Since I am a newb with all of this I was hoping there was an easy way to do it.
Click to expand...
Click to collapse
If you are using the Amon Recovery v1.5.2, it does actually wipe everything even thought it gives you that 'run via adb' nonsense. It's just a small error/bug in that version of recovery that doesn't output the correct string of text, but the wiping part does work correctly and it does actually wipe Dalvik, data, ext, etc. even though the output tells you something else.
As said above, you need to wipe ALL of those (except battery) every time you flash a new ROM, or else it can lead to some corruption like you are experiencing. If still unsatisfied or if you still can't get things to work, then rerun the official RUU as also suggested above to start fresh. But I will tell you that I've never had to rerun the RUU before in the entire 6 months I've been rooted, so I think your problem is maybe just incorrect procedure between wiping and flashing ROMs. All phones are different though. Good luck, and please keep posting so we can continue to help you out.

fowen said:
I tried to wipe everything but I got errors asking me to do it through ADP. Since I am a newb with all of this I was hoping there was an easy way to do it.
Click to expand...
Click to collapse
What recovery are you using? Anyways, the RUU wipes everything, no need to wipe beforehand, see this to RUU

I haven't flashed many types of ROM's, only a few. I have been sticking with Cyanogen Mod I would say 90% of the time. I cleared out everything and it didn't seem to help much.
Most of the time it lags when I am dealing with email, or a email comes in. Last week I got tired of it and OC'd it up to 768 and I saw a huge difference but my battery died after 6 hours. Even with the CPU clocked to 768 I can notice a huge difference when I have a email coming in.
I just flashed to Cyanogen's newest nightly to see if there are any differences. If not, I will try to un-root and flash directly to Cyanogen's rom. Will I need to clear everything before going to a new rom from stock?

I am trying to flash back to Stock and I received an error basically saying the bootloader was wrong. It appears this happens when you are trying to go backwards. I am trying to go from CyanogenMod 6.1 (Froyo) to the stock 1.5 build. Is this not what i am supposed to do?

fowen said:
I am trying to flash back to Stock and I received an error basically saying the bootloader was wrong. It appears this happens when you are trying to go backwards. I am trying to go from CyanogenMod 6.1 (Froyo) to the stock 1.5 build. Is this not what i am supposed to do?
Click to expand...
Click to collapse
Assuming you mean going back to pre-root, right out of the box state...you need to run the official RUU from your computer, not via recovery.

Yes, I am trying to go to a pre-rooted state.
I tried that, and it could never detect my android phone. I googled the error message and someone said to try it from the fast boot mode. I rebooted my phone into this and re-ran the update. It got further along but it came up with this error message along the way.

fowen said:
Yes, I am trying to go to a pre-rooted state.
I tried that, and it could never detect my android phone. I googled the error message and someone said to try it from the fast boot mode. I rebooted my phone into this and re-ran the update. It got further along but it came up with this error message along the way.
Click to expand...
Click to collapse
You are using HTC Sync and have the USB drivers installed?
----------
Sent from the XDA App on my FroYoed Sprint Hero...so forgive my inevitable typos

Sounds like a driver issue. Also make sure you have USB debugging on, otherwise adb will not recognize your device.
I've run across issues with loose fragments of data being left after a wipe via recovery. My favorite was the home key ceasing to work. A full wipe via fastboot always seems to do the trick. Just make sure you have a copy of your recovery image to reflash when done. You'll need the ENG SPL as well.
You'll do this all via adb.
In bootloader:
fastboot erase system -w
fastboot erase boot
fastboot boot your_recovery_image.img
adb shell mount /sdcard
adb push your_recovery_image.img /sdcard/your_recovery_image.img
adb shell flash_image recovery /sdcard/your_recovery_image.img
adb shell reboot
Just make sure your recovery image is on the root of your sdcard. Full wipe in minutes without that long ruu process! I've been doing this every time I flash a new ROM lately, never an issue.

Trying to restore Steak 7 Wifi to stock, need help quick!

I need to return it to stock before returning it, and I've got less than a week to do so. I've tried so many different methods and files, and the closest I've gotten is a stock/factory reset (with the original setup screen) with a root with Clockwork Recovery (CWR) installed.
I can't use the method in this thread, since this is for the T-Mobile version, and removing the T-Mobile apps and bootscreen would require my rooting it, which would put me back at square one:
http://forum.xda-developers.com/showpost.php?p=12590019&postcount=1
I did find a Wifi version of it in this post, but after flashing it multiple times (once after botching a recovery flash and being unable to boot into it), I think I found out that it's already rooted with CWR installed:
http://forum.xda-developers.com/showpost.php?p=14303822&postcount=3
And then I tried using this method (along with simply using fastboot to flash the stock recovery from the first link), and every time either CWR still came up, or no recovery came up and it simply booted into the OS when I tried to do the update or full factory reset option:
http://forum.xda-developers.com/showpost.php?p=12355315&postcount=1
EDIT: I also found this method looking through the boards, but sadly the files are also for the T-Mobile version:
http://forum.xda-developers.com/showpost.php?p=12453284&postcount=1
(I can't even access the flash_image file needed because the link is invalid)
Any help? I'd rather not return the Streak in its rooted state, even if it looks stock. If all else fails...I'll just use the method in link 2 to restore it, since at least it looks stock when it first boots up...

use the t-mobile method but the WI-FI only files instead of the t-mobile ones, then when you are back to stock get gingerbreak 1.20 and unroot it (this might be optional) then root it and then unroot it again, it gets rid of CWM and Superuser. It is completely at stock for me now.
also I used fastboot to flash the stock recovery before I used gingerbreak, I don't know if that helped or not but just to be on the safe side.

shadowswithin said:
use the t-mobile method but the WI-FI only files instead of the t-mobile ones, then when you are back to stock get gingerbreak 1.20 and unroot it (this might be optional) then root it and then unroot it again, it gets rid of CWM and Superuser. It is completely at stock for me now.
also I used fastboot to flash the stock recovery before I used gingerbreak, I don't know if that helped or not but just to be on the safe side.
Click to expand...
Click to collapse
I'll try that now, I'll post how it turns out. I tried using Gingerbreak to unroot earlier, but didn't think it would work since it just rebooted with no changes.
EDIT: Seems to work so far, I need to recharge before I can use the update or full reset options in the recovery and see if CWR is truly gone, but in any case, thank you so much, finally got it stock and unrooted.

Well, I tried what you said, and while I was able to remove the root through Gingerbreak, and I flashed the stock recovery through fastboot both before and after unrooting...CWR still came up. Tried rooting and unrooting it again, flashing the stock recovery through fastboot before and after unrooting again...CWR still came up.
I think I'll just give up and return it the way it is, I did a factory reset through CWR and turned it off (testing it once before that to make sure the setup screen would show and Superuser wasn't installed), I doubt anybody is going to notice anyway.

magus57 said:
Well, I tried what you said, and while I was able to remove the root through Gingerbreak, and I flashed the stock recovery through fastboot both before and after unrooting...CWR still came up. Tried rooting and unrooting it again, flashing the stock recovery through fastboot before and after unrooting again...CWR still came up.
I think I'll just give up and return it the way it is, I did a factory reset through CWR and turned it off (testing it once before that to make sure the setup screen would show and Superuser wasn't installed), I doubt anybody is going to notice anyway.
Click to expand...
Click to collapse
I'm in a similar situation. I tried DJ Steve's Honeystreak, got back to stock 2.2.2 but it was still rooted. Went the Gingerbreak route to unroot, root, then unroot again. Tried to flash stock update.pkg from Dell website and it booted into CWR. I would try to flash the recovery image using fastboot but 1) I don't have the recovery image and have never used fastboot and 2) it doesn't look like it would work even if I tried according to your results.

I got rid of cwr following by just following the recovery flash steps here, http://forum.xda-developers.com/showthread.php?t=1011654 nothing more and it was done.

jayfr76 said:
I got rid of cwr following by just following the recovery flash steps here, http://forum.xda-developers.com/showthread.php?t=1011654 nothing more and it was done.
Click to expand...
Click to collapse
I tried that as well, still has CWM, but I'm stuck in DELL logo loop. Can't flash anything successfully and can't boot into OS. Was up until 5am trying everything I read in the threads. Nothing. Everything I try gives me no errors, that's the wierd bit. All I need to do is break through the boot loop.

jayfr76 said:
I got rid of cwr following by just following the recovery flash steps here, http://forum.xda-developers.com/showthread.php?t=1011654 nothing more and it was done.
Click to expand...
Click to collapse
I tried the files from that thread, but they are for the t-Mobile version, not the wifi only version. Does anybody know where we can find a stock wifi only recovery image?

bimbot said:
I'm in a similar situation. I tried DJ Steve's Honeystreak, got back to stock 2.2.2 but it was still rooted. Went the Gingerbreak route to unroot, root, then unroot again. Tried to flash stock update.pkg from Dell website and it booted into CWR. I would try to flash the recovery image using fastboot but 1) I don't have the recovery image and have never used fastboot and 2) it doesn't look like it would work even if I tried according to your results.
Click to expand...
Click to collapse
Yeah, I wouldn't bother, doubt it'd work for you if it didn't work for me the however many times I tried it.
And if you've ever done anything in adb with the Android SDK, fastboot is similar - basically, you hold volume (-) and power, wait to get into fastboot, plug it into the computer, and use:
fastboot flash recovery recovery.img
to flash to the recovery. That also works for boot and system.
Bigirish said:
I tried that as well, still has CWM, but I'm stuck in DELL logo loop. Can't flash anything successfully and can't boot into OS. Was up until 5am trying everything I read in the threads. Nothing. Everything I try gives me no errors, that's the wierd bit. All I need to do is break through the boot loop.
Click to expand...
Click to collapse
Try doing the NVFlash method in APX mode, it's pretty much guaranteed to work. It's the method in the first link in my original post, and the files for the Wifi version are in the second post (extraded, the .rar file is like 14GB's, you only need the images p2 though p14 to flash). You'll still have root and CWR, but at least you'll be out of the boot loop and you'll still be able to at least remove root with Gingerbreak.

[Q] stuck in broken recovery mode

Hi everyone
First of all a little history:I used this [PhilZ-cwm6][n7000] v4.93.6 Safe Stock Kernel+CWM6+Root+exFAT+ext4-LT4 to root my n7000 on 4.0.4 (I bought it with 4.0.4).
Then after some time Android wanted an upgrade to 4.1.2 and after some time I just tried it and it failed after booting into recovery mode, because it didnt find a the expected kernel, I think. But I had the chance to boot up again.
OK I then did the update with Kies-Software and everything worked again. Then I rooted the phone again using the same method as mentioned in the post above.
Now today the phone wanted to update again, I thought, OK, if it didnt fail completely the first time, it will fail in recovery mode and let me boot up again.
But...
This time it went into recovery mode and didnt let me boot up again. It just shows the robot with the crystal and the progress bar seems to move a little but then the screen goes black for a second and the robot returns and the progress bar moves a little and the same again.... I dont get into the recovery menu.
I tried samsung kies emergency recovery, it doesnt find my n7000.
I tried to flash the kernel with a newer version from the post above. (I am not allowed to post there). No change it gets stuck in broken recovery mode.
I can push volumedown power and home to get into the download mode.
My question is what can I do?
Is there any other chance to avoid a complete stock recovery (is that the right term/way)?
What do I have to flash and how?
I am a little worried about the brick issues and I dont know which version I have to flash to set it back completely...
Please help & thanks
drz

No worries, since your download mode is still working you can flash a stock Samsung ROM via odin. Download one from here and flash it in odin while in download mode. Latest at this point of time is LT4 http://forum.xda-developers.com/showthread.php?t=1424997
This will give you the stock JB Bootloader, Recovery, and ROM. Its completely unrooted though, and the phone will not be wiped in the process, so remember to do so after you flashed it.

cr0wnest said:
No worries, since your download mode is still working you can flash a stock Samsung ROM via odin. Download one from here and flash it in odin while in download mode. Latest at this point of time is LT4 http://forum.xda-developers.com/showthread.php?t=1424997
This will give you the stock JB Bootloader, Recovery, and ROM. Its completely unrooted though, and the phone will not be wiped in the process, so remember to do so after you flashed it.
Click to expand...
Click to collapse
Thanks a lot, crownest!
I sweated a bucket of blood and seat, because I couldnt wipe cache and data first, but it worked!!!
Everything looks like before!´the update!
Some more questions (sorry):
do you think I should wipe cache and data now?
Is a stock rom like the rom on internal usbcard only?
What about the update? Can I update safely now?
Thanks again for helping...
greetz
drz

Yup you should be able to wipe cache and dalvik with no issues now.
I believe all ROMs be it stock or custom installs to the NAND memory (Someone correct me if im wrong) and never on your internal/external SDcard
As for OTA updates via Kies, I dont see why not, but if the same issue does reoccur again then my suspicions would point to a possible NAND corruption on the device. Not sure if there is a fix for that, but its a risk you gotta take. Or you can always root the phone and flash custom ROMs as new builds get released, this way you'll never have to use OTA updates again.

[Q] [URGENT] Need Help For my DEAD TF701

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......

Your phone is bootlooping after flashed firmware? Read this. [Tested on A6+ (A605GN)]

Hello everyone, I'm here to share with you guys a solution that saved my life last night.
Well, as a good user, I tried to root my phone and I got it, but the screenlock wasn't working as you guys should know, then I tried to go back to stock and wait 'til someone fix that problem, but when I flashed Stock through Odin, my phone began to bootlooping after Samsung's logo and apperently there was no reason for it to do that, but I got a lot of erros, like:
No data access (Argument invalid);
Modem error (auth), etc.
Well, what I did was just flash TWRP through odin, formatted /data and then I flashed the official recovery and firmware again.
Hope that helps!

iRomulls said:
Hello everyone, I'm here to share with you guys a solution that saved my life last night.
Well, as a good user, I tried to root my phone and I got it, but the screenlock wasn't working as you guys should know, then I tried to go back to stock and wait 'til someone fix that problem, but when I flashed Stock through Odin, my phone began to bootlooping after Samsung's logo and apperently there was no reason for it to do that, but I got a lot of erros, like:
No data access (Argument invalid);
Modem error (auth), etc.
Well, what I did was just flash TWRP through odin, formatted /data and then I flashed the official recovery and firmware again.
Hope that helps!
Click to expand...
Click to collapse
probably during flash with odin you chose Home_csc_omc..... and all phone's data still intact/untouch. that's why need to wipe data in TWRP.
if since the first place you chose csc_omc without HOME label... thats mean you do the clean flash and all will fine no need format data in TWRP.
just my thought..