Database Info

Another Recovery

If anybody need recovery, full worked with new 4.1.1 JB get it here.
Moderator Edit:
Link removed as it is proven this recovery can damage your device.

Gigabyte0 said:
If anybody need recovery, full worked with new 4.1.1 JB get it here
Click to expand...
Click to collapse
What exactly is that, where is it from?
Recovery shouldn't have anything to do with installed Android version.
Sent from my GT-I9000 using xda app-developers app

pawitp said:
What exactly is that, where is it from?
Recovery shouldn't have anything to do with installed Android version.
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
If I were to guess, it's a different CWM recovery using JB Kernel?. It probably came from 4pda.ru which is a russian site. HAs a lot of android tablet stuff.
Just a guess. Might research it a little and see what I come up with.
It's not exactly the easiest site to navigate through.
MD

Moscow Desire said:
If I were to guess, it's a different CWM recovery using JB Kernel?. It probably came from 4pda.ru which is a russian site. HAs a lot of android tablet stuff.
Just a guess. Might research it a little and see what I come up with.
It's not exactly the easiest site to navigate through.
MD
Click to expand...
Click to collapse
I don't exactly see the need of a new recovery, since it works independent of the Android version. An "unknown" recovery would be possibly unsafe as well.

Gigabyte0 said:
If anybody need recovery, full worked with new 4.1.1 JB get it here
Click to expand...
Click to collapse
this one save´d my TAB!!!
i was able to reanimate it after i messed up ..
THX a lot

pawitp said:
I don't exactly see the need of a new recovery, since it works independent of the Android version. An "unknown" recovery would be possibly unsafe as well.
Click to expand...
Click to collapse
This is not "unknown" recovery. This 6.0.1.1 with kernel from bootloader JB (boot.img)
And this recovery normal mount all partition, make backup-restore and other function.
For ICS bootloader need original recovery 6.0.1.1
For JB bootloader my recovery, rebuilding from original JB bootloader and CMW recovery

Gigabyte0 said:
This is not "unknown" recovery. This 6.0.1.1 with kernel from bootloader JB (boot.img)
And this recovery normal mount all partition, make backup-restore and other function.
For ICS bootloader need original recovery 6.0.1.1
For JB bootloader my recovery, rebuilding from original JB bootloader and CMW recovery
Click to expand...
Click to collapse
You should give some info when posting, otherwise it is "unknown".
The boot.img contains the kernel not the bootloader. The kernel source is yet to be released by Acer and we don't know if Acer has blocked the dangerous emmc wipe command (which will randomly brick tablets, the more you wipe, the riskier you are) like I did on my kernel or not.

This is not "unknown" recovery. This 6.0.1.1 with kernel from bootloader JB (boot.img)
And this recovery normal mount all partition, make backup-restore and other function.
For ICS bootloader need original recovery 6.0.1.1
For JB bootloader my recovery, rebuilding from original JB bootloader and CMW recovery
Click to expand...
Click to collapse
But what it does not, it does not flashes. Freezes and hangs. Have my tab after 30 minutes. removed and restarted, now it hangs in APX mode. Do you have a solution for this?

Hi There
after i recovered my Tab to work, i´ve done a flash with this Recovery and it freezes.
After this i only was able to turn off the Decvice.
Now it seem´s that i can´t turn on, Black Screen, no LED, only thing the Computer tells an USB Device want´s to install.
Try to install APX drivers an failed.
some ideas?

meier2009 said:
Hi There
after i recovered my Tab to work, i´ve done a flash with this Recovery and it freezes.
After this i only was able to turn off the Decvice.
Now it seem´s that i can´t turn on, Black Screen, no LED, only thing the Computer tells an USB Device want´s to install.
Try to install APX drivers an failed.
some ideas?
Click to expand...
Click to collapse
"This recovery" meaning mine or Gigabyte0's?
If you're in APX mode, you're out of luck and the service center will probably need to replace your mainboard.

"This recovery" meaning mine or Gigabyte0's?
If you're in APX mode, you're out of luck and the service center will probably need to replace your mainboard.
Click to expand...
Click to collapse
Yes, it meant the version of Gigabyte0. Does not sound good.

Spread the word please:
ONLY USE PAWITP'S RECOVERY UNLESS YOU WANT A BRICKED TABLET
If pawitp's recovery is not working for you, then wait. The Recovery released by Gigabyte0 and found on 4PDA is built with Acer's kernel and Acer still has not fixed the brick bug!
Again, do NOT use Gigabyte0's recovery!

