Database Info

[2.1 ONLY] How to install a theme using Chewitt's Installer - XPERIA X10 Themes and Apps

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[2.1 ONLY]How to install a theme using Chewitt's installer.
Additional things to remember-
You need root. ONE CLICK ROOT FOR 2.1 LINK- http://forum.xda-developers.com/showthread.php?t=834428
You need to read all steps carefully.
Credits-
Me- For making this guide
Chewitt- For the damn awesome theme!
You- For thanking us and reading this and recommending to others.
Go to the theme file and click that. *REMEMBER TO RUN AS ADMINISTRATOR*
When you open it, it will look like this.
Type 1, Enter. Now as you can see mines shows -rwxr- it is meant to show -rwsr- you will need do the additional steps to get it to -rwsr- but if it shows
-rwsr- then you may continue normally.
Now make sure you have done what I have highlighted in red. *EVERYTHING HIGHLIGHTED IN RED IS IMPORTANT* Press any key to continue.
It will start backing up your applications.
Now type in 3 and press enter
Now make sure you have done what is highlighted in red.
It will start installing applications.
Press any key to continue
Press any key to continue.
Check your handset when pressing any key to continue because it may restart.
Alright do everything highlighted in red. Type 4 and press enter and then press continue and then press any key to continue.
Type 5 and press enter. Now when the installation is done your phone would've changed and it may enable USB storage...*GO TO YOUR HANDSET AND DISABLE USB STORAGE IF IT HAS ENABLED*
Now press any key to continue.
Now to install the Dark keyboard. Type in 6 and press enter.
Now press any key to remove the install file.
Press any key to continue.
Press 9 to exit.
What your phone will look like:

Additional Steps
Now you need to do those things before continuing. *DO NOT HAVE STORAGE ON*
You will need to read these because you will be copying each word.
Type in su and have your handset with you to grant super user permission. *DO NOT TYPE IN $*
Now copy the next code entirely how I have typed it. *DO NOT TYPE IN #*
Now copy the code I have typed in and press enter.*DO NOT TYPE IN #*
Type in exit then again type in exit.
It will show -rwsr- when your done with all the steps and you continue with steps.
*SCROLL ABOVE TO CONTINUE WITH STEPS*​

Great guide as always.

Chewitt said:
Great guide as always.
Click to expand...
Click to collapse
Thanks, and loving the new theme. Keep it up as well.

Phone continually restarts
After following this guide to the letter, my phone now continually restarts itself. Gets to the Sony Ericsson startup screen and then reboots. Have searched the forum for suggestions/solutions but have found nothing. Cannot reflash, unroot or restore as the device is not recognising the device. Any help appreciated.
Sorry if this is the wrong place to post this.

s-ozanne said:
After following this guide to the letter, my phone now continually restarts itself. Gets to the Sony Ericsson startup screen and then reboots. Have searched the forum for suggestions/solutions but have found nothing. Cannot reflash, unroot or restore as the device is not recognising the device. Any help appreciated.
Sorry if this is the wrong place to post this.
Click to expand...
Click to collapse
I am not sure why this is happening.
Was your phone rooted?
And did you have mass storage on?
I recommend posting in the Q n A section and your phone may be bricked.
It was a warning and what theme were you installing?

mine just gets stuck in sony ericsson screen and thats it, nothing happens after press 3 then continue and thats it, phone restart but wont boot, same thing happened with just the black bar mod, and the file i downloaded hasnt 9 options. it brick everytime
it is rooted and rwsr

so my phone is rooted and i did steps 1 and 2 but when i come to there, the first thing it says is that mount failed and then looks up a couple of files and says read only and then says press any key to do a fresh install... and even when i do tht it says the theme is installed and ready to use but nothing happens. Also a couple of the images are not displaying, donno if its just my comp or everyone else.
Any ideas?

saketh321 said:
so my phone is rooted and i did steps 1 and 2 but when i come to there, the first thing it says is that mount failed and then looks up a couple of files and says read only and then says press any key to do a fresh install... and even when i do tht it says the theme is installed and ready to use but nothing happens. Also a couple of the images are not displaying, donno if its just my comp or everyone else.
Any ideas?
Click to expand...
Click to collapse
I get the same as this.
And constantly a message saying adb is not a recognized command, mount errors, and when trying to install it says read only files
Only thing that happens is the keyboard installer works, everything else is missing.
Been trying for ages, using rooted X10 with 2.1

LususNaturae said:
I get the same as this.
And constantly a message saying adb is not a recognized command, mount errors, and when trying to install it says read only files
Only thing that happens is the keyboard installer works, everything else is missing.
Been trying for ages, using rooted X10 with 2.1
Click to expand...
Click to collapse
Read the additional steps.
It is not possible to install a theme without doing the first steps.
When you do step 1...
And it shows Rwxr and not rwsr you need to scroll down and do the additional steps first. I have even mentioned it.
Edit:
If by step 2 you mean the rwsr...
Then you need to have your handset when you type in SU so you can give super user permission.

Same steps for the 2.1 DarkBar???
Are these the exact same steps to install the DarkBar??
Thanks for all this and for being there!!

casamg said:
Are these the exact same steps to install the DarkBar??
Thanks for all this and for being there!!
Click to expand...
Click to collapse
I just downloaded the dark bar files to see if the installer is similar.
Basically it is the same but the installer will only install the framework.
You can just follow my additional steps for the first step if your device shows rwxr when you need to have rwsr to install it.
Things to do before installation:
Have root on your phone.
Make sure you read the READ ME.txt file before doing anything.
No one is responsible for your phone being bricked.
*NOTE* When your installing the CHMOD it is step 4 while in my additional steps its 7 because the guide is just showing how to use/install a theme with Chewitt's installer.
Step 1- Pre-install check and see if it is rwsr if it is not and shows rwxr then you need to do step 4 first.
Step 2(Additional)- You need to look at my additional steps which is the second post on the thread and do those steps.
Step 3- After being done it will show you that it has changed to rwsr if it does not show then you may do the pre-install check again to see.
Step 4- Now you need to type in 2 and press enter for the application backup.
Step 5- Now you need to type in 3 to install the framework which will install your dark bar. Your phone may switch off through the installation and make sure you off USB storage.
Step 6- You may exit now.
Step 7- If you do not like your dark bar then you may proceed back to the installer and type in 5 to restore the back up files.
And your welcome.

BIg thx, author 4 description of CHMOD.

mdma.xtc said:
BIg thx, author 4 description of CHMOD.
Click to expand...
Click to collapse
Your welcome

s-ozanne said:
After following this guide to the letter, my phone now continually restarts itself. Gets to the Sony Ericsson startup screen and then reboots. Have searched the forum for suggestions/solutions but have found nothing. Cannot reflash, unroot or restore as the device is not recognising the device. Any help appreciated.
Sorry if this is the wrong place to post this.
Click to expand...
Click to collapse
Great, now mine is doing this.
Looked like I had it working but now it keeps rebooting at the Se startup screen

zm4 said:
And your welcome.
Click to expand...
Click to collapse
Thanks a lot!! I'll try it today!!

Mine ia also cannot boot up, so I have to flash it.
Retry again, but failed. I notice that in step 2, there are error.
After checked, there are no /system/etc/semc/startupshow.
Guess that the structure is difference from the system you tested.
Use SEUS to reflash.
Question: How many time that the X10 can be flashed?

Have you attempted to go into the installer and restore back up...
The framework-res.apk file may be causing your problems...
I am not sure...

