Database Info

[Q] [q] help! I deleted my phone system!

Please help! i deleted the phone SYSTEM by accident and now i dont have a phone! !!
Please help me..
THanks!

Kalekip21 said:
Please help! i deleted the phone SYSTEM by accident and now i dont have a phone! !!
Please help me..
THanks!
Click to expand...
Click to collapse
You can't turn on your phone?
And how did it happen?

Shadee13 said:
You can't turn on your phone?
And how did it happen?
Click to expand...
Click to collapse
It had some bugs in it so i went to a store and they told me to hard reset it,
But i already had a custom rec. on it so i went in recovery and selected WIPE and i could choose things (like dalvik and cache) and i selected everything (including SYSTEM) so now i dont have an OS on the phone.. any help?

Kalekip21 said:
It had some bugs in it so i went to a store and they told me to hard reset it,
But i already had a custom rec. on it so i went in recovery and selected WIPE and i could choose things (like dalvik and cache) and i selected everything (including SYSTEM) so now i dont have an OS on the phone.. any help?
Click to expand...
Click to collapse
Probably I can help you:
1. Go to recovery
2. Plug your phone to your PC (USB)
3. I am using TWRP 2.6.3.0, for me on the homescreen I have a "Mount" button, click it, and press mount usb storage.
4. After a while you will see your phone internal memory plugged in as an USB disk.
5. Download any ROM you want, make sure that you are downloading ROM for your device (There is 2 types of HTC One S, Ville and VilleC2)
Perform a factory reset in recovery
6. Flash the ROM (press install and select the ZIP file) (Do not reboot! Stay in recovery)
7. On your PC create a folder called "fastboot" on C drive
8. Download the file from the attachment, and extract the 4 files from it to the folder which you created before
9. Still on your PC... open the ROM (ZIP file), and you probably have a boot.img file in it.
10. Extract the boot.img to "fastboot" folder
11. On your phone now... In recovery select "Reboot" and select Bootloader
12. Your phone will now reboot to bootloader, you will probably see FASTBOOT USB
13. open cmd
14. In cmd write this:
Code:
cd/
cd fastboot
fastboot flash boot boot.img
After it says "Completed!" write:
fastboot reboot
15. Your phone will reboot and probably it will work
PS: Sorry for my bad english
EDIT: Hope you have already updated your phone to Jelly Bean....
Because if you was still on Ice Cream Sandwich then JellyBean ROMs will probably not work

[Guide] How to Flash The Downloaded OTA File [ HTC One Mini 4.2.2 to 4.3]

