yashsingh1/xdaforums huggingface dataset:
[Transformer TF300T Q&A, Help & Troubleshooting] ferencz.marton:
no luck....

I tried going back but got stuck at:

fastboot -i 0x0b05 flash recovery openrecovery-twrp-2.4.4.0-tf300tg-JB.blob

I tried these versions:

openrecovery-twrp-2.4.4.0-tf300tg-JB.blob

openrecovery-twrp-2.5.0.0-tf300t-4.2.blob

openrecovery-twrp-2.5.0.0-tf300tg-JB.blob

From all of them I'm getting:

sending 'recovery' (7248 KB)...

OKAY [ 1.346s]

writing 'recovery'...

FAILED (remote: (InvalidState))

finished. total time: 1.655s

Is this because my device is not rooted?

I've tried to put the zip file from the content of the asus-firmware to the microSD and run the downgrade from android 4.2 interface, but that didn't work either.
[Transformer TF300T Q&A, Help & Troubleshooting] pyraxiate:
Thats not how I did it. Download the official asus firmware and unzip it. There is a large file called blob inside ( more than a few hundred megs ). Copy the blob file to your fastboot directory and run

fastboot -i 0x0b05 flash system blob

It takes a while and you should see a blue progress bar on the tablet. The computer will just sit there until it's completely flashed and won't have any progress indicator. I used the image for 10.4.2.20 and everything downgraded perfectly including the bootloader.

After that is when you flash twrp. Not before.

Again. .... follow this post carefully. There are also links in there to download the original asus firmware files which contain the bootloader and stock recovery already. The one big blob file has the entire system included in it.

http://xdaforums.com/showthread.php?t=2195883
[Transformer TF300T Q&A, Help & Troubleshooting] ferencz.marton:
Hi,

I made those steps... I uploaded the blob file, but I used the 10.4.3.9 version. After the bootloader was downgraded I tried to put the custom bootloader which did not work.

BUT

Before I started, I made a factory reset and because the twrp didn't work I uploaded the 4.2.1 android blob file again.

From then I charged my tablet 3 times and every time it charged to 100% with 4.2.1 installed.

I will keep you posted if it will keep charging correctly or not.
[Transformer TF300T Q&A, Help & Troubleshooting] pyraxiate:
Sounds like you are at least back in business again. As far as the recovery failing to flash, I went with twrp 2.4.4.0 for my 10.4 2.20 bootloader. Seems thats the combination most others are using and I've yet to have a single odd issue. I then went with cromi ( Cleanrom Inheritance) for the 4.1 bootloader and unters kernel. Everything flies now. Im not even sure I want to play with 4.2 anymore with all the issues others have had. When I was first on a 4.2 loader, I tried just about every rom/ kernel combo available at the time and everything seemed to lag.
[AT&T, Rogers HTC One X, Telstra One XL] 696kris969:
Use this link to get 10gb free of cloud storage!

Its 5gb free and an extra 5gb for clicking the link below to download

Enjoy.:)

https://copy.com?r=jRgPdA

Sent from my suped up Venomised S-Off ViperXL running ElementalX
[AT&T, Rogers HTC One X, Telstra One XL] ChongoDroid:
Been posted, thanks for stopping in, bye now

http://xdaforums.com/showthread.php?t=2227164

Edit: by the way I'm totally kidding, I'm a copy agent
[AT&T, Rogers HTC One X, Telstra One XL] 696kris969:
Uh uh;) lol. You enjoying you're hundreds of gb?;)

Sent from my suped up Venomised S-Off ViperXL running ElementalX
[AT&T, Rogers HTC One X, Telstra One XL] ChongoDroid:
I am.. 362 to be exact..

you'd probably have better luck spamming the other copy thread lol
[AT&T, Rogers HTC One X, Telstra One XL] 696kris969:
Damn! Haha, I'm not too fussed 30gb will do me for now. Internets to slow to even put a ROM on copy lol

Sent from my suped up Venomised S-Off ViperXL running ElementalX
[AT&T, Rogers HTC One X, Telstra One XL] naveen94:
Heres my link in case anyone wants to use it. Its a win win!!!! Thanks guys!!