Yes, I guess so.
Today I try installed with "X10 Res Mods v1.1.5" from XperiaX10iUser after 3. - Install App, the mobile rebooted and stop at Sony Ericsson.
But I did not re-flash at this time , I found that adb can connect and give a shell.
So I mount /sdcard then restore the framework and it continue boot up to original.
As waste a lot of time then I copy the framework try it again and now it is working.
Mout the sd-card, for restoration
# mount -o rw -t vfat /dev/block/mmcblk0p1 /sdcard

Geronimo.X10 said:
Yes, I guess so.
Today I try installed with "X10 Res Mods v1.1.5" from XperiaX10iUser after 3. - Install App, the mobile rebooted and stop at Sony Ericsson.
But I did not re-flash at this time , I found that adb can connect and give a shell.
So I mount /sdcard then restore the framework and it continue boot up to original.
As waste a lot of time then I copy the framework try it again and now it is working.
Mout the sd-card, for restoration
# mount -o rw -t vfat /dev/block/mmcblk0p1 /sdcard
Click to expand...
Click to collapse
Thank you for your helpful post. I will add this to the thread tommarow and have you in credits.

Related

I CAN NO LONGER PROVIDE SUPPORT, NOR UPDATE THIS POST ANY MORE, AS I NO LONGER HAVE TIME DUE TO MOST OF MY TIME BEING SPENT AT WORK! SORRY
If you need help that would only take me a few seconds to answer, contact me on twitter @cubz90​
Here is a guide to Temproot and downgrade any HTC Desire HD Gingerbread Build
This method has been confirmed working for all DHD Gingerbread builds!
Please could you post the Exploit address when successfully rooted with fre3vo. Thanks
Thanks go to:
agrabren
aswethinkweiz
JSLEnterprises
Please make sure you have the phone's drivers installed on the computer you are using, otherwise this will not work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Temp Root:
1. Enable USB debugging on your phone and place your phone on CHARGE ONLY (If this doesn't work, try choosing 'HTC Sync' when connecting USB)
2. Download the DHD Downgrade folder and extract it to the root of your hard drive (usually this is the "C:\" drive on your computer)
3. Run the file named "RUN THIS FOR ROOT". A command prompt will open and will begin to do the adb steps for you.
Alternatively (If step 3 fails):
1. Open a command prompt (right click "Run as Administrator" is using Vista or W7) and locate the downgrade folder (type "CD C:\DHDDowngrade" minus the quotes in CMD)
2. Run the below commands (be sure to press enter after each line)
adb push fre3vo /data/local/tmp
adb shell chmod 777 /data/local/tmp/fre3vo
adb shell /data/local/tmp/fre3vo -debug -start FBB00000 -end FFFFFFFF
Click to expand...
Click to collapse
If the scan hangs, just reboot your DHD and start again.
You may not get all the messages (due to flushing issues when we kill adb), but if you get kicked back to your system command prompt, try "adb shell"
If you see '#' you successfully have temproot.
If you want to use Titanium Backup, you must do the following:
1. Download Busybox, su & fixsu.sh and Superuser.apk
2. Run the following commands in CMD...
adb push fixsu.sh /data/local/tmp
adb push su /data/local/tmp
adb push busybox /data/local/tmp
adb shell chmod 777 /data/local/tmp/fixsu.sh
adb shell chmod 777 /data/local/tmp/su
adb shell chmod 777 /data/local/tmp/busybox
Click to expand...
Click to collapse
3. Install Superuser.apk
4. Install Titanium Backup from the Market
5. Run the following commands in CMD:
adb shell
# cd /data/local/tmp
# ./fixsu.sh
Click to expand...
Click to collapse
If you see...
rm failed for /system/bin/su Read-only file system
Click to expand...
Click to collapse
...ignore it
You can now use Titanium to backup all User Apps + Data (You can backup System apps too)
If you don't want to go any further than rooting, and just want temproot to remove bloatware, you can also use Titanium backup to do that.
Temproot will be enabled until phone is rebooted.
Downgrade:
1. Create a goldcard:
1. Format SDCard to FAT32
2. Download Goldcard Helper from Android Market
3. Open Goldcard Helper with the SDCard in the phone, and you will see the mmc2 reverse CID
Note: Do not use the Copy feature in the app as this will copy the wrong CID!​
Alternate to the Goldcard helper app:
1. Open up a command prompt (Windows Key + R, type "CMD", press enter)
2. connect your phone as "charge only" and have usb debugging enabled
3. navigate the command prompt to the downgrade folder.
4. Type the following command:
adb shell cat /sys/class/mmc_host/mmc2/mmc2:*/cid
Click to expand...
Click to collapse
5. Select and copy the cid
Click to expand...
Click to collapse
4. Go to http://psas.revskills.de/?q=goldcard
5. Enter your email address and the mmc2 reverse CID that is showing on the Goldcard Helper app then submit it
6. The img file will be emailed to you, download and save it somewhere you will remember
7. Download this hex editor - http://mh-nexus.de/en/downloads.php?product=HxD
8. Open HxD hex editor on your computer by right-clicking it and clicking 'Run as Administrator'
9. Mount your SD card to your computer, preferably using a card reader but you can use your phone as well
10. Go to 'Extra' menu > 'Open Disk'. Select Removable Disk (which should be your SD card) under Physical Disk (and NOT logical disk), uncheck 'Open as Readonly' and click OK
11. Go to the 'Extra' > 'Open Disk Image' and open the goldcard image downloaded in Step 6. . Select '512 (Hard disks/Floppy disks)' as the sector size when prompted and click OK
12. In the goldcard image tab, go to 'Edit' > 'Select All' and then 'Edit' >'Copy'
13. In the 'Removable Disk' tab, highlight offset (line) 00000000 to offset (line) 00000170 including the 00000170 line and go to 'Edit' menu > 'Paste Write'
14. Click 'File' > 'Save' and accept any warning that you get
Click to expand...
Click to collapse
2. Place the stock 1.32 PD98IMG.zip on the root of your SDcard/Goldcard
4. Open the file in the folder named "RUN THIS FOR DOWNGRADE". The command prompt will opn and begin to do the adb steps for you.
Alternatively (If step 4 fails):
Run the below commands in CMD:
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/misc_version -s 1.31.405.3
adb reboot bootloader
Click to expand...
Click to collapse
5. You should see a white bootloader screen, press the power button to enter the bootloader and it should automatically start to detect the PD98IMG.zip file.
6. You will see a blue progress bar on the right of the screen while the file is being checked. You should now be asked to confirm if you want to install this ROM, press 'Volume Up' to confirm. Wait patiently while the ROM is installed.
7. Once the installation is complete, press the 'power' button to restart your phone.
You have successfully downgraded to stock 1.32
How to Root 1.32:
1. Download and install Visionary+ to your Desire HD
2. Open Visionary+ and choose "Temproot now". The screen may go black and may become unresponsive, please allow it to finish.
3. After temproot, choose "Attempt permroot now". This will attempt to permanently root your Desire HD. Your device should then reboot.
4. After reboot, you should successfully be rooted.
How to Radio S-Off & SimUnlock Your Desire HD - Thanks to jkoljo
How to Flash recovery with ClockworkMod
1. Search Android Market for a free app called 'ROM Manager'. Once found, install it.
2. Once it has been installed, launch 'ROM Manager' on your phone.
3. In ROM Manager, tap 'Flash ClockworkMod Recovery'. Tap on 'Desire HD' when it pops up.
4. Be patient as ClockworkMod is installed, as it can take quite some time. Once it has finished , you have ClockworkMod recovery installed on your phone.
You should now have stock 1.32, root, S-off, and CWM Recovery.
You can now flash a ROM using Clockworkmod
FAQs​
Q. How do I run CMD?
A. Windows Vista and 7 users: Press Start, type CMD. You should see CMD sppear, right click and 'Run as Administrator'. Windows XP users: Press Start, Press 'Run', type CMD, then click OK.
Q. How do I enable USB Debugging?
A. On your Desire HD go to Settings -> Applications -> Development -> Enable USB Debugging
Q. Why do I keep getting CID error in bootloader?
A. This is most often a problem with your goldcard. First make sure you have created a goldcard using the guide at the top of this post. If you have created a goldcard, format the SDCard using FAT32 and try again making sure you have followed each step very carefully. Also, make sure you have the .bin file on your SDCard after doing the adb steps.
Q. When going into bootloader it says "no image or wrong image"
A. This message will be displayed when files it is looking for cannot be found. Leave it to continue and it will update. If it displays this message after searching for PD98IMG.zip, then the file is damaged or you do not have it on your SDCard.
Q. Do I have to disconnect the phone from the computer before booting into bootloader?
A. Yes....Simplez
Q. I have tried many times to create the goldcard, but continue to get errors.
A. This could be because you are continuously making mistakes, or your SDCard cannot be made into a goldcard, try another SDCard.
More will be added when needed
Click to expand...
Click to collapse
Please press Thanks

Thanks, many are waiting for this information

Thank you Thank you Thank you !!! Got it working and loaded LeeDroid's ROM
WOW You guys are great.... thanks to all who have spent so much time and effort to crack 2.37...
I'm not very good sometimes at understanding all this programming stuff but after a full day of messing and redoing ... IT WORKS!!!
YYYeeeeeeee Hawwwwwwwww
Thanks again
aero star

4. Boot phone into Bootloader (hold volume down whilst power on), follow the steps and continue to update
what does this means ? i am in bootloader but can not see any update options, there are following options
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
any help please

Yeaaah it's work great !
Thanks !!!

ravian29 said:
4. Boot phone into Bootloader (hold volume down whilst power on), follow the steps and continue to update
what does this means ? i am in bootloader but can not see any update options, there are following options
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
any help please
Click to expand...
Click to collapse
Don't change any thing as far as I know It'll boot into "Fastboot" incase if it didn't choose "FASTBOOT"
It'll check Recvoery, Tp , etc. I forgot to name them.
Follow CuBz90's guide it works 100%. I downgraded n rooted n now running custom ROM.

Is there a way to gain root status in 2.37, so the phone can be backed up (via Titanium backup or similar) prior to the downgrade?
Failing that is there any other way to backup the phone?
I assume that when downgrading all data will be lost.

kindly reupload the "Download this ROM - Mirror" link as whenever i click it i get
-
404 Page Not Found
The page you requested was not found.

aypee3 said:
kindly reupload the "Download this ROM - Mirror" link as whenever i click it i get
-
404 Page Not Found
The page you requested was not found.
Click to expand...
Click to collapse
Both work for me

[Aek] said:
Is there a way to gain root status in 2.37, so the phone can be backed up (via Titanium backup or similar) prior to the downgrade?
Failing that is there any other way to backup the phone?
I assume that when downgrading all data will be lost.
Click to expand...
Click to collapse
You can backup apps with MyBackup, but you cannot backup the data as 2.37 cannot be rooted

Hellow, just want to confirmed it works! Happy happy joy joy! Thanks for all magicians here that made this possible!

I ve unbranded dhd do I need to make goldcard
mechanical engineer

I have added the additional step of going to SoftBank ROM into the official downgrade guide
I am still looking forward to getting a proper, universal root method for 2.37, but this will do for the time being.

gagan01 said:
I ve unbranded dhd do I need to make goldcard
Click to expand...
Click to collapse
Well every 2.37 is branded in some way, so you should not even be following this guide..

after downgrade..
when into boatloader Hboot
i can find menu:
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
but i can not select that...
just stuck
any help please?

Just leave it and it should start to update, if not, try factory reset first
Sent from my Desire HD using XDA Premium App

CuBz90 said:
Just leave it and it should start to update, if not, try factory reset first
Sent from my Desire HD using XDA Premium App
Click to expand...
Click to collapse
what that mean?
i can not into factory reset from bootloader menu...
volume button can not use...
anyone help?

finally i done it.thanks you man.

I bought dhd when it was on 2.2.. so I rooted it and after some time made ota to 2.37 build.. now phone is s-0ff and its unbranded .. do I still need to make gold card.. jkoljo pls help ...
mechanical engineer

Well this is not even my thread, why are you asking my help here?
Anyway, you do not need to make a goldcard, and you do not even need any downgrade guide. Just put stock 1.32.405.6 PD98IMG.zip (get it from my downgrade guide) into your SD card and reboot to bootloader. Accept the update and make a cup of coffee.

Moderator Edit 12/8/12
Do not use this this method twrp is officially supported for the one x. Download goo manager from the market or check the dev section.
It is not my intention to step on the toes of other people who have been more than helpful when it comes to questions relating to the installation of this or that.
Although I am reasonably familiar with many of the installation procedures when it comes to ROMs and Kernels, including Clockworkmod Recovery, etc., I am still a bit hesitant because I simply want to make sure that I am not making a mistake. After all, we spend lots of money on our phones, and the slightest error can be permanent.
I respect and admire all the developers who work tirelessly to make our lives a little bit better, and who often fulfill our ongoing need to “fiddle” with our phones. Thank you!
That being said, here is a detailed explanation of how to install Clockworkmod Recovery.
First, your bootloader must be unlocked. It doesn’t matter if you have the “TAMPERED” entry; this procedure will still work. Second, you must also have all necessary mobile phone drivers installed, including ADB, ADB drivers, and fastboot. From this point forward, I will call all these files your “Fastboot” files. If you don’t have these files, you can download them by clicking on the link at the end of this post.
At this point I’m assuming you’ve placed your Fastboot files in a separate folder within the root directory of your PC (the “C” drive?). I put these files in a folder called fastboot, but it really doesn’t matter, as long as you remember the location.
Here’s an image from my Windows Explorer screen to give you an idea of what I did:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So, here we go …
Download the Clockworkmod Recovery image file and change the name to CWM.img. This is an easy name to remember, which will help further along in these instructions.
Place your newly-named CWM.img file in the directory where your Fastboot files are located.
Power down your device.
While holding VOLUME DOWN, press and hold the POWER button for a few seconds. Continue to hold VOLUME DOWN until your bootloader screen appears.
Somewhere in the middle of your bootloader screen will be seven entries entitled FASTBOOT, RECOVERY, FACTORY RESET, CLEAR STORAGE, SIMLOCK, IMAGE CRC, and POWER DOWN.
Using your VOLUME keys, make sure FASTBOOT is highlighted, and then press the POWER button once.
You should now be in the FASTBOOT Bootloader screen. On my ONE X, and I’m assuming the same for everyone, the word FASTBOOT will be highlighted with a RED background. Either way, it should be highlighted.
Connect device to your PC via USB cable.
If all is going well, the word FASTBOOT should now say FASTBOOT USB. From this point forward, do not touch the device.
Open a Command Prompt window on your PC (Press the Start button, and in the search field type cmd, and then press Enter). Here’s an example of how your Command Prompt window may look:
You must now change the directory to where your Fastboot files are located. As I mentioned above, mine are in the directory c:\fastboot. Therefore, I would need to type the following command in the Command Prompt window: cd c:\fastboot
The “cd” refers to “change directory,” while the rest is where your Fastboot files are located. Here’s how your Command Prompt window will look like after you’ve typed the above, and BEFORE you press the Enter key.
Here’s an example of how your Command Prompt window will appear AFTER you press the Enter key:
Next you need to type the following: fastboot flash recovery CWM.img
Renaming the file to CWM.img simplifies the above entry because this name is easy to remember.
Here’s how your Command Prompt window will appear BEFORE you press the Enter key:
Now press the Enter key and let the program run.
The entire installation/flash will take only a few seconds. When complete, your Command Prompt window will return to your fastboot directory (see image below).
Ignore the error in my image above, the line called error: cannot load ‘CWM.img’
This error message appeared ONLY because I didn’t want to install Clockworkmod Recovery on my device a second time. Hey, if it ain’t broke, don’t fix it, right?
Reboot your device.
DONE! You now have Clockworkmod Recovery on your phone.
These instructions are available in PDF format by clicking on the link at the end of this post.
Peter
Here's the link to the Clockworkmod Recovery file:
Clockworkmod Recovery Image
Detailed Instructions
Fastboot Files

Thanks for the excellent guide, Peter!
We were all hardcore newbies at one point and while it's annoying to see them ask redundant questions or ones that have been answered in the first post of a thread, you have to have some sympathy for them. Especially when they do something like get a soft-bricked device and begin to panic.

Thanks a lot for this!!
Would this work similarly on Linux or Mac?
Cheers!

THANK YOU this was very helpfull

Mac or Linux, I simply don't know ...
zmanw330 said:
Thanks a lot for this!!
Would this work similarly on Linux or Mac?
Cheers!
Click to expand...
Click to collapse
Regretfully, I have little to no knowledge concerning Mac and Linux, so I don't know if it would work. Sorry.
Perhaps others can answer this question.
Peter

zmanw330 said:
Thanks a lot for this!!
Would this work similarly on Linux or Mac?
Cheers!
Click to expand...
Click to collapse
Almost identical. On my Ubuntu machine I just need to type "sudo fastboot flash recovery xxx.img" and boom!
I can't see Macs being too different.

PeterHTC said:
First, your bootloader must be unlocked.
Click to expand...
Click to collapse
has this been done? have I missed something in the past day?

So far this is only for Rogers version

Peter i am following your instructions to a tee but when i try to push cwm i get the same error that shows up on your screen, i am rooted and bootloader unlocked. Can someone help
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott> cd c:\fastboot
c:\fastboot>fastboot flash recovery CWM.img
error: cannot load 'CWM.img'
c:\fastboot>

fastboot flash recovery recovery.img
Sent from my HTC One XL using xda premium

No, you didn't miss anything ... so far
fionic said:
has this been done? have I missed something in the past day?
Click to expand...
Click to collapse
No, you didn't miss anything so far. The bootloader on AT&T units cannot yet be unlocked, but I'm sure it's only time. Once unlocked, then you can follow the installation instructions.
Peter

Peter said change the file name to CWM

I hope I'm not patronizing, but ...
sm625614 said:
Peter i am following your instructions to a tee but when i try to push cwm i get the same error that shows up on your screen, i am rooted and bootloader unlocked. Can someone help
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott> cd c:\fastboot
c:\fastboot>fastboot flash recovery CWM.img
error: cannot load 'CWM.img'
c:\fastboot>
Click to expand...
Click to collapse
I hope I don't insult you, but did you connect the phone to your PC via USB? The reason I ask is that I got my error message because I disconnected my phone prior to hitting the Enter key. As I mentioned, I didn't want to install it a second time and risk doing something harmful.
Did you also get FASTBOOT USB highlighted on your device after you plugged it in?
Peter
Addendum: Don't forget that these entries in your Command Prompt are case sensitive. Capital letters must remain as capitals, and small letters as small ... exactly as shown in my instructions. Again, I hope I'm not patronizing anyone. That's not my intention.

Of course your not insulting me, your just being detailed lol. The phone is 100% connected to the computer via USB. I am in fastboot mode with FASTBOOT USE highlighted in red. I am following you instructions perfectly and i got the same error. Do you think i should reinstall htc sync to reinstall the drivers. I am quite lost here on why this is not working.

Did you ...
sm625614 said:
Of course your not insulting me, your just being detailed lol. The phone is 100% connected to the computer via USB. I am in fastboot mode with FASTBOOT USE highlighted in red. I am following you instructions perfectly and i got the same error. Do you think i should reinstall htc sync to reinstall the drivers. I am quite lost here on why this is not working.
Click to expand...
Click to collapse
One thing I should have included in my first post (I will amend it shortly), is a link to the actual Clockworkmod Recovery file, which is currently available on another thread.
Did you download THAT file?
Peter
Addendum: Clockworkmod Recovery Files link now included in original post
Addendum 2: Re-installing HTC Sync might be helpful. It's what I would eventually do.

YES i have that file and i renamed it to the CWM.img name that you recommended. What do you think i should do?

I changed the first image in the original post ...
I changed the first image in the original post. It now includes the Clockworkmod Recovery file, marked as CWM.
Peter

Hmm, I would ...
sm625614 said:
YES i have that file and i renamed it to the CWM.img name that you recommended. What do you think i should do?
Click to expand...
Click to collapse
Well, I'm not entirely sure. What I would do is start all over again after restarting your PC and Phone. If it does not work then, uninstall and reinstall HTC sync. After that, I'm stumped. Sorry.
Peter

sm625614 said:
Of course your not insulting me, your just being detailed lol. The phone is 100% connected to the computer via USB. I am in fastboot mode with FASTBOOT USE highlighted in red. I am following you instructions perfectly and i got the same error. Do you think i should reinstall htc sync to reinstall the drivers. I am quite lost here on why this is not working.
Click to expand...
Click to collapse
Do you have a file named "CWM.img" in the same folder as fastboot? That part of the command is telling fastboot which file to install. Make sure the image file is named correctly, or you can alter the command to reflect the name of the file.

I think you should write it into the title and the post saying for now this is only for Rogers users. It might cause a problem bbecause you said even if the bootloader ssays tampered it'll work. And I'm on att and it says tampered bbut this won't work for ATT HOX.
Just a precaution
Sent from my HTC Vivid 4G LTE using Tapatalk 2

Root Guide for the T-Mobile LG V10
Read Post #2 - Great Info​
Before we start, I like to mention that I did not create any of these files and I do not take credit for the work done. All I am doing is putting everything in one place and some helpful things that I had to google. This effort is mainly to make the process easier and more efficient as opposed to having to have several tabs or windows open to do it. I will make sure the proper thanks are given at the bottom
Click to expand...
Click to collapse
Instructions Start Here:
Warning - This will erase user data so you will have to set everything back up again! Always BACK UP YOUR DEVICE!!
1. Download the following tools for this process: adb-setup-1.4.3.exe, & twrp-2.8.7.1-h901.img, & UPDATE-SuperSU-v2.46.zip
Alternative ADB and Fastboot Option - (I Prefer) [GUIDE] Install Android SDK Standalone [ADB][30 Dec 2015] for Android SDK Standalone if you are interested
2. Install adb-set-up-1.4.3.exe to install the universal adb driver (Creates adb folder in C:\ if you don't already have adb setup)
3. Go to settings, about phone, software info and tap build number 5x to enable Developer Options
4. Check the Enable OEM unlock box to enable OEM Unlock
5. Enable USB debugging
6. Plug phone into the computer
7. Click on USB options on the phone and change it to PTP (USB Debugging will connect - Authorize Your Computer when prompted from phone)
Screenshots of Enabling USB Debugging and OEM Unlock
1.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2.
3.
4.
5.
6.
7. Open a Command Window and change directory to
Code:
[B]C:\adb[/B]
or if you have Android SDK type this below
Code:
[B]C:\Android\platform-tools[/B]
and type
Code:
[B][SIZE="3"]adb devices[/SIZE][/B]
8. You will Get Prompted after adb runs - Allow USB Debugging
8. From the Command Prompt, verify adb sees the device connected -
Open Command Prompt
Code:
cd C:\adb
Code:
adb devices
9. Reboot into the bootloader in command prompt by typing: adb reboot bootloader
10. You will now unlock the bootloader, verify, and Install TWRP
Note* - Make sure you copied twrp-2.8.7.1-h901.img into the C:\adb Folder already
Code:
[SIZE="3"]fastboot oem unlock
fastboot getvar unlocked
fastboot reboot-bootloader
fastboot flash recovery twrp-2.8.7.1-h901.img
fastboot boot twrp-2.8.7.1-h901.img[/SIZE]
11. You should be in TWRP Currently.
12. Reboot the device, it will delete user settings, so you need to repeat steps 3-8 to get adb set-up again
13. Now place UPDATE-SuperSU-v2.46.zip om your phone
14. Reboot into recovery
15. Back up YOUR EFS PARTITION
16. Wipe Cache and Dalvick Cache 3x
17. Flash UPDATE-SuperSU-v2.46.zip
18. You have successfully Unlocked the bootloader and Rooted your Device!!
19. SuperSU will prompt you to give tmobile.pr.adapt root privlidges, DENY
20. Navigate with Root Explorer to /system/priv-app/AdaptClient and rename AdaptClient.apk to AdaptClient.apk.bak and reboot
21. Finally, All done
Click to expand...
Click to collapse
USEFUL ROOTING LG V10 - by: Glenn Silvasy
Give Thanks To:
@KAsp3rd - http://forum.xda-developers.com/tmobile-lg-v10/development/recovery-unofficial-twrp-t3239740
@Chainfire - For Super User
@mikeyinid - Flashable Stock Image
@TheJesus - Providing img files for stock ROM, and OEM unlock Guide
@Snoop05 - ADB Drivers and Fastboot
And Anyone else that was missed!

Updated [31 Dec 2015]
References, Guides and Great Information - Please Read​
LG-H901 Stock .img Files (Boot, System, and Recovery)
Go Here
LG-H901 Stock Flashable ZIP in TWRP
Go Herehttp://forum.xda-developers.com/lg-v10/development/lg-h901-stock-images-device-restore-t3241170http://forum.xda-developers.com/lg-v10/development/lg-h901-stock-images-device-restore-t3241170
TWRP
Go Here
ADB and Fastboot
Go Here #1
Go Here #2 - This can be reached from Go Here #1, but I posted it for a direct link to the tool just in case you miss it!
Android SDK Standalone Tools for ADB and Fastboot Devlopment Setup Guide
Go Here
Can't Get Into the Bootloader - Enter Fastboot Mode
Go Here
These links will have all the files you need in case you encounter any issues and I will also try to answer any questions within the scope of my knowledge. I been doing this for a while and there are tons of smart people on XDA. Please search for the question you want to ask to avoid issues, however, I do not believe in biting someones head off either. Researching is how you learn!! :good:

16. Wipe Cache and Dalvick Cache 3x
Click to expand...
Click to collapse
You seriously do not need to do that, this isn't 2010. In fact, if you ever do that when Xposed is installed, you'll cause a bootloop.

siraltus said:
You seriously do not need to do that, this isn't 2010. In fact, if you ever do that when Xposed is installed, you'll cause a bootloop.
Click to expand...
Click to collapse
Actually never caused a bootloop period...at worse it optimized all the apps installed which takes time, but hey thanks for the uneeded criticism
Edit: Also good thing xposed is not even a factor anyway. Sometimes you can not help being ignorant
Sent from my LG-H901 using Tapatalk

bdorr1105 said:
Actually never caused a bootloop period...at worse it optimized all the apps installed which takes time, but hey thanks for the uneeded criticism
Edit: Also good thing xposed is not even a factor anyway. Sometimes you can not help being ignorant
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
I'm opening my prompt within the folder adb installed to (C:\adb), adb devices command isn't finding anything. I have the necessary things ticked in developer options. Driver issue maybe? thanks

I never did numbers 15, 16 & 20. Not even sure what number 20 is for. Care to explain?

baySF said:
I never did numbers 15, 16 & 20. Not even sure what number 20 is for. Care to explain?
Click to expand...
Click to collapse
Your EFS partition contains your IMEI number and modem partition that allows you to connect to LTE and data services. This happens on Samsung devices, although rare, it does happen. It is good to just back it up just in case you flash and something happens to that partition, your phone essentially becomes a paper weight. I have always wiped cache and dalvick before flashing anything, feel free to do it if you like, not required.. Lastly, when you have root, that app is a T-Mobile app trying to request root permissions, do not allow it. It is an uneeded app. The only useful T-Mobile apps are the Visual Voicemail, Mobile Hot Spot and T-Mobile My Account.

sleekgreek said:
I'm opening my prompt within the folder adb installed to (C:\adb), adb devices command isn't finding anything. I have the necessary things ticked in developer options. Driver issue maybe? thanks
Click to expand...
Click to collapse
After you unlocked developer settings and checked USB Debugging, did you remember to change your connection from MTP to PTP, once you do that it should prompt you on the phone to allow the connection

bdorr1105 said:
After you unlocked developer settings and checked USB Debugging, did you remember to change your connection from MTP to PTP, once you do that it should prompt you on the phone to allow the connection
Click to expand...
Click to collapse
Yes all checked, I never get the prompt though. Also in the device manager I'm seeing The yellow exclamation for "abd interface". This is such a simple process And I've been jacking with it for awhile. I've run the 15 sec ADB several times already. On windows 10 btw
edit: changing to PTP also

sleekgreek said:
Yes all checked, I never get the prompt though. Also in the device manager I'm seeing The yellow exclamation for "abd interface". This is such a simple process And I've been jacking with it for awhile. I've run the 15 sec ADB several times already. On windows 10 btw
edit: changing to PTP also
Click to expand...
Click to collapse
I am on windows 10, so the adb driver is not installed. Did you run the universal adb driver I have posted in the OP. Run that, then ensure your phone is on PTP. If you still have that yellow exclamation point, right click, uninstall driver, then scan for hardware changes and once the driver is installed correctly, you will be good to go

bdorr1105 said:
I am on windows 10, so the adb driver is not installed. Did you run the universal adb driver I have posted in the OP. Run that, then ensure your phone is on PTP. If you still have that yellow exclamation point, right click, uninstall driver, then scan for hardware changes and once the driver is installed correctly, you will be good to go
Click to expand...
Click to collapse
adb-set-up-1.4.3.exe , yes I've installed that several times. I go to that installed folder (C:abd) and open my command prompt from within it. Maybe I'll just get the sdk again, seems like a real simple issue I can't get sorted. Freaking aggravating

sleekgreek said:
adb-set-up-1.4.3.exe , yes I've installed that several times. I go to that installed folder (C:abd) and open my command prompt from within it. Maybe I'll just get the sdk again, seems like a real simple issue I can't get sorted. Freaking aggravating
Click to expand...
Click to collapse
Well adb wont work unless the driver is working, in device manager, if you have the yellow exclamation point, it wont work. You should have seen the Google ADB driver installer come up like a normal windows program installation. Your driver is giving you problems
Try the attached drivers, just extract the zip and point the computer to look in the location of the extracted folder. See if it makes the exclamation go away

bdorr1105 said:
Well adb wont work unless the driver is working, in device manager, if you have the yellow exclamation point, it wont work. You should have seen the Google ADB driver installer come up like a normal windows program installation. Your driver is giving you problems
Try the attached drivers, just extract the zip and point the computer to look in the location of the extracted folder. See if it makes the exclamation go away
Click to expand...
Click to collapse
Thats a no go also, it's saying windows was unable to install. Thanks for the help, I have to crash though, down to 4 hours sleep before work because of this phone lol. I've never had this issue before, maybe tomorrow I can get it sorted out. thanks again

Running fastboot oem unlock will always wipe your user data

KAsp3rd said:
Running fastboot oem unlock will always wipe your user data
Click to expand...
Click to collapse
Thanks for that info, I am surprised it wipes your data or even touches the user partition. Never would have guessed it was from oem unlock
Sent from my LG-H901 using Tapatalk

bdorr1105 said:
Your EFS partition contains your IMEI number and modem partition that allows you to connect to LTE and data services. This happens on Samsung devices, although rare, it does happen. It is good to just back it up just in case you flash and something happens to that partition, your phone essentially becomes a paper weight. I have always wiped cache and dalvick before flashing anything, feel free to do it if you like, not required.. Lastly, when you have root, that app is a T-Mobile app trying to request root permissions, do not allow it. It is an uneeded app. The only useful T-Mobile apps are the Visual Voicemail, Mobile Hot Spot and T-Mobile My Account.
Click to expand...
Click to collapse
Is there a way to check if your IMEI was wiped? I still have data and can still send messages and makes calls but whenever I'm at work, I'll always get "voice access restricted" and I never got that on my nexus 5. I also lose connection to my Wi-Fi at work and at home randomly because it says "avoided poor connection". Granted all I have to do is turn Wi-Fi off then back on but it's very annoying. Again, never happened on my nexus 5.

baySF said:
Is there a way to check if your IMEI was wiped? I still have data and can still send messages and makes calls but whenever I'm at work, I'll always get "voice access restricted" and I never got that on my nexus 5. I also lose connection to my Wi-Fi at work and at home randomly because it says "avoided poor connection". Granted all I have to do is turn Wi-Fi off then back on but it's very annoying. Again, never happened on my nexus 5.
Click to expand...
Click to collapse
If you can access LTE than you are solid.. Trust me you will know, you will get rejected from the network.. It is in settings>about>status it will say 0 or be blank if it missing... Rather be safe than sorry
Sent from my LG-H901 using Tapatalk

bdorr1105 said:
Actually never caused a bootloop period...at worse it optimized all the apps installed which takes time, but hey thanks for the uneeded criticism
Edit: Also good thing xposed is not even a factor anyway. Sometimes you can not help being ignorant
Click to expand...
Click to collapse
Clearing Dalvik bootlooped both my G4 and my V10 as well as others with Xposed installed, so I'm passing the warning, no need to be butthurt. Thanks for calling me ignorant, stay classy!

siraltus said:
Clearing Dalvik bootlooped both my G4 and my V10 as well as others with Xposed installed, so I'm passing the warning, no need to be butthurt. Thanks for calling me ignorant, stay classy!
Click to expand...
Click to collapse
I cleared cache and dalvick 3 times after installing xposed, but xposed was updated... Look at how you decided to tell me, in a condescending manner so maybe when I explained my side in the aggressive manner you did which was unnecessary, but anyway, learn to be classy before you ask someone else to be classy. Have a great week and merry Christmas bud
Sent from my LG-H901 using Tapatalk

bdorr1105 said:
I cleared cache and dalvick 3 times after installing xposed, but xposed was updated... Look at how you decided to tell me, in a condescending manner so maybe when I explained my side in the aggressive manner you did which was unnecessary, but anyway, learn to be classy before you ask someone else to be classy. Have a great week and merry Christmas bud
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
Aggressive? Condescending? Wow. You need to check your ego at the door, buddy, it gets bruised way too easily.

Android SDK - Powerful tool and easy to set up for use with your Android Device
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am putting this together for some who may be confused on how to set this up. I love Android SDK, have been using it for ever and once it is setup, maintenance is extra easy. There are 100 ways to skin a cat with ADB tools and development tools. This is my personal choice, go about it how ever you want. This tool is well maintained and always updated so its a big reason I use it. Great support and a great and powerful tool
Click to expand...
Click to collapse
Part 1. Follow These Steps Below - (Preparation)
Download Links For Tools
1. Java SE Development Kit (JDK)
2. Android SDK Tools Only - Download Only, Do Not Install yet
If You Choose Windows for example
3. Universal ADB Drivers - Instructions Here
Click to expand...
Click to collapse
How to Install and Set-up
1. Install Java SE Development Kit (JDK) from Start Here section if you have not yet
2. Launch Android SDK installer you downloaded up above in Download Links
3. During install - Set Installation Path to
Code:
C:\Android\
4. After Installation is Complete, run SDK Manager.exe
5. Install 5.1.1 and 6.0 since these are the APIs for all current Devices. Should not really see anything less than 5.1.1
Note* - Just put a check box where you see the red circles in the picture. The reason I have Tools (Preview Channel) is because I updated to the 25.0.1 RC2 SDK Tools, however, that is not required. You can choose 24.4.1 and it will be fine. It will say installed where as mine does not in the picture because I chose to use 25.0.1 RC2
6. Let all updates install to completion - This could take a while depending on your internet connection
Click to expand...
Click to collapse
The Computer and Phone are now prepped for you to start the whole ADB Process
Click to expand...
Click to collapse
Part 2. Verifying ADB is set up properly and Working
IMPORTANT - Make sure you have already enabled developer options and USB Debugging or you will not see the below results
1. Open Command Prompt and Change directories to your platform-tools folder. This is where all the adb files are located. See Below
In Command Prompt Type - Refer to Part 3 so you no longer need to Change Directory
Code:
cd c:\Android\platform-tools
2. In Command prompt type
Code:
adb devices
You Should get Prompted to Allow USB debugging - Ignore if You Already Have Done This
3. If your output shows your device attached like below, then you are good to go!!!
and
YOU ARE FINISHED!!! Below is a command to get into the bootloader if interested!! Good Luck
Click to expand...
Click to collapse
Part 3. Environment Variables - No need to Change Directory in Command Prompt Anymore (This is if you want to - Not Required)
1. Press Win+R, then type
Code:
sysdm.cpl
2. Click Advanced Tab
3. Click Environment Variables Button
4. Under System Variables, find Path, click to highlight it and then hit the edit button
Windows 8
Windows 10
5. Go to the end of the Variable Value and add the following exactly as you see it in the code box below
Code:
;C:\Android\platform-tools
Windows 8
Windows 10
6. Click OK to accept the changes you just added
7. Open Command Prompt again to verify by pressing Win+R and type cmd and hit enter
8. Once Command Prompt is open -> Simply type adb devices with your device connected with USB Debugging already enabled
9. If you did everything correctly, there is no need to change paths anymore
Click to expand...
Click to collapse
Getting into the Bootloader
In Command Prompt Type:
Code:
adb reboot bootloader
Thanks To:
@Ashraf - Images used for Environment Variables - Not all were his since the guide was modified
@[B]Snoop05[/B] - ADB Drivers and Fastboot

Reserve if Needed

Thank you so much for this - can i ask what's the size of the SDK manager files which we are supposed to download? For some reason it downloads in 86 kb/s speed (normaly 5-6 mb/s) so I just wanted to know if i'm going to wait a long time

Peccoskaify said:
Thank you so much for this - can i ask what's the size of the SDK manager files which we are supposed to download? For some reason it downloads in 86 kb/s speed (normaly 5-6 mb/s) so I just wanted to know if i'm going to wait a long time
Click to expand...
Click to collapse
Hey the installer size is 145mb. I was able to download it in 15 seconds
Updating sdk manager will take a while. I am not sure of the file size... It will take a while... You only have to do this once. Updates after this will be quick
Sent from my LG-H901 using Tapatalk

bdorr1105 said:
Hey the installer size is 145mb. I was able to download it in 15 seconds
Updating sdk manager will take a while. I am not sure of the file size... It will take a while... You only have to do this once. Updates after this will be quick
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
I've tried it many times.... i have enough space on my drive, but everytime i try to download this one and only part, prints out this error message....why do i always have so many problems with it

Peccoskaify said:
I've tried it many times.... i have enough space on mi drive, everytime i try to download this one and only part it prints out this error message....why do i always have to have so many problems with it
Click to expand...
Click to collapse
Lol you and me both bro, but you don't have to install that, that is optional, the rest looks good. You should be able to use it now
Edit: looks like a network issue or the repository is down... That will work itself out.. Right now, it is not required
Sent from my LG-H901 using Tapatalk

This is seriously getting ridicolous - Now everything is downloaded, cmd sees the device I have every stupid thing set-up and still....phone only reboots when i type - adb reboot bootloader -
Shell I record it for you?
Edit:
I did record it -

Peccoskaify said:
This is seriously getting ridicolous - Now everything is downloaded, cmd sees the device I have every stupid thing set-up and still....phone only reboots when i type - adb reboot bootloader -
Shell I record it for you?
Edit:
I did record it -
Click to expand...
Click to collapse
Sounds like your bootloader is borked, you should always be able to get into...Were you able to flash TWRP successfully? Not sure where you went wrong, I would try to push boot.img again, you should have a recovery
Go Here

bdorr1105 said:
Sounds like your bootloader is borked, you should always be able to get into...Were you able to flash TWRP successfully? Not sure where you went wrong, I would try to push boot.img again, you should have a recovery
Go Here
Click to expand...
Click to collapse
I followed steps till the one i got stuck in, so no i did not flash TWRP :/ or anything else. - It's weird that it is broken because it's new phone and i did not do anything to it, expect for right now :/ But sure I'll try

Peccoskaify said:
I followed steps till the one i got stuck in, so no i did not flash TWRP :/ or anything else. - It's weird that it is broken because it's new phone and i did not do anything to it, expect for right now :/ But sure I'll try
Click to expand...
Click to collapse
I think your bootloader may still be locked
Have you done this? Make sure USB Debugging is enabled, OEM Unlock is checked, You are in PTP, type adb devices and verify it sees your device then do the following Next:
nvm edited out got ahead of myself

bdorr1105 said:
I think your bootloader may still be locked
Have you done this? Make sure USB Debugging is enabled, OEM Unlock is checked, You are in PTP, type adb devices and verify it sees your device then do the following Next:
nvm edited out got ahead of myself
Click to expand...
Click to collapse
If you look at the video you can see that i have both on and PTP too - without PTP cmd won't see my device...i think
oh sorry

Peccoskaify said:
If you look at the video you can see that i have both on and PTP too - without PTP cmd won't see my device...i think
oh sorry
Click to expand...
Click to collapse
Have you had any luck?
Sent from my LG-H901 using Tapatalk

bdorr1105 said:
Have you had any luck?
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
Nope :/

Is there way to flash some LG stock android in my phone so it will have bootloader? :/ - I'm not very good in english so i don't even know what to search for :/

Peccoskaify said:
Is there way to flash some LG stock android in my phone so it will have bootloader? :/ - I'm not very good in english so i don't even know what to search for :/
Click to expand...
Click to collapse
Yea I am looking into it the v10 is hard to find anything
Sent from my LG-H901 using Tapatalk

Peccoskaify said:
Is there way to flash some LG stock android in my phone so it will have bootloader? :/ - I'm not very good in english so i don't even know what to search for :/
Click to expand...
Click to collapse
Ok try this
1. Power phone off
2. Hold volume down and power together 3. Once LG Logo appears, let go of power for 1 second and press power again.. Never let go of volume down
4. Then chose to factory reset
This may resolve the issue so you can retry again
Sent from my LG-H901 using Tapatalk

bdorr1105 said:
Ok try this
1. Power phone off
2. Hold volume down and power together 3. Once LG Logo appears, let go of power for 1 second and press power again.. Never let go of volume down
4. Then chose to factory reset
This may resolve the issue so you can retry again
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
Did it, nothing changed, is this reason for refund?

Peccoskaify said:
Did it, nothing changed, is this reason for refund?
Click to expand...
Click to collapse
Ok another method
1. Install Terminal Emulator
2. Open the Terminal
3. Type# su
4. Type# reboot-bootloader
This should go straight to the bootloader, if it doesn't, I am at a loss

bdorr1105 said:
Ok another method
1. Install Terminal Emulator
2. Open the Terminal
3. Type# su
4. Type# reboot-bootloader
This should go straight to the bootloader, if it doesn't, I am at a loss
Click to expand...
Click to collapse
I just can't anymore - so far thank you for your help, even though it's never year you are willing to help, not many people would waste time with me

Peccoskaify said:
I just can't anymore - so far thank you for your help, even though it's never year you are willing to help, not many people would waste time with me
Click to expand...
Click to collapse
Thats not correct, su did not work, you should have a # symbol before the command, guess not being rooted doesn't help
edit: connect your phone to the computer and type the same command
I think strangely it is just recognizing adb reboot and omitting the bootloader, so try adb reboot-bootlader when connected to the computer

Code:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DISCLAIMER
I am not responsible for bricks, cats being both alive and dead, heat death of the universe, etc. I've attempted to minimize the chance of damage, but you will use this guide at your own risk.
Thanks to [mention]ejwith9953[/mention] for getting TWRP working correctly
Thanks to [mention]forgottonhacker[/mention] for proofreading and formatting
ABOUT
WINDOWS ONLY GUIDE
THIS GUIDE IS FOR THE PEOPLE SEEKING TO INSTALL TWRP AND OBTAIN A FIX FOR SOFT-BRICKED DEVICES
STEP 1
On a DESKTOP:
Download CURE_4 and extract to desktop (or a folder to your preference).
[Download Links at Bottom of Post]
On your PHONE:
Go to Settings > About phone > tap build number, till it says your a developer.
Go to Settings > Developer Options and enable OEM unlock, and USB debugging
Reboot Device
STEP 2
Connect Device to PC
Open your extracted folder and run START_HERE.bat
Let it run, it will copy files, execute temp root exploit, and open a new CMD window.
In the new window, copy/paste commands individually.
Code:
adb shell
run-as -s1
su
dd if=/data/local/tmp/twrp.img of=/dev/block/mmcblk0p25
When you see the following:
Code:
26404+0 records in
26404+0 records out
Get ready to pull out the battery ( reboot recovery does NOT work )
Put the battery back in and hold the PWR and VOL UP at the same time, when you see Alcatel splash let go of power but continue to hold volume up.
Say hello to TWRP!
STEP 3
Now we are going to install SuperSU it’s easy from here don’t fret!
IMPORTANT
BACKUP /SYSTEM PARTITION IN TWRP AND MAKE A COPY ON YOUR PC
Now that you have a backup go back and tap install. Tap on "up a level" then sdcard.
Find SuperSu.zip and swipe to install!
Reboot system! (this may take a few minutes so don’t freak out)
Verify that SuperSu got installed.
Go back to the extracted folder on your computer and run CLEANUP.bat
SOFT FIX
Boot up to custom recovery tap wipe > advanced wipe
Select Dalvik cache and Cache, then SWIPE to wipe
Go back to the Home Screen
Tap Advanced > fix permissions and Swipe
REBOOT AND ENJOY
If this fix did not work for you please do contact me as I have another method, I will be putting up a debloated version of the ROM soon.
I will be adding more to the guide, so make sure to turn on your notifications!
DOWNLOADS
Stock-ish ROM EXTRACT FROM ZIP FIRST! then flash as /system
password: fax
Dropbox  Google  Box.net  Mega
​EDIT: On payday going to buy another one of these phones for stock firmware.

Reserved

Broken Download Link
The Link to download the Code-4 package is broken, and it makes me oh-so-sad!!! Help!

WowTheDog said:
The Link to download the Code-4 package is broken, and it makes me oh-so-sad!!! Help!
Click to expand...
Click to collapse
try now. also "cure-4" XD

Cure-4 download link not working.
I tried to say...
faxanidu said:
try now. also "cure-4" XD
Click to expand...
Click to collapse

The cure-4 thing is missing again, can we get a hold of that?

Omg everyone flagging as malware give me a bit

Hey, it all worked, I had a soft bricked phone, and its booting now. I did the commands in OSX, I just opened the START_HERE.bat and saw your adb commands. The only hangup was that I couldn't push Supersu.zip to /sdcard/ because it wasn't writable for some reason, but I just pushed it to the tmp path from the other commands instead.
Thanks so much!

Good brother my problem is that I have my soft brick phone and I do not know what to do to revive it, do you have any idea how to repair it?

ericcorp said:
Hey, it all worked, I had a soft bricked phone, and its booting now. I did the commands in OSX, I just opened the START_HERE.bat and saw your adb commands. The only hangup was that I couldn't push Supersu.zip to /sdcard/ because it wasn't writable for some reason, but I just pushed it to the tmp path from the other commands instead.
Thanks so much!
Click to expand...
Click to collapse
Odd it pushes supersu automatically. Might had something to do with the soft brick. Your welcome though! Spread the word!

sanpuyon said:
Good brother my problem is that I have my soft brick phone and I do not know what to do to revive it, do you have any idea how to repair it?
Click to expand...
Click to collapse
Follow guide fixes soft brick also just reboot it. let it sit awhile then plug it in. Should be a able to get ADB shell

faxanidu, I just tried on my dead device and I got twrp :good: but won't complete boot after fixing permission tho. Hey that's good enough for me, congrats on what you did! Just gonna wait till a rom gets put up.
To get started I did have to do some steps in oem recovery like I said from the other thread, otherwise my device shows as unauthorized tho, enable adb, then rock volume back and forth till I get mounted /system, then hit reboot. It seems I've tried just doing one or the other but it would still be unauthorized. Just sayin, and again like I told you I don't really know what I'm doing
Thanks again, and if you have any further advice or tips, I'm all ears
edit: I didn't have supersu show up either but I put it on an sdcard and installed it that way.

i am too afraid to try this, is this safe? if i brick my phone, how do i flash stock firmware
---------- Post added at 03:24 AM ---------- Previous post was at 02:59 AM ----------
faxanidu said:

Good news everyone! I have built a massive guide for the alcatel ideal! install custom recovery and more now! also fix for soft bricked phones! just follow this guide.
WIndows only
Thanks to ejwith9953 with getting TWRP working correctly, he is the bomb!
So dont forget to thank him!
STEP 0
DISCLAIMER! I am not responsible for bricks, cats being both alive and dead, heat death of the universe, etc. Ive minimized the chance of damage as much as possible, but still use this guide at your own risk.
​
STEP 1​​Goto settings > about phone > tap build number, till it says your a developer.
Goto settings > developer Options. slide on OEM unlock, and USB debugging
Download CURE_4 to your computer and extract folder to desktop (or somewhere).
Reboot phone.
Links are at bottom!
STEP 2​​Open your extracted folder, run START_HERE.bat
Let it run, it will copy files, execute temp root exploit, and open a new CMD window.
In the new window type in these codes from top to bottom letting each one finish. ( or copy/paste )
Code:
adb shell
run-as -s1
su
dd if=/data/local/tmp/twrp.img of=/dev/block/mmcblk0p25
When you see:
26404+0 records in
26404+0 records out
your ready to pull out the battery ( reboot recovery does NOT work )
Put the battery back in and hold the PWR and VOL UP at the same time, when you see alcatel let go of power but continue to hold volume up.
Welcome to custom recovery my friends!
STEP 3​​Now we are going to install SuperSU its easy from here dont fret! but first!
click backup, under partitions uncheck everything EXCEPT system. Now swype to backup.
Now that you have a backup go back and click install. click "up a level" then sdcard.
scroll down and click SuperSu.zip. Swipe to install! Now Reboot system! (this may take a few minutes so dont freak)
check that SuperSu installed, did it? great! go back to the extracted folder on your computer and run CLEANUP.bat
STEP 4 -SOFTFIX ONLY​​Boot up to custom recovery click wipe > advanced wipe
checkmark Dalvik cache and Cache, the SWIPE to wipe ( sounds dirty )
now click BACK all the way to main screen. now click advanced.
click fix permissions And Swipe. Now REBOOT. hopefully that will boot your phone if not let me know. i dont
have an extra one to purposfully softbrick to test. but ill have a debloated pre rooted ROM for you
to use soon regardless
More to the guide will be coming, for now this is the basics. im going to bed see you all later!
LINKS!
password: fax
Dropbox  Google  Box.net  Mega
​
EDIT: 4 links encrypted
Click to expand...
Click to collapse
faxanidu said:
Click to expand...
Click to collapse
Thank you! i am now happily running twrp, though with some mods, i rooted with kingroot first then ran the commands
Now we wait for lineage os or cm13

For some reason I can't do this on my working phone. when it comes to the "getting uid" screen, everything that runs says "missing second argument" then I try entering the commands it says "run-as: Package '-s1' is unknown"?

scohut said:
For some reason I can't do this on my working phone. when it comes to the "getting uid" screen, everything that runs says "missing second argument" then I try entering the commands it says "run-as: Package '-s1' is unknown"?
Click to expand...
Click to collapse
What the? Never had that problem can't reproduce plz send screenshot

faxanidu said:
Good news everyone! I have built a massive guide for the alcatel ideal!
Click to expand...
Click to collapse
Thank you so much for this.
I started and misread the text as a lowercase "L" instead of the number one for the "run-as -s1" part of the code. I wasn't sure how to correct it when I got an error, so I started over and ran the START_HERE.bat again. When the new cmd window opens, I can't type anything. It reads:
# Device:Alcatel_4060A
-Getting uid 0->Ok.
-Checking permissive run-as.->Ok
# turn off/on the bluetooth.....................................................
..............←[s←[0;34m
[email protected]:/data/local/tmp #
Click to expand...
Click to collapse
I'm not sure how to start over to get back on track for the adb shell code.
I know, it's pretty bad that I didn't get past the first part of Step 2. Any help is appreciated.

faxanidu said:
What the? Never had that problem can't reproduce plz send screenshot
Click to expand...
Click to collapse
this..

Rush-O-Matic said:
Thank you so much for this.
I started and misread the text as a lowercase "L" instead of the number one for the "run-as -s1" part of the code. I wasn't sure how to correct it when I got an error, so I started over and ran the START_HERE.bat again. When the new cmd window opens, I can't type anything. It reads:
I'm not sure how to start over to get back on track for the adb shell code.
I know, it's pretty bad that I didn't get past the first part of Step 2. Any help is appreciated.
Click to expand...
Click to collapse
That happens rarely just reboot and start again

faxanidu said:
That happens rarely just reboot and start again
Click to expand...
Click to collapse
And it reads what?

scohut said:
this..
Click to expand...
Click to collapse
Looks like exploit.sh for corrupted or something plus if you have any mods like exposed might interfere with it. The script dumps info it need to patch see policy then creates run-as with info.
Edit: I'm basically using dirty cow exploit. Works on everything