My Nexus 7 Wifi would start but then I got the 4 coloured circles rotating forever. I tried restoring factory settings with no effect. I thought I might reinstall the OS using Nexus Root Toolkit V1.9.3. Driver wouldn't install automatically. I installed a driver manually and Device Manager shows Android Phone -> Android ADB Interface but Toolkit test says ADB Device was not found. Tried Flash Stock + Unroot with Soft Bricked/Bootloop option. Failed at sending bootloader. (Bootloader is locked). Unlocked and tried again. Failed at writing bootloader (Invalid state), then sending boot (data transfer failure - Unknown error). Device now shows tiny message 'Booting failed' on Google screen with options to Start / Restart bootloader / Recovery Mode / Power off options when it starts. Maybe I've killed the device. Thought I would try the '[GUIDE] Flashing a Factory Image with fastboot/return to stock', but don't know what image I should flash. nakasi android 4.3 JWR66Y? Won't be able to enable usb debugging on my device when I get to driver installation section. Is device recoverable? I'm completely new to Android so if you want to help you'll need lots of patience.
Never mind
I tried Nexus Root Toolkit a few more times and it got past the error and completed the install. Can't image why it worked, but it's OK now.
Related
I have an unlocked rooted nexus 10. I downloaded the rom file and google tools to the device. I restarted into recovery mode and cleared system, and all caches. Well since I'm stupid the rom img is not on the device and I'm stuck with no OS to boot into. I tried to reflash the stock Rom through my macbook from this link "nexus10root.com/nexus-10-unroot/how-to-unrootunbrick-nexus-10-factory-firmware/" and I get this error - error ERROR: usb_write failed with status e00002be FAILED (data transfer failure (No such file or directory))" when it tries to install the system. Is there anything else I can do? My guess is that it is not in USB debug mode since I tried a factory reset. Thanks in advance
Edit: All happy now, a change of pc solved the problem of not detecting the device!
Hi all! I have another challenge for you!
Right, I've got myself in a tizz with my Defy +. While updating between CM10.1 versions I found myself in a situation where I couldn't get past the boot animation. So I loaded the TWRP restore I had made prior to updating...
Except it wouldn't, instead it came up with 'Failed' each time I tried any of the TWRP backups I had created. So the next step was to wipe partitions and start flashing various ROMs until I found one what worked. Except they didn't work either. Eventually I thought the best idea would be to just turn the phone off and see where I was with booting.
So power on, boot logo, blue light, red light then... nothing. Just the boot logo static. Went into the custom bootloader to go into recovery again, nothing. Pressing Custom recovery simply loops back to the top bootloader screen.
Ok next step, flash .sbf and start from scratch. So into the Moto bootloader it is to plug in and flash except... it's no longer detected by my computer.
"Ok" I think, "We'll just flash files from the SD card after I use an external SD card reader.
Except now when I enter Moto recovery to flash the TWRP recovery I get:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verifiaion failed
Installation aborted
So to recap:
1) Tried to flash and update, failed
2) Tried to recover, recoveries wouldn't write (I think this is becaue I'd changed to EXT4 on /data and /cache and had forgotten to go back to EXT3 before trying to recover)
3) Tried to boot, epicly failed
4) Tried to flash .sbf, Defy+ won't appear in RSDLite 5.7 with latest driver
5) Tried to flash from SD card, sig verification failed
6) Googletastic for the last four days
Notes:
a) I CAN charge the Defy+ using the wall charger but I get '?' for the battery level indicator but...
b) In Cmod bootloader 2.1 (Which I can use a little) it shows the correct battery level
c) I /was/ getting some errors with not being able to mount /cache from the moto recovery but I've since used the cmod bootmenu 2.1 to set it back to ext3 and it's all happy now, those errors aren't appearing
d) Plugging in my Defy red lens I get W8 x64 detecting the correct portal drivers and such but when I go to moto bootloader this device also doesn't appear in RSDLite
e) Both devices prompt windows to install a Motorola Flash Interface driver in Device Manager when plugged in in moto bootloader mode and neither device appears in RSDLite despite the fact the program is running in Admin mode
f) Looking at the logs in bootloader, it appears that I might not have formatted anything from ext4 to 3, everything I select in the cmod bootmenu returns .E:Error in /system/... , (Result: Invalid arguement) , Done..
So at the moment I think I need to acheive one of the following:
1) Find a file that allows me to write any useful data to /system like a recovery or some of those bootmenu files that passes the signature verification
2) Find a way to troubleshoot RSDLite so I can actually flash .sbf and get out of this hellhole
Many regards!
Alexis
If your custom recovery is not working, then you cannot do anything other than flash an sbf(nothing except data and cache wipe can be done via stock recovery): this is due to the locked boot loader(recoveries cannot be simply flashed from the stock recovery as you're trying to do)
Sent from my MB526 using Tapatalk 2
Success (ish)!
Yes I swapped to a different machine and then upgraded the version of RSD Lite installed on it from 4.7 to 6.1.5
[URL="http://forum.gsmhosting.com/vbb/f166/rsdlite-6-0-mtk-patch20-rsd-lite-6-0-a-1545012/index2.html#post8988239"]http://forum.gsmhosting.com/vbb/f166/rsdlite-6-0-mtk-patch20-rsd-lite-6-0-a-1545012/index2.html#post8988239
And flashed the 'lower' of the two .sbf's from the links on this forum for the British variant. After a DEA1 error (Phone is dead, code corrupt and all the bad things) I managed to flash the file.
As of yet I've not managed to get out of the bootloop but I've not carried out the requisite steps as mentioned in the "So you think you've bricked your Defy/Defy+" thread.
Lessons learned:
1) Motorola drivers and RSD Lite are pennickety, you will probably need to mix them up in order to get them to behave properly
2) If all else fails, use a different computer
3) You will probably need to flash over and over, while making every effort to not muck them up. Be aware the efuse system only has limited uses before it's useless though...
My saga continues, from no USB support hopefully to a fully working device again
In the end switching PC then doing the factory reset from moto recovery let the phone boot, all standard but the dodgy USB stuff at the first post is what sent me away from the right track.
Hi. My Nexus 7 (wifi) has LRX22G android version. Recently my tablet freezed so I held power button for few seconds to force reboot. After boot i saw decryption failed (picture in attachments in rar file) . After I clicked reset tablet it booted in recovery mode with no command image. I chose wipe data/factory reset. It showed wipe complete but after reboot android stuck on boot loop with no command image (cant show due to prevent spam system on xda and attachments size limit :/ I will send link on private message) . I force shut down and after boot it again shows decryption failed. I suppose that i need to flash rom (I bootloader locked, without root) but i cant enable usb debugging, because i cant get out from this "decrytpion failed window"(I want flash to KTU84P version if possible because LRX22G works slooowly :/). I hope that i showed my problem clearly(I dont speak englisch very well). Thanks for help in advance
Solved .
Tablet came back from service. Mainboard was broken. Topic to close .
Hello. I tried downgrading from the latest ASUS firmware to Android 6.0.1
I used this tutorial to install the raw firmware: http://www.asus-zenfone.com/2016/12/asus-zenfone-3-raw-firmware-and-asus.html
Went all the way to the last step when the app hanged. ASUS Flash tool went all the way saying
Code:
Run flash image script ...
It was hanged there. And as per this video, went all the way to the end where it showed the "code bar" on the right (https://www.youtube.com/watch?v=P8xg7A-P7Ak)
This is when the "Android" uninstalled driver showed up in Windows. This is under "Other devices - Android". I tried updating this driver using the ASUS_Android_USB_drivers_for_Windows found here: https://www.asus.com/Phone/ZenFone-3-ZE552KL/HelpDesk_Download/ but it wouldn't install the drivers.
Note that I used these ASUS USB drivers to get the ASUS ADB Interface installed. As per the tutorial I showed in the very first paragraph, I never got the "ASUS Android Bootloader Interface". This is what I think this "Other devices - Android" is found under Computer - Manager - Device Manager.
Most tutorials on the internet shows that the "ASUS Android Bootloader Interface" should be installed using these drivers found on ASUS website, the ASUS_Android_USB_drivers_for_Windows.
Now of course because I unplugged the phone, it will continously stay on the Android splashpage showing the loading circle infinitely.
As a last attempt I tried installing the "stock", not "raw" firmware (the one I wanted to install WW_13.16.5.49 but ASUS would not let you downgrade using the recovery "power+volume down" and using "Apply update from microSD card". It would give the
Code:
Warning- No file-contexts. This package is for "ww-phone" devices, this is a E:error in /side load/ package.zip (status 7) Installation aborted.
)
Well, after it brinked, I tried it again and this time it DID install WW_V13.16.5.49. Was succesfull. But after the ASUS splashscreen it's still stuck in the booting process.
I am very sorry if my post is convoluted but I tried explaining everything I did. Any way to un-brink it? I think maybe if I figure out how to properly install the ASUS Android Bootloader Interface, I can try again ASUS Flash tool and install the raw image and maybe that will fix it?
Please help. Any questions if my thread is too confusing, please let me know and I will answer it. I can't even turn off the phone. While it's stuck into the load splash screen, if I press the power button it just restarts, not turn off.
I still have access to fastboot (pwr + volume up) or recovery (pwr + volume down)
EDIT: Phone won't get recognized anymore in ASUS Flash Tools. Serial number won't show up to select
Factory reset and delete cache/dalvik through recovery and post back. It'll take 5-10min to boot up after that. You should always delete cache/dalvik after flashing.
wang1chung said:
Factory reset and delete cache/dalvik through recovery and post back. It'll take 5-10min to boot up after that. You should always delete cache/dalvik after flashing.
Click to expand...
Click to collapse
Thank you, this actually worked!!
Aaaand, it's actually on the version 13.16.5.49!!!! THIS IS EXACTLY WHAT I WANTED!
So apparently by brinking my latest nougat 7.0 update from ASUS via the ASUS Flash Tool trying to flash the .RAW 13.20.10.137, the standard recovery system (power+volume down) allowed me to install the 13.16.5.49 version. Then I assume remnants files didn't allow to properly boot, and your idea to wipe cache and factory reset fixed that!
What is so great is that I was scared that because the .RAW firmware was newer than the version I needed (13.16.5.49), I wouldn't have been able to install it. It was the same problem initially, when I tried to install 13.16.5.49 directly via recovery over the latest nougat 7.0 version from ASUS, but it was giving me
Code:
Warning- No file-contexts. This package is for "ww-phone" devices, this is a E:error in /side load/ package.zip (status 7) Installation aborted.
I think this error was due to the fact that ASUS won't allow older firmwares to be installed over newer ones, as per their webpage
https://www.asus.com/support/faq/1009748
Code:
You can not change the SKU from one to another, e.g., WW -> TW, and also can not downgrade your firmware, e.g., V2.20.40.13 -> V2.19.40.18
So in the end, what allowed the 13.16.5.49 stock firmware to be succesfully installed? The installer not detecting a proper firmware anymore because of the damaged update due to ASUS Flash Tools hanging because my computer won't install ASUS Android Bootloader Interface?
Glad you got it going :good:
Yesterday suddenly while turning on my device it stuck at android one logo.
Device status : Bootloader locked, No Root. Never hard reset in past. it was running as it was out of the box with latest May 2020 security update.
So, i tried to unlock bootloader with adb which offcourse failed.
then i tried to hard reset, as i opened recovery mode (power + vol+) there was an error E: failed to load bcb message, failed to fsync : operation not permitted.
still i choose wipedata/factory reset. it stuck at [wiping data... formatting disk...] for 5 hours. i understood it wont proceed.
Then, i opened the device went to unlock bootloader with EDL method as shown in few videos ( by connecting pins and plugging usb to pc). it showed in the pc ( qualcomm was listed in device manager> ports)
Then i downloaded Mi flash and official rom, was unable to flash with error "ack count don't match".
Again reading here and there, i downloaded miflash-beta, it was able to flash the device successfully.
disconnected the usb, connected the battery strap and started device > Again it stuck at android one screen for 1 hour.
So, i again went to recovery mode to find out that the error " E: failed to load bcb message, failed to fsync : operation not permitted." Still exists.
Read here in some thread that it is related to partition damaged, but no solution anywhere.
Please help me with solution. This is my only phone. i don't have any job nor money to buy other phone during lockdown.
HELP.
Thanks everyone for this wonderful forum.
MIA1_Stuck said:
Yesterday suddenly while turning on my device it stuck at android one logo.
Device status : Bootloader locked, No Root. Never hard reset in past. it was running as it was out of the box with latest May 2020 security update.
So, i tried to unlock bootloader with adb which offcourse failed.
then i tried to hard reset, as i opened recovery mode (power + vol+) there was an error E: failed to load bcb message, failed to fsync : operation not permitted.
still i choose wipedata/factory reset. it stuck at [wiping data... formatting disk...] for 5 hours. i understood it wont proceed.
Then, i opened the device went to unlock bootloader with EDL method as shown in few videos ( by connecting pins and plugging usb to pc). it showed in the pc ( qualcomm was listed in device manager> ports)
Then i downloaded Mi flash and official rom, was unable to flash with error "ack count don't match".
Again reading here and there, i downloaded miflash-beta, it was able to flash the device successfully.
disconnected the usb, connected the battery strap and started device > Again it stuck at android one screen for 1 hour.
So, i again went to recovery mode to find out that the error " E: failed to load bcb message, failed to fsync : operation not permitted." Still exists.
Read here in some thread that it is related to partition damaged, but no solution anywhere.
Please help me with solution. This is my only phone. i don't have any job nor money to buy other phone during lockdown.
HELP.
Thanks everyone for this wonderful forum.
Click to expand...
Click to collapse
did you find any solution
Same with my phone. Did you find any solution ?