Hi,
I try to boot my Nexus 7 (2013/wifi). I have access to :
a white google logo
a fastboot access
and a recovery mode (with a sideload option)
I was reading my email when the tablet suddenly reboot and stuck on the Google logo. Now, I don't know what can I do.
Code:
Fastboot oem unlock
doesn't work (FAILED <unknow error>).
I can flash a new bootloader (FLO-04.04) but can't unlock it.
Are you getting any specific error message ?
After recovery mode I have something like :
Code:
-- Wiping cache...
Formatting /cache..
Cache wipe complete.
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_locale
I make a `fastboot oem unlock` right now and waiting after a error :angel:
Code:
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
edit : After 23000 s
FAILED (unknown status code)
May be my best choice is to waiting for 5.1 OTA (nexus 7 2013 wifi) and make a sideload ?
Any suggestion ?
jaiunxda said:
Any suggestion ?
Click to expand...
Click to collapse
Last chance : https://www.change.org/p/google-lg-...aign=share_twitter_responsive#petition-letter
I accepted the 5.1 OTA, it seemed to download fine, rebooted to install it, and it failed at around 20% or so with this log:
Code:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
"/system/app/ConfigUpdater/ConfigUpdater.apk" has unexpected contents.
E:Error in cache/update.zip
(Status 7)
Installation aborted.
Since then, that's all I get when I boot it up. I don't have ADB Debugging enabled, so I figured the easiest way to fix it was to flash back to stock, but I can't get it the bootloader to unlock. I can get to the bootloader, and fastboot recognizes it with the correct serial number, but fastboot oem unlock keeps failing with this:
Code:
...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: ()
finished. total time: 2.640s
I've tried all the USB ports on my computer and several different cables, but the result is the same. I've been banging my head against the wall for a couple weeks now on this, tried a couple different tools, but it all keeps failing at the same spot because the bootloader just won't unlock. Is there any hope of fixing this, or am I in the market for a new tablet?
Can you try opening ADB/Command Prompt with administrative rights and retrying the unlock of the bootloader?
Fobos531 said:
Can you try opening ADB/Command Prompt with administrative rights and retrying the unlock of the bootloader?
Click to expand...
Click to collapse
All right, gave that a shot, but still getting the same results.
I had my N7 go belly up too while doing the update. What got things back to normal was to use the "flash-all.bat" file that comes with all the updates (it's in the zip file from Google. Caution!!! ****Each flash-all.bat is unique to each Android version****. Make sure you use the proper .bat file. ). First I had to go back to 4.4.4 (for some unknown reason). After that, I did the same (ran the "flash-all.bat" file that came with 5.1) and bingo, everything went fine.
I was about to toss my N7 in the garbage, but after getting this suggestion from XDA member "Fobos531", gave it it go and it worked.
Look over here:
http://forum.xda-developers.com/nexus-7/help/thank-google-bricking-nexus-7-t3082379
Also make sure to take a look at this thread, I thought it might be relevant: http://forums.androidcentral.com/go...s-bootloader-failed-remote-invalid-state.html
phillip - Unfortunately (or maybe fortunately), since I can't get the bootloader unlocked, I haven't been able to get far enough to screw it up by flashing the wrong thing. Using the flash-all.bat starts by failing to unlock the same way, then not flashing anything at all because the bootloader is still locked.
Phobos - My tablet shows 4.23 installed. Since the last successful system update was the LRX22G OTA, is it then likely I have the invalid version? And if so, any clue how I would go about fixing that with the bootloader still locked?
Maybe bootloaders can be flashed while being locked? Try flashing this one using fastboot(the link is from this site:http://www.wugfresh.com/google-changes-nakasi-and-nakasig-factory-packs/) : https://www.androidfilehost.com/?fid=95916177934550135 Make sure the md5 checksum is valid: it has to be df53028033c9eccf4fe5ba7bc198ce24). Afterwards flash it using "fastboot flash bootloader name-of-bootloader-file.img (i think this is the right command).
Note: Everything you do, you do on your own risk.
Good luck!
EDIT: In the WugFresh page it says that your bootloader must already be unlocked, but I just don't have any idea on how to fix the adb error you are getting.
I have flashed Rollback package and stuck in bootlogo.
I can boot only in Fastboot mode but i cannot flash anything.
Message says FAILED (remote: Command not allowed)
How i will recover this device ?
Device is VNS-L31
mahmutelmas06 said:
I have flashed Rollback package and stuck in bootlogo.
I can boot only in Fastboot mode but i cannot flash anything.
Message says FAILED (remote: Command not allowed)
How i will recover this device ?
Device is VNS-L31
Click to expand...
Click to collapse
Hello,
take a look at the UNIFIED HELP THREAD,
post#6 ---- UNBRICKING AND DOWNGRADING FROM EMUI 5
where it is well explained how to use the rollback package.
You need the marshmallow version of your ROM stock.
Ex: VNS-L31 Rollback Package + VNS-L31 (C432 or C185 or others) B160 / 1,
depends on whether dual or single SIM or others available for your CUST / Region (C432 or others).
Follow the procedure carefully ...
Cheers
This error pops up whenever i try to install a custom rom.
I have tried multiple versions of TWRP and multiple roms, all get this error.
I have an LG-H870
Fixed by removing the line
Code:
abort("E1001: Failed to update system image.");
in
(ROM ZIP)/META-INF/com/google/android/updater-script
orakmoya said:
Fixed by removing the line
Code:
abort("E1001: Failed to update system image.");
in
(ROM ZIP)/META-INF/com/google/android/updater-script
Click to expand...
Click to collapse
this will never work. it just ignored the error,but the error still exists and you will not flash successfully
I am getting always the same error:
E1001: Failed to update system image.
Updater process ended with ERROR: 1
I wiped and formatted every partition, installed the most recent firmware.
I would appreciate any suggestion or advise. Thanks.
Then begin from new. First the right miui version with mi flashtool( don't look your bootloader) and then step by step