kinda of a new at this. basically my tablet boots with asus logo and top left says "the device is UnLocked"
tried to flash cyanogen mod and put some wrong files.
i know its bricked but cant do much. Vol- + Pwr doesnt get me anywher
Vol+ + Pwr makes some recognition on my computer but cant do much. like fastboot wont recognize as a device.
pls help\
UPDATE: Got it to go in APX mode. and got drivers installed. dont know whats next...
thanks in advance
Few questions first... (I am an Android n00b, but have had issues and flashed custom ROMs about 9 times now.)
Did you make sure to see if the device was properly detected in your OS of choice beforehand? Installed all the software to do so?
Did you install either CWM or TWRP to the device?
Make a recovery in case of issue?
I followed the topic (in this very forum) about flashing. I had some issues being new and all, but got it right... BEFORE I did an actual flash.
[GUIDE] TF300T Unlock/Root/Flash for Factory JB Devices (newbie friendly)
I am using the latest TWRP instead of the guides CWM advice. Due to CWM failing to create a backup for me. I felt not having a backup plan, was something similar to going to a redlight district without a rubber. Which means... What if something goes wrong, how will I fix it?
Does the device detect? Can you move files to the device from your computer?
techknewz1 said:
kinda of a new at this. basically my tablet boots with asus logo and top left says "the device is UnLocked"
tried to flash cyanogen mod and put some wrong files.
i know its bricked but cant do much. Vol- + Pwr doesnt get me anywher
Vol+ + Pwr makes some recognition on my computer but cant do much. like fastboot wont recognize as a device.
pls help\
UPDATE: Got it to go in APX mode. and got drivers installed. dont know whats next...
thanks in advance
Click to expand...
Click to collapse
Hey there, just curious as to how you managed to 'put some wrong files', what exactly did you do to achieve this?
If you can still get into recovery and you have fastboot hooked up, you can proceed to either:
re-flash the correct CWM version if your recovery is broken, or
upload the CyanogenMod package you want to install to your device and simply wipe & flash!
I don't recommend installing last week's nightlies, rotation is still broken. Not sure as to what version last worked.
Good luck!
Xynergy said:
Hey there, just curious as to how you managed to 'put some wrong files', what exactly did you do to achieve this?
If you can still get into recovery and you have fastboot hooked up, you can proceed to either:
re-flash the correct CWM version if your recovery is broken, or
upload the CyanogenMod package you want to install to your device and simply wipe & flash!
I don't recommend installing last week's nightlies, rotation is still broken. Not sure as to what version last worked.
Good luck!
Click to expand...
Click to collapse
So here is what happened. Basically i tried flashing files and put it for the wrong tablet. Now i can only get into apx mode and fastboot doesnt recognize it and neither does adb recognize it.
Related
Hi! I have a bricked ZTE Libra (Sapo A5 in Portugal) and no mather how much I search for solutions I only seem to make things worse, so I was hoping someone here could help me.
Things started to go wrong after flashing a CyanogenMod rom. Everything worked except two things: I couldn't use anything that required my SIM card (so no phone or messaging) and I could not access the recovery screen (clockworkmod).
Without the recovery screen, I turned to ROM Manager but since it uses clockworkmod to do its work it didn't help.
Then I started trying other ways to recover my phone, until I tried ADB which allowed me a shell in my android. But then I broke it all by doing "wipe system" which cleaned my system of everything that was still working and left me with an expensive brick.
Now all I can do is boot until I see the green droid. If I don't press the volume buttons it goes into "device" mode and I can see it listed under "adb devices" but have no idea what to do with it.
If I press the volume button down to go into recovery mode it keeps flashing but never really goes anywhere.
If I press it up to go into the bootloader it stays the same and the only thing I can use to tell me something is different than the normal mode is that lsusb reports the vendor as "Google Inc." instead of what it reports in normal mode: "ONDA Communication S.p.A.".
With this I'm not even sure if I can get to the bootloader or not, but even if that is the bootloader, I have no idea what to do with it that might help me recover my phone.
By the way, I'm trying all this on Linux, although I could try solutions in Windows if required.
Can anyone tell me what can I do in this situation?
Ok, maybe my first post wasn't that easy to answer, so I'll make a simpler question to see if someone can help me.
What can be done at my android's bootloader? What is it for and what tools do I need to use to do it?
You could try installing ClockworkMod recovery using wbaw's guide here http://forum.xda-developers.com/showthread.php?t=1319257 Once that's installed you should be able to flash a new rom with it.
In bootloader mode you can flash a new kernel or recovery image using fastboot.
If you follow that guide that I wrote & Amphoras linked to then you should be able to get a working clockworkmod installed and then you can use that to flash a working rom, or restore a backup.
Thank you both, I'll try what you said as soon as I can and then I'll let you know if it worked!
Ladies and gentleman, today a miracle happened, my ZTE came back from the dead!
Apparently the problem was that I installed some GEN2 applications on my GEN1 model.
I found this while reading the tutorial you suggested, after which I upgraded my ZTE to GEN2 which allowed me to slowly recover everything else.
So, I have to say, thank you very much, and I hope I won't need your help again anytime soon! xD
ok so i have a pretty big problem and very minimal experience with flashing and rooting. Reading and studying many many forums i have peiced together what i have done wrong to do brick my tablet. So to begin a few days ago i managed to wipe my stock recovery and flashed a non existant one, reason being is i didnt download a recovery and unzip it in the required folder. the following day i had it rooted, that was successful. i installed an app from the android market which required root access and a reboot. It is now in bootloop on the "Asus Inspiring Innovation Persistant Perfection" Recovery results in the "Dead Andriod" screen. i have tried flashing using easy flasher but i cant get into APX mode to do so. if i exicute apx mode and plug the usb into the pc i dont get a response, but if have the cable already plugged in and exicute apx i hear chimes and i get "win 7 apx drivers not installed" i tried easy flasher and successfuly flashed WW_epaduser9_2_1_27UpdateLauncher asus stock rom however it still stuck in bootloop. i tried the recovery feature that came with easy flasher but that still result in bootloop when i boot from recovery. i have tried many recovery mods and none seem to work. im doing something wrong i just need someones help getting me out of this i dont want to make anymore mistakes. i have done enough damage. im taking this as light as possible, im a noob i watched the xda noob video and i read a t101 guide on a thread here on this website. many thanks for caring about a strangers issues.
asus tf101 S/N :B60KASO41231
ICS 4.0.3
9.2.1.27
rooted stock rom
audiphur said:
ok so i have a pretty big problem and very minimal experience with flashing and rooting. Reading and studying many many forums i have peiced together what i have done wrong to do brick my tablet. So to begin a few days ago i managed to wipe my stock recovery and flashed a non existant one, reason being is i didnt download a recovery and unzip it in the required folder. the following day i had it rooted, that was successful. i installed an app from the android market which required root access and a reboot. It is now in bootloop on the "Asus Inspiring Innovation Persistant Perfection" Recovery results in the "Dead Andriod" screen. i have tried flashing using easy flasher but i cant get into APX mode to do so. if i exicute apx mode and plug the usb into the pc i dont get a response, but if have the cable already plugged in and exicute apx i hear chimes and i get "win 7 apx drivers not installed" i tried easy flasher and successfuly flashed WW_epaduser9_2_1_27UpdateLauncher asus stock rom however it still stuck in bootloop. i tried the recovery feature that came with easy flasher but that still result in bootloop when i boot from recovery. i have tried many recovery mods and none seem to work. im doing something wrong i just need someones help getting me out of this i dont want to make anymore mistakes. i have done enough damage. im taking this as light as possible, im a noob i watched the xda noob video and i read a t101 guide on a thread here on this website. many thanks for caring about a strangers issues.
asus tf101 S/N :B60KASO41231
ICS 4.0.3
9.2.1.27
rooted stock rom
Click to expand...
Click to collapse
i finally got easy flasher to work, installed apx drivers manually updated device booted into apx mode ran easy flasher and got me out of bootloop, thank you.
audiphur said:
i finally got easy flasher to work, installed apx drivers manually updated device booted into apx mode ran easy flasher and got me out of bootloop, thank you.
Click to expand...
Click to collapse
Can you post the steps please?
mstrblueskys said:
Can you post the steps please?
Click to expand...
Click to collapse
Try this:
Open page with EasyFlasher
Download EasyFlasher
Restart your device into APX (power off than power on while holding volume up - screen will turn black and it will look like off)
Connect your tablet to windows computer. If you already have APX drivers just continue with next step. If don't, windows probably show you info that they didn't find proper driver. Just download APX driver (link on Easy Flasher page), open device manager on windows, right click on APX (it will have exclamation mark next to it) and choose update driver and select manual location to location where you extracted apx drivers.
Download the latest ASUS stock firmware (link also on Easy Flasher page)
Choose Flash Asus stock zip / Unbrick and select location of downloaded stock
When finished, click on flash button in Recovery area.
reboot and pray
Hey folks,
once there was a little boy who was glad to own a new Transformer, but after he made a mistake, the little boy thought his beloved Transformer transformed into a pretty pricey paperweight (Oh, by the way the "little man" was me :crying.
The following lines are telling the whole story.
DISCLAIMER
I am in no way responsible for what you do with your Transformer, even when you are following these (my) instructions.
There is always the risk of making it worse and this risk is completely down to you!!!
(Because it worked for me, I dont guarantee it will work for anybody else.)
Precondition:
- TF300T
- unlocked
- rooted
- CWM Recovery 5.8.2.0 Touch
- Stock ICS
What I did:
Flashing the stock rom from ASUS via CWM.
What happend:
My Transformer was stuck in a recovery loop, which means it started, the asus logo appeared on the screen and instead of starting Android, CWM started.
The Problem:
- The Transformer wasnt able to start...
- Fastboot didnt work. If I tried to get into fastboot mode the message:
"The Device is Unlocked.
Android cardhu-user bootloader <2.10 e> released by "ww_epad-9.4.3.29-20120511" A03
Checking for android ota recovery
Booting recovery kernel image"
appeard.
- ADB didnt recognized my device
- Wipe, format, etc in CWM didnt work.
So I managed to get out:
- Installing Transformer Prime drivers. Universal Naked Driver 0.7 http://forum.xda-developers.com/showthread.php?t=1766220 and/ or TransformerPrimeDriver http://downloadandroidrom.com/file/TransformerPrime/drivers Choose one or take both (worked not the first time, but after a few tries Windows recognized my TF300T as ASUS Prime ADB device.)
- ADB still didnt work.
- I found & downloaded "WSG_UnBricker_TF300T_V1.0.2.zip" http://www.4shared.com/zip/7XYW-4c4/WSG_UnBricker_TF300T_V102.html to my PC(Google will help. You also can choose and try the original one from MasterZen88, but I chose the other one)
- after extracting I started the WSG_Unbricker.bat on my PC and started the ADB Shell.
- There I did the commands from DiamondBacks' Option 1a and rebooted the Transformer.
- After doing so my Transformer stucked on the ASUS Screen.
- I pressed Power till the screen went black.
- Then I hold Power + Volume Down. Then I chose Fastboot Mode. On my PC I started WSG_Unbricker.bat again. Here I started "Install Menu" and tried to install recovery, boot, system, all... Did a few restarts with my Transformer and repeated this step. After a few times I was able to start into CWM Recovery 5.5.0.4 instead of the 5.8.2.0 in the beginning.
- Transformer in CWM Recovery I opened cmd out of the WSG_UnBricker-folder and did the command: adb devices. My Transformer was RECOGNIZED!
- I downloaded cm9.1.0-tf300t.zip http://get.cm/?device=tf300t, renamed it into update.zip (after all maybe not necessary )
- put this update.zip into the same folder you started your cmd out of.
- Then I did the command: adb push update.zip /sdcard/update.zip
- After the transfer was finished I was able to flash the update.zip via CWM Recovery.
- Now I rebooted and watched my Transfromer booting into Android! :highfive:
I m not sure ir this story really helps anybody.
I m not sure if even anyone reads this lines, but maybe I could help another little boy
Ok, I don't test, because I already use TWRP, but it will be good if you could insert the links for all of your different files so that the members can use your method correctly.
Thanks.
What ROM were you on when you soft bricked? CM9/10 or a stock JB? Also, did you upgrade to the OTA JB when you first got it?
timmytim said:
What ROM were you on when you soft bricked? CM9/10 or a stock JB? Also, did you upgrade to the OTA JB when you first got it?
Click to expand...
Click to collapse
don't think he has since he was able to install CM
timmytim said:
What ROM were you on when you soft bricked? CM9/10 or a stock JB? Also, did you upgrade to the OTA JB when you first got it?
Click to expand...
Click to collapse
Hey,
I was on stock ICS (unlocked bootloader + rooted) and flashed the stock JB via CWM.
Now I m on CM 9 and thinking of updateing to CM 10 because the ICS bootloader isnt affected by this update (at least I think so )
Droid_1 said:
Hey,
I was on stock ICS (unlocked bootloader + rooted) and flashed the stock JB via CWM.
Now I m on CM 9 and thinking of updateing to CM 10 because the ICS bootloader isnt affected by this update (at least I think so )
Click to expand...
Click to collapse
hello mate..same problem with tf201...stuck on asus logo i see you solved your problem..my computer do not recognize my tab when connect it via usb..shall i go into apx mode or how you did this ? because fastboot and abd do not work..cannot boot into recovery and vol+ & power button also dont work ..thx
0din said:
hello mate..same problem with tf201...stuck on asus logo i see you solved your problem..my computer do not recognize my tab when connect it via usb..shall i go into apx mode or how you did this ? because fastboot and abd do not work..cannot boot into recovery and vol+ & power button also dont work ..thx
Click to expand...
Click to collapse
Hello,
when my transformer was stuck on asus logo I was able to go to bootloader so... at the moment I dont have an idea.
But this thread may help http://forum.xda-developers.com/showthread.php?t=1514088 if you didnt read already.
Just want to say thank you.
I Bricked the tf300 by flashing a JB rom and still using a ICS bootloader.
Flashing the cm-9.1 version was a good advice, now i can boot again.
Tank You!
I want to install custom ROM on my Zenfone 5.
Things you should know:
.. Phone OS completely corrupts unable to boot the device (even android logo also not appear)
.. It is not showing charging symbol also when connected to charger/usb
.. Phone never boots into recovery mode (it is just restarting(vibration)! and stay idle)
.. It has TeamWin recovery project that appear after 30 mins of charging (useful!!)
So, can anybody tells me how install custom ROM (http://forum.xda-developers.com/zenfone-5/orig-development/beta-cyanogenmod-12-1-tank0412-t3285392) please don't say boot into recovery mode and do some adb/fastboot commands it is not working (volume up+power or any combination). It is just showing one big red charging bar symbol without charging.. and some times TeamWin which may helpful because it has filemanager and I can browse but I don't know how to install with that.
If you have any ideas please share me..
Thanks
You can put rom on the external sdcard and install it after TWRP booting.
But i think that something wrong with bootloader on your phone so you should try to make unbrick.
tank0412 said:
You can put rom on the external sdcard and install it after TWRP booting.
But i think that something wrong with bootloader on your phone so you should try to make unbrick.
Click to expand...
Click to collapse
Thanks for the answer..
Hard bricked device - Just like it's name, your device is dead. It behaves like a real brick. You can have no operation on pressing the power button.
So we can make a conclusion: soft bricked device can’t be defined as "BRICKED"; the hard bricked device is the real "DEAD & BRICKED", and it can't be unbricked. Sorry for the answer to how to unbrcik hard bricked Android phone.
This is the situation of my phone and whenever I flash a zip file from TWRP I'm getting following error..
"E: Error executing updater binary in zip '/sdcard/.....zip'"
I'm googling this error but unable to get anything(trying some of the one plus one solutions to the similar problem).. Please help me..
wyephani said:
Thanks for the answer..
Hard bricked device - Just like it's name, your device is dead. It behaves like a real brick. You can have no operation on pressing the power button.
So we can make a conclusion: soft bricked device can’t be defined as "BRICKED"; the hard bricked device is the real "DEAD & BRICKED", and it can't be unbricked. Sorry for the answer to how to unbrcik hard bricked Android phone.
This is the situation of my phone and whenever I flash a zip file from TWRP I'm getting following error..
"E: Error executing updater binary in zip '/sdcard/.....zip'"
I'm googling this error but unable to get anything(trying some of the one plus one solutions to the similar problem).. Please help me..
Click to expand...
Click to collapse
It looks like you use TWRP by Knone which is broken a bit. So you should install TWRP by quanganh2627.
Try to flash this package via TWRP:
https://drive.google.com/file/d/0B-Fin8UxrD6PNm1NSDNQQ3JqUkU/view?usp=sharing
It will install a stable TWRP.
tank0412 said:
It looks like you use TWRP by Knone which is broken a bit. So you should install TWRP by quanganh2627.
Try to flash this package via TWRP:
It will install a stable TWRP.
Click to expand...
Click to collapse
Hi! Your zip file successfully installed but after that also I'm getting same error. Is there any file download problem (Checksum or like that) or do I have to restart my phone(No OS installed!)
wyephani said:
Hi! Your zip file successfully installed but after that also I'm getting same error. Is there any file download problem (Checksum or like that) or do I have to restart my phone(No OS installed!)
Click to expand...
Click to collapse
Thanks for your TWRP. I successfully installed custome ROM of this..(http://forum.xda-developers.com/zenfone-5/orig-development/rom-cyanogenmod-12-1-xhook-t3289543) but I'm getting these problems which are nowhere found in any forum
1. Charging stops at 10% never goes beyond this point
2. IMEI missing (seriously !!)
Thanks
wyephani said:
Thanks for your TWRP. I successfully installed custome ROM of this..(http://forum.xda-developers.com/zenfone-5/orig-development/rom-cyanogenmod-12-1-xhook-t3289543) but I'm getting these problems which are nowhere found in any forum
1. Charging stops at 10% never goes beyond this point
2. IMEI missing (seriously !!)
Thanks
Click to expand...
Click to collapse
Try to downgrage to stock rom:
https://drive.google.com/file/d/0BwEWY6gMvYOeelBEQ2J0ckxnRmc/view
tank0412 said:
Try to downgrage to stock rom:
https://drive.google.com/file/d/0BwEWY6gMvYOeelBEQ2J0ckxnRmc/view
Click to expand...
Click to collapse
Yes, I'm trying that but the problem here is I'm unable to flash TWRP now (Run the command prompt - wait for device - phone starts several times but only big red battery symbol without charging/usb cable showing red bar below - boot into installed OS) that's it without flashing the TWRP phone reboots and command prompt still waiting for device even device already booted.
Interestingly now the battery showing 100% directly (I don't know ! whether it is actual figure or something goes wronng!) but still my IMEI is empty and I want to install stock ROM on this device for this purpose.
Note: still power + volume up/down to goto recovery mode not working
Any help appreciated. Thanks!!
wyephani said:
Yes, I'm trying that but the problem here is I'm unable to flash TWRP now (Run the command prompt - wait for device - phone starts several times but only big red battery symbol without charging/usb cable showing red bar below - boot into installed OS) that's it without flashing the TWRP phone reboots and command prompt still waiting for device even device already booted.
Interestingly now the battery showing 100% directly (I don't know ! whether it is actual figure or something goes wronng!) but still my IMEI is empty and I want to install stock ROM on this device for this purpose.
Note: still power + volume up/down to goto recovery mode not working
Any help appreciated. Thanks!!
Click to expand...
Click to collapse
You bricked your device.
You should use unbrick method:
http://4pda.ru/forum/index.php?showtopic=584672&st=460#entry33842670
Good evening! I hope you can help me.
I flashed LineageOS 14.1, but I wanted to go back to EMUI. I made all the wipes and tried to flash different stock firmwares through a forced update (volume buttons + power button), but it never worked. At that point, I read about a guy in this forum who suggested to create a flashable zip with Huawei Update Extractor: I followed the suggestion and tried to flash it with TWRP. No error was given, but when I tried to restart, TWRP told me I had no OS installed. I thought it was strange, so I tried to restart anyway. That's when I got in rescue mode. I can't get into the recovery and I can't use fastboot. What rescue mode shows me is:
RESCUE MODE
Attention!
Please update system again
Update User Guide:
*link*
*android avatar*
Error!
Func NO: 10 (boot image)
Error NO: 2 (load failed!)
Pressing the three buttons, I'm able to force an update. The problem is I can't find a firmware that doesn't get rejected. With Lollipop firmwares, it starts to install, but it fails at 12%. With Marshmallow ones, the installation process doesn't even start.
What can I do to make it work again? I'm very sad because this phone was gifted to me a couple of days ago and I already messed it up. I don't even know how to turn it off.
What can I do to get in fastboot mode? At that point, what should I do to flash the stock firmware? Or maybe do I need to find the first stock firmware ever installed into this phone to make the forced update work?
Please, I need help. Thank you in advance!
P.S. The phone's model is ALE-L21. I live in Italy, so I assume it's a European version.
Did you managed to fix this?
Jhon_Locke said:
Did you managed to fix this?
Click to expand...
Click to collapse
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
ErikChimello said:
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
Click to expand...
Click to collapse
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Jhon_Locke said:
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Click to expand...
Click to collapse
No, it doesn't show anything if I write that command...
I guess mine won't ever boot into the rom because it seems like there's no system installed. I made some researches and found out there are some softwares that let you reflash the partitions IF the phone is recognized as "HUAWEI USB COM 1.0". I'm still trying to figure out how to do it correctly though. I feel like if I do something wrong, then my phone won't probably turn on again.
In your case, you should be able to flash a custom rom without any issue. You just have to be very careful and inform you as much as you can: I don't want your phone to end up like mine?. Anyway, it seems pretty hard to go back to the stock rom, so think about it before you flash a custom rom. Also, make a Nandroid Backup is very important.