Related
Hi together,
I've got a Motorola Photon Q 4g LTE mobile phone and this afternoon I wanted to install CyanogemMod, but whatever I do, I stuck with the following problem:
I can't install any other Custom Recovery. I tried ClockworkMod and OpenRecovery, but I always get the s**t Motorola Bootloader, when I start in Recovery Mode. The Bootloader of my Phone is unlocked via Motorola Website, as told in many other threads.
I know that the users arrrghhh, shabbypenguin and Skrilax_CZ are great experts with firmware and such things, but I'm not allowed to write in developer's forums because I'm new here.
Has anybody got an idea for me, how to geht the Custom Recovery to work?
Btw: I tried to root the phone as well, but that wasn't posible. May be things come together or depend on each other.
Thanks for your help!
When you flash recovery (IE run the fastboot command) is it successful?
With the phone in fastboot/bootloader mode, type "fastboot devices" in the command prompt (where you run the fastboot flash command) and what does it output?
Also, try this.
arrrghhh said:
When you flash recovery (IE run the fastboot command) is it successful?
Click to expand...
Click to collapse
When I flash recovery, I just flash the Motorola given Recovery by Motoroloa Bootloader. The Phone restarts, a logo with the Android Man is shown (stomach opend with some engeniering tools in it) and after about 5-7 Minuten, the system starts normally.
I also managed it to change the "Unlocked Message" into a Motorola Logo by using fastboot flash logo xxxx.bin and I nearly destroyed the flash by flashing an unlikely file. So the phone was shortly out of order because oder "flash failure" (fastboot mode). After that, I managed to flash the "boot.img" file of an CyanogenMod, so the flash was rebuilt and I could use the phone normally.
arrrghhh said:
With the phone in fastboot/bootloader mode, type "fastboot devices" in the command prompt (where you run the fastboot flash command) and what does it output?
Click to expand...
Click to collapse
It shows the connected devices by showing a 8 or 9 ditigt number. It's almost the same view like I connected the phone without fastboot and use "adb devices".
arrrghhh said:
Also, try this.
Click to expand...
Click to collapse
This one I didn't tried yet, because I was so dissappointed of the mismatch with ClockworkMod & Open Recovery. Do you think, that trying this one will help, after two others failed?!
Thanks for you notice and your time. That's very helpful!
You need to boot to recovery after flashing it. There's a shell script that is re-flashing stock recovery - the dead Android dude with tools sticking out of him is stock recovery....
arrrghhh said:
You need to boot to recovery after flashing it. There's a shell script that is re-flashing stock recovery - the dead Android dude with tools sticking out of him is stock recovery....
Click to expand...
Click to collapse
Ah ja, now I'm one step closer. I did not know, that the dead Android dude is the sign for stock recovery.
I'll give it this afternoon another try and will report. A bunch of thanks to you at this time!
Hi, it's me again. I managed now the reboot to recovery, by holding the volume up button while doing the "fastboot reboot"-command with the command box. That worked and I could start Photon Q Open Recovery 2.06.
Unfortunately, I did something wrong or so and now the script re-flashed stock recovery again. Nevertheless, I now know how to operate and will do the rest by my own (hopefully).
@arrrghhh: Thank you very much for your help!
So, I finally did everyhting the right way (now with ClockworkMod Recovery), because I now have CyanogenMod running on my Motorola Photon Q
:victory:
@arrrghhh: Thank you very very much!
Hello, I have a problem with my Moto G after unlocking the bootloader. Let me just post the basic info of the phone:
-Moto G XT1032 (16GB)
-Bought in UK Amazon, used in Slovenia
-Android version KitKat 4.4.2
I followed the instructions to unlock bootloader from the Motorola site. The cmd window is like this (pic in attachment) . The first time it rebooted it showed the warning sign at begginng and actually almost booted succesfully but then said com.android.proccess has stopped (something like that) so i turned it off and it automatically turns on again and it does show the warning that bootloader is unlocked and the motorola animation startup and after that the screen become black (but is turned on) and it's stuck like that. Please help my with any solution, because i just got this phone like a week ago and to have it bricked now would be just awfull. So yeah, please post any suggestions on how to fix this.
+I find out now that I am able to get into fastboot, if that helps. I don't know what to do if any of you do please help
Had a similar problem. I solved it by rebooting to bootloader and flashing a custom recovery. Try either cwm or twrp. From there i flashed cyanogenmod.
Gesendet von meinem XT1032 mit Tapatalk
wget21 said:
Had a similar problem. I solved it by rebooting to bootloader and flashing a custom recovery. Try either cwm or twrp. From there i flashed cyanogenmod.
Gesendet von meinem XT1032 mit Tapatalk
Click to expand...
Click to collapse
Thanks for replying! I'm sorry could you please be more specific on how to do that, i'm still a noob at doing this stuff
How to get to fastboot mode
Keep in mind, that vol up is the enter key in fastboot mode and power button will turn your device off. When you are in fastboot mode you can connect the phone via USB and you should see "usb connected" or something similar popping up. You can also list the connected devices with
Code:
fastboot devices
Once you're in fastboot mode install a recovery.img. Either twrp or cwm.
You can flash it with:
Code:
fastboot flash recovery recovery.img
And finally boot to recovery by selecting it in fastboot mode.
Then you can copy cyanogenmod or another rom with adb:
Code:
adb push C:\path\to\rom.zip /sdcard/
Then flash the rom by selecting "install zip", "choose zip from /sdcard/" and selecting 0 and the rom you just copied over.
Edit: you might find this useful if you dont have adb + fastboot already set up.
Edit: also you should put recovery.img and rom.zip in the same folder as adb and fastboot (will make the path thing obsolete).
wget21 said:
Had a similar problem. I solved it by rebooting to bootloader and flashing a custom recovery. Try either cwm or twrp. From there i flashed cyanogenmod.
Click to expand...
Click to collapse
what are you refering to with "rebooting to bootloader"?
tenjou_89 said:
what are you refering to with "rebooting to bootloader"?
Click to expand...
Click to collapse
Bootloader or Fastboot mode.
You can go into this mode by turning the phone off, then press and hold Power + Vol down buttons for about 3-5 seconds.
Alternatively, if you have ADB working, you can type in your command prompt: adb reboot bootloader
So, I went through the temp root/S-off routine with WeakSauce and Firewater. Then flashed TWRP over adb. Rebooted to TWRP which asked if I wanted to install SuperSU. I said yes. Rebooted again and came back up in TWRP. Cannot boot to system. Rebooting always takes me back to recovery. Help would be much appreciated!
Oh, and I can also boot to the bootloader, if that helps.
Can you load a rom to the internal memory or on the SD card and then flash and install a new rom?
Same Here
droidmark said:
So, I went through the temp root/S-off routine with WeakSauce and Firewater. Then flashed TWRP over adb. Rebooted to TWRP which asked if I wanted to install SuperSU. I said yes. Rebooted again and came back up in TWRP. Cannot boot to system. Rebooting always takes me back to recovery. Help would be much appreciated!
Oh, and I can also boot to the bootloader, if that helps.
Click to expand...
Click to collapse
Hey man the same thing happened to me last night, i thought i bricked my phone. I personally dont think the adb method of getting twrp onto the phone is working right now. If someone knows what we are doing wrong plz let us know.
Here is how i fixed it:
1. Put phone into bootloader, put it on fastboot, plug it into computer. You will see it change to "fastboot usb"
2. Download and do this http://forum.xda-developers.com/showthread.php?t=2708686 . To do this go back to your console (terminal or cmd), navigate back to the folder with adb in it, and instead of running the adb commands just type in " fastboot flash boot M8VZWbootInsecure.img ". its easiest to put that boot img in the same folder as adb and fastboot. once that is done you just need to reboot the phone and you are golden.
3. Problem is, when you do this you can no longer get back to your recovery, you get a screen with a red triangle and exclamation mark. I thought I bricked my phone lol.
4. Doing a alternate soft reset will get the phone back to normal android ( hold down power and volume up for 10 secs)
5. to fix it complete use the flashboot method of copying over the recovery onto the phone as shown here http://teamw.in/project/twrp2/226 . This is essentially the same method as in step 2 its just copying over the twrp.img into the recovery section of the phone.
By doing this I was able to get TWRP to work and be able to boot normally to system. Hope this helps.
I think the command you run has something to do with it. "Fastboot flash boot nameofrecovery.img"
Almost certain the command has to be "fastboot flash nameofrecovery.img"
Sent from my HTC6525LVW using Tapatalk
edited to fix all my auto-correct typing mistakes.
The Stig 04 said:
I think the command you run has something to do with it. "Fastboot flash boot nameofrecovery.img"
Almost certain the command has to be "fastboot flash nameofrecovery.img"
Click to expand...
Click to collapse
My understanding is that there's two ways of getting into a custom recovery in adb:
1: "fastboot flash recovery nameofrecovery.img" this will flash over the previous recovery whatever that was. It will stick and you get into the new recovery either through hboot or a ROM's advanced power menu.
2: "fastboot boot nameofrecovery.img" this will boot into the recovery temporarily and allow you flash things. Once you reboot from that temp recovery it will boot using whatever kernel (or other .img file in this case) you have flashed into the boot partition.
The syntax for flashing is "fastboot flash <partition> <name-of-file-to-flash-to-that-partition>"
The syntax for booting an image is "fastboot boot <name-of-the-file-to-boot>"
It sounds like you mixed those 2 together and typed " fastboot flash boot nameofrecovery.img" so when you go to boot your phone now the only thing your phone sees to boot is the recovery. That's why your solution is twofold.
1: Flash the kernel to the boot partition: "fastboot flash boot nameofkernel.img" (sometimes these are just named "boot.img"). This will load the Kernel, modules, and ROM so that your phone will boot properly.
2: flash the recovery to the recovery partition: "fastboot flash recovery nameofrecovery.img" This will permanently install your custom recovery so that you can go back into it next time you want to flash ROMs, make/restore backups, etc.
You should be good to go and will likely never make THAT mistake again. Ask me how I know...
cntryby429 said:
edited to fix all my auto-correct typing mistakes.
My understanding is that there's two ways of getting into a custom recovery in adb:
1: "fastboot flash recovery nameofrecovery.img" this will flash over the previous recovery whatever that was. It will stick and you get into the new recovery either through hboot or a ROM's advanced power menu.
2: "fastboot boot nameofrecovery.img" this will boot into the recovery temporarily and allow you flash things. Once you reboot from that temp recovery it will boot using whatever kernel (or other .img file in this case) you have flashed into the boot partition.
The syntax for flashing is "fastboot flash <partition> <name-of-file-to-flash-to-that-partition>"
The syntax for booting an image is "fastboot boot <name-of-the-file-to-boot>"
It sounds like you mixed those 2 together and typed " fastboot flash boot nameofrecovery.img" so when you go to boot your phone now the only thing your phone sees to boot is the recovery. That's why your solution is twofold.
1: Flash the kernel to the boot partition: "fastboot flash boot nameofkernel.img" (sometimes these are just named "boot.img"). This will load the Kernel, modules, and ROM so that your phone will boot properly.
2: flash the recovery to the recovery partition: "fastboot flash recovery nameofrecovery.img" This will permanently install your custom recovery so that you can go back into it next time you want to flash ROMs, make/restore backups, etc.
You should be good to go and will likely never make THAT mistake again. Ask me how I know...
Click to expand...
Click to collapse
I didn't use fastboot load TWRP, I used the adb method shown on TeamWin's project page for the Verizon M8:
***********
Download - ADB / Terminal method:
Download the newest .img file from here
Download the above file. Save it to the root of your /sdcard directly (internal memory only) and rename it to twrp.img
Launch terminal emulator or connect to your computer and open an adb shell, then type the following:
su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p43
Then reboot to complete installation.
***********
Thanks all for the other suggestions which I am about to attempt!
I had this happen to me on my Asus EeePad TF101. It seems that TWRP has a bug that prevents it from setting a "boot to system" flag on some devices, causing it to always boot to recovery.
The solution for the TF101 was to reinstall the stock boot image, which appears to align with the instructions already given. Good luck! I know the terrible feeling I had when this happened to my tablet...
Zallantor said:
Hey man the same thing happened to me last night, i thought i bricked my phone. I personally dont think the adb method of getting twrp onto the phone is working right now. If someone knows what we are doing wrong plz let us know.
Here is how i fixed it:
1. Put phone into bootloader, put it on fastboot, plug it into computer. You will see it change to "fastboot usb"
2. Download and do this http://forum.xda-developers.com/showthread.php?t=2708686 . To do this go back to your console (terminal or cmd), navigate back to the folder with adb in it, and instead of running the adb commands just type in " fastboot flash boot M8VZWbootInsecure.img ". its easiest to put that boot img in the same folder as adb and fastboot. once that is done you just need to reboot the phone and you are golden.
3. Problem is, when you do this you can no longer get back to your recovery, you get a screen with a red triangle and exclamation mark. I thought I bricked my phone lol.
4. Doing a alternate soft reset will get the phone back to normal android ( hold down power and volume up for 10 secs)
5. to fix it complete use the flashboot method of copying over the recovery onto the phone as shown here http://teamw.in/project/twrp2/226 . This is essentially the same method as in step 2 its just copying over the twrp.img into the recovery section of the phone.
By doing this I was able to get TWRP to work and be able to boot normally to system. Hope this helps.
Click to expand...
Click to collapse
Whew! Thanks!!
Not only did that save my bacon, it had the added benefit of getting me the insecure kernel which I had forgotten about since going through the whole root/S-off/unlock bootloader/insecure kernel routine with my Droid DNA quite a while back.
Zallantor said:
Hey man the same thing happened to me last night, i thought i bricked my phone. I personally dont think the adb method of getting twrp onto the phone is working right now. If someone knows what we are doing wrong plz let us know.
Here is how i fixed it:
1. Put phone into bootloader, put it on fastboot, plug it into computer. You will see it change to "fastboot usb"
2. Download and do this http://forum.xda-developers.com/showthread.php?t=2708686 . To do this go back to your console (terminal or cmd), navigate back to the folder with adb in it, and instead of running the adb commands just type in " fastboot flash boot M8VZWbootInsecure.img ". its easiest to put that boot img in the same folder as adb and fastboot. once that is done you just need to reboot the phone and you are golden.
3. Problem is, when you do this you can no longer get back to your recovery, you get a screen with a red triangle and exclamation mark. I thought I bricked my phone lol.
4. Doing a alternate soft reset will get the phone back to normal android ( hold down power and volume up for 10 secs)
5. to fix it complete use the flashboot method of copying over the recovery onto the phone as shown here http://teamw.in/project/twrp2/226 . This is essentially the same method as in step 2 its just copying over the twrp.img into the recovery section of the phone.
By doing this I was able to get TWRP to work and be able to boot normally to system. Hope this helps.
Click to expand...
Click to collapse
I was soft bricked and only able to boot into bootloader and recovery and this write up worked for me. Just wanted to say thanks.
Don't use adv/terminal way. It's writing recovery to wrong partition..
Sent from my HTC6525LVW using XDA Premium 4 mobile app
The fastboot command to flash your recovery is:
fastboot flash recovery recovery.img
where "recovery.img" is the name of your recovery.img file on your host computer. Don't use "fastboot flash boot recovery.img", as I believe this will flash your boot partition, not the recovery partition.
hanginwithdaddo said:
The fastboot command to flash your recovery is:
fastboot flash recovery recovery.img
where "recovery.img" is the name of your recovery.img file on your host computer. Don't use "fastboot flash boot recovery.img", as I believe this will flash your boot partition, not the recovery partition.
Click to expand...
Click to collapse
if you flash to anything but the recovery partition your in some trouble.
same goes for anything like this, make sure you know what that .img is and you trust it. someone could have renamed an hboot to recovery and you end up flashing an hboot to your recovery partition because someone was careless with naming of files.
So I need help... I'm stuck in a bootloader loop. And every time I try to do this fix, terminal keeps telling me this:
error: cannot open 'M8VZWbootInsecure.img'
Any ideas?
tim.ton said:
So I need help... I'm stuck in a bootloader loop. And every time I try to do this fix, terminal keeps telling me this:
error: cannot open 'M8VZWbootInsecure.img'
Any ideas?
Click to expand...
Click to collapse
are you on a mac? reboot...
---------- Post added at 08:36 AM ---------- Previous post was at 08:32 AM ----------
The Stig 04 said:
I think the command you run has something to do with it. "Fastboot flash boot nameofrecovery.img"
Almost certain the command has to be "fastboot flash nameofrecovery.img"
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
This is incorrect.
command is:
fastboot flash recovery nameofrecovery.img
additionally, since you can boot into TWRP, have you tried sideloading a rom?
(in TWRP, go to ADVANCED, click SIDELOAD... i think you need to swipe to activate... then from terminal: adb sideload nameofROM.zip)
RBThompsonV said:
are you on a mac? reboot...
---------- Post added at 08:36 AM ---------- Previous post was at 08:32 AM ----------
This is incorrect.
command is:
fastboot flash recovery nameofrecovery.img
Click to expand...
Click to collapse
Oh yeah! Lol I knew it was something like that. Thanks!
Sent from my HTC6525LVW using Tapatalk
Guys im opening this thread on how to unlock Boot loader and flashing twrp in steps clearly...as there are no clear guide to do this in main threads and people can also share things here...Thanks for the devs who are working for us[emoji3]
Thanks and all credit goes to Dev (Uberlaggydarwin) for developing the magic tool (Magictricks.zip) for unlock and initiating development of this device and all I need from you is just clicking thanks button below that's all [emoji12] [emoji12] [emoji12]
Sent from my F1f using XDA-Developers mobile app
Steps: Making bootloader unlockable
Download Magictricks.zip by (uberlaggydarwin) - go to stock recovery- select install from storage- select the downloaded zip- flash or update it.
This will make the boot loader unlockable and brings fastboot to our device...see below how to unlock bootloader through fastboot completely.
Sent from my F1f using XDA-Developers mobile app
Adb commands for fastboot and flash twrp.
First set up adb shell on your Windows..Download link available below...
Steps to command in adb shell properly to fastboot and to flash custom recovery...let's begin
1-Download adb and install adb drivers for oppo f1.
2-extract the files from adb.rar to your c directory in a folder named adb(creat one) or just extract the folder in c directory.
3-once the files are located in c:\adb go to start menu then search for cmd
4-Type in cd c:\adb then click enter
5-Type in "adb devices" it will show the connected devices it should be bunch of numbers
6-If you can't see them it means adb drivers for your device are not installed then install with adb installer
7- Disconnect your oppo f1 and put your phone in fastboot mode(press and hold vol+ and power button} u will see fastboot screen on phone then connect via usb then let the system install bootloader driver....proceed below
7-Then finally Command in fastboot for our device.
Put twrp recovery image(rename as twrp) in the same folder where adb is present then tick 'oem unlock' on developer option settings in the device before you continue.
Don't proceed here unless you flash "magictricks.zip" through stock recovery.
Starting Boot loader unlock and custom recovery steps:
Connect your device via usb in fastboot mode and command as below..
Type this "fastboot oem unlock" then press enter.(Will wipe your data so backup before you do and wait for reboot) command will show 'ok finished' with some like 0.07secs
Type this "fastboot flash recovery twrp.img" then press enter. wait it will flash then command will show 'ok finished' then disconnect and boot in to new recovery.....enjoy
Note - once u flash the recovery disconnect the phone and switch off from the fastboot then u should boot the twrp recovery first otherwise system will reflash the stock recovery...To boot in to twrp recovery command as "fastboot boot twrp.img" press enter
That's it you have unlocked your boot loader and installed twrp recovery successfully[emoji3] [emoji12] [emoji3] [emoji12]
Credits
Thanks to @uberlaggydarwin for developing magictricks to unlock
Download links:
Magictricks by uberlaggydarwin - https://strangebinaries.re/f1f/magictricks.zip
ADB driver installer(optional) - www14.zippyshare.com/v/ufYG71o0/file.html
ADB Folder files-https://drive.google.com/file/d/0B9SasC5iWK5kT1liMlpKRGY3LVU/view?usp=sharing
Twrp recovery for f1f - http://build.twrp.me/twrp/twrp-3.0.2-0-f1f.img
Rooting guide:
After installing TWRP recovery flash this Super Su Stable version and reboot then install super su from playstore if you dont see any icon
Flashable Su Binaries - http://forum.xda-developers.com/showthread.php?p=23427715
Sent from my F1f using XDA-Developers mobile app
reserve
Thankss a lot
drganbds said:
Adb commands for fastboot and flash twrp.
First set up adb shell on your Windows..Download link available below...
Steps to command adb properly please share it somebody[emoji12] ill share once I know and master it
1-Download adb and install adb drivers for oppo f1.
2-extract the files from adb.rar to your c directory in a folder named adb(creat one) or just extract the folder in c directory.
3-once the files are located in c:\adb go to start menu then search for cmd
4-Type in cd c:\adb then click enter
5-Type in "adb devices" it will show the connected devices it should be bunch of numbers
6-If you can't see them it means adb drivers for your device are not installed then install with adb installer
7-THEN FINALY COMMAND some for our device.
Put twrp recovery image(rename as twrp.img) in the same folder where adb is present then tick 'oem unlock' on developer option settings in the device before you continue.
Don't proceed here unless you flash "magictricks.zip" through stock recovery.
Starting Boot loader unlock and custom recovery steps:
Connect your device via usb and command as below..
Type this "fastboot oem unlock" then press enter.(Will wipe your data so backup before you do and wait for reboot)
stucked at waiting for device ( then i press vol + plus power button) command shows Ok finished but nothing happened to device no changes nothing...help please
Click to expand...
Click to collapse
I think you have not installed your adb drivers properly...use pdanet pc version to install otherwise use adb installer which is available in dl.
Sent from my F1f using XDA-Developers mobile app
Guys if u stuck at "waiting for device"
solution - disconnect the device, put it in fastboot mode (press and hold vol+ and power you will see fastboot screen)and connect it again then it will install bootloader drivers and continue. It will show 'ok finished' then u can continue to flash recovery and other stuffs...enjoy[emoji3] [emoji12] [emoji3] [emoji12]
Sent from my F1f using XDA-Developers mobile app
@ teteakholhring. you have done it right go head flashing recovery step.....now u unlocked the bootloader then flash the recovery
Thread re edited please check if u have doubts.
Hi
sorry about my poor English.
I am sure that I flashed magictricks.zip and ticked "OEM unlock"
and the phone is in fastboot mode.
And I typed in "fastboot oem unlock", it showed "Okay, finished",
then I typed in "fastboot flash recovery twrp.img", it also showed "Okay, finished".
Then nothing happen, my phone is still with stock recovery, and my data is stilled there, can someone give me a help?
I attached my cmd picture.
Thank you!
^^ I've read from other thread that right after you flashed the TWRP recovery image, you must start-up the phone in TWRP recovery first before eventually booting to Android.
I haven't unlock my phone yet though but I will once I see some custom ROMs available.
Sent from my F1f using Tapatalk
x36023x36023 said:
Hi
sorry about my poor English.
I am sure that I flashed magictricks.zip and ticked "OEM unlock"
and the phone is in fastboot mode.
And I typed in "fastboot oem unlock", it showed "Okay, finished",
then I typed in "fastboot flash recovery twrp.img", it also showed "Okay, finished".
Then nothing happen, my phone is still with stock recovery, and my data is stilled there, can someone give me a help?
I attached my cmd picture.
Thank you!
Click to expand...
Click to collapse
All your steps are perfectly right but once u flash the recovery disconnect the phone and switch off from the fastboot then u should boot the twrp recovery first otherwise system will reflash the stock recovery...
Do the recovery flash again and boot to twrp first...
It is not necessary that oem unlock will wipe your data so no worry.
Me too I'm waiting for available alternative roms to install twrp recovery ....I just flashed magictrick and it said that I have update the build.... Thanks sure it will be functional....
x36023x36023 said:
Hi
sorry about my poor English.
I am sure that I flashed magictricks.zip and ticked "OEM unlock"
and the phone is in fastboot mode.
And I typed in "fastboot oem unlock", it showed "Okay, finished",
then I typed in "fastboot flash recovery twrp.img", it also showed "Okay, finished".
Then nothing happen, my phone is still with stock recovery, and my data is stilled there, can someone give me a help?
I attached my cmd picture.
Thank you!
Click to expand...
Click to collapse
Ok you did everything right.. I've attached the picture how i did it.. I was busy solving the same problem.. Remove the usb when it says booting then it will boot into twrp recovery.. Then flash latest supersu..that's it download super user from playstore.. Thre you go.. You got what you wanted..
teteakholhring said:
Ok you did everything right.. I've attached the picture how i did it.. I was busy solving the same problem.. Remove the usb when it says booting then it will boot into twrp recovery.. Then flash latest supersu..that's it download super user from playstore.. Thre you go.. You got what you wanted..
Click to expand...
Click to collapse
Ya right guys...Please check this thread's main page everything was written clearly for how to do it correctly...enjoy
Sent from my F1f using XDA-Developers mobile app
hoping someone will upload a video on how to properly root our device.
wakaranay said:
hoping someone will upload a video on how to properly root our device.
Click to expand...
Click to collapse
What doubt you have? I'm here to clear it all and every steps are clearly explained in the main page...
Sent from my F1f using XDA-Developers mobile app
thank you for all your help
I made my phone rooted
but when I forced to delete original apps like original browser
and reboot
all the things on home page will disappear
when I delete original browser only
it still happened
this never happened on my other Sony device
can anyone tell me why
x36023x36023 said:
thank you for all your help
I made my phone rooted
but when I forced to delete original apps like original browser
and reboot
all the things on home page will disappear
when I delete original browser only
it still happened
this never happened on my other Sony device
can anyone tell me why
Click to expand...
Click to collapse
Use root app delete from playstore or manually remove .apk file along with .odex file...
Sent from my F1f using XDA-Developers mobile app
all dones!!
first i open command in the folder by shift+right click and selecting "open command window here"
usb debugging on
typed "adb devices"
it is detected
typed "adb boot bootloader"
it is gone to download mode
typed "fastboot devices"
fastboot device detected
typed "fastboot boot mycwm.img"
shows download complete
and shows booting.....
here problem starts
it takes a lot time ..
i was taken it 1hour and 14minutes
but nothing happened:crying::crying::crying:
device working fine . boots normally. no damage
but i cant go in the cwm recovery
SHARUK154 said:
all dones!!
first i open command in the folder by shift+right click and selecting "open command window here"
usb debugging on
typed "adb devices"
it is detected
typed "adb boot bootloader"
it is gone to download mode
typed "fastboot devices"
fastboot device detected
typed "fastboot boot mycwm.img"
shows download complete
and shows booting.....
here problem starts
it takes a lot time ..
i was taken it 1hour and 14minutes
but nothing happened:crying::crying::crying:
device working fine . boots normally. no damage
but i cant go in the cwm recovery
Click to expand...
Click to collapse
Is the CWM you're using made for your specific device.
Sent from my SM-S903VL using Tapatalk
SHARUK154 said:
all dones!!
first i open command in the folder by shift+right click and selecting "open command window here"
usb debugging on
typed "adb devices"
it is detected
typed "adb boot bootloader"
it is gone to download mode
typed "fastboot devices"
fastboot device detected
typed "fastboot boot mycwm.img"
shows download complete
and shows booting.....
here problem starts
it takes a lot time ..
i was taken it 1hour and 14minutes
but nothing happened:crying::crying::crying:
device working fine . boots normally. no damage
but i cant go in the cwm recovery
Click to expand...
Click to collapse
Hmm, you forgot to flash CWM recovery, you just typing to boot to recovery, so yeah, ended up with stock recovery.
First run this command ~
Fastboot flash recovery mycwm.img - - once it's success, then this command ~
Fastboot boot mycwm.ing - - Give it some time, it'll boot to CWM.
sachin n said:
Hmm, you forgot to flash CWM recovery, you just typing to boot to recovery, so yeah, ended up with stock recovery.
First run this command ~
Fastboot flash recovery mycwm.img - - once it's success, then this command ~
Fastboot boot mycwm.ing - - Give it some time, it'll boot to CWM.
Click to expand...
Click to collapse
The fastboot boot command should have worked to boot the CWM.img directly without flashing shouldn't it?
I don't have a device that uses fastboot but I've dealt with users that have used fastboot boot to boot an .img without actually flashing the .img. Am I missing something?
Sent from my SM-S903VL using Tapatalk
Droidriven said:
The fastboot boot command should have worked to boot the CWM.img directly without flashing shouldn't it?
I don't have a device that uses fastboot but I've dealt with users that have used fastboot boot to boot an .img without actually flashing the .img. Am I missing something?
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Oh, I've never used cwm, my all device's have twrp, since we flash twrp [fastboot flash recovery <whatevertherecoveryname.img>] before using the command boot to " recovery.img" thought this would goes with the cwm too. That's why I suggested him.
Never knew that we can boot to cwm without actually flashing it using fastboot command.
Thanks.
sachin n said:
Oh, I've never used cwm, my all device's have twrp, since we flash twrp [fastboot flash recovery <whatevertherecoveryname.img>] before using the command boot to " recovery.img" thought this would goes with the cwm too. That's why I suggested him.
Never knew that we can boot to cwm without actually flashing it via fastboot.
Thanks.
Click to expand...
Click to collapse
I could also be wrong about the specifics of its useage but I have read of testing a .img to see if it's compatible with a device before actually flashing it to avoid bricking since nothing is being written to the device by only booting the .img, then if it works, the user knows they can safely flash it without harming the device or continue just using it temporarily and only boot it when they need it instead of flashing it permanently. If it doesn't work the device can just be rebooted and no harm no foul.
This is one way for users with devices that have no custom recovery for their model to test a recovery from a different model to see if it can be used.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
I could also be wrong about the specifics of its useage but I have read of testing a .img to see if it's compatible with a device before actually flashing it to avoid bricking since nothing is being written to the device by only booting the .img, then if it works, the user knows they can safely flash it without harming the device or continue just using it temporarily and only boot it when they need it instead of flashing it permanently. If it doesn't work the device can just be rebooted and no harm no foul.
This is one way for users with devices that have no custom recovery for their model to test a recovery from a different model to see if it can be used.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Whoah, Nice.
Thanks for the tip :good:
sachin n said:
Whoah, Nice.
Thanks for the tip :good:
Click to expand...
Click to collapse
But....
As with all things android, this method does not work on all devices.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
But....
As with all things android, this method does not work on all devices.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Yep
Droidriven said:
Is the CWM you're using made for your specific device.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
it is not made for my device
my device is not support permanent flashing.
once i flashed with the same cwm.img.
but it bricked.
before it bricks its works for me
fastboot boot cwm.img
but now it only stuck on booting
in this forum there written that "infocus m2 4g is not permanentaly flashable , you have to port cwm.img each time from pc".