https://copy.com?r=AbXhYP
[AT&T, Rogers HTC One X, Telstra One XL] bigbubbamcgee:
I have never heard of Copy before. Has anyone had any issues with it??? Is this another one of those sites that is here for a short time and then disappears, or is it pretty legit?

I found it to be as slow as molasses when I tried it a few minutes ago.
[AT&T, Rogers HTC One X, Telstra One XL] 696kris969:
Yeah its kinda good it takes forever to upload things though

Sent from my suped up Venomised S-Off ViperXL running ElementalX
[RAZR i Android Development] HSD-Pilot:
Nice, i'll give it an try after work.

Edit: Works flawless here. Just flashed Omars Rom over Retail GB JB. Finally the ability to flash multiple Zips in one Process > I missed it.

Thanks for your Work!

Gesendet von meinem XT890 mit Tapatalk 2
[RAZR i Android Development] Marco Lomas:
Ty so much, im gonna try it in a couple hours :D

Intel device - Razr i Owner

Hit thanks if i help you or you like my style
[RAZR i Android Development] -AdMiRaL-:
Thank you Hazou,

It works on my phone too. :good: I agree, like it more than CWM. Just did a full backup. Backup files look good.
[RAZR i Android Development] dog121:
Nice one agreed much better than cwm

Great stuff thanks
[RAZR i Android Development] wozn:
Fantastic. Thanks, much prefer team win, been using it on my nexus 7 and it has its advantages
[RAZR i Android Development] spartan-117-mc:
outstanding work, flawless, thanks for sharing
[RAZR i Android Development] ro_explorer:
Excellent work (said in the voice of ingress :) )!
[RAZR i Android Development] lebobo:
External SDCard = 0 MB with TWRP

I just installed it and I cannot make a backup to my EXTERNAL SDCard. TWRP say that my external SDCard size is 0MB.

If I try to backup with CWM to the same SDCard, it works fine...

Can someone confirm there is a bug about it ?

-----

I solved my issue : i re-downloaded and re-flashed and now it works fine !
[RAZR i Android Development] HSD-Pilot:
Nope, works fine here. Already tried all the important stuff (backup > flash > restore) and got no problems. External SD is recognized.

Gesendet von meinem XT890 mit Tapatalk 2
[RAZR i Android Development] Hazou:
hmm, cant think of anything that can fix your problem at the moment. Sry, maybe a reflash/redownload?
[RAZR i Android Development] lebobo:
Windows installer to flash TWRP recovery

I made a simple Windows installer to flash TWRP recovery (and to restore stock recovery or CWM Recovery).

This installer is adapted from @mattlgroff CWM installer (thanks for his work : all credits for him !)

I only cleaned the code and adapted it to be used with TWRP.

You can download it here : http://xdaforums.com/showthread.php?p=41479852#post41479852
[RAZR i Android Development] hypophysis:
Thanks a lot for this recovery. I like it way more than CWM.

I packaged it in a flashable ZIP and flashed it through CWM. If anyone is interested in the ZIP, just tell me, I could post it if there is a demand.

Any idea why both recoveries are so sluggish on our otherwise so quickly reacting RAZR i?
[RAZR i Android Development] Hazou:
Nope, I don't know yet why both Recovery's GUI work slow. I am looking into it, but this far I don't know. The strange thing is that the stock recovery works fast and when I put the graphic file from there in our recovery it is still slow. But maybe we can find something.
[RAZR i Android Development] Omar-Avelar:
If you check with top you can see kworker threads eating a lot of cpu cycles while in recovery (30%). I even tried a different Kernel on the recovery thinking it was a Kernel bug but it is showing the same slow performance. I was unable to find the source of the issue but I would guess it is not the graphics.c / framebuffer configuration ;/
[RAZR i Android Development] Hazou:
Ah oke, I already thought that it couldn't be it. Because that file is just a loader for the driver. Ty for the confirmation. I did read in another post to lock the CPU in high frequency. Could that help?
[RAZR i Android Development] Omar-Avelar:
Will not help, it will only make the phone get hotter. In fact the Kernel's CPU governor still exists in recovery so it is better to let it scale down at 600 MHz when CPU usage is low -- and ramp up when needed. Problem is someone/somewhere is still taxing the CPU and making kworker use a lot of cycles -- it could be a bad module or a device causing a bunch of interrumpts, no idea at this point.