Greeting from Vietnam, and sorry for my English
So, you dont want to wait the official-update from your carier/country, you got the OTA file from somewhere else, i'm gonna show you how to flash it, step by step with some stricks
This might works with other phones (I think), but in this guide we'll doing stuffs with HTC One Mini Android 4.2.2, flashing 4.3 OTA file
Before you do anything, i suggest you should do a nandroid backup, so you can get back your official rom any time. This is very important, please google for it
(For those who dont know: to do this, you'll need Unlock bootloader, then installing a custom recovery, i recommend TWRP instead of CWM, i've got error with cwm once -> Get into Recovery Mode -> Backup -> Save it to your computer)
I've googled and tried some other ways to upgrade the phone, but it was not work, like:
http://forum.xda-developers.com/showthread.php?t=2573479
Flash another 4.2.2 ROM -> [Settings > About > Software update] -> Download (only) the OTA file -> Flash the stock recovery file -> Then the phone will alert "the update is downloaded and ready"
Click to expand...
Click to collapse
Well, that's the idea. But right after your download is done (in your phone), it turns out error: "Variant system version", saying your phone has been modified, and end up by delete the OTA file
Let's get started
1. Requirement, Your phone must be:
Disabled Fast Boot:
Settings > Power > Untick Fast boot
Click to expand...
Click to collapse
Enabled USB Debugging:
Settings -> Developer Options -> USB Debugging
If you do not see "Developer Options", Go to Settings > About phone > Software > More > click on build number 7 times. This should enable that section
Click to expand...
Click to collapse
Unlocked Bootloader
Got the S-Off (For HTC phones, to: be able to write to /system)
Installed a custom recovery (recommend TWRP)
The guide can be found at here: http://forum.xda-developers.com/showthread.php?t=2365506
2. Download the OTA file
You can use any OTA files, like the EU, the international,...
For HTC One mini, 4.3 OTA file can use this: OTA_M4_UL_JB43_SENSE55_MR_HTC_Europe_2.12.401.1-1.32.401.2_release_342200vz5jcl35ysxswchv.zip by http://forum.xda-developers.com/showpost.php?p=48404636&postcount=1
3. Flash the firmware
Extract the OTA file you'll get firmware.zip
Make sure you already got the fastboot.exe, adb.exe, AdbWinApi.dll, ... files -> Move all these files + the firmware, the OTA file into a folder like: D:\htc
Reboot your phone into Fastboot USB Mode
Power off > Hold the both Volume Down key + Power key several seconds > Fast Boot
(Use the Volume key to change the selection, the Power key to chose/enter)
Click to expand...
Click to collapse
Make sure your phone is recognized by fastboot and adb, to check:
fastboot devices
- and:
adb devices
Click to expand...
Click to collapse
In case you got error "Device not found" with adb: turn the phone into Recovery Mode, it will fix this, so you can do adb push, shell...
Relock the bootloader, so we can flash the firmware update:
fastboot oem lock
The phone will reboot
Click to expand...
Click to collapse
Reboot to OEM update mode:
adb reboot oem-78
The phone will show the white-text HTC
Click to expand...
Click to collapse
Flash the firmware.zip:
fastboot flash zip firmware.zip
You'll see a green progressbar on the screen, if not: do the command again
Click to expand...
Click to collapse
Unlock Bootloader from http://htcdev.com, install the TWRP Recovery again
fastboot flash unlocktoken Unlock_Code.bin
fastboot flash recovery Twrp-2.6.0.0.img
You might need to get the new Unlock_Code.bin from htcdev
Click to expand...
Click to collapse
Now your phone is wiped, the /sdcard/ folder is empty
4. Make the OTA Flash-able file
Download the sample.zip file at here, we'll rename it to: OTA-4.3.zip, see How to make a flashable zip at here: http://forum.xda-developers.com/showthread.php?t=2163974
Open OTA-4.3.zip with winrar or 7zip, you'll see 2 folders: META-INF/ and system/ . We're going to put data from the OTA file into this zip file (Notice that the system/ folder is empty)
From the extracted OTA file that you've downloaded (OTA_M4_UL_JB43_SENSE55_MR_HTC_Europe_2.12.401.1-1.32.401.2_release_342200vz5jcl35ysxswchv.zip) copy 2 folders: system/ and patch/ into OTA-4.3.zip, just drag and drop them to opened OTA-4.3.zip (by winrar), hit OK in the winrar popup
--> You might wonder why we're doing this: Why we put 2 folders from OTA_M4_UL_JB43_SENSE55_MR_HTC_Europe_2.12.401.1-1.32.401.2_release_342200vz5jcl35ysxswchv.zip to the new, almost empty OTA-4.3.zip; instead of delete all other files, folders from OTA_M4_UL_JB43_SENSE55_MR_HTC_Europe_2.12.401.1-1.32.401.2_release_342200vz5jcl35ysxswchv.zip
--> The anwser is: i have no idea, the second way just doesn't work, i tried
5. Flash the OTA Flash-able file
Copy the OTA Flash-able file (OTA-4.3.zip) into your phone, your phone can not boot up now, so we'll use adb push command
adb push OTA-4.3.zip /sdcard/
It may takes few minutes
Click to expand...
Click to collapse
Now simply Install Zip from recovery:
Boot into Recovery Mode > Install Zip > select OTA-4.3.zip
Click to expand...
Click to collapse
Reboot the phone, if everything goes well, it's showing a progressbar of the Apps installing
You're now in 4.3

Thank you for this information but unfortunately it didnt work for me.
windovv said:
You'll see a green progressbar on the screen, if not: do the command again
Click to expand...
Click to collapse
I do see the green progress bar and it moves to the right but....
the Fastboot/DOS window finishes the flash firmware command successfully but the green progress bar shown on the phone does not go to the very end.....
so at this point I reboot back to fastboot on the phone and then unlock the bootloader then follow the rest of your instructions....
Everything appears to be successful but when i boot the phone it displays the boot animation to the end then just stays there....The phone never goes past the boot animation
Ive managed to restore a backup so thats not a problem but im really struggling to install the 4.3 and sense 5.5 update using the other method shown at the beginning of your post and your method here
anyhow, looks my radio, HBOOT etc is updated now ive flashed the "firmware.zip" from my OTA

