Related
So I'm not fluent in the linux terminal. I'm basically illiterate, deaf and dumb. So here I am trying to root using toasts tutorial, How To Root The HTC EVO ~ Part-1 \0/
the forum won't let me post links yet., and apparently the software here thinks some part of the code I'm posting is a link.
Anyway I'm at this step,
- At this point it will boot into a rooted rom.
- YOU ARE NOW ROOT!!!
- rename the PC36IMG.zip on your sdcard:
- plug your phone into a usb port on your desktop and do:
Click to expand...
Click to collapse
I may be root but I had a problem and had to redo this step... my sdcard was not being recognized. After reflashing/ updating I was able to access it again.
Now this rename the zip file step... I'm thinking if I rename it the code I'm supposed to enter isn't going to work. What should I rename it to?
How should I enter this code? first off my sd card isn't called sdcard it's called an 8 digit number.
I tried this (can't post the code for some reason) without changing the name of the zip file. I'm thinking I don't have the locations right because I know the file is in there.
I need some direction to get to the next step.
Thanks
Mods please move this thread....
to wherever it will get the most or correct exposure. Sorry if I put it in the wrong place.
i have no idea what your doing...i rooted via the unREVOked method...i had to downgrade to 2.1, then actually root...can u send me a PM with what tutorial your following? and also the current info you have for your phone, like what its running (2.1 or 2.2) and stuff of that nature.... we shall see if i can help, not sure but its worth a shot
okay form what i read you have already flashed the .zip. Make sure you clear your data and cache as these will cause boot loops if not cleared. Also you can rename the .zip to anything you want, this just makes it so the bootloader does not try to install the .zip a second time.
oshizzle1991 said:
i have no idea what your doing...i rooted via the unREVOked method...i had to downgrade to 2.1, then actually root...can u send me a PM with what tutorial your following? and also the current info you have for your phone, like what its running (2.1 or 2.2) and stuff of that nature.... we shall see if i can help, not sure but its worth a shot
Click to expand...
Click to collapse
I'm running 2.1. I never upgraded. The tutorial I'm following is in thread #690762 I'll try to pm the link but I don't think they'll let me. I thought unrevoked wasn't a full root. I want to unlock nand. I'm also using Ubuntu here, not windows.
http://forum.xda-developers.com/showthread.php?t=690762
nfaust01 said:
okay form what i read you have already flashed the .zip. Also you can rename the .zip to anything you want, this just makes it so the bootloader does not try to install the .zip a second time.
Click to expand...
Click to collapse
Nice looks like I'm allowed to put up links now... Thanks!
Yes I flashed the .zip my phone called it "updating" when it was going on.
Make sure you clear your data and cache as these will cause boot loops if not cleared.
Click to expand...
Click to collapse
Do I do that from the boot menu?
Also you can rename the .zip to anything you want, this just makes it so the bootloader does not try to install the .zip a second time.
Click to expand...
Click to collapse
I just removed the .zip part. What is the point of the next step, which I couldn't get to work, if I rename the file?
Code:
adb shell mv /sdcard/PC36IMG.zip /sdcard/root-PC36IMG.zip
Well I guess I'm going to start over and wait for the latest unrevoked to come back out. Thanks to everyone that tried to help. "NO ROOT FOR YOU!"
You have a lot to learn....
First of all, don't rename the sdcard, rename pc36img.zip. Just rename it to anything you want so boat loader doesn't recognize it and try to update itself. Next, you aren't utilizing root. You do have a rooted boot loader, but you are still using a protected recovery and rom. Install a custom recovery and flash a new rom so you can be cool.
dkdude36 said:
First of all, don't rename the sdcard, rename pc36img.zip
Click to expand...
Click to collapse
Yes, I know I have a lot to learn. I didn't rename the sdcard, that wasn't possible. I figured part of the problem with getting this to work was the path. My sdcard wasn't called sdcard it was called some 8 digit number. I eventually worked around pushing the file to the sd card by installing the phone as a drive and dragging the file to the sdcard.
Just rename it to anything you want so boat loader doesn't recognize it and try to update itself.
Click to expand...
Click to collapse
After I rebooted and updated/ flashed the file, I renamed the file on the sdcard by removing the .zip. I did this via disk drive on my laptop because I wasn't getting anywhere with the command line.
Again this part didn't make any sense to me, not that most of it does, but what was the point of the next command in the directions if I renamed the file?
Next, you aren't utilizing root. You do have a rooted boot loader, but you are still using a protected recovery and rom. Install a custom recovery and flash a new rom so you can be cool.
Click to expand...
Click to collapse
Right "I have a lot to learn" I thought following the directions in toasts tutorial step by step would have gotten me to that point. I didn't realize I was just supposed to skip stuff when I run into problems. That kinda seems like what your telling me to do. I thought all of the commands were important.
I was hoping you had some follow up insight dkdude.
if you still on 2.1, try this method (just make sure the files aren't corrupted)
http://forum.xda-developers.com/showthread.php?t=741294
Hi,
I'm following the tutorial here: http://forum.xda-developers.com/showthread.php?t=1739426
I am on the 3rd option and am trying to load the latest clockworkmod on my GS3, I have it downloaded, but it is an .img file.
The tutorial says:
if you download this recovery you will need to extract this file (if you have issues extracting try removing the .md5 extension first) to get a recovery.img file and copy to your phone's internal /sdcard
connect your phone to computer and use adb
type adb shell
once in the shell run su
then
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
Can someone please explain this in more detail? I am looking for links to the ADB program I need as-well as how to use it to apply those commands.
Also I am having a hit-or-miss issues with Windows reading my phone as an external device, the phone reads as an established MTP connection but Windows sometimes reads it, or does not. What am I doing wrong here?
Thank you.
Info:
Phone: Samsung-SGH-I747
Carrier: AT&T
Andriod Version: 4.1.1
OS: Windows 8 64Bit
Samsung Software: Kies 2.5.0.12114_1
Here is how I done it. It's in a zip file if you already have the non-touch version installed. All you need to do with this is install from SD from CWM recovery. None of the adb stuff has to be messed with. 7th post.
http://forum.xda-developers.com/showthread.php?t=1877761
Edit: This was on down in the post you quoted. If you don't have any CWM recovery installed, then do the below, then install the above touch version zip from sd in CWM recovery.
Third, alternate #3 if unfamiliar with adb commands and uncomfortable using any command line
Decide if you want to use TWRP or CWM.
If you would like to install ClockworkMod recovery then grab Rom Manager from the Play store and in the menu select to install ClockworkMod Recovery.
I am no expert by any means but you have to run those commands in the command prompt (DOS) system. Hit the start menu and find the run and type in cmd and that will open up command line or it should be in the Accessories folder as well.
If Windows sometimes doesn't recognize your phone I would uninstall and re install the drivers to see if that helps.
I have a heck of a time to get ADB and everything working when I first started so I know how you feel. Just keep reading the forums and everything and you will get it to work.
bo.benson said:
Here is how I done it. It's in a zip file if you already have the non-touch version installed. All you need to do with this is install from SD from CWM recovery. None of the adb stuff has to be messed with. 7th post.
http://forum.xda-developers.com/showthread.php?t=1877761
Edit: This was on down in the post you quoted. If you don't have any CWM recovery installed, then do the below, then install the above touch version zip from sd in CWM recovery.
Third, alternate #3 if unfamiliar with adb commands and uncomfortable using any command line
Decide if you want to use TWRP or CWM.
If you would like to install ClockworkMod recovery then grab Rom Manager from the Play store and in the menu select to install ClockworkMod Recovery.
Click to expand...
Click to collapse
Currently my phone has NO clockwork Mod installed, I am wanting to install the latest version ( recovery-clockwork-6.0.1.2-d2att ) I have this file in .img format, I am trying to figure out how to install it on my phone -- the tutorial says add it to your sdcard, I have done that, then it says connect to your phone and use ADB commands, that is the part where I need more information, also do I wipe cache/reset settings/dalvick cache during any of this process? Should my phone be in download mode when doing ADB commands or what specifically is where I do not understand.
I would like to understand the process more in-depth and ADB as well - opposed to going the RomManager route, from my research it seems that updates/versions are available first with that method.
Thanks
Kweli87 said:
Currently my phone has NO clockwork Mod installed, I am wanting to install the latest version ( recovery-clockwork-6.0.1.2-d2att ) I have this file in .img format, I am trying to figure out how to install it on my phone -- the tutorial says add it to your sdcard, I have done that, then it says connect to your phone and use ADB commands, that is the part where I need more information, also do I wipe cache/reset settings/dalvick cache during any of this process? Should my phone be in download mode when doing ADB commands or what specifically is where I do not understand.
Thanks
Click to expand...
Click to collapse
He gave you the link to the play store app in the post. It's android terminal emulator..type terminal emulator in play store its the top app.
I just merely gave you a second option which I did and functioned flawlessly. Grab Rom Manager from the play store and select the top option to flash CWM Recovery. It will ask you your phone type and carrier and then will give you the option to install it. Easier than the whole adb thing.
Ok that route did work, thanks.
Now I installed the latest CM10 Nightly - cm-10-20121206-NIGHTLY-d2att
And then rebooted and installed the latest Gapps - gapps-jb-20121011-signed
It does not seem that any of the google apps are in my apps
Also the Play Store no longer works....just "Connection Timed Out"
Specifically I am looking to use Google Now/G-Mail/Drive/Voice/etc...
Did I do something wrong? CWM said the Gapps installed successfully. Was I supposed to wipe cache somewhere?
Thanks for the help.
bo.benson said:
He gave you the link to the play store app in the post. It's android terminal emulator..type terminal emulator in play store its the top app.
I just merely gave you a second option which I did and functioned flawlessly. Grab Rom Manager from the play store and select the top option to flash CWM Recovery. It will ask you your phone type and carrier and then will give you the option to install it. Easier than the whole adb thing.
Click to expand...
Click to collapse
Kweli87 said:
Ok that route did work, thanks.
Now I installed the latest CM10 Nightly - cm-10-20121206-NIGHTLY-d2att
And then rebooted and installed the latest Gapps - gapps-jb-20121011-signed
It does not seem that any of the google apps are in my apps
Also the Play Store no longer works....just "Connection Timed Out"
Specifically I am looking to use Google Now/G-Mail/Drive/Voice/etc...
Did I do something wrong? CWM said the Gapps installed successfully. Was I supposed to wipe cache somewhere?
Thanks for the help.
Click to expand...
Click to collapse
I have not noticed that. I used the same Gapps file to do mine and everything worked fine on I believe the 11-30 NIGHTLY, no wiping that I remember. Now this was before I got on Official JB, was still back on stock ICS. Haven't flashed CM since upgrading. I will after today as battery life sucks on the Official, if it does the same to me I will let you know.
Touch version of CWM is pretty sweet, no accidental clicks too far with the volume keys, works right from your screen. That was the link in the first post I gave you. Download it to your SD, go into recovery and install it from SD.
Looks like mine had no problems with the gapps 11-30 nightly coming from LK3. Haven't got around to downloading the latest nightly yet. Will do today. Let me know if you got it resolved.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I absolutely do not understand the flashing firmware. I'm att, on 3.19, supercid, rooted, s-off with no access to a computer. I read in some places you don't need one and I see that some people say you do, idk. I'm absolutely lost on it. All I know is to put the zip in the root of my file. I'm not certain on what zip, I know to reboot into fastboot to flash and update but afterward, I read You have to flash a dev rom or something. Idk. I'm still obviously new at the unlocked thing but I'm really good at understanding how to do most things on here or I wouldn't be where I'm at now. Help please!!!!!!
Blundog said:
I absolutely do not understand the flashing firmware. I'm att, on 3.19, supercid, rooted, s-off with no access to a computer. I read in some places you don't need one and I see that some people say you do, idk. I'm absolutely lost on it. All I know is to put the zip in the root of my file. I'm not certain on what zip, I know to reboot into fastboot to flash and update but afterward, I read You have to flash a dev rom or something. Idk. I'm still obviously new at the unlocked thing but I'm really good at understanding how to do most things on here or I wouldn't be where I'm at now. Help please!!!!!!
Click to expand...
Click to collapse
You want Lollipop firmware I suppose? Do you know your MID? What carrier and country? I can hook you up. I'd ask for you firmware version that you have now, but I assume you don't know. If you do, that would be all the info I need.
Blundog said:
I absolutely do not understand the flashing firmware. I'm att, on 3.19, supercid, rooted, s-off with no access to a computer. I read in some places you don't need one and I see that some people say you do, idk. I'm absolutely lost on it. All I know is to put the zip in the root of my file. I'm not certain on what zip, I know to reboot into fastboot to flash and update but afterward, I read You have to flash a dev rom or something. Idk. I'm still obviously new at the unlocked thing but I'm really good at understanding how to do most things on here or I wouldn't be where I'm at now. Help please!!!!!!
Click to expand...
Click to collapse
because you are in super cid, and s-off so you can flash any FW , you can refer thread Firmware Flashing without the panic attacks...
Instructions:
1. Download firmware of choice in above links
2. Rename firmware to 0P6BIMG.zip (the first character is a zero, NOT A LETTER O)
3. Put renamed firmware.zip on your external_SD
4. Boot into your bootloader and make sure your in hboot and let it update its firmware.
5. No PC, no adb, no fastboot, no terminal is needed, just a root explorer to rename and transfer the renamed firmware file to external_sd
6. After you have updated your firmware, make sure to remove the 0P6BIMG.zip from your external_sd because it will ask to update your firmware everytime your reboot to your bootloader which it is technically supposed to do but its unnecessary after you have done it once (unless you are planning on flashing firmware again).
7.Profit!
Huntervn said:
because you are in super cid, and s-off so you can flash any FW , you can refer thread Firmware Flashing without the panic attacks...
Instructions:
1. Download firmware of choice in above links
2. Rename firmware to 0P6BIMG.zip (the first character is a zero, NOT A LETTER O)
3. Put renamed firmware.zip on your external_SD
4. Boot into your bootloader and make sure your in hboot and let it update its firmware.
5. No PC, no adb, no fastboot, no terminal is needed, just a root explorer to rename and transfer the renamed firmware file to external_sd
6. After you have updated your firmware, make sure to remove the 0P6BIMG.zip from your external_sd because it will ask to update your firmware everytime your reboot to your bootloader which it is technically supposed to do but its unnecessary after you have done it once (unless you are planning on flashing firmware again).
7.Profit!
Click to expand...
Click to collapse
Yeah.....He still needs to know the info I asked him about.
Plus when he said "place it in the root of my file" shows he already looked at that thread or one similar. He doesn't understand it, so by sending him back to the thread, you're not really helping him much.
I'm not trying to rag on you, I'm just trying to help you to help others.
xunholyx said:
Yeah.....He still needs to know the info I asked him about.
Plus when he said "place it in the root of my file" shows he already looked at that thread or one similar. He doesn't understand it, so by sending him back to the thread, you're not really helping him much.
I'm not trying to rag on you, I'm just trying to help you to help others.
Click to expand...
Click to collapse
I appreciate the help. I was able to update my firmware first try. I vaguely remembered watching my friend do it to 4.4.4 a while back and when I started doing it I would remember but couldn't have gotten started without help on here. Now, I'm attempting to update twrp. I'm on 2.8.3 and need it to 2.8.4. I've downloaded flashify and have terminal emulator up but not sure where to go from here?
Blundog said:
I appreciate the help. I was able to update my firmware first try. I vaguely remembered watching my friend do it to 4.4.4 a while back and when I started doing it I would remember but couldn't have gotten started without help on here. Now, I'm attempting to update twrp. I'm on 2.8.3 and need it to 2.8.4. I've downloaded flashify and have terminal emulator up but not sure where to go from here?
Click to expand...
Click to collapse
Ha! I did it. Thanks for the help guys, much appreciated
Blundog said:
I appreciate the help. I was able to update my firmware first try. I vaguely remembered watching my friend do it to 4.4.4 a while back and when I started doing it I would remember but couldn't have gotten started without help on here. Now, I'm attempting to update twrp. I'm on 2.8.3 and need it to 2.8.4. I've downloaded flashify and have terminal emulator up but not sure where to go from here?
Click to expand...
Click to collapse
Don't use flashify. Download this onto your phone. It's the official TWRP 2.8.4.0
Rename it to "twrp.img" (no quotes) and move it from downloads onto the root of your internal storage using a file explorer. (I recommend ES File Explorer) By root of, I mean not in a folder, just on the internalSD.
Open terminal emulator and type:
su (hit enter)
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p43 (hit enter and don't screw up that command, copy and paste recommended)
That will bring you up to the newest version.
EDIT: I saw you solved your issue while I was trying to respond. :good:
xunholyx said:
Don't use flashify. Download this onto your phone. It's the official TWRP 2.8.4.0
Rename it to "twrp.img" (no quotes) and move it from downloads onto the root of your internal storage using a file explorer. (I recommend ES File Explorer) By root of, I mean not in a folder, just on the internalSD.
Open terminal emulator and type:
su (hit enter)
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p43 (hit enter and don't screw up that command, copy and paste recommended)
That will bring you up to the newest version.
EDIT: I saw you solved your issue while I was trying to respond. :good:
Click to expand...
Click to collapse
Yeh, thanks for the help. I didn't use flashify, I used the app, actually. At first it said unsuccessful but I rebooted into recovery and it was updated. A little weird but whatevr works, I guess. So if I put the. IMG on the root of my sdcard I can't use hboot ?
Blundog said:
Yeh, thanks for the help. I didn't use flashify, I used the app, actually. At first it said unsuccessful but I rebooted into recovery and it was updated. A little weird but whatevr works, I guess. So if I put the. IMG on the root of my sdcard I can't use hboot ?
Click to expand...
Click to collapse
Yes! That happens to me too. I almost always use the TWRP Manager app, and it almost always crashes, but I think the crash only happens when it tries to get back into the app after the flash. It's buggy, but it works. After the crash, the new version is always installed.
Talk about mini heart attack! Awesome!!
I have 4.6.4 AT&T OS and I want to downgrade to 4.6.3 unlock OS. In recovery mode the phone is connected with computer, I see serial number and "sideload" next, the update.bin file is in ADB folder, but at next step I get the message
"cannot read update.bin" . I run Win 10 on computer, I try also on Win 7, same problem. I downloaded
4.6.3 unlock OS first with Microsoft Edge, it has .zip extension, then downloaded with Chrome it came with .bin extension, neither one work. Any ideas ? Because I ran out.
That sounds confusing and frustrating. Where did you get the .bin from? I downloaded the one linked in this post and had no problems: http://forum.xda-developers.com/showpost.php?p=62768812&postcount=2
You definitely want a .bin file, not a zip (the .bin should be around 1.2gb). There's also the distinct possibility that ADB is improperly installed. If that's the case, there should be more info in that link that will help you.
In my signature, I link to a walkthrough describing everything I did to get my phone downgraded, rooted, etc. Maybe take a look and see if you missed any steps.
munkymack said:
That sounds confusing and frustrating. Where did you get the .bin from? I downloaded the one linked in this post and had no problems: http://forum.xda-developers.com/showpost.php?p=62768812&postcount=2
You definitely want a .bin file, not a zip (the .bin should be around 1.2gb). There's also the distinct possibility that ADB is improperly installed. If that's the case, there should be more info in that link that will help you.
In my signature, I link to a walkthrough describing everything I did to get my phone downgraded, rooted, etc. Maybe take a look and see if you missed any steps.
Click to expand...
Click to collapse
I downloaded 4.6.3 OS from 3-4 diffrent links from forum including that in your post, also direct from amazon. With Microsoft Edge, Internet Explorer the file is downloaded with .zip, no matter the link I used, so I thought that's the problem so I used Mozzila and Chrome, it came with .bin extension. The .bin file seems to be ok, I can open and extract folders and files from it with WinRAR so it's not corrupt.
About ADB, I read before how to deal with it, seems to work correctly, I can connect the phone in windows with phone on, also in recovery mode the phone appear sideload like it should. So at this point I don't no what to do.
markmm said:
I have 4.6.4 AT&T OS and I want to downgrade to 4.6.3 unlock OS. In recovery mode the phone is connected with computer, I see serial number and "sideload" next, the update.bin file is in ADB folder, but at next step I get the message
"cannot read update.bin" . I run Win 10 on computer, I try also on Win 7, same problem. I downloaded
4.6.3 unlock OS first with Microsoft Edge, it has .zip extension, then downloaded with Chrome it came with .bin extension, neither one work. Any ideas ? Because I ran out.
Click to expand...
Click to collapse
Microsoft Edge and Internet Explorer downloaded the 4.6.3 update as a zip file for me also. I've had the same error (cannot read update.bin) once when trying to sideload an update.bin. I never could figure out what the problem was, so I downgraded my phone using Safestrap. It is not recommended that you use Safestrap to update or downgrade your phone, but a few people including me have updated or downgraded their phone with Safestrap without any problems.
You will need to root your phone if you want to use Safestrap for the downgrade:
See Installing Root, Safestrap, CM11 for how to root and install Safestrap on your phone. You do not need to install CM11.
Launch Safestrap and select Install Recovery.
Download the 4.6.3 flashable-stock-image you will need for the downgrade and put the file on your phone.
Power your phone off, then power it back on.
When Safestrap starts, select RECOVERY> Install>
Browse to and select ss_update-fire-phone-35.4.6.3_user_463001620.zip.
Swipe to the right Swipe to Confirm Flash.
When the flash is complete, select Reboot System> CONTINUE>.
If you don’t want your phone rooted, launch Safestrap and uninstall Recovery, launch Kingroot and unroot your phone. I would also do a factory reset.
Edited to add: To unroot Kingroot 4.0, launch Kinguser, tap gear icon> Root authorization settings> Remove Root permission> Clear>. For Kingroot 4.5, launch Kingroot, tap gear icon> Root authorization settings> Remove Root permission> Continue> OK>. Manually uninstall any Kingroot apps that are still installed on your phone.
jack9955 said:
Microsoft Edge and Internet Explorer downloaded the 4.6.3 update as a zip file for me also. I've had the same error (cannot read update.bin) once when trying to sideload an update.bin. I never could figure out what the problem was, so I downgraded my phone using Safestrap. It is not recommended that you use Safestrap to update or downgrade your phone, but a few people including me have updated or downgraded their phone with Safestrap without any problems.
You will need to root your phone if you want to use Safestrap for the downgrade:
See Installing Root, Safestrap, CM11 for how to root and install Safestrap on your phone. You do not need to install CM11.
Launch Safestrap and select Install Recovery.
Download the 4.6.3 flashable-stock-image you will need for the downgrade and put the file on your phone.
Power your phone off, then power it back on.
When Safestrap starts, select RECOVERY> Install>
Browse to and select ss_update-fire-phone-35.4.6.3_user_463001620.zip.
Swipe to the right Swipe to Confirm Flash.
When the flash is complete, select Reboot System> CONTINUE>.
If you don’t want your phone rooted, launch Safestrap and uninstall Recovery, launch Kingroot and unroot your phone. I would also do a factory reset.
Click to expand...
Click to collapse
Thank you for your reply, I read about root/safestrap method but initially I did not want to root the phone.
Now seems to be the only choice, so thank you for info about this.
If you just type "adb devices" on the PC with the phone connected, do you see the phone? If not, then you have a driver issue. If that is the issue, the Amazon Dev. Service "Connecting your device" page may help.
Yes, at adb devices command the phone appear with serial number........ sideload. Appear connected whith phone on, I can copy on it and also in recovery mode after "apply update from ADB" . I belive that's not the problem.
I'm having the same problem. Cannot read update.bin when trying to sideload 4.6.3.
vkramac said:
I'm having the same problem. Cannot read update.bin when trying to sideload 4.6.3.
Click to expand...
Click to collapse
See this post, on how you may be able to correct your problem.
jack9955 said:
See this post, on how you may be able to correct your problem.
Click to expand...
Click to collapse
Thanks for linking this post. Regrettably, it still doesn't work...no worries though
vkramac said:
Thanks for linking this post. Regrettably, it still doesn't work...no worries though
Click to expand...
Click to collapse
I have had the exact same problem when trying to install the 4.6.3 update (cannot read update.bin), I had to use Safestrap to downgrade my phone. When you downloaded the update, was the extension a .bin or a .zip? When you say "it still doesn't work", do mean Safestrap doesn't work as well?
jack9955 said:
I have had the exact same problem when trying to install the 4.6.3 update (cannot read update.bin), I had to use Safestrap to downgrade my phone. When you downloaded the update, was the extension a .bin or a .zip? When you say "it still doesn't work", do mean Safestrap doesn't work as well?
Click to expand...
Click to collapse
I've been trying to do this through stock recovery. The file extension was .bin retrieved from Amazon's website.
I'm not interested in using Safestrap.
vkramac said:
I've been trying to do this through stock recovery. The file extension was .bin retrieved from Amazon's website.
I'm not interested in using Safestrap.
Click to expand...
Click to collapse
Yep. Can't figure this out at all. Most adb commands are working fine. ADB kill-server. ADB start-server. ADB devices. ADB reboot recovery.
Its just the ADB sideload that gets the error. Cannot read update.bin.
I'm starting to think this is WIN 10 ****ing with me.
vkramac said:
Yep. Can't figure this out at all. Most adb commands are working fine. ADB kill-server. ADB start-server. ADB devices. ADB reboot recovery.
Its just the ADB sideload that gets the error. Cannot read update.bin.
I'm starting to think this is WIN 10 ****ing with me.
Click to expand...
Click to collapse
OK, should you find a solution to the "cannot read update.bin", please post how you was able to fix the problem, your fix may help others. From an internet search, I see the most common reason for the "cannot read . . ." error is the file has a double extension of .zip.zip, bin.bin, or bin.zip.
vkramac said:
Yep. Can't figure this out at all. Most adb commands are working fine. ADB kill-server. ADB start-server. ADB devices. ADB reboot recovery.
Its just the ADB sideload that gets the error. Cannot read update.bin.
I'm starting to think this is WIN 10 ****ing with me.
Click to expand...
Click to collapse
Maybe a stupid question- But did you change the name of the downloaded bin file to "update.bin"?
Years later, but maybe it'll help. For me, it was a combo of WIndows and Bitdefender: Under properties of the update file, it said access was blocked due to the file being from another PC - checking the box there and disabling Bitdefender (only one at a time didn't help) solves the issue.
jack9955 said:
Microsoft Edge and Internet Explorer downloaded the 4.6.3 update as a zip file for me also. I've had the same error (cannot read update.bin) once when trying to sideload an update.bin. I never could figure out what the problem was, so I downgraded my phone using Safestrap. It is not recommended that you use Safestrap to update or downgrade your phone, but a few people including me have updated or downgraded their phone with Safestrap without any problems.
You will need to root your phone if you want to use Safestrap for the downgrade:
See Installing Root, Safestrap, CM11 for how to root and install Safestrap on your phone. You do not need to install CM11.
Launch Safestrap and select Install Recovery.
Download the 4.6.3 flashable-stock-image you will need for the downgrade and put the file on your phone.
Power your phone off, then power it back on.
When Safestrap starts, select RECOVERY> Install>
Browse to and select ss_update-fire-phone-35.4.6.3_user_463001620.zip.
Swipe to the right Swipe to Confirm Flash.
When the flash is complete, select Reboot System> CONTINUE>.
If you don’t want your phone rooted, launch Safestrap and uninstall Recovery, launch Kingroot and unroot your phone. I would also do a factory reset.
Edited to add: To unroot Kingroot 4.0, launch Kinguser, tap gear icon> Root authorization settings> Remove Root permission> Clear>. For Kingroot 4.5, launch Kingroot, tap gear icon> Root authorization settings> Remove Root permission> Continue> OK>. Manually uninstall any Kingroot apps that are still installed on your phone.
Click to expand...
Click to collapse
i am facing the same issue but the problem is i cant turn my phone on because it get bricked when i was trying to install MIUI 7 in it. Now it is just stuck to the amazon logo and i tried to do all these stuff to download amazon latest and installing it through adb but in command prompt it says *cannot read update.bin i cant understand what is going over here please help me out to solve this issue or i will not be able to buy a new phone dew to some financial conditions.
hamza said:
i am facing the same issue but the problem is i cant turn my phone on because it get bricked when i was trying to install MIUI 7 in it. Now it is just stuck to the amazon logo and i tried to do all these stuff to download amazon latest and installing it through adb but in command prompt it says *cannot read update.bin i cant understand what is going over here please help me out to solve this issue or i will not be able to buy a new phone dew to some financial conditions.
Click to expand...
Click to collapse
Hi, I found out your computer may block files that appears to be malicious. See this thread for information on how to unblock it.
Got it to work
I was having the same problem. I kept getting the message" cannot read file"
I was able to get it to work by typing "adb sideload" and then dragging the file in the command window right behind "adb sideload". the string will look like this
"PS C:\Users\Ryan\Desktop> adb sideload C:\Users\Ryan\Desktop\update.bin.bin
and then press enter.
Someone was "helping" me root my Mi Mix2. I can't be 100% sure what went wrong, but he managed to get it stuck in Fastboot mode, such that no matter what I do (i.e. any combination of power offs, or simultaneous button presses, or commands from terminal). I suspect he did not understand me when I said Magisk was tool best suited...he may have used some more familiar or standard tool like SuperSU or something to try and root.
Assuming I have sufficiently described my problem, is there anything I can do to get the phone back into a usable state?
Is your bootloader unlocked? If yes try to flash ROM using miflash tool.
I appreciate the response/suggestion.
fotocreaman said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
Yes. I double checked with "fastboot oem device-info" commmand
fotocreaman said:
If yes try to flash ROM using miflash tool.
Click to expand...
Click to collapse
On your advice I did that, including downloading current (?) version and current(?) version of stock ROM. I received a message to effect that a flash script (.bat) file was missing (or at least not found).
Other threads regarding this error suggest unzipping something (?) twice but I didn't see a file inside the original zip file that could be additionally unzipped, and certainly nothing with a .bat extension.
Can you put here the exact error message and when it exactly occurs? Describe the steps you did to get to that point
Hi aa040371
1- download fastboot rom for your phone and unzip it twice , put folder in C:\ storage http://update.miui.com/updates/v1/fullromdownload.php?d=chiron_global&b=F&r=global&n=
2- Look at the tutorial to use miflashtool https://c.mi.com/thread-1857937-1-1.html
regards
I'm Still Here...
So, after more than a few detours and distractions, I have my phone (Mi Mix 2S, not the plain "2" I originally indicated!) basically back to stock...good frustration-tolerance building exercise.
I am currently in the process of trying to get TWRP to remain after booting to OS. I have researched/read numerous threads on this -- e.g. boot into TWRP, flash TWRP, reboot directly into TWRP again -- but somehow none of them do the trick. Every time I boot into the OS, the Recovery partition gets overwritten and I am back to the stock recovery tool. If I can trust/believe what at least one person has indicated online, this appears to be due to a script in /system/bin, but I can't get at that file to rename or delete it. In fact, I can't even see it in the file system as that area is completely locked down. I know it is there as a Find command executed via ADB shell lists it even though it indicates it is off-limits.
So I turned my attention to loading a rooting app/tool instead hoping that would let me get TWRP to hang around for long term...another excursion in futility. My phone model is M1803D5XA, so according to one more forum thread somewhere, I am supposed to be using SuperSU rather than Magisk? Whatever...it seems impossible: most of the zip files I located don't pass security/file-signing check. The one I found that at least starts to load/install (SR5-SuperSU-v2.82-SR5-20171001224502) works fine right up until it fails while trying to update "sepolicy" files. For some reason I have to sideload SuperSU from TWRP because I am not allowed to push a file even to my SDcard via ADB.
I just don't get why this all has to be so difficult, as in each and every step along the way. I feel like Sisyphus or Job or someone similar...sigh Any thoughts or suggestions still welcome...thanks.
aa040371 said:
So, after more than a few detours and distractions, I have my phone (Mi Mix 2S, not the plain "2" I originally indicated!) basically back to stock...good frustration-tolerance building exercise.
I am currently in the process of trying to get TWRP to remain after booting to OS. I have researched/read numerous threads on this -- e.g. boot into TWRP, flash TWRP, reboot directly into TWRP again -- but somehow none of them do the trick. Every time I boot into the OS, the Recovery partition gets overwritten and I am back to the stock recovery tool. If I can trust/believe what at least one person has indicated online, this appears to be due to a script in /system/bin, but I can't get at that file to rename or delete it. In fact, I can't even see it in the file system as that area is completely locked down. I know it is there as a Find command executed via ADB shell lists it even though it indicates it is off-limits.
So I turned my attention to loading a rooting app/tool instead hoping that would let me get TWRP to hang around for long term...another excursion in futility. My phone model is M1803D5XA, so according to one more forum thread somewhere, I am supposed to be using SuperSU rather than Magisk? Whatever...it seems impossible: most of the zip files I located don't pass security/file-signing check. The one I found that at least starts to load/install (SR5-SuperSU-v2.82-SR5-20171001224502) works fine right up until it fails while trying to update "sepolicy" files. For some reason I have to sideload SuperSU from TWRP because I am not allowed to push a file even to my SDcard via ADB.
I just don't get why this all has to be so difficult, as in each and every step along the way. I feel like Sisyphus or Job or someone similar...sigh Any thoughts or suggestions still welcome...thanks.
Click to expand...
Click to collapse
Recovery will get overwritten by dm-verity, you have to flash either magisk or another mod that disables dm-verity, but personally I suggest to use a custom rom if you don't care about miui
HrX said:
Recovery will get overwritten by dm-verity, you have to flash either magisk or another mod that disables dm-verity, but personally I suggest to use a custom rom if you don't care about miui
Click to expand...
Click to collapse
Hello...thanks. I definitely don't care about MIUI...in fact the whole exercise I am struggling through is so I can get LineageOS onto my phone. I've probably read 50+ threads/posts on 6-7 different forums regarding unbricking/unlocking/rooting/TWRPing/customROMing my particular phone, but this is the first time I've seen mention of DM-Verity. I'll look into it...not really hopeful, though. But anyway...thanks again.