But definetly making the CPU processor be stuck at max is not the solution (IMO) :D
[RAZR i Android Development] Hazou:
New version online, TWRP 2.6!

Hazou
[RAZR i Android Development] jacbarahona72:
Work fine, thank you very much :good:

backup and installation of zip's correctly :highfive:

does the installation of the Rom by Omar Avelar :victory:
[RAZR i Android Development] Locazoo:
Is there a way to make it multi-boot? I'd like to try ubuntu for example :)
[RAZR i Android Development] test_user7:
Just installed CWM and there is no any problems with formatting.
[RAZR i Android Development] Hazou:
Updated TWRP recovery to 3.0.0.0

Not tested every bit of it through fully. But I don't think there is any problem.
[RAZR i Android Development] Hazou:
Updated to TWRP 3.0.1-0

Downloads are now available in the "Download" section of the thread.
[RAZR i Android Development] Hazou:
TWRP updated to 3.0.2-0.

Also included a flashable zip file than can be flashed through your outdated recovery to update. After the update, reboot into your new recovery.

Made an error when uploading the files. Uploaded the new files under the same name.

They are updates from seeing this message.
[RAZR i Android Development] je_rem_y:
Thank you Hazou ! Unfortunately I had some problem :(

I downloaded the flashable zip that I flashed with TWRP 3.0 but I been stuck in a boot loop when I tried to reboot in the updated TWRP. I managed to get out of the boot loop by pressing "Power + Vol up". I don't know if it was because the first upload you made was broken (I downloaded it at 7PM from France and I don't know if it was already re-uploaded) or if there is still a problem with the file.

I tried again at 1AM (next day) with the "classic" .img that I flashed with Rashr. Rashr said the file was not recognized as a valid Android image. I bypassed the message by disabling some checking in Rashr. Rashr managed to flash TWRP. I rebooted and that worked ! I don't know if there is something to modify in the .img to make it a valid Android image and I don't know if that's a problem.
[RAZR i Android Development] Hazou:
The first ones had a problem with selinux that stopped booting the recoverys. At around 10pm CET I had replaced them with the right ones. They should work without any problem. That "Rashr" doesn't recognized them is strange.
[RAZR i Android Development] je_rem_y:
I downloaded the flashable zip at 6pm CET so it was broken. Rashr seem to complain about the header, it's that check that I needed to disable.
[RAZR i Android Development] je_rem_y:
I'm talking with the developer of Rashr to check if Rashr or the recovery can be improved and he said me that :

He wanted me to create a backup of the recovery over Rashr and send him the backup. But Rashr don't let me make a backup and that problem is still not resolved :

Failed execute:/data/data/de.mkrtchyan.recoverytools/files/busybox mv "/data/data/de.mkrtchyan.recoverytools/files/recovery-from-13-3-2016-0-52.img" "/storage/emulated/0/Rashr/recovery-backups/recovery-from-13-3-2016-0-52.img" 2>&1Output:mv: can't rename '/data/data/de.mkrtchyan.recoverytools/files/recovery-from-13-3-2016-0-52.img': No such file or directory

He don't know if it's the problem but we can try to add 'ANDROID!' on the first line like he said to check if that resolve the problem ?

Thanks

Ps. If you have an idea for the backup problem. Can it be a problem from the ROM ?

---------- Post added at 02:36 AM ---------- Previous post was at 02:18 AM ----------

The Rashr developer ask me to do a screencast so I tried that :

adb shell screenrecord /sdcard/rashr.mp4

But I have this error :

Request for encoder buffer failed

