As noted Here, and following on, I managed to get updated through to the OTA ICS, and attempted an upgrade to the 3.1 FlexRom.
After some attempts at fixing things, I'm at the point right now, where the issue seems to be in the boot-up sequence.
I have the following variables in play:
* I have fastboot access, but no ADB.
* The tab is now stuck in a continuous loop of the ANDROID boot loader screen.
(previously, it was the FlexRom bootloader)
* The USB at first was trying to install the A500 drivers, and now fails on "MTP USB Device" installation. It fails, but because it's unlocked, I have the first point available.
* CWM no longer loads, nor can I access any recovery functions.
(When CWM was loading, I used it to flash back to the stock OTA rom, rather than attempt another upgrade)
Attempted:
*using fastboot to update the rom via the update command. FAIL.
*using fastboot to run the OEM unlocker. The computer side says "OKAY" but nothing changed on the screen.
*fastboot WILL reboot the tab if given the command, so I know something is getting through, even with the failure of the USB cord to "work"
Have not attempted:
* Hard reset via the little hole. (I honestly don't think it will work)
* Methods I'm not aware of.
So to sum up, I'm stuck in a boot loop and can't get out.
Ideas?
Did you remove bootloader.blob and the recovery folder,from that stock OTA that you flash trough CWM?
I think you are not.That's why you're in this situation.Your bootloader is locked again, and you have the stock recovery (or may be broken recovery).
Try to do hard reset (the real hard reset) with the lock screen button+volume and power (search this forum or google it).It may help you .
Did you try other fastboot commands like: 'fastboot flash recovery recovey.img' or 'fastboot flash boot boot.img' (boot.img and recovery.img must be in the same folder with fastboot to do it this way) what they return?
If above doesn't help you still has a chance with nvflash but you must read this thread after post #48
Hope this is helpful enough!
sending 'recovery' (6144 KB)... FAILED (remote: (00000002))
(for 'fastboot flash recovery recovery.img')
Now it did reboot, and it seems I may be locked again.
This error popped up:
Fastboot: Not support the command in Lock mode
Failed to process command download: hexidecimal error code
No errors on a proper 'hard' reboot, it erased userdata and cache, and is letting me into the setup, so that's probably a good thing.
and indeed it is. I'm back into the OS, and it booted up normally.
I thought I had tried it before, but apparently, it didn't take.
Thanks!
Related
I was loading up my Nexus 7 (2013) with the Project L rom and ran into a problem. At the end of the install, I got an error that it could not erase the cache. I can boot into Bootloader but nothing else. It won't boot into recovery or launch the system OS. When I try to launch the system OS, I just get that updating animation that sits there for hours. Fastboot does recognize the device though, but when I try to do a fastboot erase of a partition, it just hangs. Anyone know how I can get out of this?
Try a complete reflash of 4.4.4 or 5 from fastboot.
Sent from my Nexus 7 using Tapatalk
ritchea said:
Try a complete reflash of 4.4.4 or 5 from fastboot.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I tried the process again. Whether I am trying to erase a partition, re-format a partition, or flash a partition, I get write errors. It is almost as if the rom is write-protected or something. It will copy partition images to whatever partition the bootloader is using, but just won't write them to the proper partitions.
So you are saying when you give the command [fastboot flash system system.img], you get a write error. I'm obviously not an expert, but i thought a new flash would do a complete wipe and create new partitions. If that is not the case (meaning flashing requires that partitions be in place), then you need someone who can tell you if/how to code for partitions or send it in for repair.
Is adb working? If so, you might want to try Wug's toolkit. (see android development).
When you try to start recovery from fastboot, do you get Andy with the red triangle, or what?
Sent from my Nexus 7 using Tapatalk
Check if your Android SDK is up to date
ritchea said:
So you are saying when you give the command [fastboot flash system system.img], you get a write error. I'm obviously not an expert, but i thought a new flash would do a complete wipe and create new partitions. If that is not the case (meaning flashing requires that partitions be in place), then you need someone who can tell you if/how to code for partitions or send it in for repair.
Is adb working? If so, you might want to try Wug's toolkit. (see android development).
When you try to start recovery from fastboot, do you get Andy with the red triangle, or what?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
ADB doesn't find the device any longer, although it did when I started the process. So I am left with using Fastboot. When I try to go into recovery, the screen goes black, then I get the Google logo, and it just sits there. When I try to launch into the system, I get they Andy lying down with the rotating geometric shape in his belly - forever. All that seems to work is the bootloader, and it's not really working. This is the kind of results that I am getting.
Code:
C:\Users\Daniel\Downloads\Nexus 7>fastboot devices
07b8be03 fastboot
C:\Users\Daniel\Downloads\Nexus 7>fastboot flash recovery openrecovery-twrp-2.8.
0.1-flo.img
sending 'recovery' (7878 KB)...
OKAY [ 0.254s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 90.015s
C:\Users\Daniel\Downloads\Nexus 7>fastboot flash bootloader bootloader-flo-flo-0
4.04.img
sending 'bootloader' (3911 KB)...
OKAY [ 0.130s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 1.067s
C:\Users\Daniel\Downloads\Nexus 7>
What happens when you do [fastboot reboot recovery]? I wish I understood more about this. First, lying down Andy with the red triangle is the recovery "pre" screen for stock recovery. The fact that system reboots to it may indicate you have no OS. Once you get to that screen, have you tried to get to the next screen (holding vol+/- and power at the same time for a few seconds)? It's tricky and directions say vol+ plus power, but it seems I've always had to press vol in middle. I've read it both ways. Try this first.
[When Stock Recovery starts you will see the Android fallen down screen
To bring up the Recovery menu
Power+VolUp to show recovery menu
Must be this sequence Press/Hold Power, THEN Press/Release VolUp, release Power]
Although I've found many instances of the write write failure you describe, no definitive answers. It does seem that Wug's Toolkit is worth a try. I read the following on his site. I realize it's about unlocking, but the point is you don't need adb to run commands from fastboot.
"WugFresh Mod Carey Parks • 4 days ago
You don't need to be connected via ADB (on with usb-debug enabled) to unlock. You just be connected via FASTBOOT (bootloader mode). Just use the "Unlock" button, and follow the instructions it gives you to MANUALLY boot your device into bootloader mode, then proceed from there. Its fine that your device is messed up.. you just have to get the bootloader unlocked. Once its unlocked you can use "Flash Stock + Unroot" with softbrick/bootloop mode to get your device back to normal. Cheers!"
Using the toolkit from fastboot without adb might help. (In fact, I didn't know this.) He further brought up these commands: You could also try to issue the commands (NRT advanced utilities > launch cmd prompt):
fastboot format system
fastboot format data
fastboot format cache
Of course this clears everything. But from this point, you could try the "Flash Stock+Unroot" step on the first page of the toolkit.
Have you tried to flash a totally different set of files (like the official 4.4.4 decompressed and placed into the fastboot folder)?
It is possible that your SD card has become corrupted. I'm pretty sure you can't issue any mount commands without adb so you can't set the card to write.
For the 15-20 minutes it will take to set up the toolkit and use it (it has to download files for your device, too). it may be worth the effort. Also, Wug is very good about helping. If you can provide him with a copy of what's happening (while using the toolkit), he will try to help. He really understands this stuff. If you're a "toolkit snob" (my term for those who deny usefulness of toolkits), then ignore that suggestion. You already understand how to use fastboot (which is why some say don't use toolkits). My personal experience is that the kit has helped me get out of bootloops a few times.
ritchea said:
What happens when you do [fastboot reboot recovery]? I wish I understood more about this. First, lying down Andy with the red triangle is the recovery "pre" screen for stock recovery. The fact that system reboots to it may indicate you have no OS. Once you get to that screen, have you tried to get to the next screen (holding vol+/- and power at the same time for a few seconds)? It's tricky and directions say vol+ plus power, but it seems I've always had to press vol in middle. I've read it both ways. Try this first.
[When Stock Recovery starts you will see the Android fallen down screen.
Click to expand...
Click to collapse
The Android logo I get when trying to boot into the OS is the animated one with the spinning wire-mesh ball thingy that one generally sees when the OS is updating itself. It just doesn't stop. I'll give the toolkit thing a try, but am about to head out for the day. Won't have a chance until later tonight or tomorrow.
djeaton said:
The Android logo I get when trying to boot into the OS is the animated one with the spinning wire-mesh ball thingy that one generally sees when the OS is updating itself. It just doesn't stop. I'll give the toolkit thing a try, but am about to head out for the day. Won't have a chance until later tonight or tomorrow.
Click to expand...
Click to collapse
Oh, I understand on the Andy. OK. Have a great day.
Kinda weird-- http://forum.xda-developers.com/showthread.php?t=2917463different circumstances but same problem. No one responding there, either.
I don't know why this would work when wug's does not, but some claim it did http://forum.xda-developers.com/showthread.php?t=2381582. You would download, extract, click Dead_Nexus7.bat file and run from fastboot.
Hello guys, a friend of mine has a galaxy nexus with some problems.
When I turn on the phone, it starts booting normally, but a few seconds after getting into "desktop" it starts popping up errors saying that the process as stopped.
I've already tried a few things, but without success. I'm running out of ideas and here I'm asking for your help.
Things I've tried:
-Boot into recovery mode and wipe all data.
The phone says that the operation completed successfully, but after rebooting the phone remains the same. All apps, wallpaper, lock screen, etc. It seems that nothing was changed by this process.
-Flash a original google ROM
Following the tutorials, the first step is to unlock the bootloader with fastboot oem unlock. The phone shows a confirmation asking if I want to unlock it, I say yes, and it shows "status: unlocked". But after rebooting the phone it is locked again!!!
I tried to flash the room without rebooting the phone after unlocking it,
Code:
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-maguro-i9250xxla02.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-takju-imm76i.zip
The first command to flash the bootloader also says that completes successfully, but when I'm flashing the radio it will complain saying that the phone has the wrong bootloader version installed.
-Flashing via Odin
It fails when is flashing system.img to the phone
-Flash custom recovery - fastboot flash recovery recovery.img
The process completes "successfully" but when I boot into recovery mode, there is the original one and not the one I just flashed.
-emmc brickbug - partition scanner
I found this thread http://forum.xda-developers.com/showthread.php?t=1823918 and tried to run the partition scanner. As I can't have the phone on enough time to use adb shell, I tried to use this scanner via adb sideload but the phones returns an error when running it. (probably because it doesn't have busybox installed, not sure)
After trying all of steps above, the phone is still the same... nothing changed. Once, I managed to connect it to the pc as an usb storage device, and was able to copy some photos from the phone and deleted them. But after rebooting they were all there again. It seems that all write changes are not persistent.
I'm out of ideas now... Do you have any idea of what is the problem? Or any suggestion for me to try?
Thanks in advance
I believe that there is a script in the android SDK tools called flashall.bat which will reflash the kernel, bootloader, recovery, ROM ect. I'm not sure how to use it, but you could potentially try that
Hi, thanks for you suggestion, but unfortunately it didn't work.
I had a look at the flashall.bat script and it runs the same commands I run manually.
I think that the phone might have some hardware problem... Normally I would buy a new phone, but I'm trying to fix it because it is important for my friend and for me because it is challenging.
I guess that the next thing I will try, will be trying to run emmc_find_brick script by @hg42 via sideload
Try formatting /system and reinstall android. Power your device into bootloader mode. Make sure your device is unlocked. Also, make sure you have the factory image downloaded. After your device is plugged in into your computer, use this fastboot command: fastboot erase system. This will delete everything from /system. Also format /data and /cache: fastboot erase data and fastboot erase cache. After that, try installing the factory image again.
LG G3 D852
Hey everyone, here's the summary of my whole situation: I've been trying to toy around with some roms for an old phone I had sitting around. Long story short, good phone busted so now back to this one.
Anyways, while trying to install literally every rom (except the one installed already, which I keep flashing to be able to text and all), no matter what ROM it was, it gave me an error saying, "Error executing updater binary in zip". I did some searching and read that it was because TWRP was outdated. Havent used this phone since 2016, so everything on it is outdated, made sense to me.
THIS IS WHERE MY REAL TROUBLE BEGINS!
So, while trying to update TWRP, I tried using different methods such as the Official TWRP App, as well as Flafishy, but all failed.
>>Booted into TWRP recovery, tried to update that way using the image file, followed instructions on the TWRP site, and it said it succeeded! But, when I went to power off and back on into recovery to make sure it went well, it started up in Fastboot Mode instead, and the only way to get that screen off was to take battery out. So now, every time I boot to recovery, it enters Fastboot Mode. However it CAN start up normally without issue.
>>>>The next issue I'm having is with updating TWRP through ABD.
After noticing it was only going to let me use Fastboot, I started the phone, made sure root access was given to Apps & ADB as well as made sure that Android Debugging was enabled.
Then, booted back to Fastboot screen and tried to flash the recovery file using the commands in cmd.
Made sure cmd was opened in the correct directory with the TWRP file, and after typing the flash command, command prompt sits at "Waiting for device" and the device doesnt respond, sits at the firmware screen completely frozen.
Here is what I typed for cmd;
C:\Users\Daqo\Desktop>fastboot reboot bootloader
rebooting into bootloader...
OKAY [ 0.199s]
finished. total time: 0.202s
C:\Users\Daqo\Desktop>fastboot flash twrp-3.0.0-0-d852
< waiting for device >
^^^Gets stuck here^^^
****Please note that after typing the bootloader command, the phone reboots normally and I have to manually press "Reboot to Bootloader" from the popup reboot screen (holding power button) in order to get to the firmware screen. I have tried rebooting to bootloader before and after typing the command to flash the file****
Any help is greatly appreciated
Hi,
i bricked my phone (by flashing lineageos16, now in QDL mode). Tried both blankflash files (oreo and NDX) but the logs usually look like:
EDIT: Somehow I managed to blank flash the device (literally tried it a zillion times) and since being genius I flashed the wrong file...
It was the Verizon file and now I'm stuck at the bootscreen saying the device is locked. I can unlock it but the next reboot it's locked again.
I guess, because of it, I'm unable to flash a recovery or a different bootloader (fastboot command always fails). When booting a recovery via fastboot the device shows the 'powered by' logo and nothing happens.
Selecting Qcom from the menu takes me back to the 'Fastboot Flash mode' screen. Tried the restart-edl command, same happens (fb_mode_clear doesn't help).
EDIT2: Talking to myself...
Battery does not load. I was able to flash a different bootloader (from the offical EU image) by changing the partition names inside the XML file (bootloader.image) to <something>_a. After that I flashed the whole image to the phone (again with
changed partition names "<something>_a" in flashall.bat).
Result: The device bootloops (powered by logo) and after some attempts it restores the verizon bootloader.
EDIT3: Still talking to myself...
No chance to flash a firmware without flashing the correct singleboot.img first. Putting the device into edl mode doesn't work (command restricted. edl cable or hotkeys neither work. SBL partitions protected. TP for edl unknown).
Hi guys,
I tried to flash TWRP on my Wiko Lenny 4 earlier.
I used adb and fastboot to flash it, however the touchscreen wouldn't work and I was stuck at the "swipe to allow kernel modifications" screen in TWRP. No problem, I reboot in recovery mode, and switched to fastboot mode.
I found another TWRP image and, after flashing with
-> fastboot flash recovery twrp.img
I typed another command,
- >fastboot boot twrp.img.
Since then I am stuck at the Wiko boot screen, saying:
Orange State
Your device has been unlocked and can't be trusted (initially I unlocked OEM)
Your device will boot in 5 seconds
Whatever combination of power+vol up/down I try to use, it only reboots to this screen.
adb won't reconize any device, as well as fastboot. And both are up-to-date.
Perhaps there exists a recovery image that I can put on my sd card, and hopefully it will automatically boot on the sd card as I don't have any control right now.
If someone has an idea, please tell me.
thanks
[EDIT] Solved
Using this link https://aiomobilestuff.com/how-to-unbrick-wiko-stock-firmware-via-wiko-official-site/
I was able to download Wiko's recovery tool from https://customer-world.wikomobile.com/
After unzipping and starting the software, it automatically installed drivers (I guess, if it does not, mediatek usb wiko drivers can be used instead) and downloaded the software into the phone which works now.