[Q] Moved contents of /data/data only level up, now can't unlock my screen. - Sony Xperia L

Hi,
I've CM12 on Xperia L, by mistake I moved all folders of /data/data one level up. Now phone boots-up normally but I don't see unlock pattern. I'm receiving notifications beeps but unable to access my phone.
Please suggest how may I move back folder to correct folder. I don't have any critical files on phone.
USB Debugging is disabled on my phone so i cant use adb.
I tried to use Cyanogen Recovery to apply update but it failed with some errors of signature and footer.
I tried to flash CWM but installer stuck on "waiting for device"
I checked "adb devices", it says "unauthorized" maybe its not allowed root access.

shznaqvi said:
Hi,
I've CM12 on Xperia L, by mistake I moved all folders of /data/data one level up. Now phone boots-up normally but I don't see unlock pattern. I'm receiving notifications beeps but unable to access my phone.
Please suggest how may I move back folder to correct folder. I don't have any critical files on phone.
USB Debugging is disabled on my phone so i cant use adb.
I tried to use Cyanogen Recovery to apply update but it failed with some errors of signature and footer.
I tried to flash CWM but installer stuck on "waiting for device"
I checked "adb devices", it says "unauthorized" maybe its not allowed root access.
Click to expand...
Click to collapse
pull out battery
wait...
pull in battery
(dont touch powerbutton! dont try to boot)
hold vol - (or + im not sure)
connect phone to pc
if you got blue led.... you are in fastboot mode....
then flash a kernel with cwm via fastboot
then flash a rom via cwm
Sent from my C2105 using XDA Free mobile app