Can it be related to the multimedia problem from the ROM ?
[RAZR i Android Development] Hazou:
The encoding could be related to the multimedia problem.

The other thing with "ANDROID!" is because we use a specific Intel format. The Image does normally contain some sort of encrypted header. AFAIK our images (even stock) have never contained 'ANDROID!' like in other roms. It just doesn't boot if I use the normal format.
[RAZR i Android Development] je_rem_y:
I tried the previous ROM and I have the same error :(

Ok I will say it to DsLNeXuS, the Rashr developer.
[RAZR i Android Development] Tamsta_T:
Guys, 3.x.x.x recovery works fine, If it doesn't - something's wrong with your phones :) I had a problem with v. 2.8.6 , it never worked on my phone, even RSDLite'ing did change nothing (2.8.5 was OK though). Hazou even killed my last hope saying „If this one doesn't work, 2.8.7.0 (future versions) when it ever comes out will also not work.“, so I was very surprised to see v. 3.0.0.0 working! Did not test every function, but main things (wiping, flashing etc) work fine. So have a patience and keep trying ;)
[RAZR i Android Development] Hazou:
I will also have a look at the newer Intel devices and see how there recovery image is packed. If there is so such line in there, maybe I am packing the recovery's the wrong way or the older Intel devices needs it like this.

Also, again with the other ARM based apps and zip script. The busybox and flash executables included is build for ARM devices. We should test if an ARM busybox works on x86. I highly doubt it will work.

The good thing about the new recovery is, is that it is based on Android Marshmallow. And that Android version has all the x86 code into it with even more optimizations (no need to change anything anymore). So luckily for you and every Intel device the newer 3.x versions will work almost always.
[RAZR i Android Development] je_rem_y:
DsLNeXuS provide me a dev version of Rashr with some fixes and the recovery can now be flashed without any problem. So it seems that you are packing the recovery's the right way :D
[RAZR i Android Development] Hazou:
Cool. It's working again.

That just a single typo can break the flashing procedure. Good it is fixed now.
[RAZR i Android Development] ciberbeb:
Just to confirm, v3.0.2-0 works perfectly. I used the flashable zip, and flashed it from TWRP 2.8, absolutely no problem.
[RAZR i Android Development] dragmore88:
i9100 twrp sdcard0 dead

hi. Just updated from CWM to TWRP 3.0.2.0 for my aging Samsung Galaxy 2 i9100 and i seem to have issues with my sdcard0 mount. My external sdcard works fine, but the internal one (partition) i get these errors:

mount point /emmc (FS:vfat)

Present YES

Size 0MB

Used 0MB etc..

Trying to repair Fs i get:

failed to mount /emmc (invalid agrument)

unable to mount emmc/twrp/.twrps etc..

/sbin/fsck.fat -y /dev/block/mmcblkop11 process ended with error :1

unable to repair etc..

Is there a way from inside TWRP to repartition, remount and make new fs ?

br d
[RAZR i Android Development] Hazou:
Hi, U are posting in the wrong subforum for your device. But to answer your question.

U can format the partitions manually in TWRP. This can be done in the 'wipe' section of the menu.

From there u can repair, wipe, format and change file system of the selected partitions.
[RAZR i Android Development] Aljecama12:
In the Downloads there are two files, one says "flashable.zip" So, Can I flash this recovery through my actual one (cwm)?

If not, how do I flash an img through fastboot?

thank you!
[RAZR i Android Development] Hazou:
yes u can
[RAZR i Android Development] Jorge_Amaya:
download not found?

sorry guys. Im looking for this file but i can't find the download link... is it still up or something?

couldn't find this device on the TWRP official webpage. so im hanging from this one :(

anyone? share at least?
[RAZR i Android Development] Hazou:
U can find them in the Download section above the first post ;)
[RAZR i Android Development] Jorge_Amaya:
Oh what a dumb. Thanks!

btw... for some weird reasons i can't root this device. i have tried many ways. Any method suggested?

it would be awesome.

Im having issues with the Radio working on this phone. it just stopped working. did a factory reset and all that. with no avail.