Sirius-C said:
Thank you for this information but unfortunately it didnt work for me.
I do see the green progress bar and it moves to the right but....
the Fastboot/DOS window finishes the flash firmware command successfully but the green progress bar shown on the phone does not go to the very end.....
Click to expand...
Click to collapse
I think this step is just fine, i've noticed that the progress bar was near to the end, not full of the bar. If you not sure about this, you can do this step (run this command) twice:
fastboot flash zip firmware.zip
You'll see a green progressbar on the screen, if not: do the command again
Click to expand...
Click to collapse
Everything appears to be successful but when i boot the phone it displays the boot animation to the end then just stays there....The phone never goes past the boot animation
Click to expand...
Click to collapse
It seems like you have just flashed the firmware.zip only, the rest of the OTA file has not been flashed successfully yet. The phone is now wiped, so it can't boot up
Reboot the phone, if everything goes well, it's showing a progressbar of the Apps installing
Click to expand...
Click to collapse
Notice that in some cases, there's no progressbar showing, but the phone still configuring itself, and it can takes about 5-10 miniutes
so at this point I reboot back to fastboot on the phone and then unlock the bootloader then follow the rest of your instructions....
Click to expand...
Click to collapse
At this step, pls install a custom recovery ~> goto recovery mode ~> File Management, you'll see that there're system folders, like /sdcard/, check out if they're empty or not...
Bottom line: make sure firmware.zip has been flashed (do the flash command twice), verify step 4 and step 5 in #1

Hello,
Many thanks for your reply.
I did flash the OTA zip after modifying it. I can only think that I did not wait long enough after the boot animation, although i did wait approx 5 minutes or more.
Since posting here I have managed to install the OTA update but I used the alternative method here:
http://forum.xda-developers.com/showthread.php?t=2573479
I already had an unlocked bootloader and S-OFF so I skipped that part of the tutorial...
But I was unsuccessful the first time because I did not SUPERCID, as I read passed it..

[Q] Im stuck in recovery

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

lineages OS and twrp bootloop possible cause

Investigating right now why fresh twrp 3.2.1.0 and sideloaded lineageos 16 with addonsu, arm64 for oneplus2 does reboot fine but once you go into twrp and change time and language you and up with bootloop.
After installing twrp and setting timezone and language to your timezone and English (might be set), lineageOS 16 ROM sideload install does reset it to central time and no language selected setting.
Checked settings after first reboot, left at central and ended up in bootloop.
After successful install as in lineageOS howto (every step) and enabling developer option without touching any of the dev options, i shut down and manually booted to recovery vol down+power.
Didn't touch anything just clicked to reboot system and ended up in bootloop.
Another run from scratch.
Note1: Not using any lock mechanism during tests, no pattern etc., BT disabled, wifi setup done
Note2: I see no errors during sideload but i wonder if OEM unlock might be the problem which i executed every time.
Note3: It seems that visiting twrp recovery after successful install and various successful restarts from lineageOS (without visiting recovery) cause this bootloop and if yes, why?
Note4: I was able to boot lineageOS when disabling the offered prompt to install twrp app and the option to install it as system app, might this cause the bootloop without having gaps installed?
Now that i am not experiencing bootloop i enabled Developer Options and didn't touch anything in there. Shut down and Booted up succesfull afterwards.
Powered Off and manually entered twrp recovery. Rebooted successful out of twrp.
Enabled Advanced Restart in Dev Options and went with Restart and Recovery.
In twrp > Reboot > System successful booted.
Enable Root Access for Apps only and reboot into Recovery, from there reboot System successfully.
Just to make sure, shut down and Power up again, successfully.
Default USB configuration set to File Transfer and copy over contacts.vcf, turn off File transfer, import vcf, followed by a restart into recovery.
Again in twrp > Reboot > System > successful booted.
Time for, adb backup --twrp
Back in LineageOS install/update F-Droid.
Again in twrp > Reboot > System > successful booted.
Install adaway give root access and accept to reboot without going into twrp, successfuly.
Update hosts file in adaway and accept to reboot without going into twrp, successfuly.
Quick check, reboot through recovery went successful.
Taking a break from testing. Not sure what the bootloop cause is for now, except the twrp app install system offer?