SdtBarbarossa said:
pull out battery
wait...
pull in battery
(dont touch powerbutton! dont try to boot)
hold vol - (or + im not sure)
connect phone to pc
if you got blue led.... you are in fastboot mode....
then flash a kernel with cwm via fastboot
then flash a rom via cwm
Sent from my C2105 using XDA Free mobile app
Click to expand...
Click to collapse
I tried to do that in bootloader mode with Fastboot flash recovery recovery.tar but it didnt help. Here's the output.
E:\SonyXperiaL\files>Fastboot flash recovery recovery.tar
sending 'recovery' (3210 KB)...
OKAY [ 0.140s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.187s
Please tell me:
1. Is the .tar file a kernel? Do i need an .img file?
2. Kernels are phone + model specific? (I've CMW-xperiaL installer with adb commands batch file, that probably works in adb-mode with USB Debugging Enabled.)
3. What will be the correct Fastboot command?

shznaqvi said:
I tried to do that in bootloader mode with Fastboot flash recovery recovery.tar but it didnt help. Here's the output.
E:\SonyXperiaL\files>Fastboot flash recovery recovery.tar
sending 'recovery' (3210 KB)...
OKAY [ 0.140s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.187s
Please tell me:
1. Is the .tar file a kernel? Do i need an .img file?
2. Kernels are phone + model specific? (I've CMW-xperiaL installer with adb commands batch file, that probably works in adb-mode with USB Debugging Enabled.)
3. What will be the correct Fastboot command?
Click to expand...
Click to collapse
omfg oO :
1. tar is not a xperia file...its odin (samsung)stuff... dont touch this oO
2. please go to thunderzap.in/downloads ... download TZ4.15 for xperia L alias Taoshan ... extract boot.img from it...
3.
fastboot flash boot boot.img
our xperia have a boot+recovery partition... we dont got normal recovery
...PLEASE never flash stuff that not SPECIALY for xperia L alias Taoshan
Sent from my Xperia T using XDA Free mobile app

SdtBarbarossa said:
omfg oO :
1. tar is not a xperia file...its odin (samsung)stuff... dont touch this oO
2. please go to thunderzap.in/downloads ... download TZ4.15 for xperia L alias Taoshan ... extract boot.img from it...
3.
fastboot flash boot boot.img
our xperia have a boot+recovery partition... we dont got normal recovery
...PLEASE never flash stuff that not SPECIALY for xperia L alias Taoshan
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
Thanks! thunderzap did it.
The recovery.tar file came along with CWM recovery installer. It copies .tar and other .sh files into the /tmp and install those files from phone shell.

shznaqvi said:
Thanks! thunderzap did it.
The recovery.tar file came along with CWM recovery installer. It copies .tar and other .sh files into the /tmp and install those files from phone shell.
Click to expand...
Click to collapse
thats fine for fota recovery check my app at themes and apps section
Sent from my C2105 using XDA Free mobile app

Related

[Q] RE-root after 2.3.4 update?

Hello,
I am trying to root my SNS and since my fast bootloader is already UNLOCKED, is there anyway I can root my phone without wiping everything?
Flash custom recovery and then flash superuser.zip in custom recovery
snandlal said:
Part 3 - Recovery
1 - Download the ClockworkMod recovery image (for i9020A models, use this i9023 recovery image too!) 3024v3-i9023.img from [MOD][RECOVERY]Clockwork 3.0.2.4 New wipe & confirm menus!! i9023 & i9020 versions
2 - Save it to the Android SDK "tools" dir
3 - Open a command prompt go to run & type "CMD" & hit enter
4 - Switch to the directory where you unzipped the Android SDK & go to "tools"
5 - Then type "fastboot flash recovery 3024v3-i9023.img" & hit enter
You should get something like this, if not your image is corrupted, download it again
sending 'recovery' (3980 KB)... OKAY [ 0.621s]
writing 'recovery'... OKAY [ 0.511s]
finished. total time: 1.132s
6 - Then back on the SNS select Power Off (Reboot also works)
Click to expand...
Click to collapse
I was trying this guide, but my CMD says "fastboot" is not recognized as an internal or external command, operable program or batch file. should I not use cmd.exe ?
linushsu said:
I was trying this guide, but my CMD says "fastboot" is not recognized as an internal or external command, operable program or batch file. should I not use cmd.exe ?
Click to expand...
Click to collapse
You either need to have the tools folder of the SDK in your path or you need to cd into that directory.
linushsu said:
I was trying this guide, but my CMD says "fastboot" is not recognized as an internal or external command, operable program or batch file. should I not use cmd.exe ?
Click to expand...
Click to collapse
hi
u phiscally check the folder "tools" having the fastboot.exe file in it
linushsu said:
I was trying this guide, but my CMD says "fastboot" is not recognized as an internal or external command, operable program or batch file. should I not use cmd.exe ?
Click to expand...
Click to collapse
Forget fastboot for now. Download Joeykrim's "flash_image gui"
Download latest custom recovery
Rename it recovery.img
Open flash_image gui
Select recovery and browse to recovery and flash it
Now you have permanent cust recovery.
Do your thang, says Uncle Jimmy
http://forum.xda-developers.com/showthread.php?t=1139261
Firstly I want to thank everyone for helping me out! THANKS !
secondly, Thank you Chamb' is used your simple one-click method and it worked great!
snandlal, your method did not work, the "flash_image gui" could not get started on my phone since it was not rooted maybe I did something wrong.
Thanks all !
snandlal said:
Forget fastboot for now. Download Joeykrim's "flash_image gui"
Download latest custom recovery
Rename it recovery.img
Open flash_image gui
Select recovery and browse to recovery and flash it
Now you have permanent cust recovery.
Do your thang, says Uncle Jimmy
Click to expand...
Click to collapse
Im trying to flash my recovery now, for future rooting. anyway is says the Flash_image GUI is for Nexus s 4G, I do not have 4G. will it still work?

[TIP] Downgrade from JB to 0.30 works!

G'day guys, I won't go into too much detail but as I lost root by updating OTA to JB I have been successfully able to downgrade the firmware to 0.30 (and bootloader evidentially)
WARNING: YOU WILL LOSE ALL DATA ON INTERNAL STORAGE, IM NOT RESPONSIBLE FOR BRICKS, TRY AT OWN RISK!
WARNING: DO NOT TRY TO WIPE DATA FROM THE BOOTLOADER WHILST A CUSTOM RECOVERY IS INSTALLED, YOU WILL BRICK YOUR TABLET MAKE SURE YOU ARE RUNNING THE STOCK JB/ICS BOOTLOADER BY FLASHING THE ASUS BLOB PACKAGE FIRST!
You must have unlocked bootloader and be running the latest firmware 10.4.4.16
Procedure
1) Download 0.30 update from Asus website: http://www.asus.com.au/Tablet/Transformer_Pad/ASUS_Transformer_Pad_Infinity_TF700T/#download
2) extract the blob file from inside the second zip, put in your ADB/FASTBOOT directory
If you don't have fastboot download it here http://www.mediafire.com/?nbw2ofv3xd5s35l
3) Reboot tablet into bootloader (ON + VOLDOWN) then select fastboot mode
4) type command: fastboot -i 0x0b05 flash system blob
5) wait for ages....
6) the install will hang on the spinning asus diagram
7) reboot into bootloader and select the "wipe data" (same menu as where fastboot is)
8) should reboot automatically and you should have sucessfully downgraded to ICS 0.30
Hope it also works for you.
http://forum.xda-developers.com/showthread.php?t=1492887
Does it work with above method?
No idea, but you're welcome to try
Sent from my GT-I9100 using xda app-developers app
Has anyone tried this method to downgrade to .26 from .30?
Ok, confirmed, it doesn't work to revert to .26. You get signature mismatch. I gave it a shot
Now, if I upgrade to JB and downgrade can I go to .26? Hmmm, might give it a whirl.
tbtaf said:
Has anyone tried this method to downgrade to .26 from .30?
Click to expand...
Click to collapse
It won't work. You will get a signature mismatch. It seems to work between JB & 0.30
b3z said:
It won't work. You will get a signature mismatch. It seems to work between JB & 0.30
Click to expand...
Click to collapse
I can confirm this does work and does revert the bootloader.
Guys, can we move this to development? I personally believe it would be a great help to many over there. It saved my backside. I can tell you that! Great threat here!:laugh:
Uh, I can't access fastboot anymore with the JB update. It comes up as unknown device. I have installed the Naked Drivers and have had it installed for awhile with no problems.
The cmd sticks to < waiting for device >.
Can you create a zip with the right ADB/FASTBOOT drivers? I have try many but my tablet is not showing when i do FASTBOOT DEVICES
---------- Post added at 06:06 AM ---------- Previous post was at 05:58 AM ----------
androidxen said:
Uh, I can't access fastboot anymore with the JB update. It comes up as unknown device. I have installed the Naked Drivers and have had it installed for awhile with no problems.
The cmd sticks to < waiting for device >.
Click to expand...
Click to collapse
same here
2) extract the blob file from inside the second zip, put in your ADB/FASTBOOT directory
Click to expand...
Click to collapse
ADB/FASTBOOT folder? Sorry, haven't really fooled around much with my TF700, except for getting root. (and then loosing it like an idiot when I rushed to upgrade to JB)
Accophox said:
ADB/FASTBOOT folder? Sorry, haven't really fooled around much with my TF700, except for getting root. (and then loosing it like an idiot when I rushed to upgrade to JB)
Click to expand...
Click to collapse
1) To be able to use this fastboot method you need to have installed the android-sdk (google it) with the platform-tools package and also the Google USB drivers (i think it is in the extras package)
1A) Alternatively download this package, it contains the ADB/FASTBOOT application... not sure about the correct drivershttp://www.mediafire.com/?nbw2ofv3xd5s35l
2) Inside this package are two executables called adb and fastboot. Using windows command prompt you will have to navigate to the folder that contains these two executables and type "fastboot devices" if you have your TF700 plugged in and in fastboot mode you should see a few numbers and you're ready to go!
b3z said:
1) To be able to use this fastboot method you need to have installed the android-sdk (google it) with the platform-tools package and also the Google USB drivers (i think it is in the extras package)
1A) Alternatively download this package, it contains the ADB/FASTBOOT application... not sure about the correct drivershttp://www.mediafire.com/?nbw2ofv3xd5s35l
2) Inside this package are two executables called adb and fastboot. Using windows command prompt you will have to navigate to the folder that contains these two executables and type "fastboot devices" if you have your TF700 plugged in and in fastboot mode you should see a few numbers and you're ready to go!
Click to expand...
Click to collapse
Oh, well, then I'm an idiot. I thought it was a /system/fastboot or something silly that asus decided to do. Simple enough.
I get a:
C:\platform-tools>fastboot -i 0x0b05 flash system WW_9.4.5.30.zip (this is the unpacked update from the asus site)
sending 'system' (375245 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.656s
Should I have unlocked bootloader to downgrade?
does the "wipe data" feature of the stock recovery really delete the whole internal storage or does it leave the internal sdcard partition intact? i forgot to make a backup of this part (only my apps through titanium) and now my JB upgrade failed and i don't want to lose all my pictures and stuff
0x000 said:
does the "wipe data" feature of the stock recovery really delete the whole internal storage or does it leave the internal sdcard partition intact? i forgot to make a backup of this part (only my apps through titanium) and now my JB upgrade failed and i don't want to lose all my pictures and stuff
Click to expand...
Click to collapse
It does. I made that mistake too, lost my notes for the year so far... :banghead:
Sent from my Incredible 2 using xda app-developers app
How long might 'ages' be?
Been at sending 'system' (798394 KB) ...
for over 15 mins
Sent from my HTC PH39100 using xda premium
kyrtap10 said:
Should I have unlocked bootloader to downgrade?
Click to expand...
Click to collapse
You do need to unlock your bootloader to down grade.
buhohitr said:
You do need to unlock your bootloader to down grade.
Click to expand...
Click to collapse
Ok, now I know to make sure that I have backup of my root before updating
160bpm said:
I get a:
C:\platform-tools>fastboot -i 0x0b05 flash system WW_9.4.5.30.zip (this is the unpacked update from the asus site)
sending 'system' (375245 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.656s
Click to expand...
Click to collapse
you can't just flash the zip, you have to extract the "blob" file inside the zip and flash that

[Q] Erased recovery

Help Ive erased recovery and im not really experienced with fastboot I was trying to install clockworkmod and ended up deleting recovery please help ive got the kernal image from ASus but it is tar.gz please help im so confused I cant update or flash custom rom now its a nightmare just got this 2 or 3 days ago
4SHR4F said:
Help Ive erased recovery and im not really experienced with fastboot I was trying to install clockworkmod and ended up deleting recovery please help ive got the kernal image from ASus but it is tar.gz please help im so confused I cant update or flash custom rom now its a nightmare just got this 2 or 3 days ago
Click to expand...
Click to collapse
So I assumed that your device is unlocked? I recommend to flash twrp, more easier and works wellstart with section 2).
http://forum.xda-developers.com/showthread.php?p=32825557
how did you delete recovery?
cyanogen mod forum has a good wiki on fastboot.
buhohitr said:
So I assumed that your device is unlocked? I recommend to flash twrp, more easier and works wellstart with section 2).
http://forum.xda-developers.com/showthread.php?p=32825557
Click to expand...
Click to collapse
I followed this thread before it says Scott's TF700T Recovery Install tool V1.0
www.scottsroms.com
Congrats! You now have a custom Recovery installed on the official
JB release by Asus!
From here you can install a custom ROM or simply root the stock ROM.
The choice is yours!
Thank you for using my Recovery Install Tool!
Please visit www.scottsroms.com!
Donations Greatly Appreciated but Never Expected!
But when I boot into recovery I get Un recoverable bootloader error (0x00000000)
Also when I used the program it does the first reboot but not the second I dont know why? Please HELP
4SHR4F said:
I followed this thread before it says Scott's TF700T Recovery Install tool V1.0
www.scottsroms.com
Congrats! You now have a custom Recovery installed on the official
JB release by Asus!
From here you can install a custom ROM or simply root the stock ROM.
The choice is yours!
Thank you for using my Recovery Install Tool!
Please visit www.scottsroms.com!
Donations Greatly Appreciated but Never Expected!
But when I boot into recovery I get Un recoverable bootloader error (0x00000000)
Also when I used the program it does the first reboot but not the second I dont know why? Please HELP
Click to expand...
Click to collapse
I don't think you did it correctly, first boot you should see the 4 icons and you need to hit the volume down button on your device (within 10sec) to select USB icon then hit the volume up button to select this setting, now proceed with the instruction on your pc to flash. Make sure you copy the recovery twrp file named" openrecovery-twrp-2.3.1.0-tf700t.blob" from here http://goo.im/devs/OpenRecovery/tf700t to the "install Recovery" folder and RENAME this file to recovery.blob
buhohitr said:
I don't think you did it correctly, first boot you should see the 4 icons and you need to hit the volume down button on your device (within 10sec) to select USB icon then hit the volume up button to select this setting, now proceed with the instruction on your pc to flash. Make sure you copy the recovery twrp file named" openrecovery-twrp-2.3.1.0-tf700t.blob" from here http://goo.im/devs/OpenRecovery/tf700t to the "install Recovery" folder and RENAME this file to recovery.blob
Click to expand...
Click to collapse
OK last time im trying this wish me luck
Edit: Same problem grrrrrr it says its sent hasnt reboot my device as well so have to do it manually and still says same error
4SHR4F said:
OK last time im trying this wish me luck
Edit: Same problem grrrrrr it says its sent hasnt reboot my device as well so have to do it manually and still says same error
Click to expand...
Click to collapse
Sounds like your pc is not communicate correctly with your device. When your device is on and you execute Scott's bat file, is your device reboot into recovery so that you can select fastboot mode? Basically, Scott bat file is using adb command to reboot your device into recovery mode, you manually select and enable fast boot mode on your device, then the script is using fastboot command to push the recovery.blob (located in the same directory as Scott bat file) to your device.
buhohitr said:
Sounds like your pc is not communicate correctly with your device. When your device is on and you execute Scott's bat file, is your device reboot into recovery so that you can select fastboot mode? Basically, Scott bat file is using adb command to reboot your device into recovery mode, you manually select and enable fast boot mode on your device, then the script is using fastboot command to push the recovery.blob (located in the same directory as Scott bat file) to your device.
Click to expand...
Click to collapse
Yes it reboots the first time allowing me to go into recovery but then doesnt reboot second after it writes the recovery files dont know why fastboot works thats why I can delete recovery but writing is a problem :~
4SHR4F said:
Yes it reboots the first time allowing me to go into recovery but then doesnt reboot second after it writes the recovery files dont know why fastboot works thats why I can delete recovery but writing is a problem :~
Click to expand...
Click to collapse
And you did select the USB icon and the text displayed "fastboot" on your device? You also have the twrp renamed to recovery.blob in the same folder as the script? Let manually push this file using fastboot.exe and see what's happens.
buhohitr said:
And you did select the USB icon and the text displayed "fastboot" on your device? You also have the twrp renamed to recovery.blob in the same folder as the script? Let manually push this file using fastboot.exe and see what's happens.
Click to expand...
Click to collapse
With fastboot same problem when I load from command prompt it sends the file however if I do it without starting from that directory it says file not found but fastboot devices show the number should I make a video and send it
4SHR4F said:
With fastboot same problem when I load from command prompt it sends the file however if I do it without starting from that directory it says file not found but fastboot devices show the number should I make a video and send it
Click to expand...
Click to collapse
don't trust the log from fastboot or any script. Just make sure the recovery.blog is in the same directory of the fastboot command and you must execute fastboot.exe from command prompt.
1. manually boot to fastboot mode from your device. (boot to recovery then select USB icon)
2. Open command prompt and run as admin and navigate to fastboot.exe directory (with recovery.blog in this directory also)
3. type;
fastboot.exe -i 0x0B05 flash recovery recovery.blob
4. Once done, type
fastboot -i 0x0B05 reboot
Let me know the status.
buhohitr said:
don't trust the log from fastboot or any script. Just make sure the recovery.blog is in the same directory of the fastboot command and you must execute fastboot.exe from command prompt.
1. manually boot to fastboot mode from your device. (boot to recovery then select USB icon)
2. Open command prompt and run as admin and navigate to fastboot.exe directory (with recovery.blog in this directory also)
3. type;
fastboot.exe -i 0x0B05 flash recovery recovery.blob
4. Once done, type
fastboot -i 0x0B05 reboot
Let me know the status.
Click to expand...
Click to collapse
This is what I get recovery.blob is in the folder and fastboot works as I can delete recovery just not write for some reason
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
H:\Users\Install user>cd C:\Fastboot
H:\Users\Install user>fastboot devices
015d262e99141416 fastboot
H:\Users\Install user>fastboot.exe -i 0x0B05 flash recovery recovery.blob
error: cannot load 'recovery.blob': No error
H:\Users\Install user>
Also I would also like to point out it does not let me reboot after I write the files (using holding shift key and opening command prompt) as it freezes I think??? BEcause I can reboot from fastboot before I input writing flash recovery but after it wont allow don't know why?
4SHR4F said:
This is what I get recovery.blob is in the folder and fastboot works as I can delete recovery just not write for some reason
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
H:\Users\Install user>cd C:\Fastboot
H:\Users\Install user>fastboot devices
015d262e99141416 fastboot
H:\Users\Install user>fastboot.exe -i 0x0B05 flash recovery recovery.blob
error: cannot load 'recovery.blob': No error
Click to expand...
Click to collapse
Did you even notice that you didn't change to drive C: before calling fastboot? Is your recovery.blob in C:\Fastboot or in "H:\Users\Install user"?
_that said:
Did you even notice that you didn't change to drive C: before calling fastboot? Is your recovery.blob in C:\Fastboot or in "H:\Users\Install user"?
Click to expand...
Click to collapse
Yes I know but my command prompt is awkward either way ive tried using Android flasher but I find the problem is my device freezes while writing files dont know why
4SHR4F said:
Yes I know but my command prompt is awkward either way ive tried using Android flasher but I find the problem is my device freezes while writing files dont know why
Click to expand...
Click to collapse
Try this, copy the recovery.blob to this directory:
H:\Users\Install user\
Then type dir then hit enter, make sure your fastboot.exe and recovery.blob are there
H:\Users\Install user> dir then hit enter
Should show both fastboot.exe and recovery.blob
Now execute the fastboot command to push the recovery.blob
buhohitr said:
Try this, copy the recovery.blob to this directory:
H:\Users\Install user\
Then type dir then hit enter, make sure your fastboot.exe and recovery.blob are there
H:\Users\Install user> dir then hit enter
Should show both fastboot.exe and recovery.blob
Now execute the fastboot command to push the recovery.blob
Click to expand...
Click to collapse
Same problem says its sent and that it is written but after if I try to reboot the tablet doesn't respond and cant go into recovery because of that error 0x00000000
All I want to do is get UBuntu and Clean ROM on my Tablet then no more modding
OK I give up with command prompt can I use Odin or some other software to flash recovery or at least flash a custom rom from windows rather then twrp or cwm boatloaders or can I get ubuntu and do it through ubuntu any possibilities helpful please
4SHR4F said:
OK I give up with command prompt can I use Odin or some other software to flash recovery or at least flash a custom rom from windows rather then twrp or cwm boatloaders or can I get ubuntu and do it through ubuntu any possibilities helpful please
Click to expand...
Click to collapse
Nope, no Odin, but if your device is rooted, you could download goomanager from the market and install twrp using goomanager app.
buhohitr said:
Nope, no Odin, but if your device is rooted, you could download goomanager from the market and install twrp using goomanager app.
Click to expand...
Click to collapse
What about install linux without root and from there send in the recovery that way will that work
4SHR4F said:
What about install linux without root and from there send in the recovery that way will that work
Click to expand...
Click to collapse
You can be the first one to try...it may or may not works, but the methods I provided proved by many that they worked.

