Related
I know this question has been asked by many people in many ways, but I am lost and would appreciate your help.
To make a long story short, I have a TF101 which keeps going into CWMD no matter what I do. I cannot cold boot it through to the OS. I have tried several solutions to get the device working again including:
http://theunlockr.com/2011/11/28/how-to-unroot-and-remove-cwm-recovery-on-asus-transformer/
Attempting to flash the stock ROM straight from the ASUS website
http://www.blogotechblog.com/2012/02/how-to-install-rooted-stock-ics-rom-on-eee-pad-transformer
NOTHING is working right! I have a complete backup of apps and data using Titanium and I just want a clean, rooted machine to start from. What is the most sure fire way to do this?
Undying gratitude in advance!
John
How about some basic information?
What did you last do before this started happening?
What version of CWM do you have?
I tried to do the OTA update after temporarily rooting the device with OTA Rootkeeper
I am using v 5.5.0.4
Does cwm even see anything that you can flash if you choose "choose zip from sdcard"? If it does, this might help, but you will probably have to push it with adb... http://forum.xda-developers.com/showthread.php?t=1552303
Search around for hints on using adb, there are guides and freaky ways to install drivers to get it to work.
I managed to use a rooted rom to get it to boot up (one that you did at http://forum.xda-developers.com/showthread.php?t=1552303). And now have the following issues:
The ROM does not have either Market or Google Play. so I can't install things like ROM manager and Titanium
The system is acting "modally" - essentially requiring that I completely exit an application before i enter another one. So in order to use another app, I have to completely back out of the one I'm in.
Even though the ROM is running the latest update, the system is prompting me to load the OTA update anyway.
Flash Gapps
Sent from my Transformer TF101 using xda premium
Can't seem to flash anything now. Least not from the computer or the OS. I'm stuck with CWMOD 3.2.0.1 roach2010-tf101-r1. It won't cold boot. ADB recognizes the unit in recovery mode but I have to assume that the entire OS is buggered. I can't even do a device wipe without an error. I think I have to get it back to "factory" via ADB, but I haven't found a clear and reliable set of instructions.
Melting....melting!!!
just use the one click root tool by kennethpenn, work perfectly thanks. use titanium back to do a backup of all the app and system then took out all the att bloatware. i have few questions at this point.
1.
will i be able to get OTA updates from att? what will happen to all the bloatware that i deleted? would they appear again?
2.
what happens if i do a factory reset on the phone? would i brick the phone? under normal condition that will erase all apps i installed and return it to factory setting, that means all the att bloatware will be back? will i lost root?
3.
what other things i can do after i root the phone at this point?
thank you for your help
no one can help me with those questions??? anyone???
i am sure a lot of people have the same question.
1.
will i be able to get OTA updates from att? what will happen to all the bloatware that i deleted? would they appear again?
I'm not 100% sure on this, but as long as you're running an actual AT&T ROM (not an Asian or Rogers ROM), you'll be notified of the OTA's. Now, if you're not using the stock Recovery image (that is, if you've installed CWM Recovery), you won't be able to apply the update. OTA updates get applied via the stock Recovery image.
2.
what happens if i do a factory reset on the phone? would i brick the phone? under normal condition that will erase all apps i installed and return it to factory setting, that means all the att bloatware will be back? will i lost root?
If you do a factory reset from CWM or within the phone's UI, you're fine. Root will remain in place, and you won't brick it. It just clears the user data from the phone, and should leave "sdcard" intact. However, I'm not 100% sure what happens if you do a factory reset from the bootloader. So just don't do it that way, unless someone else can confirm that it's okay.
3.
what other things i can do after i root the phone at this point?
You ca use apps like AutoKiller to change your memory management, for one. That's about all I'm doing with root right now. If we ever get custom kernels, you'll be able to overclock your CPU. If you search the Play Store for "root," you'd doubtlessly find some other root apps that you may be interested in.
Hope this helps!
Don't ever ever ever install an OTA on any rooted Android device. At the least, it won't work anyway, or you will lose root. At the worst, you will be stuck in a bootloop. Updated ROMs (based on the OTA's, but rooted, and safe to flash) usually get posted in Development soon after the OTA's go out. That is what you want to install.
craig0r said:
However, I'm not 100% sure what happens if you do a factory reset from the bootloader. So just don't do it that way, unless someone else can confirm that it's okay.
Click to expand...
Click to collapse
I can confirm that it's OK. My phone was rooted and stuck in a boot loop. I did a factory reset. It was reset and still rooted after the fact. So you can do it.
thank you all
redpoint73 said:
Don't ever ever ever install an OTA on any rooted Android device. At the least, it won't work anyway, or you will lose root. At the worst, you will be stuck in a bootloop. Updated ROMs (based on the OTA's, but rooted, and safe to flash) usually get posted in Development soon after the OTA's go out. That is what you want to install.
Click to expand...
Click to collapse
Just to clarify, pre-rooted versions of the official ROMs (which often get posted on XDA, as I mentioned) may need unlocked bootloader to install, so this will possibly not be an option for a while. Although there may be alternate safe ways to update (but not OTA). For instance, a leaked 1.83 firmware version is already available as an RUU in the Development subforum. Apparently, its okay to install via RUU, then re-root.
In general, the safe thing to do is to read up on here when updates are released, and see if there is a safe way to update on a rooted phone.
All,
See that the new AT&T update for the 850 G3 came out...I'm currently rooted via towelroot and nothing else. Tried downloading the update, rebooted, installing process and failed. Said I was rooted. Booted me back to normal. Anyway to unroot myself without wiping everything?
Nope, you pretty much have to flash back to stock via the top file which will wipe EVERYTHING including the internal storage. The better question is why do you want the att update. If you are absolutely desperate you can try the root cloak xposed module, that may or may not trick the updater into attempts to flash but may also brick your phone.
I just tried this and it didn't work. I the below method last night but the LG Flash Tool keeps failing and giving me the error "cannot change to download mode". I saw there were some issues when using Windows 8 so I"m going to try and put Windows 7 on my old laptop and try again. If not I will try another computer with Windows 7 already installed.
http://forum.xda-developers.com/att-lg-g3/general/unroot-return-to-factory-stock-att-lg-g3-t2820827
I updated my Oneplus One manually to the newest Version of CM12s. While flashing it, my Recovery (TWRP) chrashed. So to be sure I installed my freshly performed Nandroid Backup. But nothing helped. I couldnt connect with the Wifi, no SIM Cards were found, no Bluetooth Connectivity and it had Random Reboots. So i decided to flash back to Stock CM11s (the first ever released). But the Problems were the same afterwards. I flashed the Stock image via ADB and, after I found out nothing changed, via the Oneplus One Toolkit, but the Problems were still there. I also made a video on Youtube to show what happens and i hope that i can repair it and must not send it back to repair, because a repair would cost me up to 300€. So pls tell me a way to fix this Problem, because I really like this Phone:crying::crying::crying:
For the video search "Oneplus One not working" by the User "axel thegamer"
AxelWexel said:
I updated my Oneplus One manually to the newest Version of CM12s. While flashing it, my Recovery (TWRP) chrashed. So to be sure I installed my freshly performed Nandroid Backup. But nothing helped. I couldnt connect with the Wifi, no SIM Cards were found, no Bluetooth Connectivity and it had Random Reboots. So i decided to flash back to Stock CM11s (the first ever released). But the Problems were the same afterwards. I flashed the Stock image via ADB and, after I found out nothing changed, via the Oneplus One Toolkit, but the Problems were still there. I also made a video on Youtube to show what happens and i hope that i can repair it and must not send it back to repair, because a repair would cost me up to 300€. So pls tell me a way to fix this Problem, because I really like this Phone:crying::crying::crying:
For the video search "Oneplus One not working" by the User "axel thegamer"
Click to expand...
Click to collapse
Can't find your video, can you paste the link as text?
gsmyth said:
Can't find your video, can you paste the link as text?
Click to expand...
Click to collapse
i cant, because i made a new account here.
just search "oneplus one not working", then set "filter" on today and you will find it
AxelWexel said:
i cant, because i made a new account here.
just search "oneplus one not working", then set "filter" on today and you will find it
Click to expand...
Click to collapse
Ok found your vid, I see you have flashed the stock image files via ADB, have you done a full factory reset (wiping data) from the phone/TWRP? Its a bit worrying that flashing the stock image files didnt sort the issue. As it seems to be WiFi on/off that causes the reboot it would make me think it was to modem/radio but this should have been written again when you flashed the stock images.
@AxelWexel can you check in your Settings>About phone menu if your IMEI number is showing? Just in case your EFS has become corrupted. It definitely sounds fixable as if something has corrupted and needs wiped fresh.
EFS fix:
http://forum.xda-developers.com/oneplus-one/general/fix-people-corrupt-efs-mobile-data-t2836389
Also worth a shot, fixing corrupt partitions guide in ADB:
http://forum.xda-developers.com/oneplus-one/general/guide-identifying-fixing-corrupted-t2993500
gsmyth said:
Ok found your vid, I see you have flashed the stock image files via ADB, have you done a full factory reset (wiping data) from the phone/TWRP? Its a bit worrying that flashing the stock image files didnt sort the issue. As it seems to be WiFi on/off that causes the reboot it would make me think it was to modem/radio but this should have been written again when you flashed the stock images.
@AxelWexel can you check in your Settings>About phone menu if your IMEI number is showing? Just in case your EFS has become corrupted. It definitely sounds fixable as if something has corrupted and needs wiped fresh.
EFS fix:
http://forum.xda-developers.com/oneplus-one/general/fix-people-corrupt-efs-mobile-data-t2836389
Also worth a shot, fixing corrupt partitions guide in ADB:
http://forum.xda-developers.com/oneplus-one/general/guide-identifying-fixing-corrupted-t2993500
Click to expand...
Click to collapse
Thx for the Links and i tried to watch on my phone and there is no imei number. I also did a full wipe after i found the issues. I also tried it via the Toolbox to flash the stock rom back but it hadnt change anything. But I will look the links you postet and reply if anything has changed. But now thx again:good:
P.S: I renamed the Video to "Oneplus One not working (23.06.2015)" to find it more easily
Edit 1: The Second Link with fixing corrupt partitions via adb wont work for me because i dont have root but my bootloader is unlocked. so i cant find the root acsess for adb in the developer options
Edit 2: I installed color os like the link said, done everything it said, but still no wifi, bluetooth and no sim card detection:crying:. Luckily the random reboot stopped Could you again help me further more because it seemed to help
Edit 3: I went back to cm11s, because in color os when i turned the phone off it turned on again, the connectivity was not there. After the install it became worse with the random reboots. I think i must send it to repair and pay 300€:crying::crying::crying::crying:
Galaxy s8 on Verizon, a standard update notice kept appearing past few days, finally installed it. The minute it finished, it is now in an endless restarting loop. The phone does unlock and show my homescreen. I can get into it, but I only get about 10 seconds to do stuff then it freezes/restarts. Tried Clear Partition Cache in the recovery mode. Tried Safe Mode. No luck.
When I rush over to Settings>Software Update, and click it, it says "Software update in progress"....so it makes me think it is the remnants of the new software update completing itself, and that causes the rebooting. The final stages perhaps? Is there a way to CEASE that the second I unlock my phone? To stop all the background stuff.
Or maybe wouldnt make a difference. Any ideas besides factory reset? Way to revert back?
Wanted to backup a few recent pictures first.
A factory reset is the last resort to fix this.
Maybe it's theme related. Try toggling the button layout (settings -> display -> navigation bar) a couple of times.
If you have substratum installed, try disabling it.
If you want to back up your pictures;
Have you tried accessing the phone using a computer? Either just through a file explorer or by using ADB? To use ADB, you may need to get into settings -developer mode
I tried plugging into a computer, but I only have about 10 seconds, so I dont get enough time to access the files. I get into the phone drive on windows Samsung Galaxy>DCIM> CAMERA> ...then it reboots.
Developer mode is already enabled. Can ADB be used while on the recovery mode screen? I can access that command line looking screen as long as needed.
But accessing the phone normally like turning it on and unlocking the screen would not work, I would keep losing the connection when it reboots.
halfhumble said:
Galaxy s8 on Verizon, a standard update notice kept appearing past few days, finally installed it. The minute it finished, it is now in an endless restarting loop. The phone does unlock and show my homescreen. I can get into it, but I only get about 10 seconds to do stuff then it freezes/restarts. Tried Clear Partition Cache in the recovery mode. Tried Safe Mode. No luck.
When I rush over to Settings>Software Update, and click it, it says "Software update in progress"....so it makes me think it is the remnants of the new software update completing itself, and that causes the rebooting. The final stages perhaps? Is there a way to CEASE that the second I unlock my phone? To stop all the background stuff.
Or maybe wouldnt make a difference. Any ideas besides factory reset? Way to revert back?
Wanted to backup a few recent pictures first.
Click to expand...
Click to collapse
Try downloading that same version of Odin flashable stock firmware from the internet, the same version as the update that you received, then flash that via Odin. As long as the update does not upgrade your bootloader or your binary, it will not wipe your user data(pics).
But first....
If you can get to the homescreen and unlock the device, don't touch anything else once the device opens, just connect it to PC and retrieve your photos from the internal storage, then factory reset the device.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Try downloading that same version of Odin flashable stock firmware from the internet, the same version as the update that you received, then flash that via Odin. As long as the update does not upgrade your bootloader or your binary, it will not wipe your user data(pics).
Click to expand...
Click to collapse
I dont know what version the update was that caused it or how I would find out. But I ended up getting it fixed.
I just downloaded the most recent version firmware from SamFW.com, and used that one. The First flash, the phone was worse! It was now stuck at the samsung logo looping. I flashed it a second time, then it worked! Phone back to normal and backed up my pictures. I had used the home CSC file too, and none of my user data was wiped. I thought it was supposed to wipe that, got lucky
I assume once that OTA update comes back and tries to install, I may have this problem all over again. I can't go forever without the security updates.
Droidriven said:
If you can get to the homescreen and unlock the device, don't touch anything else once the device opens, just connect it to PC and retrieve your photos from the internal storage, then factory reset the device.
Click to expand...
Click to collapse
^
I had tried that a couple times, it lasts about 15 seconds then restarts. Not enough time, I would get to the DCIM folder but before pics loaded, it froze and restarted.
halfhumble said:
I dont know what version the update was that caused it or how I would find out. But I ended up getting it fixed.
I just downloaded the most recent version firmware from SamFW.com, and used that one. The First flash, the phone was worse! It was now stuck at the samsung logo looping. I flashed it a second time, then it worked! Phone back to normal and backed up my pictures. I had used the home CSC file too, and none of my user data was wiped. I thought it was supposed to wipe that, got lucky
I assume once that OTA update comes back and tries to install, I may have this problem all over again. I can't go forever without the security updates.
^
I had tried that a couple times, it lasts about 15 seconds then restarts. Not enough time, I would get to the DCIM folder but before pics loaded, it froze and restarted.
Click to expand...
Click to collapse
The most recent version that you downloaded might be the same update. The OTA updates and the Odin flashable updates are the same thing, the OTA update is just more automated. Flashing the same version as the OTA update via Odin, yields the same results. I think the Home CSC is the one that doesn't wipe user data. I think the Home CSC is intended for users that intend on keeping the device and using it in the same region/network and the other CSC is intended for users that want to sell the device or use the device in a different region or if you have a custom ROM and custom recovery on the device and you want to restore to stock. I could be wrong though.
If you do get a prompt for an OTA update, backup your data then factory reset the device then allow the device to update. That should prevent any further issues with updating via OTA.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
The most recent version that you downloaded might be the same update. The OTA updates and the Odin flashable updates are the same thing, the OTA update is just more automated. Flashing the same version as the OTA update via Odin, yields the same results. I think the Home CSC is the one that doesn't wipe user data. I think the Home CSC is intended for users that intend on keeping the device and using it in the same region/network and the other CSC is intended for users that want to sell the device or use the device in a different region. I could be wrong though.
If you do get a prompt for an OTA update, backup your data then factory reset the device then allow the device to update. That should prevent any further issues with updating via OTA.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Okay, I see.
Well when the phone did boot back up normally after the 2nd flash, there was a pop up that said software update unsuccessful. So I'm not sure if the same OTA update actually updated per se. But yeah, next time Im ready, I've got everything backed up!
Thanks so much!
halfhumble said:
Okay, I see.
Well when the phone did boot back up normally after the 2nd flash, there was a pop up that said software update unsuccessful. So I'm not sure if the same OTA update actually updated per se. But yeah, next time Im ready, I've got everything backed up!
Thanks so much!
Click to expand...
Click to collapse
I always prefer updating via Odin instead of OTA, it is much better and less chance of issues such as bootloop or random reboot. These are the issues you were having. I actually suggest using Odin or Smart Switch on PC the next time an update is available. Or, on older devices, use Odin or Samsung Kies to update. OTA is frequently unreliable, it commonly causes bugs, especially if the update is a newer android version than what is already on the device, it usually causes conflicts due to user data from your previous system apps and user settings conflicting with the new system because of differences between the older system apps and the newer system apps or differences in settings in the older system conflicting with changes in how the newer system settings are handled. Systems don't like using system data that was created by another system when there are differences between the two systems.
Another method that can be used is if your manufacturer/carrier releases a stock update.zip that can be flashed via stock recovery, they are made specifically for flashing via stock recovery ONLY, they are not the same as the stock firmware file that is flashed via Odin. These can be downloaded to the phone's internal/external memory then you boot into stock recovery then factory reset/wipe cache in recovery(backup data before wiping) then you can flash the update.zip. Alternatively, you can flash the update.zip without resetting/wiping(this is called a "dirty" flash), in theory, a dirty flash is useful when you don't want to wipe data or lose data. But that comes with a chance of causing bugs, as you have discovered for yourself during your update process.
Sent from my SM-S767VL using Tapatalk