Boot Animation Change Issue - Pixel 4a

Hello everyone.
So I've been having some trouble changing my boot animation in my Pixel 4a running Android 12. I have tried every method I possibly can, and nothing seems to work. My device is rooted, and the bootloader unlocked. I have all necessary drivers updated, debugging enabled, etc etc.
I have tried:
Boot Animation apps - Just give error messages
Rebooting the bootloader into recovery to flash the .zip - This option isn't available in my boot recovery
5-6 different file manager apps - all of them won't let me either delete the original bootanimation.zip file or copy/paste the new one I have ready to go
Using a windows based root file manager - same as above
Is htis an Android 12 issue? Since it was released relatively recently I just need to wait for an updated method?
Any help would be appreciated. Thanks.

DKM-Eby said:
Hello everyone.
So I've been having some trouble changing my boot animation in my Pixel 4a running Android 12. I have tried every method I possibly can, and nothing seems to work. My device is rooted, and the bootloader unlocked. I have all necessary drivers updated, debugging enabled, etc etc.
I have tried:
Boot Animation apps - Just give error messages
Rebooting the bootloader into recovery to flash the .zip - This option isn't available in my boot recovery
5-6 different file manager apps - all of them won't let me either delete the original bootanimation.zip file or copy/paste the new one I have ready to go
Using a windows based root file manager - same as above
Is htis an Android 12 issue? Since it was released relatively recently I just need to wait for an updated method?
Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
Have you also enabled r/w permissions for the system partition?

Droidriven said:
Have you also enabled r/w permissions for the system partition?
Click to expand...
Click to collapse
Every time I try with my root file manager it says "error changing permissions." I'll add a screenshot of what they currently are.
The error on the bottom is after I added the check mark in the Owner row, under the S column. The other ones were already set.

DKM-Eby said:
Every time I try with my root file manager it says "error changing permissions." I'll add a screenshot of what they currently are.
The error on the bottom is after I added the check mark in the Owner row, under the S column. The other ones were already set.
Click to expand...
Click to collapse
Put a check in the box beside "recursive" in the upper part, and tap "apply" then, in the lower part, check the box beside "recursive" then tap "apply".

Droidriven said:
Put a check in the box beside "recursive" in the upper part, and tap "apply" then, in the lower part, check the box beside "recursive" then tap "apply".
Click to expand...
Click to collapse
Still gives error while trying to apply.

DKM-Eby said:
Still gives error while trying to apply.
Click to expand...
Click to collapse
Boot to recovery and choose the option to "wipe cache partition", if you have custom recovery, wipe the cache partition and the dalvik cache partition(DO NOT factory reset). After wiping cache(s), reboot the device and then see if that helps.
Any time you make a change of any kind to the system partition, rebooting to recovery and then wiping the cache partition(s) and then rebooting is usually required in order for the changes to take effect.

Droidriven said:
Boot to recovery and choose the option to "wipe cache partition", if you have custom recovery, wipe the cache partition and the dalvik cache partition(DO NOT factory reset). After wiping cache(s), reboot the device and then see if that helps.
Any time you make a change of any kind to the system partition, rebooting to recovery and then wiping the cache partition(s) and then rebooting is usually required in order for the changes to take effect.
Click to expand...
Click to collapse
There are no options in my recovery mode to wipe the cache for anything. The only thing available in recovery was to factory reset.
I also noticed something in Magisk - I installed the boot animation changer module, and when running it, it says it does not support my sunfish kernel. So I'm wondering if my Pixel 4a is just completely unable to perform this action?

DKM-Eby said:
There are no options in my recovery mode to wipe the cache for anything. The only thing available in recovery was to factory reset.
I also noticed something in Magisk - I installed the boot animation changer module, and when running it, it says it does not support my sunfish kernel. So I'm wondering if my Pixel 4a is just completely unable to perform this action?
Click to expand...
Click to collapse
You don't have a stock recovery if you don't see the option to wipe cache partition. Can you post a screenshot of what your recovery looks like.
If Magisk says it doesn't support your kernel, you need to see if there is a custom kernel available for Pixel 4a that it does support.