how coyuld I fix it or to wwhom should I ask for assistance??:crying::crying::crying:

in advance, many thanks!
[RAZR i Android Development] Hazou:
For root:

- Unlock the bootloader

- Install TWRP

- Install SuperSU or other superuser apps compatible with x86.

- U are rooted

For the radio I should try to go back to full stock with a reflash. Use RSD-Lite for it and make sure u are using 4.1.2 (android version) firmware. Stay away from lower versions when u are flashing with RSD-Lite. The radio and all software will be reflashed.

If the radio still doesn't work, I don't know.
[RAZR i Android Development] 1stStep:
Same "Flashing recovery..." for 3 hours now. As the guy aldred didn't report back and it was twrp2.8.x era, I'd like to know it is a know issue and I just follow your advice Hazou (terminate+retry). BTW Do I need drivers as I'm with linux and dmesg shows the SMI device? Also, I use USB2 port.

./fastboot flash recovery recovery.img
sending 'recovery' (10263 KB)...
OKAY [ 1.197s]
writing 'recovery'...
OKAY [ 1.798s]
finished. total time: 2.994s
~/sdk/platform-tools$ md5sum recovery.img
60dff26f3ee5e9338ee4a6f8cf7df098 recovery.img
~/sdk/platform-tools$ md5sum recovery
recovery.img recoverytwrp3.0.2-0.img.zip
~/sdk/platform-tools$ md5sum recoverytwrp3.0.2-0.img.zip
140ca54806ce72eb7dea8e6fcf4ba068 recoverytwrp3.0.2-0.img.zip

[22384.189467] usb 3-2: new full-speed USB device number 5 using xhci_hcd
[22384.206972] usb 3-2: not running at top speed; connect to a high speed hub
[22384.209917] usb 3-2: New USB device found, idVendor=22b8, idProduct=7112
[22384.209927] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[22384.209933] usb 3-2: Product: Android
[22384.209937] usb 3-2: Manufacturer: Android
[22384.209941] usb 3-2: SerialNumber: Medfield2******0
[22384.212120] usb-storage 3-2:1.0: USB Mass Storage device detected
[22384.212332] scsi7 : usb-storage 3-2:1.0
[22385.212686] scsi 7:0:0:0: Direct-Access Android Android 0000 PQ: 0 ANSI: 2
[22385.213671] sd 7:0:0:0: Attached scsi generic sg1 type 0
[22385.221399] sd 7:0:0:0: [sdb] Attached SCSI removable disk
[22405.290800] usb 3-2: USB disconnect, device number 5
[22413.566960] usb 3-2: new high-speed USB device number 6 using xhci_hcd
[22413.586795] usb 3-2: New USB device found, idVendor=22b8, idProduct=7100
[22413.586807] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[22413.586812] usb 3-2: Product: Fastboot smi S
[22413.586817] usb 3-2: Manufacturer: Motorola Inc.
[22413.586821] usb 3-2: SerialNumber: TA3******4

Thanks
[RAZR i Android Development] Hazou:
USB2 is fine. If fastboot can see the device the drivers are correct installed. Are u using latest fastboot?

Normal recovery flashing on all 3 off my devices took at most 10 seconds.
[RAZR i Android Development] 1stStep:
I'm nearly sure I don't use the latest (I got mine ~2010/2012), and for the drivers I can't say more than dmesg says and normal boot mounts a XT890 in ubuntu launcher and I can browse internal storage that shows usual Pictures, Music, DCIM dirs and so on

[39449.181664] usb 3-2: USB disconnect, device number 6
[39454.422647] usb 3-2: new full-speed USB device number 9 using xhci_hcd
[39454.439979] usb 3-2: not running at top speed; connect to a high speed hub
[39454.442918] usb 3-2: New USB device found, idVendor=22b8, idProduct=710e
[39454.442930] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[39454.442936] usb 3-2: Product: XT890
[39454.442941] usb 3-2: Manufacturer: motorola
[39454.442946] usb 3-2: SerialNumber: Medfield2******0
[39454.443269] usb 3-2: ep 0x82 - rounding interval to 32 microframes, ep desc says 48 microframes
fab@xps:~$

