Installing a custom recovery on Galaxy Note 2 LTE
Samsung devices come with a unique boot mode called
Download Mode which is very similar to Fastboot Mode on some devices with unlocked bootloaders. Heimdall is a cross-platform, open source tool for interfacing with Download Mode on Samsung devices. The preferred method of installing a custom recovery is through this boot mode. Rooting the stock firmware is neither recommended nor necessary.
1. Download koush's ClockworkMod Recovery, and the Heimdall Suite:
koush's ClockworkMod Recovery: download
md5: a89a57f343b0784581c5fa4ef68209e4
Windows:
Heimdall Suite 1.4RC1 Command-line Binary(has bug): download
Heimdall Suite 1.4RC2 Command-line Binary: download
NOTE: The Heimdall Suite 1.4RC2 requires the Microsoft Visual C++ 2012 Redistributable Package to be installed on the computer, which can be downloaded here. You will need the 32/64 bit version as required by Heimdall, NOT as required by your OS. Heimdall currently seems to be 32 bit. You may well ACTUALLY need to reboot for the redistributable to install properly.
2. Power off the Galaxy Note 2 LTE and connect the USB adapter to the computer but not to the Galaxy Note 2 LTE.
3. Now boot the Galaxy Note 2 LTE into download mode by holding down Home & Volume Down & Power. Accept the disclaimer. After this insert the USB cable into the device.
Windows only:
Run the included zadig.exe in the drivers folder of the Heimdall Suite.
Choose Options » List All Devices from the menu.
Select Samsung USB Composite Device or Gadget Serial or Device Name from the drop down menu.
Click Replace Driver (having selecting "Installed Driver" from the drop down list built into the button).
NOTE: A prompt may appear warning that the installer is unable to verify the publisher of the driver, ignore it and select "Install this driver anyway." Also you may receive two strange prompts, possibly from Windows, about security. Cancel then both and just carry on.
NOTE: On Windows 8 you must disable driver signature enforcement in order to use zadig.
4. Place koush's ClockworkMod Recovery file into the Heimdall directory.
5. On the computer, open a terminal and run the following command from the Heimdall directory:
heimdall flash --recovery recovery.img --no-reboot
Tip: It may be necessary to run the command as root in Linux distributions, ie "sudo heimdall [...]". If a blue bar doesn't show up after the process has finished or this appears: "Failed to confirm end of file transfer sequence!", it may be a symptom.
Tip: it may be necessary to capitalize the name of the partition on some devices... ie --KERNEL instead of --kernel, or ---RECOVERY instead of --recovery
Tip: protocol initialization can (does?) fail if the device is connected via a USB hub - connect directly to the PC
6. A blue transfer bar will appear on the device showing the recovery being transferred.
7. You need now to manually reboot the phone into ClockworkMod Recovery mode.
8. The Galaxy Note 2 LTE now has ClockworkMod Recovery installed. Continue to the next section.
Source http://wiki.cyanogenmod.org/w/Install_CM_for_t0lte
OK, so what if the MD5SUM check is not the same for CWM? I've been trying to download the right one all night, have used the one from the CM wiki page, as well as this one, and neither one's check sum matches the one listed in the install instructions.
Returned with this error.
ERROR: Failed to confirm end of file transfer sequence!
ERROR: RECOVERY upload failed!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Related
My tab started giving al kind of errors on internal apps and stuff so i shut it down and now it is in reboot loop.
I can get it into odin download mode or fastboot mode. But i cannot see it with adb or fastboot (it doesent show up when using adb devices or fastboot devices.
i can use odin to do a pda flash but outcome is stil the same.
also did nvflash from Retail 3.1 CWM Recovery, Root & full back up!
al goes fine but after that still no adb reboot recovery or adb devices
iam desperate please help me with this
renedg said:
My tab started giving al kind of errors on internal apps and stuff so i shut it down and now it is in reboot loop.
I can get it into odin download mode or fastboot mode. But i cannot see it with adb or fastboot (it doesent show up when using adb devices or fastboot devices.
i can use odin to do a pda flash but outcome is stil the same.
also did nvflash from Retail 3.1 CWM Recovery, Root & full back up!
al goes fine but after that still no adb reboot recovery or adb devices
iam desperate please help me with this
Click to expand...
Click to collapse
Here's what you do.
Download the file linked below
Download ODIN attached below
Once both are downloaded, extract PDA_SIGNED_P7105.tar
Boot your tablet into ODIN and plug it into your PC
Open the ODIN program on your PC and check the box next to PDA
Click the PDA button and navigate to the file you downloaded earlier
Press Start and let it flash
Once it is done, it will still boot loop.
You need to go into recovery (It will now be the default recovery) and wipe data/factory reset only.
Reboot and it should load up, however you will be on 3.0.1.
You can get back to 3.1 by rooting and installing recovery again or by using the update feature in the tablet's settings.
Good luck!
http://www.mediafire.com/?gcenefqc3khcc0c
renedg said:
My tab started giving al kind of errors on internal apps and stuff so i shut it down and now it is in reboot loop.
I can get it into odin download mode or fastboot mode. But i cannot see it with adb or fastboot (it doesent show up when using adb devices or fastboot devices.
i can use odin to do a pda flash but outcome is stil the same.
also did nvflash from Retail 3.1 CWM Recovery, Root & full back up!
al goes fine but after that still no adb reboot recovery or adb devices
iam desperate please help me with this
Click to expand...
Click to collapse
Please DO NOT ask Questions in the Development forum
Moving to General
When i have done this and go into recovery (power and left volume) i stil get usb icon and download (odin) and still no device found with adb or fastboot (driver i sbeing loaded so somehow my system does regonize it as fastboot or recovery device but with fastboot devices or adb devices still no device in list.
It is alive again. Thanks all who helped out
renedg said:
when i have done this and go into recovery (power and left volume) i stil get usb icon and download (odin) and still no device found with adb or fastboot (driver i sbeing loaded so somehow my system does regonize it as fastboot or recovery device but with fastboot devices or adb devices still no device in list.
Click to expand...
Click to collapse
it is alive again. Thanks all who helped out
You are the man! My IO Galaxy Tab 10.1 is alive again!
Thanks!
Hi All,
I am done the ODIN step, but it still in bootloop mode. I dont know how to do with the Fastboot recover mode. I tried with my Windows 7 and it can't recognized my fastboot driver and stay in the <waiting for device>. Is there any solution for me. Thank you so much.
ericc191 said:
Here's what you do.
Download the file linked below
Download ODIN attached below
Once both are downloaded, extract PDA_SIGNED_P7105.tar
Boot your tablet into ODIN and plug it into your PC
Open the ODIN program on your PC and check the box next to PDA
Click the PDA button and navigate to the file you downloaded earlier
Press Start and let it flash
Once it is done, it will still boot loop.
You need to go into recovery (It will now be the default recovery) and wipe data/factory reset only.
Reboot and it should load up, however you will be on 3.0.1.
You can get back to 3.1 by rooting and installing recovery again or by using the update feature in the tablet's settings.
Good luck!
Click to expand...
Click to collapse
Hello, I have also followed these directions however I am having issues rebooting into recovery using adb.
When I execute adb devices no devices are found.
Any additional help would be appreciated. Thanks
UPDATE:
Success!! I was able to correct the boot loop problem by installing fastboot on a linux machine and running sudo fastboot -w. Also my tablet was in fastboot mode (Power + Volume down, then Select the usb symbol).
Instructions for installing fastboot were found here http://forum.xda-developers.com/showpost.php?p=14675422&postcount=2
boot looping SOLVED! Honeycomb 3.1 google i/o galaxy tab 10.1
[IO TAB] Boot looping? Try this to get your tab back...
I had an issue with my IO 10.1 Tab boot looping. I imagine that this would work for retail as well but have not tried it.
This process will factory reset your device.
You will need fastboot and recovery.img to boot into recovery in order to perform a factory reset.
Fastboot & Stock IO recovery comes from this post as an attachment at the bottom.
You need adb to continue (windows).
1. Extract files to where adb resides (platform-tools folder in android SDk main folder) e.g
C:\Program Files\Android\android-sdk\platform-tools .
2. Plug your tab in to a power source and then hold down the power button until it shuts down. Wait until the tab displays the charging battery.
3. Press and hold the volume down (left button in landscape) and power buttons until the usb and odin icons show up. Volume down to move left and volume up to select the usb logo. Now you should be in fastboot. Plug the usb into your computer.
4. Time to fire up adb!
Start / run / cmd , cd\,
Than, cd to your platform-tools folder or wherever your adb is at. (should be in platform-tools inside of android-sdk-windows)
5. In cmd type "adb start-server" without quotes to start adb. All comands should exclude quotes.
6. Type "fastboot devices" your device serial should appear!If not:
Edit the “<PATH TO ANDROID SDK>\extras\google\usb_driver\android_winusb.inf” file and copy/paste the following lines and add them to the [Google.NTx86] section (for 32bit Windows) and/or [Google.NTamd64] (for 64bit Windows).
NO Empty line above this set, though galaxy tab 10.1v but works for all variants!(tab detected as adb xxx device)
;Galaxy Tab 10.1v
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&REV_9999&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6601
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
;
Download the fastboot zip attached to this post (includes both Win and Linux version) and extract the files to your “<PATH TO ANDROID SDK>\platform-tools” folder
7. Now, type "fastboot boot recovery.img"
8. Now you should boot into recovery. For "adb command lines" to work boot with clockworkmod recovery img (Command and files here: http://droidbasement.com/db-blog/?p=2032)
If you want to try other stuff like push a system restore, kernel or whatever, now you can. If you fail at it, you can always repeat the steps leading up to this point to get back to recovery.
9. Time to just get the tab back! Select "wipe data/factory reset" and confirm, clear cache.
10. After that is done select "reboot device".
Credits to JASKRU from rootwiki, with some additions and modifications extracted from different sources!
for rooting the tab install the zip file from this post in recovery mode (loading recovery.img from fastboot):
http://droidbasement.com/db-blog/?p=2054
P.S don't reboot into recovery with adb command "adb reboot recovery" as it doesn't work, correct way is with fastboot command as mentioned in step 7!
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
FIRST STEP: add the attached fastboot files into the container folder of adb (in sdk folder)
This is mine:
C:\Program Files\Android\android-sdk\platform-tools
of course I did that and mine is in the same folder as yours
I get to step six and thats when it gives me the error
E:\android-sdk-windows\platform-tools>fast boot devices
'fast' is not recognized as an internal or external command,
operable program or batch file.
also when I go to the left instead of odin this is my pic (in attachment)
NOW if I hit the power button and the right on in landscape mode I do get the android system recovery options says Android System Recovery <3e> (pic attached)
I have tried wiping date clearing cache as far as fastboot goes it still doesnt let me in fastboot eventhough im not sure at this point what fastboot even is
I finally got CWM 4.0.0.4 on it but now what because somehow im on 3.0.1 on my tab it wont charge and idk what to do
These steps were tested on 3.1.can you update your firmware from kies or on device?fastboot is needed to boot into the recovery image as in your pic which you already have managed being in older firmware.
E:\android-sdk-windows\platform-tools>fast boot devices
I believe something is still wrong, did you extract the contents of zip file in the platform-tools or the complete folder?Second, how was your tab once in fastboot recongnized by windows it should be as an adb. Device and not fastboot. Third, try manually installing the driver from extras folder, google, usb in android sdk. Last is your system 64bit or 32bit as the modification in inf file should be made accordingly. The only issue is driver or fastboot exe not being in adb folder.
Adding, once in recovery as in the pic, try command adb devices and let know if your device is detected hence you can push a restore fileto your device and reboot or push original recovery.zip file and apply it from sdcard (internal memory).
Last try odin option and flash firmware as tar file mentioned in this forum, try the bootloop or blank screen threads.
tried this route but it cannot find my device via ADB - used the PDANet driver - note i did not get a driver in the extras folder
ideas?
mughalgxt said:
These steps were tested on 3.1.can you update your firmware from kies or on device?fastboot is needed to boot into the recovery image as in your pic which you already have managed being in older firmware.
E:\android-sdk-windows\platform-tools>fast boot devices
I believe something is still wrong, did you extract the contents of zip file in the platform-tools or the complete folder?Second, how was your tab once in fastboot recongnized by windows it should be as an adb. Device and not fastboot. Third, try manually installing the driver from extras folder, google, usb in android sdk. Last is your system 64bit or 32bit as the modification in inf file should be made accordingly. The only issue is driver or fastboot exe not being in adb folder.
Adding, once in recovery as in the pic, try command adb devices and let know if your device is detected hence you can push a restore fileto your device and reboot or push original recovery.zip file and apply it from sdcard (internal memory).
Last try odin option and flash firmware as tar file mentioned in this forum, try the bootloop or blank screen threads.
Click to expand...
Click to collapse
solved my problem -
first fastboot.exe is located in the android-sdk\tools directory. i copied it to my android-sdk\platform-tools directory
Then i get into the tablet's fastboot mode (holding down power + volume down, then select the USB icon) i plug in the cable to my PC's USB, then go to device manager and you should see a fastboot device with an exclamation mark. right click on this and select update driver then navigate to android-sdk\extras\google\usb_driver directory and select android_winusb.inf - it should now install the driver
open up a cmd window and follow the instructions highlighted above starting at step 7
animatechnica said:
solved my problem -
first fastboot.exe is located in the android-sdk\tools directory. i copied it to my android-sdk\platform-tools directory
Then i get into the tablet's fastboot mode (holding down power + volume down, then select the USB icon) i plug in the cable to my PC's USB, then go to device manager and you should see a fastboot device with an exclamation mark. right click on this and select update driver then navigate to android-sdk\extras\google\usb_driver directory and select android_winusb.inf - it should now install the driver
open up a cmd window and follow the instructions highlighted above starting at step 7
Click to expand...
Click to collapse
IN Short, follow the steps in my previous post from 1st till end! Flashing the bootloader file from my thread in development section, is easiest way. Replacing fastboot with recovery option in bootscreen solves many issues for non-developers!
yes and i should add your method was very effective ! thanks
what threw me off initially was not finding the fastboot.exe which was in a different folder and the usbdriver - which needed to be installed separately and can be found by launching SDK manager, selecting Available packages-Third-party Add ons-Google Inc - Google USB Driver Package revision 4
mughalgxt said:
IN Short, follow the steps in my previous post from 1st till end! Flashing the bootloader file from my thread in development section, is easiest way. Replacing fastboot with recovery option in bootscreen solves many issues for non-developers!
Click to expand...
Click to collapse
Thanks!!!
This totally worked!
vokhoa408 said:
Thanks!!!
This totally worked!
Click to expand...
Click to collapse
Is this thing getting Ice cream sandwich?
that might solve all these problems.
Samsung Galaxy Tab 10.1 boot loop
Edit: *Fixed!* Ok, so here is my advice to all you other noobs who bricked your tablet, be AWARE that your tablet actually is conscious, it chooses when it wants to work. Just do everything it says on here, all the fixes I have listed, reboot a bunch of times, yell at it, and when you cry a true tear of pain and remorse, and it splashes down on the surface, it will recognize this and all of a sudden work. Booted to 3.0.1 and going to update, that all that is holy.
Hi Guys, I am having the same problem and need some expert advice please, I have a Samsung Galaxy Tab 10.1 with Android Honeycomb 3.1, running Windows XP Pro SP3
I've gone over every solution to this problem on xda over two days and none have worked for me, either that or i'm not doing it correctly.
I successfully rooted my Tab a few days ago, then tried to install a 'boosted' theme and everything is messed up now. When I boot it just hangs on the samsung loading screen, and it reboots to the same screen.
I have tried wiping data/factory reset in cwm
I have tried wiping cache partition
I have tried running Odin through downloading mode
I have adb and fastboot installed on my computer
I have Samsung Android adb interface driver in Device Manager
I have PDAnet installed
When I boot holding the volume down and power button to get the two options, the only two options I have are the Odin Downloading green guy on the right, and an icon with a box and an arrow coming out of it that takes me to CWM on the left.
So I cannot choose fastboot mode on the Tab, when I try to run 'fastboot flash system new.img' through cmd.exe it just says < waiting for device >
I"m a total noob to this and should have left well enough alone when I successfully rooted it, i'm sure I must be just missing a small step, if I could get a bit of guidance it would be greatly appreciated, thanks.
In the end I found it fairly easy to root my samsung epic 4g galaxy sph-d700 but the documentation was a bit tricky (because some of it was based on odin rather than heimdall, it wasn't always clear where to get ROM's, how ClockWorkMod Recovery (CWM) fits into the picture, etc.). I hope that this post will be useful.
(1) Install heimdall on the computer running ubuntu (heimdall is a program that will flash ROM's to the phone)
apt-get install heimdall-flash
(2) Download to the computer the latest CWM and an appropriate, i.e., pre-rooted, ROM from an archive such as that of kennyglass123. BML ROM's may be easier for beginners than are MTD ROM's. The ROM should be matched to the phone, which means both the hardware and the system it is replacing. I used
cwm-5.0.2.7-epic4g.tar (ClockWorkMod Recovery; extract its contents)
Deodexed-FC09-BML.zip (a ROM and system for the android phone; leave the file zipped)
(But ThePeoplesROMv2.22_BML.zip has also been recommended and there are others in circulation).
(3) Connect the android phone to the computer via USB cable; the phone should show up on the desktop as a removable disk. Transfer the ROM file (Deodexed-FC09-BML.zip) from the computer to the sd card of the phone (just as you would transfer any file, e.g., an mp3, by drag and drop or by copying from the command line from/to the appropriate directory).
(4) On the computer extract recovery.bin from the CWM tarfile
tar xvf cwm-5.0.2.7-epic4g.tar
(I renamed recovery.bin to cwm5_recovery.bin to remind myself what it is.)
(5) Disconnect and turn off the phone and restart the phone in Download mode by turning off the phone and turning it on while holding down the number "1" on the physical keyboard. "Download" mode starts (black screen with yellow triangle with worker digging).
(6) Connect the phone to the computer by USB cable. From the computer use heimdall to flash the CWM file to the phone as a recovery file. Flashing is not the same as file transfer: phone must be in Download mode and the heimdall program must be used to flash the file onto the phone's ROM. The command is:
heimdall flash --recovery cwm5_recovery.bin
(7) Disconnect the phone and restart phone with on/off, camera, and volume-down buttons ("three-fingered salute"). Hold all three buttons until the lighted buttons at the bottom of the phone turn on. Phone will start in "Recovery" mode with a menu of 7-10 items.
(8) Navigate the Recovery menu with the volume up/down keys and select items with the camera button. Select item "Install zip from sdcard". Navigate file menu to choose Deodexed-FC09-BML.zip (or another zipped ROM file you have selected). ROM will install.
(9) When the Recovery mode menu returns, select "Reboot phone" and the phone should boot (slowly the first time) to the new ROM and be rooted. There will be a new "Superuser" app on the phone and you should be able to install apps from the Play Store that require root privileges.
qbking77 has some excellent YouTube videos that walk through the process.
root samsung epic 4g galaxy sph-d700 on ubuntu 13.04
I left out "on ubuntu 13.04" in the title of the post.
michaelaoash said:
In the end I found it fairly easy to root my samsung epic 4g galaxy sph-d700 but the documentation was a bit tricky (because some of it was based on odin rather than heimdall, it wasn't always clear where to get ROM's, how ClockWorkMod Recovery (CWM) fits into the picture, etc.). I hope that this post will be useful.
(1) Install heimdall on the computer running ubuntu (heimdall is a program that will flash ROM's to the phone)
apt-get install heimdall-flash
(2) Download to the computer the latest CWM and an appropriate, i.e., pre-rooted, ROM from an archive such as that of kennyglass123. BML ROM's may be easier for beginners than are MTD ROM's. The ROM should be matched to the phone, which means both the hardware and the system it is replacing. I used
cwm-5.0.2.7-epic4g.tar (ClockWorkMod Recovery; extract its contents)
Deodexed-FC09-BML.zip (a ROM and system for the android phone; leave the file zipped)
(But ThePeoplesROMv2.22_BML.zip has also been recommended and there are others in circulation).
(3) Connect the android phone to the computer via USB cable; the phone should show up on the desktop as a removable disk. Transfer the ROM file (Deodexed-FC09-BML.zip) from the computer to the sd card of the phone (just as you would transfer any file, e.g., an mp3, by drag and drop or by copying from the command line from/to the appropriate directory).
(4) On the computer extract recovery.bin from the CWM tarfile
tar xvf cwm-5.0.2.7-epic4g.tar
(I renamed recovery.bin to cwm5_recovery.bin to remind myself what it is.)
(5) Disconnect and turn off the phone and restart the phone in Download mode by turning off the phone and turning it on while holding down the number "1" on the physical keyboard. "Download" mode starts (black screen with yellow triangle with worker digging).
(6) Connect the phone to the computer by USB cable. From the computer use heimdall to flash the CWM file to the phone as a recovery file. Flashing is not the same as file transfer: phone must be in Download mode and the heimdall program must be used to flash the file onto the phone's ROM. The command is:
heimdall flash --recovery cwm5_recovery.bin
(7) Disconnect the phone and restart phone with on/off, camera, and volume-down buttons ("three-fingered salute"). Hold all three buttons until the lighted buttons at the bottom of the phone turn on. Phone will start in "Recovery" mode with a menu of 7-10 items.
(8) Navigate the Recovery menu with the volume up/down keys and select items with the camera button. Select item "Install zip from sdcard". Navigate file menu to choose Deodexed-FC09-BML.zip (or another zipped ROM file you have selected). ROM will install.
(9) When the Recovery mode menu returns, select "Reboot phone" and the phone should boot (slowly the first time) to the new ROM and be rooted. There will be a new "Superuser" app on the phone and you should be able to install apps from the Play Store that require root privileges.
qbking77 has some excellent YouTube videos that walk through the process.
Click to expand...
Click to collapse
michaelaoash said:
I left out "on ubuntu 13.04" in the title of the post.
Click to expand...
Click to collapse
Append --no-reboot to the heimdall command otherwise you cannot finish the steps because the phone reboots and you lose cwm.
TABLET: Fusion5 Premium+ (Re-branded yuandao N90 II dual core RK3066)
ISSUE: The tablet is now stuck in recovery mode (red triangle black exclamation) Stock 3e recovery after a failed firmware upgrade which I think was due to me selecting 'upgrade' and not 'restore'.
Details:
Before this failure rkbatch tool could see my device.
I have now tried rkbatch tool on 4 different PC's with different OS'es (Win8 x64, Win7 x32, Win XP x32, Linux x32) and at least 5 different USB cables using the latest driver_assist and batch tools or Linux equivalents.
Can not get rktools to see device in flash mode on any of them.
All the PC's can see it in ADB though.
“adb devices” reports device in recovery mode.
There's no fastboot and no shell which reports *“exec*'/system/bin/sh' failed:*No*such file or directory” but sideload appears to work.
“adb ls” of /sys /system /data etc show they are all empty.
I have the found the following firmwares specifically for this device
:LINK withdrawn
:LINK withdrawn
PM for the links
Unfortunately both of these updates are *.img files which as I can't connect using rkbatch
tool, I can't flash.
I have tried zipping them and flashing from sideload or from SDCARD both both fail, from sdcard the error is “no update found”. In sideload mode it reports “installation aborted” after the verifying the update stage. I'm quite sure there is more to creating a working update.zip but unsure of the details.
My question is does anybody no of a way to convert these supplied .img files into a format, probably update.zip, that I can either install via sideload OR from sdcard?
Thanks
Acer Predator 8 GT-810 system\etc backup please!
Make a backup folder etc
Do you still need it? I can send it you tomorrow or something like that.
p8tgames said:
Do you still need it? I can send it you tomorrow or something like that.
Click to expand...
Click to collapse
hey man if u able to send me a back up. Will that solve my problem ?
I made mistake to wipe everything in my phone and now i dont have OS ( i cant start my phone) i can only enter TWRP and thats all. i can use pc to transfer files to my phone and then install the files from there , so i wonder if any1 send me back up will that save me ???
i cand find anywhere OS for acer predator gt 810
there is official avolo zip on acers' page. flash that zip and you're safe
Flash archive corrupted
Hi, I downloaded this archive and I want to flash my tablet, but Intel Phone Flash Tool Lite(flasher for x86 devices) say, that archive corrupted. I downloaded firmware 3 time, but its not working.I used TWRP to install firmware, it installed, but i have BootLoop.Please, someone, do Backup of firmware.
dvijetrecine said:
there is official avolo zip on acers' page. flash that zip and you're safe
Click to expand...
Click to collapse
Hi, I downloaded this archive and I want to flash my tablet, but Intel Phone Flash Tool Lite(flasher for x86 devices) say, that archive corrupted. I downloaded firmware 3 time, but its not working.I used TWRP to install firmware, it installed, but i have BootLoop.Please, someone, do Backup of firmware
Alex_merser54 said:
Hi, I downloaded this archive and I want to flash my tablet, but Intel Phone Flash Tool Lite(flasher for x86 devices) say, that archive corrupted. I downloaded firmware 3 time, but its not working.I used TWRP to install firmware, it installed, but i have BootLoop.Please, someone, do Backup of firmware
Click to expand...
Click to collapse
Use fastboot to flash the stock ROM instead of Intel flash tool. (If you know what you're doing, just read the part in blue below.)
fastboot is for Android devices, whether they have Qualcomm or Intel processors. Using Intel Flash tool is more akin to using Qualcomm's QPST for flashing, which is also something that should only be attempted
after trying fastboot. The Intel flash tool expects the .zip file to be in a format such as a Chuwi ROM with Windows is. Intel Flash tool unfortunately doesn't expect the .zip to be in the Android format like Acer's stock
ROM "AV0L0-something.zip" is.
With the tablet off, and plugged into your computer, hold both volume buttons and power it on. (You probably already knew this step, but here just in case )
It will vibrate longer than it usually does when turning on.
The screen should indicate that the device is in download, or "dnx" mode.
Open a command prompt in administrator mode,(the title of the window should say "Administrator: Windows Command Prompt" or "Administrator: <current directory>")
Type:
Code:
fastboot
If command not found, then either copy fastboot.exe into System32, or add the path it is in to your PATH variable, or simply navigate to its directory within the command prompt.
If you're not familiar with the PATH variable, you can just shift+right-click on fastboot.exe, click "Copy Path" and then paste it into the command prompt to use it's full path in place of simply "fastboot".
Once you're able to type "fastboot" or paste the full path and press enter and it returns the fastboot help message, type:
Code:
fastboot devices
this will either return a single line containing your device's serial number, or it will return nothing at all
If you see a serial number, you're in business.
(make sure the tablet is not low on battery before you continue):
Type:
fastboot update <path to ROM .zip>
Click to expand...
Click to collapse
This should initiate a full reflashing of the stock ROM. The tablet will reboot a couple times, you should hear/feel an even longer vibration during the process, do not touch it or unplug it from the computer until it is at the initial Google device setup screen waiting for your input.
Note that this full reflashing will also overwrite TWRP with the stock recovery.
if "fastboot devices" returns nothing at all, and also doesn't say "command not found" then do the following:
open device manager on computer, find the tablet's driver (may be under portable devices, or COM ports. sometimes under USB.)
if you can't find it, look for an "unknown device" with a yellow exclamation mark on it. If you see that, then you may not have had the driver installed in the first place. To verify, unplug the tablet from the computer
and see if the unknown device disappears from device manager.
If you were able to find the tablet in device manager, then right click and "Uninstall Device" and be sure to check the box to uninstall the driver software as well before clicking OK.
Then, unplug the tablet from your computer if you haven't already.
Download the latest driver from the same place on Acer's website that you downloaded the stock ROM from. Install the driver and restart your computer if it says it needs to.
Afterward, ensure the tablet is off and try the steps above again.
biorpg said:
Use fastboot to flash the stock ROM instead of Intel flash tool. (If you know what you're doing, just read the part in blue below.)
fastboot is for Android devices, whether they have Qualcomm or Intel processors. Using Intel Flash tool is more akin to using Qualcomm's QPST for flashing, which is also something that should only be attempted
after trying fastboot. The Intel flash tool expects the .zip file to be in a format such as a Chuwi ROM with Windows is. Intel Flash tool unfortunately doesn't expect the .zip to be in the Android format like Acer's stock
ROM "AV0L0-something.zip" is.
With the tablet off, and plugged into your computer, hold both volume buttons and power it on. (You probably already knew this step, but here just in case )
It will vibrate longer than it usually does when turning on.
The screen should indicate that the device is in download, or "dnx" mode.
Open a command prompt in administrator mode,(the title of the window should say "Administrator: Windows Command Prompt" or "Administrator: <current directory>")
Type:
If command not found, then either copy fastboot.exe into System32, or add the path it is in to your PATH variable, or simply navigate to its directory within the command prompt.
If you're not familiar with the PATH variable, you can just shift+right-click on fastboot.exe, click "Copy Path" and then paste it into the command prompt to use it's full path in place of simply "fastboot".
Once you're able to type "fastboot" or paste the full path and press enter and it returns the fastboot help message, type:
this will either return a single line containing your device's serial number, or it will return nothing at all
If you see a serial number, you're in business.
(make sure the tablet is not low on battery before you continue):
Type:
This should initiate a full reflashing of the stock ROM. The tablet will reboot a couple times, you should hear/feel an even longer vibration during the process, do not touch it or unplug it from the computer until it is at the initial Google device setup screen waiting for your input.
Note that this full reflashing will also overwrite TWRP with the stock recovery.
if "fastboot devices" returns nothing at all, and also doesn't say "command not found" then do the following:
open device manager on computer, find the tablet's driver (may be under portable devices, or COM ports. sometimes under USB.)
if you can't find it, look for an "unknown device" with a yellow exclamation mark on it. If you see that, then you may not have had the driver installed in the first place. To verify, unplug the tablet from the computer
and see if the unknown device disappears from device manager.
If you were able to find the tablet in device manager, then right click and "Uninstall Device" and be sure to check the box to uninstall the driver software as well before clicking OK.
Then, unplug the tablet from your computer if you haven't already.
Download the latest driver from the same place on Acer's website that you downloaded the stock ROM from. Install the driver and restart your computer if it says it needs to.
Afterward, ensure the tablet is off and try the steps above again.
Click to expand...
Click to collapse
Thank you, but I just entered EFI and load android.efi file, also I autorun it and reflash via recovery
Hi,
I have encountered a suddenly dead old device. It was working long time without an issue, but one day it does not start and just a logo is displayed. It was possible to turn off the device or enter the recovery menu. I have found more posts about repairing with some unofficial flash tools or using unofficial ROMs.
I was able to revive the device finally with success and using official tools only, so I would like to share the steps I have used, basically it is about downloading the official ROM from Acer site and flashing it with ADB:
1. You will need Windows computer, I was not able to make the Mac recognise the phone properly, but maybe it is somehow possible.
2. Download official Android 4.4.2 ROM from ACER site: https://www.acer.com/ac/en/GB/content/drivers
enter SNID (check the phone under cover), look in OS category and download, the ZIP file is ~700MB large, do not unzip.
Download also the Drivers and extract it.
No need to download unofficial ROMs or drivers for this phone I think.
3. Download android platform tools from https://developer.android.com/studio/releases/platform-tools and unpack to some directory
4. Install phone Drivers manually from Device manager, use Action/Add device command and navigate to INF in the driver folder.
5. Turn on the phone and star recovery mode (Vol down+Power).
6. Connect the charged device with USB cable.
7. Start cmd.exe and navigate to platform-tools directory, start "adb devices" command, your device should be listed.
If no device is listed, return to driver installation step.
8. start "adb reboot bootloader", phone will reboot, hint about flashing the ROM appears
9. start "adb sideload yourpathto/officialROM.zip
10. wait few minutes until the installation is finished, phone reboots and should work.
11. you are happy
Hey,
2 Years ago my E700 dropped down, since then it does not work anymore. It shows no reaction if i want to start the device.
Could something be broken?
Do you have an idea to fix it?