[CLOSED] No Longer Required
I would go into Settings and do a factory reset.
Or you could reflash the ROM with flashtool
Or you could also enter recovery mode and factory reset there.
I personally would just do the first option as its much easier.
Hey
I just want to start fresh, Everything back to what it was.
Can you help me restore my Xperia Play It says Free Xperia Play when i boot it up and has CM7
Thank You
- Sonny Dickson
Flash the stock ROM, and re-lock your bootloader.
Sent from the best phone ever
Using Fastboot i can't
iMaclatform-tools Sonny$ ./fastboot-mac -i 0x0fce flash system system.sin
< waiting for device >
sending 'system' (198672 KB)...
ERROR: usb_write failed with status e000400d
FAILED (data transfer failure (No such file or directory))
Related
Even being a SW and HW developer for a long time, I did had to spend some time to learn all the buzzwords in the "Android rooting" world to recover my Acer A200 tablet, so I'm sharing to save other people time:
My kid tried to guess the gesture password to play in my tablet, I don't know how many times, locking my Acer A200.
I tried google recovery, but the WiFi was off (and I could'nt turn on as the tablet was locked), so I went to the web to find a solution.
Factory reset seemed like a good one (turn device ON pressing power+down vol and switching the orientation key), it boots, then shows 'erasing user data', then hangs with an error:
Code:
Unrecoverable bootloader error (0x19000008)
Now the device is not booting, it get stuck on Acer logo after animation...
So I tried to use ADB to revert the damage, as indicated in one forum, but USB debug mode was not active when I did the factory reset.
ADB installation itself is unecessarily complicated, and as I cannot find a way to list the device in linux+adb ($>platform-tools/adb devices), even adding it to: /etc/udev/rules.d/51-android.rules (obtained with lsusb)
Code:
#Acer
SUBSYSTEM=="usb", ATTR{idVendor}=="0502", ATTR{idProduct}=="337d", MODE="0666", GROUP="plugdev"
It seems android isn't even booting to enable the debug bridge.
So I went to the "fastboot" as last resource (reboot using power+vol.down+switch.toggle), and did the command:
Code:
android-sdk-linux> platform-tools/fastboot oem unlock
I selected the "open lock" image and rebooted, now it shows: Bootloader v0.03.06-ICS(UnlockMode), but hangs in the same point.
So I downloaded a stock image from:
acertabletforum/stock-ics-recovery-image
Burned it using:
Code:
$> platform-tools/fastboot flash recovery /home/gaglocal/backup/acer/stockrecovery.img
sending 'recovery' (6144 KB)...
OKAY [ 1.882s]
writing 'recovery'...
OKAY [ 2.689s]
finished. total time: 4.571s
Same status after reboot.
So I've downloaded 'stock ROMs' from:
4shared/AcerStockROM
But when I try to write using fastboot:
Code:
error: update package has no android-info.txt or android-product.txt
So it seems this ROM is just for SDcard update (ie.: place the zip file as update.zip in the root of a fat32 sdcard, then boot using power+vol.down to perform the recovery process with it) but it fails and shows a dead android with a red triangle in the belly, not funny.
As the error that shows up when trying to issue the factory reset is after "erasing user data" I decided to do:
Code:
platform-tools/fastboot erase data
erasing 'data'...
FAILED (remote: (00030003))
finished. total time: 0.167s
This indicates this tablet has some HW misconfiguration issue. As some posted, I repeated the proccess a few times - no luck.
So I wrote the CWM 5.5.0.4 image from this forum, rebooted, and performed the sdcard recovery method again.
Same dead droid icon...
Finally I decided to erase the flash again, starting with the cache partition, using fastboot:
Code:
platform-tools/fastboot erase cache
erasing 'cache'...
OKAY [ 1.452s]
finished. total time: 1.453s
Finally, rebooted with the "factory reset" again and it worked!
At least i learned a lot without having to go to the Nvidia very-low level flashing process
A200 dead
gabriel_agm said:
Even being a SW and HW developer for a long time, I did had to spend some time to learn all the buzzwords in the "Android rooting" world to recover my Acer A200 tablet, so I'm sharing to save other people time:
My kid tried to guess the gesture password to play in my tablet, I don't know how many times, locking my Acer A200.
I tried google recovery, but the WiFi was off (and I could'nt turn on as the tablet was locked), so I went to the web to find a solution.
Factory reset seemed like a good one (turn device ON pressing power+down vol and switching the orientation key), it boots, then shows 'erasing user data', then hangs with an error:
Code:
Unrecoverable bootloader error (0x19000008)
Now the device is not booting, it get stuck on Acer logo after animation...
So I tried to use ADB to revert the damage, as indicated in one forum, but USB debug mode was not active when I did the factory reset.
ADB installation itself is unecessarily complicated, and as I cannot find a way to list the device in linux+adb ($>platform-tools/adb devices), even adding it to: /etc/udev/rules.d/51-android.rules (obtained with lsusb)
Code:
#Acer
SUBSYSTEM=="usb", ATTR{idVendor}=="0502", ATTR{idProduct}=="337d", MODE="0666", GROUP="plugdev"
It seems android isn't even booting to enable the debug bridge.
So I went to the "fastboot" as last resource (reboot using power+vol.down+switch.toggle), and did the command:
Code:
android-sdk-linux> platform-tools/fastboot oem unlock
I selected the "open lock" image and rebooted, now it shows: Bootloader v0.03.06-ICS(UnlockMode), but hangs in the same point.
So I downloaded a stock image from:
acertabletforum/stock-ics-recovery-image
Burned it using:
Code:
$> platform-tools/fastboot flash recovery /home/gaglocal/backup/acer/stockrecovery.img
sending 'recovery' (6144 KB)...
OKAY [ 1.882s]
writing 'recovery'...
OKAY [ 2.689s]
finished. total time: 4.571s
Same status after reboot.
So I've downloaded 'stock ROMs' from:
4shared/AcerStockROM
But when I try to write using fastboot:
Code:
error: update package has no android-info.txt or android-product.txt
So it seems this ROM is just for SDcard update (ie.: place the zip file as update.zip in the root of a fat32 sdcard, then boot using power+vol.down to perform the recovery process with it) but it fails and shows a dead android with a red triangle in the belly, not funny.
As the error that shows up when trying to issue the factory reset is after "erasing user data" I decided to do:
Code:
platform-tools/fastboot erase data
erasing 'data'...
FAILED (remote: (00030003))
finished. total time: 0.167s
This indicates this tablet has some HW misconfiguration issue. As some posted, I repeated the proccess a few times - no luck.
So I wrote the CWM 5.5.0.4 image from this forum, rebooted, and performed the sdcard recovery method again.
Same dead droid icon...
Finally I decided to erase the flash again, starting with the cache partition, using fastboot:
Code:
platform-tools/fastboot erase cache
erasing 'cache'...
OKAY [ 1.452s]
finished. total time: 1.453s
Finally, rebooted with the "factory reset" again and it worked!
At least i learned a lot without having to go to the Nvidia very-low level flashing process
Click to expand...
Click to collapse
Could you list the steps you took for the last successful attempt?
I tried all method but stuck at recovery.
Also does following;
"fastboot flash:raw boot boot.img-kernel boot.img-ramdisk.gz
fastboot flash recovery recovery.img"
unable to recover stock.
My bootloader is unlocked
Before Rooting ROM:
Kernel version: 2.6.39.4+
Image version : Acer_AV041_A200_RV10RC02_WW_GEN1
Build No. : Acer_AV041_A200_1.076.00_WW_GEN1
Hi, i installed the latest LG G5 Update (lineage-14.1-20170822-nightly-h850-signed), the first regular reboot was fine.
The second reboot has "bricked" my phone.
Please check the attached Picture from the phone.
Anyon a idea how to get back the phone to "life"??? :crying:
Thank you in advance for any assistance
MoPhat
This advise comes "as is" and with no warranty and I will not be responsible for any damages of any kind.
That's a soft brick (I wouldn't even call it a brick) and should be easy to resolve.
Did you erase data and system before flashing the ZIP file? You should always do this before flashing a new OS or did you just flash over your original LG5's OS without erasing those partitions?
Try re-downloading lineage-14.1-20170822-nightly-h850-signed and run a crc32 check on both zip files (the one you downloaded originally and the one you downloaded the second time) to see if the crc32 values match. If they don't, that would explain why you ended up in this situation (assuming you flashed the file the correct way). If you are on Windows, you can download a utility called "hashmyfiles" by NirSoft to get the crc32 along with other checksum values. If you are on linux, you can use the "crc32 lineage-14.1-20170822-nightly-h850-signed.zip" command to see the crc32 value and if values do not match, try downloading it again and do the check one more time until the values match. You can also click on the "sha256" and "sha1" links below the link you downloaded the file from and then using "hashmyfiles" you can compare the values whether they match.
Anyway, the way I personally would go with this one is try to enter Recovery mode, erase system, data (and probably boot but not necessary as the OS zip file will over write it anyway) and try again. If your recovery asks you to install root / SuperUser, you should select "No" and use LOS's official SuperUser add-ons if that's what you are after.
Thank you marco-v
I can't check the crc from the file because i have updated the latest Version with the build in update function...
I have tryed to boot in the recovery menu by pressing the power und volume down button, realising when i see the lg logo an pressing again both to (normaly) enter the recovery mode. it appears the same message
http://androidflagship.com/20275-boot-lg-g5-recovery-mode
the only menu that Comes are the "factory data reset" menu, but this makes no difference...
any further ideas?
marco-v said:
This advise comes "as is" and with no warranty and I will not be responsible for any damages of any kind.
That's a soft brick (I wouldn't even call it a brick) and should be easy to resolve.
Did you erase data and system before flashing the ZIP file? You should always do this before flashing a new OS or did you just flash over your original LG5's OS without erasing those partitions?
Try re-downloading lineage-14.1-20170822-nightly-h850-signed and run a crc32 check on both zip files (the one you downloaded originally and the one you downloaded the second time) to see if the crc32 values match. If they don't, that would explain why you ended up in this situation (assuming you flashed the file the correct way). If you are on Windows, you can download a utility called "hashmyfiles" by NirSoft to get the crc32 along with other checksum values. If you are on linux, you can use the "crc32 lineage-14.1-20170822-nightly-h850-signed.zip" command to see the crc32 value and if values do not match, try downloading it again and do the check one more time until the values match. You can also click on the "sha256" and "sha1" links below the link you downloaded the file from and then using "hashmyfiles" you can compare the values whether they match.
Anyway, the way I personally would go with this one is try to enter Recovery mode, erase system, data (and probably boot but not necessary as the OS zip file will over write it anyway) and try again. If your recovery asks you to install root / SuperUser, you should select "No" and use LOS's official SuperUser add-ons if that's what you are after.
Click to expand...
Click to collapse
So it looks like your Recovery mode is messed up too? Not sure how that might have happened unless you instructed LOS to "Update Recovery" .
Have you tried to see if you are able to enter fastboot mode and reflash your custom recovery image again and try to enter Recovery mode again? The one I use on my device (Oppo Find 7) is a TWRP image and I find it very reliable.
You can see if you can boot to Recovery by running the following command from fastboot mode (assuming you have a TWRP image)
fastboot boot twrp-x.x.x-x-h850.img
Replace x.x.x.x with the version of the file.
Tryed, result is:
Code:
C:\Temp\root_H850>fastboot boot twrp-3.1.1-0-h850.img
downloading 'boot.img'...
OKAY [ 0.430s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.451s
With "adb.exe devices" are the phone not listed
Ok, my device is locked!?!?
Code:
C:\Temp\root_H850>fastboot flash recovery twrp-3.1.1-0-h850.img
target reported max download size of 536870912 bytes
sending 'recovery' (19076 KB)...
OKAY [ 0.428s]
writing 'recovery'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.456s
So i have tryed to unlock the device again with the unlock key i get:
Code:
C:\Temp\root_H850>fastboot flash unlock unlock.bin
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.037s]
writing 'unlock'...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.059s
How can i disable the " Enable OEM unlock" in the developer Settings without a gui???
Ok, fastboot works, that's good but it looks like your bootloader is locked again.
FAILED (remote: oem unlock is not allowed)
Click to expand...
Click to collapse
Try following these instructions: https://forum.xda-developers.com/lg-g5/development/recovery-team-win-recovery-project-lg-g5-t3363047 and see if you can get TWRP running and if you do, you can try flashing LOS again but format data + system (you will lose all data) and if you are not careful, you might lose data on internal storage + external storage so read carefully what's displayed on the screen before going ahead.
Also: http://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS and this will show you how to unlock your bootloader.
---------- Post added at 01:42 PM ---------- Previous post was at 01:41 PM ----------
I just read your post, you can try:
fastboot oem unlock
and see if it works. May be it will because it was unlocked already once but can't tell for sure.
Sorry, nothing has worked.
I will try set "upgrade error" back in the lg update tool to flash the original firmware, but i need a SERIAL or the IMEI number, how can i find this out?
Normally, IMEI numbers are located right under the battery on phones that come with removable back covers and batteries. Yours however slides out, it might be somewhere there or perhaps you can check the box / packaging. So the following command didn't work?
fastboot oem unlock
What's the error you got? The official bootloader instructions on LG's website should have worked as it supports your model. To me the only issue you seem to be having is a restricted booloader and once you unlock it, everything should be fine. This is why you can't boot into TWRP using the boot command.
Not worked, the result is:
Code:
C:\Temp\root_H850>fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.025s
I see, thx, if the LG official unlock instructions did not or no longer work followed by the instructions here https://forum.xda-developers.com/lg-g5/development/recovery-team-win-recovery-project-lg-g5-t3363047, I am out of ideas. Perhaps someone else can help and provide further hints.
I try to re-flash my Pixel 2 XL but failed. The status is it reboot and reboot and......non-stop reboot.
I try to flash factory image on Recovery mode. it failed on bootloader. Below is the status on windows CMD.
----------------------------------------------
D:\Download\platform-tools-Flash>fastboot flash bootloader bootloader-taimen-tmz12a.img
target reported max download size of 536870912 bytes
sending 'bootloader_b' (36344 KB)...
OKAY [ 0.097s]
writing 'bootloader_b'...
FAILED (remote: Flashing is not allowed for Critical Partitions
)
finished. total time: 0.107s
D:\Download\platform-tools-Flash>
------------------------------------------------
I can not use the new phone anymore, please help to check my problem. Thanks.
Have you performed in fastboot Mode, at any time, this command: "fastboot flashing unlock_critical" ? (Without " ")
You can't flash factory image in recovery, it has to be done in bootloader mode, also can you boot in bootloader? Is your bootloader locked or unlocked?
Beast38 said:
I try to re-flash my Pixel 2 XL but failed. The status is it reboot and reboot and......non-stop reboot. I try to flash factory image on Recovery mode. it failed on bootloader. Below is the status on windows CMD. I can not use the new phone anymore, please help to check my problem. Thanks.
Click to expand...
Click to collapse
Apparently you have not unlocked your bootloader (critical) correctly. There are two separate commands needed to fully unlock it. That and you can't flash images from Recovery mode, you flash while in Bootloader mode. Read and follow the directions found on the same page you downloaded the image from HERE.
Thanks all. I re-check all procedure and re-do all process. It finally works fine for now.
I can not sure which step went wrong. All I know is "unlock done" "root failed or not complete".
Hi everyone,
I was in the process of unlocking my bootloader, flashing a recovery and rooting my Pixel C with the Skipsoft Toolkit when something went wrong.
The bootloader unlocked (30 sec screen and chirp) and I flashed TWRP but it got stuck there.
TWRP kept asking for the password to decrypt data, and now everytime I start my Pixel C it goes straight there again.
I've tried different options in the Skipsoft Toolkit but nothing seems to work and goes back to the 'Mount Decrypt Data' TWRP screen.
A few things that Ive tried are listed below.
Any help with me getting back to stock and having the Pixel C working again would be greatly appreciated.
Thankyou
4. Root/UnRoot/Disable Encryption/Flash Stock Boot/Check Root Status [ADB Mode]
7. Unroot, Uninstall Busybox and Restore Stock Boot/Recovery [ADB Mode]
1. Push file, reboot to Custom Recovery and install manually [simplest method]
Working out the best location to set for Internal Storage..
Waiting for Adb Mode ...
Device mode detected [recovery adb]
Android Version Detected: 7.1.2 Serial Number:
Pushing Unroot-SuperSU.zip to: /sdcard/
root\Unroot-SuperSU.zip: 1 file pushed. 0.1 MB/s (3574 bytes in 0.064s)
File/s pushed successfully
Device mode detected [recovery adb]
Device Serial Number:
Rebooting to Fastboot Mode and continuing..
Device mode detected: Fastboot Mode
Device Serial Number:
Device Bootloader State: Locked
Booting TWRP recovery-twrp-3.1.1.1-ryu.img ..
creating boot image...
creating boot image - 13051904 bytes
downloading 'boot.img'...
OKAY [ 0.323s]
booting...
FAILED (remote: image verification failed)
finished. total time: 0.328s
An Error Occured
Press any key to return to the Main Menu..
5. Rename Recovery Restore Files [Fix system flashing stock recovery on boot]
Device Bootloader State: Locked
Booting TWRP recovery-twrp-3.1.1.1-ryu.img ..
creating boot image...
creating boot image - 13051904 bytes
downloading 'boot.img'...
OKAY [ 0.331s]
booting...
FAILED (remote: image verification failed)
finished. total time: 0.331s
An Error Occured
Press any key to return to the Main Menu..
9. Download/Extract/Flash Google Factory Stock Image [Flash Part or Whole Rom]
2. Flash Google Stock Image [in the put_google_factory_image_here\device folder]
image-ryu-opm1.171019.015.zip
ryu-opm1.171019.015-factory-64c65be2.zip
Are you ready to proceed? Type y[yes] or n[no]:
Google Stock Image found [.zip format] in the correct folder.
Filename of image to flash: ryu-opm1.171019.015-factory-64c65be2.zip
Processing archive: put_google_factory_image_here\GooglePixelC\image-ryu-opm1.171019.015.zip
Extracting android-info.txt
Extracting boot.img
Extracting cache.img
Extracting recovery.img
Extracting system.img
Extracting vendor.img
Everything is Ok
Starting Flash Process..
Flashing Bootloader Image..
target reported max download size of 268435456 bytes
sending 'bootloader' (16384 KB)...
OKAY [ 0.416s]
writing 'bootloader'...
FAILED (remote: unsupported command)
finished. total time: 0.431s
An error occured when flashing the image
Try rebooting the device manually back to fastboot mode:
1. Unplug the usb cable
2. Stand the tablet in landscape mode [power button on top] and Press and Hold the
Power and Volume Down buttons for 10-15 seconds until it reboots to Bootloader
mode. Then select 'Switch to fastboot mode' using the volume button and press
the power button. The device will say 'Waiting for fastboot command...'
From the main menu in the Toolkit choose the Download/Extract/Flash menu, then
select Flash previously downloaded image.
Sometimes there is a glitch in the flash process and doing it again will fix it.
You can skip the password and change data file system partition to ext3. Then install custom systems like lineage os.
rhmanoa said:
You can skip the password and change data file system partition to ext3. Then install custom systems like lineage os.
Click to expand...
Click to collapse
Hi and thanks for the response.
How do I change data file system partition to ext3?
I can skip the decrypt password screen in TWRP and go into the general settings, but I dont know how to convert the system partition to ext3.
Thanks
Go to wipe data/cache then advanced wipe then change partition setting select data partition change to ext3.
when i tried to unlock bootloader it says:
target reported max download size of 1610612736 bytes
sending 'unlock' (5 KB)...
OKAY [ 0.032s]
writing 'unlock'...
FAILED (remote: Invalid data)
finished. total time: 0.095s
why always like that , i've tried to get new img but still remote invalid data
Z2 Plus doesn't actually lock the bootloader. With locked bootloader, the phone can still boot with unofficial ROMs, there's merely a warning message before the phone continue to boot - even if you unlock the bootloader, such warning still won't go away.
You may use QPST/QFIL's partition manager (with the firehose flasher program extracted from stock ROM package) to flash TWRP into the recovery partition.
Unlocking bootloader merely provides convenience in fastboot mode. However it's not hard for Z2 to enter EDL (9008) mode, the so-called "deep flash USB cable" works. There're test points on the mainboard as well.
Hi! If you're trying (and failing) to flash the sn.img file received via email, check on my answer Here.
Good luck!
Yea please someone help tried everything but it still shows unlocking failed remote invalid data