Database Info

[Q] ICS update failed

Hi,
I just tried performing the ICS update on my Transformer. However during this process, the tablet showed a yellow triangle with a black exclamation mark in it. I waited for about 10 minutes to see if anything would happen, but it just stayed on this screen. So I powered it down and tried turning it back on, but it just gets stuck on the Asus/Nvidia splash screen on boot.
I have tried holding the power button and volume down and entering recovery mode, however I get the same yellow triangle as I had before. If I wait without going in to recovery I get the option of performing a cold boot or wiping the data on the tablet. If I select cold boot, it just hangs, I have left it there for 10 minutes or so to see if it would work but get nothing. I have also tried wiping the data from this menu then retrying all the steps I have mentioned above, but it still doesn't work.
It is not rooted and I have applied all other updates to it without trouble so far. Is there anything I can do to fix this?
Thanks,
Ryan

I had the exact same problem. Got it fixed. Use the method from this thread: tabletroms.com/forums/transformer-rom-development/1071-asus-transformer-nvflash-stock-3-1-stock-3-2-recovery-roms-unbricking-tools.html

Thanks for your reply. I noticed on that page that it says that if the serial number is BD70 or above (which mine is) do not use the tool. Has there been an update that allows this to be used on the newer units?
Thanks,
Ryan

Hi there!
I got a similar problem yesterday and the error was that a file inside the DATA partition could not be deleted. I noticed when doing a factory reset from CWM.
If you have CWM and you can flash the "super wipe tool" you can fix the problem. Then you re-flash the ROM. I got it working and now I'm on a clean clean clean clean.... clean shiny install
check my threat if you want:
http://forum.xda-developers.com/showthread.php?t=1516204
Hope it helps!

I'm guessing I do not have CWM as I do not know what it is?
Thanks,
Ryan

sh.assassin said:
Hi,
I just tried performing the ICS update on my Transformer. However during this process, the tablet showed a yellow triangle with a black exclamation mark in it. I waited for about 10 minutes to see if anything would happen, but it just stayed on this screen. So I powered it down and tried turning it back on, but it just gets stuck on the Asus/Nvidia splash screen on boot.
I have tried holding the power button and volume down and entering recovery mode, however I get the same yellow triangle as I had before. If I wait without going in to recovery I get the option of performing a cold boot or wiping the data on the tablet. If I select cold boot, it just hangs, I have left it there for 10 minutes or so to see if it would work but get nothing. I have also tried wiping the data from this menu then retrying all the steps I have mentioned above, but it still doesn't work.
It is not rooted and I have applied all other updates to it without trouble so far. Is there anything I can do to fix this?
Thanks,
Ryan
Click to expand...
Click to collapse
Ok, I'm going to help you unbrick your device. But you need to forget everything other people in here have told you. Ok? And just do. Don't question. Just follow the steps.
(1) Go to the following asus webpage, choose android as OS and download your version of the 21 firmware. WW, US, TW, etc.
http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#download
(2) Rename the downloaded zip file to "EP101_SDUPDATE.zip"
(3) Move zip file to a micro sdcard.
(4) Insert microsdcard into the TF.
(5) Turn off TF.
(6) Power on by pressing power button and volume down buttons at the same time. When white texts appear on upper left hand corner, release power button and volume down buttons and press volume up button.
(7) Watch your TF unbricking itself.
(8) Leave it alone to do its thing.
(9) Write me a check for 2,000 yen.

Thanks, that has sucessfully unbricked the tablet.
However if I try to attempt the ICS update again it says checking integrity of firmware file and then says update failed.
Does anyone have any ideas as to why this is happening?
Thanks,
Ryan

british.assassin said:
Thanks, that has sucessfully unbricked the tablet.
However if I try to attempt the ICS update again it says checking integrity of firmware file and then says update failed.
Does anyone have any ideas as to why this is happening?
Thanks,
Ryan
Click to expand...
Click to collapse
Download is corrupted. Have you tried again?

Yes I have, about 10 times and it always comes up with that error.

