Related
tf300t
I was using energy rom, I am 90% sure it was the 4.1 version. (the rom folder was labed Energy.TF300.JB.11.30.2012.zip)
Today i tried to revert it back to complete stock. tried to flash the latest blob from asus' website using fastboot, and when it rebooted, i got the dead android logo, and then nothing. I then followed some other guides from here and such to try to recover it, and now I am stuck with it going straight into TWRP v2.3.1.0 recovery. It then asks me for a password. I can use the adb reboot bootlader command to get back to the fastboot screen, but anytime i try to flash anything, it never takes. the command window says it went, but the tablet just freezes up, until I hold down power until it reboots. Is there any fix for this? Or am I completely and utterly screwed? I will reply asap to any posts, so feel free to ask me for more info if neeed, ill answer the best i can.
Basically you have flashed a 4.2 bootloader onto a 4.1 recovery (TWRP 2.3.1.0)
Sorry but that is a brick.
If you had updated TWRP to a compatible version at the same time you may have been able to save this first ......
As far as I'm aware the only fix is to send it back to Asus for repair.
crap LOL. I got into fastboot, used fastboot erase system, and fastboot erase recovery. Now when i try to click any of the 3 icons, i get unrecoverable bootloader error 0x000000. I can still use fastboot tho when i reboot. anytime i try to flash still, the tablet freezes. when on 3 icon screen, it says at top left:
keydriver not found.. Booting OS
Android cardhu-user bootloader (1.00 e) released by "US_epad-10.6.1.15.3-20130416" A03
It there anything i could do at this point? It is not rebooting into twrp anymore at all. And if i let it boot normally, it just sits at the asus logo. Am i mistaken in assuming it is ready for an OS to be put on it?
rboutin2 said:
crap LOL. I got into fastboot, used fastboot erase system, and fastboot erase recovery. Now when i try to click any of the 3 icons, i get unrecoverable bootloader error 0x000000. I can still use fastboot tho when i reboot. anytime i try to flash still, the tablet freezes. when on 3 icon screen, it says at top left:
keydriver not found.. Booting OS
Android cardhu-user bootloader (1.00 e) released by "US_epad-10.6.1.15.3-20130416" A03
It there anything i could do at this point? It is not rebooting into twrp anymore at all. And if i let it boot normally, it just sits at the asus logo. Am i mistaken in assuming it is ready for an OS to be put on it?
Click to expand...
Click to collapse
Well any chance you had has now gone as you wiped from the bootloader which has now sent a message to the incompatible recovery to wipe and it doesn't understand the partitions so who knows what state it is in now. Sorry.
ok. well than you for your help anyways. everyone says search LOL, but everytime I try to do the things everyone says to they fail for me LOL.
rboutin2 said:
ok. well than you for your help anyways. everyone says search LOL, but everytime I try to do the things everyone says to they fail for me LOL.
Click to expand...
Click to collapse
Unlucky mate. You never know Asus might fix it for free? It has happened.
Hey everybody,
I get my Nexus S from the repair station. They said it can't be repaired because it was "my fault". It wasnt't my fault because I had the problem last year too and they repaired it, f**k Samsung. But now after the "failed repair" I can start my Nexus S but only into the bootloader (when I only press the sleep button it boot into the bootloader too). No Rom or something else like a Recovery Image are installed. So I can only choose these 4 options:
REBOOT BOOTLOADER (yes, it will reboot into the bootloader again)
REBOOT (it will reboot into the bootloader and it says in a red font above the "PRODUCT NAME": FASTBOOT MODE - NO BOOT OR RECOVERY IMG
RECOVERY (see at REBOOT)
POWER OFF (it will go off)
The smartphone is locked and it is the i9023 model. My Laptop can luckily detect my Nexus and the drivers were installed sucessfully.
I tried to unlock the bootloader with the Wugfresh-Tool and the command prompt put it always fail. First the screen with the question "Unlock bootloader?" appears but when I press "yes" it will freze.
I am in real trouble. Hope u guys can help me.
Thanks, AzN MusiQ
have you tried with "manual" unlock? I suppose you're on windows, navigate with terminal in the dir in which you have the fastboot file and the others, place in that folder also the other files you need for flashing. Then fastboot oem unlock, and if it gives you "waiting for device", it seems that your pc doesn't identify well your phone, otherwhise it should work. Try this and, if you can unlock it, from terminal using fastboot flash firstly the recovery, then the image "soju" you find on google official site. Then, when you installed your rom, boot that rom and see if everything works, bootloader boots and recovery stars correctly. At this point you can easily flash what you want
thranduil93 said:
have you tried with "manual" unlock? I suppose you're on windows, navigate with terminal in the dir in which you have the fastboot file and the others, place in that folder also the other files you need for flashing. Then fastboot oem unlock, and if it gives you "waiting for device", it seems that your pc doesn't identify well your phone, otherwhise it should work. Try this and, if you can unlock it, from terminal using fastboot flash firstly the recovery, then the image "soju" you find on google official site. Then, when you installed your rom, boot that rom and see if everything works, bootloader boots and recovery stars correctly. At this point you can easily flash what you want
Click to expand...
Click to collapse
Yeah I tried he manual unlock with the program "command prompt", but it doesn't work
AzN MusiQ said:
Yeah I tried he manual unlock with the program "command prompt", but it doesn't work
Click to expand...
Click to collapse
What does it says? Why it fails?
The screen with the question "Unlock bootloader?" appears but when I press "yes" it will freze.
And so I must put out the battery.
Nobody?
Gesendet von meinem Nexus 7 mit Tapatalk 4
I have asked this question before, but still cant do it
http://forum.xda-developers.com/showthread.php?p=52609305
" http://forum.xda-developers.com/show....php?t=2548530
http://forum.xda-developers.com/show....php?t=1980139
Could someone please tell me how to hide this screen as I am not 100% sure how to do it. Thanks"
I have the adb files downloaded and the logo.bin file, but I am not sure how to map it to fastboot.exe. Do you have to open SDK Manager then do something there?
Thanks again!
Banana4Life said:
I have asked this question before, but still cant do it
http://forum.xda-developers.com/showthread.php?p=52609305
" http://forum.xda-developers.com/show....php?t=2548530
http://forum.xda-developers.com/show....php?t=1980139
Could someone please tell me how to hide this screen as I am not 100% sure how to do it. Thanks"
I have the adb files downloaded and the logo.bin file, but I am not sure how to map it to fastboot.exe. Do you have to open SDK Manager then do something there?
Thanks again!
Click to expand...
Click to collapse
If you mean the Warning bootloader unlocked message then download mototool, Boot into bootloader, connect your device to your Computer and select remove unlocked message. The New Logo should be flashed .
ItzzAce said:
If you mean the Warning bootloader unlocked message then download mototool, Boot into bootloader, connect your device to your Computer and select remove unlocked message. The New Logo should be flashed .
Click to expand...
Click to collapse
Thanks, worked a charm!
So i did a stupid thing and flashed the wrong image when i was installing a new rom, I managed to lock myself out of ADB, TWRP and download mode. I'm in a bit of a pickle right now I've been trying everything I can to fix it, but I managed to do nothing. Is there anyone that can walk me through the steeps to get unbricked.
I've tried recovery through hisuite, but it says my device is not supported. My phone showed up via CMD command (fastboot devices) but not (adb devices). I have no idea what to do?
PLEASE HELP ME!!!
Nixonkai417 said:
So i did a stupid thing and flashed the wrong image when i was installing a new rom, I managed to lock myself out of ADB, TWRP and download mode. I'm in a bit of a pickle right now I've been trying everything I can to fix it, but I managed to do nothing. Is there anyone that can walk me through the steeps to get unbricked.
I've tried recovery through hisuite, but it says my device is not supported. My phone showed up via CMD command (fastboot devices) but not (adb devices). I have no idea what to do?
PLEASE HELP ME!!!
Click to expand...
Click to collapse
Give the all required information like Brand, model number in your post first.
Huawei honor 5x kiwi L24, I can't really acces the phone so finding some information is impossible. My main issue is when I boot it's failing to verify the Boot.img , recovery.img and system.img . I don't exactly know what all information I can give you
Nixonkai417 said:
So i did a stupid thing and flashed the wrong image when i was installing a new rom, I managed to lock myself out of ADB, TWRP and download mode. I'm in a bit of a pickle right now I've been trying everything I can to fix it, but I managed to do nothing. Is there anyone that can walk me through the steeps to get unbricked.
I've tried recovery through hisuite, but it says my device is not supported. My phone showed up via CMD command (fastboot devices) but not (adb devices). I have no idea what to do?
PLEASE HELP ME!!!
Click to expand...
Click to collapse
First open the tool
Select the update.app file
Then press Ctrl and select the imgs you want
And then right click and click extract selected
Like in here
https://up.harajgulf.com/imagef-149893652739431-png.html
-Hope- said:
First open the tool
Select the update.app file
Then press Ctrl and select the imgs you want
And then right click and click extract selected
Like in here
https://up.harajgulf.com/imagef-149893652739431-png.html
Click to expand...
Click to collapse
I have already done that, I've tried flashing it via SP flash tool but nothing, it won't show up. I've downloaded correct drivers and done what I could but my phone shows up as Lemobile android adb interface. It sometimes shows as a disk drive as well.
When I run CMD command (fastboot flash oem info) it shows everything but the recovery.img system.img and boot.img need verification how can I verify them without the debugging bridge active on the phone.
Nixonkai417 said:
I have already done that, I've tried flashing it via SP flash tool but nothing, it won't show up. I've downloaded correct drivers and done what I could but my phone shows up as Lemobile android adb interface. It sometimes shows as a disk drive as well.
When I run CMD command (fastboot flash oem info) it shows everything but the recovery.img system.img and boot.img need verification how can I verify them without the debugging bridge active on the phone.
Click to expand...
Click to collapse
What do you mean sir
Imgs are already verified cause they are official
And you don't need USB debug in fastboot mode
Your device is not has mtk processor so it won't work
-Hope- said:
What do you mean sir
Imgs are already verified cause they are official
And you don't need USB debug in fastboot mode
Your device is not has mtk processor so it won't work
Click to expand...
Click to collapse
I rooted my phone and was running xenon HD on my Huawei honor 5x, in the midst of switching ROMs I accidently targeted a TWRP recovery.img with the ROM and Gapps.
So what my phone dose now is when it powers on it an all green screen with a red box and a blue box. After a second it come up with " recovery image verify failed, please update to verified images." I can enter fastboot&rescue mode and a Huawei erecovery, but when i do try to download the recovery via WIFI it says package failure.
Nixonkai417 said:
I rooted my phone and was running xenon HD on my Huawei honor 5x, in the midst of switching ROMs I accidently targeted a TWRP recovery.img with the ROM and Gapps.
So what my phone dose now is when it powers on it an all green screen with a red box and a blue box. After a second it come up with " recovery image verify failed, please update to verified images." I can enter fastboot&rescue mode and a Huawei erecovery, but when i do try to download the recovery via WIFI it says package failure.
Click to expand...
Click to collapse
What happens when you try flashing through fastboot
Assuming that your bootloader is unlocked have you tried reflashing twrp?
-Hope- said:
What happens when you try flashing through fastboot
Assuming that your bootloader is unlocked have you tried reflashing twrp?
Click to expand...
Click to collapse
I had unlocked my bootloader but some research I was doing says, when you accidently flash wrong images it can relock the bootloader. I lost the original bootloader code and i don't exactly have the box anymore, so getting a new code will be difficult.
Nixonkai417 said:
I had unlocked my bootloader but some research I was doing says, when you accidently flash wrong images it can relock the bootloader. I lost the original bootloader code and i don't exactly have the box anymore, so getting a new code will be difficult.
Click to expand...
Click to collapse
As long as the bootloader says 'phone is unlocked' then its ok
-Hope- said:
As long as the bootloader says 'phone is unlocked' then its ok
Click to expand...
Click to collapse
I'm my case the bootloader has relocked, so in green it say phone status: locked.
Nixonkai417 said:
I'm my case the bootloader has relocked, so in green it say phone status: locked.
Click to expand...
Click to collapse
I've reread your previous post and you didn't mentioned what happens in the cmd window when trying to flash the files?
-Hope- said:
I've reread your previous post and you didn't mentioned what happens in the cmd window when trying to flash the files?
Click to expand...
Click to collapse
(REMOTE: command not allowed)
I have already sent an email to Huawei support, just waiting on a response to see if they can give me another unlock code. If I'm unable to unlock the boot loader again with the codes, what's my options for unlocling the boot loader without Huawei's help.
SO... I did a dumb thing... my friend asked me to install android Q beta on her phone, so I did a sideload.... never checking if it was a verizon phone first... the sideload never errored looked like all was good until the reboot.... operating system corrupt warning... boot to recovery same message... only fastboot with a locked verizon boot loader... did some research looks like I need a firehose... yep.. cant find one... any suggestions or perhaps someone able to help me out?
Did you already try to flash the factory image?
Can be found here: developer.android.com/preview/download#flash (sorry, I cannot post links yet)
First try to flash it without the "-w" flag. If it still does not start, try it with the "-w" flag, but that will delete all data on the phone.
// EDIT if that does not work you might want to head over to the Pixel 3 XL guys here: https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849/page10
I can not flash anything in fastboot due to locked bootloader it always says not permitted. booting recovery or OS always says corrupted with the triangle, recovery does NOT show the android guy, just a warning message. fastboot and qualcomm EDL is all I have available.
LSDemon said:
I can not flash anything in fastboot due to locked bootloader it always says not permitted. booting recovery or OS always says corrupted with the triangle, recovery does NOT show the android guy, just a warning message. fastboot and qualcomm EDL is all I have available.
Click to expand...
Click to collapse
If you are sure that you can't get into recovery I'd suggest getting an RMA for your friend who has been without the device for 4 or 5 days.