OK, I'll try know to search where I can find the latest sdk.

BTW, I did put a sdcard in the phone ATM.

Oh, and

./fastboot devices
????????????	fastboot

Have a good Sunday man
[RAZR i Android Development] Hazou:
If u have the sdk installed. Just run the "android" script in one of the subfolders.
[RAZR i Android Development] 1stStep:
Okay, I had SDK tools 19 and platform tools 11... updating to 22 & 19...

Sorry

---------- Post added at 12:54 PM ---------- Previous post was at 12:12 PM ----------

Something new with updated sdk:

./fastboot devices
TA3******4	fastboot

nicer, but

./fastboot flash recovery recovery.img
(bootloader) Variable not supported!
error: cannot open 'recovery.img'

phone:

Getvar partition-type:recovery
Fastboot command failed

Back to PC:

~/sdk/platform-tools$ find .. -name "reco*"
~/sdk/platform-tools$

Oh, oh... it seems update wiped the folder :( ... DL again...

---------- Post added at 01:20 PM ---------- Previous post was at 12:54 PM ----------

More verbose now,

md5sum rec*
60dff26f3ee5e9338ee4a6f8cf7df098 recovery.img
~/sdk/platform-tools$ ./fastboot flash recovery recovery.img
(bootloader) Variable not supported!
target reported max download size of 104857600 bytes
sending 'recovery' (10263 KB)...
OKAY [ 1.328s]
writing 'recovery'...
OKAY [ 2.019s]
finished. total time: 3.348s

... but the phone now says this for more than 5mn

Getvar max-download-size
Downloading ...
Flashing recovery ...

For the first time on normal boot I saw a prompt to allow this computer (rsa key). I said yes, always... then retry... still the same.

I'm wandering : is there a some DONE/Flashing success'd on flashing end? Does this flashing process also changes the fastboot menu? Does this phone also suffers the issue of stock reco being restored on first normal boot if first post-flash reboot was not to fastboot+reco : I didn't dare going into the fastboot recovery submenu entry ...

Again, I have no SDCard in the phone.

And no SIM too.

Hope I'm just yet another stupid newb, sorry again

[Edit]I did

./adb reboot recovery

which gave the stock liing open-belly droid for a while and auto reboot, then retried with no success, then

./adb reboot bootloader

, still endless flashing on retry.

???

Worth a try putting back the genuine battery?

[Edit] Or would you advise I first try your CWM60514 then switch to this TWRP3020 ?

Good night man

[Edit] : 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.
[RAZR i Android Development] Hazou:
This was all I needed to know. The recovery is flashed succesfully.

This is a security measure for ADB access. ADB needs to give access to the PC to connect, otherwise it will not allow it

No it does not. The fastboot menu doesn't change. It will just say succeeded and u can continue with using the volume buttons to navigate

Yes, only on stock rom if u use the function "reboot recovery" in the device terminal or use "adb reboot recovery".

/\

|

Will not work, the battery.

CWM does work, but same methods will be used

haha need. :D

Got more stuff to do so I don't comment all the time :P

From here on u can:

Flash:

- Roms

- Superuser packages to root stock and others

- Flash modifications

- Most important make backups of your system

It is what u want to do
[RAZR i Android Development] 1stStep:
Yes Hazou, you see, the single thing that puzzled me was

there is no "Success" on the phone itself

which remains forever on "Flashing ..."

Re-reading my previous posts, I can see the message on the PC said ~Writing OKAY~ which I may confused with ~Sending OKAY~.

Sorry for the noise

Thanks for all time spent, sorry for wasted
[RAZR i Android Development] taurui:
Can I just flash the zip in CWM Recovery or do I have to use fastboot?
[RAZR i Android Development] Hazou:
U can ;)
[RAZR i Android Development] 1stStep:
Is the result of this the replacement of CWM by TWRP ? CWM will suicide herself overwriting her own partition with the code of TWRP ? (newb question :highfive: )