I had the same failure and had to install .13 and update 3times to get to ICS. Got it from the Unlockr link. Worked great and then rooted with ViperMod.
A clean install is seemingly not having as many issues. Plus I already have an AOKP ICS rom on my phone, so I already know most of the ICS features.

I did try downloading .13 and installing it the same way as I did .21 (putting in on the micro sd and powering on with power & vol - to get into recovery mode), however when I try this I get the yellow triangle and black exclamation mark again, only this time it does not stop my tablet from booting back in to .21.

british.assassin said:
Yes I have, about 10 times and it always comes up with that error.
Click to expand...
Click to collapse
This error comes up when you have a corruption in your stock recovery.
You won't be able to "downgrade" to .13 the way you did with this. Unfortunately, there's no easy way for you to go about this. Here is what you need to do. Yeah, it will be a little long.
(1) Root via nachoroot.
(2) Install CWM via recovery installer. Can be found in the app portion of this forum.
(3) Download the repacked .13 version from the following link.
http://dl.project-voodoo.org/transformer-roms/3.0.x/
(4) Download stock recovery.
http://forum.xda-developers.com/attachment.php?attachmentid=606402&d=1306284085
(5) Flash the repacked .13 version via CWM.
(6) Restart the TF.
(7) Flash the stock recovery.
(8) Restart TF.
(9) Upgrade via OTA. One of the updates will give you the appropriate stock recovery.
Failure to follow my instructions precisely will result in brick.

[Q] LG G3 rebooted into TWRP, won't get out of it now.

