hi, after installing the rom manager premium and installing the latest nightly build i no longer can access the recovery. i installed the latest recovery the rom manager said to do, and now i reboot my phone and hold the home button and it just stays in the g1 screen. if i reboot and hold the home button while the phone is connected to usb the phone enters the fastboo g1 bootlader but in the same g1 screen but with red letteres on the corner. i need help. thanks.
fastboot still works but i dont want to have to do all that process again
I would just flash another recovery with fast boot. You won't ned to re root
Sent from my SGH-T959 using XDA App
how do i do this?
djbootleg said:
how do i do this?
Click to expand...
Click to collapse
1: use ADB :
connect ur device with PC , use CMD : type path to ADB folder and then
type : adb shell : enter
type : #mount -a
type : #flash_image recovery /sdcard/recovery.img
reboot
2 : use terminal :
type $Su
type #mount -a
type : #flash_image recovery /sdcard/recovery.img
3 : use Droid explorer tool : download and install newest version
copy img file to sdcard
connect ur device with pc
u'll see a red icon ( Fl ) , click there and show the path to ur img file => ok wait 1' and reboot ur fone
if unsuccessful, u can change ur sdcard and try again !!! ^^
I ran into this issue as well, assuming it's a bug with the latest update of ROM Manager (which I just updated this morning prior to getting this issue.)
Not sure if it had anything to do with the fix but after some fiddling I decided to try reinstalling the ROM Manager recovery (after reinstalling the amon ra recovery from the same app with no success) and it worked, YMMV obviously but that worked for me.
This happened to me too!
Hello,
I was trying this mod: Android Lockscreen mod. Post here.
Using terminal i removed /system/framework/android.policy.odex
When i tried to move new android.policy.odex, it gave me an error and phone rebooted.
After that phone is not responding, it hangs at Galaxy S start screen. Seems like phone is screwed.
Any suggestion please, what can I do now? I am ready to flash everything new, but how can I do that?
Please suggest
Thanks
Is your phone capable of 3 button download mode? If not is your device recognized by your comp? If 3 button is enabled....enter download mode (Vol - + Home + Power) and reflash with desired firmware.
If download mode is disabled but computer recognizes device try 'adb reboot recovery' and try to restore device.
If those do not work might have to send it in.
Good luck, post back with results.
cannot remove files like that and build.prop, framework-res etc.. you need to replace in 1 command.. ie copy from one directory to another using root explorer etc.
or cp in terminal not rm etc.
your only recourse now is to reflash
gold_sprinter said:
Is your phone capable of 3 button download mode? If not is your device recognized by your comp? If 3 button is enabled....enter download mode (Vol - + Home + Power) and reflash with desired firmware.
If download mode is disabled but computer recognizes device try 'adb reboot recovery' and try to restore device.
If those do not work might have to send it in.
Good luck, post back with results.
Click to expand...
Click to collapse
Hi,
Yes I am able to boot into recovery mode,
When I go to Download mode, computer recognizes device,
Can you please tell me where I have to type: adb reboot recovery
Thanks!
Just flashed phone with Froyo xxJPK (Odin). Everything fine again.
Thanks
pinku1 said:
Just flashed phone with Froyo xxJPK (Odin). Everything fine again.
Thanks
Click to expand...
Click to collapse
Glad to hear you got your phone working again. JPK is awesome btw
Sent from my GT-I9000 using XDA App
lgkahn said:
cannot remove files like that and build.prop, framework-res etc.. you need to replace in 1 command.. ie copy from one directory to another using root explorer etc.
or cp in terminal not rm etc.
your only recourse now is to reflash
Click to expand...
Click to collapse
i wrote my solution in the other thread before but just to enlighten you: he could have restored the system easily from the recovery as adb works perfectly well in the recovery ...
I tried to install overcome 8.9 v2.3.1.
but I download the update & not the FULL zip [TEH N00B]
to make things worst I did not backup my system !!!!!!
I can access to the CWM-recovery so im not afraid of my tablet bricked
but the only zip i do have is not complete,
how i can move the the proper file to the tab?
or I need to go the odin route?
in that case what rom should I use?
many thanks
Don't have my tab with me at the moment but doens't the tab show up on a computer if it's in download or recovery mode?
Are you using CWM 5.5.0.4? if yes here is my suggestion...
First you need adb installed on your computer..
Second, you already have overcome full zip file..
This is the step..
Connect your device with computer
From device, Go to recovery - advance menu - mount /system and mount /data
From your computer go to adb terminal and type this
Code:
adb shell "ls /data/media/"
If you can see list of file from your device sdcard, so you make adb work for your device ..
Place your zip file on your path, says on C://overcome.zip and you want to copy the file to /sdcard/download/
This is the code
Code:
Adb push overcome.zip /data/media/download/.
wait for copying progress done..
After you done with moving file to device sdcard check content of your sdcard with this code
Code:
Adb shell "ls /data/media/download/"
When you found your file from list, you can flash overcome.zip from recovery
Thanks for you quick answer
I do have recovery 5.5.0.4
I can get to mount /system & mount/data
when i go to adb and use the command to list the files i got this error
C:\android\sdk-windows\platform-tools>adb shell "ls /data/media/
- exec '/system/bin/sh' failed: No such file or directory (2) -
and tryng to do this command i got this error
C:\android\sdk-windows\platform-tools>adb get-state
unknown
seems like the device is connected
i tried this and the tablet rebooted (not in recovery but reboot)
C:\android\sdk-windows\platform-tools>adb reboot-bootloader
many thanks
Ok I found the way to make that work
i post the reply maybe can help someone else.
suwandiapr should get the credit anyway.
In a phone you have one wrong rom or somenthing and you can get a good one
and copy that to the sd, in a tablet or any device without microsd you need to push the file using this command adb push
let's say you got a rom called supernoob.zip
adb push supernoob.zip /data/media/supernoob.zip
and remeber if you are using a tablet o phone without sd always keep 2 roms in case
Yes i made a simple batch file for windows in development section...
just bought p7310 today and same boot loop actually
hi all
even if i believed i was a geek with nexus or android phones i was wrong !!!!!i just brick my new P7310 wifi tab
-first i root OK
-after i ran rom manager (so manytimes used with my nexus one...) OK
-i flashed CWM but i chose "10.1" (no 8.9 choice at this time) so when rebooting i got this famous (hum) reboot loop just after the welcome screen "samsung galaxy tab 8.9" ..pffffffffff what a stupid beginer i fell about myself ....
- i tried to go in revovery but the loop appears and appaers .....
so i read and read and read forums and probably the solution or a step to a little begining of solution seems to be here ...
i dl Odin v3 and hope to be able to use it and installing a good version ...
thanks to read me and sorry for my english (i m french)
brunobassman said:
hi all
even if i believed i was a geek with nexus or android phones i was wrong !!!!!i just brick my new P7310 wifi tab
-first i root OK
-after i ran rom manager (so manytimes used with my nexus one...) OK
-i flashed CWM but i chose "10.1" (no 8.9 choice at this time) so when rebooting i got this famous (hum) reboot loop just after the welcome screen "samsung galaxy tab 8.9" ..pffffffffff what a stupid beginer i fell about myself ....
- i tried to go in revovery but the loop appears and appaers .....
so i read and read and read forums and probably the solution or a step to a little begining of solution seems to be here ...
i dl Odin v3 and hope to be able to use it and installing a good version ...
thanks to read me and sorry for my english (i m french)
Click to expand...
Click to collapse
Go to dowload menu and try to flash stock recovery in your tab..
Here is the stock recovery for p7300/p7310
Start odin, and put the file in pda slot..
Please see entire thread for your own safety..
So I brought myself in a bad situation.
Here's a video showing what the phone does and me trying to get into CWM:
http ://www .youtube. com/watch?v=5F2Gg_eU7Yw
I was trying to root my sony xperia z1 compact using this guide: http ://techglen. com/2014/02/05/root-xperia-z1-compact-d5503-4-3-14-2-a-1-114-official-firmware/
Following the steps it asked me to CWM 6 using this guide: http ://techglen. com/2014/02/05/install-cwm-6-on-xperia-z1-compact-d5503-4-3-14-2-a-1-114-official-firmware/2
I checked firmware and version of my phone and everything was correct.
I must admit I have no clue as to what I'm doing but I'm normally ok with tech stuff and the guide seemed detailed and trust worthy so I thought I could do it following the guide.
I got the bootloading unlocked just fine and started to install CWM. I made it this far:
- After downloading CWM kernel zip (Its not the actual name of file, just a reference name), place it in internal or external SD Card of your smartphone
- Now extract CWM kernel zip on your PC’s desktop and copy boot.img
- Paste this file inside the folder where you have installed Minimal ADB and Fastboot
- Now turn off your smartphones completely
- Plug in mobile’s USB in cable in PC port only
- Hold Volume up button and plug in USB cable in mobile’s port
- LED will turn blue (If it does not remain blue for long, then read Optional part in bootloader unlocking method explained above
- Once you are successfully in fastboot mode, then you can continue
- Now type Fastboot flash boot boot.img and press Enter
- It will flash boot.img file on your device
- Now unplug the device and boot it up
- As soon as you see purple colored LED, start pressing volume up and down buttons repeatedly, until you are in CWM mode
- In CWM Mode, select “Install Zip”
Click to expand...
Click to collapse
I downloaded CWM .img file, placed it in my ADB folder and placed a copy on my phone. Using ADB I flashed the CWM .img (bolded step), unplugged the phone and the CWM screen came up and I was able to navigate using the volume buttons. So far so good.
At this point I realized that the CWM .img file I had downloaded and placed on my phone was not a zip file and I couldn't find it. So I hit reboot to boot up my phone normally so I could place the .img packed as a .zip file on the phone. Some error message came up, but I didn't manage to read it but caught something saying root I think.
As it rebooted the sony logo came up but then the purple led turned on and it seemed to boot into CWM again. A brief screen explaining how to navigate came up as you see in the video below (but with no menu options to actually navigate) before it rebooted and repeated.
I can still use ADB and fastboot, but I can't get into CWM and I can't boot normally.
Edit: Just tried "adb devices" and it says "list of devices attached" and then it's just blank. I can't push files onto the phone (error: device not found) but I can still reboot the device fusing fastboot and there's no error when I try and reflash cwm. Reading up on this it would seem that usb debugging has somehow been turned back on so adb can't acces the phone but fastboot can. Any way to turn on usb debugging through fastboot?
I tried a forced shutdown using the off button next to the sim card but it didn't help.
The phone is not recognized by my computer so I can't place or delete files from it.
Here's a video showing what the phone does and me trying to get into CWM:
http ://www .youtube. com/watch?v=5F2Gg_eU7Yw
If I don't press the volume button it will just keep looping in the sony logo and purple led light.
What I want to do is get back to a normal boot, remove the CWM .img file and put the .img file packed as .zip file onto the phone and retry the process.
I have googled a lot of options, but most results are a year old and I hardly understand half of what is being suggested. If anyone could please walk me through the process in a language that a total idiot can understand I would be so grateful and hopefully get my sleep back.
ravneravn said:
So I brought myself in a bad situation.
Here's a video showing what the phone does and me trying to get into CWM:
http ://www .youtube. com/watch?v=5F2Gg_eU7Yw
I was trying to root my sony xperia z1 compact using this guide: http ://techglen. com/2014/02/05/root-xperia-z1-compact-d5503-4-3-14-2-a-1-114-official-firmware/
Following the steps it asked me to CWM 6 using this guide: http ://techglen. com/2014/02/05/install-cwm-6-on-xperia-z1-compact-d5503-4-3-14-2-a-1-114-official-firmware/2
I checked firmware and version of my phone and everything was correct.
I must admit I have no clue as to what I'm doing but I'm normally ok with tech stuff and the guide seemed detailed and trust worthy so I thought I could do it following the guide.
I got the bootloading unlocked just fine and started to install CWM. I made it this far:
I downloaded CWM .img file, placed it in my ADB folder and placed a copy on my phone. Using ADB I flashed the CWM .img (bolded step), unplugged the phone and the CWM screen came up and I was able to navigate using the volume buttons. So far so good.
At this point I realized that the CWM .img file I had downloaded and placed on my phone was not a zip file and I couldn't find it. So I hit reboot to boot up my phone normally so I could place the .img packed as a .zip file on the phone. Some error message came up, but I didn't manage to read it but caught something saying root I think.
As it rebooted the sony logo came up but then the purple led turned on and it seemed to boot into CWM again. A brief screen explaining how to navigate came up as you see in the video below (but with no menu options to actually navigate) before it rebooted and repeated.
I can still use ADB and fastboot, but I can't get into CWM and I can't boot normally.
Edit: Just tried "adb devices" and it says "list of devices attached" and then it's just blank. I can't push files onto the phone (error: device not found) but I can still reboot the device fusing fastboot and there's no error when I try and reflash cwm. Reading up on this it would seem that usb debugging has somehow been turned back on so adb can't acces the phone but fastboot can. Any way to turn on usb debugging through fastboot?
I tried a forced shutdown using the off button next to the sim card but it didn't help.
The phone is not recognized by my computer so I can't place or delete files from it.
Here's a video showing what the phone does and me trying to get into CWM:
http ://www .youtube. com/watch?v=5F2Gg_eU7Yw
If I don't press the volume button it will just keep looping in the sony logo and purple led light.
What I want to do is get back to a normal boot, remove the CWM .img file and put the .img file packed as .zip file onto the phone and retry the process.
I have googled a lot of options, but most results are a year old and I hardly understand half of what is being suggested. If anyone could please walk me through the process in a language that a total idiot can understand I would be so grateful and hopefully get my sleep back.
Click to expand...
Click to collapse
I hope you made a backup of your phone.
It may be worth wiping everything and flashing the Z1 stock firmware on to your phone. Stock firmwares can be found relatively easily by using Google. There are also lots of different video tutorials on YouTube on how to how to revert back to stock firmware and on how you can escape bootloops. Try this: www. youtube. com/watch?v=j4gm9VeQCHA
You're on the wrong forum, this one is for Xperia Z, for Xperia Z1 Compact go here:
http://forum.xda-developers.com/sony-xperia-z1-compact
Hi everyone i´m new to this forum. I own a Asus ME176CX and updated to official lollipop 5 from asus.com. The device is rooted and it was a little bit slow so i decided to uninstall via root uninstall some of the Bloat Apps.
The Result is ... I messed it up. I deinstalled too many apps, and it seems that i uninstall some system apps too. When my device is booting it wont stop booting and i´m only able to turn the device off.
I can get into fastboot but my recovery mode says only failed when i try to start it. I´m really new to Android and asking for some advise here. I tried a lot of this workarounds here but nothing worked for me
#pleasehelpthenoob
Thanks in Advance
Waido1981 said:
Hi everyone i´m new to this forum. I own a Asus ME176CX and updated to official lollipop 5 from asus.com. The device is rooted and it was a little bit slow so i decided to uninstall via root uninstall some of the Bloat Apps.
The Result is ... I messed it up. I deinstalled too many apps, and it seems that i uninstall some system apps too. When my device is booting it wont stop booting and i´m only able to turn the device off.
I can get into fastboot but my recovery mode says only failed when i try to start it. I´m really new to Android and asking for some advise here. I tried a lot of this workarounds here but nothing worked for me
#pleasehelpthenoobA
Thanks in Advance
Click to expand...
Click to collapse
If you want lollipop, take it to warranty. If you don't mind getting stuck on kitkat (after lollipop update you can run windows or linux on this tablet, and maybe use custom rom if anyone will make it using my idea), just say and I will write you steps how to get kitkat back.
Waido1981 said:
Hi everyone i´m new to this forum. I own a Asus ME176CX and updated to official lollipop 5 from asus.com. The device is rooted and it was a little bit slow so i decided to uninstall via root uninstall some of the Bloat Apps.
The Result is ... I messed it up. I deinstalled too many apps, and it seems that i uninstall some system apps too. When my device is booting it wont stop booting and i´m only able to turn the device off.
I can get into fastboot but my recovery mode says only failed when i try to start it. I´m really new to Android and asking for some advise here. I tried a lot of this workarounds here but nothing worked for me
#pleasehelpthenoob
Thanks in Advance
Click to expand...
Click to collapse
Did you manage to work it out as I'm in the same boat at the moment - I can get to fastboot and can power on and off but stuck at boot! recovery efforts just show dead android and "Error"!
Anyone?
Cheers
noggin-the-nog said:
Did you manage to work it out as I'm in the same boat at the moment - I can get to fastboot and can power on and off but stuck at boot! recovery efforts just show dead android and "Error"!
Anyone?
Cheers
Click to expand...
Click to collapse
yeah my girlfriend has the same tablet. I took a backup with girlfriends device with fbrl and get it on my device. Just had to change settings and accounts and everything works well again.
Hi Everyone, I'm new here too.
I have the same problem in this topic.
I can use fastboot mode Only, I can't use adb mode, and the bootloader is locked.
when i was trying to install original firmware with this command:
fastboot update update.zip
I get this messege:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
I need solution for this.
I haven't problem to installing any operating system, like Windows, Ubuntu, Tizen, Android x86, or other.
Please, I really need help, more than five months i am looking for a way out from this problem but it's all failed, because the boot loader was locked.
Any help would be very appreciated.
Thank you in advance.
Hi
Doesn't anybody have any ideas to help me ?
Maybe I must unlock bootloader to solve my problem.
But how I can do that ?
Waido1981 said:
Hi everyone i´m new to this forum. I own a Asus ME176CX and updated to official lollipop 5 from asus.com. The device is rooted and it was a little bit slow so i decided to uninstall via root uninstall some of the Bloat Apps.
The Result is ... I messed it up. I deinstalled too many apps, and it seems that i uninstall some system apps too. When my device is booting it wont stop booting and i´m only able to turn the device off.
I can get into fastboot but my recovery mode says only failed when i try to start it. I´m really new to Android and asking for some advise here. I tried a lot of this workarounds here but nothing worked for me
#pleasehelpthenoob
Thanks in Advance
Click to expand...
Click to collapse
For people with access to bootloader:
1- Download .17 and extract it on desktop
2- go to META-INF\com\google\android\updater-script and open it with notepad ++, and delete first 2 lines
3- compress it and rename it to update.zip and place it in adb folder (for me its c:\\adb)
4- shutdown the tablet and press (power and vol-) to go to bootloader.
5- write on adb "adb push update.zip /sdcard/" wait until it finishes (dont leave bootloader)
6- Download Temp Recovery: www.androidfilehost.com/?fid=24052804347782876
7- On windows, open temp recovery program, and say "ACCEPT", and press 2 then press T4 and it should boot to the temp recovery on the tablet.
8- then install the update.zip, and then format cache and dalvik, then reboot and it should be fixed.
//////////////////////////////////////////////////////
//////////////////////////////////////////////////////
For people without access to bootloader:
1- Download .17 and extract it on desktop
2- go to META-INF\com\google\android\updater-script and open it with notepad ++, and delete first 2 lines
3- compress it and rename it to update.zip and place it in adb folder (for me its c:\\adb)
4- copy droidboot.img from .17 and put in in adb folder
5- go to fastboot and write "fastboot boot droidboot.img" it should boot to bootlaoder *do it at least 10 times because sometimes, the tablet boots to software and not bootloader*
6- if you are in bootloader then, Download Temp Recovery: www.androidfilehost.com/?fid=24052804347782876
7- After downloading, On windows, open temp recovery program, and say "ACCEPT", and press 2 then press T4 and it should boot to the temp recovery on the tablet.
8- then install the update.zip, and then format cache and dalvik, then reboot and it should be fixed.
//////////////////////////////
Good Luck! :laugh:
//////////////////////////////
Ruben Craveiro said:
For people without access to bootloader:
1- Download .17 and extract it on desktop
......
7- After downloading, On windows, open temp recovery program, and say "ACCEPT", and press 2 then press T4 and it should boot to the temp recovery on the tablet.
Click to expand...
Click to collapse
Hi Ruben,
What do you mean from step 1 ? Where can I find the (.17) to i can download it ?
When I perform step 7, it gave me error.
Overall, I had sent my problem to Asus support and their interaction was bad enough to hates them.
My problem has now ten months I have not found a solution, and the company asking me to send the device to America and I'm outside America.
I promise you I will avoid buying Asus devices from today onwards.
Thank you for trying to help us.
Venting said:
Hi Ruben,
What do you mean from step 1 ? Where can I find the (.17) to i can download it ?
When I perform step 7, it gave me error.
Overall, I had sent my problem to Asus support and their interaction was bad enough to hates them.
My problem has now ten months I have not found a solution, and the company asking me to send the device to America and I'm outside America.
I promise you I will avoid buying Asus devices from today onwards.
Thank you for trying to help us.
Click to expand...
Click to collapse
Did you manage to boot into the temp TWRP recovery or is that not working either?
lambdadroid said:
Did you manage to boot into the temp TWRP recovery or is that not working either?
Click to expand...
Click to collapse
Hello lambdadroid,
No, It's not work.
Venting said:
Hello lambdadroid,
No, It's not work.
Click to expand...
Click to collapse
You said you have access to fastboot though? Then you should also be able to boot into the temp recovery (e.g. TWRP)
lambdadroid said:
You said you have access to fastboot though? Then you should also be able to boot into the temp recovery (e.g. TWRP)
Click to expand...
Click to collapse
OK ..
I don't flashed the TWRP Recovery, and I can't get into fastboot / droidboot mode.
But when I press on this buttons (Volume up + Volume down + and Power) while booting, the device stopped on the ASUS logo screen, and in this status my PC connected with my Tablet device, and I can use fastboot commands, no thing other.
I can't use the ADB commands.
Also, When I tried flashing the firmware with ASUS Flash Tool, or CMD shell, I got the same message: FAILED (remote failure).
When I was trying to install the original firmware through CMD Shell with this command: "fastboot flash update update.zip"
I got this message:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
When I tried with IntelAndroid-FBRL-07-24-2015 to flash TWRP or CWM Recovery, I got the error messages such as:
FAILED (data transfer failure (Unknown error))
FAILED (command write failed (No such device or address))
FAILED (command write failed (Unknown error))
I can't write anything to the device, That's everything.
I think i must unlock the bootloader to solve my problem.
But how do I do that ?
Venting said:
OK ..
I don't flashed the TWRP Recovery, and I can't get into fastboot / droidboot mode.
But when I press on this buttons (Volume up + Volume down + and Power) while booting, the device stopped on the ASUS logo screen, and in this status my PC connected with my Tablet device, and I can use fastboot commands, no thing other.
I can't use the ADB commands.
Also, When I tried flashing the firmware with ASUS Flash Tool, or CMD shell, I got the same message: FAILED (remote failure).
When I was trying to install the original firmware through CMD Shell with this command: "fastboot flash update update.zip"
I got this message:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
When I tried with IntelAndroid-FBRL-07-24-2015 to flash TWRP or CWM Recovery, I got the error messages such as:
FAILED (data transfer failure (Unknown error))
FAILED (command write failed (No such device or address))
FAILED (command write failed (Unknown error))
I can't write anything to the device, That's everything.
I think i must unlock the bootloader to solve my problem.
But how do I do that ?
Click to expand...
Click to collapse
What you're saying doesn't make much sense. How did you actually mess up your tablet?
Please also tell me the following:
- What happens if you power on the tablet normally?
- What happens if you power on the tablet using Vol+ and the power button?
- What happens if you power on the tablet using Vol- and the power button?
Unlocking the bootloader is not possible on this device and it wouldn't help you anyway if you can't get into fastboot (the droidboot screen). As far as I know the fastboot screen you can enter with Vol+ and Vol- and the power button is pretty much useless, you need the droidboot screen to recover your tablet.
lambdadroid said:
What you're saying doesn't make much sense. How did you actually mess up your tablet?
Please also tell me the following:
- What happens if you power on the tablet normally?
- What happens if you power on the tablet using Vol+ and the power button?
- What happens if you power on the tablet using Vol- and the power button?
Unlocking the bootloader is not possible on this device and it wouldn't help you anyway if you can't get into fastboot (the droidboot screen). As far as I know the fastboot screen you can enter with Vol+ and Vol- and the power button is pretty much useless, you need the droidboot screen to recover your tablet.
Click to expand...
Click to collapse
If I press on the power button normally
Or I press on Volume up button, and Power button
Or I press on Volume down button, and Power button
The result is the same, It's a red line is showing on screen bottom, then the device stops working.
You can see this Picture here
Venting said:
If I press on the power button normally
Or I press on Volume up button, and Power button
Or I press on Volume down button, and Power button
The result is the same, It's a red line is showing on screen bottom, then the device stops working.
You can see this Picture here
Click to expand...
Click to collapse
How did you actually mess up your tablet?
I don't think you'll have many options to repair your tablet at this point. You could have luck if you have a powered OTG hub, by booting something like Linux and flashing the necessary stuff back to the internal storage, although depending on how much you messed up, that may not make things better. The other option is sending it in to ASUS.
Venting said:
Hi Ruben,
What do you mean from step 1 ? Where can I find the (.17) to i can download it ?
When I perform step 7, it gave me error.
Overall, I had sent my problem to Asus support and their interaction was bad enough to hates them.
My problem has now ten months I have not found a solution, and the company asking me to send the device to America and I'm outside America.
I promise you I will avoid buying Asus devices from today onwards.
Thank you for trying to help us.
Click to expand...
Click to collapse
what i mean with .17 is the software (first lollipop release)
you can get it here: http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/UL-K013-WW-12.10.1.17_KK-user.zip
and to run the temp recovery make sure you have access to bootloader and have all drivers installed, if your computers says something about adb drivers for bootloader add these drivers so that it works: http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ADB_driver.zip if you still cant acces is because you did not installed properly all the needed drivers. I wish u luck.
---------- Post added at 08:49 PM ---------- Previous post was at 08:44 PM ----------
[/COLOR]
Venting said:
If I press on the power button normally
Or I press on Volume up button, and Power button
Or I press on Volume down button, and Power button
The result is the same, It's a red line is showing on screen bottom, then the device stops working.
You can see this Picture here
Click to expand...
Click to collapse
if you cant access bootloader or fastboot the only way to get it back, is to have a otg powered hub, and run uefi, and then boot linux and then reinstall the android partitions. (im very newbie at this so i cant tell u much about it)
---------- Post added at 09:00 PM ---------- Previous post was at 08:49 PM ----------
Venting said:
OK ..
I don't flashed the TWRP Recovery, and I can't get into fastboot / droidboot mode.
But when I press on this buttons (Volume up + Volume down + and Power) while booting, the device stopped on the ASUS logo screen, and in this status my PC connected with my Tablet device, and I can use fastboot commands, no thing other.
I can't use the ADB commands.
Also, When I tried flashing the firmware with ASUS Flash Tool, or CMD shell, I got the same message: FAILED (remote failure).
When I was trying to install the original firmware through CMD Shell with this command: "fastboot flash update update.zip"
I got this message:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
When I tried with IntelAndroid-FBRL-07-24-2015 to flash TWRP or CWM Recovery, I got the error messages such as:
FAILED (data transfer failure (Unknown error))
FAILED (command write failed (No such device or address))
FAILED (command write failed (Unknown error))
I can't write anything to the device, That's everything.
I think i must unlock the bootloader to solve my problem.
But how do I do that ?
Click to expand...
Click to collapse
well you have made some stuff wrong, BUT i think you can get it back, first of all its not supposed for you to actually install twrp or cwm, and you need this file: (droidboot.img) https://drive.google.com/file/d/0B3h_JptTNZeeRjdXdE1rWlNLYnM/view?usp=sharing
and place it in c:\\adb and then do fastboot boot droidboot.img and then it should boot to the bootloader if it doesnt, then do it again and again until it does.. (you need to do it several times to make it work, at least thats how i got out of bootloop), then in the bootloader you have access to adb commands so temp recovery should be working, if it still doesnt then it means it needs the adb drivers for the bootloader, after u loaded twrp recovery load .17 update(place the update in microsd, or adb push update.zip /sdcard/) and it should work
lambdadroid, Ruben Craveiro
Thank you guys so much for trying help me.
I tried everything except OTG powered hub.
I will try with OTG powered hub, and I hope solves my problem.
Thank you for everything.
Ruben Craveiro said:
For people with access to bootloader:
1- Download .17 and extract it on desktop
2- go to META-INF\com\google\android\updater-script and open it with notepad ++, and delete first 2 lines
3- compress it and rename it to update.zip and place it in adb folder (for me its c:\\adb)
4- shutdown the tablet and press (power and vol-) to go to bootloader.
5- write on adb "adb push update.zip /sdcard/" wait until it finishes (dont leave bootloader)
6- Download Temp Recovery:
7- On windows, open temp recovery program, and say "ACCEPT", and press 2 then press T4 and it should boot to the temp recovery on the tablet.
8- then install the update.zip, and then format cache and dalvik, then reboot and it should be fixed.
//////////////////////////////////////////////////////
//////////////////////////////////////////////////////
For people without access to bootloader:
1- Download .17 and extract it on desktop
2- go to META-INF\com\google\android\updater-script and open it with notepad ++, and delete first 2 lines
3- compress it and rename it to update.zip and place it in adb folder (for me its c:\\adb)
4- copy droidboot.img from .17 and put in in adb folder
5- go to fastboot and write "fastboot boot droidboot.img" it should boot to bootlaoder *do it at least 10 times because sometimes, the tablet boots to software and not bootloader*
6- if you are in bootloader then, Download Temp Recovery
7- After downloading, On windows, open temp recovery program, and say "ACCEPT", and press 2 then press T4 and it should boot to the temp recovery on the tablet.
8- then install the update.zip, and then format cache and dalvik, then reboot and it should be fixed.
//////////////////////////////
Good Luck! :laugh:
//////////////////////////////
Click to expand...
Click to collapse
Hello
I tried these two methods to recover my unrooted Memo tab. The push method doesn't do anything and the second method says "wating for device"
A little background info on how I got here. The tablet got stuck on the loading screen after the last OTA update. I tried to do the factory reset from the tablet but I get the following messsage, "E: Can't open /dev/block/by-name/misc"
I have also tried to load the zip file using sideload and get the following message.
E:failed to verify whole-file signature
E:signature verification failed
Not sure what else to try...any help is appreciated.
wifebeeter said:
Hello
I tried these two methods to recover my unrooted Memo tab. The push method doesn't do anything and the second method says "wating for device"
A little background info on how I got here. The tablet got stuck on the loading screen after the last OTA update. I tried to do the factory reset from the tablet but I get the following messsage, "E: Can't open /dev/block/by-name/misc"
I have also tried to load the zip file using sideload and get the following message.
E:failed to verify whole-file signature
E:signature verification failed
Not sure what else to try...any help is appreciated.
Click to expand...
Click to collapse
make sure your device is conected to pc and that it has all the drivers needed (adb drivers)...boot into bootloader and load temp recovery and flash latest version
---------- Post added at 10:10 PM ---------- Previous post was at 10:00 PM ----------
Venting said:
lambdadroid, Ruben Craveiro
Thank you guys so much for trying help me.
I tried everything except OTG powered hub.
I will try with OTG powered hub, and I hope solves my problem.
Thank you for everything.
Click to expand...
Click to collapse
you can access dnx mode(fastboot starting #1#2#3), so you can go into bootloader, heres how: get the file efilinux.efi and droidboot.img and put them in adb folder (you can get the droidboot.img on update.zip and if u look on .33 version theres a zip inside of it that its called ESP, you can find efilinux.efi from there) after doing that go into DnX mode on the tablet, and do these fastboot commands: "fastboot flash osloader efilinux.efi" and do "fastboot boot droidboot.img" and this will certainly make you boot to droidboot/bootloader and from there you can load temp recovery and flash the software, and no need for otg hub
Ruben Craveiro said:
make sure your device is conected to pc and that it has all the drivers needed (adb drivers)...boot into bootloader and load temp recovery and flash latest version
HI
I tried temporary recovery and I get the following messege.
error: closed
<waiting for device>
Click to expand...
Click to collapse