Hi ppl!
First, my device failed to get the OTA Update because I deleted some system apps (see my original post).
Then I found this post where another user restored original APKs in /system/apps and managed to manually update to JB by downloading the dlpkgfile in this post.
So I proceed, restored my /system/apps (with 755 permissions), rooted with OTA RootKeeper and SuperSU, placed the dlpkgfile and command files, restarted to fastboot (Power+Vol Down) and entered Recovery mode.
The green android with the blue progress bar went for over 10 minutes, then ... the android with the RED TRIANGLE appeared
After a minute or so the device restarted, an ASUS logo with a blue progress bar ran, but then it got stuck in the ASUS logo.
I'm still able to restart to fastboot (Power+Vol Down), where a message appears:
Code:
Android cardhu-user bootloader (1.00 e) released by "US_epad-10.4.2.9-20120809" A03
, and where I have 4 choices:
1. RCK: Recovery mode, when I select this the Red Triangle appears again.
2. Android: Normal android boot, gets freeze right away
3. Fastboot USB download protocol: Tried using ADB, but don't really know what it is. Here's an image of how the device appear in my Windows PC
4. Wipe Data: Already done this, seems to wipe user data, but still gets stuck on ASUS logo
Some pictures I took of my device: http://imgur.com/I13ou http://imgur.com/Jezpn
I also tried downloading .30 firmware from ASUS website and placing the Zip contents in my SD card, then booting recovery but no luck.
It's pretty awful that everything went so bad, I'm hoping there is a solution.
Anything would be really appreciated!!!
Thanks!
benoror said:
Hi ppl!
First, my device failed to get the OTA Update because I deleted some system apps (see my original post).
Then I found this post where another user restored original APKs in /system/apps and managed to manually update to JB by downloading the dlpkgfile in this post.
So I proceed, restored my /system/apps (with 755 permissions), rooted with OTA RootKeeper and SuperSU, placed the dlpkgfile and command files, restarted to fastboot (Power+Vol Down) and entered Recovery mode.
The green android with the blue progress bar went for over 10 minutes, then ... the android with the RED TRIANGLE appeared
After a minute or so the device restarted, an ASUS logo with a blue progress bar ran, but then it got stuck in the ASUS logo.
I'm still able to restart to fastboot (Power+Vol Down), where a message appears:
Code:
Android cardhu-user bootloader (1.00 e) released by "US_epad-10.4.2.9-20120809" A03
, and where I have 4 choices:
1. RCK: Recovery mode, when I select this the Red Triangle appears again.
2. Android: Normal android boot, gets freeze right away
3. Fastboot USB download protocol: Tried using ADB, but don't really know what it is. Here's an image of how the device appear in my Windows PC
4. Wipe Data: Already done this, seems to wipe user data, but still gets stuck on ASUS logo
Some pictures I took of my device: http://imgur.com/I13ou http://imgur.com/Jezpn
I also tried downloading .30 firmware from ASUS website and placing the Zip contents in my SD card, then booting recovery but no luck.
It's pretty awful that everything went so bad, I'm hoping there is a solution.
Anything would be really appreciated!!!
Thanks!
Click to expand...
Click to collapse
You don't have a recovery to boot into
Sent from my SGH-T989 using xda app-developers app
OK, I found this tutorial about flashing ASUS firmware with fastboot: http://www.theandroidsoul.com/how-to-restore-asus-transformer-tf300t-back-to-stock/
The problem is that the following commands:
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 flash system US_epad-user-9.4.3.30.zip
both produce the error: "Signature mismatch"
I guess it's becaus my fastboot is newer version, since it was actually installed during the JB update, but I'm trying to flash a older .30 firmware.
I gues I will have to wait ASUS releases the new firmware for manual flashing it.
Just guessing...
benoror said:
OK, I found this tutorial about flashing ASUS firmware with fastboot: http://www.theandroidsoul.com/how-to-restore-asus-transformer-tf300t-back-to-stock/
The problem is that the following commands:
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 flash system US_epad-user-9.4.3.30.zip
both produce the error: "Signature mismatch"
I guess it's becaus my fastboot is newer version, since it was actually installed during the JB update, but I'm trying to flash a older .30 firmware.
I gues I will have to wait ASUS releases the new firmware for manual flashing it.
Just guessing...
Click to expand...
Click to collapse
Thank you for posting this. I wanted to try something like this with the new boot loader that came with jb but it appears flashing the older firmware will not work.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
funnel71 said:
Thank you for posting this. I wanted to try something like this with the new boot loader that came with jb but it appears flashing the older firmware will not work.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
You're welcome. So, do you have a clue on how to restore my older bootloader soy I can get back to .30 stock?
benoror said:
You're welcome. So, do you have a clue on how to restore my older bootloader soy I can get back to .30 stock?
Click to expand...
Click to collapse
That is exactly what I'm wanting to know if it's even possible. If I can safely downgrade, I can re-root, but I'm limited on what I can do with a locked bootloader.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
peopole!!! new firmware is out!!!
http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF300T/US_epaduser_10_4_2_9_UpdateLauncher.zip
here is a direct download link!!! US version only!!!
PS: im pushing using
fastboot -i 0x0B05 flash system blob
Click to expand...
Click to collapse
[blob extracted from the above zip]
okay asus animated boot is up and i seem to successfully unbrick my device!!!!
Screens http://imgur.com/a/D7wqI
kindrudekid said:
peopole!!! new firmware is out!!!
http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF300T/US_epaduser_10_4_2_9_UpdateLauncher.zip
here is a direct download link!!! US version only!!!
PS: im pushing using
[blob extracted from the above zip]
okay asus animated boot is up and i seem to successfully unbrick my device!!!!
Screens http://imgur.com/a/D7wqI
Click to expand...
Click to collapse
I don't know you mate..
But I'm so happy for you!! Glad everything worked out well! Cheers!!
Same Here!!!
Flashing the new ASUS firmware unbricked my device!!!!
Please mark this topic as SOLVED
ASUS should really make this process easier.
Thanks for all the support!
Greetings.
soft bricked?
I dont see how this is solved......I have seen some people comment they have no fastboot or recovery,
I tried to do manual update in cwm and when I rebooted with adb all I have is asus boot logo, it also does not say I have an unlocked bootloader,
I have no fastboot no recovery no adb connect all I have is asus boot logo.......volume+-power does nothing vol down + power also does nothing.
how do you flash new firmware without adb or any type of recovery?
uelabs said:
I dont see how this is solved......I have seen some people comment they have no fastboot or recovery,
I tried to do manual update in cwm and when I rebooted with adb all I have is asus boot logo, it also does not say I have an unlocked bootloader,
I have no fastboot no recovery no adb connect all I have is asus boot logo.......volume+-power does nothing vol down + power also does nothing.
how do you flash new firmware without adb or any type of recovery?
Click to expand...
Click to collapse
I have the same problem!!
please need help on this!!
AFAIK you should still have access to fastboot, I'm newbie and never messed up by unlocking the bootloader
It worked!
Thank you so much! I had this same problem with mine and couldn't find an answer anywhere until I found your post.
hmm, I lost my tablet for nearly a month then updated CM10 when prompted having connected to my new wireless. This of course (since the Oct update) put the ROM out of kilter with the bootloader. I didn't have an old ROM on the SDCARD, and old CWM so I couldn't mount an external to get a rom on. I tried pushing a rom to the SD with adb but the drivers weren't going in right and I just couldn't get any joy. I followed this thread to fastboot the current stock JB on in the hope that it would give me a fresh start but it's hanging now at the second (glossy) ASUS logo. I really don't know where to go from here. Is it possible there was a problem with the write?
erasing the memory from the boot menu worked!
biscuits said:
erasing the memory from the boot menu worked!
Click to expand...
Click to collapse
Can you tell me how you erased memory from boot menu - or maybe i understand this in different way.
I have only bootloop and it boots to CWM where i cannot mount any SD card - not internal not external.
Also Vol down + power doesnt work - there is no option to enter fastboot mode....device just bootloops and then enters CWM...
Tried to push through adb but there is no SD card to copy files. Tried different methods but cannot mount any storage...
Thanks JB update
kindrudekid said:
peopole!!! new firmware is out!!!
here is a direct download link!!! US version only!!!
PS: im pushing using
[blob extracted from the above zip]
okay asus animated boot is up and i seem to successfully unbrick my device!!!!
My fastboot is working but it seems that i cannot write anything on my internal sd card.. When i run fastboot -i 0x0B05 flash system blob
My PC shows no erros - it does all the steps. But my tablet freezes and that it - it never unfreezes, i need to power it off.
But fastboot and abd commands work - like reboot or boot into bootloader.
Click to expand...
Click to collapse
I'm kind of screwed and It's not even my mistake, I guess.
I clean flashed the Mahdi Update 25/04 yesterday earlier I had 03/03. In the morning I experienced 2 -3 random reboots and later only one random reboot after which my phone won't boot (bootloop). When i enter bootloader, it automatically selects "start" and boots into system and then reboots.
Once i got the chance and my phone booted fully. But then when I selected reboot into recovery so that i can restore a NAND. IT reboots, the team win logo shows up and then the cycle repeats.
Basically, i don't have access to recovery, my bootloader isn't stable (i.e. it automatically boots without selecting) so I'm unable to flash a stock img as of now. If and when my Nexus fully boots into system it stays the same for about 1 hr if i have any luck. PLz help.
From India. Unlocked Bootloader and custom Rom "Mahdi".
Have you tried using add to boot into recovery? If not also try to getting a logcat when it reboots, those will give us a little more of a general idea of what is actually happening.
First thing don't panic. You can't brick a nexus. You should be able to get into bootloader (volume down + power button) use Wugs Nexus Root toolkit from XDA forum. reload stock ROM in fastboot mode. I have done this lots of time. It's a draw back to being a tinkerer just can't leave well enough alone.
It sounds like your power bottom might be stuck to be honest.
Sent from my Nexus 5 using Tapatalk
nyterage said:
Have you tried using add to boot into recovery? If not also try to getting a logcat when it reboots, those will give us a little more of a general idea of what is actually happening.
Click to expand...
Click to collapse
I managed to somehow get into my bootloader and flashed the following
1. bootloader.img
2. radio.img
3. system.img
4. stock kernel (boot.img)
5. twrp recovery.img
I skipped userdata,img as i need to save my data.
I then went into recovery and did a factory wipe (not including internal storage)
My stock rom booted BUT the setup screen showed up and during the setup process it rebooted again and I couldn't mount my storage to backup.
MY MAIN PRIORITY IS TO COPY THE CONTENTS OF MY SD CARD Before flashing the whole stock image (including userdata)
Now when I type "adb version" in cmd I get Android Debug Bridge Version 1.0.31 but when I type "adb devices" whilst my phone is in fastboot mode, it doesn't list my phone. So i'm unable to "adb pull /mnt/sdcard"
I'm in the same situation with rare access to B/L (based on luck) and Recovery.
Plz tell me what to do when I am able to connect in bootloader mode (fastboot)
IF required I can upload a video showing that what problem I am facing.
scuccria said:
I managed to somehow get into my bootloader and flashed the following
1. bootloader.img
2. radio.img
3. system.img
4. stock kernel (boot.img)
5. twrp recovery.img
I skipped userdata,img as i need to save my data.
I then went into recovery and did a factory wipe (not including internal storage)
My stock rom booted BUT the setup screen showed up and during the setup process it rebooted again and I couldn't mount my storage to backup.
MY MAIN PRIORITY IS TO COPY THE CONTENTS OF MY SD CARD Before flashing the whole stock image (including userdata)
Now when I type "adb version" in cmd I get Android Debug Bridge Version 1.0.31 but when I type "adb devices" whilst my phone is in fastboot mode, it doesn't list my phone. So i'm unable to "adb pull /mnt/sdcard"
I'm in the same situation with rare access to B/L (based on luck) and Recovery.
Plz tell me what to do when I am able to connect in bootloader mode (fastboot)
IF required I can upload a video showing that what problem I am facing.
Click to expand...
Click to collapse
To use adb pull you have to enter the recovery. You need universal naked usb driver 0.73 to make adb work in recovery. If you are on windows 8 or 8.1 you have to turn off the driver signiture enforcement befote installing the universal naked usb driver 0.73
Tapatalk-kal küldve az én Nexus 5-el
El Daddy said:
It sounds like your power bottom might be stuck to be honest.
Click to expand...
Click to collapse
I agree. It's a malfunctioning power button due to several reasons (moisture, drops, etc.). I had this on my Nexus S.
Hi, I have the following problem.
A friend of mine gave me a Honor H60-L12 with a problem with calls. No audio or microphone was working. It was a stock phone, with emui 2.3 and Android 4.4.2
I decided to upgrade it, and downloaded an h60-l12_emui3.0_4.4_5.8.5. That solved the problem, but now, I have a chinese phone, without google play market, or google account, AND, it only works on 2G. No matter what I set on the APN. Same sim card works perfect on another phone.
I tried to restore the phone with differents update.app, with the 3 button method and the local update method, nothing works. Is there anything I can do to get a normal android build on emui3.0 or i bricked the phone?
Thanks a lot
Go to fastboot and flash manually. Check the method to flashing rom through fastboot mode.
For this, you need to download the stock rom(miui 2.3 specificly for your version only, else it won't work) and then you have to extract it using "Huawei Extractor" to get the required files. Then those files can be flashed using following fastboot command.
- fastboot flash recovery RECOVERY.img
- fastboot flash system SYSTEM.img
- fastboot flash boot BOOT.img
- fastboot flash cache CACHE.img
- fastboot flash cust CUST.img
- fastboot flash userdata USERDATA.img
I have tried this and I succeed.
Refer the below link(Its using multi tool):
http://forum.xda-developers.com/honor-6/development/guide-to-stock-rom-method-t3099261
Ashishakp, thanks for reply!!! My phone is now on stock ROM again.
I still have the problem with the chinese firmware version. Is there a way I can update it to the ROM that came with the phone? It was a USA android build, with google market and google account.
Best solution would be EMUI 3.0 International via OTA.
Is that possible?
I have a H60-L12, it was on B116 (but it was marked as B1116 in settings....) and it never got any OTA, even honor suite still say it's up to date. And when I go in "updates" it was like a simple OTA checking screen, not with the blue EMUI logo.
I was previously rooted so the bootloader is unlocked.
So I flashed the latest EMUI 2.3 (B121), only flashing recovery and system in fastboot. And it worked well. Now I have the blue EMUI update screen with the local update button. I put the update.app for EMUI 3.1 (B532) on the dload folder on SD card, used the local update button, it reboot but it say the update failed and come back to the B121.
Then I flashed the recovery and system from B532, but once it reboot it stay on the honor logo (with the powered by android at the bottom). But nothing else, I waited 5 minutes. Hopefully it was not bricked, I go in fastboot mode again and flashed back B121, reboot and all normal again.
I still don't get where is the problem. The 3 button method don't work too, but i tested under B116, it just take the honor screen without any menu to flash update.app.
Hi i currently have Moto XT 1092 retail version and i had got an Android update 6.0 few weeks back. I also had downloaded es flie explorer and accidently i had pulled up a moto app and then i rebooted the system into bootloader. There i deleted the cache and did a factory reset. After the whole process my phone was stuck in the boot lap withe android robot erasing something. I struggled for 2 days to fix it but nothing worked. Here are the steps which helped me overcome this problem and can help others as well.
1. Pls unlock your bootloader if its locked else not flashing of stock will work and it will show pre validation failed, invalid system image or pib signature error.
2. Download stock firmware from filefactory for your device. Mine was 5.1 XT 1092 XML file.
3. Reboot the phone in bootloader and use the fastboot flash method to flash syatem image.
4. The sequence is faatboot OEM lock begin and then rest commands and then end command fastboot OEM lock.
5. Wait for phone to reboot.
6. Automatically after the restart once yu connected the phone will ask for a new system update which is 6.0.
7. The rest is smooth and you will be good to go.
Let me know if you face any problem.
Thx
Gautam
Hi guys.
I gave my nexus 5 to my girlfriend after I bought a new smartphone. I used to run a rom on it. Yesterday she tried to update the official system through the android notification and it's boot looping since then.
I tried to flash a rom again through nexus toolkit, but I don't really remember the android version it has. (Autodetect doesn't work since it's not in debug mode). Any suggestion on what to do? What happens if I select a wrong android build when I am asked " your current android build "? Thanks for support
Choose *any build* and continue normally.
You can manually flash the phone using fastboot commands. Adb commands and debugging are not necessary using fastboot to flash a rom.