Hi I'm new to this rooting stuff but I've been rooted for nearly a year, and had TWRP on my LG G3 as well (I didn't do much with it to be honest).
For some time now, my phone has been insisting on me updating my G3 to a newer version (OTA update). I found out that this update file is located at cache/fota, a file called dlpkgfile, which I cut and pasted to some other folder, and then switched off the option about looking for updates automatically, so that it wouldn't bother me anymore.
I went to the Update Center and it still said "Update Available" like before, most likely because it hadn't yet detected the absence of the file. I thought that I'd clear this "misconception" by clicking install now, only to find it restarting, and then popping up the TWRP screen.
Now I don't know how to get out of this.
I clicked the Reboot button, which gives four options:
System
Power Off
Recovery
Bootloader
I tried all of them, only to see this same TWRP thing pop up.
Please do help me. Thanks in advance.

Hold power button for 10 seconds the will turn off and then start it again
Sent from my LG-P765 using Tapatalk

I think it is trying to flash a file that does not exist. You need to be pretty careful with OTA updates when you have a custom recovery installed.
If the solution above does not work, try wiping cahe and reset. If not, try to backup and then install this backup.
That's what I would do. Hope it helps!

Totally Screwed up my Honor 8

Howdy folks! In need of some urgent help... I'm also not terribly familiar with android as I came from years of using iphones.... Yesterday I did the OTA update to EMUI 5. Everything was fine except bluetooth would fail to turn on...so I tried doing a factory reset in the settings. The reset failed less than 10% in and when the phone rebooted, it seems like only half the OS reset and is totally screwed up (no access to the soft keyboard anymore, etc.).
Reading on how to either rollback to EMUI 4/Marshmallow, I tried using the Huawei Update Extractor after downloading L04 6.0 firmware from the Huawei site ( Honor 8_Firmware_FRD-L04_Android 6.0_EMUI 4.1_C567B122_United States_Nonspecific ).
After issuing the adb command to flash the first file, boot.img, I get a "FAILED (remote: Command not allowed).
I'm a total loss at this point. I'd be extremely grateful if anyone can point me in the right direction in terms of what to do next!

I was in the same position as you. Here is what I did:
Download both the rollback package and the full marshmallow firmware (I used a german one since that is my region, i linked one for the UK version, google your specific model to find them) from the hihonor community website: https://community.hihonor.com/docs/DOC-1752 and read the PDFs that are included in both zips, they contain the instructions to roll back to Marshmallow.
You will need an external SD card and you will lose your data.
In case the steps are not clear enough:
1. Copy the dload folder of the rollback package to the root of the SD.
2. Force update the phone (hold volume up and down at the same time when powering up).
3. Shut down the phone after the force update is done.
4. Delete dload folder of the rollback package and replace it with the dload folder of the full marshmallow firmware.
5. Force update the phone again.

fauxfive55 said:
Howdy folks! In need of some urgent help... I'm also not terribly familiar with android as I came from years of using iphones.... Yesterday I did the OTA update to EMUI 5. Everything was fine except bluetooth would fail to turn on...so I tried doing a factory reset in the settings. The reset failed less than 10% in and when the phone rebooted, it seems like only half the OS reset and is totally screwed up (no access to the soft keyboard anymore, etc.).
Reading on how to either rollback to EMUI 4/Marshmallow, I tried using the Huawei Update Extractor after downloading L04 6.0 firmware from the Huawei site ( Honor 8_Firmware_FRD-L04_Android 6.0_EMUI 4.1_C567B122_United States_Nonspecific ).
After issuing the adb command to flash the first file, boot.img, I get a "FAILED (remote: Command not allowed).
I'm a total loss at this point. I'd be extremely grateful if anyone can point me in the right direction in terms of what to do next!
Click to expand...
Click to collapse
First of all, confirm that your model is the L04 model.
The rollback procedure to MM is the following:
- Download the B300 from here http://www.hihonor.com/us/support/details?DOC_ID=92098
- Put the 'Update.APP' (~80MB) file in a folder called 'dload' in your external storage
- Turn off your phone then maintain all the buttons (Volume+, Volume-, Power) to turn it on.
After the update finishes, check your build number, you should be on B300.
- Now, delete the 'Update.APP' that's in your 'dload' folder
- copy the 'Update.APP' (~3 GB or so) of the B122 http://www.hihonor.com/us/support/details?DOC_ID=89264
- Turn off your phone then maintain all the buttons (Volume+, Volume-, Power) to turn it on.
Let your phone optimize, reformat its partitions.
You should now have MM on B122, you can then update to B162 through OTA.

takichiman said:
First of all, confirm that your model is the L04 model.
The rollback procedure to MM is the following:
- Download the B300 from here http://www.hihonor.com/us/support/details?DOC_ID=92098
- Put the 'Update.APP' (~80MB) file in a folder called 'dload' in your external storage
- Turn off your phone then maintain all the buttons (Volume+, Volume-, Power) to turn it on.
After the update finishes, check your build number, you should be on B300.
- Now, delete the 'Update.APP' that's in your 'dload' folder
- copy the 'Update.APP' (~3 GB or so) of the B122 http://www.hihonor.com/us/support/details?DOC_ID=89264
- Turn off your phone then maintain all the buttons (Volume+, Volume-, Power) to turn it on.
Let your phone optimize, reformat its partitions.
You should now have MM on B122, you can then update to B162 through OTA.
Click to expand...
Click to collapse
Thanks for your replies. I sincerely appreciate it. I tried doing the above and when updating the rollback, it would only read to 5% and when phone rebooted it was in the same state it was before attempting the rollback. Could it be something to do with the SD card? Any other ideas? Thanks again.

fauxfive55 said:
Thanks for your replies. I sincerely appreciate it. I tried doing the above and when updating the rollback, it would only read to 5% and when phone rebooted it was in the same state it was before attempting the rollback. Could it be something to do with the SD card? Any other ideas? Thanks again.
Click to expand...
Click to collapse
Alright now let's try another method to save it.
- Turn off the phone
- Keep holding the volume+ button then plug it to a computer.
- Keep holding the volume+ until you see the honor logo.
- You should now see the eRecovery.
- Choose download latest software and recovery.
This is a video of these steps:
Sent from my FRD-L04 using XDA Labs

fauxfive55 said:
Thanks for your replies. I sincerely appreciate it. I tried doing the above and when updating the rollback, it would only read to 5% and when phone rebooted it was in the same state it was before attempting the rollback. Could it be something to do with the SD card? Any other ideas? Thanks again.
Click to expand...
Click to collapse
Assuming you have successfully flashed the rollback update (B300), I successfully rolled back to B162 by making a "dload" folder on my external SD card, and placing the Update.APP file in there, and then accessing recovery using the pwr+vol (+/-) buttons.. For some reason placing the Update.APP file in the internal storage did not work with the stock recovery, even though the instructions for the rollback ask you to do so. Hopefully this helps.

takichiman said:
Alright now let's try another method to save it.
- Turn off the phone
- Keep holding the volume+ button then plug it to a computer.
- Keep holding the volume+ until you see the honor logo.
- You should now see the eRecovery.
- Choose download latest software and recovery.
This is a video of these steps:
Sent from my FRD-L04 using XDA Labs
Click to expand...
Click to collapse
Thanks again. Doing this gave me a "getting package info failed" in eRecovery.

fauxfive55 said:
Thanks again. Doing this gave me a "getting package info failed" in eRecovery.
Click to expand...
Click to collapse
Not sure exactly why it worked, but I finally got it restored and am running the latest EMUI 5. Thank you so much everyone for your contributions. I owe you folks a beer!

fauxfive55 said:
Not sure exactly why it worked, but I finally got it restored and am running the latest EMUI 5. Thank you so much everyone for your contributions. I owe you folks a beer!
Click to expand...
Click to collapse
I'm in the same situation you were in, command not allowed, rollback not working, dload folder with update.app in sd card not working.
How and what did you do after that ?
Thanks in advance

Place the dload folder/files on the root of the internal memory.

Go look on ModaCo.
There is a guy called Paul O'Brien who I think has some thing to do with Honor in some way.
He will help you sort your phone
Sent from my Honor 8 using XDA Labs

I somehow managed to actually rollback my phone ! I'm starting to feel a lot better.
Bootloader's locked again, though (no more "this device has been unlocked and cannot be trusted")
Only small problem now is I have the "this device was reset" message problem still around.
Read online here on xda that I need to wait 72 hours before logging on again with my new password (I did change it, that must be why)
I'll just wait these 72 hours and see if it works.
Else if you did have this issue too i'd love to hear about it.

Honor 5C Soft Brick / Hard Brick HELP??!!??

Hi, well it looks like i have probably hard bricked my phone. After updating to nougat i decided to do afresh clean install. I wanted my phone to as if i had just bought it and came with nougat/emui 5 installed. So i did a factory reset from within the settings menu. But then i thought i would completely erase everything and start from the latest build before nougat, so emui 4.1.2/ marshmallow. So after wiping all the partitions in twrp and then doing a volume up + power to do complete factory wipe followed by using the three button method to install the B130 UPDATE.APP in dload folder on my sdcard, all worked as expected. The update completed at 100% and then rebooted. So there i am waiting for my phone to boot to start the setup process as i have done dozens of times before...BUT...my phone will not boot to the initial setup wizard. It just stays stuck on the Honor logo pulsing animation for ever and ever and ever!!!!!!
So i do the volume up + power button to get to stock recovery and do factory wipe and cache wipe as well. It works as expected so i reboot and once again use the 3 button method to install the update.app on my sdcard. That works as expected and at 100% says its succeeded and reboots. Once again i wait for it to boot to the initial setup wizard but....ALAS...it stays on that DAMN pulsing Honor logo. Ive tried rebooting it several times, redoing the factory wipe and install several times, but nothing. Ive gone into fastboot mode (volume down + power) to try and flash the boot.img and system.img ive extracted from update.app but get the error message -- remote: command failed -- and the same if i try to unlock bootloader. Obviously its not going to work because my bootloader isnt unlocked and nor can i got in to developer settings to enable oem unlock and turn USB debugging on because my phone wont boot past that bloody honor logo.
The only thing i havent done yet is to use eRecovery but i dont have broadband and i doesnt seem to work over public wifi! So i will go to my friends tomorrow and use their broadband and hopefullly eRecovery will download/restore the latest firmware. The only other thing i can think of is to download the original nem-l51c432B102 that came with my phone when bought, extract the update.app file and replace the B130 i have on my sdcard dload folder at present.
Sorry for such a long post but i wanted to expalin evrything in detail to hopefully resolve my problem without going backwards and forwards with questions and answers and taking for ever.
So ANYONE and EVERYONE who managed to read the whole post, if you have even the slightest idea of how to get my phone working, please oh please share it with me. Also my phone is still under warranty so if i needed to send it to a huawei centre to get it fixed would they do it and do it for free??? because eseentialy all i did was a factory wipe/reset and install a frmware and it goes KAPUT!! thats not my fault right????!!???
Thank you to one and all for any wisdom you can share.

please....please.......help???
So sorry for my original long post people, i simply wanted to give as much detail and info as possible because being vague doesnt help anyone. It seems that might have worked against me.
Please,please any suggestions would be appreciated to the N'th degree! I have tried everything i can think of and i am truly desperate now. I dont understand why i cant get it to work...
I can go into stock recovery and wipe the cach and do factory reset and that works fine, no errors.
I can hold the 3 buttons down to install the firmware package(ive got update.app from B130 build) and that works fine, gets to 100% and says 'success' and then reboots, with no errors.
But either way the phone refuses to boot past the honor logo boot animation and ive left it for hours hoping,praying, it will work after the 32nd time...
I can access fastboot but that is useless because my bootloader is not unlocked and i cant get to developer options to enable 'usb debugging' and 'oem unlock'. So i just get error message 'remote: Command Failed' with any command i type.
But thats madness, i cant comprehend why it wont boot because everything seems to work!?!
There has to be a way to get my device functioning again.
I am pulling my hair out, i am at a complete loss, it doesn't make sense. PLEASE ANYONE ..... please help....
Thanks HONOR-able enthusiasts for any help, no matter how small!

Need help with Samsung Tab 7.7 (SCH-I815LSV)

I'll give you the whole story so bear with me. First off, I'm very new to the Android OS and tinkering with phones and tabs. I'm a computer network administrator and pc mechanic. I'm mainly a hardware guy though, no programming experience at all. But I'm not afraid to jump right into the inner workings though, especially if it's already broken.
And that's probably why I find myself in this position today with this device.
I recently bought this Tab 7.7 to use as a display for my new drone. When it arrived I tried to download the flight control app and it refused to install. No error messages, it just did not install. In looking, the unit was on Honeycomb 3.0. My guess was it was WAY behind in upgrades so off I went to make it bigger and better. I downloaded a zip file for Lollipop 5.1 onto my SD card and was able to load that. Upon reboot I had a screen and an OS. I went into settings and saw where it had upgraded. Success, right? Well, then I went into Wi-Fi settings to add my network. The keyboard would not come up on screen. So I did a bit more research and tripped over the fact that I needed to also load a GAPPS file to add the apps and drivers back. THAT is when I went down the rabbit hole.
The install did not go well and I somehow wound up with no OS at all. Probably after thinking I was following the correct process of resetting and clearing caches before installing the new files. Then this 3 day journey of learning began. I have downloaded Odin, Notepad++ to edit files, Minimal ADB and Fastboot, Samsung KIES and all manners of ROM builds and GAPP files. As of this moment I have absolutely no OS on the unit. Upon turn on it goes directly into the CWM Recovery v6.0.4.5 screen. I am able to boot it to the download screen and Odin can SEE the unit. But I can't get any further with that program other than seeing the unit listed as detected. I'm not able to get anywhere with KIES. No detection or anything.
Now I'm admitting I messed this unit up. I'm not blaming any written procedure or ROM developer. I'm not stupid but evidently don't know all I NEED to know about this process. So I'm here asking for guidance. I really would like to revive this unit and get it back to where I can use it as my monitor as originally planned. But one step at a time. Please give me the correct steps to do to get an OS reloaded and revive this unit.
I'm thinking that my best bet would be to use a TWRP image file to rebuild it. But I need the step by step process for that to make sure I do it correctly.
MANY thanks for this board and the help AOT!!!
Dave

Being the impatient type as well as a DIY'er, I pressed on with trying to revive it myself. I downloaded TWRP as a zip file and added it to the SD card. Booted and installed from the zip file. Screen said it loaded successfully. I rebooted and tried going into recovery (holding power and volume up) expecting it to go into the TWRP console. Instead it went into the regular CWM Recovery screen. Oh well, another frustrating dead end for me. I'll just set it aside until I get some good instructions from someone that knows what they're doing. Best I do that rather than brick it. I can at least access the recovery screen. Odin sees the unit but I cannot find the right file to load from there.

Okay, I'm truly stopping now. Another dead end. I was able to find a couple of files for restore using Odin. Loaded one and now I boot into Android system recovery <3a> instead of the CWM Recovery screen as before. I tried loading a recovery image from a zip file and it failed signature. That seemed to be telling me the tab is now not rooted. So I downloaded SuperSU to the SD card and tried to load it. No joy, it fails signature too.
Arrrggghhhh.........

Can't even shut it down.

Told you I'm impatient. Now have used Odin and installed TWRP 3.0.2-0. Going slowly now. Taking it one step at a time. This is the first positive step I've had so far in 3 days.
:silly:

Baby steps. LOL
Used TWRP to flash SuperSU. Now the unit is rooted and rebooted to TWRP. I still have no OS on there as of yet. I'm guessing my next step is finding a good stable ROM file and use TWRP to flash onto the tab.

Downloaded OmniROM Marshmallow 6.0.1 (https://androidfilehost.com/?w=file...69dc16313bf0332c8794621c6c7f505edf855e0d499d8) and the Open GApps ARM 6.0 stock file (http://opengapps.org/).
Will try to flash those through TWRP and hope for the best.

Joy...at last. The downloaded OMNI 6.0.1 worked when loaded using TWRP. The GApp file failed. Will try another one to see if it works.
https://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368

Booted to TWRP and was going to install the GApps file. I had left OMNI 6.0.1 on the card too and by mistake selected it. Dooohhh......
I'm an accident waiting for a place to happen. LOL
So, after REloading Android 6.0 I proceeded to load the gapps base file. Reboot and all appears to be going smooth. Apps updating and such. After about 2 minutes I get a message onscreen that unfortunately setup wizard has stopped. Hit okay but the message persists to pop up.
So.....
I guess I'll take a short break then do a wipe and reload of the OMNI and the working gap file and see what happens. At least I got to see it actually boot and let me get into setup. I went to add my Wi-Fi network, added the credentials but it never connected. Something else to look into.
More fun ahead....but at least I'm moving forward now.

A happy camper. Because I was able to revive this tab and because I had the patience to figure it out myself. And my wife swears I have no patience.
LOL
So...the key was downloading Odin and the Samsung drivers on my laptop.
Then download the TWRP.tar file to the laptop.
Boot the tab into download mode by holding power and volume down button. Select yes to continue.
Connect the tab to the laptop with the USB cable. See that Odin can communicate with the tab.
Select AP and find the TWRP file location and start. After it finished, rebooted and since there was no OS installed, TWRP recovery opened.
The next thing was download SuperSU file and drop it onto the SD card. You CAN go ahead and find the correct ROM you want and download the file as well as the GApp file. Drop all 3 onto the SD card.
Then insert it into the tab and select Install. Just be very observant WHICH file you load in what order.
You will need to install the SuperSU, reboot and then install the OS ROM followed by the GApp file.
Select SD card and the SuperSU file. Wait for it to complete then reboot.
After loading SuperSU and reboot, you need to get back into TWRP Recovery program by rebooting while holding power and volume up. This time when you select Install, pick the ROM file first then pick additional files and select the GApp. This way TWRP will first install the OS from the ROM file and immediately load the apps file. Then reboot and you are done!!!
And it took 3 days of round about to figure this out.
LOL
I just downloaded my flight control app and I'm off and running with Marshmallow.
Hope this helps at least one person that is new to this whole process as I was!!!
Dave