I bricked my MT6577-based phone. I ran an app which re-partitions the drive, and this stopped the phone from booting -- the initial boot splash screen appears (in this case an Android icon), but it doesn't get to the point where it loads the OS (which would be represented by an Android icon where the droid's eyes and 'jetpack' light up).
I have placed the phone in recovery mode (power+vol up), and connected this to my PC (Windows 7). The PC does not recognise the phone and flags up an "unknown device" (code 43), so I cannot do anything with the flash tool or MTK tools.
I'm assuming that the original ROM is still intact, but can anyone confirm: is this phone recoverable? I should point out that it appears not to be possible to get a copy of the stock ROM for this device, I have searched at length with no success.
If it's dead without the ROM, a single line to the effect will put my mind at rest at least
Reinstall the drivers and then connect your phone in recovery mode
Use yuweng's ctr recovery porting tool and get the custom recovery
Then in wipe menu, wipe data and emmc partition then try
Otherwise you'll need the stock rom to he flashed by flashtool
Press thanks :good: if I've helped :highfive:
Related
Hello there,my Wave 8 HD+ stuck in android boot logo. I downloaded the wave8hd_20151105_v1.8 update thru wireless update and install, it says error in installing:
E:error in /mnt/internal_sd/adupsfota/update.zip
(Status 7)
Installation aborted.
My tablet is now in recovery mode and cant move highlight due to no volume buttons available,i can only select the "reboot system now" option.
Any other alternative for volume button so that i could just do the factory reset??
I also followed the detailed instruction on bluewave website on how to update the said Tablet thru PC but to no avail.
i emailed both the Telecom Company from where i get my Bluewave Tablet and the Bluewave Customer support but until now they stiil haven't replied yet.
thank you very much for your immediate reply.
-Jovi
jovirex said:
Hello there,my Wave 8 HD+ stuck in android boot logo. I downloaded the wave8hd_20151105_v1.8 update thru wireless update and install, it says error in installing:
E:error in /mnt/internal_sd/adupsfota/update.zip
(Status 7)
Installation aborted.
My tablet is now in recovery mode and cant move highlight due to no volume buttons available,i can only select the "reboot system now" option.
Any other alternative for volume button so that i could just do the factory reset??
I also followed the detailed instruction on bluewave website on how to update the said Tablet thru PC but to no avail.
i emailed both the Telecom Company from where i get my Bluewave Tablet and the Bluewave Customer support but until now they stiil haven't replied yet.
thank you very much for your immediate reply.
-Jovi
Click to expand...
Click to collapse
maybe try to use adb and try to push the firmware manually.. if they have a firmware download available
toolhas4degrees said:
maybe try to use adb and try to push the firmware manually.. if they have a firmware download available
Click to expand...
Click to collapse
I did use the software Rockchip Batch Tool v1.7 provided by Bluewave in their website,install the 33GT driver for my tab(Tab can now be seen by my PC and download the correct firmware update(using my serial number at the back of said tablet) still provided by Bluewave,but still error in upgrade..
i just want to know how to change the highlighted option in recovery mode so i can wipe/factory reset my Tablet disregarding the said update..
there is an option in recovery mode "recover system from back up" but i could not choose to highlight and select the option..
any alternatives for the volume button??Btw,the firmware provided by Bluewave is in ".img" format,not "zip"..
thank you so much for your reply..
-Jovi
i have the same problem, got an error after wireless update.. please help!
to fix this... use your otg cable and connect a usb mouse then reboot it once its reboot use the mouse to move into the recovery mode... wipe data and cache then select update adb sideload once inside the sideload press the power button until it reboot.. once you see the bluewave and its start to have a loading in the lower right corner.. voila... your tablet is fix ... hope it help u
ohgnevets said:
i have the same problem, got an error after wireless update.. please help!
Click to expand...
Click to collapse
wave 8hd+
jho_zep said:
to fix this... use your otg cable and connect a usb mouse then reboot it once its reboot use the mouse to move into the recovery mode... wipe data and cache then select update adb sideload once inside the sideload press the power button until it reboot.. once you see the bluewave and its start to have a loading in the lower right corner.. voila... your tablet is fix ... hope it help u
Click to expand...
Click to collapse
hello, jho_zep, thank you so much for your reply, i am now able to move the highlight to select using my mouse, but still when i try to update from ADB, it tells me to send package to the device etc.. and i also tried to press the power button, it wont reboot the system, it would only shutdown the system.. another thing, i still cant get rid of the system update. " installing system update" then error comes in, my android is down.. i tried wipe date/ factory reset, still nothing.
Thanks in advance
Do you already solve your problem? because I have now the same problem as this.
I have pressed the wireless update then it restarted and it says an Error status 7.
I don't know what to do and how to deal with this problem.
can you help me?
My nextbook tablet rk3026 has a partition named metadata that holds the recovery boot commands. You could possibly try to wipe it and do a factory reset. I don't think it actually gets mounted so you would need to find a file the same size as the partition and dd to it. Or back up your system with rockchip flash tool then using a hex editor replace all data in metadata image with zeros. Obviously be careful. Here is a tool download with included guide credits to finless at freaktab(not sure if he is here at xda) for posting it.
http://freaktab.com/forum/developme...p-your-rk-device-rom-with-the-new-rk-2-1-tool
as always BACKUP and know if you don't do it correctly you may get a brick.
thank you for the response Destructos. but that solution won't help for my freakin weird tab 33gt HD+.
I get frustrated now
Problem solved
first thing to do is make sure that you have already installed the rkchip_usb driver in your computer.
What are the requirements?
1st of course your Tablet and Cable Connector
2nd Finless ROM Flash Tool v1.37
3rd Rokchip BatchTool v1.7
4th the update image/firmware for your Bluewave 8 HD+ that is downloadable from their official website
Steps:
1. off your tablet and connect it to the computer
2. open the Finless Rom Flash, uncheck all the boxes
3. turn ON your Tablet (be attentive) and while the blue screen is starting you may NOTICE that the ROM FLASH TOOL detected your device, it says "RKAndroid Mass Storage USB". when you have read that, press immediately the "Reboot Flash mode" and your device will in black screen. but ROM Flash tool still detected your device as "RKAndroid Mass Storage USB "
4. Open the Batch Tool, (you must know how to use it) find your image, then you will notice that the CONNECTED DEVICES below have color green, in that case you may now Click UPGRADE. wait for a minute and booooom, you device is functionable again.
have a feedback if it is helpful.
P.S.
before I go to that steps, when I am stuck in RECOVERY MODE of my device, I Click the Recover from BACKUP then my tablet restarts and it turns to BOOTLOOP and repeatedly saying NO COMMAND.
PLDC said:
first thing to do is make sure that you have already installed the rkchip_usb driver in your computer.
What are the requirements?
1st of course your Tablet and Cable Connector
2nd Finless ROM Flash Tool v1.37
3rd Rokchip BatchTool v1.7
4th the update image/firmware for your Bluewave 8 HD+ that is downloadable from their official website
Steps:
1. off your tablet and connect it to the computer
2. open the Finless Rom Flash, uncheck all the boxes
3. turn ON your Tablet (be attentive) and while the blue screen is starting you may NOTICE that the ROM FLASH TOOL detected your device, it says "RKAndroid Mass Storage USB". when you have read that, press immediately the "Reboot Flash mode" and your device will in black screen. but ROM Flash tool still detected your device as "RKAndroid Mass Storage USB "
4. Open the Batch Tool, (you must know how to use it) find your image, then you will notice that the CONNECTED DEVICES below have color green, in that case you may now Click UPGRADE. wait for a minute and booooom, you device is functionable again.
have a feedback if it is helpful.
P.S.
before I go to that steps, when I am stuck in RECOVERY MODE of my device, I Click the Recover from BACKUP then my tablet restarts and it turns to BOOTLOOP and repeatedly saying NO COMMAND.
Click to expand...
Click to collapse
Why is it, when I do this, my tablet can't be detected by the software? I'm stuck on recovery mode. When it's on the blue logo, still does nothing.
I can only see my device when I look for it on Device Manager under Android Phone. Why is that? It doesn't show the "Other Devices". I've installed the driver but to no avail, still fails me. Please help. Thanks!
Your Android device is stuck on bootloader screen? When you boot after rooting or installing a custom ROM on your device, you only see the big, dull logo of your manufacturer? Don't panic as this is normal and understandable. During the root or installation process, an error occured and ruined:silly: your entire operating system. When you install ROMs, you have to delete the current operating system, and if an error occur, it will terminate any installation done on your device, which leaves your device with came-with-box software components:crying:, which in this case the bootloader. It got stuck on the bootloader screen because your device has no available system to boot into. So the solution is simple:
Case #1. In case you've installed a recovery and have backed up your system, boot into recovery and restore it.
Case #2. If you haven't installed recovery, search through the internet for recovery installation tutorial for your device, make sure to search by the model e.g.GT-P5200 not the name e.g.Samsung Galaxy Tab 3. Boot into recovery and wipe everything exists on your hard disk. Transfer the ROM you want to install from your PC to the device turned on and with the recovery booting in, so the PC can access the device, or else it will be in accesible even if plugged in via USB cable. After that install the ROM you transfered to your device, and now it will boot.
Sorry that I couldn't be more informative, this is how far i can go, but if you have any questions, just quote my post, and I'll be in response.
See ya later!:fingers-crossed:
Good evening, I have in my hands a smartphone lg p778g does not pass me the logo to light following a simple copy of the folder whatsapp internal memory to the microsd (it was blocked after you copy and to restart it and did not initiate more ... it stays in the LG logo when turned on and there does not pass.
I tried to hard reset with vol (+ or -) buttons + home + power but rather than get out the menu of recovery I get the doll android slept with a triangle exclamation and there is no way to enter the menu that tightening no buttons.
Then I looking for information online found the utility tool flash, did all the steps as marked, I installed the drivers perfectly, the PC detects me the phone without problems, but always in the middle of the update (put the mobile mode s / w upgrade ) 50% program lg cancel the process by saying that there has been an unknown error and try try again by disconnecting and connecting the mobile, but no way, I give retry to to try again and again it hangs at 50% and I jump the error screen again.
I wonder if there is some other program where you can do the hard reset this phone than by the official LG utility, or by microsd.
The operating system used is Windows 7 64-bit, disable the Windows firewall and antivirus and run as administrator utility tool flash lg 2014, but always the same. I also tried running the utility lg mobile support tool directly to you directly seeking the most updated for lg p778g firmware, but it's the same as using the lg flash tool 2014, the 50% of the upgrade stops and gives me the message error.
A greeting and I hope you can help me, I need the phone !!
We'd need someone with a p778g. The problem may be be caused by the special branding of the phone, or an encrypted bootloader. Or the internal flash got completely cleared, partitions and baseband rom, which means a full brick. Otherwise flashing stock in D/L mode should work, even if anything else fails. But this goes mainly for LGs official tool working online. With the LG Flash Tool 2014 i had also problems.
I think both tools have to ways to perform the unbricking. Either with the phone put in D/L mode by the user (if Fastboot don't work on the PC), or by recognizing the phone (but with a still running system) via ADB, then auto-switching to Fastboot. And you should also be able to attach the phone when it's already in Fastboot mode. The latter methods don't work on both my systems under Win10. When my desktop pc had been upgraded to 8.1, i performed all servicing of the L9 with my netbook, which was still on Seven.
My last unbrick was months ago, and i don' t know what happens at 50%. It's something important, and knowing it may help to understand the nature of the problem(loss of contact between phone and pc before the actual process starts, errors during flashing...).
It could be like this:
-phone seems to get recognized by driver&tool, that is good
-image gets downloaded(only with the official tool)
-image gets temporarily extracted on the pc(both online and offline). I fear that by completing the extraction the 50% mark is reached, and that no actual writes to the phone can be performed.
And LG's stock recovery, which calls itself "service mode" or "s/w mode" can be mistaken for D/L mode. I'm talking about the D/L mode, which is also present with a custom recovery, but theoretically D/L mode, S/W mode and Fastboot could be used for unbricking
lecorbusier said:
We'd need someone with a p778g. The problem may be be caused by the special branding of the phone, or an encrypted bootloader. Or the internal flash got completely cleared, partitions and baseband rom, which means a full brick. Otherwise flashing stock in D/L mode should work, even if anything else fails. But this goes mainly for LGs official tool working online. With the LG Flash Tool 2014 i had also problems.
I think both tools have to ways to perform the unbricking. Either with the phone put in D/L mode by the user (if Fastboot don't work on the PC), or by recognizing the phone (but with a still running system) via ADB, then auto-switching to Fastboot. And you should also be able to attach the phone when it's already in Fastboot mode. The latter methods don't work on both my systems under Win10. When my desktop pc had been upgraded to 8.1, i performed all servicing of the L9 with my netbook, which was still on Seven.
My last unbrick was months ago, and i don' t know what happens at 50%. It's something important, and knowing it may help to understand the nature of the problem(loss of contact between phone and pc before the actual process starts, errors during flashing...).
It could be like this:
-phone seems to get recognized by driver&tool, that is good
-image gets downloaded(only with the official tool)
-image gets temporarily extracted on the pc(both online and offline). I fear that by completing the extraction the 50% mark is reached, and that no actual writes to the phone can be performed.
And LG's stock recovery, which calls itself "service mode" or "s/w mode" can be mistaken for D/L mode. I'm talking about the D/L mode, which is also present with a custom recovery, but theoretically D/L mode, S/W mode and Fastboot could be used for unbricking
Click to expand...
Click to collapse
If i was you:
1) Enter in bootload mode using LELUS Method
2) Flash a TWRP 3.0.2 recovery
3) In TWRP recovery format all partitions
4) Install a custom rom
5) Enjoy
I'd appropriate it, if anyone would be willing to help me out with my issue.
I have a LG G2 D801, 32GB.
Had it ROOTED, TWRP Recovery, and Lineage OS 14.1 running perfectly just fine. Until I recently tried to Flash Lineage OS 15.1, which then caused my phone to completely go into a black screen with a dead Android Robot having a exclamation point in a red triangle coming out of it's belly.
Yes, I'm able to get into: Android System Recovery <3e> LRXX22G
- Tried, Reboot System Now and it loops right back into the Android System Recovery <3e> LRXX22G screen. (so that's a dead end)
- Tried, Wipe Cache Partition, then Reboot System Now and it loops right back into the Android System Recovery <3e> LRXX22G screen. (so that's a dead end)
- Tried, Wipe Data/Factory Reset, then Wipe Cache Partition, then Reboot System Now and it loops right back into the Android System Recovery <3e> LRXX22G screen. (so that's a dead end)
- Last but not least, leaving me with the only real option I have left to help fix my phone is the, Apply Update From ADB. (Yes, I tried that one too) Which is why I need your help!
Here's a quick scenario of what happens after trying that last option. (Apply Update From ADB)
-Basically my phone then asks me to ADB Sideload files.
-I connect my phone to my PC. (Windows 7, x64)
-Check my Device Manager to see if it's fully connected, but my D801 connects each time under SAMSUNG Android Phone - AndroidNet Sooner Single ADB Interface. (which I know has to be wrong)
-I go into my CMD Prompt, to access my installed ADB Shell, to search for attached ADB Devices. (Yes, it sees my phone as: LGD801cb55c4e4 sideload)
-I proceed to try to sideload a ROM and after about 30% Signature Verification, Fails causing my D801 to Abort Installation. (no matter what I throw at it, IMG/KDZ/TOT files fail as well.)
Now when it comes to trying the methods listed in: https://forum.xda-developers.com/showthread.php?t=2432476 to Flash Stock Firmware, I simply can't because my D801 doesn't connect to my PC in Device Manager under Ports or QHSUSB_BULK. (it connects each time under SAMSUNG Android Phone - AndroidNet Sooner Single ADB Interface.
I've also tried SRKtool_2.1_droidth which ends up leaving me at another dead end.
If you have the time please help, and or point me in the right direction.
I've already installed the needed drivers:
qualcomm-driver
adb-setup-1.4.3
LGMobileDriver_WHQL_Ver_4.2.0
Downloaded all the corresponding files to my PC for my D801:
Firmware Files (KDZ & TOT also Extracted)
LG Flash Tool 2014 & 2015
SRKtool_2.1_droidth
Megalock DLL File
D801 DLL File
LGUP
Silly suggestion perhaps, but after freaking out for about an hour when this happened to me I ended up realizing I could reboot to TWRP using the hard keys. Honestly, I only mention it because I was trying everything else too. If you didn't already try it (I didn't see it in your description) I think it's the power key and volume down key while it's off and as soon as you see the splash screen, release them both and immediately repress and hold them both until you see TWRP. Just a thought.
I loved that phone!
Sent from my [device_name] using XDA-Developers Legacy app
Just tried your technique @C-Tec. Thank you. But that only brings up the Factory Data Reset Screen (to Erase all user data & Restore default settings) instead of the TWRP Recovery screen. (so that's a dead end)
Because, after selecting Yes, Erasing data and Restoring default settings, my phone reboots in to the same loop I started from, as if I never did anything to remedy the situation.
Update on my progress:
-So I was able to get in to Download Mode. (holding the VOLUME UP button, while the phone is off)
-Followed by the Firmware Update Screen after plugging my phone in to my PC via USB. (which then read my phone as - LG Mobile USB Serial Port. (COM8) under Ports in Device Manger)
-I then Flashed the D801 Stock Lollipop KDZ. (by using the LG Flash Tool 2014)
-Waited for the progress bar to completely fill to 100% and BOOM! I fixed my problem.
-Android Lollipop running like NEW. (that's 2014 NEW :crying
-Now to retry Lineage OS 15.1.
Here's a helpful Video Clip, to understand how to use the Flash Tool. -
Just search for: LG G2 - Fix LG Logo Stuck/ Boot Loop Fix / Flash Firmware - EASY METHOD in YouTube.
Being that I'm low ranked I cant post any links just yet, sorry.
I even went out of my way and ordered a LG V20 off of Swappa, which arrives tomorrow. Due to this issue.
Hi all,
Well, operator error is definitely at fault here... I made a series of mistakes that got me to where I am now. All I intended on doing was repairing my dad's tablet which was running atrociously slowly. I tried to follow some steps, but improvised as I was getting errors and obviously ended up making things a lot worse...
Now tuning on the tablet will directly go to a command line interface with a long series of errors and these are the last 2 lines:
Rich (BB code):
blkD :HardDisk - Alias (null)
PciRoot (0x0) /Pci (0x17,0x0) Ctrl (0x0) /HD(14,GPT,80868086-8086-8086-8086-000000000008,0x646828,0x16D47D8)
blkE :BlockDevice - Alias (null)
PciRoot (0x0) /Pci (0x17,0x0) Ctrl (0x0)
Press ESC in 1 seconds to skip startup.nsh, any other key to continue.
Shell> _
In this state it cannot be interacted with and won't be detected by my PC over USB.
This happens for normal, recovery and bootloader modes. The only mode that I can access is DNX mode but attempting to boot droidboot will result in the same command line UI described above, including when trying to restore the BIOS using the PC executable (which I assume needs to enter fastboot mode, which it can't do...).
What can I do now? Any way to get anything working in the above screen or through DNX?
I'm thinking that a partition was corrupt in addition to me wiping the ESP is causing this. Maybe it's possible to completely format and setup all the partitions and start from scratch again? How can I flash esp.img when all I have access to on the tablet is DNX mode?
Detailed history below...:
HISTORY
1)
The tablet is a Lenovo Yoga Tab 2 1050F. It was running very slowly to the point where my dad just didn't bother to use it. I thought it would be wise to factory reset it as a first step. There is no option to do so within the Lenovo skin of Android so I started by going into recovery mode and performed a factory reset from there.
After it rebooted, the Android UI would loop back to the language selection after connecting to a WiFi network and I would get "Unfortunately Google Play Services has stopped." error message. It would just loop through the Language Selection > Connect to WiFi network pages over and over.
2)
Having installed CM on my old S3 back in the day, I thought I could go about the same process and flash a gapps ZIP file in recovery mode. That didn't work, I got an error because the zip was unsigned.
I thought I could install TWRP to flash unsigned zips, reinstall Gapps and get the tablet passed the Android UI loop.
3)
I followed this guide on XDA to install an unofficial TWRP (which involved unlocking the bootloader). It didn't work because I couldn't flash over ADB (because the tablet couldn't allow Developer Mode since it was stuck in the Android UI loop). So I flashed as many files as I could in fastboot.
I eventually flashed the TWRP recovery.img but that didn't work : when turning on to Recovery mode it would just go back to the bootloader screen.
4)
I thought I must have screwed up something up so I tried to restore the BIOS using an executable I found but I realized the tablet was already upgraded to Lollipop and the only BIOS restoration exe was for Kitkat. Sure enough it got even worse and I could no longer boot Android.
5)
I still had bootloader and fastboot though so I followed a guide to restore the tablet to the original OS (which ironically I already downloaded before trying to get TWRP but forgot about and didn't unpack). I set up Intel Platform Tools but the flash process didn't work because it went to droidboot and then lost USB connection. On the Intel program it would just stay stuck at 20% Wiping ESP. It would time out twice and then give me a final error message.
6)
So I thought to explore the flash.xml file provided to see if I could do the steps manually. I knew it was stuck at wipe ESP because in droidboot it couldn't get commands from PC. So I went into fastboot and wiped ESP manually myself! Little did I know how foolish this was to do because I was simply unable to flash the provided ESP.img again. Following this I lost access to the bootloader.
7)
I found a guide to restore a bricked 1050F here on XDA but it needs droidboot which now goes to the command line UI described at the top of this post. When attempting to restore the kitkat BIOS again, droidboot is also needed which results in the same cmd UI.
8)
Which leads me to where I am now which is that the tablet doesn't boot to: normal, recovery, bootloader/fastboot or droidboot. Which is why I am now asking for help. What can I do?
I'm thinking that a partition was corrupt in addition to me wiping the ESP is causing this. Maybe it's possible to completely format and setup all the partitions and start from scratch again? How can I flash esp when all I can get access to is DNX mode?
Thanks for reading this far and if you have any more ideas, please let me know, thanks in advance.
Hi, would anyone like to weigh in on this issue?