Related
is there a way to unroot and lock the bootloader again ?
quattro_rs said:
is there a way to unroot and lock the bootloader again ?
Click to expand...
Click to collapse
Yes.
Several discussions about it already in here.
To relock the bootloader is as simple as "fastboot oem lock" command.
There's a couple of different ways to get the root out, they're all mentioned in the thread for it.
but as of now no way to flash the stock recovery
slowz3r said:
but as of now no way to flash the stock recovery
Click to expand...
Click to collapse
If you apply the 2.3.1 update, it reflashes the stock recovery on every normal boot, doesn't it?
I lost "permanent" CWM when I did the update and went back to stock. You can still get to CWM via ROM Mgr or fastboot flash.
distortedloop said:
If you apply the 2.3.1 update, it reflashes the stock recovery on every normal boot, doesn't it?
I lost "permanent" CWM when I did the update and went back to stock. You can still get to CWM via ROM Mgr or fastboot flash.
Click to expand...
Click to collapse
Some people had issues flashing 2.3.1 official using CWM.
2.3.1 is incremental so it doesnt include a full recovery
slowz3r said:
Some people had issues flashing 2.3.1 official using CWM.
2.3.1 is incremental so it doesnt include a full recovery
Click to expand...
Click to collapse
2.3.1 may not include a full recovery, but it includes patches to the boot image (boot.img.p & recovery-from-boot.p) and a script to install the patches on each boot if the recovery is not stock.
The script is /etc/install-recovery.sh and here's what it does:
Code:
#!/system/bin/sh
if ! applypatch -c MTD:recovery:2048:8fa462e56115c0bf8141c3879afc8966a2b1c7f0; then
log -t recovery "Installing new recovery image"
applypatch MTD:boot:2949120:ddf4dec1310bc3213cbcdee1f4915e86f045755b MTD:recovery 33b0a9d47b4c83c37d763affdebe5fa84e4f220d 3194880 ddf4dec1310bc3213cbcdee1f4915e86f045755b:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
can someone explain how to do it step by step im new at this ?
ok i managed to lock the bootloader but im still not sure how to unroot the device !
distortedloop said:
2.3.1 may not include a full recovery, but it includes patches to the boot image (boot.img.p & recovery-from-boot.p) and a script to install the patches on each boot if the recovery is not stock.
The script is /etc/install-recovery.sh and here's what it does:
Code:
#!/system/bin/sh
if ! applypatch -c MTD:recovery:2048:8fa462e56115c0bf8141c3879afc8966a2b1c7f0; then
log -t recovery "Installing new recovery image"
applypatch MTD:boot:2949120:ddf4dec1310bc3213cbcdee1f4915e86f045755b MTD:recovery 33b0a9d47b4c83c37d763affdebe5fa84e4f220d 3194880 ddf4dec1310bc3213cbcdee1f4915e86f045755b:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
Click to expand...
Click to collapse
Oh, alright
google hasnt released a full OS for flashing have they?
quattro_rs said:
can someone explain how to do it step by step im new at this ?
Click to expand...
Click to collapse
It's in the FAQ that is stickied at the top of the forum here...this is always a good place to start when looking for answers.
Here's the relevant section with links:
Q: How do I root/unroot the Nexus S?
Check the development section links below for more detail, but you gain root on the Nexus S by booting the phone into fastboot mode and typing "fastboot oem unlock." This will wipe your phone and it's SD card partition. To unroot it, again boot into fastboot mode and type "fastboot oem lock."
Step 1: http://forum.xda-developers.com/showthread.php?t=878786
Step 2: http://forum.xda-developers.com/showthread.php?t=875875
In the event you want to return to stock, simply flash the NAND backup found here: http://forum.xda-developers.com/showthread.php?t=884093 . This will restore everything, including the stock recovery image. Then as mentioned above go into the bootloader/fastboot mode and enter "fastboot oem lock" in ADB.
(All credit goes to the original author(s) of the linked thread!)
Click to expand...
Click to collapse
If that doesn't get you going, let me know specifically what's confusing you and I'll try to help.
For me, on 2.3.1, I think I would just use adb shell to rm or uninstall the superuser.apk (/data/app/com.noshufou.android.su-1.apk (might be different name on yours depending on version) and then to rm the su binary (/system/bin/su). Then I'd reboot the phone to make sure the recovery was stock, then I'd fastboot oem lock the phone.
Flashing a nandroid might be easier for you.
slowz3r said:
Oh, alright
google hasnt released a full OS for flashing have they?
Click to expand...
Click to collapse
Not that I'm aware of!
Wish they would...I miss having a nice stock image from a trusted source to go back to, but other than root and CWM, I haven't messed with the OS; Gingerbread's fast and sweet enough for me for now.
I don't care for some of the apps though, the gapps camera sucks by a long shot compared to Samsung's SGS camera app, for example.
distortedloop said:
Not that I'm aware of!
Wish they would...I miss having a nice stock image from a trusted source to go back to, but other than root and CWM, I haven't messed with the OS; Gingerbread's fast and sweet enough for me for now.
I don't care for some of the apps though, the gapps camera sucks by a long shot compared to Samsung's SGS camera app, for example.
Click to expand...
Click to collapse
Normally I would do CM, but Im not a fan of alpha stage builds, ill wait for beta and then do nightlies from there
Hopefully the CM team take care of issues like the camera, and such
EDIT: never been a fan of CWM, hope Amon_RA releases a recovery
slowz3r said:
Normally I would do CM, but Im not a fan of alpha stage builds, ill wait for beta and then do nightlies from there
Hopefully the CM team take care of issues like the camera, and such
EDIT: never been a fan of CWM, hope Amon_RA releases a recovery
Click to expand...
Click to collapse
Ditto.
Ditto.
Ditto (for the most part, CWM isn't bad, but I also prefer Amon_RA).
distortedloop said:
It's in the FAQ that is stickied at the top of the forum here...this is always a good place to start when looking for answers.
Here's the relevant section with links:
If that doesn't get you going, let me know specifically what's confusing you and I'll try to help.
For me, on 2.3.1, I think I would just use adb shell to rm or uninstall the superuser.apk (/data/app/com.noshufou.android.su-1.apk (might be different name on yours depending on version) and then to rm the su binary (/system/bin/su). Then I'd reboot the phone to make sure the recovery was stock, then I'd fastboot oem lock the phone.
Flashing a nandroid might be easier for you.
Click to expand...
Click to collapse
i manged to lock/unlcok the bootloader ,
what i dont understand is this :
Requirements:
-Clockwork recovery or other custom recovery
Click to expand...
Click to collapse
quattro_rs said:
i manged to lock/unlcok the bootloader ,
what i dont understand is this :
Click to expand...
Click to collapse
the stock recovery does not allow you to flash custom/unsigned roms or other files for that matter.
so a custom Recovery is required, as of now the only one I believe is available is ClockWorkMod
got it all working now thanks to you and distortedloop .
thanks a lot guys.
A few days ago I started having Issues with my GPS. Long story short flashing the latest nightly of CM10.1 fixed the issue.
I like CM10.1 ALOT however I just feel like its not quite finished enough to use as a DD. Currently im running the older kernel and bootloader required for Cyanogenmod to work.
What im wondering is, if I flash to stock JellyBean for my phone (updated kernel, bootloader+chain, etc.) Using one of the many guides here on XDA in the future when a more stable version of Cyanogenmod comes out will I be able to flash back to the old prerequisites for CM to work.
+1 Quick question. Best way to flash latest CWM Recovery touch (6.0.3.0) would be?
Ive looked but some say using ROM Manager breaks the phone half the time and others just recommend using ADB like so:
Code:
$ su
# dd if=/sdcard/.img of=/dev/block/mmcblk0p18
# reboot recovery
Thanks.
nuke235 said:
A few days ago I started having Issues with my GPS. Long story short flashing the latest nightly of CM10.1 fixed the issue.
I like CM10.1 ALOT however I just feel like its not quite finished enough to use as a DD. Currently im running the older kernel and bootloader required for Cyanogenmod to work.
What im wondering is, if I flash to stock JellyBean for my phone (updated kernel, bootloader+chain, etc.) Using one of the many guides here on XDA in the future when a more stable version of Cyanogenmod comes out will I be able to flash back to the old prerequisites for CM to work.
+1 Quick question. Best way to flash latest CWM Recovery touch (6.0.3.0) would be?
Ive looked but some say using ROM Manager breaks the phone half the time and others just recommend using ADB like so:
Code:
$ su
# dd if=/sdcard/.img of=/dev/block/mmcblk0p18
# reboot recovery
Thanks.
Click to expand...
Click to collapse
To your first question, yes you will be able to flash back to get CM to work. Only prerequisites you need is just unlocked bootloader and a custom recovery.
To your second question, the best way would be to use ADB, but there is an easier way. budzylikessoup already packaged the touch version into a tar, ready for you just to odin it to your phone. http://forum.xda-developers.com/showthread.php?t=2215567
Watanuki-Kun said:
To your first question, yes you will be able to flash back to get CM to work. Only prerequisites you need is just unlocked bootloader and a custom recovery.
To your second question, the best way would be to use ADB, but there is an easier way. budzylikessoup already packaged the touch version into a tar, ready for you just to odin it to your phone. http://forum.xda-developers.com/showthread.php?t=2215567
Click to expand...
Click to collapse
Thanks man, simple and to the point.
Im not as familiar with odin as I should be so Ill just probably just use ADB with the d2vzw recovery IMG from here: http://www.clockworkmod.com/rommanager
Unless there is a better place to get the recovery images?
nuke235 said:
Thanks man, simple and to the point.
Im not as familiar with odin as I should be so Ill just probably just use ADB with the d2vzw recovery IMG from here: http://www.clockworkmod.com/rommanager
Unless there is a better place to get the recovery images?
Click to expand...
Click to collapse
That is the best place to get them.
Just for reference, if you want to get more familar with odin, here is a good tutorial on how to use it.
http://androidfirmwares.net/Guide/Details/9
In there it has an odin version and usb drivers, just use this version of Odin 3.07 and the latest usb drivers from samsung for the S3.
http://samsung-updates.com/Odin307.zip
I have an ASUS TF300T running stock 4.2.1 build JOP400D_epad-10.6.1.27.5-20130902. I'd really like to, at a minimum, root this thing so I can boost it up a little bit. And at the most, install another ROM like CM 11.
I've rooted other machines (Droid Incredible, and my current Droid Razr) so I am not a novice by far. But after searching around I am finding that I can't really determine the 'best' method for rooting the TF300T. By best I mean - easiest and safest. With this in mind, can someone suggest the best method (and URL) for rooting the TF300T? And if I want to go so far as putting CM 11 on it (like I did for my phone) can Safestrap be run on this tablet? Any caveats?
Thanks in advance!
P.S. I might mention I use a Mac, so if whatever root method can run on a Mac that would be great. Otherwise if the method can work under a Win 7 VM (VirtualBox) that would be fine too.
-Tom
SimpTheChimp said:
I have an ASUS TF300T running stock 4.2.1 build JOP400D_epad-10.6.1.27.5-20130902. I'd really like to, at a minimum, root this thing so I can boost it up a little bit. And at the most, install another ROM like CM 11.
I've rooted other machines (Droid Incredible, and my current Droid Razr) so I am not a novice by far. But after searching around I am finding that I can't really determine the 'best' method for rooting the TF300T. By best I mean - easiest and safest. With this in mind, can someone suggest the best method (and URL) for rooting the TF300T? And if I want to go so far as putting CM 11 on it (like I did for my phone) can Safestrap be run on this tablet? Any caveats?
Thanks in advance!
P.S. I might mention I use a Mac, so if whatever root method can run on a Mac that would be great. Otherwise if the method can work under a Win 7 VM (VirtualBox) that would be fine too.
-Tom
Click to expand...
Click to collapse
I don't know about safestrap, but this is one of the pickiest tablets when it comes to ROMs: One mismatched bootloader, and it becomes an expensive paperweight.
There are several root methods in the General Forum if thats all you want to do.
For Customs ROMs, you will have to first unlock the bootloader, then update to the latest stock ROM, install the right TWRP, then pick the corresponding ROM. Never click wipe data in the bootloader menu.
cmendonc2 said:
I don't know about safestrap, but this is one of the pickiest tablets when it comes to ROMs: One mismatched bootloader, and it becomes an expensive paperweight.
Click to expand...
Click to collapse
Yeah, that's my worry, from what I read it seems this is a very 'picky' tablet - and I don't want to blow it up... so maybe I'll just start with rooting it. That way I can at least customize a few things, get rid of bloatware, etc. Hopefully that will help it a bit.
cmendonc2 said:
There are several root methods in the General Forum if thats all you want to do.
For Customs ROMs, you will have to first unlock the bootloader, then update to the latest stock ROM, install the right TWRP, then pick the corresponding ROM. Never click wipe data in the bootloader menu.
Click to expand...
Click to collapse
So what would you consider the 'easiest' and 'safest' of the root methods shown in the general forum? Any suggestions? Also, I assume the latest stock ROM is still the 4.2.1 build JOP400D_epad-10.6.1.27.5-20130902? I haven't got anything newer yet via System Update. That's why I was thinking of going to CM 11 like I did on my phone - to get Kit Kit. We'll probably never get it directly from ASUS....
-Tom
SimpTheChimp said:
Yeah, that's my worry, from what I read it seems this is a very 'picky' tablet - and I don't want to blow it up... so maybe I'll just start with rooting it. That way I can at least customize a few things, get rid of bloatware, etc. Hopefully that will help it a bit.
So what would you consider the 'easiest' and 'safest' of the root methods shown in the general forum? Any suggestions? Also, I assume the latest stock ROM is still the 4.2.1 build JOP400D_epad-10.6.1.27.5-20130902? I haven't got anything newer yet via System Update. That's why I was thinking of going to CM 11 like I did on my phone - to get Kit Kit. We'll probably never get it directly from ASUS....
-Tom
Click to expand...
Click to collapse
To root, you can try this: http://forum.xda-developers.com/showthread.php?t=2685628
cmendonc2 said:
To root, you can try this: http://forum.xda-developers.com/showthread.php?t=2685628
Click to expand...
Click to collapse
Hmm, I'll give this a try. So is this what you used to get root on your TF300T? It looks like it works for a variety of different machines.
Does this only do root? Or also bootloader unlock so you can run other ROMS? Also, if for whatever reason I had to revert root and reinstall stock, will that work after rooting with this method?
Thanks!
SimpTheChimp said:
Hmm, I'll give this a try. So is this what you used to get root on your TF300T? It looks like it works for a variety of different machines.
Does this only do root? Or also bootloader unlock so you can run other ROMS? Also, if for whatever reason I had to revert root and reinstall stock, will that work after rooting with this method?
Thanks!
Click to expand...
Click to collapse
This does ONLY root. Your bootloader is still unlocked, but if you reinstall stock, the root will be removed. If you do choose to unlock your bootloader, it can never be relocked and your warranty is forever void.
cmendonc2 said:
This does ONLY root. Your bootloader is still unlocked, but if you reinstall stock, the root will be removed. If you do choose to unlock your bootloader, it can never be relocked and your warranty is forever void.
Click to expand...
Click to collapse
OK cool, I'll give it a shot. I'll first start with root and see if I can then optimize the tablet to run a little bit better (and get rid of the bloatware). Then later on I may consider unlocking the bootloader and trying another ROM - especially KitKat.
-Tom
cmendonc2 said:
This does ONLY root. Your bootloader is still unlocked, but if you reinstall stock, the root will be removed. If you do choose to unlock your bootloader, it can never be relocked and your warranty is forever void.
Click to expand...
Click to collapse
CMendonc2:
IT WORKED! Not only that, it was easy and quick!
Thanks!
SimpTheChimp said:
CMendonc2:
IT WORKED! Not only that, it was easy and quick!
Thanks!
Click to expand...
Click to collapse
Glad to hear it! Don't be afraid to ask any other questions
cmendonc2 said:
Glad to hear it! Don't be afraid to ask any other questions
Click to expand...
Click to collapse
OK cmendonc2, I like having root, but I think I am about ready to unlock this baby and put on another ROM. I know the risks, and that my warranty will be voided - but I've had this a couple of years so it's not under warranty anyway.
So... I got the ASUS Bootloader unlocker program from the ASUS site; and I have what I believe is the latest TWRP. Is there a good place for instructions on how to unlock this thing and install a new ROM? I know it can be picky so I want to do it right and not brick it.
Also any suggestions on a good ROM? I was thinking CM 11, but I've also heard good things about OmniROM.
Thanks.
-Tom
SimpTheChimp said:
OK cmendonc2, I like having root, but I think I am about ready to unlock this baby and put on another ROM. I know the risks, and that my warranty will be voided - but I've had this a couple of years so it's not under warranty anyway.
So... I got the ASUS Bootloader unlocker program from the ASUS site; and I have what I believe is the latest TWRP. Is there a good place for instructions on how to unlock this thing and install a new ROM? I know it can be picky so I want to do it right and not brick it.
Also any suggestions on a good ROM? I was thinking CM 11, but I've also heard good things about OmniROM.
Thanks.
-Tom
Click to expand...
Click to collapse
OK so you have bootloader 10.6.1.27.5. That's the latest version, so you don't have to worry about upgrading stock. This TWRP (http://www.androidfilehost.com/?fid=23329332407579270) is compatible with the bootloader. Download any 4.4.4 ROM from here: http://forum.xda-developers.com/transformer-tf300t/development. Then download the latest GAPPS from here: http://goo.gl/ZcwCW9.
After unlocking, extract the TWRP blob and put it on your SD card. type this into Terminal Emulator on your tablet:
Code:
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Then restart and go into TWRP. Wipe Data and cache, then install your new ROM and gapps.
cmendonc2 said:
OK so you have bootloader 10.6.1.27.5. That's the latest version, so you don't have to worry about upgrading stock. This TWRP (http://www.androidfilehost.com/?fid=23329332407579270) is compatible with the bootloader. Download any 4.4.4 ROM from here: http://forum.xda-developers.com/transformer-tf300t/development. Then download the latest GAPPS from here: http://goo.gl/ZcwCW9.
After unlocking, extract the TWRP blob and put it on your SD card. type this into Terminal Emulator on your tablet:
Code:
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Then restart and go into TWRP. Wipe Data and cache, then install your new ROM and gapps.
Click to expand...
Click to collapse
Thanks, cmendonc2... I'll give this a shot tonight. I think KitKat will perform better on this tablet (I hope). I think I'll try OmniROM first.
BTW, I thought I read somewhere that there was one TWRP option (a specific Wipe option) that I was to NEVER use or I would brick the tablet. You know what that option is?
-Tom
SimpTheChimp said:
Thanks, cmendonc2... I'll give this a shot tonight. I think KitKat will perform better on this tablet (I hope). I think I'll try OmniROM first.
BTW, I thought I read somewhere that there was one TWRP option (a specific Wipe option) that I was to NEVER use or I would brick the tablet. You know what that option is?
-Tom
Click to expand...
Click to collapse
Thats the Bootloader option "Wipe Data". You see that when u press vol down and power to get the three icons. It is the icon on the far right. Selecting that will result in an expensive paperweight.
SimpTheChimp said:
Thanks, cmendonc2... I'll give this a shot tonight. I think KitKat will perform better on this tablet (I hope). I think I'll try OmniROM first.
BTW, I thought I read somewhere that there was one TWRP option (a specific Wipe option) that I was to NEVER use or I would brick the tablet. You know what that option is?
-Tom
Click to expand...
Click to collapse
OK I got the TWRP but when I extract it there is no .blob file. So what am I missing? There doesn't seem to be much in this .zip file.... I guess to do it the terminal way (seems the easiest to me) I need the blob file. I've googled left and right but I can't find a TWRP 2.7.0.1 blob.
Or would this ROM Manager app work?
UPDATE: Never mind, I figured out how to flash recovery using Fastboot on my Mac! TWRP is now installed and working! Going to try flashing OmniRom and see how that goes. So I think the only question I have left is: When I am flashing a new ROM (i.e. over the old stock) what wipe options in TWRP should I use first? Obviously cache and Dalvik, but which other ones? System? Data? For this first flash I obviously want/need to start fresh.
SimpTheChimp said:
OK I got the TWRP but when I extract it there is no .blob file. So what am I missing? There doesn't seem to be much in this .zip file.... I guess to do it the terminal way (seems the easiest to me) I need the blob file. I've googled left and right but I can't find a TWRP 2.7.0.1 blob.
Or would this ROM Manager app work?
UPDATE: Never mind, I figured out how to flash recovery using Fastboot on my Mac! TWRP is now installed and working! Going to try flashing OmniRom and see how that goes. So I think the only question I have left is: When I am flashing a new ROM (i.e. over the old stock) what wipe options in TWRP should I use first? Obviously cache and Dalvik, but which other ones? System? Data? For this first flash I obviously want/need to start fresh.
Click to expand...
Click to collapse
For factory reset: wipe data, cache, dalvik
For dirty flash: wipe cache, dalvik cache
Q&A for [RECOVERY][TF700T] TWRP 2.8.3.0 touch recovery [2014-12-22]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY][TF700T] TWRP 2.8.3.0 touch recovery [2014-12-22]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
where is the link?
1122qqww said:
where is the link?
Click to expand...
Click to collapse
Here: http://www.teamw.in/project/twrp2/105
I strongly recommend installation using the fastboot method, as the apps are reported to work poorly or not at all.
TWRP 2.8.5.0 Won't Boot
I just installed TWRP 2.8.5.0 on my TF700T via the fastboot method (since TWRP Manager fails to install it). However, when I attempt to boot the recovery, the device locks up. This is different behavior than 2.8.4.0, which had a kernel panic and rebooted the device. Any idea how to go about debugging, or should I simply try older recoveries / wait until a newer one comes out?
N1FFO said:
I just installed TWRP 2.8.5.0 on my TF700T via the fastboot method (since TWRP Manager fails to install it). However, when I attempt to boot the recovery, the device locks up. This is different behavior than 2.8.4.0, which had a kernel panic and rebooted the device. Any idea how to go about debugging, or should I simply try older recoveries / wait until a newer one comes out?
Click to expand...
Click to collapse
My self-built one works fine. Can anyone else reproduce this problem with TWRP 2.8.5?
_that said:
My self-built one works fine. Can anyone else reproduce this problem with TWRP 2.8.5?
Click to expand...
Click to collapse
Nope!
Just dd'd 2.8.5.0 onto tf700. Flashed and works tadellos.
Works Now
das chaos said:
Nope!
Just dd'd 2.8.5.0 onto tf700. Flashed and works tadellos.
Click to expand...
Click to collapse
Naturally, the dd method is the one method I didn't try. So I just did, and it works now. I did have to perform a normal reboot to complete the installation (as opposed to rebooting directly into recovery), but the instructions mentioned that (although they didn't specify that the reboot needed to be a normal one). So all is well now, and I can move on to installing ZOMBi-Pop, my main goal all along.
Makes me wonder why TWRP and fastboot failed, but oh well.
N1FFO said:
Makes me wonder why TWRP and fastboot failed, but oh well.
Click to expand...
Click to collapse
These methods also require reboot to system not to recovery.
das chaos said:
These methods also require reboot to system not to recovery.
Click to expand...
Click to collapse
I can believe that for fastboot, but TWRP Manager claimed that the flashing failed. On my OnePlus One, TWRP Manager flashed the recovery just fine. Is the claimed failure just a caveat of flashing on the TF700T, and the new recovery will actually work despite it if you perform a system reboot afterwards? I think I'll try that next when the next version comes out, just to see.
N1FFO said:
I can believe that for fastboot, but TWRP claimed that the flashing failed. On my OnePlus One, TWRP flashed the recovery just fine. Is the claimed failure just a caveat of flashing on the TF700T, and the new recovery will actually work despite it if you perform a system reboot afterwards? I think I'll try that next when the next version comes out, just to see.
Click to expand...
Click to collapse
Did you try to flash the twrp.blob in recovery?
That won't work unless you put the blob into a flashable zip.
Oh, re-reading your post you probably mean it failed in TWRP Manager. You take your chances with these apps. Don't use them...
berndblb said:
Did you try to flash the twrp.blob in recovery?
That won't work unless you put the blob into a flashable zip.
Oh, re-reading your post you probably mean it failed in TWRP Manager. You take your chances with these apps. Don't use them...
Click to expand...
Click to collapse
You're right, I meant TWRP Manager. Thanks for pointing that out, I edited the previous post to reflect that.
berndblb said:
Oh, re-reading your post you probably mean it failed in TWRP Manager. You take your chances with these apps. Don't use them...
Click to expand...
Click to collapse
That bricked my first tf300t!
Repeat:
Don't ever use TWRP Manager or Goo Manager for flashing recovery.
das chaos said:
That bricked my first tf300t!
Repeat:
Don't ever use TWRP Manager or Goo Manager for flashing recovery.
Click to expand...
Click to collapse
+1
add Flashify to the list. Or make that: apps in general
Fastboot or dd command is the way to go
Never mind, thanks
Never mind
Bgecko
USB OTG not working on htc one m7
USB keyboards not work on htc one m7 that support USB host mode via a USB OTG cable noooooooot work
openrecovery-twrp-2.8.5.0-m7.img
Can anyone turn this into a zip for me?
TLR - I think if I can get a zip of the latest TWRP I can get myself out of a nasty bootloop
I seem to have gone and bricked my Infinity while under the influence...
Installed new rom.
Decided to factory reset.
During format there was an error, and E: data no longer mountable (didn't realize this at the time)
Bootloop
Read some things online and thought maybe I didn't have the right TWRP
Installed a new recovery that was "compatible" with the rom I was installing
It was Philz cwm (freaked out)
Read a post that said I could force the tablet to re-format the :data partition from TWRP by using the terminal command "mke2fs -T ext4 /dev/block/mmcblk0p8" BUT can't run a terminal command from cwm
Can't find a way to enter fastboot to put twrp back onto transformer (No option for usb)
jbjcurly said:
Can't find a way to enter fastboot to put twrp back onto transformer (No option for usb)
Click to expand...
Click to collapse
Read this:
http://forum.xda-developers.com/showthread.php?t=2688891
Problem solved!
_that said:
Read this:
http://forum.xda-developers.com/showthread.php?t=2688891
Click to expand...
Click to collapse
Thanks _that! I actually used a flashable version of your twrp recovery (2.6.3 maybe?) that I found, followed the plan I outlined above, and all is now well.
Where to get TWRP 2.8.6.0 for TF700T
Does anyone know where a TWRP 2.8.6.0 .img for the TF700T can be found? It's not available on the official website (actually, NOTHING for the TF700T is available on the offcial website).
Alternatively, does anyone know where a patched version of 2.8.50 that supports f2fs can be found? Or should I revert to 2.8.4.0?
Eh, maybe I'll just build 2.8.6.0 myself. How hard can it be?
Slightly harder than finding the Kang TWRP 2.8.6 by lj in the dev section I would think....
Hi
Since updating my OPO to YOG4PAS1N0 I couldn't reboot my OPO. Since the last update it won't even boot any more. I've reflashed to stock 4.4.4, installed every update and had the same issue. I even tried to flash the zip true recovery, but i got an error while doing it. So, after three times of updating, I'm back to square one.
After going back to stock I have to factory reset in recovery, otherwise the OPO won't boot.
But of course I'd like to install Lollipop (and later Marshmallow). What can I do? I have a Mac with OSX 10.11 and a laptop with Windows 7, so I'm able to use both.
I did the flashing on my Macbook with the Toolkit found here. But I don't think there's an issue with this, as it uses the terminal. It's just easier then to type it all myself
Thanks in advance.
erdeebee said:
Hi
Since updating my OPO to YOG4PAS1N0 I couldn't reboot my OPO. Since the last update it won't even boot any more. I've reflashed to stock 4.4.4, installed every update and had the same issue. I even tried to flash the zip true recovery, but i got an error while doing it. So, after three times of updating, I'm back to square one.
After going back to stock I have to factory reset in recovery, otherwise the OPO won't boot.
But of course I'd like to install Lollipop (and later Marshmallow). What can I do? I have a Mac with OSX 10.11 and a laptop with Windows 7, so I'm able to use both.
I did the flashing on my Macbook with the Toolkit found here. But I don't think there's an issue with this, as it uses the terminal. It's just easier then to type it all myself
Thanks in advance.
Click to expand...
Click to collapse
It'd help if you actually posted what errors you're getting, without information like that it's virtually impossible to troubleshoot. Anyway, your best bet is probably just to flash the stock images with fastboot. Back up anything important first as this will wipe your device. See section 8 of my guide:
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
The only error I got, was that it's impossible to boot. I'll try your guide asap
Heisenberg said:
It'd help if you actually posted what errors you're getting, without information like that it's virtually impossible to troubleshoot. Anyway, your best bet is probably just to flash the stock images with fastboot. Back up anything important first as this will wipe your device. See section 8 of my guide:
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Click to expand...
Click to collapse
I unlocked the bootloader.
I installed the latest fastboot image.
Now my OPO is stuck again at the 1+ / Powered by Android-screen. I can't boot into recovery, but fastboot mode is still possible.
Everything up to cm-12.0-YNG1TAS2XK-bacon-signed-fastboot seems to work fine.
erdeebee said:
I unlocked the bootloader.
I installed the latest fastboot image.
Now my OPO is stuck again at the 1+ / Powered by Android-screen. I can't boot into recovery, but fastboot mode is still possible.
Click to expand...
Click to collapse
erdeebee said:
Everything up to cm-12.0-YNG1TAS2XK-bacon-signed-fastboot seems to work fine.
Click to expand...
Click to collapse
Is there a reason you're using that particular build instead of the latest? How are you installing it?
Heisenberg said:
Is there a reason you're using that particular build instead of the latest? How are you installing it?
Click to expand...
Click to collapse
I'm sorry, I thought my message was clear. The latest build gives the same problem. With this build, I'm able to boot. I installed this in terminal as a fastboot-images.
This guy has the exact same problem.
erdeebee said:
This guy has the exact same problem.
Click to expand...
Click to collapse
Assuming that you want to upgrade your OPO to latest available version of Cyanogen
- Flash latest *fastboot* image from here http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
- If you have already tried above step, flash cm-12.0-YNG1TAS2I3-bacon-signed-fastboot.zip and then upgrade via OTA incremental update zip
Mr hOaX said:
Assuming that you want to upgrade your OPO to latest available version of Cyanogen
- Flash latest *fastboot* image from here http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
- If you have already tried above step, flash cm-12.0-YNG1TAS2I3-bacon-signed-fastboot.zip and then upgrade via OTA incremental update zip
Click to expand...
Click to collapse
I've tried the first, didn't work. I've tried flashing 11S and started upgrading. I didn't have issues until 12.0. When I got to 12.1 I couldn't reboot (but I could shut down and boot). With the latest update I couldn't even boot normally.
Anyone has some idea?
Verstuurd vanaf mijn A0001 met Tapatalk
erdeebee said:
Anyone has some idea?
Verstuurd vanaf mijn A0001 met Tapatalk
Click to expand...
Click to collapse
Not sure if its a language barrier but first of you are going to have to supply more information than that. Secondly what have you tried to fix it and especially since there are tutorial out the waaaaahzooo in here on how to repair your "bricked" phone.
Please research make some attempts and if any issue please document in full what your issue is. I guarantee you though whatever it is someone here has gone through it already so search thorough
playya said:
Not sure if its a language barrier but first of you are going to have to supply more information than that. Secondly what have you tried to fix it and especially since there are tutorial out the waaaaahzooo in here on how to repair your "bricked" phone.
Please research make some attempts and if any issue please document in full what your issue is. I guarantee you though whatever it is someone here has gone through it already so search thorough
Click to expand...
Click to collapse
What I have tried is on page 1 of this thread.
I tried to install 4.4.4 with a flashable zip and then installed all updates. I installed the 5.1.1 zip. I installed the fastboot 5.1.1 and 4.4.4 and installed all updates.
Now I'm on 5.0.
On the last update I couldn't update reboot or boot anymore. The update before that I couldn't reboot, bu I could boot.
erdeebee said:
What I have tried is on page 1 of this thread.
I tried to install 4.4.4 with a flashable zip and then installed all updates. I installed the 5.1.1 zip. I installed the fastboot 5.1.1 and 4.4.4 and installed all updates.
Now I'm on 5.0.
On the last update I couldn't update reboot or boot anymore. The update before that I couldn't reboot, bu I could boot.
Click to expand...
Click to collapse
My bad on that did not even realize there was another page.. dont know how that happened... Wow I say just start from scratch and go to cm page and download the latest stock software. I am sorry I see others have tried to help you and to be honest your breakdown is a lil confusing. NO worries though hopefully someone will come along to help