NoThrills said:
Spread the word please:
ONLY USE PAWITP'S RECOVERY UNLESS YOU WANT A BRICKED TABLET
If pawitp's recovery is not working for you, then wait. The Recovery released by Gigabyte0 and found on 4PDA is built with Acer's kernel and Acer still has not fixed the brick bug!
Again, do NOT use Gigabyte0's recovery!
Click to expand...
Click to collapse
And I will concurr. So far, Pawitp's has caused 0 issues.
Why somebody would want to install an unheard of recovery, with absolutely 0 information about it, is just asking for trouble.
I'll toss in a note to the FSM, and have him deal with Gigabyte0 on what to do with this link.
MD

Moscow Desire said:
And I will concurr. So far, Pawitp's has caused 0 issues.
Why somebody would want to install an unheard of recovery, with absolutely 0 information about it, is just asking for trouble.
I'll toss in a note to the FSM, and have him deal with Gigabyte0 on what to do with this link.
MD
Click to expand...
Click to collapse
Maybe you can also let this know on 4PDA.ru, as I am not Russian (and you are) you can probably explain it better:
In the Acer 3.0 Android kernel the command MMC_CAP_ERASE, which has caused all the old bricks, is still present. At least it is in the A110 3.0 kernelsource and I have no reason to believe they would remove it in the A700 3.0 kernelsource but not in the A110 one.
When this command exists in the kernel, and the Recovery also allows it (Recovery can also disable it, but the current A700 recovery doesn't do that), you are almost guarantueed a brick.
If you could translate that to 'the Russians' I guess we can save a few more people from bricking.

Thread Closed

[Q] how to get fastboot mode back on the tablet

What I have done so far, in order:
Installed the OTA JB upgrade on my 100% stock unrooted tablet.
Installed and configured ADB.
Downgraded to the .30 firmware.
Rooted my device (confirmed working).
So right now I have rooted ICS, but I can't choose the fastboot option anymore when I boot using the volume down+power combination. I only have the option to boot the device normally or wipe data.
How can I get fastboot back on my device? ADB is still working normally.
It's probably a simple solution I'm missing but I've been trying to get CM10 installed for about 2 hours now just trying to work my way through the steps one at a time and right now I'm a bit lost.
Thanks in advance for the help.

Octhellion said:
What I have done so far, in order:
Installed the OTA JB upgrade on my 100% stock unrooted tablet.
Installed and configured ADB.
Downgraded to the .30 firmware.
Rooted my device (confirmed working).
So right now I have rooted ICS, but I can't choose the fastboot option anymore when I boot using the volume down+power combination. I only have the option to boot the device normally or wipe data.
How can I get fastboot back on my device? ADB is still working normally.
It's probably a simple solution I'm missing but I've been trying to get CM10 installed for about 2 hours now just trying to work my way through the steps one at a time and right now I'm a bit lost.
Thanks in advance for the help.
Click to expand...
Click to collapse
I have been on JB for awhile, so if my memory served me right, for ICS, you need to unlock your device to get to fastboot? On JB, you could get to fastboot without unlocked. Correct me if I'm wrong ppl.

That's correct. You need to unlock if you want fastboot on ICS. If you upgrade to JB, you can keep your root and have fastboot back.
Also, you need to be unlocked regardless if you want to install a custom ROM like CM10 or any custom recoveries. Even if you upgrade to JB and get fastboot back, it will not flash if you're not unlocked.

I forgot to mention that I already used an unlock tool and it says this device is unlocked during boot. I'm on my phone right now so if someone could provide me with a link with more information about this unlocking I would be very appreciative.

http://forum.xda-developers.com/showthread.php?t=1795156

ArmyAg08 said:
http://forum.xda-developers.com/showthread.php?t=1795156
Click to expand...
Click to collapse
That's the app I already tried, but the fastboot option is still missing.

re-locking the bootloader under jelly bean.

I have to sent in my A700 to Acer for repair because it won't charge anymore.
I flashed back to a full Stock ROM 4.1.1 (RV16RC01_EMEA_DE) but the problem is that I cannot re-lock the bootloader with fastboot oem lock (boot.img is not an official image)
I have NOT rooted or modified the ROM in any way.
So is there still a way to lock the bootloader??
I need to quickly find a solution because I only have 17% battery left.

No there is no way at this moment to relock the bootlader.

any experience that it will void the warrenty?
I'm not willing to pay over 100euros for repair just because there is an hardware failure that is not related to software.

Maybe you can flash an ICS stock FULL Rom, it will relock the bootloader (ics's one) and do not upgrade to JB( or your bootloader will be unlocked).
And then send your tab (with ICS) to repair

will do that.

nex86 said:
will do that.
Click to expand...
Click to collapse
Did it work?

yes I flashed an older ICS ROM.
Apperently its a beta but it worked.

nice

good tot know, thanks!

Warranty has nothing to uploading your own software or open bootloader unless acer proves that it was the cause of damage to the equipment.
I had a problem with the a210, and although it was open bootloader and uploaded custom ROM for the duration of the warranty.
ACER exchanged motherboard under warranty.

Any chance you could give a step by step for flashing the ICS full rom back?
I tried this but got stuck on the Iconia boot animation.
I can get back to jb but with unlocked bootloader...

I tried this but got stuck on the Iconia boot animation.
Click to expand...
Click to collapse
If you reset your Userdata, the Tab does not stuck anymore

Wesie said:
If you reset your Userdata, the Tab does not stuck anymore
Click to expand...
Click to collapse
I "thought" I tried at, but its VERY possible I didn't.
Should the need arise again I'll definitely remember to do so.
Thanks for the reply!

Can't mount any partition

Hello guys, as the title suggest i can't mount any partition on my tab...
i'm using TWRP 2.4.4.0 and i'm on the 4.2 JB bootloader...
what should i do to get it working again?
also in the bootloader i can see this
Code:
Key driver not found... Booting OS
Android cardhU-user bootloader <1.00 e> released by "WW_epad-10.6.1.8-20130225" A03

matt95 said:
Hello guys, as the title suggest i can't mount any partition on my tab...
i'm using TWRP 2.4.4.0 and i'm on the 4.2 JB bootloader...
what should i do to get it working again?
Click to expand...
Click to collapse
As long as you can use fastboot, replace it with the version that works on your bootloader:
TWRP 2.4.4. 0-4.2.
CAREFUL: A lot of people bricked their tablets in this state.
Read one of the many threads on this particular issue.
Sent from my TF300T using Tapatalk HD

i've tried to flash the new recovery but it remains always the same, for instance i've flashed the 2.5.0.0 4.2 version but every time i boot into recovery it says TWRP 2.4.4.0 (which is the one i had before)

matt95 said:
i've tried to flash the new recovery but it remains always the same, for instance i've flashed the 2.5.0.0 4.2 version but every time i boot into recovery it says TWRP 2.4.4.0 (which is the one i had before)
Click to expand...
Click to collapse
Weird.
Are you using fastboot to flash?
What messages are you getting from fastboot?
Sent from my TF300T using Tapatalk HD

Code:
ERROR: could not get pipe properties
and then it flashes it correctly but nothing seems to change

matt95 said:
Code:
ERROR: could not get pipe properties
and then it flashes it correctly but nothing seems to change
Click to expand...
Click to collapse
OK, so flashing fails silently for some reason.
Do you see the blue flash bar on the bootloader screen, when fast boot says "writing"?
Never had any fastboot issues on Linux, but I have seen lots of people having issues with drivers on Windows. If you are using Windows, you might want to read up, how to make sure you have the proper drivers installed.
Short of that, no idea. :-/
Maybe can you post the full output of fastboot?
Should not be more than a couple of lines, right?
Sent from my TF300T using Tapatalk HD

i'm not at home now, i'll post them as soon as i get to it...
anyway i used MacOs, Linux and Windows

Make sure you're using the newest fastboot. There may be a bug on your current version.
Back in August I soft-bricked my tablet - no recovery and no ADB access. Fastboot would turn on on the tablet, but fastboot on my computer (Debian) kept hanging on "waiting for device". I had used fastboot on the same computer a couple weeks earlier to flash a recovery, and lsusb showed all the correct device info, so I thought fastboot was broken on the tablet and I was SOL. Well, fastboot got added to the Debian repos at some point, and I installed that version. 8 months and 2 fastboot updates went by before I even attempted to fix my tablet again (2 weeks ago), but somehow it worked, and I now have an awesome tablet to play with. I have no idea what happened with fastboot when my tablet first bricked, but I can only assume that one of the fastboot updates fixed a nasty bug that only showed up when I bricked the tablet.
I know your device is being recognized by fastboot, and your situation is much different than mine was, but you could be experiencing a completely different bug.

EndlessDissent said:
Make sure you're using the newest fastboot.
Click to expand...
Click to collapse
Good point!
matt, any progress?

http://forum.xda-developers.com/showthread.php?p=40809070
mb it will help you

sorry guys today i was very busy, i'll try to solve it tomorrow

matt95 said:
sorry guys today i was very busy, i'll try to solve it tomorrow
Click to expand...
Click to collapse
In your bootloader, what version of ASUS firmware does it say you are running. It makes a big difference for which version of TWRP you should be using.
edit:
sorry in your first post i could see you listed it, I think you may be getting this besause you dont have the TWRP version for 4.2 jellybean. the versions that are compatible are labeled -4.2 at the end.
here is the link for the right twrp for asus firmware 10.6.1.8 - http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
Version 2.5.5.0-4.2. of twrp is only compatible with the update for our tab that came out last week-asus firmware 10.6.1.15.3

CBank said:
In your bootloader, what version of ASUS firmware does it say you are running. It makes a big difference for which version of TWRP you should be using.
edit:
sorry in your first post i could see you listed it, I think you may be getting this besause you dont have the TWRP version for 4.2 jellybean. the versions that are compatible are labeled -4.2 at the end.
here is the link for the right twrp for asus firmware 10.6.1.8 - http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
Version 2.5.5.0-4.2. of twrp is only compatible with the update for our tab that came out last week-asus firmware 10.6.1.15.3
Click to expand...
Click to collapse
at first i didn't install the correct TWRP but now i can't even flash the correct one that's my problem

I believe this may be the same issue that alot of devices suffered from when the 4.2.1 update first came out.
Here is a thread on the issue
http://forum.xda-developers.com/showthread.php?t=2179874
From what I understand it seems that the 4.2.1 bootloader changed the way that the partition table was setup and thus all previous versions of custom recoveries could not mount any partitions (twrp would ask for password & not be able to mount any partition & cwm also not able to mount any partition) and a new twrp-4.2 version had to be made specifically for the 4.2.1 bootloader.
Still not sure as to why this caused the fastboot issue with the majority of people that flashed an incompatible version of twrp or cwm.
The fastboot issue I am talking about is that when you use the "flash" command everything will seem to go fine , it will say writing... and successful on the command prompt but you will not get any blue progress bar on the tablet itself and after the flash command has completed the fastboot reboot command will not reboot the tablet. Which I find very odd as other fastboot commands will still work without issue.
The only know solution if this is the issue you have is to replace the motherboard.

pjc21 said:
The only know solution if this is the issue you have is to replace the motherboard.
Click to expand...
Click to collapse
bad news

matt95 said:
bad news
Click to expand...
Click to collapse
Well, don't give up yet. That there is no known solution does not mean we can't find any.
If fastboot is broken, can you access via adb, while in recovery?
Also there was a thread on unbricking with fastboot issues. Might try that:
http://forum.xda-developers.com/showthread.php?t=2236885
Sent from my TF300T using Tapatalk HD

i'm able to use adb and also fastboot commands... the recovery however do not work obviously because it isn't the right one... i'm here on xda since 2010 and i still make such mistakes stupid me

matt95 said:
i'm able to use adb and also fastboot commands... the recovery however do not work obviously because it isn't the right one... i'm here on xda since 2010 and i still make such mistakes stupid me
Click to expand...
Click to collapse
Just shows that it can happen to the best of us!
Why don't you try the method from the thread in my last post?
Seems the guy had the same issue with fastboot and solved it.
Sent from my TF300T using Tapatalk HD

i'll definitely try that method! i'll let you know, thanks guys

matt95 said:
i'll definitely try that method! i'll let you know, thanks guys
Click to expand...
Click to collapse
I'm in the same situation that you're in. I can send simple fastboot and ADB commands to the tab but as soon as I try to write anything, it just freezes and requires a hard reset. You'll find that you will be able to erase and send simple reset/info request but no write commands. You'll be able to erase your recovery partition but you will not be able write anything new to it. Good luck!
I ordered a MB from ebay last night. Now I just need to find a guide on replacing it.....

Help!... I lost my motorola droid razr HD stock recovery and I cannot boot to android

Hi buddies, I am new to flashing roms. I recently flashed a new recovery on my motorola droid hd, it succeed but after rebooting to recovery I realized that the resolution of safestrap recovery was larger than my screen so I could not use functions like "swipe to flash" and "swipe to unlock" or any other function at the lower end of the screen. So I turned it of and restarted then it says bootstrap disabled, it tries booting but spends forever when it gets to the red eye. I downloaded as "said to be" stock recovery and it flashed fine, but I still cannot to boot to my stock recovery. I need help to get my phone back..... please.
NB: * I tried flashing a rom with RSD Lite version 4 to 6 but the software cannot detect my phone in AP Fastboot mode.
* I have already install drivers from motorola and so many android drivers but still my phone is not detected (Only fastboot in command prompt sees it)
* Phone displays Device is locked, Status Code 0
* When ever I try flashing a recovery through fastboot cmd it starts and fails (Preflash validation failed, remote failure)
* Previous threads with links to download stock razr HD recovery and roms have broken links. (Please help me get a a stock recovery and rom)

kbolero said:
Hi buddies, I am new to flashing roms. I recently flashed a new recovery on my motorola droid hd, it succeed but after rebooting to recovery I realized that the resolution of safestrap recovery was larger than my screen so I could not use functions like "swipe to flash" and "swipe to unlock" or any other function at the lower end of the screen. So I turned it of and restarted then it says bootstrap disabled, it tries booting but spends forever when it gets to the red eye. I downloaded as "said to be" stock recovery and it flashed fine, but I still cannot to boot to my stock recovery. I need help to get my phone back..... please.
NB: * I tried flashing a rom with RSD Lite version 4 to 6 but the software cannot detect my phone in AP Fastboot mode.
* I have already install drivers from motorola and so many android drivers but still my phone is not detected (Only fastboot in command prompt sees it)
* Phone displays Device is locked, Status Code 0
* When ever I try flashing a recovery through fastboot cmd it starts and fails (Preflash validation failed, remote failure)
* Previous threads with links to download stock razr HD recovery and roms have broken links. (Please help me get a a stock recovery and rom)
Click to expand...
Click to collapse
What version of android were you running? The zero means means your bootloader is locked.

OGdroidster said:
What version of android were you running? The zero means means your bootloader is locked.
Click to expand...
Click to collapse
4.4 Kitkat

kbolero said:
4.4 Kitkat
Click to expand...
Click to collapse
Reflash stock rom. Just to make sure you have the correct drivers uninstall any drivers you may have tried before. Then install these drivers acording to witch system you are running 32 bit or 64 bit system; takling about your pc of course, for 32 bit use these drivers: https://www.androidfilehost.com/?fid=24269982087010422 , for 64 bit use these drivers: https://www.androidfilehost.com/?fid=24269982087010424 , next we are going to make sure rsd lite installed correctly because on windows installs don't always install correctly so uninstall the version or current one your using and use this rsdlite version it has never failed me: https://forum.xda-developers.com/attachment.php?attachmentid=3388466&d=1435873884 , Now flash the last version of kk moto firmware and you should be fine. Here is the stock firmware: https://www.androidfilehost.com/?fid=24269982087011676
If you run into complications let me know and ill help you. After we get it running you will need to reroot, but to use a custom recovery you will need TWRP not safestrap. To flash TWRP you need to unlock the bootloader witch you use the sun app for that and that app cost 25 bucks. You pay during the process

OGdroidster said:
Reflash stock rom. Just to make sure you have the correct drivers uninstall any drivers you may have tried before. Then install these drivers acording to witch system you are running 32 bit or 64 bit system; takling about your pc of course, for 32 bit use these drivers: https://www.androidfilehost.com/?fid=24269982087010422 , for 64 bit use these drivers: https://www.androidfilehost.com/?fid=24269982087010424 , next we are going to make sure rsd lite installed correctly because on windows installs don't always install correctly so uninstall the version or current one your using and use this rsdlite version it has never failed me: https://forum.xda-developers.com/attachment.php?attachmentid=3388466&d=1435873884 , Now flash the last version of kk moto firmware and you should be fine. Here is the stock firmware: https://www.androidfilehost.com/?fid=24269982087011676
If you run into complications let me know and ill help you. After we get it running you will need to reroot, but to use a custom recovery you will need TWRP not safestrap. To flash TWRP you need to unlock the bootloader witch you use the sun app for that and that app cost 25 bucks. You pay during the process
Click to expand...
Click to collapse
thanks a lot OGdroidster, I got it flashed to stock at a phone shop yesterday, but I will learn your steps above because I will need them in the future or any time I brick my phone

kbolero said:
thanks a lot OGdroidster, I got it flashed to stock at a phone shop yesterday, but I will learn your steps above because I will need them in the future or any time I brick my phone
Click to expand...
Click to collapse
Cool Download everthing and it ready to go for next time.

OGdroidster said:
Cool Download everthing and it ready to go for next time.
Click to expand...
Click to collapse
Okay

Are you going to root it and unlock the bootloader?

OGdroidster said:
Are you going to root it and unlock the bootloader?
Click to expand...
Click to collapse
I have already rooted it but Motorola is saying the phone does not qualify for bootloader unlocking. Do you have any idea to go around it (unlock bootloader)?

kbolero said:
I have already rooted it but Motorola is saying the phone does not qualify for bootloader unlocking. Do you have any idea to go around it (unlock bootloader)?
Click to expand...
Click to collapse
You have to use the sun app.

OGdroidster said:
You have to use the sun app.
Click to expand...
Click to collapse
Okay, you mentioned that earlier. I will try it.
Thanks.