To clean up another thread, I open this one to continue:
chipzter said:
I used the mempodroid exploit so I didn't need to install a custom recovery to root it.
It freezes and shows the acer-logotype and it shows the following text in the upper left corner:
Bootloader Version 0.04.04-ICS-MDRR (Unlock Mode)
So not totally dead. But definitely not completely alive either....
Do you think it would be OK to make a new thread with my problem? It would be nice to keep the discussion public so that it can help other people if they get the same problem...
Click to expand...
Click to collapse
@ Chipzter
Which language-firmware does you need? Because Acer has different FW versions for diff. countries?
First of all, download from Acer a Full Firmwareversion of your choise ( or country) from here
http://global-download.acer.com/Step5.aspx?Step1=Tablet&Step2=ICONIA%20TAB&Step3=A510&BC=Acer&SC=&LC=en&OS=a09&FS=O02&Category=OS
The file must be have a little bit more as 300MB.
* Open the archiv. You'll find a pdf and a file "update.zip" in it. Follow the instruction: copy the file update.zip to the root od the external SD card and start the Tab with the Key-Kombo, which is written there.
? Does it works? What it happen? What does you see?
You can try this a few times, it doesn't matter. Pls give attention, that your Accu has as min. 50%, or after that the TAB start to flash, connect the power-supply during the flash-phase. If you want to repeat, disconnect first at all, the power-supply; if the Tab start to flash, connect the power again.
Pls write the result here, don't try anything with Flashboot at this time or other things.....
Wesie said:
Which language-firmware does you need? Because Acer has different FW versions for diff. countries?
Click to expand...
Click to collapse
I don't know exactly. It was ordered online in Sweden, but from a company that sends everything from France. Still I think it was the same version that's generally available in Swedish stores. I had the language set to English though, because I'm more comfortable with English operating systems.
Wesie said:
First of all, download from Acer a Full Firmwareversion of your choise ( or country) from here
(...URLS removed since I don't have permission to post URLs yet...)
The file must be have a little bit more as 300MB.
Click to expand...
Click to collapse
Since the device never booted properly after the failed OTA update, I wasn't sure which firmware version I had. I tried the following ones:
EMEA.CUS1
WW.GEN1
EMEA.DE
EMEA.GB
All of them had file sizes over 300Mb.
No matter which one I tried, It always showed me the green android with a spinning icon for about 0.1 second, then it showed a lying down android with a red exclamation mark and nothing else happened. And I tried many times. But this was before my failed rescue attempts with flashboot.
Wesie said:
* Open the archiv. You'll find a pdf and a file "update.zip" in it. Follow the instruction: copy the file update.zip to the root od the external SD card and start the Tab with the Key-Kombo, which is written there.
? Does it works? What it happen? What does you see?
You can try this a few times, it doesn't matter. Pls give attention, that your Accu has as min. 50%, or after that the TAB start to flash, connect the power-supply during the flash-phase. If you want to repeat, disconnect first at all, the power-supply; if the Tab start to flash, connect the power again.
Click to expand...
Click to collapse
Now I'm unable to enter the recovery mode at all. the key combination has no effect and it always stops at the green acer logo and the Bootloader version message.
Ok, maybe the language check failed.
1- Take the update.zip file and unzip it to a folder.
2- Go to folder "\META-INF\com\google\android"
3- Edit the updater-script and put a # as first character of first line. This will avoid this line to execute: #assert(getprop("ro.product.name") == "a510_...");
4- Zip all files again and name it update.zip.
Copy the zip to the root and try the key-combo once again ( without Power-supply) . Reconnct the power, if the tablet start to flash.
I just tried it and it didn't work.
My problem is that the recovery doesn't even start. I think I need to get the recovery partition working before updating using the update.zip method will work.
Hard issue ...
OK - let's try to activate the Stock-Recovery:
* Download the stockrecovery from here and save the *.img file in the same directory, where your adb / fastboot.exe is available
Switch the board on with following procedure:
> press the Volume+ Key (2 Dots) + Power and switch the Screen Lock few times on / off
with this prcodure you should go into the Fast-Boot-Mode.
Here you can flash the Stock-Recovery:
> fastboot flash recovery <name of the image.img>
If the flash-process is finish
> fastboot reboot
stahai Andrea
Wesie said:
* Download the stockrecovery from here and save the *.img file in the same directory
Click to expand...
Click to collapse
Hmm.. I didn't see any link to the stock recovery. I did find one in the CWM thread called recovery_1_044_00.img and tried to flash that to recovery. The good news: I'm still able to enter fastboot mode and flashing doesn't give me any error. The bad news: It didn't help. I'm still unable to enter recovery mode even after flashing the stock recovery.
erihed claim
chipzter said:
Hmm.. I didn't see any link to the stock recovery. I did find one in the CWM thread called recovery_1_044_00.img and tried to flash that to recovery. The good news: I'm still able to enter fastboot mode and flashing doesn't give me any error. The bad news: It didn't help. I'm still unable to enter recovery mode even after flashing the stock recovery.
Click to expand...
Click to collapse
try the attached stock recovery.img (6.0 MB)
good luck
The good news: I'm still able to enter fastboot mode and flashing doesn't give me any error.
Click to expand...
Click to collapse
OK, first step is done.
If you've flashed the stock-Bootloader, than you can try once again to update the Tablet with the update.zip from the external-SD Card (a description pdf should be already available in the file, which you've download from the Acer-Homepage)
Please ensure, that the update.zip contains a full image ( file-size over 300MB ) and for sure, please disable the language flag.
If you need some help to modify the one line in the script, give me a small hint, I'll make it for you and give you the DownLoad-link.
If the flashprocess ist finish , without any errors, you must only reset your data ( in this case, I'll prefer to use the scenario via Reset-Button)
is it possible you are on jelly bean?
in this case the combination to enter the recovery is:
Power and Vol ** after first vibration release the power button after second vibration release the ** button and press *
@Paulinche
is it possible you are on jelly bean?
in this case the combination to enter the recovery is:
Power and Vol ** after first vibration release the power button after second vibration release the ** button and press *
Click to expand...
Click to collapse
The bootloader is the "old" one (ISC), and I think, that this combination is the new key-stroke for the CWM. If Chipzter try to reanimate the Tab with the org. Stock-SW, so that he can make, after successful flashing the tab, reset the UserDate and booting normal, the online-update:laugh:
Ok, let's start from scratch. Ground zero so to speak.
I'd like to know what bootloader you are running now. ICS or JB?
Reason is, that the recoveries, stock or CWM, must match the bootloader version, because they contain the specific Boot kernel. You can not mismatch these, or nothing's going to work. Not a Rom,not an update.
If you have ICS bootloader, you must have either a stock ICS Recovery, or an ICS CWM.
If you have a JB bootloader, you must have JB stock recovery, or JB CWM.
You can fastboot flash a stock ICS or JB recovery (stock or CWM), then you are able to flash stock roms or custom roms. But they must match, or you're just pissing in the wind.
So what be 'Ye Matey?
MD
If he use the bootloader from the Link, this is the BL from ISC.
Also the SW form the Acer-Server is ISC. So it should match. On other hand: The FW from Acer flashed also the BL to the right version (in recovery mode)
If his Tablett is starting ( maybe with or without Reset of the User-Data), he can use the normal updates via WLAN ( 1st there come an update for ISC, the 2nd update to JB.).
But i this moment, he must bring back to live his Tab....
For sure, I let him not go over the CWM, because something was going wrong, and a "one click tool" was used, after that some partitions was formated and if someone flashed the CWM, he should know, what he do --- here I want minimize the risk.
So I try to give him a hand to bring the Tab back to live with the stock FW, because with CWM, there can be going something wrong. Uncomfortable we're living not in the same country and I have not the Tab in front of me ...
Paulinche said:
try the attached stock recovery.img (6.0 MB)
good luck
Click to expand...
Click to collapse
Thank you for posting that .img file! Unfortunately, I still have no luck initiating the recovery process, even though fastboot seems to succceed:
$ ./fastboot flash recovery recovery.img
sending 'recovery' (6144 KB)...
OKAY [ 1.554s]
writing 'recovery'...
OKAY [ 1.472s]
finished. total time: 3.026s
I would expect (but really have no idea) that if I have a working boot loader (which seems to be the case for me) it should be enough to flash the correct recovery partition to be able to boot into recovery mode. But maybe it depends on data in some other partition like BOOT or SYSTEM. (I'm assuming that the boot partition doesn't contain the boot loader, but just the kernel and RAMdisk for booting the OS contained in SYSTEM)
I've probably messed up both BOOT and SYSTEM in my desperate efforts, but in my defence ( ) my first attempt to flash a new recovery (both stock and custom) failed somehow since the original stock recovery got reflashed automatically on boot even using the correct key combination.
---------- Post added at 01:26 AM ---------- Previous post was at 01:16 AM ----------
Moscow Desire said:
Ok, let's start from scratch. Ground zero so to speak.
I'd like to know what bootloader you are running now. ICS or JB?
Click to expand...
Click to collapse
Hi MD! Thank you for taking the time to reply! I'm really moved by the willingness of people here to try and help me out!
The tablet was running ICS before the meltdown. I was attempting to do an over-the-air update but it froze at around 80% (if memory serves) and I finally had to reboot at which point it got stuck at the "ICONIA TAB" logo after the olympic animation sequence.
I take it that the bootloader is still from ICS since the following text is displayed when trying to boot now:
Bootloader Version 0.04.04-ICS-MDRR (Unlock Mode)
---------- Post added at 01:34 AM ---------- Previous post was at 01:26 AM ----------
Wesie said:
OK, first step is done.
If you've flashed the stock-Bootloader, than you can try once again to update the Tablet with the update.zip from the external-SD Card (a description pdf should be already available in the file, which you've download from the Acer-Homepage)
Click to expand...
Click to collapse
I may be wrong, but I think I've flashed the recovery partition, not the boot loader. I read somewhere that you can't flash the boot loader over USB without using nvflash and that something necessary for that to work on A510 is still not publicly available.
In any case, the recovery still won't start. The device still freezes at the boot loader version message.
By the way, I also tried an older version of the CWM recovery image (6.0.1.4) that I think was ICS compatible.
chipzter said:
Thank you for posting that .img file! Unfortunately, I still have no luck initiating the recovery process, even though fastboot seems to succceed:
$ ./fastboot flash recovery recovery.img
sending 'recovery' (6144 KB)...
OKAY [ 1.554s]
writing 'recovery'...
OKAY [ 1.472s]
finished. total time: 3.026s
I would expect (but really have no idea) that if I have a working boot loader (which seems to be the case for me) it should be enough to flash the correct recovery partition to be able to boot into recovery mode. But maybe it depends on data in some other partition like BOOT or SYSTEM. (I'm assuming that the boot partition doesn't contain the boot loader, but just the kernel and RAMdisk for booting the OS contained in SYSTEM)
I've probably messed up both BOOT and SYSTEM in my desperate efforts, but in my defence ( ) my first attempt to flash a new recovery (both stock and custom) failed somehow since the original stock recovery got reflashed automatically on boot even using the correct key combination.
---------- Post added at 01:26 AM ---------- Previous post was at 01:16 AM ----------
Hi MD! Thank you for taking the time to reply! I'm really moved by the willingness of people here to try and help me out!
The tablet was running ICS before the meltdown. I was attempting to do an over-the-air update but it froze at around 80% (if memory serves) and I finally had to reboot at which point it got stuck at the "ICONIA TAB" logo after the olympic animation sequence.
I take it that the bootloader is still from ICS since the following text is displayed when trying to boot now:
Bootloader Version 0.04.04-ICS-MDRR (Unlock Mode)
---------- Post added at 01:34 AM ---------- Previous post was at 01:26 AM ----------
I may be wrong, but I think I've flashed the recovery partition, not the boot loader. I read somewhere that you can't flash the boot loader over USB without using nvflash and that something necessary for that to work on A510 is still not publicly available.
In any case, the recovery still won't start. The device still freezes at the boot loader version message.
By the way, I also tried an older version of the CWM recovery image (6.0.1.4) that I think was ICS compatible.
Click to expand...
Click to collapse
Remember that the sequence to boot to stock recovery, is different in ICS than the sequence steps for JB. I guess this changed with the release of JB. Honestly, can't remember how to boot to recovery on ICS (I always use adb, but that won't work for you.) At least on the 700 it did.
If the recovery.img flashed successfully, then there's no reason why you shouldn't be able to boot to it. Don't know the sequence for the ICS 510, but on the A500, it was vol- and pwr.
Another idea, is to see if anybody has a boot.img, system.img and flexrom.img for ICS. Then you can simply fastboot it.
As with the bootloader, it's correct. You have to use NVFlash to flash the .bin. You can however, flash a bootloader.blob via CWM though. I helped a person last month get his tab straight using that method.
MD
I still have no luck initiating the recovery process
Click to expand...
Click to collapse
Does you've follow the instruction which Acer attached?
If the original update.zip failed in the beginning, you must modify the first line in the update.zip [add a # in front; thats all]
META-INF\com\google\android\updater-script
First line is simular :
Code:
assert(getprop("ro.product.name") == "a510_ww_gen1");
change it to
Code:
#assert(getprop("ro.product.name") == "a510_ww_gen1");
Please give an attention, that you does not make the change with a normal Windows-Editor ( diff. CR&LF ). PLease use Notepad++, Textpad or a simular editior...
Another idea, is to see if anybody has a boot.img, system.img and flexrom.img for ICS
Click to expand...
Click to collapse
I have all 3 files (German) from my Tab, after CWM, root and AD-free. This means, that this is not 100% original and the Tab reject the online-Update.
That's the reason, that I was going also the way via "Back to stock" which is described in the attached pdf. After the Tab was finish to flash the stock-FW, the TAB stocks at the point with the Olympic rings. Here a RESET of all User-data (Factory-Reset) must be done and the Tab start without any error. Now I was able to received all online-Updates and the TAB was up-to-date (Stock-FW).
After time, the new CWM was published ... but this is a another story. First of all, the Tab should be flash the upgrade.zip, booting, and update by hishelf via WLAN
Wesie said:
you does not make the change with a normal Windows-Editor ( diff. CR&LF )
Click to expand...
Click to collapse
and do not use WinRar to save the changed zip, you can use 7zip for this.
In the case Wesie will allow you to use fastboot you can try this:
you can install the complete firmware.zip using fastboot "fastboot update xxx.zip"
or you can search for all the five .img files and flash them with fastboot "fastboot flash [partition] [imagefile.img]"
- recovery.img
- bootloader.img
- boot.img
- system.img
- flexrom.img (partition name is flex)
for a bootable tablet you only need bootloader, boot and system - also you can try some custom ROMs
Don't know what's happen in the meantime : no response form chipzter at all . Maybe the Tab is working, maybe not
@Paulinche
The tip to flash the complete upgrade.zip via fastboot is nice :good:
I haven't know this one: THX!
Moscow Desire said:
Remember that the sequence to boot to stock recovery, is different in ICS than the sequence steps for JB. I guess this changed with the release of JB. Honestly, can't remember how to boot to recovery on ICS (I always use adb, but that won't work for you.) At least on the 700 it did.
Click to expand...
Click to collapse
The key sequence to enter recovery that worked before (although the recovery process itself did not) was to hold down the two-dots button while powering on and releasing the power button when it vibrates. I assume that it's the boot loader that reacts to the key presses and since I still have the ICS boot loader, the recovery key sequence should be the same. Besides, there's no second vibration if I keep pressing the two-dots button.
Moscow Desire said:
If the recovery.img flashed successfully, then there's no reason why you shouldn't be able to boot to it. Don't know the sequence for the ICS 510, but on the A500, it was vol- and pwr.
Click to expand...
Click to collapse
Yeah, that's what I can't figure out. Why doesn't it boot into recovery, no matter what kind of recovery.img I flash.
Moscow Desire said:
Another idea, is to see if anybody has a boot.img, system.img and flexrom.img for ICS. Then you can simply fastboot it.
Click to expand...
Click to collapse
If any one has those three .img files, I'd appreciate it a lot if I could get copies of them and see if it would help revive my tablet. All A510 owners I know have all upgraded to JB. :crying:
Moscow Desire said:
As with the bootloader, it's correct. You have to use NVFlash to flash the .bin. You can however, flash a bootloader.blob via CWM though. I helped a person last month get his tab straight using that method.
Click to expand...
Click to collapse
That was my original plan. If I could get the CWM recovery working, I'd stand a chance of restoring the device using an official update file.
---------- Post added at 11:30 PM ---------- Previous post was at 11:22 PM ----------
Wesie said:
Does you've follow the instruction which Acer attached?
If the original update.zip failed in the beginning, you must modify the first line in the update.zip [add a # in front; thats all]
META-INF\com\google\android\updater-script
Click to expand...
Click to collapse
I was pretty sure that would not work since I no longer get the "Booting recovery kernel image" image when I try to enter recovery mode. And since recovery mode won't start, it will not even look for the update.zip file. I tried it just to make sure, but it didn't work. I'm on a mac so I used the built in zip function.
---------- Post added at 11:38 PM ---------- Previous post was at 11:30 PM ----------
Paulinche said:
you can install the complete firmware.zip using fastboot "fastboot update xxx.zip"
Click to expand...
Click to collapse
I tried to use "fastboot update" but it seems that the content of the zip file is different from the zip file used for SD card updates because fastboot outputs the following error messages:
./fastboot update ~/Downloads/iconia/OS_Acer_RV28RC01.EMEA.CUS1_A40I_A/update.zip
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
Does anyone know where I might find a firmware.zip file for A510 that works with fastboot? That would be awesome!
---------- Post added at 11:42 PM ---------- Previous post was at 11:38 PM ----------
Wesie said:
Don't know what's happen in the meantime : no response form chipzter at all . Maybe the Tab is working, maybe not
Click to expand...
Click to collapse
Sorry for not staying in touch. But I promise to let you guys know if I get my tablet working! (Which it isn't in case there was any doubt )
OK,
I believe, you've the bootloader from ISC on the TAB. (please write the No. which is in the Display a ahort time during boot)
If you want to flash a version - and you didin't know which one you have had - I think, this one is not a bad one: OS_Acer_RV28.RC02.WW.GEN1_A40I_A
Extract the update.zip from the archiv and copy this one on root of the external-SD card.
Normally you can start the flash procedure with:
Hold the Volume ** (don't release)
press and Hold the POWER (don't release)
TILL you can read "Recovery in the upper left corner
or following the description in the pdf:
Hold the volume ** (don't release)
Hold Power (don't release)
Once "Power"key white LED lights, released the POWER BUT still hold the Volume**
If you can read "Erasing cache .... " released the Volume**
than the TAB should start the flashing. If the update failed (about the version-check), than we can modify the update.zip.
Please confirm, that the Recovery process is started ...and also was is happen, does the Tab start to flash, interrrupt after a few second ... does not start to flash ...
All A510 owners I know have all upgraded to JB
Click to expand...
Click to collapse
so as written before:
I've a backup from my Tab - before i've upgrade to JB- from the DE-Version, but you can selected English as language, too - after CWM, root and install "ad-free". If you want, you can have a copy of this files.
Wesie said:
OK,
I believe, you've the bootloader from ISC on the TAB. (please write the No. which is in the Display a ahort time during boot)
If you want to flash a version - and you didin't know which one you have had - I think, this one is not a bad one: OS_Acer_RV28.RC02.WW.GEN1_A40I_A
Click to expand...
Click to collapse
The only thing displayed during boot is the following line:
Bootloader Version 0.04.04-ICS-MDRR (Unlock Mode)
Wesie said:
Hold the Volume ** (don't release)
press and Hold the POWER (don't release)
TILL you can read "Recovery in the upper left corner
or following the description in the pdf:
Hold the volume ** (don't release)
Hold Power (don't release)
Once "Power"key white LED lights, released the POWER BUT still hold the Volume**
If you can read "Erasing cache .... " released the Volume**
Click to expand...
Click to collapse
I've tried both methods several times but absolutely nothing happens. It still just says Bootloader Version 0.04.04-ICS-MDRR (Unlock Mode)
Wesie said:
so as written before:
I've a backup from my Tab - before i've upgrade to JB- from the DE-Version, but you can selected English as language, too - after CWM, root and install "ad-free". If you want, you can have a copy of this files.
Click to expand...
Click to collapse
I would really appreciate copies of those files! I know enough German to find my way around a computer. At least enough to switch the language to English!
Related
When I hold the power button plus Volume down key I am only getting two options. One is to wipe data and the other is to enter USB Fastboot mode. I just upgraded to the latest TWRP recovery and when I click the Wipe icon the TWRP splash screen shows up for a second. What I am hoping is that someone has some insight as to why the recovery icon has disappeared and how to get it back. Usually I am not the person asking the questions generally I am the one answering. If anyone has a clue it would definitively help. I did search and found a couple threads where something similar happened but there was no direct answer as how to fix it. Please help.
stedrocklp said:
When I hold the power button plus Volume down key I am only getting two options. One is to wipe data and the other is to enter USB Fastboot mode. I just upgraded to the latest TWRP recovery and when I click the Wipe icon the TWRP splash screen shows up for a second. What I am hoping is that someone has some insight as to why the recovery icon has disappeared and how to get it back. Usually I am not the person asking the questions generally I am the one answering. If anyone has a clue it would definitively help. I did search and found a couple threads where something similar happened but there was no direct answer as how to fix it. Please help.
Click to expand...
Click to collapse
I had a similar issue when I restored a TWRP backup I made with pre version 2.2.1. I was able to get help from the Dees_Troy on IRC.
Notes from IRC conversation
Whatever you restored from your pre TWRP 2.2.1 old backup is not a kernel. The dev that made the original device configuration files for the 300 couldn't find boot . So he just threw boot onto the wrong partition you need to install a working kernel via fastboot.
Steps that got me backup and running.
1. Flashed latest TWRP via fastboot. 'fastboot -i 0x0B05 flash recovery twrp.blob' rebooted
2. Downloaded a cm9 rom and opened the zip file and extract boot.blob . Flashed with 'fastboot -i 0x0B05 flash boot boot.blob' then rebooted.
Now TWRP recovery worked and I was able to install a new custom rom.
Backups made with version 2.2.1 or grater work correctly for me now.
Thank you Thank you Thank you!
brbjr said:
I had a similar issue when I restored a TWRP backup I made with pre version 2.2.1. I was able to get help from the Dees_Troy on IRC.
Notes from IRC conversation
Whatever you restored from your pre TWRP 2.2.1 old backup is not a kernel. The dev that made the original device configuration files for the 300 couldn't find boot . So he just threw boot onto the wrong partition you need to install a working kernel via fastboot.
Steps that got me backup and running.
1. Flashed latest TWRP via fastboot. 'fastboot -i 0x0B05 flash recovery twrp.blob' rebooted
2. Downloaded a cm9 rom and opened the zip file and extract boot.blob . Flashed with 'fastboot -i 0x0B05 flash boot boot.blob' then rebooted.
Now TWRP recovery worked and I was able to install a new custom rom.
Backups made with version 2.2.1 or grater work correctly for me now.
Click to expand...
Click to collapse
That was definitely the problem and I had been trying everything for the past two days. I appreciate you taking the time to reply.
asus tf300 help
brbjr said:
I had a similar issue when I restored a TWRP backup I made with pre version 2.2.1. I was able to get help from the Dees_Troy on IRC.
Notes from IRC conversation
Whatever you restored from your pre TWRP 2.2.1 old backup is not a kernel. The dev that made the original device configuration files for the 300 couldn't find boot . So he just threw boot onto the wrong partition you need to install a working kernel via fastboot.
Steps that got me backup and running.
1. Flashed latest TWRP via fastboot. 'fastboot -i 0x0B05 flash recovery twrp.blob' rebooted
2. Downloaded a cm9 rom and opened the zip file and extract boot.blob . Flashed with 'fastboot -i 0x0B05 flash boot boot.blob' then rebooted.
Now TWRP recovery worked and I was able to install a new custom rom.
Backups made with version 2.2.1 or grater work correctly for me now.
Click to expand...
Click to collapse
hey Im sry I never posted here b4 but I think this thread is the closest to the problem I have. My tf300 jad 4.1.1 ota update, i decided to change the rom since it seemed to have so many advantages. I installed TWRP correctly and according to the process I made later with debugfs tool I got root. It was all good but then I messed up, I installed Hydroponyc rom without backing up my rom and from then on, all hell broke loose. I can acces Clockworck (I changed TWRP for clock thought it might help......) and fastboot but any rom I install it doesnt go past the first asus logo that says device is unlocked on the upper left of the screen. Is there anyway u could help me please? Forgive my noobness I never posted here b4 I dont know if Im breaking any rule but i dont wanna wind up with a very expensive paper weight.
Did I brick it?
manegonzalez said:
hey Im sry I never posted here b4 but I think this thread is the closest to the problem I have. My tf300 jad 4.1.1 ota update, i decided to change the rom since it seemed to have so many advantages. I installed TWRP correctly and according to the process I made later with debugfs tool I got root. It was all good but then I messed up, I installed Hydroponyc rom without backing up my rom and from then on, all hell broke loose. I can acces Clockworck (I changed TWRP for clock thought it might help......) and fastboot but any rom I install it doesnt go past the first asus logo that says device is unlocked on the upper left of the screen. Is there anyway u could help me please? Forgive my noobness I never posted here b4 I dont know if Im breaking any rule but i dont wanna wind up with a very expensive paper weight.
Click to expand...
Click to collapse
I kinda have the same problem! Tried the boot.blob thing but, sadly, that didn't work for me ;(
solution
mizifih said:
I kinda have the same problem! Tried the boot.blob thing but, sadly, that didn't work for me ;(
Click to expand...
Click to collapse
hey I was super frustrated by this but I took some time out and then I found this post I tried it and it worked perfectly give it a shot
Looks like partition sizes chaged with the Asus update. I couldn't flash CM10 or any other rom as well (signature mismatch). If you installed the official 4.1.1 update, you need to manually install it again. Older versions and rollbacks wont work unless you push to some trickery mmcblk0p4, but that's another thread in itself
Download the JB update from Asus's website (if you still have it, that's fine) and extract the blob file. Put the blob file in teh same directory as your fastboot. Boot your TF300 into bootloader and enter:
fastboot -i 0x0B05 flash system blob
It will take a while to install, so be patient. Hope this helps
manegonzalez said:
hey I was super frustrated by this but I took some time out and then I found this post I tried it and it worked perfectly give it a shot
Looks like partition sizes chaged with the Asus update. I couldn't flash CM10 or any other rom as well (signature mismatch). If you installed the official 4.1.1 update, you need to manually install it again. Older versions and rollbacks wont work unless you push to some trickery mmcblk0p4, but that's another thread in itself
Download the JB update from Asus's website (if you still have it, that's fine) and extract the blob file. Put the blob file in teh same directory as your fastboot. Boot your TF300 into bootloader and enter:
fastboot -i 0x0B05 flash system blob
It will take a while to install, so be patient. Hope this helps
Click to expand...
Click to collapse
Doing it now. I'll update as soon as I finish it. Thank you very much for your reply.
UPDATE 1: I can see the shiny-silver ASUS and the progress circles, waiting to see what happen!
UPDATE 2: Setting up Jellybean now (Welcome setup)!
UPDATE 3: Looks like it's working!
Dude, thank you so much! I'll fool around with it. Is there a root method working already? I was wondering if there's a way to restore my backups, at least the ones I made for my gaming progress.
manegonzalez said:
hey Im sry I never posted here b4 but I think this thread is the closest to the problem I have. My tf300 jad 4.1.1 ota update, i decided to change the rom since it seemed to have so many advantages. I installed TWRP correctly and according to the process I made later with debugfs tool I got root. It was all good but then I messed up, I installed Hydroponyc rom without backing up my rom and from then on, all hell broke loose. I can acces Clockworck (I changed TWRP for clock thought it might help......) and fastboot but any rom I install it doesnt go past the first asus logo that says device is unlocked on the upper left of the screen. Is there anyway u could help me please? Forgive my noobness I never posted here b4 I dont know if Im breaking any rule but i dont wanna wind up with a very expensive paper weight.
Click to expand...
Click to collapse
you can flash the file named "blob" extracted from stock JB zip file(download from ASUS website,now there is only US SKU,10.4.2.29),it's about 7XX MB,then use the command "fastboot -i 0x0B05 flash system blob" (put the blob in the same directory with fashboot),It will restore your JB OS.till now,other rom can not work by this way.
jijitax4 said:
you can flash the file named "blob" extracted from stock JB zip file(download from ASUS website,now there is only US SKU,10.4.2.29),it's about 7XX MB,then use the command "fastboot -i 0x0B05 flash system blob" (put the blob in the same directory with fashboot),It will restore your JB OS.till now,other rom can not work by this way.
Click to expand...
Click to collapse
What if you can only boot to APX mode? I only have the option of using that because my unlocked bootloader got erased in the process of updating to JB. Is there a way to install a bootloader using fastboot? Or will it only work with an existing bootloader?
In other words, when I issue the fastboot command
fastboot -i 0x0B05 flash system blob
I get "waiting on device" and nothing happens after that.
Thank you, this worked !!!!!!
Rooting- error: cannot load "flashboot flash recovery r1-modaco-reco... .img"
I'm rooting my HTC One S the first time. And I was stupid and thought that HTC One X Clockworkmod flash would work.
Now I know how flashing and clockworkmod installing works but before that I accidentally flashed the One X command: "fastboot flash recovery recovery-clockwork-touch-5.8.2.7-endeavoru.img" and now when I go to recovery it gives me a red text and nothing works.
I searched everywhere for a guide to remove it and did not found. So I thought I could flash it over with an One S flash, but then when I entered the command: "fastboot flash recovery r1-modaco-recovery-clockwork-touch-ville.img" It gave me this: "error: cannot load 'recovery r1-modaco-recovery-clockwork-touch-ville.img'. My phone is connected perfectly, when I type 'fastboot devices' it shows me my phone is there.
So I think this is not a big problem for developers. Can anyone tell me what to flash or do to get rid of the One X recovery? Otherwise I just have to live with a phone with unlocked Bootloader and no access to root
Do you have the IMG I the directory from which you are running fast boot?
edscholl said:
Do you have the IMG I the directory from which you are running fast boot?
Click to expand...
Click to collapse
Ofcourse
rixrasta said:
Ofcourse
Click to expand...
Click to collapse
mabey I should just do a factory reset :/
Why don't you dl goo manager from market, open it and open menu and tap on Install OpenScriptRecovery and let it install twrp--although, I guess if you aren't rooted yet that won't work
Did you try fastbooting the cwmr from here--
http://www.clockworkmod.com/rommanager
Did you check the md5 on the modaco recovery before flashing
At the red text did you try hitting vol+ or vol- not sure which one takes you to stock recovery. What does red text say--
Did you hard reboot with holding down vol- and power at same time then release pwr after screen goes off and continue to hold vol-
Not sure what is wrong, just giving some ideas--
rugmankc said:
Why don't you dl goo manager from market, open it and open menu and tap on Install OpenScriptRecovery and let it install twrp--although, I guess if you aren't rooted yet that won't work
Did you try fastbooting the cwmr from here--
Did you check the md5 on the modaco recovery before flashing
At the red text did you try hitting vol+ or vol- not sure which one takes you to stock recovery. What does red text say--
Did you hard reboot with holding down vol- and power at same time then release pwr after screen goes off and continue to hold vol-
Not sure what is wrong, just giving some ideas--
Click to expand...
Click to collapse
Tyvm for your reply,
the cwmr for HTC One S does not exist any more on the page you gave me. There's only a blank page if you click on it
yes I did hard reboot and the red text says: This build is for development purposes only do not distribute outside HTC without HTC's written permission. Failure to comply my lead to legal action.
I tried the superboot from this site: htt p://w ww.m odaco.co m/to pic/352493-how-to-root-your-htc-one-s-for-windows-mac-and-linux/
This just brought up the recovery message again...
Then I tried flashing these files:h ttp://ww w.m odaco.c om/topic/353006-interim-clockworkmod-touch-recovery-for-the-htc-one-s-stock-download/
no help.
Any other ideas I should try?
However the flashing went through this time and there were no error, but the recovery is still f**ked.
rixrasta said:
Tyvm for your reply,
the cwmr for HTC One S does not exist any more on the page you gave me. There's only a blank page if you click on it
yes I did hard reboot and the red text says: This build is for development purposes only do not distribute outside HTC without HTC's written permission. Failure to comply my lead to legal action.
I tried the superboot from this site: htt p://w ww.m odaco.co m/to pic/352493-how-to-root-your-htc-one-s-for-windows-mac-and-linux/
This just brought up the recovery message again...
Then I tried flashing these files:h ttp://ww w.m odaco.c om/topic/353006-interim-clockworkmod-touch-recovery-for-the-htc-one-s-stock-download/
no help.
Any other ideas I should try?
However the flashing went through this time and there were no error, but the recovery is still f**ked.
Click to expand...
Click to collapse
Try this twrp .img
http://teamw.in/project/twrp2/100
The red text will stay till you relock, I believe, or flash stock recovery--
twrp recovery is the way to go. Me too I couldn't install the clockwork one!
rugmankc said:
Try this twrp .img
h ttp://team w. in/projec t/twrp 2/100
The red text will stay till you relock, I believe, or flash stock recovery--
Click to expand...
Click to collapse
I flashed the "openrecovery-twrp-2.2.2.0-ville.img". Didnnt change anything :/
sorry to hear that, not sure what else to do, so you still have onex recovery?
even if you run an ruu, i think you still have to flash the stock recovery first. haven't read up on that much, as never needed to run one
Don't know if trying to flash the stock recovery will help. I have the original one at home, but not sure if that is what they still call stock recovery with new ota's having come out
If it cannot load it, you probably spelt the name wrong. rename the image file to recovery.img (make sure it isn't .img.img) and flash that. Make sure the file path is correct! (e.g fastboot flash recovery C:\Users\Me\Desktop\recovery.img)
usaff22 said:
If it cannot load it, you probably spelt the name wrong. rename the image file to recovery.img (make sure it isn't .img.img) and flash that. Make sure the file path is correct! (e.g fastboot flash recovery C:\Users\Me\Desktop\recovery.img)
Click to expand...
Click to collapse
no no, the flashing finished successfully. I entered "fastboot flash recovery openrecovery-twrp-2.2.2.0-ville.img" and then it flashed without problems, but in the phone it didn't change a thing. If I enter recovery then there's the android icon with a white background and under it is the red text.
But keep guessing, maybe I really am doing something stupid wrong
When I go to Fastboot USB mode with my phone then I open the command prompt and firstly type "cd c:\CWM" (the folder where my flashing files are). Then secondly I type "fastboot devices" (just to be shure). And thirdly depending on what I am flashing I type "fastboot flash recovery name.img". I have tried "fastboot flash recovery openrecovery-twrp-2.2.2.0-ville.img", "fastboot flash recovery r2-modaco-recovery-clockwork-touch-ville" and "fastboot flash recovery ville_recovery_signed". Every one of them finishes successfully but doesn't change anything in the phone. I already have recovery-clockwork-touch-5.8.2.4-ville.zip and CWM-SuperSU-v0.96.zip in my phones directory to install root when I get into the recovery. In the C:\CWM folder in my computer are these files:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
(these where exctracted from fastboot.zip)
openrecovery-twrp-2.2.2.0-ville.img
r2-modaco-recovery-clockwork-touch-ville.img
ville_recovery_signed.img
the text won't disappear with unlocked bootloader, so that's ok.
Try to boot into bootloader hit fastboot reboot bootloader and then choose recovery. It can take a while to boot into recovery.
Gesendet von meinem HTC One S mit Tapatalk 2
stunner2002 said:
the text won't disappear with unlocked bootloader, so that's ok.
Try to boot into bootloader hit fastboot reboot bootloader and then choose recovery. It can take a while to boot into recovery.
Gesendet von meinem HTC One S mit Tapatalk 2
Click to expand...
Click to collapse
fastboot ->reboot bootloader ->bootloader ->recovery. Absolutely no change, It took half a second to bring up the "HTC quietly brilliant" logo and about two seconds for the red text to appear under it. No buttons work after that and I just have to hold the power button down to shut it down.
And by bootloader is unlocked!
As stunner said above it can take a while to boot into recovery, how long have you waited?
Give it a few minutes... Also you could try flashing stock recovery, it is distributed in the all-in-one tool and also in paulobriens posts about superboot. Then run a RUU.
But my best to would be to try fastboot booting a custom recovery, "fastboot boot cwm.img".
If this is the thing where you go int recovery for a millisecond and then back to the 'red text' screen (you have to watch carefully to notice), you should try erasing your cache in fastboot mode.
fastboot erase cache
Click to expand...
Click to collapse
-Jobo
It's gotten a little confusing and some suggestions are being repeated. I wonder if the android icon you are describing is the stock recovery symbol. At that screen have you tried to press vol+ or maybe volume-. I forget which one takes you to stock recovery. May want to check on that.
Also, have you tried typing "fastboot boot recovery" to go straight to recovery, bypassing htc restrictions
Here is very early stock recovery--not sure if it is still considered "stock" with new versions out now--I did mention that earlier--
https://www.dropbox.com/sh/yhrq0tia8512rj9/go28kc1NeP/ville_recovery_signed.img
I did have issues fastbooting recovery before. You can as mentioned try fastboot erase cache before fastbooting recovery. And change the name of your recovery to just recovery.img before you fastboot.
I assume you have nandroid backup on phone and copies of it and sdcard backup on pc.
I think when I had issues with recovery sticking it was my N1 and I typed "fastboot erase system" first, then fastbooted recovery. Then wiped all and restored nandroid. I am not sure we can do that on the 1s with no s-off. Someone else may know.
Can you access sdcard where you could reformat it fat32 thru a windows formatter program. Of course copy all to pc first. Sometimes sdcard formats help things you wouldn't expect it to.
Some folks have reported formatting works better thru phone on the 1s, maybe because it is an internal card. I did it once and think I had to redo it thru phone. But, if it gets recovery working, no big deal.
All these are suggestions and as the devs say--at your own risk--
I thought you said you said in first post, phone works, just no root capabilty. If that is true it should be fixable--I hope.
---------- Post added at 05:06 PM ---------- Previous post was at 04:32 PM ----------
rixrasta said:
no no, the flashing finished successfully. I entered "fastboot flash recovery openrecovery-twrp-2.2.2.0-ville.img" and then it flashed without problems, but in the phone it didn't change a thing. If I enter recovery then there's the android icon with a white background and under it is the red text.
But keep guessing, maybe I really am doing something stupid wrong
When I go to Fastboot USB mode with my phone then I open the command prompt and firstly type "cd c:\CWM" (the folder where my flashing files are). Then secondly I type "fastboot devices" (just to be shure). And thirdly depending on what I am flashing I type "fastboot flash recovery name.img". I have tried "fastboot flash recovery openrecovery-twrp-2.2.2.0-ville.img", "fastboot flash recovery r2-modaco-recovery-clockwork-touch-ville" and "fastboot flash recovery ville_recovery_signed". Every one of them finishes successfully but doesn't change anything in the phone. I already have recovery-clockwork-touch-5.8.2.4-ville.zip and CWM-SuperSU-v0.96.zip in my phones directory to install root when I get into the recovery. In the C:\CWM folder in my computer are these files:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
(these where exctracted from fastboot.zip)
openrecovery-twrp-2.2.2.0-ville.img
r2-modaco-recovery-clockwork-touch-ville.img
ville_recovery_signed.img
Click to expand...
Click to collapse
you should also have adb.exe if you are using adb--
frdd said:
As stunner said above it can take a while to boot into recovery, how long have you waited?
Give it a few minutes... Also you could try flashing stock recovery, it is distributed in the all-in-one tool and also in paulobriens posts about superboot. Then run a RUU.
But my best to would be to try fastboot booting a custom recovery, "fastboot boot cwm.img".
Click to expand...
Click to collapse
Okay I waited for 10 minutes, nothing happens. I've even tried to hold down all the button combinations(with the three buttons) for a few minutes.
I've tried flashing everything and fastboot boot just takes me directly to the recovery with the red text. I flashed both the recoveries in the all-in-one tool.
As I know absolutely nothing about RUU(only what the letters stand for) then I'd rather not do that because I read from some threads that RUU has quite a high chance to mess up your phone. Or if you direct me to a tutorial that u insure me that is 100% good then I could give it a go : D
[
I think I have made the same mistake of flash recovery, but I can not get into cwm recovery, I only appear for 1 second the recovery, then restarts and returns to the operating system. SD card, all changes are discarded when you restart the phone, which is also only if I try to install or remove some utility. Can not install any recovery, even if fastboot works well and looks real mind install the recovery but when I reboot, it returns to its previous behavior, with recovery not working. I tried to install the recovery in every way, from fastboot, from All in one with quickroot, but none of these operations has changed the state of the system.
Unfortunately you can not install a Stock RUU because the bootloader unlocked and the recovery is not the stock, and especially not when there is no tutorial to follow to bring this situation to the ONE S, to its original state
Hopefully someone will be able to find a solution to your and my problem.
One option you guys may need to entertain, if applicable, would be to exchange phones with Carrier. Worth a shot--
I have not heard of this exact issue, but most comments say if you can't boot to recovery you are bricked--
Has anyone tried "fastboot boot recovery" command in terminal window?
Not sure if this belongs over here in Q/A as a new thread, or if I should append this to shabbypenguin's root thread. I am attempting to root my Photon Q following shabbypenguin's method. I downloaded the latest SDK bundle, installed latest Motorola drivers, successfully unlocked the bootloader.
I can't seem to get any recovery images to flash correctly at this point, though. When I run "fastboot flash recovery cwmrecovery.img" I get the following output:
Code:
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (6632 KB)...
OKAY [ 0.519s]
writing 'recovery'...
OKAY [ 2.363s]
finished. total time: 2.885s
Not sure if "Variable not supported" is a normal message or not, but otherwise it appears to have completed successfully? But when I reboot into recovery mode, I always get the android with a red triangle screen, like this. I have tried flashing shabbypenguin's CWM recovery image, the latest TWRP recovery image, and the stock recovery image linked to in this thread. Same result every time; red triangle screen.
My phone is running the updated OTA build (77.8.10). Is that what is hindering my ability to flash and root successfully? Not sure where else I could have gone wrong. The only other thing I can think of is that before starting with all this, I did have encryption enabled on the phone. But before unlocking the bootloader and attempting to flash CWM recovery, I performed a factory reset to remove the encryption.
UPDATE: it doesn't actually seem like the recovery images are getting flashed at all. At first I thought something was being corrupted (given the red triangle).
But if I press the Up/Down Vol buttons on that screen, I get the Android system recovery utility menu. So if a recovery flash had occurred, this would have been overwritten, right?
I'd be grateful for any suggestions of what to try at this point.
i've never seen that bootloader message before, but it seems like your recovery might be getting flashed back to stock when you reboot. another guy had this issue, you might hopefully be able to solve it by reading this short thread here:
http://forum.xda-developers.com/showthread.php?t=2017748
edit; in short, you could try rooting with Motofail2go: http://forum.xda-developers.com/showthread.php?t=1940594, then use your SU priviledge to rename recovery-from-boot.p to recovery-from-boot.bak,(in /system), then reflash recovery of choice and it should stick.
Thanks yogi! That was indeed my problem as well. I hadn't come across that thread in my initial searching, so I really appreciate your ultra fast response and the sage solution you figured out in the earlier thread. You rock!
Ah, glad that worked for you also! I'm not sure why some people have had to do that, while I don't think I ever did(I have a file named recovery-from-boot.bak, but I don't think I actively renamed it). I am also not sure why we have have an unlockable bootloader, yet without a 3rd-party exploit, some people are getting stuck
In shabbys supersu zip the script had it rename that boot on recovery file. Maybe people are skipping that step after flashing recovery or moto changed the file location and it doesnt match shabbys original script now.
Sent from my XT897 using Tapatalk 2
Rangerbry said:
In shabbys supersu zip the script had it rename that boot on recovery file. Maybe people are skipping that step after flashing recovery or moto changed the file location and it doesnt match shabbys original script now.
Sent from my XT897 using Tapatalk 2
Click to expand...
Click to collapse
Ah ok, i figured something was renaming that file. The thing is, is there a way to boot straight into recovery from the bootloader? I've always had to boot into the system and then adb reboot recovery.
just hold up like normal after
fastboot reboot
ah yes ok, i guess people should do that after flashing recovery so they can get SU flashed before losing their recovery. and we'll see if Shabby's SU zip still disables that recovery file. i guess that's sort of standard procedure on phones in general, but i don't think i ever did that on this device.
Nice, thanks! Yeah, I was booting back in to system and doing adb reboot recovery as well. The couple blog write-ups I was following weren't clear on that aspect, but then, using the hardware buttons to force it directly to recovery makes perfect since; wondering why I didn't think about that at the time.
Guys!
I have the same problem!
My phone version XT925:
4.1.2
unlocked bootloader
no ROOT
Phone not loading to recovery! so I can't install SU.zip, to get ROOT and rename recovery-from-boot.p.
And because my version 4.1.2 I can't use exploit to get root.
I am realy need your help!
Alex42rus said:
Guys!
I have the same problem!
My phone version XT925:
4.1.2
unlocked bootloader
no ROOT
Phone not loading to recovery! so I can't install SU.zip, to get ROOT and rename recovery-from-boot.p.
And because my version 4.1.2 I can't use exploit to get root.
I am realy need your help!
Click to expand...
Click to collapse
Have you done the hardware key method?
Power + down till phone resets than power + up will you are in recovery?
Otherwise use this command in fastboot(meaning you have SDK tools and you open a command window in platform tools folder):
adb reboot recovery
than the phone should reboot itself into recovery
let us know if you need anything else
Hinyo said:
Have you done the hardware key method?
Power + down till phone resets than power + up will you are in recovery?
Otherwise use this command in fastboot(meaning you have SDK tools and you open a command window in platform tools folder):
adb reboot recovery
than the phone should reboot itself into recovery
let us know if you need anything else
Click to expand...
Click to collapse
>Power + down till phone resets than power + up will you are in recovery?
Phone goes to boot menu.
if I select recovery, phone try to load it (green horizontal anroid logo), but after some time it start the system.
>adb reboot recovery
the same.
Alex42rus said:
>Power + down till phone resets than power + up will you are in recovery?
Phone goes to boot menu.
if I select recovery, phone try to load it (green horizontal anroid logo), but after some time it start the system.
>adb reboot recovery
the same.
Click to expand...
Click to collapse
This means you have stock recovery.
Flash a custom recovery - TWRP, CWM, OpenRecovery.
If you are having issues with recovery not sticking, there is a thread right below yours which addresses this.
Especially see this post from kabaldan.
arrrghhh said:
This means you have stock recovery.
Flash a custom recovery - TWRP, CWM, OpenRecovery.
Click to expand...
Click to collapse
Yes, I am tring, but when I do it, I have "variable not supported" message.
Console:
C:\adt-bundle-windows-x86_64\sdk\platform-tools>fastboot flash recovery twrp-hdr
ecovery.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (6678 KB)...
OKAY [ 0.502s]
writing 'recovery'...
OKAY [ 1.960s]
finished. total time: 2.465s
C:\adt-bundle-windows-x86_64\sdk\platform-tools>
Alex42rus said:
Yes, I am tring, but when I do it, I have "variable not supported" message.
Click to expand...
Click to collapse
Please read the link I provided above, and see if it helps you. Or the second post in this thread...
arrrghhh said:
Please read the link I provided above, and see if it helps you. Or the second post in this thread...
Click to expand...
Click to collapse
>Stock OTA update contains /system/etc/install-recovery.sh that will re-flash the recovery to stock any time you boot the android system.
>Boot to custom recovery first before starting the android system after the update
This path realy help me! I go to recovery by presing power + up after recovery.
> and remove this script by using the console or adb shell:
adb shell not connected, and I not find console in recovery, but before reboot recovery ask me to remove "re-install recovery"
great thanks !
Had the same problem trying to flash TWRP to my XT926. Flashing multiple versions of CWM or TWRP gave the same results. (bootloader) variable not supported, but flashing would still appear to proceed ok. However the recovery was always jacked somehow. The only thing that would flash correctly (even with the error) was the stock recovery.
I was using minimal adb & fastboot. Clued in off of a thread off of droid rzr forums (cannot post url due to my new user status) I FINALLY realized I needed to replace the included AOSP binaries with the motorola ones.
Upon replacing the binaries flashing proceeded without error & TWRP was installed & running correctly.
So as this thread came up most of the time when searching for solution to my error, I hope this reply helps.
So, in short double check your version of adb fastboot (or its binaries), your usb drivers, & your recovery is appropriate/ latest update for your phone/ firmware.
Sent from my XT926 using XDA Free mobile app
4ndr01dpilot said:
So, in short double check your version of adb fastboot (or its binaries), your usb drivers, & your recovery is appropriate/ latest update for your phone/ firmware.
Click to expand...
Click to collapse
Thanks for this tip. I used the fastboot version from Motopocalypse instead of my standard ADB installation version, and the variable message stopped appearing. :highfive:
I was puzzled for days being stuck in endless "Flashing recovery ..."
In the end I decided, after saying 1 hour waiting a hypothetical "success/congrats message", NOT QUITTING the current fastboot screen, to select the recovery option in this very fastboot menu (on a Razr i : Vol- to highlight recovery item, then Vol+ to select) and bang I was in TWRP menu. What to do next once in, it is another story.
I've followed instructions to unlock my bootloader which is done. I'm not sure if - "Device is unlocked. Status Code 3:" is correct or not, but that is what I see.
After unlocking I flashed TWRP 2.6.3.0-xt1032.img and it flashed correctly according to adb (attached). When I reboot the phone into bootloader and select recovery the screen just goes blank. I also tried "recovery-clockwork-touch-6.0.4.7-falcon.img", which seemed to flash OK in adb. The bootloader screen goes blank when I select recovery on the phone for CWM as well.
Both recovery flashes showed a similar result on the phone - this paste is for CWM
In Moto bootmode:
USB Connected
cmd: getvarartition-type:recovery
cmd: getvar:max-download-size
cmd: download:07b2000
cmd: flash:recovery
Mismatched partition zize (recovery)
The phone has stock Android 5.0.2 installed and still works, but I can't get any further than flashing the recovery image in adb. I did flash the logo.bin in adb and it seemed to flash correctly .
I'm running Windows 8.1, USB 3 ports.
Is there something I'm missing, or a different way to do the root? I'm stuck at this point, but luckily can run with the stock ROM for now.
I would appreciate any help I can get, Thanks
both recoveries you have used are seemingly outdated for lollipop bootloader. i would suggest you to try out the newly built TWRP (which is not yet publicly released) cant post URLs here yet but search for '[RECOVERY][falcon]TWRP 2.8.7.0 touch recovery [2015-06-24]' here in XDA
---------- Post added at 11:14 PM ---------- Previous post was at 11:03 PM ----------
here is the URL: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
koshikas said:
both recoveries you have used are seemingly outdated for lollipop bootloader. i would suggest you to try out the newly built TWRP (which is not yet publicly released) cant post URLs here yet but search for '[RECOVERY][falcon]TWRP 2.8.7.0 touch recovery [2015-06-24]' here in XDA
---------- Post added at 11:14 PM ---------- Previous post was at 11:03 PM ----------
here is the URL: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Click to expand...
Click to collapse
I tried and same result. After flashing with adb - disconnect USB , boot into bootloader, down to recovery, push power button and blank screen. Normal power up does the same thing as does factory. Ad I can confirm the version is 41.18.
Thanks
jjcdennis said:
I tried and same result. After flashing with adb - disconnect USB , boot into bootloader, down to recovery, push power button and blank screen. Normal power up does the same thing as does factory. Ad I can confirm the version is 41.18.
Thanks
Click to expand...
Click to collapse
these blank screens are quiet frustrating, can you get hold of the stock firmware for your model and flash back the stock recovery first and then try again with latest custom recoveries
koshikas said:
these blank screens are quiet frustrating, can you get hold of the stock firmware for your model and flash back the stock recovery first and then try again with latest custom recoveries
Click to expand...
Click to collapse
I had problems last weekend after trying to go to CM12.1 after rooting and ending up in a bootloader loop. I ended up using a KitKat stock rom and mfastboot2 and typed in all of the lines - it worked. The phone then updated to 5.0.2 via auto update.
I don't have that stock from the network update, but found this one - XT1034_Retail_Canada_502_Stock_Untouched which contains 3 files, Meta-inf, system and boot.img. I don't see a recovery in the folder. I'm not really sure what to look for and how to do this.
Thanks
jjcdennis said:
I had problems last weekend after trying to go to CM12.1 after rooting and ending up in a bootloader loop. I ended up using a KitKat stock rom and mfastboot2 and typed in all of the lines - it worked. The phone then updated to 5.0.2 via auto update.
I don't have that stock from the network update, but found this one - XT1034_Retail_Canada_502_Stock_Untouched which contains 3 files, Meta-inf, system and boot.img. I don't see a recovery in the folder. I'm not really sure what to look for and how to do this.
Thanks
Click to expand...
Click to collapse
make sure you get exactly a stock ROM that is made for your model. trying firmware made for other models is surefire way of bricking you phone. usually the stock firmware images ending with '*.xml.zip' do have a 'recovery.img' in them.
koshikas said:
make sure you get exactly a stock ROM that is made for your model. trying firmware made for other models is surefire way of bricking you phone. usually the stock firmware images ending with '*.xml.zip' do have a 'recovery.img' in them.
Click to expand...
Click to collapse
Thanks again.
If I find a correct ROM (I do have a KitKat 4.4.4 version), do I flash back with adb, or with mfastbootv2?
The ROM I showed was from here: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
I have also found a firmware link on this thread "http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795" that looks to be in the correct format. There are thorough instructions on how to flash the firmware, but I am not sure if this will fix my issue or not.
Would appreciate any advice on how to proceed.
Thanks
I finally understood your comment "...can you get hold of the stock firmware for your model and flash back the stock recovery first and then try again with latest custom recoveries". I got a copy of the stock firmware, extracted the recovery from it and flashed it via adb to the phone - ok. I then tried to get into phone fastboot recovery, but was faced with the blank screen again. I flashed twrp 2.8.7.0 and the same thing in fastboot recovery - blank screen. I also tried cwm 6.0.5.1 and the same thing, blank screen.
ADB sees the device and accepts the commands, but the Motorola fastboot recovery doesn't open any of the recoveries. Nothing else in the bootloader seems to work ie: Factory - blank screen.
Every one of the recovery files other than the stock recovery shows a pink colored error "Mismatched partition size (recovery).
Anybody have any ideas as to what I can do to get a recovery to work?
Is there a different way to root this phone?
@jjcdennis i think you should post this to one of the active threads, since nobody with experience (this is well beyond mine) has dropped in yet. i would highly recommend; http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Moved to http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
I tried to flash a custom rom (KatKiss), and it seems that I did something wrong along the way because the tablet is stuck in a bootloop.
So I rebooted my tablet and access the bootloader ("fastboot devices" recognize my device) and try to go to the recovery (with the TWRP splash screen, "adb devices" recognize my device). Unfortunately after 20 seconds on the splash screen, the tablet reboots (tries to load my katkiss android but bootloop everytime).
Bootloader : 10.6.1.14.10
TWRP : 3.1.1.0
Since the fastboot recognize my device while in bootloader, I think that I should try to flash twrp since it seems to be corrupted somehow.
Every time I flashed a rom nothing went wrong but now that I have a problem I don't want to worsen it and would like some help on the issue.
Did you flash the rom in your current TWRP?
Something is off... Did you possibly flash the TF201 rom version??
Whatever you do - do not use Wipe Data from the bootloader!!
Reflash TWRP, format data, then reflash the rom
And report in more detail what you did
Sent from my Nexus 5X using Tapatalk
Thank you for the fast reply!
I did flash the rom with my current TWRP and only downloaded the rom version for the TF700. Below is what I tried from your suggestion:
I check that my device is recognized:
fastboot device
So I tried flashing TWRP:
fastboot flash recovery twrp-3.1.1-0-tf700t
After it succeeded, I reboot the tablet:
fastboot reboot
And as a result... nothing changes, I don't know if I should try with older version of TWRP. Seems like I only have access to the tablet with the fastboot.
That is very strange indeed. Yes, try a 3.0.2 version of TWRP and see if that works.
If not, I would flash the Asus stock blob in fastboot and start from scratch....
Sent from my TF700T using Tapatalk
Kromlech said:
And as a result... nothing changes, I don't know if I should try with older version of TWRP. Seems like I only have access to the tablet with the fastboot.
Click to expand...
Click to collapse
Not sure if this will help but I had a reboot problem with trying to load into TWRP. I posted my solution into a different thread but will toss it out here..
I just had this problem with a Transformer 201Prime. The cycle went something like this..
Power on.... get ASUS logo in middle, Tegra3 logo on lower right, and bootloader unlocked in upper left....
then a buzz... then reboot.....
So I would try the power button and hold the volume down... that got me into the bootloader but when I hit the volume up button it would give me the TWRP logo... then buzz and reboot...
After much monkeying around... I realized I would have to re install everything. Fortunately I had the original NVFLASH bloob files backed up so I was able to get into the NVFLASH commands.
Here is a great tutorial, it is for the 201 so be sure to download the correct files but the steps are basically the same.
https://forum.xda-developers.com/tra...prime-t3486237
The other problems is I had to download a bloob tool to 'unpack' the necessary .bin and .ebt files that are mentioned in the commands... I used the following link to download the tool.
https://github.com/AndroidRoot/BlobTools
I hope this helps shake loose a few answers.
Once I was able to get a working recovery I could flash an updated ROM. (KatKiss is my current favorite)
I tried to flash version 3.0.2 of TWRP and the problem is still the same.
@Unidave199 the link you put in your post points to a post that doesn't seems to exist anymore, has it been moved?
@berndblb how do I do for flashing a rom with the fastboot? any stock rom to recommend?
double post
Kromlech said:
I tried to flash version 3.0.2 of TWRP and the problem is still the same.
@Unidave199 the link you put in your post points to a post that doesn't seems to exist anymore, has it been moved?
@berndblb how do I do for flashing a rom with the fastboot? any stock rom to recommend?
Click to expand...
Click to collapse
Unidave's link would only help you if you generated your device specific nvflash blobs when the tablet was still functioning. Did you:
flash a specifically modded recovery - flash the moddded bootloader, use wheelie to generate and save your blobs, return everything to factory specs?
I highly doubt it since you would have mentioned...
To flash the stock blob in fastboot you download the Asus firmware from here: https://www.asus.com/my/support/Download/28/1/0/11/29/8/
Extract the zip twice until you see a blob and a meta-inf file.
Move the blob into your fastboot folder, discard the rest of the file
Issue these commands one by one, letting each one finish before starting the next. Some will finish quick, others may take up to 3 minutes:
Code:
fastboot erase system
fastboot erase boot
fastboot erase recovery
fastboot erase misc
fastboot erase cache
fastboot erase userdata
fastboot flash system blob
fastboot reboot
The first boot will take a while, but that should put you back on a stock JB 4.2 system.
Trash all the files you used in your last attempt and redownload the rom, gapps and supersu
Fastboot flash TWRP
Reboot
Format /data in TWRP (this will take up to 1 hour - let it finish!!), then convert /data to f2fs
Flash the rom, gapps, supersu
If you flash Nougatella remember that you have to turn on wifi right after the language selection during setup or Google framework will crash.
Spend the end of the day doing it, but it worked flawlessly! Thanks a lot @berndblb, now I can use my tablet again!
Kromlech said:
I tried to flash version 3.0.2 of TWRP and the problem is still the same.
@Unidave199 the link you put in your post points to a post that doesn't seems to exist anymore, has it been moved?
@berndblb how do I do for flashing a rom with the fastboot? any stock rom to recommend?
Click to expand...
Click to collapse
My apologies for the problem with my link, looks like you resolved it, but wanted to post a correct working link to take someone else into the full conversation and context...
https://forum.xda-developers.com/showpost.php?p=71150385
berndblb said:
To flash the stock blob in fastboot you download the Asus firmware from here: https://www.asus.com/support/Download/28/1/0/11/fq2B3oq64av1O95/8/
Click to expand...
Click to collapse
Broken link ? that post isn't very old, either. ??
berndblb said:
Did you flash the rom in your current TWRP?
Something is off... Did you possibly flash the TF201 rom version??
Whatever you do - do not use Wipe Data from the bootloader!!
Reflash TWRP, format data, then reflash the rom
And report in more detail what you did
Click to expand...
Click to collapse
I did wipe data from bootloader, now I can't go to bootloader. How to revive my tf700t?
Please help
Thanks
ketulharini said:
I did wipe data from bootloader, now I can't go to bootloader. How to revive my tf700t?
Please help
Thanks
Click to expand...
Click to collapse
You'll need to refer to post #8. However, the link to the tf700 stock blob is broken. You'll have to search Google for one. They're out there, but it does require digging .Make sure the one you get is for the proper SKU of your tablet (US, Worldwide, JP, etc.). I completed the process myself maybe a month ago. Good luck!
monogwai said:
You'll need to refer to post #8. However, the link to the tf700 stock blob is broken. You'll have to search Google for one. They're out there, but it does require digging .Make sure the one you get is for the proper SKU of your tablet (US, Worldwide, JP, etc.). I completed the process myself maybe a month ago. Good luck!
Click to expand...
Click to collapse
I got the stock blob ww version.
Just tab doesn't stay on fastboot mode keeps rebooting.
Don't know how to do it.
Is it possible to get stable fastboot screen some how? Or just flash the bootloader to get fastboot working.
May be this noob question but I don't know how to do.
Thanks
ketulharini said:
I got the stock blob ww version.
Just tab doesn't stay on fastboot mode keeps rebooting.
Don't know how to do it.
Is it possible to get stable fastboot screen some how? Or just flash the bootloader to get fastboot working.
May be this noob question but I don't know how to do.
Thanks
Click to expand...
Click to collapse
There is one more piece to the puzzle- hold short while I dig it up.
Here it is: http://www.transformerforums.com/forum/transformer-pad-infinity-tf700-tegra-3-development/46302-guide-help-my-transformer-tf700-boots-only-recovery.html
Do be *very* careful. Read thrice, do it once. Especially if you're feeling noob-y.
monogwai said:
There is one more piece to the puzzle- hold short while I dig it up.
Here it is: http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Do be *very* careful. Read thrice, do it once. Especially if you're feeling noob-y.
Click to expand...
Click to collapse
Thanks for this information.
One more question,
My tab is keep bootlooping neither it stays on twrp nor bootloader.
It has blue screen of recovery that is twrp after 5 to 10 seconds it boots again.
Is this enough time to execute the commands while it is on blue screen?
Thanks
ketulharini said:
Thanks for this information.
One more question,
My tab is keep bootlooping neither it stays on twrp nor bootloader.
It has blue screen of recovery that is twrp after 5 to 10 seconds it boots again.
Is this enough time to execute the commands while it is on blue screen?
Thanks
Click to expand...
Click to collapse
Well, that depends on several things. What I did was write a short little DOS batch file to process all the fastboot commands. So, with your batch file ready, open your command prompt (change directory to your adb/fastboot directory if it's not set in system's 'path=' environment variable) and have the batch command typed in, ready to hit enter. Tether to pc via USB, proceed to boot to adb. The second you hear windows make the USB notification sound, slap that enter key. It should just process and reset the tab and get you out of TWRP bootloop. Which is just step one.
If you aren't familiar with writing bat files for DOS, let me know.
monogwai said:
Well, that depends on several things. What I did was write a short little DOS batch file to process all the fastboot commands. So, with your batch file ready, open your command prompt (change directory to your adb/fastboot directory if it's not set in system's 'path=' environment variable) and have the batch command typed in, ready to hit enter. Tether to pc via USB, proceed to boot to adb. The second you hear windows make the USB notification sound, slap that enter key. It should just process and reset the tab and get you out of TWRP bootloop. Which is just step one.
If you aren't familiar with writing bat files for DOS, let me know.
Click to expand...
Click to collapse
You mean a batch file with the adb commands right? Once he can boot into fastboot he has all the time in the world to run the commands for the buster99 (description in post #8). Depending on what situation he came from before, it might be a good idea to start all fresh...
The tricky thing are the adb push bootit.ko and the insmod command. Those have to be timed just right to get executed, so a batch file might come in handy. Both commands only take a second or two to execute, so your window of 5 seconds could work. Maybe not in the same session, but they should work.
If the insmod command does not kick the tablet into the bootloader, there are 2 possible reasoons:
adb push bootit.ko did not work
the insmod command did not work
To find out if the file push worked you could add a simple list command for the contents of /sdcard/. Again - tricky, I know since you still are working with the 5 sec window, but that's what you got to work with...
That would look something like in the attached picture. So after pushing bootit.ko you issue:
Code:
adb shell ls /sdcard/
Try it with the batch file, try it with single commands... Don't give up. As long as you have any kind of adb access you should be able to solve it.
Good luck!
berndblb said:
You mean a batch file with the adb commands right?
Click to expand...
Click to collapse
Yeah.
berndblb said:
Once he can boot into fastboot he has all the time in the world to run the commands for the buster99 (description in post #8).
Click to expand...
Click to collapse
Again, mistake in my terminology. What I meant to say is, batch commands for the process involving the Bootit.ko- the adb portion.
Thanks for clearing that up.
@ketulharini
Anyhow, I was unable to get the process to take without having automated *every last step* of the process. Literally open the cmd window, have the command for your batch file typed in ready to go, and plug in. Hear the noise from windows and slap enter asap. That's the only way I could get it in time, and I'm a ridiculously fast typist.
monogwai said:
Yeah.
Again, mistake in my terminology. What I meant to say is, batch commands for the process involving the Bootit.ko- the adb portion.
Thanks for clearing that up.
@ketulharini
Anyhow, I was unable to get the process to take without having automated *every last step* of the process. Literally open the cmd window, have the command for your batch file typed in ready to go, and plug in. Hear the noise from windows and slap enter asap. That's the only way I could get it in time, and I'm a ridiculously fast typist.
Click to expand...
Click to collapse
Care to share the batch file?