Hi Guys,
Firstly, thanks so much for the info on this community. I've followed loads of the threads and almost all of what I need to know is here.
I have a KF2 @ v10.3.1. I've rooted it and applied the 2nd bootloader using a homemade lead (thanks to the thread on that!). I started in Windows but switched to Kubuntu after getting driver issues etc.. To compound the problem, the KF2 is blocked by Amazon, which didn't help as I couldn't load apps whist it was stock. (It's not stolen or otherwise illegally obtained. Amazon sent it in error, and despite me contacting them to ask how to return it, they've never replied)
Anyhow, After following THIS thread, which appeared to go OK, after rebooting I'm unable to boot into Recovery. The blue screen just stays there. I can still boot normally, but I would like to load CM10 which is loaded as per the thread, along with gapps, both in zip format. I have read many threads about being stuck on the blue screen, but these are always locked and need to be restored, but I have no problem booting normally and the KF2 is not locked. I've searched this site and googled plenty.
I don't expect an exact answer, but if someone could just point me at what to look at, I'm sure I can find the rest of the info I need on here. :good:
Oh, also. Another quick question. I see that the CM10 images are constantly being updated, if (when I get mine working) I want to use one of these, is it simply a case of copying the zip file over? Or is there more to do than that.
Many thanks in advance.
You can boot normally? Into stock, I assume.
Run the apk tool from here:
http://forum.xda-developers.com/showthread.php?t=2106463
Should get you fixed right up
The zip file will have to be flashed from recovery. So, its a matter of copying the zip file (and gapps) over. Boot into recovery. Wipe data, cache, dalvik and system. Then flash rom first, the gapps.
Also, be VERY CAREFUL and make sure you have a GOOD DOWNLOAD by checking the md5 on the file. If you wipe the system (which deletes the stack file) you will not be able to boot into recovery or anything.
I still recommend that you purchase a fastboot cable.
Edit: also, when booting into recovery you might have to hit the power button a couple of times.
--
Sent from my mind to your screen.
Cheers mindmajick. I've tried to do this but still having a few problems.
If I use the wired version, the runme.bat does not have permissions to the data/app folder. I can't seem to run it in Kubuntu as it says I can't run a binary file if I make it executable, but says I don't have permission if I remove execute. (I'm looking into this - but I'm not very good with Linux, so lots of Googling!!...lol....) Also I see that there are some issues with this version with the wireless version being favored. Unfortunately as I'm unable to log onto my Amazon account, I can't use this method.
I will continue to try, I'm almost there now, thanks for you help so far.
SportyPorty said:
Cheers mindmajick. I've tried to do this but still having a few problems.
If I use the wired version, the runme.bat does not have permissions to the data/app folder. I can't seem to run it in Kubuntu as it says I can't run a binary file if I make it executable, but says I don't have permission if I remove execute. (I'm looking into this - but I'm not very good with Linux, so lots of Googling!!...lol....) Also I see that there are some issues with this version with the wireless version being favored. Unfortunately as I'm unable to log onto my Amazon account, I can't use this method.
I will continue to try, I'm almost there now, thanks for you help so far.
Click to expand...
Click to collapse
Really confused. Pm me with your gmail account and I'll chat you through it
--
Sent from my mind to your screen.
Cheers, PM'd you.
Sorry if I've not explained it very well.
I tried to use the KF2CM10.zip via the Desktop method. I downloaded and ran the runme.bat file. This is what I get -
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
C:\Users\Steve\Desktop\Kindle Fire Root\KF2CM10>ECHO off
Press any key to continue . . .
.
Removing install-recovery.sh to ensure that stock rom does not overwrite TWRP
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Usage: mount [-r] [-w] [-o options] [-t type] device directory
rm failed for systemetcinstall-recovery.sh, No such file or directory
rm failed for systemRECOVERY-AMZN-4430-OTTER2-PROD, No such file or directory
.
Pushing stack
failed to copy 'stuff\stack' to '\sdcard\': Read-only file system
sdcardstack: cannot open for read: No such file or directory
.
Inserting stack override to \system
datalocaltmpstack: cannot open for read: No such file or directory
.
Pushing freedom-boot
failed to copy 'stuff\boot.img' to '\sdcard\': Read-only file system
.
Pushing TeamWinRecoveryProject
failed to copy 'stuff\recovery.img' to '\sdcard\': Read-only file system
.
Writing freedom-boot to \boot via dd
sdcardboot.img: cannot open for read: No such file or directory
.
Writing TWRP to recovery via dd
sdcardrecovery.img: cannot open for read: No such file or directory
.
Rebooting
.
Make sure to press the power button during the secondary bootloader to reboot in
to recovery.
.
Give credit where credit is due: Script written by [email protected]
Press any key to continue . . .
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I'm still unsure how to run the runme.sh from Kubuntu command line.
I tried - ./runme.sh
but error is - unable to run a binary file - or something like that.
I'm unable to use the cordless version com.powerpoint45.FMKilo-2.apk due to the fact that as the KF2 is blocked by Amazon, I'm unable to log in and download or install .apk files.
Is there is an alternative way to install .apk files without needing to log in?
Hopefully that makes a little more sense. Cheers
Yes. Download the fmkilo apk from his thread, (use the browser if you have to) then once downloaded pull down the notification bar and tap on the apk link. Also, make sure that the option to install from unknown sources is set in the settings before doing the download
You could alternatively push the file via adb to the system Directory.
Is USB debugging enabled? Are you rooted?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mindmajick said:
Yes. Download the fmkilo apk from his thread, (use the browser if you have to) then once downloaded pull down the notification bar and tap on the apk link. Also, make sure that the option to install from unknown sources is set in the settings before doing the download
Click to expand...
Click to collapse
Yup, that did it. I had overlooked the fact that I was still able to use the browser on the KF2 and didn't really know you could install .apk's using that method anyway. So now I have carried on and installed Jellybean 4.2.2 on there and it works a treat.
Thank you ever so much Mindmajick for taking an interest in my problem, I really do appreciate yours and the rest of the developers time on here. :good:
Cheers
Sporty
fmkilo apk link shows as removed
mindmajick said:
Yes. Download the fmkilo apk from his thread, (use the browser if you have to) then once downloaded pull down the notification bar and tap on the apk link. Also, make sure that the option to install from unknown sources is set in the settings before doing the download
You could alternatively push the file via adb to the system Directory.
Is USB debugging enabled? Are you rooted?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Went to link for fmkilo apk and, link shows link removed?
galearned said:
Went to link for fmkilo apk and, link shows link removed?
Click to expand...
Click to collapse
Correct. Tried to talk them out of removing but it was removed. Only removed so no one uses it stupidly...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
fmkilo apk removed from link
mindmajick said:
Correct. Tried to talk them out of removing but it was removed. Only removed so no one uses it stupidly...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Not a problem: Thanks
I think this is a method of pushing the flash and image files to the tablet and then installing using ADB by the way it is described.
I think I have that method copied down some place else.
I have never used this method but, sounds like it would work.
I also presume you need root to do the install via ADB.
Regards Jerry
Related
Here is an interesting article that will help you if you want CRT screen Off animation like in Nexus S:
http://www.freeyourandroid.com/guide/enable-crt-animation
Worked with no problems on my SGC with Rogers ROM.
I actually used NinjaMorph to package the modified resources.arsc into framework-res.apk, but I assume the original method will work too.
Safe to flash
this?
Aquethys said:
Safe to flash
this?
Click to expand...
Click to collapse
Probably no. Most likely you will end up with phone freezing on the Samsung logo at boot. framework-res.apk files are not interchangeable between models, maybe not even between firmware versions for the same phone.
Can you post a step by step guide then? I can't really understand anything here
The step-by-step instructions from the link in the first post are pretty much what i did. Read the comment by ravenstark - if you mount the filesystem with root explorer there will be no need to execute the commands in red in section 8.
The instructions from the link in your post cover steps 3-7. You still have to download the file to your PC (1), decompile it (2) and upload it back to the phone once you are done with it (8).
For the first step which terminal do you use??
(Free Your Android guide)
adb. If you don't have you can download it from here. It is part of the SDK and probably the most essential tool.
The command is exactly as written there
Aquethys said:
For the first step which terminal do you use??
(Free Your Android guide)
Click to expand...
Click to collapse
What do you mean? If you're using a Windows PC, then just open up a cmd prompt. You should read the guides at the beginning of that page so you know how to setup adb and the apk tool.
The big picture is this. Connect your pc to computer, pull file from phone to PC using adb, modify file on PC, push file back to phone using adb.
For what it's worth, here's a thread I wrote quite a long time ago, some is not applicable for the Glide, but most of it still applies. If you're going to be mucking around in your phone it's best to know how to do a few things first. Read Before Flashing.
When I try and open SDK or AVD (what's the difference :| ) then I just get a quick terminal screen that closes.
It would be appreciated if someone could just create a flashable CWM version >_<
I hate my inexperience @ this. It keeps saying this isn't "adb" isn't recognized, but I've downloaded it! How can I check?!
Aquethys said:
I hate my inexperience @ this. It keeps saying this isn't "adb" isn't recognized, but I've downloaded it! How can I check?!
Click to expand...
Click to collapse
Ok, so what have you done so far?
What should be done. Assuming you're using Windows, install the Android SDK. Once installed, launch the SDK Manager. Then from the list of installable options, choose the Platform Tools and I always like to get the drivers. Once done, you will have this path, CrogramFiles(x86)\Android\android-sdk\platform-tools, now you could add this path to your variables in Windows, which would be easiest, or copy the Platform-tools folder to C:. Then plug in your phone via USB to your computer.
Now, if you added the Path to your variables, just go Start>Run>cmd, and at the cmd prompt type adb devices. If you see a device you're good.
If you copied the Platform-tools folder over, then Start>Run>cmd, and in the cmd prompt type,
C:
then
cd platform-tools
then
adb devices
Beyond that, can't really help, never use apk tool. Good luck.
Aquethys said:
It would be appreciated if someone could just create a flashable CWM version >_<
Click to expand...
Click to collapse
Attached to this post is a CWM update with CRT Screen OFF and battery icon with percent for ROGERS ROM. I'm not sure this will work on AT&T ROM.
Make a backup before applying this update so you can restore if you end up stuck on SAMSUNG logo on boot.
Apologies to the author of the battery mod - I couldn't find his post to link to here...
Aquethys said:
I hate my inexperience @ this. It keeps saying this isn't "adb" isn't recognized, but I've downloaded it! How can I check?!
Click to expand...
Click to collapse
Hopefully the file tcfx44 posted works for you. Either way, I highly suggest you learn how to use adb and some other tools if you plan on flashing your phone in the future. It could prove useful some day.
Will this apply over OsiMood? I really am not sure if I am using the Rogers, but apparently I am because in XDA App it says I927-R and same with a benchmark.
Doesn't work for OsI mood 2.1.30 or whatever version was released today. I don't want to give up the amazing UI and stuff of OSi. I'm working fine though, so doesn't look like the install failed or bricked. Any revisions?
Aquethys said:
Doesn't work for OsI mood 2.1.30 or whatever version was released today. I don't want to give up the amazing UI and stuff of OSi. I'm working fine though, so doesn't look like the install failed or bricked. Any revisions?
Click to expand...
Click to collapse
I changed a bit the CWM mod. Hopefully this one will work. Make a backup of your current ROM - I'm not sure if this mod is compatible with OsiMood.
tcfx44 said:
I changed a bit the CWM mod. Hopefully this one will work. Make a backup of your current ROM - I'm not sure if this mod is compatible with OsiMood.
Click to expand...
Click to collapse
CRT Screen Mod -- Works with Rom manager..
Addition
Default Battery Indicator Changed.. Shows Percentage in steps of 5%..
Anyone having problems powering off and crashing GO Launcher? (then run through media scanner, etc..)
Could you remove the battery mod? I don't like it compared to OSiMood battery >_>
Finally, sorry for demanding so much, could you also put CRT on and ICS animations here?
Sorry!!!!!
Having serious problems turning off. This then affects my underclock.
Motorola Defy Mini XT320/XT321 all-in-one script/utility
I've ported mattlgroff's DROIDRAZR all-in-one Script to the Motorola Defy Mini XT320/XT321. This will make life easier and it will do it for you.
Make sure you have fastboot mode if not please refer to this guide for fastboot but there is a fastboot checker in option 6 but it won't install fastboot for you.
Link: http://forum.xda-developers.com/showpost.php?p=36199694&postcount=3
Options available:
1. Root your Motorola Defy Mini XT320/XT321
2. Install 2nd-init/TWRP Recovery
3. Overclock installation
4. Unroot Device
5. Wipe Data/Factory Reset
6. Fastboot checker.
7. Exit Utility
Instructions:
NEW PACKAGE & instructions
1. Download the EXE file at http://www.mediafire.com/?c81fnrtrki65e9i
2. Double click on the exe.
3. Choose an option by entering a number from 1 to 7
OLD PACKAGE & instructions
1. Download package at [REMOVED OLD LINK]
Please Download the fixed package at http://www.mediafire.com/?krxtemrthsz5ier
EXE Version: http://www.mediafire.com/?0kwmx4whjj1ua8c
2. Extract the zip file making sure all the files are in the same place.
3. Click on the batch file named 'DefyMiniUtility.bat'
4. Choose an option by entering a number from 1 to 7.
Credits to:
- Bernd.Defy for overclock module and Guitwo2 for init.d script
- Guitwo2 and jkkk88 for TWRP and aweosomeabhjeet for 2nd-init
- DoOMLoRD for unroot script
- Mattlgroff for the original DROID RAZR all-in-one script
If anyone knows if I missed a member for the credits, please PM me. Thanks
Make sure press thanks if it works
Guys please don't repost it as your own work, otherwise I'll report it and you will get banned from XDA.
NOTE: If you have previously used the old EXE to install TWRP then please remove the old folders by using these instructions using cmd before using updated exe to install TWRP;
1.
Code:
adb shell
2.
Code:
su
3.
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock11 /system
4.
Code:
rm -R /system/bootmenu
Then use the updated exe to install TWRP.
NOTE: If you don't like TWRP, you can download Guitwo2's Permanent CWM at http://forum.xda-developers.com/attachment.php?attachmentid=1875373&d=1365682716
Temporary CWM Recovery: http://forum.xda-developers.com/attachment.php?attachmentid=1875299&d=1365680458
2nd-init does NOT work in CWM Recovery
Thanks to @Guitwo2 for CWM Recovery.
Instructions on how to install Permanent CWM Recovery:
1. Make sure stericson-busybox is installed
2. Put XT320_bootmenuV2.zip in the root of your sdcard
3. Reboot into fastboot mode by typing this command in cmd:
Code:
adb reboot bootloader
4. Then type this command in cmd:
Code:
fastboot boot recovery.img
5. Then use volume keys to navigate and power button to select option. Select install zip from sdcard, then select XT320_bootmenuV2.zip and select yes to install the zip file
6. Then reboot device by selecting reboot device now.
CWM 6 has a bug where it asks you to 'disable recovery flash' when you select reboot system now make sure you select NO or you will soft brick your device.
Changelog:
-v2 No need to mount /sdcard in CWM Recovery. Fixed TWRP installation issues.
-v2.0.1 Released an .exe version of script, to simplify installation
-v2.0.1.1 Fixed bootmenu.zip
This can install a custom recovery?
This can install a custom recovery?
Thank you
The root process worked for me. Now i can install link2sd and set up a swap partition.
I cant install TWRP and i think the reason is that the bat was having some problem to send that bootmenu.tar file to my sd card. I tried to send that file myself before starting the entire process and it didnt worked.
I took a picture of the error i'm getting . Thank you again, i was really mad about that low internal space xD
same problem... someone can fix it? please
fca.sjc said:
The root process worked for me. Now i can install link2sd and set up a swap partition.
I cant install TWRP and i think the reason is that the bat was having some problem to send that bootmenu.tar file to my sd card. I tried to send that file myself before starting the entire process and it didnt worked.
I took a picture of the error i'm getting . Thank you again, i was really mad about that low internal space xD
Click to expand...
Click to collapse
sfoot13 said:
same problem... someone can fix it? please
Click to expand...
Click to collapse
Ok, I've made a fixed script here. The error was that the sdcard is a directory so it will refuse to push files into it.
Here's the updated script below. Just put the .bat file in the same place as the other files.
Thanks
rootdefyxt320 said:
Ok, I've made a fixed script here. The error was that the sdcard is a directory so it will refuse to push files into it.
Here's the updated script below. Just put the .bat file in the same place as the other files.
Click to expand...
Click to collapse
Ty for the quickly answer.
Btw, my gsm network wasnt working after the root process. If the same thing happens to someone else, just do a master reset and it will work again.
pull command is working now
That sdcard copy part is working now. The TWRP process is still not working for me. I tried to do myself the commands using the adb interface and when i use the command to intall the tar, i got the message 'tar: no space left on device" . I hope you can help me with that and i'm sorry about all this questions xD .
fca.sjc said:
That sdcard copy part is working now. The TWRP process is still not working for me. I tried to do myself the commands using the adb interface and when i use the command to intall the tar, i got the message 'tar: no space left on device" . I hope you can help me with that and i'm sorry about all this questions xD .
Click to expand...
Click to collapse
You must have more than 5MB free in your /system partition. Please move your apps to the /flex partition or delete the useless apps in /system.
rootdefyxt320 said:
You must have more than 5MB free in your /system partition. Please move your apps to the /flex partition or delete the useless apps in /system.
Click to expand...
Click to collapse
Thank u so much to everyone who make it possible xD
(can i do now a overclock to 720 without problems?)
sfoot13 said:
Thank u so much to everyone who make it possible xD
(can i do now a overclock to 720 without problems?)
Click to expand...
Click to collapse
Yes but it sometimes gets unstable so you should overclock to 700MHz which is the highest I got without reboots. pll2_l_val=73 gives you 700MHz.
rootdefyxt320 said:
Yes but it sometimes gets unstable so you should overclock to 700MHz which is the highest I got without reboots. pll2_l_val=73 gives you 700MHz.
Click to expand...
Click to collapse
Thank u so much and TWRP doesn't work xD i have 8.5 mb free on system but it can't create the folders on bootmenu
sfoot13 said:
Thank u so much and TWRP doesn't work xD i have 8.5 mb free on system but it can't create the folders on bootmenu
Click to expand...
Click to collapse
I've released an .exe version of my script. This should work now .
Link: http://www.mediafire.com/?0kwmx4whjj1ua8c
Thank u bro and sorry but i can't overclock it to 700 =/
i installed TWRP but it doesn't work and when i turn on my mobile it freezes on home screen :/ is a mess.... it's possible install it via recovery (temportal CWM)?
OFF TOPIC.
Congrats on your well deserved mention on the portal.
sfoot13 said:
i installed TWRP but it doesn't work and when i turn on my mobile it freezes on home screen :/ is a mess.... it's possible install it via recovery (temportal CWM)?
Click to expand...
Click to collapse
It worked for others but in your situation the only thing I can advise is to do a data wipe and relfash SBF file. Just go to Guitwo2's there to install permanent CWM.
Link: http://forum.xda-developers.com/showthread.php?t=2229233
rootdefyxt320 said:
It worked for others but in your situation the only thing I can advise is to do a data wipe and relfash SBF file. Just go to Guitwo2's there to install permanent CWM.
Link: http://forum.xda-developers.com/showthread.php?t=2229233
Click to expand...
Click to collapse
:good: Working! Thank u so much, now i have CWM working on my defy mini, i'm really thankful, thanks again
Hi, it's me again... i have a new trouble
i installed the xt320_bootmenu.zip (from this thread http://forum.xda-developers.com/showthread.php?t=2229233) the first time that i rebooted works fine, but the on the second reboot it doesn't work, then i went to data to check if test.log was there and here's the problem... no test.log...
init.d was working fine until that i did it, i guess that my phone have troubles making work init.d
some solution for this annoying guy? thanks in advance!
sfoot13 said:
Hi, it's me again... i have a new trouble
i installed the xt320_bootmenu.zip (from this thread http://forum.xda-developers.com/showthread.php?t=2229233) the first time that i rebooted works fine, but the on the second reboot it doesn't work, then i went to data to check if test.log was there and here's the problem... no test.log...
init.d was working fine until that i did it, i guess that my phone have troubles making work init.d
some solution for this annoying guy? thanks in advance!
Click to expand...
Click to collapse
Looks like 97bootmenu deleted itself, please reinstall the CWM zip again and it should work.
I DO NOT TAKE CREDIT FOR THE WORK. I ONLY TRANSLATED THE SCRIPTS TO ENGLISH .
I AM NOT RESPONSIBLE IF YOU BRICK OR BREAK YOUR FUJITSU.
I have managed to find a bat file which will allow you to root your F-02E japanese phone.
I have also found a script to allow system R/W made by kikuhare
Steps Involved:
Make sure your phone has 100% charge.
Download the Root + System Mount
Extract the zip's to different folders.
Enable USB debugging under Menu > Settings > Developer Options.
Point to the folder where you extracted drivers from "usb_driver_F-02E_1.0.zip". Wait for drivers to install.
Make sure the phone is connected as PTP not MTP.
CMD into the folder "f-02e_oneclick_su_installer". It is inside the "Root + System Mount_1" files folder.
Run the runme.bat.
Download "Root Checker by joeykrim" from the Play Store.
Run the "Root Checker" app
Wait for the process to finish.
UPDATE System R/W
Connect phone to computer
Download the System Read Write Mounter_1.zip <<<<<< Only need to download if you did not download the "Root + System Mount_1.zip" file.
CMD into the "F-02E_system-mounter" It is inside the "Root + System Mount_1" files folder.
Extract the file and run the"START.bat"
Run everytime the system restarts to mount system as R/W.
Enjoy root .
NOTE: This method does not give full root permissions. You will still be able to underclock the CPU to some degree and use the CoreControl app to disable cores. I will have to run start.bat inside F-02E_system-mounter folder everytime the phone restarts to get system R/W
Drivers: usb_driver_F-02E_1.0.zip
Root Includes System Mount: Root + System Mount_1.zip
System R/W Mounter: System Read Write Mounter_1.zip
Screenshots:
Feel free to ask questions.
anaschillin said:
Hi, I have managed to find a bat file which will allow you to root your F-02E japanese phone. I do NOT take CREDIT for the work. I have merely found the zip. I have tested it and it works. I AM NOT RESPONSIBLE IF YOU BRICK OR BREAK YOUR FUJITSU.
Steps Involved:
Make sure your phone has 100% charge.
Extract the zip's to different folders.
Enable USB debugging under Menu > Settings > Developer Options.
Point to the folder where you extracted drivers from usb_driver_F-02E_1.0.zip. Wait for drivers to install.
CMD into the folder where you extracted the f-02e_oneclick_su_installer.zip files.
Run the runme.bat.
Download RootChecker from the Play Store. https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en
Reboot the phone.
Run the RootChecker app
Wait for te process to finish.
Enjoy root .
NOTE: This method does not give full root permissions. You will still be able to underclock the CPU to some degree and use the CoreControl app to disable cores.
Drivers:
http://www.4shared.com/zip/kGmw0Suu/usb_driver_F-02E_10.html?
Root: http://www.4shared.com/zip/D90h9kH2/f-02e_oneclick_su_installer.html?
Feel free to ask questions.
Click to expand...
Click to collapse
I havent even got the phone yet but are there any custom roms that work on this phone? Thanks
the-blind-bandit said:
I havent even got the phone yet but are there any custom roms that work on this phone? Thanks
Click to expand...
Click to collapse
No, not enough developers and interest for the phone outside Japan. I doubt anyone will be willing to put in effort as well
Oh well, but it is a very good phone, i think ill still get it though. I just wanted to know is half of it in Chinese even if you select english, i just heard this on youtube about another one of fujitsu's phones?
Sent from my Xperia T
the-blind-bandit said:
Oh well, but it is a very good phone, i think ill still get it though. I just wanted to know is half of it in Chinese even if you select english, i just heard this on youtube about another one of fujitsu's phones?
Sent from my Xperia T
Click to expand...
Click to collapse
Only Docomo and Fujistu apps are in Japanese. Everything else is in English.
Thats fine i suppose with root explorer i can delete those apps by deleting the apk in system app? Also if you have xposed app settings you can change the language per app would that also work?
Sent from my Xperia T
the-blind-bandit said:
Thats fine i suppose with root explorer i can delete those apps by deleting the apk in system app? Also if you have xposed app settings you can change the language per app would that also work?
Sent from my Xperia T
Click to expand...
Click to collapse
I have just frozen them, just incase if the phone needs the at somepoint. Xposed framework doesnt work as it need system R/W and the root method has not allowed system R/W mainly because the phone bootloader not unlocked. Secondly make sure you do not uninstall/disable the Phonebook and Phonebook Service provided by Docomo. Its key to allowing you to add and sync contacts.
So Xposed wont work at all then, thats a shame what about lucky patcher, does that need R/W?
Sent from my Xperia T
Improved the .bat file. Now you will have system R/W
Download the root file again and run it. Follow the steps starting at 10 if you have already rooted. :good:
Thanks
Sent from my Xperia T
anyone else besides the OP got their f02 rooted with this?
I may not be able to help any further. I have boot looped my phone. I cannot get it past the NTT Docomo screen. I think I know what is causing it but I cannot get the phone connected to the PC. I may need to send it into Fujitsu.
Good luck on fixing it
Sent from my Xperia T
I tried the following OP method didnt work for me
Thank! i just got the F-02e today. will try to root it.
btw, have you overcome a heating and self-shutting off prob on this phone?
anaschillin said:
Hi, I have managed to find a bat file which will allow you to root your F-02E japanese phone. I do NOT take CREDIT for the work. I have merely found the zip. I have tested it and it works. I AM NOT RESPONSIBLE IF YOU BRICK OR BREAK YOUR FUJITSU.
Steps Involved:
Make sure your phone has 100% charge.
Extract the zip's to different folders.
Enable USB debugging under Menu > Settings > Developer Options.
Point to the folder where you extracted drivers from usb_driver_F-02E_1.0.zip. Wait for drivers to install.
CMD into the folder where you extracted the f-02e_oneclick_su_installer-improved.zip files.
Run the runme.bat.
Download RootChecker from the Play Store. https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en
Run the RootChecker app
Wait for the process to finish.
UPDATE
Download ES File Explorer. Run it.
Press Menu then scroll down the list and click Root Explore.
Change the directory to root. (Meaning where you can see all system folders)
Look for system and hold the folder, then press more then properties.
Press Change in permissions.
Tick all the boxes at the bottom.
Enjoy root .
NOTE: This method does not give full root permissions. You will still be able to underclock the CPU to some degree and use the CoreControl app to disable cores. I have not been able to mount system as R/W and I had trouble installing BusyBox.
Drivers: usb_driver_F-02E_1.0.zip
Root: f-02e_oneclick_su_installer-improved.zip
Screenshots:
Feel free to ask questions.
Click to expand...
Click to collapse
anaschillin said:
I may not be able to help any further. I have boot looped my phone. I cannot get it past the NTT Docomo screen. I think I know what is causing it but I cannot get the phone connected to the PC. I may need to send it into Fujitsu.
Click to expand...
Click to collapse
i hope they can fix it immedietly, only you have work for this device (i hope any other)
question:
anyone have a stock rom for this device? may show me that's link?
Click to expand...
Click to collapse
Hi I am in the same situation, uninstall many applications in Japanese that I have the phone now in its box sirbe not all, send email to the seller took days with him and a solution is supposedly looking for me if I were to fix it passeth forums or sbrire a new post with the solution that would not be other than the original rom flaseo greetings
GattacaWroclaw said:
Hi I am in the same situation, uninstall many applications in Japanese that I have the phone now in its box sirbe not all, send email to the seller took days with him and a solution is supposedly looking for me if I were to fix it passeth forums or sbrire a new post with the solution that would not be other than the original rom flaseo greetings
Click to expand...
Click to collapse
You can reset the factory settings. Reboot the phone and hold the volume up, the phone will boot into recovery mode. You will be able to do a factory recovery.
armei said:
Thank! i just got the F-02e today. will try to root it.
btw, have you overcome a heating and self-shutting off prob on this phone?
Click to expand...
Click to collapse
I have not been able to overcome the issue. It is a design issue. Because it is waterproof phone the heat cannot disperse.
The only thing I have been able to do is keep the CPU frequency down to lower the time it takes for the phone to heat up.
garynsa said:
I tried the following OP method didnt work for me
Click to expand...
Click to collapse
What does it, when you run the root file?
Could you also tell your build number. Is it VR17xxx or VR16xxx?
[OBSOLETE THREAD]
This thread is obsolete. A solution was found, which is posted here:
http://forum.xda-developers.com/g4/help/method-to-root-lg-g4s-model-h735-lg-g4-t3248030
Please use the new thread for discussions.
------------------------
Original thread:
------------------------
Hi,
I have been trying to root the LG G4S (H735), also known as "LG G4 Beat".
I tried two things:
Approach 1
I tried the method posted by konsolen in this thread:
http://forum.xda-developers.com/g4/general/lg-g4s-world-root-lg-devices-t3231759
but it didn't work for me. I tried several times with varying approaches, but the boot process always gets stuck on the LG logo.
Approach 2
I also tried to inject the root as suggested in this thread for the G4:
http://forum.xda-developers.com/g4/help/rooting-lg-h735-g4-beat-t3192491
I've used the Inject_Root_G4.zip from this link, which I believe is the same shared elsewhere:
https://mega.nz/#!BIxUzbqI!nt2YnGnGQlSiBQ-Ar-c-q7oDMIEsg6xd0Kmek-q0clg
And I get the same problem - stuck on the LG logo when booting.
For anyone who wants to reproduce Approach 2 to maybe find a solution:
1. Start up LGFlashTool2014. You can follow instructions in thread by konsolen (see Approach 1 above). You can use his .kdz file as well. Important: Pull out your USB cable as soon as the green letters COMX (with a number instead of X) appear on the phone. My flashtool actually didn't display the progress percentage, but apparently this at 9%. It doesn't matter if you don't see the percentage though, I've verified with this KDZ image that if you pull the cable at the very moment the green letters appear, nothing is corrupted. The phone will still display 0%. Leave it as it is after you unplugged the cable.
2. Kill your flash tool with the windows task manager. After it closed, you can plug the phone back in and open a windows command line in the folder where your Send_Command.exe is (you can download the package in konsolen's instructions which contains Send_Command.exe as well).
3. Open the console to your phone with
Code:
Send_Command.exe \\.\COMX.
(with your number instead of X)
You will have to do steps 1-3 every time you want to get this console, for example to run all the dd commands below.
4. Calculate the dd parameters and backup your system partition into a .img file. There is an excellent guide by dominik-p for how to determine your individual dd parameters:
http://forum.xda-developers.com/g4/help/how-to-determine-dd-parameters-lg-g4-t3184867
5. Keep a copy of your system.img somewhere safe, you can use it to restore your system if something goes wrong. So don't use this original in the next steps!
6. Copy the .img file to a linux system and mount it. I'm guessing who is trying this knows how to do this. Anything you change in the folder you mounted the image on, will be saved in the image. You can then use this updated image to overwrite your original system partition, again with dd (as described in the thread by dominik-p) using your parameters. So here's the crucial bit: You get root access to your system files via linux. When you know the right things to mess with, you can root your phone with the updated image. Injecting the root as done in step 8 is one way to change the system on the G4 in order to root it.
7. [Optional] If you are new to this, you may want to do a simple test before you continue.
Create a testfile (test.txt) on the mounted system partition. Then copy the .img file back to your phone and try to "dd" it back over your system partition.
Then, check if you see the test file on your system partition -- you may have to reboot the phone after the dd command (and log back in with Send_Command.exe) in order to see the updates.
8. Inject root with the Inject_Root_G4.zip on the mounted folder of the image on your linux system. You can follow instructions (Step 2) here:
http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
9. Copy the new img file to your phone and "dd" it over your system partition, using your own dd parameters.
10. Reboot the phone (you can also just type LEAVE in the Send_Command.exe console).
Now, it should be rooted - if it worked for you!
If it worked for you, that's great. It didn't for me, it got stuck on the LG logo in the boot process again. So I had to write my original system.img back onto my system partition to get the phone back.
I did get the following errors in Step 8 above, though I did try anyway to use the resulting image. The errors may have something to do with my problem, but it may also be because the inject root is for the G4, not the G4s.
Code:
sudo ./autoroot.sh
cp: cannot create regular file ‘operatingtable/lib64/libsupol.so’: No such file or directory
chmod: cannot access ‘operatingtable/lib64/libsupol.so’: No such file or directory
chcon: cannot access ‘operatingtable/lib64/libsupol.so’: No such file or directory
chmod: cannot access ‘operatingtable/bin/app_process64_original’: No such file or directory
chcon: cannot access ‘operatingtable/bin/app_process64_original’: No such file or directory
chmod: cannot access ‘operatingtable/bin/app_process_init’: No such file or directory
chcon: cannot access ‘operatingtable/bin/app_process_init’: No such file or directory
If anyone finds a solution to this, or has any ideas what could be tried, I would be very interested to hear it. I'm new to rooting phones and don't have much experience beyond what I did in the last days.
Cheers
Jennifer
jen.magnolis said:
4. Calculate the dd parameters and backup your system partition into a .img file. There is an excellent guide by @dominik-p for how to determine your individual dd parameters:
http://forum.xda-developers.com/g4/help/how-to-determine-dd-parameters-lg-g4-t3184867
Click to expand...
Click to collapse
Happy that my guide has helped you
As I said here:
http://forum.xda-developers.com/g4/help/rooting-lg-h735-g4-beat-t3192491/page5
Everyone who is interested to inject root must edit the autoroot.sh from the inject.zip and use the correct files from SuperSU
More information about the files:
https://su.chainfire.eu
Maybe you have to use other files. Not the files from the inject.zip
Download the Update-SuperSU zip from http://download.chainfire.eu/supersu
Copy the files you need to the "su" folder of the extracted inject.zip
For information which files are needed read the "update-binary" file from the SuperSU zip.
(located here META-INF/com/google/android/update-binary)
Good luck everyone :good:
Thanks again for the links! I'll try again soon, when I get time for it, and report the results here
By the way, here's the ls -lR of my system.
Ok, no problem, take your time.
I've got also lot of other work to do...
I just read your system.txt (thanks)
According to these lines:
Code:
lrwxr-xr-x. 1 root 2000 13 Aug 24 02:05 app_process -> app_process32
-rwxr-xr-x. 1 root 2000 13588 Aug 24 02:05 app_process32
It seems that the firmware is 32 bit.
More info about your firmware is in /system/build.prop
So you have to take the right lines from update-binary and copy them and edit the autoroot.sh
Please don't ask me which lines. It's a bit difficult... (you have to understand the logic in update-binary)
Then copy the files from the right folder (arm?) to the "su" folder.
Sorry. I'm out now here for the next time. I have a H815 and happy with it.
I think you will find the solution. :good:
Custom Recoverys
Hi All
Are there any custom recovery's for the G4 beat/G4s
Thanks
Thanks dominik-p for your help. Good luck with your other work, don't worry I won't distract you with asking questions You already helped a lot.
benji5688, you can check for official firmware (.kdz file) on this link, pasting your IMEI instead of YOUR-IMEI in the link below.
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=YOUR-IMEI
I did not find any for mine there, but I did find it on
http://devtester.ro/projects/lg-firmwares/
Which brought me to this link where I could find mine:
http://pkg02.azure.gdms.lge.com/dn/downloader.dev?fileKey=FW703UV132GQAUP7A0ED99N/H73510c_00.kdz
but you should look for your specific model.
jen.magnolis said:
Hi,
I have been trying to root the LG G4S (H735), also known as "LG G4 Beat".
I tried two things:
Click to expand...
Click to collapse
LOL
I did the exact same thing as you, and really the EXACT, I also contacted dominik-p for the same problem you got with the bs. LOL
Was about to do the same thing you did here too just told that to dominik-p lol.
You post is great, well detailled. Hope someone found something
But got something different. my phone is the LGH731 LG G4 Vigor from Videotron in Canada.
If someone need files or system.img LINK
That's not the exact same thing as the post owner but i'm pretty sure the root method will be. (DON'T use this system.img to inject in you H735) it's from a H731 and they don't have the same partition size.
Ha, that's funny, and you got the same problem of course (frozen logo boot).
We will find a solution. It's just a matter of time. I'm a bit pressed for work in the next days but I'll get back into it around mid week. I think the main problem was, as I suspected and also as dominik-p pointed out, we've been using the wrong inject files. And the G4s is 32 bit so obviously it won't work with 64 bit libs.
First thing I'll try is using the other files from the link dominik-p shared. I'll also read the guide and try to understand which files need to be changed to gain root access in general, i.e. learn the basics of how to root. Then I think/hope I'll be able to fix this. And finally get to move all my stuff onto SD and get my storage back
Meanwhile, if you get any new results, let me know.
Cheers
jen.magnolis said:
Ha, that's funny, and you got the same problem of course (frozen logo boot).
We will find a solution. It's just a matter of time. I'm a bit pressed for work in the next days but I'll get back into it around mid week. I think the main problem was, as I suspected and also as dominik-p pointed out, we've been using the wrong inject files. And the G4s is 32 bit so obviously it won't work with 64 bit libs.
First thing I'll try is using the other files from the link dominik-p shared. I'll also read the guide and try to understand which files need to be changed to gain root access in general, i.e. learn the basics of how to root. Then I think/hope I'll be able to fix this. And finally get to move all my stuff onto SD and get my storage back
Meanwhile, if you get any new results, let me know.
Cheers
Click to expand...
Click to collapse
Yes i'm trying this today (the 32-64 bits thing)
Custom recovery
What does this file do though?
Is it a custom recovery or is it the stock rom?
Thanks Benji
benji5688 said:
What does this file do though?
Is it a custom recovery or is it the stock rom?
Thanks Benji
Click to expand...
Click to collapse
It's the stock ROM. It can be used for recovery, depending what your problem is. If you destroyed your ROM by trying to root, you can recover with this.
If you mess with something in your system partition (where the Android OS is installed), you'd need a copy of your individual system partition (like a "backup") to restore. This highly depends on your phone/version, so you have to do this backup yourself. You can follow the instructions with the dd parameters, linked to from the main thread.
Are there any custom recoverys
Hi
Are there any custom recovery available, I want to get Xposed.
Can anyone make one?
Thanks for all the help
benji5688 said:
Hi
Are there any custom recovery available, I want to get Xposed.
Can anyone make one?
Thanks for all the help
Click to expand...
Click to collapse
I far as I know to get Xposed you need to be rooted... Well there is no root method availaible, well you can try the methods that Jen explained here but I doubt they will work... if yes, you lucky ****
Is the g4s running marshmallow? Is so you would need to use a compatible su install.
Sent from my VS986 using XDA Free mobile app
larsdennert said:
Is the g4s running marshmallow? Is so you would need to use a compatible su install.
Sent from my VS986 using XDA Free mobile app
Click to expand...
Click to collapse
No the problem is really just changing the 64 bits command to make then use the 32 bits ones
I manage everything except this one
Code:
chcon --reference=operatingtable/bin/app_process32 operatingtable/bin/app_process64_original
I agree with xsteacy, this will most likely not work, that's why we opened this discussion
We just have to find the right files to use (instead of the 64 bit ones).
I will get back onto the subject by Wednesday when I have time.
I solved it! My phone is rooted
I asked someone to test my script before I post the results. Hang on there, tomorrow I'll post the solution.
Good times!
jen.magnolis said:
I solved it! My phone is rooted
I asked someone to test my script before I post the results. Hang on there, tomorrow I'll post the solution.
Good times!
Click to expand...
Click to collapse
0.0 OH!?
Ok I'm putting it out there for others to test as well.
Please report if it worked so I can take this into account before updating the main thread instructions.
In the attached .zip file there is a README with instructions.
Note: Thanks goes to @konsolen who shared instructions on how to open the COM port on the H735.
The script in konsolens post is essentially the upater-binary script of the SuperSU package, but with a few modifications.
That may have been necessary on konsolens phone, but it didn't work on mine. For me, using the original script worked.
However, the zip file has to be extracted manually with busybox before the updater-binary script is started. I am not
sure if busybox absolutely needs to be in the /sbin folder, but that's where I saw elsewhere that it belonged, so
I moved it over there in my script. I haven't tested this with busybox being elsewhere.
Thanks goes also to @dominik-p for sharing the link to excellent documentation and for his instructions on how
to make a backup (with dd) of your system, in case anything goes wrong.
UPDATE: I did all commands in root_lgh375.sh manually when I found it already worked, so please report if all is good with the script, but I think it should be, it only does what I did manually.
Congratulations @jen.magnolis
Well done
Guys i tried to install MIUI 7 on my amazon firephone i downloaded all the files and did a reboot in recover all going good then when i tried to install miui files it got stuck in the recovery mood and i restarted the phone and now it is stucked on amazon logo nothing doing else even i tried wipe data twice from hard reset mood please help did it brick my phone? help me to solve this.
hamza said:
Guys i tried to install MIUI 7 on my amazon firephone i downloaded all the files and did a reboot in recover all going good then when i tried to install miui files it got stuck in the recovery mood and i restarted the phone and now it is stucked on amazon logo nothing doing else even i tried wipe data twice from hard reset mood please help did it brick my phone? help me to solve this.
Click to expand...
Click to collapse
if you can acces to recovery, the only thing you can do is adb sideload ...bin
with an original stock ROM for your fire phone
(.bin must be the extension of the file, that you can get from official amazon site)
pipataki said:
if you can acces to recovery, the only thing you can do is adb sideload ...bin
with an original stock ROM for your fire phone
(.bin must be the extension of the file, that you can get from official amazon site)
Click to expand...
Click to collapse
Thanks a lot for your help after starting this thread i did a lot of research about it and i got the same solution from Xda and i tried it is same manner as some nice people posted it on this site but now another issue is being created automatically which is adb sideload command is not working when i write the following command
adb sideload "filename.bin"
its shows me an error "*cannot read filename.bin"
i tried it by changing the file name as "update.bin" and also tried it same file name which i downloaded from the amazon site. Please help me to resolve issue. Thanks again.
hamza said:
Thanks a lot for your help after starting this thread i did a lot of research about it and i got the same solution from Xda and i tried it is same manner as some nice people posted it on this site but now another issue is being created automatically which is adb sideload command is not working when i write the following command
adb sideload "filename.bin"
its shows me an error "*cannot read filename.bin"
i tried it by changing the file name as "update.bin" and also tried it same file name which i downloaded from the amazon site. Please help me to resolve issue. Thanks again.
Click to expand...
Click to collapse
filename is the name of file... <file.bin> you have to download that file from amazon or see in index thread
pipataki said:
filename is the name of file... <file.bin> you have to download that file from amazon or see in index thread
Click to expand...
Click to collapse
yeah i downloaded the file from amazon site and its original name was "update-kindle-35.4.6.6_user_466001420.bin" but i changed it to "update.bin" and it didn't work.
hamza said:
yeah i downloaded the file from amazon site and its original name was "update-kindle-35.4.6.6_user_466001420.bin" but i changed it to "update.bin" and it didn't work.
Click to expand...
Click to collapse
its still not working still showing that error "cannot read file.bin"
hamza said:
its still not working still showing that error "cannot read file.bin"
Click to expand...
Click to collapse
If you have the device via adb (with adb devices command) you can do an adb sideload sure... so in your case I supose, the file is corrupted... better dont rename it... but, if you can connect via adb, you can sideload sure...
pipataki said:
If you have the device via adb (with adb devices command) you can do an adb sideload sure... so in your case I supose, the file is corrupted... better dont rename it... but, if you can connect via adb, you can sideload sure...
Click to expand...
Click to collapse
no file was not corrupted because i downloaded another file from another site and it is showing same error i really cant understand what is happening. Is there any administration need?
hamza said:
no file was not corrupted because i downloaded another file from another site and it is showing same error i really cant understand what is happening. Is there any administration need?
Click to expand...
Click to collapse
did you do adb devices first?... first you have to know if adb can connet with the device... that will be listed with that command... adb devices
if you want send an screenshot with the result of making adb devices
Try to sideload what version of fire os you had before MIUI upgrade. If you had fireos 4.6.6, sideload 4.6.6, if you had 3.6.5 sideload 3.6.5
ozan2 said:
Try to sideload what version of fire os you had before MIUI upgrade. If you had fireos 4.6.6, sideload 4.6.6, if you had 3.6.5 sideload 3.6.5
Click to expand...
Click to collapse
i was having 4.6.6 and i sideloaded this version i am shocked that all things i am doing are totally good but why this error is occuring
hamza said:
i was having 4.6.6 and i sideloaded this version i am shocked that all things i am doing are totally good but why this error is occuring
Click to expand...
Click to collapse
I think that here in my computer I have the original update of Stock Rom, If you want I can upload it to my shared folder...
(left 3 hours and 5 minutes, maybe)...
to be sure that the upload and the download then is rigth, I tell you the exactly weight of file...
1314263238 bytes, you can test if the file you had has the same weight...
pipataki said:
I think that here in my computer I have the original update of Stock Rom, If you want I can upload it to my shared folder...
(left 3 hours and 5 minutes, maybe)...
to be sure that the upload and the download then is rigth, I tell you the exactly weight of file...
1314263238 bytes, you can test if the file you had has the same weight...
Click to expand...
Click to collapse
Size of my file is 1.2 GBs which is approximately equal to your file as you told me. I actually download it from amazon original site not any third party site but yeah upload it and please give me the link i will surely be thankful to you. I really appreciate your help and really happy to be new here at Xda developer.
hamza said:
Size of my file is 1.2 GBs which is approximately equal to your file as you told me. I actually download it from amazon original site not any third party site but yeah upload it and please give me the link i will surely be thankful to you. I really appreciate your help and really happy to be new here at Xda developer.
Click to expand...
Click to collapse
is uploaded totally...
the url of shared folder is in my Lollipop thread...
Are you accesing sideload by recovery?...
sideload only works invoked in recovey of the phone, in safestrap or in stock recovery
pipataki said:
is uploaded totally...
the url of shared folder is in my Lollipop thread...
Are you accesing sideload by recovery?...
sideload only works invoked in recovey of the phone, in safestrap or in stock recovery
Click to expand...
Click to collapse
Yes I am accessing it through phone recovery because i cant turn my phone on thats why i cant use safestap thats why i put my phone on recovery mood and selects install from adb option then from laptop i open console by pressing nd holding shift and right click and selecting open command prompt where my original amazon rom is placed then i use to write the sideload command which is adb sideload <filename.bin> and the then it shows error *cannot read <filename.bin>
That is all the procedure what i do everytime and it get failed please let me know if i am doing any thing wrong in it. Thank you
hamza said:
Yes I am accessing it through phone recovery because i cant turn my phone on thats why i cant use safestap thats why i put my phone on recovery mood and selects install from adb option then from laptop i open console by pressing nd holding shift and right click and selecting open command prompt where my original amazon rom is placed then i use to write the sideload command which is adb sideload <filename.bin> and the then it shows error *cannot read <filename.bin>
That is all the procedure what i do everytime and it get failed please let me know if i am doing any thing wrong in it. Thank you
Click to expand...
Click to collapse
Try using another wire and/or another port and/or another file... (the original stock that I had is in my shared folder, that one for exemple or any other one)... I hope you could relive it...
pipataki said:
Try using another wire and/or another port and/or another file... (the original stock that I had is in my shared folder, that one for exemple or any other one)... I hope you could relive it...
Click to expand...
Click to collapse
Thank You so much for your such response got it okay the problem was i didn't unblock the update file which dont know earlier but as you reffer me another link i worked on it and i got my phone back. Once again thank you so much it was really nice to be here. I will suggest all my friends your site.
hamza said:
Thank You so much for your such response got it okay the problem was i didn't unblock the update file which dont know earlier but as you reffer me another link i worked on it and i got my phone back. Once again thank you so much it was really nice to be here. I will suggest all my friends your site.
Click to expand...
Click to collapse
you can go to mobile shop and it will cost only 200 to 300 rupee for software, i also had this issue (soft brick) then i tried alot but finally i go to mobile shop and install the software ..
hamza said:
Yes I am accessing it through phone recovery because i cant turn my phone on thats why i cant use safestap thats why i put my phone on recovery mood and selects install from adb option then from laptop i open console by pressing nd holding shift and right click and selecting open command prompt where my original amazon rom is placed then i use to write the sideload command which is adb sideload <filename.bin> and the then it shows error *cannot read <filename.bin>
That is all the procedure what i do everytime and it get failed please let me know if i am doing any thing wrong in it. Thank you
Click to expand...
Click to collapse
Hello,
This may be a stupid question but did you specify the proper path? ie: c:\'filename"
just a shot, good luck
slim1001 said:
Hello,
This may be a stupid question but did you specify the proper path? ie: c:\'filename"
just a shot, good luck
Click to expand...
Click to collapse
Yes man, his phone is recovered and I had this error, solution for "cannot read" is here: https://forum.xda-developers.com/fire-phone/help/adb-sideload-error-read-t3634246