Xperia L stuck at recovery screen

Model - Sony xperia l - C 2014
I wanted to flash CM12 to my device. I followed the instructions on Cyanogenmod site.
I enabled USB debugging mode.
I unlocked the bootloader (as per the instructions on sony)
I'm using a linux machine. I've installed adb and fastboot tools.
I havent backed up my bootloader or system (but ive taken data backup before starting the process)
1) When i try to flash the CM ROM using adb sideload method, i get the error..
this package is for device c2105 c2104 c2105 c2104 taoshan this device is .
2) If i try to use fastboot method to flash new recovery, using the folowing command
#fastboot flash recovery cm-12-20150906-NIGHTLY-taoshan-recovery.img
i get the error..
sending 'recovery' (9702 KB)...
OKAY [ 0.308s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.310s
Now my phone is unable to boot normally. it gets stuck at recovery.
This is the first time i've tried to flash a new ROM. Any suggestion would be greatly appreciated.
Thank you
abhishek.karvi said:
Model - Sony xperia l - C 2014
I wanted to flash CM12 to my device. I followed the instructions on Cyanogenmod site.
I enabled USB debugging mode.
I unlocked the bootloader (as per the instructions on sony)
I'm using a linux machine. I've installed adb and fastboot tools.
I havent backed up my bootloader or system (but ive taken data backup before starting the process)
1) When i try to flash the CM ROM using adb sideload method, i get the error..
this package is for device c2105 c2104 c2105 c2104 taoshan this device is .
2) If i try to use fastboot method to flash new recovery, using the folowing command
#fastboot flash recovery cm-12-20150906-NIGHTLY-taoshan-recovery.img
i get the error..
sending 'recovery' (9702 KB)...
OKAY [ 0.308s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.310s
Now my phone is unable to boot normally. it gets stuck at recovery.
This is the first time i've tried to flash a new ROM. Any suggestion would be greatly appreciated.
Thank you
Click to expand...
Click to collapse
1.boot to recovery
2.connect to pc
3. use this commands in adb:
adb shell
setprop ro.product.device taoshan
4. flash cm12 or any other rom for taoshan
do this all while in same session (dont reboot after the terminal command or it will be gone)
Sent from my mint using XDA Free mobile app
SdtBarbarossa said:
1.boot to recovery
2.connect to pc
3. use this commands in adb:
adb shell
setprop ro.product.device taoshan
4. flash cm12 or any other rom for taoshan
do this all while in same session (dont reboot after the terminal command or it will be gone)
Sent from my mint using XDA Free mobile app
Click to expand...
Click to collapse
Thank you for the reply SdtBarbarossa .
I've done steps 1,2.
On 3rd step, when i give command #adb shell , im getting error....
error: device unauthorized. Please check the configuration dialog on your device.
Now since the device is stuck at recovery and does not boot, i cant re-authorize my computer from my phone.
I'd like to mention that i started fooling around with my ROM on a different workstation and im trying to fix this on a different workstation right now... having said that, do i need to retry the mentioned steps from the previous computer?
Thanks again.
abhishek.karvi said:
Thank you for the reply SdtBarbarossa .
I've done steps 1,2.
On 3rd step, when i give command #adb shell , im getting error....
error: device unauthorized. Please check the configuration dialog on your device.
Now since the device is stuck at recovery and does not boot, i cant re-authorize my computer from my phone.
I'd like to mention that i started fooling around with my ROM on a different workstation and im trying to fix this on a different workstation right now... having said that, do i need to retry the mentioned steps from the previous computer?
Thanks again.
Click to expand...
Click to collapse
Thats bad ;-( flash aromafm and use the inbuild terminal!
Then you need only the setprop command
Sent from my mint using XDA Free mobile app
SdtBarbarossa said:
Thats bad ;-( flash aromafm and use the inbuild terminal!
Then you need only the setprop command
Sent from my mint using XDA Free mobile app
Click to expand...
Click to collapse
ive downloaded aromafm. It says 1) copy the file to phones sdcard and 2) boot into recovery and select "install from zip"
The problem is :
1) I'm unable to copy anything to phone, since the phone is stuck at recovery and MTP is not working when i connect it to USB
2) My recovery doesnt have option "install from zip".... (recovery screen says - Cyanogen recovery)
Can i forcibly push the file to my sd card using flashtool or adb? or will keeping the file on external sd card work too? if so, how do i proceed?
Also i forgot to mention earlier that when i give the command # adb devices, it says unauthorised.
But im able to use the command #adb sideload *.zip (although it fails)
When i try the sideload method..flash starts but fails with the error..
On my computers terminal it says
Total xfer: 1.00x
On my phone the error is
this package is for device c2105 c2104 c2105 c2104 taoshan this device is .
E: Failed to install /sideload/package.zip
.
.
Installation aborted
I have downloaded the zip file from cyanogenmod official site, and im sure that ive taken the correct file for my device, and have checked that the hash mathces.
Thnx again.
abhishek.karvi said:
ive downloaded aromafm. It says 1) copy the file to phones sdcard and 2) boot into recovery and select "install from zip"
The problem is :
1) I'm unable to copy anything to phone, since the phone is stuck at recovery and MTP is not working when i connect it to USB
2) My recovery doesnt have option "install from zip".... (recovery screen says - Cyanogen recovery)
Can i forcibly push the file to my sd card using flashtool or adb? or will keeping the file on external sd card work too? if so, how do i proceed?
Also i forgot to mention earlier that when i give the command # adb devices, it says unauthorised.
But im able to use the command #adb sideload *.zip (although it fails)
When i try the sideload method..flash starts but fails with the error..
On my computers terminal it says
Total xfer: 1.00x
On my phone the error is
this package is for device c2105 c2104 c2105 c2104 taoshan this device is .
E: Failed to install /sideload/package.zip
.
.
Installation aborted
I have downloaded the zip file from cyanogenmod official site, and im sure that ive taken the correct file for my device, and have checked that the hash mathces.
Thnx again.
Click to expand...
Click to collapse
Copy the file to external sd
Sent from my mint using XDA Free mobile app
SdtBarbarossa said:
Copy the file to external sd
Sent from my mint using XDA Free mobile app
Click to expand...
Click to collapse
Even if I copy the file to external sd card, I'm unable to install it from there since I don't get a "install" option in recovery.
Its been too long so I went to the Sony store and got it fixed.
Anyways, Thanks for your help SdtBarbarossa, i appreciate it.
Once again, thank you
abhishek.karvi said:
Model - Sony xperia l - C 2014
I wanted to flash CM12 to my device. I followed the instructions on Cyanogenmod site.
I enabled USB debugging mode.
I unlocked the bootloader (as per the instructions on sony)
I'm using a linux machine. I've installed adb and fastboot tools.
I havent backed up my bootloader or system (but ive taken data backup before starting the process)
1) When i try to flash the CM ROM using adb sideload method, i get the error..
this package is for device c2105 c2104 c2105 c2104 taoshan this device is .
2) If i try to use fastboot method to flash new recovery, using the folowing command
#fastboot flash recovery cm-12-20150906-NIGHTLY-taoshan-recovery.img
i get the error..
sending 'recovery' (9702 KB)...
OKAY [ 0.308s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.310s
Now my phone is unable to boot normally. it gets stuck at recovery.
This is the first time i've tried to flash a new ROM. Any suggestion would be greatly appreciated.
Thank you
Click to expand...
Click to collapse
Try this command for installing recovery: " fastboot flash boot recovery.img"
change "recovery" word with your downloaded recovery file name.
@SdtBarbarossa
Hi, I have run into the same problem as OP, and have been trying to install aromafm but get the following output:
Code:
E: Cannot load volume /misc!
Finding update package...
Opening update package...
Verifying update package...
E: footer is wrong
E: signature verification failed
Installation aborted.
E: Cannot load volume /misc!
I have tried several aroma zips but its the same with all of them
I have checked and indeed the device ID is set to "".
Alhaj said:
Try this command for installing recovery: " fastboot flash boot recovery.img"
change "recovery" word with your downloaded recovery file name.
Click to expand...
Click to collapse
Ok, I was afraid to try this but finally dared, and it fixed my situation!
I ran it, and unlike trying to flash to recovery, flashing to boot proved successful (no "command not allowed" message). Then unplugged USB, and phone booted to recovery (I highly recommend TWRP), from where I installed the system and additional apps (surprisingly, without errors about device ID or incorrect signatures), and afterwards booted into system flawlessly.
Thanks!
severoraz said:
Ok, I was afraid to try this but finally dared, and it fixed my situation!
I ran it, and unlike trying to flash to recovery, flashing to boot proved successful (no "command not allowed" message). Then unplugged USB, and phone booted to recovery (I highly recommend TWRP), from where I installed the system and additional apps (surprisingly, without errors about device ID or incorrect signatures), and afterwards booted into system flawlessly.
Thanks!
Click to expand...
Click to collapse
Well its been a long time since i last had the time to pick up my XL ... but nice to hear that the fix still worked if you have any other question send me a pn since im no longer monitoring these threads ( due to missing time ;-( )
SdtBarbarossa said:
Well its been a long time since i last had the time to pick up my XL ... but nice to hear that the fix still worked if you have any other question send me a pn since im no longer monitoring these threads ( due to missing time ;-( )
Click to expand...
Click to collapse
Thanks! I picked mine up as a backup phone but this community has kept it running smooth

[HELP] Factory Reset from Settings while on Custom ROM

As the title says, I (without thinking) did a factory reset from within the settings menu while using a custom rom. My tablet boots and sits on the attached screen. I cannot access fastboot but while on the screen I have ADB access and can send commands. Also, none of the Volume&Power Buttons combinations will work. Please advise..
Here you go: http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Sent from my K00C using Tapatalk
berndblb said:
Here you go: http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
Thanks for the suggested thread, unfortunately after the "adb shell insmod /bootit.ko" command my tablet simply powers off and does not reboot. I read through the thread and saw that someone else experienced the same but there doesn't seem to be a resolution.
berndblb said:
Here you go: http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
Will this work if I accidentally did wipe davlink in TWRP after I flashed a rom? I can get into TWRP but cant reflash rom and am in boot loop when I try to flash it says MD5 not found
JGuinan007 said:
Will this work if I accidentally did wipe davlink in TWRP after I flashed a rom? I can get into TWRP but cant reflash rom and am in boot loop when I try to flash it says MD5 not found
Click to expand...
Click to collapse
Is that a serious question???
I used red size 6 type in that post to make clear what that trick is NOTfor.....
You must have done a little more than "accidentally wipe Dalvik" my friend. Dalvik would just get rebuild on the next boot if you wiped it.
The message that no MD5 is found is pretty normal if no MD5 is present, but it would not prevent you from flashing the rom.
My wild guess is that you somehow corrupted /data and it won't mount, but I don't really know because your post lacks anything that might be helpful.
Like specific information.
Try again.
Harder.
berndblb said:
Is that a serious question???
I used red size 6 type in that post to make clear what that trick is NOTfor.....
You must have done a little more than "accidentally wipe Dalvik" my friend. Dalvik would just get rebuild on the next boot if you wiped it.
The message that no MD5 is found is pretty normal if no MD5 is present, but it would not prevent you from flashing the rom.
My wild guess is that you somehow corrupted /data and it won't mount, but I don't really know because your post lacks anything that might be helpful.
Like specific information.
Try again.
Harder.
Click to expand...
Click to collapse
I'm still not sure what happened. I was flashing KatKiss-7.1_TF700T_015.zip and left my tablet on my desk. I ran out to the store and came home to my 6yo son holding the tablet and telling me it wasn't working. From what I gathered from what he said was he typed "yes" but wasn't sure what option he picked in TWRP. Going through options I think he picked the option to wipe cache dalvik after the rom was flashed but I am still not 100% sure what happened all I know is I'm stuck on Katkiss boot loop and when I go into TWRP to flash anything else it tells me failed no md5 or something along those lines
JGuinan007 said:
I'm still not sure what happened. I was flashing KatKiss-7.1_TF700T_015.zip and left my tablet on my desk. I ran out to the store and came home to my 6yo son holding the tablet and telling me it wasn't working. From what I gathered from what he said was he typed "yes" but wasn't sure what option he picked in TWRP. Going through options I think he picked the option to wipe cache dalvik after the rom was flashed but I am still not 100% sure what happened all I know is I'm stuck on Katkiss boot loop and when I go into TWRP to flash anything else it tells me failed no md5 or something along those lines
Click to expand...
Click to collapse
jmms1124.
Here is the instructions that I followed that restored my TF700T:
Download and install ADB, Fastboot and the required drivers - Download and run this cool little tool which has it all packed into one: [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.1 - xda-developers (don't forget to hit the Thanks button)
NOTE: at the moment Fastboot seems to have issues with Windows 8
This awesome tool installs the ADB and Fastboot.exe to a folder on your C:\ drive (look for a file titled “adb”) as well as the corresponding drivers. This takes about 15 seconds to install following the prompts.
I installed the device drivers - if you have already tried to connect the tablet to your PC and it's recognised as a portable device you should be ok. If not, download the Asus Sync Utility from their support/downloads site and install it.
Download the latest firmware from Asus (Always make sure that you download the correct SKU version -WW, US etc.) and extract the zip twice so you access the blob file (a blob is a collection of binary data stored as a single entity) – copy and paste this blob file into the previously mentioned “adb” folder on your C:\ drive.
Reset the device with a paperclip/needle (about 2 cm down of the SDcard slot)
Power down the tablet and disconnect it from the keyboard dock.
Connect it to your computer via the original USB cable.
Push and hold the Volume Down key (left side of the rocker) and the Power key until you feel the tablet vibrate twice. Let go when you see the tiny script. Read it and it tells you that your tablet is now in Fastboot mode and you will see three or 4 icons (depending on the bootloader version). Select the USB icon to get into the Fastboot mode.
Your PC should acknowledge that a USB device has been connected (an audible indication) Don’t panic if the device does not appear under “My Computer” (as mine did not either – Fastboot will still communicate with it), you can go into Control Panel/Hardware and Sound/ Device Manager and you may see “Fastboot” icon, expand this and the device will be represented again by the “Fastboot” icon. Right click, select “Properties”, Driver tab and then select “Update Driver” and allow it to search automatically and update from the internet. This should then update and change to Asus icons. You now can be certain that you have the current device drivers.
In Windows Explorer navigate to the folder that contains your adb.exe and fastboot.exe
Win 7 press Shift + right click and select "Open command window here".
In the resulting command prompt screen type the following codes (those in bold):
C:\adb\ (or whatever the path to your fastboot folder is..)
fastboot devices (If that command returns a string of numbers and letters, you are good as gold. If it returns: "No devices found", fastboot is not working - yet - and you have to troubleshoot)
Followed by each in turn of the below, selecting Yes as required and allowing each to complete the process:
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
The resulting screen should look something like this below – NOTE, I did make a couple of typos while I was attempting this which returned some multiple choice garble if this happens recheck you input instructions:
E:\asus>fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 1.979s]
finished. total time: 1.980s
E:\asus>fastboot erase recovery
erasing 'recovery'...
OKAY [ 1.023s]
finished. total time: 1.025s
E:\asus>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 39.623s]
finished. total time: 39.624s
E:\asus>fastboot erase boot
erasing 'boot'...
OKAY [ 0.303s]
finished. total time: 0.304s
E:\asus>fastboot erase misc
erasing 'misc'...
OKAY [ 0.602s]
finished. total time: 0.603s
E:\asus>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 1.459s]
finished. total time: 1.460s
fastboot -i 0x0B05 flash system c:\adb\TF700T\blob - depending where you stored your blob, also this was the first time that I saw the loading bar appear on my tablet.
It will now go through the process of reinstalling your Android stock ROM and you should see the something similar to the following:
E:\asus>fastboot -i 0x0B05 flash system e:\asus\blob
erasing 'system'...
OKAY [ 1.731s]
sending 'system' (800935 KB)...
OKAY [134.276s]
writing 'system'...
OKAY [131.640s]
finished. total time: 267.649s
fastboot -i 0x0B05 reboot
E:\asus>fastboot -i 0x0B05 reboot
rebooting...
finished. total time: 0.020s
E:\asus>
I disconnected and rebooted My Asus TF700T and I now have a fully functioning Tablet with a stock ROM.
It has been reported that after completing this you may have some issues getting back get into recovery, hitting RCK and getting the dreaded dead Android (with a red triangle with an exclamation point in the middle). I have not attempted this but have been led to believe that flashing TWRP 2.7.0.1 via Fastboot works.
All acknowledgement and appreciation for this method should go to Buster99, a Senior Member of XDA Developers
http://forum.xda-developers.com/show...2179759&page=2
And to Snoop05, also a Senior Member of XDA Developers for the awesome ADB/Fastboot/Driver tool.
http://forum.xda- developers.com/showthread.php?t=2588979
To whom I am most grateful for the return of my tablet to a working state, I hope this works for you. Good Luck.
Thanks to Browndog181 for this great instruction he made.
Good luck to bring back live to your tablet.:
Scenic-3.
JGuinan007 said:
I'm still not sure what happened. I was flashing KatKiss-7.1_TF700T_015.zip and left my tablet on my desk. I ran out to the store and came home to my 6yo son holding the tablet and telling me it wasn't working. From what I gathered from what he said was he typed "yes" but wasn't sure what option he picked in TWRP. Going through options I think he picked the option to wipe cache dalvik after the rom was flashed but I am still not 100% sure what happened all I know is I'm stuck on Katkiss boot loop and when I go into TWRP to flash anything else it tells me failed no md5 or something along those lines
Click to expand...
Click to collapse
So you got a little software engineer in the house, eh? :cyclops:
For these little rascals you need Apple devices: Safely locked down so the average user cannot do much damage :laugh:
You can do the buster99 described in the post above, but I would leave that as a last resort.
Sounds to me as if your son formatted something and since nothing exciting happened after typing "yes", he tried pushing some other buttons, interrupting the format and corrupting the partition.
I assume you can still boot into recovery and use it and fastboot is also accessible to you. Correct me if wrong.
Use TWRP's build in file manager to check if you can see the contents of your sdcard. If you can, it was not /data he formatted, but /cache or Dalvik. If so, just format cache, wipe Dalvik and reflash the rom
If /data is not accessible you'll have to format it from the Wipe > Advanced menu. That process takes 1 hour+, so send your son out of the house on a play date or some such....
That you see "md5 not found" probably means the box for "Verify MD5" (or "Check MD5" or something similar, can't remember what the official TWRP had there) is checked on the Install page just before you flash. TWRP will abort the installation if it does not find a MD5 for the zip you are trying to flash if you told it to look for one...
Make sure that is unchecked, then flash the rom.
If none of this works, take screenshots or write down the error messages you get and post them.
Here are pictures of what happens when I try to reflash
View attachment 4004171
View attachment 4004172
View attachment 4004173
View attachment 4004174
View attachment 4004180
Yes, /data and /cache cannot be mounted. Did you format them in TWRP?
Your version of TWRP is pretty outdated. You should update it to 2.8+ at the least, the last version is 3.0.2.
Did 2.7 even support f2fs? Can't remember....
Remember that if you format data you end up with ext4 file system and have to convert to f2fs again.
Sent from my TF700T using Tapatalk
I think i'm sending my son to boarding school. I'm not sure if he formatted them he has no idea what he did I know I can only use external sd to try to flash should I get TWRP 3.0.2 to my extenal sd and flash that or will that not work since it may have to be reformated? and how do I go about that?
JGuinan007 said:
I think i'm sending my son to boarding school. I'm not sure if he formatted them he has no idea what he did I know I can only use external sd to try to flash should I get TWRP 3.0.2 to my extenal sd and flash that or will that not work since it may have to be reformated? and how do I go about that?
Click to expand...
Click to collapse
No man, you have a working recovery now. Fix your problems first, then update the recovery.
BTW, I don't even know if you can properly flash Nougatella with TWRP 2.7. Maybe it's YOU who should be sent to boarding school... :angel:
Ok, so go to Wipe > Format Data, type yes and place the tablet on a high shelf. Leave it alone for an hour plus, this takes a while (and make sure it has enough juice)
Then go to Wipe > Advanced > check Cache and swipe the button. This will take a minute or two
Now go back to the home page, go to Mount and see if it lets you mount data, cache and microSD (check mark next to it). If it does not, reboot into recovery, go to Mount and see if they are mounted now. You are probably ok at this point. If you can mount the partitions you can flash a rom, but I think you should update TWRP first.
I don't believe anyone has made a recovery flashable package for 3.0.2 so flash it in fastboot. If you are not sure how, go to the General section and check out my Beginners Guide - it's all in there.
Once that is done, when you reboot (fastboot reboot), be ready to grab the tablet. Let it buzz once, then push and hold the Volume Down button to get into fastboot again and enter recovery through the RCK icon.
You should now have TWRP 3.0.2 on there.
Now convert data to f2fs (there's another guide in General for that), then flash the rom, gapps and SuperSU.
Enjoy

Categories

Resources