Somehow I ****ed up my Oneplus One pretty badly.
I can't load in fastboot at all (either with pushing the vol+ key & power key nor with adb reboot-fastboot)
I already flashed the oneplus one recovery tool image and even tried the colouros image.
Nothing worked and I even can't adb push any file on my sdcard nor can I sideload any file to it (error can't find media)
every restart bring me directly to the recovery. (earlier i still had twrp running and tried wiping and flashing zips. even the stockroms didn't work. there was nothing else on the internal space but the gapps/rom zip files)
Isn't there a way I can force a complete image on my phone like I could on my Samsung with odin?
Did i accidently delete my boot partition?
How can I install the fastboot mode?
I will pay via paypal.
Related
I tried to root my me302kl by following the first post described in this thread, but it seems I've bricked my tablet
http://forum.xda-developers.com/showthread.php?t=2601837
I have the LTE version, unlocked the bootloader using the apk from Asus, and followed the fastboot method in the first post, and now I'm stuck at the Asus logo on startup. I'm trying to factory reset by using the update download from the Asus website, but when i try
fastboot erase cache
fastboot erase system
fastboot flash update US_ME302C-V4.7.3-0-ota-user.zip
it fails with this:
writing 'update'...
FAILED (remote: partition table doesn't exist)
Then I tried following perpe's advice but both methods did not work
Download the update zip for your device and sku from ASUS. Unpack it once, there should be a second zip, try to flash it with
fastboot update name-of-your.zip
if this doesn't wotk, then copy the update zip to an external sd card. Your sd card should be formated in far32. Place the card into the tablets sd card. Press Volume UP + Power to boot it into the bootloader, it should flash it automatically, if not look if yor bootloader has a menu entry "sd download..." select it with the volume keys and power.
Click to expand...
Click to collapse
When booting into recovery mode, I get the dead android robot icon, regardless of whether the .zip file is on the SD card or not. I've also tried making a system.img file out of the system folder from the extracted zip file and flashing that with fastboot flash system system.img and fastboot flash boot boot.img, but that didn't work either.
Any kind soul have advice on how to make use of the official Asus OTA .zip file, or perhaps be able to supply some .img backups for me to make use of?
EDIT
Found out that to get the recovery menu to show up, you have to hold the power button and press volume up. I thought that the menu would show up automatically so I got confused. ADB sideloaded the Asus OTA .zip and everything is back to normal
Hello
How to flash oryginal soft on this tablet. Can you help with this ?
I tried SDK and wiped all system but now i cannot flash the system. How should i do it ?
I have firmware fros ASUS page and now what?
I tried fastboot flash update... but i have measege that unknown partition and cannot determinate image file name. What im doing wrong?
Thanks!
Lenino83 said:
Hello
How to flash oryginal soft on this tablet. Can you help with this ?
I tried SDK and wiped all system but now i cannot flash the system. How should i do it ?
I have firmware fros ASUS page and now what?
I tried fastboot flash update... but i have measege that unknown partition and cannot determinate image file name. What im doing wrong?
Thanks!
Click to expand...
Click to collapse
download the OTA zip from the asus website
unzip once, you should have another zip
power on the tablet while holding volume up to boot into recovery mode
after the android robot shows up, hold volume up and press the power button to get the recovery menu to show
install the zip using adb sideload
using adb sideload will differ depending on what OS you're using. you can google to find out more specific instructions for that because it's a little more work to get it for windows. for OSX if you have homebrew, you can just 'brew install android' and it will install all the android tools for you.
once you have adb installed, in the terminal type 'adb sideload pathname_of_zip.zip' and it will restore your device to factory settings
I had the same problem and your trick saved me from sending it back. I am not sure if i would have send it back as I have yet to brick something since I am playing with android back in the days of Viewsonic gtablet. We are stuck with 4.2.
Sent from my T0LTE using Tapatalk
help
tkuichooseyou said:
Found out that to get the recovery menu to show up, you have to hold the power button and press volume up. I thought that the menu would show up automatically so I got confused. ADB sideloaded the Asus OTA .zip and everything is back to normal
Click to expand...
Click to collapse
hello
got like the same problem.. dead robot, no boot, in recovery does not want to update from ota file.
Can u explain please how to ADB sideload ota.zip?
What I need, drivers and step by step?
I tried but I get no device in adb
Thank you:crying:
ionratiu2000 said:
hello
got like the same problem.. dead robot, no boot, in recovery does not want to update from ota file.
Can u explain please how to ADB sideload ota.zip?
What I need, drivers and step by step?
I tried but I get no device in adb
Thank you:crying:
Click to expand...
Click to collapse
You have to download adb or android sdk, or google how to install adb. Once you have installed the adb, hold the power button, and either Volume UP or down to put tablet into bootlfash recovery mode. Once you have it in recovery mode, push volume up or down to get into true recovery mode.
There you would see adb sideload.
Download US or WWW files from Asus website, and unzip the file into ADB directory or whatever path. then type adb sideload name of the file.
Please read the 1st post by OP on this thread twice or three times, and it tells you how to get your tablet back from brink.
back
rob_z11 said:
You have to download adb or android sdk, or google how to install adb. Once you have installed the adb, hold the power button, and either Volume UP or down to put tablet into bootlfash recovery mode. Once you have it in recovery mode, push volume up or down to get into true recovery mode.
There you would see adb sideload.
Download US or WWW files from Asus website, and unzip the file into ADB directory or whatever path. then type adb sideload name of the file.
Please read the 1st post by OP on this thread twice or three times, and it tells you how to get your tablet back from brink.
Click to expand...
Click to collapse
Got it. Done! the tablet is running again, but I encounter another issue
I have no permission to write internal sd.
I cant touch internal, some apps that require writing don't work (play store, camera, etc) I cant root, unlock or do anything that require w permissions.
Any way to fix that?
Or I have to wait for a CWM and rom image ?
ionratiu2000 said:
Got it. Done! the tablet is running again, but I encounter another issue
I have no permission to write internal sd.
I cant touch internal, some apps that require writing don't work (play store, camera, etc) I cant root, unlock or do anything that require w permissions.
Any way to fix that?
Or I have to wait for a CWM and rom image ?
Click to expand...
Click to collapse
You can download king's root or something which is a window app, and it does give your tablet root. I am not exactly sure about the name, but would let you know once I have access to my laptop.
Sent from my T0LTE using Tapatalk
ASUS MEMO PAD FHD10 ME302KL frozen logo screen
I have problem with my asus memo pad 10. It just shows asus logo startup screen and nothing more and it have no reaction with anything I do.
Please help!
I can't boot into recovery mode, but there is no problem to boot into fastboot mode!
Could anyone provide stock recovery file or link? Then I can flash recovery and do the adb sideload.
Thanks!!
Hey, I have an Archos Helium 45 that I put a custom ROM on a while ago, but today decided to revert to the stock ROM because it was having some issues. I must have done something wrong though, and softbricked my phone. Now this would be no problem if only I could enter recovery mode, however when I boot up my phone holding down the +volume and power button, all I get is a green screen, which is the fastboot mode. On this screen there is nothing I can select (just seems to be some tiny tiny white, unreadable text on the top). I'm guessing this is because I installed TWRP over the regular recovery.
When I first installed the custom ROM, I did something wrong and softbricked my phone too, and had the same problem of not being able to select anything on the green screen, but then I was able to use the command 'adb reboot recovery' via the PC to boot into recovery mode. However, now this does not work anymore, and when using 'adb devices', it returns an empty list. I still do get a code when using 'fastboot devices' though.
Does anyone have any solution to boot into recovery mode from the fastboot mode?
I read somewhere that I could try flashing the img files from the original ROM via fastboot one by one, however the only img file in ROM's zip file is boot.img.
I also tried updating the ROM using 'fastboot update update.zip' but then it says
Code:
archive does not contain 'android-info.txt'
error: update package 'update.zip' has no android-info.txt
Edit: Never mind, right after creating this thread I found out I could enter recovery mode simply by continuing to hold the +volume button and releasing the power button after the green screen... (and I also plugged it into my computer right when TWRP started, don't know if this was a requirement or coincidence) **** I spent all day looking for a fix and ended up finding it just by trying something.
I'm having issues with the stock ROM though, but at least I can install an other custom ROM and have a working phone.
I flashed TWRP to the device successfully, and proceeded to try to install Magisk 19.3 zip. It would begin to do a recovery bootloop. I fixed it using TWRP, and tried using the patched boot img from magisk manager instead. This is where things go wrong. After flashing boot.img, the phone refuses to boot, and asks me to do a factory reset. I did this twice, and the phone continued not to boot. I then tried installing the latest android Q factory image. The flash failed, and the phone stopped showing up when I do fastboot devices or adb devices. It is stuck in the bootloader telling me slot b is not bootable. I have tried different ports, but adb and fastboot are no longer responding.
Take out the battery for 10 sec or more replace, see if you can get back into recovery. Recovery should be TWRP.
You may need to uninstall and reinstall the driver on your computer. IF it is a Win computer should show up in device manager at the top under Android.
https://www.xda-developers.com/how-to-install-custom-rom-android/
or you can do a factory reset which is also a button.
I fixed it by holding down the power and vol up buttons, which allowed me to use fastboot again and fixed everything. Thanks for the help tho>
First of all, thanks for the great guides published here and all the work that went into them. They help resolve a lot of issues.
Unfortunately I encountered an issue today on my KIW-L21 that I can't find a solution for in the published guides. Today a stock update (installed via TWRP) got stuck on first boot and somehow managed to break the DLOAD recovery option (accessed by pressing Vol Up+Down when powering up the phone). Whenever I try to enter the DLOAD recovery mode now, the phone is not flashing the UPDATE.APP from the dload folder on the SD card anymore, but is showing an update screen (looks like a usb plug in a circle). This process stays on 5% for a while and then just reboots the phone into the regular system. So no option to recover from the UPDATE.APP anymore. Otherwise the phone still seems to be working fine.
Here's what I did to run into the problem:
- Successfully flash 5.1_EMUI 3.1_C432B140 firmware found in the Honor 5X repository on XDA via DLOAD recovery
- Flash TWRP (twrp-3.3.1-0-kiwi) via fastboot
- Download update to 6.0.1_EMUI 4.0_C432B350CUSTC432D003 via the regular update option
- After download the phone automatically booted into TWRP to install the update
- Reboot after TWRP flashed the update got stuck on boot and the DLOAD recovery got replaced by that update feature
Since then I booted into TWRP recovery again and installed AOSiP 9.0 + Magisk after wiping data/system/cache. This worked fine and AOSiP is booting and working correctly. The only issue now is that the DLOAD recovery did not get restored that way. That behavior stayed the same.
I tried eRecovery (reports an error after connecting to the wifi network, but this did not work before either) and stock recovery (extracted from B140 firmware and flashed via fastboot) without success. Both stock recovery options failed with an error message but did not provide any details regarding the issue.
Is the lost DLOAD recovery a known issue? Not sure if a partial update is stuck somewhere and needs to be deleted or if the DLOAD recovery function can be flashed via fastboot to fix this.
*** UPDATE 1
Here's some additional things I tried to fix the issue and that I noticed during those attempts:
- Recovery via HiSuite unfortunately does not seem to work. When booted into the bootloader HiSuite does not recognize the device. When booted into AOSiP, the phone is recognized, but the HiSuite app installed on the phone fails to work due to missing location authorizations. It doesn't ask for them though, just displays an error pop-up that leads to settings where I don't have the option to enable location access for the app. When manually checking the location permission for apps HiSuite is not among those that I can enable/disable this for.
- TWRP recovery can't be accessed from the phone despite flashing it via "fastboot flash recovery twrp.img". When launching recovery on the phone I end up in EMUI stock recovery. I can access and use TWRP via "fastboot boot twrp.img" though.
- I tried using the DLOAD update with the dload folder copied to the internal storage (local SD card). This did not change the phone getting stuck at a 5% update instead of the EMUI firmware flash.
- The local dload folder however seemed to have an impact on the stock recovery. While the stock recovery failed with an error before, it now gets the stuck at 99% done and a reboot just restarts the stock factory reset. I did find a way to exit this loop without waiting for the battery to drain (reboot with both volume buttons pressed into the update mode I don't want, reboot regularly once it stops on 5%) that got me back into a running/reset AOSiP.
- I can't boot into EDL mode via ADB (adb reboot edl). I was hoping HiSuite might help in that mode, but the command just rebooted the phone into AOSiP.
- The 5% update issue does not get resolved by disconnecting the phone from a cable during the operation. I read on XDA that this solved the issue for other HUAWEI devices, did unfortunately not work for mine.
- I noticed the bootloader does not show the FRP info anymore on the screen of the phone. It just shows "PHONE Unlocked". Not sure if that is important or just changed to this after unlocking the bootloader a few days ago.
The fact the flashing the recovery partition with TWRP does not seem to work properly suggests a partitioning issue to me. Is there a way to repartition the device and manually flash the relevant partitions via fastboot or some other tool?
If anyone knows how to fix the issue, a pointer in the right direction would be appreciated.
[SOLVED]
I finally managed to fix the issue by reverting to stock in several steps.
Tools required:
- Stock Firmware (I used the C432B140 I downloaded from the XDA Honor 5X repository)
- ADB/Fastboot toolset
- Huawei Update Extractor
- Stock firmware UPDATE.APP in dload folder on SD card installed in phone
1. I extracted BOOT.IMG, RECOVERY.IMG and SYSTEM.IMG from the full stock firmware
2. I rebooted the phone into bootloader (using command "adb reboot bootloader")
3. I flashed the stock recovery image (using command "fastboot flash recovery RECOVERY.IMG)
4. I flashed the stock system image (using command "fastboot flash system SYSTEM.IMG)
5. I flashed the stock boot image (using command "fastboot flash boot BOOT.IMG")
6. I rebooted the phone (using command "fastboot reboot"), this rebooted the phone in a stock B140 / B350 hybrid stock EMUI
7. I entered the ProjectMenu by entering *#*#2846579#*#* on in the phone app and chose "4. Software Upgrade" > "1. SDCard Upgrade" and confirmed that I want to perform the update.
8. The phone finally rebooted into the regular EMUI dload updater and reflashed stock firmware C432B140 to my phone
Afterwards the recovery from dload could also be started via Vol Up+Down when powering up the phone.
Hope this helps someone else fix the issue in case anyone encounters this.
I am facing a very similar issue on a KIW-L21 (running a custom ROM though).
Can anyone guide me to whether the steps presented can be modified to work coming from a custom ROM?
There are a number of generic installation guides for custom roms eg https://www.xda-developers.com/how-to-install-custom-rom-android/
However this one is specifically for the LG G6 and tested using the US997 model. It worked for me, but I welcome comments on how to improve it.
Create a folder on the PC for all the downloads and files
Download phone driver from LG website
https://www.lg.com/us/support/help-library/lg-mobile-drivers-and-software-CT10000027-20150179827560
Download ADB/Fastboot https://developer.android.com/studio/releases/platform-tools (You need to unzip once downloaded)
(I had an error "adb server version (31) doesn't match this client (41) killing". I searched my PC and found an older version which I had used for another phone and deleted the folders and reinstalled from the download)
Ensure the phone is backing up. (Google backup is working, you have all your photos music etc downloaded) the next steps will wipe the phone
Remove the PIN/Password/Fingerprints from the phone so it will boot without any security.
Unlock the bootloader
https://developer.lge.com/resource/mobile/RetrieveBootloader.dev
The phone will then reboot and do a complete wipe so you need to wait a while for Android to setup.
Telegraph has the latest news on LG G6 ROMs and Recovery. From here I got the links for SHRP recovery which seems more up to date for LG G6 than TWRP. (https://web.telegram.org/#/[email protected])
https://sourceforge.net/projects/pa-g6/files/Releases/SHRP/20.07.2020/US997/
I named the downloaded file "recovery" (You need the .img file not the ZIP)
There are lots of active ROMS for LG G6 I have Lineage installed on another phone which works really well, but Havoc seems the most popular on the G6.
Download the ROM and Gapps https://opengapps.org/ (I used Nano, remember G6 is 64bit)
You will also need to update the bootloader. This was the latest I found for the US997
https://androidfilehost.com/?fid=1899786940962575226
(I missed the bootloader the first time and Gapps will not flash, I was helped by the LG G6 community on Telegram https://web.telegram.org/#/[email protected])
Now you have downloaded all you need
Then connect the phone to the PC and ensured you have ADB debug on in developer options and boot the phone into fastboot
On the PC open a command prompt in the folder you have all the files:
adb reboot bootloader
To load the recovery to the phone :
Fastboot flash recovery recovery.img
YOU MUST NOW BOOT DIRECTLY TO RECOVERY. Do not reboot to Android as this will automatically reset recovery to the stock version.
Unplug the USB cable and reboot to recovery (hold volume down + power button).. continue holding until phone reboots...
As soon as you see the LG logo on the screen.. let go of the power button then quickly press it again (never letting go of volume down).
Keep holding until you see the Factory Reset screen. Click thru the factory reset screens using the volume buttons to move up/down and power button to select. Choose "Yes" twice (saying you want to reset the phone it should boot into your new recovery. Despite what the screen says it won't actually factory reset/wipe your data... as long as you've installed a custom recovery and have not booted into Android since then.
Most likely you will be asked the password to decrypt the data folder. I tried my phone PIN and other default passwords suggested on the internet. I eventually found that this is a known issue and you need for cancel out of this screen and go and "FORMAT DATA"
Reboot directly to recovery (select reboot recovery in Skyhawk), this time you should not be asked for the decryption password.
I recommend you backup your current setup before making changes. If you hit issues you can use the recovery to restore. My SD card slot is broken (Poor LG design) so I plugged a USB thumb drive into the USB C slot and did a full backup. (No data since I just formatted it).
Wipe the partitions before you flash
Full wipe ("The only option you ever need")
Select Advanced and wipe system partition.
FLASH (You need to put the ZIP files either on the USB drive as I did, or copy to your SD card, or you can use ADB sideloader from the PC to push the files to the phone). The USB drive seems the easiest since you can plug it into your PC to load the files then plug it into the phone to read them.
Flash in the following order
Bootloader
ROM
Gapps
After Installing wipe cache and Davik
Reboot
It will do lots of processing while setting up. Ensure it stays cool (remove case and leave it plugged in with the screen off)
Donate to the developer of your new ROM at the end when it works.
I have been running my LG G6 on Android 10 for a few weeks and thought I would share my observations, I am using Havoc 3.7 installed with Skyhawk, I did not root the phone.
Likes : Very smooth experience, phone feel like it is running much faster. Very stable, I had one surprise reboot in the time I have used it. No issues (so far) with installing or using any apps including banking. Much lower use of storage, I have 6GB free.
Same : Battery life is about the same as before.
Gaps : Cannot encrypt, VOLTE doesn't work (which may become a big issue for T-Mobile and AT&T soon), when being used the phone gets much warmer than it did before and the wifi setting randomly turns off.
Next Steps: I am going to try Lineage which has released some fixes for the WIFI issue and report back.
I'm trying to follow the instructions as per this guide for the tmo version of G6 (H87220g) and I'm running into a roadblock on the recovery flash:
[[email protected] tmp]$ mkdir skyhawk
[[email protected] tmp]$ cd skyhawk && 7z x ../SHRP_v2.3.2_us997-233920072020.zip
[[email protected] skyhawk]$ fastboot flash recovery recovery.img
Sending 'recovery' (36936 KB) OKAY [ 1.252s]
Writing 'recovery' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Click to expand...
Click to collapse
I downloaded the Skyhawk zip from the PA download link, unzipped it and used the recovery.img file found inside the zip as part of the fastboot command. Is this incorrect ?
Yes, you need the recovery.img file to flash via fastboot. Have you successfully unlocked the boot loader? You cannot replace recovery without unlocking.
You also need to ensure you have the appropriate files for your phone I have a US997 but as you have H872 you would need skyhawk for the H872 in the notes above you are still using US997.
bootloader is unlocked as per:
https://forum.xda-developers.com/tmobile-g6/how-to/unlock-bootloader-tmo-t3578099
fastboot flash is failing and I'm not the only one it seems like based on comments here and reddit...
I gonna try out @runningnak3d guide and see if that works...
This guide is for the US997. The H872 has a much more complicated process to install recovery : https://forum.xda-developers.com/tmobile-g6/how-to/root-h872-to-including-11g-t3775518