Ok, so Was using my nexus s today and I kept getting the notification to perform a system update to the newest version of gingerbread (2.3.4). Prior to pressing update my phone was at 2.3.1 default with 2.5.### ClockworkRecovery and it was rooted. Everything worked on it perfect. So I proceeded to download and install the update, and CWR fails to install the update and I would have to take out the battery to restart the phone. I had been doing this multiple times and I wanted to get it updated. So I go into CWR and try installing it manually:
I look around and try to find the file and I couldn't, I reset user data to see if it would fix it and it didn't, then I go back and start formatting the following folders, /system, /cache, /data and one other but I did not format /boot, so Then (noob me) I restart to phone and of course the rom is gone. I get back to recovery and try to restore from update.zip but the console said the file could not be found, I look up my model and look for a full verison rom and the mount my usb storage and place the rom .zip on the storage and try to install from .zip on sd but it did not work so I end up grabbing this and installing it and now I'm stuck, when I do adb shell it doesn't pick up the phone any more, it can fast boot on the phone but it can't go into recovery and I have no idea what I should do to try to fix this problem.
NOTE: before I ened up installing and replacing the recovery, my /system folder would not mount due to "invalid arguments"
Model is i9020T
I don't have firmware version access
and if there is any other information I can provide please let me know
Update:
I got the device to be recognized by fastboot but not by "adb shell", when I type adb shell no device is found, so I guess my question now is do I need to just flash a new recovery and then try to flash a new rom?
Solution:
1. fastboot your phone, (volume up+lock/power button)
2. place the recovery image you want to install in the "Android SDK"/tools/ folder
3. in your cmd/terminal, while in "Android SDK"/tools/ execute:
Code:
fastboot flash recovery "NAME-OF-RECOVERY.img"
4. once that is installed and it should work, then restart your recovery mode
5.clear all your data/factory reset, including davlik cache
6.mount your sd to your computer so you can place the Rom you want on your phone's sd
7. In recovery choose zip from sdcard to install.
8. It should install, if it gives you problems try another rom, I had problems with rAv 1.2.2, keep restarting every minute. I used "NS-2.3.4-GRJ22-Stock-Deodexed-signed.zip" and it worked.
9. Restart the phone and be patient the phone will start up and you should be set.
Hope this helps someone!
Related
HI,
2 of my PC (Windows 7 64) does not see my transformer in USB Debug mode. I installed the 64 bit Dell driver on each PC. Could someone provide me with some options to try.
Is there a way to completely reset the Transformer to stock without USB or being able to load a kernel from SD card?
2 ways to reset -
If you can boot then go into settings --> backup and reset --> factory data reset.
If you can't, hold volume-down then press power, and wait till wipe data appears, use vol keys to select it.
and search for the Universal Naked Drivers, those may help.
Thanks. That seemed to wipe the user settings and data, but not the recovery app "CWM-based Recovery v5.5.04 roach-tf101-r2". As a result the following happened after I reset.
System reboots
System comes up clean and runs setup (wifi, gmail account, etc).
System downloads firmware update.
System reboots to install update
Android appears and runs for a few seconds
Mesages appear: CWM-based Recovery v5.5.04 roach-tf101-r2
Finding update package, opening update package, Verifying update package
E: failed to verify whole-file signature
E:signature verification failed
Installation aborted
At this point the TF still will not install zip from sd card since as you told me before I need a different recover and is not found by the PC with a naked driver.
However, the unit is functional.
Any other options to root and get a new recovery installed and finally a new ROM.
Note: the PC does see the TF if I am in the recovery. However, as soon as boot the TF and enable USB debug the TF us not seen.
To go back to totally stock including stock recovery, download and flash an official ROM from Asus website.
baseballfanz said:
To go back to totally stock including stock recovery, download and flash an official ROM from Asus website.
Click to expand...
Click to collapse
I have no problem doing that, but how do I do it if I cannot connect the TF to PC via USB or load a zip file via recovery? Both of these do not work!
Did you update cwm via ROM manager? That's the issue there, you can run Roach2010's fix to fix that.
If terminal emulator app works you can flash a downloaded and extracted
(through es file explorer) recoveryblob with
Code:
su
dd if=/sdcard/recoveryblob of=dev/block/mmcblk0p4
reboot
Then you have working recovery and can either flash ROM or Stock.
Thanks for all the replies.
I finally got it working. It took me forever to understand that having a recovery that could only read from the internal memory was not a big deal. I created a folder on the internal sd and dropped in the zip for the external version of CWM . I rebooted and loaded the new restore and from then on I could load ROMs from my external uSD card. I am now happily running the latest version of Revolver.
Jerry
Hi Guys,
Just thought I'd provide a warning and a fix to a half day ordeal recovering from a soft-brick after wanting to make the switch from TW to WWE.
What made this all go wrong?
I have a Padfone 2 which had the latest TW_A68-10.4.17.15
I have a accidentally turned off adb USB debugging mode
The process:
I unlocked my bootloader using the ASUS official unlocker.
I had then install 2.7.0.1 twrp which didn’t work
Install 2.5.0.0 twrp which did.
Forgot to do a backup which I usually did, but guess I thought that I have done this so many times, nothing would go wrong.
DON’T GET COCKY BACKUP FIRST.
Opted for the easy way out and write to system VIA twrp using zip, which was reported to work.
This installed and didn’t report any error.
After reboot, app.phone and another OS programs crashed constantly and rebooted.
I removed my sim and this stopped the crashed apps, but not the reboots.
I realised I was in a whole world of trouble and it was only at this moment did I realise that I didn’t have USB Debugging turned on. Frantically tried to enable it in between reboots, but failed and was now presented with only a ASUS spinning circle of death, or even better later, only the which ASUS logo before it reached it.
All I had available was fastboot and twrp.
You’d think this was an easy fix, but I didn’t have a usable/original rom on the /data/media a.k.a /sdcard partition.
Note: have a handful of roms including your original rom saved on the phone before trying anything, as this phone has no access to external storage when all goes pear shaped.
I wiped caches, didn’t work.
I then wiped data, which then deleted the only rom I had access to. So I couldn’t even now retry installing from zip.
ADB didn’t work from any recovery including CWM 6.0.4.4
I was at a loss and didn’t know what to do.
The recovery:
Installed twrp 2.6.3.0 was persistent with ADB sideload, even though I didn’t have USB Debugging enabled.
Note: ADB sideload will still work even if you don’t have USB Debugging enabled. It’ll either take a min or two to register on your computer, but if not reboot and reboot again to get it to register.
Sideloaded the wrong firmware file again.
Note: If you are trying to sideload the original firmware, extract the zip “TW_PadFone2_user_10_4_17_15_UpdateLauncher.zip” and sideload the zip hiding within “ASUS” -> “Update” -> “TW_A68-10.4.17.15-0-ota-user.zip”
After another long time trying to get the ADB device to register, finally got a second chance and got back to the original firmware.
Did this deter me from the switch from TW to WWE. HELL NO!!
Enable ADB USB Debugging
Make sure you push the rom WWE to your /sdcard partition
How to do it right.
Load the original recovery attached recovery.stock.img
Reboot into recovery and select "apply update from external storage" and choose the zip file to flash.
This will fail! It's what it's meant to do
At this point the recovery changes the partition table and then restarts.
On reboot we will have a nice "Installation aborted", this because, being changed the partition table, the recovery can not find the file to flash as it the partition containing the data has been reformed losing its contents. So you will need to copy the file again via adb.
Select "wipe data / factory reset"
You need to do a wipe, because it formats the partition where we will send the file. Having just changed, the partition has not a file system and so it must be formatted to save something on it.
Upon rebooting to ADB stopped working under the stock recovery. It registered with my computer but the command to repush the WWE rom to /data/media kept failing.
Rebooted into fastboot and install twrp 2.6.3.0. At this stage as I knew that the partition table had been updated, I sideloaded the WWE rom, which works more reliably when it's originally enabled
Did a Wiped cache for safe measure
Reboot and welcome to another 2GBs of space and WWE firmware.
NOTE: Always flash the inner zip “TW_A68-10.4.17.15-0-ota-user.zip” not the outer zip “TW_PadFone2_user_10_4_17_15_UpdateLauncher.zip”
freak4916 said:
Load the original recovery attached recovery.stock.img
Click to expand...
Click to collapse
Where can I find this?
So I installed TWRP recovery backed up my stock os and flashed cyanagen mod 11
After a week or so I went in the cyanagen mod updates and started updating, everything worked
but now when I tried to flash in to my stock rom I go to recovery and I see that I have Clockwork revovery insted of TWRP
so I was stupid and i flahsed TWRP and didnt unistall clockwork mod
When i went in the recovery i had clockworkmod and then I rebooted and went in to TWRP
Now im stuck in 2 recoverys and cant go to cyanagen
I really need help
im using the LG G2 D802
gamehero said:
So I installed TWRP recovery backed up my stock os and flashed cyanagen mod 11
After a week or so I went in the cyanagen mod updates and started updating, everything worked
but now when I tried to flash in to my stock rom I go to recovery and I see that I have Clockwork revovery insted of TWRP
so I was stupid and i flahsed TWRP and didnt unistall clockwork mod
When i went in the recovery i had clockworkmod and then I rebooted and went in to TWRP
Now im stuck in 2 recoverys and cant go to cyanagen
I really need help
im using the LG G2 D802
Click to expand...
Click to collapse
I don't know if I understood you but just to be sure; you get in recovery mode CWM and on reboot TWRP?
I don't think you will like this solution but probably you will get your phone to work again xD (you will lose your data)
First of all you need:
- Android SDK bundle (google it, you will find it) on your Computer
- And a Rom you want to sideload (In your case the Cyanogen Rom)
- Cwm
Follow this steps:
1. go to the SDK bundle folder you downloaded -> go to sdk
-> go to platformform-tools
-> copy your ROM (ZIP-file) inside that folder
-> and name it to ROM.zip (so you won't need to write down a longname in cmd afterwards)
2. go to the SDK bundle folder you downloaded -> go to sdk
-> now press [shift] + [right mouse button] on platformform-tools (folder) to open cmd
3. Reboot your device into recovery mode (use cwm)
4. Go to “Mounts & Storage” and make sure that you can see “Unmount /sdcard/” and “Unmount /system/” (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount).
5. Now connect your device to the PC.
6. Once the phone is connected to the PC type “adb devices” in the cmd. If it returns a long alphanumeric string the phone is successfully connected in ADB mode. (if not look out for a usb driver for your phone; most time the problem lies in there)
7. Now type “adb push ROM.zip /sdcard/ROM.zip” (replace the word ROM if didn't named it)
8. This may take a while so be patient.
9. Once the process is complete you’ll see a message like <12345678kb to 1234567kb> on the cmd window.
10. Now unplug the device.
11. Go to the main screen of recovery and perform factory reset, wipe cache partition and then in advance menu wipe Dalvik cache. (Now you will lose your data for sure xD)
12. Now go to install zip from sdcard and choose the zip file you just transferred.
13. Once the process is complete, reboot the device
Hope this will help you.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
If you use TWRP there are some similar step by step guides ( maybe you should look for sideload)
GuiltyGod said:
I don't know if I understood you but just to be sure; you get in recovery mode CWM and on reboot TWRP?
I don't think you will like this solution but probably you will get your phone to work again xD (you will lose your data)
First of all you need:
- Android SDK bundle (google it, you will find it) on your Computer
- And a Rom you want to sideload (In your case the Cyanogen Rom)
- Cwm
Follow this steps:
1. go to the SDK bundle folder you downloaded -> go to sdk
-> go to platformform-tools
-> copy your ROM (ZIP-file) inside that folder
-> and name it to ROM.zip (so you won't need to write down a longname in cmd afterwards)
2. go to the SDK bundle folder you downloaded -> go to sdk
-> now press [shift] + [right mouse button] on platformform-tools (folder) to open cmd
3. Reboot your device into recovery mode (use cwm)
4. Go to “Mounts & Storage” and make sure that you can see “Unmount /sdcard/” and “Unmount /system/” (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount).
5. Now connect your device to the PC.
6. Once the phone is connected to the PC type “adb devices” in the cmd. If it returns a long alphanumeric string the phone is successfully connected in ADB mode. (if not look out for a usb driver for your phone; most time the problem lies in there)
7. Now type “adb push ROM.zip /sdcard/ROM.zip” (replace the word ROM if didn't named it)
8. This may take a while so be patient.
9. Once the process is complete you’ll see a message like <12345678kb to 1234567kb> on the cmd window.
10. Now unplug the device.
11. Go to the main screen of recovery and perform factory reset, wipe cache partition and then in advance menu wipe Dalvik cache. (Now you will lose your data for sure xD)
12. Now go to install zip from sdcard and choose the zip file you just transferred.
13. Once the process is complete, reboot the device
Hope this will help you.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
If you use TWRP there are some similar step by step guides ( maybe you should look for sideload)
Click to expand...
Click to collapse
So I got to step 4 and I see the mount system but I don't see umount sdcard
Then mount system or skip this part
5,6 and 7 are the most important part.
Can you push the Rom on your phone?
GuiltyGod said:
Then mount system :S
5,6 and 7 are the most important part.
Can you push the Rom on your phone?
Click to expand...
Click to collapse
adb push ROM.zip /sdcard/ROM.zip if I dont have the sdcard umonted will this still work?
I know I am repeating myself more or less (because I always edit my posts xD)
Well as long as you can push your file there shouldn't be sny problem
GuiltyGod said:
I know I am repeating myself more or less (because I always edit my posts xD)
Well as long as you can push your file there shouldn't be sny problem
Click to expand...
Click to collapse
so I wrote the command and it sad "5143kb/s «241840314 bytes in 45.912s»"
then i went install the zip and I can't find it
ok i went and mounted the data , pushed the file and installed it, thank you so much
But now i need to install the stock backup that I did with TWRP
That's pretty weird xD Because you get the message for a successful transfer but can't find the Zipfile.
You could try to push the Zipfile again and don't wipe anything at all (because you already wiped everything) and try to find the Zip file again to flash it.
Btw what does CWM gives you as options if you click install Zip files?
GuiltyGod said:
That's pretty weird xD Because you get the message for a successful transfer but can't find the Zipfile.
You could try to push the Zipfile again and don't wipe anything at all (because you already wiped everything) and try to find the Zip file again to flash it.
Btw what does CWM gives you as options if you click install Zip files?
Click to expand...
Click to collapse
it's all good now but now i have CWM and i need TWRP to install my stock backup
Watch this video (shows you how to change recovery in general):
http://m.youtube.com/watch?v=jnESTcH2ioA
And read this instructions if you still have some doubts and want to go for sure (recovery for LG2 D802):
http://forum.xda-developers.com/showthread.php?t=2472223
Sry I am a bit lazy right now xD Came back from work
It's been a rough morning over here.
I've had a lot of issues with the latest update (12.1) so I decided to download the .zip for CM12s and install it from recover - the exact same way I updated it initially (before I got the 12.1 OTA update).
I used the same .zip file from before, builds.cyngn.com/cyanogen-os/bacon/12.0-YNG1TAS0YL-bacon/2263178b74/cm-12.0-YNG1TAS0YL-bacon-signed
After installing from internal storage from the menu, it seems to install fine, and then it takes me back to the menu and I select Restart System.
After 20 minutes looking at the Cyanogen boot logo, I'm assuming it's stuck.
When I plug the phone into the computer, it says it's charging but neither Windows or my Chromebook recognize the device to allow file transfer.
If I press down+power, I can still get to the Cyanogen menu, but without a new .zip file I'm not sure what else to try.
Any advice? I'm pretty worried!
nagem145 said:
It's been a rough morning over here.
I've had a lot of issues with the latest update (12.1) so I decided to download the .zip for CM12s and install it from recover - the exact same way I updated it initially (before I got the 12.1 OTA update).
I used the same .zip file from before, builds.cyngn.com/cyanogen-os/bacon/12.0-YNG1TAS0YL-bacon/2263178b74/cm-12.0-YNG1TAS0YL-bacon-signed
After installing from internal storage from the menu, it seems to install fine, and then it takes me back to the menu and I select Restart System.
After 20 minutes looking at the Cyanogen boot logo, I'm assuming it's stuck.
When I plug the phone into the computer, it says it's charging but neither Windows or my Chromebook recognize the device to allow file transfer.
If I press down+power, I can still get to the Cyanogen menu, but without a new .zip file I'm not sure what else to try.
Any advice? I'm pretty worried!
Click to expand...
Click to collapse
Have you tried using fastboot to flash the stock images?
Are you using twrp?
1.I suggest installing twrp vor any recovery you like.
2. Than redownload rom and gapps (just to be sure)
3. Mount your device as mtp storage in twrp and put Rom and gapps in it
4. Than wipe /system /data /cache
(data wipe will delete all apps, your internal storage will be untouched)
5. flash rom and gapps
6. reboot your phone
If that does not help try Heisenbergs solution.
I have almost finished setting up new Redmi 6.
After rooting, getting TWRP on the phone I have reinstated all apps trough TitaniumBackup. I have reinstated too many apps from TB and at some point I have removed 1 or 2 apps too many that I thought are only from TB...
Inside TB I went into system apps and deleted apps wit: Backup copy [APK + backup]. Before I realised that apps with backup were actually original Xiaomi appswas too late, I had few warnings later and phone rebooted but couldn't boot into system.
This way I got rid of:
com.android.providers.telephony
com.android.phone
I could recreate what I have removed going into old phone and seeing which apps are backed up from system...
Can you help me to get apps back trough TWRP or FASTBOOT?
USB debugging was still on last time
My SD card is formatted as part of internal storage
TWRP File Manager can browse ROOT folder
It is newest ROM for Redmi6, [V10.3.6.0.OCGMIXM_], can someone provide copy of APKs please?
When in TWRP I mount system only, and try to [wipe dalvik] I get messages:
Failed to wipe dalvik
Updating partition details...
df /external_sd > /tmp/dfoutput.txt process ended with ERROR: 1
df /external_sd > /tmp/dfoutput.txt process ended with ERROR: 1
...done
Unable to mount storage
I almost will not loose any data, but:
if I can I'd like to move missing apps back to /app/data/ OR /system/app/ ? to recover system so it starts
if need be I will flash Xiaomi ROM and start from scratch but will loose many h of hard work on de-bloating etc [I hope that flashing original ROM will be easy since TWRP is working fine]
During TWRP - ADB sideload:
HTML:
adb install com.android.phone.apk
error: device '(null)' not found
- waiting for device -
What can I do???
-------------------------------------------------------------------------------------
Turns out I had to flash original stock
Xiaomi guide is terrible and out of date, so:
there are prerequisites required, like ADB, drivers, that is well explained on Xiaomi site, then...
download original stock for fastboot >>> unpack folder XXX sitting inside 2 archives [it's not zip] >>> download/install and run XiaoMiFlash.exe >>> SELECT button - navigate to unpacked folder XXX >>> attach mobile >>> refresh = device will appear on list >>> FLASH
Read official xiaomi instructions on flashing original ROM just in case something will get updated
Why not any other way?
In TWRP it asked me for a password at the start
I couldn't get /system/ or /data/ mounted, wiped or formatted.
I have seen folks giving advice on how to do it, but often it didn't make sense or it didn't work.
I would be risking bricking new device by other methods & I had no more than 3 pictures to loose on flashing ROM and hours spent on doing up.
Interesting is, there really wasn't even one working advice on how to mount i.e. /system in TWRP when password is missing in booted operating system [like my case, I couldn't find any info on that, all at some point were going to advice to do something that required mounted /system or /data]
But then I just finished whole process of flashing stock ROM; I have set [1. simple password] then [PIN], went to TWRP, tried to use OS password/PIN and it didn't work, it didn't remove encryption .
----------------------------------------------------------------------------------------------------------------------------------------------
Found a solution on how to root the phone after all above.
After another Original stock ROM 10.3.6.0.OCGMIXM flash with XiaoMiFlash.exe, phone will automatically restart and start OS
But... I didn't let it to boot
Once it restarted I have pressed Vol- [button down] and waited for fastboot to load [no need to hold power button]
Installed TWRP 3.0.0.0
Restarted
Hold Vol+ [button up]
TWRP loads
CANCEL if asks for password
----------------------
INSTALL boot.img [when you flash stock ROM it is inside folder, just copy it across]
in MOUNT tick /vendor & /system
use back button to exit MOUNT
INSTALL Magisk 19.3.zip
clean dalvik cache and swipe
I have once again restarted to RECOVERY/TWRP
------------------------
When OS booted I couldn't run/start Magisk APK/aplication. Screen blinked and that's all. Root not working.
download Magisk Manager [7.3.4 in my case] from web & install
I could start application this time & it asked me to install something extra - I have chosen to install it right away
Magisk reboots phone
Now phone was finally rooted
---------------------
I used external USB attached to phone with files so I didn't need to copy files to phone.
This is much more convenient as after restarting to TWRP first time there is nothing on the phone and you would have to sideload.
---------------------------
Below is LibreOffice doc with ADB commands to uninstall bloatware. In the column next to uninstalling commands, are commands to instal same app back [I do not know will this always work since I tried only on few] [some missing - you can create it yourself]
Potentially further down the list there are more necessary apps. Uninstalling them did not cause problems in my set up, but sometimes they might be needed for less important stuff...
https://www.dropbox.com/s/xpfeh4wx1nv5dlf/Bloatware removal + SD as internal.ods?dl=0