It's possible this is also somewhere else, but I am having trouble finding it....so I gave up and figured I'd ask.
Okei. I started with TWRP 2.8.6.1. So from my understanding flashing a modem does not work in versions of TWRP newer than 2.8.6.0. I get that, and so I decided to downgrade. However, that seems to be the version that I am unable to get working. I've attempted to flash the 2.8.6.0 recovery via fastboot. Everything says it's good in my terminal. So I go ahead and boot into recovery, but my phone goes to a black screen for a moment and then reboots into OS. I tried a different method, via the app from the google play store. It tells me that there is an error of some sort, or that I already have it installed. So I used the google play app to install 2.8.6.1, which worked flawlessly. So now I am back where I started.
Is there some trick to getting specifically TWRP 2.8.6.0 working so that I am able to use it to flash a different modem? Will using an even earlier version yield the same results? Or am I better off doing it via fastboot?
Thank you for your time <3
Use philz recovery
Myrskyta said:
It's possible this is also somewhere else, but I am having trouble finding it....so I gave up and figured I'd ask.
Okei. I started with TWRP 2.8.6.1. So from my understanding flashing a modem does not work in versions of TWRP newer than 2.8.6.0. I get that, and so I decided to downgrade. However, that seems to be the version that I am unable to get working. I've attempted to flash the 2.8.6.0 recovery via fastboot. Everything says it's good in my terminal. So I go ahead and boot into recovery, but my phone goes to a black screen for a moment and then reboots into OS. I tried a different method, via the app from the google play store. It tells me that there is an error of some sort, or that I already have it installed. So I used the google play app to install 2.8.6.1, which worked flawlessly. So now I am back where I started.
Is there some trick to getting specifically TWRP 2.8.6.0 working so that I am able to use it to flash a different modem? Will using an even earlier version yield the same results? Or am I better off doing it via fastboot?
Thank you for your time <3
Click to expand...
Click to collapse
I too have experienced exactly what you describe and have yet to find a solution. I own 2 OPO's, plus I administer one for a friend who purchased one based on my recommendation. The oldest one I own which was purchased 4 months prior to the others has worked perfectly with any recovery or ROM I've installed on it. It has TWRP-2.8.6.0 installed and has no problems flashing any partition from recovery. My newer handset and my friend's both refuse to boot into recovery with that version installed. It doesn't matter if I flash from fastboot or from TWRP itself. I have no idea why this phenomena occurs on some of these devices, but it makes administering them a more time consuming pain in the ass. I'm going to try Phil's recovery, as was suggested, as a workaround, but I'm dumbfounded as to why the inconsistencies exhibit themselves on particular devices.
Odysseus1962 said:
I too have experienced exactly what you describe and have yet to find a solution. I own 2 OPO's, plus I administer one for a friend who purchased one based on my recommendation. The oldest one I own which was purchased 4 months prior to the others has worked perfectly with any recovery or ROM I've installed on it. It has TWRP-2.8.6.0 installed and has no problems flashing any partition from recovery. My newer handset and my friend's both refuse to boot into recovery with that version installed. It doesn't matter if I flash from fastboot or from TWRP itself. I have no idea why this phenomena occurs on some of these devices, but it makes administering them a more time consuming pain in the ass. I'm going to try Phil's recovery, as was suggested, as a workaround, but I'm dumbfounded as to why the inconsistencies exhibit themselves on particular devices.
Click to expand...
Click to collapse
Well....at least now I know I'm not totally crazy. Thank you~
=)
Ejvyas said:
Use philz recovery
Click to expand...
Click to collapse
Is there any particular reason for Philz recovery over standard CWM?
Also, while this might be a viable option my understanding is that, that would render my old backups useless since I was previously using TWRP? That's kind of unfortunate. =(
Myrskyta said:
Is there any particular reason for Philz recovery over standard CWM?
Also, while this might be a viable option my understanding is that, that would render my old backups useless since I was previously using TWRP? That's kind of unfortunate. =(
Click to expand...
Click to collapse
uploaded the file for you (Take out .apk extension), hope you know how to flash thru fastboot. Else google.
KSKHH said:
uploaded the file for you (Take out .apk extension), hope you know how to flash thru fastboot. Else google.
Click to expand...
Click to collapse
Unfortunately, if that is the same one from twrp's website it isn't going to do me any good. I already attempted that through fastboot. 2.8.6.1 works flawlessly. 2.8.6.0 seems to bootloop once and then toss me back into the OS. Thank you though, I appreciate it.
Had the same problem tried to flash back to 2.8.6.0 via TWRP and didn't work and seemed like recovery had disapeared so used TWRP App to install 2.8.6.1 booted into recovery then rebooted and tried to downgrade to 2.8.6.0 but got a message about same recovery, rebooted phone tried again and it installed no problem.
stylez said:
Had the same problem tried to flash back to 2.8.6.0 via TWRP and didn't work and seemed like recovery had disapeared so used TWRP App to install 2.8.6.1 booted into recovery then rebooted and tried to downgrade to 2.8.6.0 but got a message about same recovery, rebooted phone tried again and it installed no problem.
Click to expand...
Click to collapse
Hmm...maybe I'll give it another shot then. I had opted to just flash them via fastboot because I couldn't get it to work. It's not the worst thing ever. Thank you =)
Myrskyta said:
Is there any particular reason for Philz recovery over standard CWM?
Also, while this might be a viable option my understanding is that, that would render my old backups useless since I was previously using TWRP? That's kind of unfortunate. =(
Click to expand...
Click to collapse
just FYI, philz recovery does support TWRP backups. you just have to enable that feature in the settings
Oh! Thank you for letting me know. I'll keep that in mind. =)
Save yourself all that trouble, just flash modems with fastboot....fastboot flash modem modem.bin
Related
Hello, I seem to have soft bricked my tf700.
I flashed a newish pacman nightly in CWM (after wiping data/cache/dalvik cache), which completed with no errors, then I flashed the corresponding GAPPS. But my device became stuck in the pacman boot intro.
So I tried flashing slimkat which led to my device not getting past the first bootup screen (where you can enter recovery if pressing the corresponding buttons).
After this screw-up I stupidly hit the wipe data button on the bootloader. I then tried doing the method of using fastboot to erase system, cache, and all that so I could flash system blob of the newest asus US SKU (that is correct for a US bought tf700 right?). Either this or wiping the data caused me to have a different bootloader as pictured below as I no longer have the android button and it does not ask me to press volume up to access recovery (the only way to access recovery is by hitting the wipe data button in bootloader).
I can still fastboot flash CWM, but trying to flash TWRP does not work as it finishes but going into recovery causes the tablet to just restart. Trying to flash asus stock as above would always give me an error like the one pictured below. Similar errors occur if trying to flash any rom inside CWM via an external sd card.
I do not have access to adb as i believe i dont have usb debugging enabled since the pacman rom or any other rom did not ever start. It just gives me the device not found error even after manually installing the drivers on two different computers.
Cant seem to get these pics to load, but copying the url and pasting it works.
http://imgur.com/AaU0GMt
http://imgur.com/vDTVa4B
You probably flashed the wrong Rom. Try flashing the >right< stock Rom and go from there. Double check everything you flash.
tylerleo said:
You probably flashed the wrong Rom. Try flashing the >right< stock Rom and go from there. Double check everything you flash.
Click to expand...
Click to collapse
Whats the "right" rom here? Talking about the original asus stock rom? I have now tried the the pacman nightly, pacman release, slim kat release, clean rom release, an ICS asus stock rom, and two different versions of the jellybean asus stock rom. These were either done in CWM via internal sd card, external sd card, or done through fastboost flash system blob and flash zip.
gio3505 said:
Whats the "right" rom here? Talking about the original asus stock rom? I have now tried the the pacman nightly, pacman release, slim kat release, clean rom release, an ICS asus stock rom, and two different versions of the jellybean asus stock rom. These were either done in CWM via internal sd card, external sd card, or done through fastboost flash system blob and flash zip.
Click to expand...
Click to collapse
Whatever Rom came on the device,(Good thing to have, da) I'm not familiar with this device.
tylerleo said:
Whatever Rom came on the device,(Good thing to have, da) I'm not familiar with this device.
Click to expand...
Click to collapse
As far as i know, i have installed the stock rom, or atleast multiple versions of it with no success as it gives me an error stating something like staging or system when trying to write it.
gio3505 said:
As far as i know, i have installed the stock rom, or atleast multiple versions of it with no success as it gives me an error stating something like staging or system when trying to write it.
Click to expand...
Click to collapse
Hmm, I'd Download a stock Rom for the device offline, take on the sd card and put it on there real quick and try to flash that, if not, you probably bricked your device. I wouldn't know how to fix it beyond that. Ask the dev that made the Rom were everything that went south and an email to cwm wouldn't hurt either
I am also not sure if I need to have my external sd card formatted a certain way or download a specific CWM to allow flashing the stock rom. Ive spent over 10 hours trying to figure this out, very frustrating.
I have run CWM 6.0.4.6, CWM 6.0.4.7, and older versions to see if I could flash the stock rom with no luck. I have also tried different versions of TWRP but they always hang and reboot my tf700. I get errors ranging from status 6, status 7, cannot mount data, cannot mount staging, and cannot mount system. I am completely lost on what I can do. I have even tried a seperate sdcard to see if maybe the one I was originally using was bad with no luck. GG :/
gio3505 said:
I have run CWM 6.0.4.6, CWM 6.0.4.7, and older versions to see if I could flash the stock rom with no luck. I have also tried different versions of TWRP but they always hang and reboot my tf700. I get errors ranging from status 6, status 7, cannot mount data, cannot mount staging, and cannot mount system. I am completely lost on what I can do. I have even tried a seperate sdcard to see if maybe the one I was originally using was bad with no luck. GG :/
Click to expand...
Click to collapse
You gotta stop flashing stuff and slow down!
During all of this you never posted your bootloader version, so you may have been on the wrong bootloader to begin with - who knows.
When you hit the Wipe Data in the bootloader menu you caused the BL do write a wipe data command to the misc partition, causing the tablet to boot to recovery each time you booted (I'm guessing here) and then interrupting it. Usually, with CWM installed, it eventually sorts it out and executes the wipe data command, but that takes hours! You just have to leave it alone.
Hard to tell where you are now since you flashed all kinds of stuff since then.
Can you still boot into the bootloader and have a fastboot connection?
What's the BL version number?
If you boot, what does it boot into?
The picture links are broken - at least in Tapatalk. Post them again?
berndblb said:
You gotta stop flashing stuff and slow down!
During all of this you never posted your bootloader version, so you may have been on the wrong bootloader to begin with - who knows.
When you hit the Wipe Data in the bootloader menu you caused the BL do write a wipe data command to the misc partition, causing the tablet to boot to recovery each time you booted (I'm guessing here) and then interrupting it. Usually, with CWM installed, it eventually sorts it out and executes the wipe data command, but that takes hours! You just have to leave it alone.
Hard to tell where you are now since you flashed all kinds of stuff since then.
Can you still boot into the bootloader and have a fastboot connection?
What's the BL version number?
If you boot, what does it boot into?
The picture links are broken - at least in Tapatalk. Post them again?
Click to expand...
Click to collapse
Yes, the pictures are broken. You can still copy paste the url though. Couldnt figure out why it wouldnt work.
The tablet boots into the first screen that states it is unlocked, but does not go any further.
There is no bootloader version on the top left when holding down power + volume down.
I can still get to the place where it allows me to wipe data or fastboot, but the android icon to boot into android is now gone.
adb does not recognize my device even after manually installing the drivers, but fastboot works fine.
Is there any other way to find my bootloader version?
gio3505 said:
Yes, the pictures are broken. You can still copy paste the url though. Couldnt figure out why it wouldnt work.
The tablet boots into the first screen that states it is unlocked, but does not go any further.
There is no bootloader version on the top left when holding down power + volume down.
I can still get to the place where it allows me to wipe data or fastboot, but the android icon to boot into android is now gone.
adb does not recognize my device even after manually installing the drivers, but fastboot works fine.
Is there any other way to find my bootloader version?
Click to expand...
Click to collapse
Maybe you want to edit your post with the urls then.... Makes it easier for people trying to help...
You're seriously messed up, I think. I see a USB icon in there which would indicate that your bootloader is ancient. But then it says: "starting USB fastboot protocol".
Is that after you selected the USB icon?
Anyway, I think you're only chance is buster99's method to get it back. Did you try that already?
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Naturally you have to extract the system blob from the 10.6.1.14.10 US Asus firmware, but then you can try to fastboot flash it with buster's method.
Good luck!
berndblb said:
Maybe you want to edit your post with the urls then.... Makes it easier for people trying to help...
You're seriously messed up, I think. I see a USB icon in there which would indicate that your bootloader is ancient. But then it says: "starting USB fastboot protocol".
Is that after you selected the USB icon?
Anyway, I think you're only chance is buster99's method to get it back. Did you try that already?
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Naturally you have to extract the system blob from the 10.6.1.14.10 US Asus firmware, but then you can try to fastboot flash it with buster's method.
Good luck!
Click to expand...
Click to collapse
Its starts the usb fastboot automatically if no input is selected. I had a different bootloader up until i tried that thing that buster did. It always gives me an error like cant write to system or something if i try it.
gio3505 said:
Its starts the usb fastboot automatically if no input is selected. I had a different bootloader up until i tried that thing that buster did. It always gives me an error like cant write to system or something if i try it.
Click to expand...
Click to collapse
Which blob did you flash with buster's method?
I'm afraid you flashed something totally incompatible with your tablet...
You did not generate your nvflash blobs sometime prior to this, did you?
berndblb said:
Which blob did you flash with buster's method?
I'm afraid you flashed something totally incompatible with your tablet...
You did not generate your nvflash blobs sometime prior to this, did you?
Click to expand...
Click to collapse
I flashed the asus stock rom downloaded from their website. The US version as it was bought in the US (right? 0.o). I hadnt heard of nvflash before trying to install a rom so i did not make a backup.
gio3505 said:
I flashed the asus stock rom downloaded from their website. The US version as it was bought in the US (right? 0.o). I hadnt heard of nvflash before trying to install a rom so i did not make a backup.
Click to expand...
Click to collapse
Are you sure you downloaded the correct firmware? For the TF700?
Do you still have the original zip you extracted the blob from?
Post the exact file name please.
berndblb said:
Are you sure you downloaded the correct firmware? For the TF700?
Do you still have the original zip you extracted the blob from?
Post the exact file name please.
Click to expand...
Click to collapse
US_epaduser10_6_1_14_10_UpdateLauncher (2)
or
US_epaduser_VER104425UpdateLauncher
or
US_epad_user_9_4_5_30_20120907_UpdateLauncher
Ive downloaded a lot of different versions from the asus website. The last one came from a forum post listing older firmware, which I have tried a lot of different ones.
gio3505 said:
US_epaduser10_6_1_14_10_UpdateLauncher (2)
or
US_epaduser_VER104425UpdateLauncher
or
US_epad_user_9_4_5_30_20120907_UpdateLauncher
Ive downloaded a lot of different versions from the asus website. The last one came from a forum post listing older firmware, which I have tried a lot of different ones.
Click to expand...
Click to collapse
You flashed all of those blobs???
In which order?
With what result?
Jeez - I think you're done for...
Sorry mate, but gotta catch some sleep now. Maybe somebody else has a bright idea...
berndblb said:
You flashed all of those blobs???
In which order?
With what result?
Jeez - I think you're done for...
Sorry mate, but gotta catch some sleep now. Maybe somebody else has a bright idea...
Click to expand...
Click to collapse
I flashed the newest one first, and it gave me one of those errors that wouldnt allow me to flash it, and i tried the others with the same result. So technically i didnt flash any of them. I have been able to flash some roms, but they wouldnt boot so i would be stuck where i was when i started.
gio3505 said:
I flashed the newest one first, and it gave me one of those errors that wouldnt allow me to flash it, and i tried the others with the same result. So technically i didnt flash any of them. I have been able to flash some roms, but they wouldnt boot so i would be stuck where i was when i started.
Click to expand...
Click to collapse
Right stop flashing random stuff - you have combinations of JB4.2.1, JB4.1.1 and ICS 4.0.3 just listed there.
Let me put a call out to @lj50036 who may be able to save you but if you have messed the bootloader up with no nvflash backups you are not going to be happy with the result. If you can still get to the bootloader screen then he can perform miraculous superhero acts and *maybe* save your device.
gio3505 said:
I flashed the newest one first, and it gave me one of those errors that wouldnt allow me to flash it, and i tried the others with the same result. So technically i didnt flash any of them. I have been able to flash some roms, but they wouldnt boot so i would be stuck where i was when i started.
Click to expand...
Click to collapse
Shoot me an email at [email protected]
We can use hangouts see if there is a solution to your issue ...
Thx Josh
Ive tried CM 11, C-Rom, Pac-Man, and PA.
I have to sideload them using CWM's install from sideload, I reboot and it just gets stuck on the loading screen, for every single ROM.
And now somehow my backup is corrupted and I cant install that either.
I've been searching for hours, how do I fix this.
Is there a stock Boost mobile rom somewhere I could try? Nothing seems to be working except for CWM.
Thanks in advance.
rnaodm said:
Ive tried CM 11, C-Rom, Pac-Man, and PA.
I have to sideload them using CWM's install from sideload, I reboot and it just gets stuck on the loading screen, for every single ROM.
And now somehow my backup is corrupted and I cant install that either.
I've been searching for hours, how do I fix this.
Is there a stock Boost mobile rom somewhere I could try? Nothing seems to be working except for CWM.
Thanks in advance.
Click to expand...
Click to collapse
Here are the stock ROMs to be flashed in fastboot: http://sbf.droid-developers.org/phone.php?device=14
Thank you ill try that right away!
Do I install it from cwm? There doesnt seem to be an option to install it from fastboot, Just the following:
Normal Powerup
Recovery
Factory
Switch Console
Barcodes
BP Tools
I got some MoKee Build and it actually booted but was full of errors and app crashes.
rnaodm said:
Do I install it from cwm?
Click to expand...
Click to collapse
No, look here: http://forum.xda-developers.com/showthread.php?t=2542219
It's a batch file executed from a PC
Thanks again, Ive had a few android devices and ran multiple roms, never ran into this problem before though.
rnaodm said:
Thanks again, Ive had a few android devices and ran multiple roms, never ran into this problem before though.
Click to expand...
Click to collapse
You're welcome. Make sure you flash the version you had before. Downgrading can be a pain.
Once your stock ROM is restored, you can flash a custom recovery and ROM again
I cant really get the flashboot commands working, adb doesnt see my device in fastboot mode. Ill have to keep trying. Its odd how Ive gotten two roms to boot, but the background apps kept crashing.
Thanks
I got it, I extracted the stock firmware zip in the Minimal ADB and Fastboot folder, and instead of mfastboot, I just used fastboot, And its loading the stock moto globe now.
Hopefully this thread helps others who might be in my situation.
Thanks Dalek kuchen!
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....
Okay, many of us don't do this everyday but I flashed TWRP 3.0.2.0 on my OPO and needed to go back to 2.8.6.0 to use jgcaap's MM build.
So i tried flashing 2.8.6.0 img file from 3.0.2 and guess what happened? No. It didn't downgrade it self, instead I lost my recovery. My phone rebooted straight to system after being stuck on Bootlogo for a while. So I flash the recovery AGAIN via fastboot, flashify, RashR, Flashfire, Mobile Terminal whatever I could think of. But nope, same result whatsoever. Flashing other recoveries doesn't work either. Same errors return.
Then I thought of flashing 3.0.0.0 instead of 2.8.6.0 and yes, flashing 3.0.0.0 from 3.0.2.0 worked indeed. Then I started to download all the recovery files till 2.8.6.0 and started flashing them one after another, step by step climbing down the number and it kept downgrading but ONE version down at a time, if I try to skip it returns the same bs as before. Then flashing down until I reached 2.8.6.0 and then flashed that too via RashR. And surprise! Surorise! The recovery version I needed was not working. It would be flashed then the recovery would disappear and it would go into a no recovery state like before again. Then I'd flash 2.8.6.1 and get recovery back. And now finally after all the endeavor I'm on 2.8.6.1.
Anybody might know the reason of this stupid anomaly? And why it doesn't work?
And also why I can't flash ANY OTHER recovery?
Unnecessary screenshot attached :good: enjoy~
Tiash420 said:
Okay, many of us don't do this everyday but I flashed TWRP 3.0.2.0 on my OPO and needed to go back to 2.8.6.0 to use jgcaap's MM build.
So i tried flashing 2.8.6.0 img file from 3.0.2 and guess what happened? No. It didn't downgrade it self, instead I lost my recovery. My phone rebooted straight to system after being stuck on Bootlogo for a while. So I flash the recovery AGAIN via fastboot, flashify, RashR, Flashfire, Mobile Terminal whatever I could think of. But nope, same result whatsoever. Flashing other recoveries doesn't work either. Same errors return.
Then I thought of flashing 3.0.0.0 instead of 2.8.6.0 and yes, flashing 3.0.0.0 from 3.0.2.0 worked indeed. Then I started to download all the recovery files till 2.8.6.0 and started flashing them one after another, step by step climbing down the number and it kept downgrading but ONE version down at a time, if I try to skip it returns the same bs as before. Then flashing down until I reached 2.8.6.0 and then flashed that too via RashR. And surprise! Surorise! The recovery version I needed was not working. It would be flashed then the recovery would disappear and it would go into a no recovery state like before again. Then I'd flash 2.8.6.1 and get recovery back. And now finally after all the endeavor I'm on 2.8.6.1.
Anybody might know the reason of this stupid anomaly? And why it doesn't work?
And also why I can't flash ANY OTHER recovery?
Click to expand...
Click to collapse
Did you try flashing the recovery img via TWRP itself? And are you using any theme on TWRP 3.x.x.x?
Nope no themes and I tried flashing through every method I could think of but nope, doesn't work.
Tiash420 said:
Nope no themes and I tried flashing through every method I could think of but nope, doesn't work.
Click to expand...
Click to collapse
You don't need to be on TWRP 2.8.6.0 to flash jgcaap MM build. Just use 3.0.2.0 it flashes modem and does everything the older one you're trying to get to can do.
Sent from my A0001 using Tapatalk
Renosh said:
You don't need to be on TWRP 2.8.6.0 to flash jgcaap MM build. Just use 3.0.2.0 it flashes modem and does everything the older one you're trying to get to can do.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I get the notification quick settings bug, I mean, I can't get quick setting toggles directly from notification nor can I have a regular basic swipe lock screen. And the bugs persist no matter which ever recovery I'm flashing through and with or without Gapps. How do I get pass that? Meanwhile my friend on the other hand downloaded the same version from the same place and he doesn't face those bugs. :'| Why is this happening to me?
Tiash420 said:
I get the notification quick settings bug, I mean, I can't get quick settings directly from notification nor can I have a regular basic swipe lock screen. And the bugs persist no matter which ever recovery I'm flashing through and with or without Gapps. How do I get pass that?
Click to expand...
Click to collapse
I've been seeing mentions of flashing 21/4 build first set it up then dirty flash latest update. I also got the same issue when I last flashed jgcaap MM ROM. It would have been best to just ask for advise there than assume it's a recovery issue
Sent from my A0001 using Tapatalk
Renosh said:
I've been seeing mentions of flashing 21/4 build first set it up then dirty flash latest update. I also got the same issue when I last flashed jgcaap MM ROM. It would have been best to just ask for advise there than assume it's a recovery issue
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I'll thank my friends who owned the OPO before I did for the recovery 'assumptions' :|
Tiash420 said:
I'll thank my friends who owned the OPO before I did for the recovery 'assumptions' :|
Click to expand...
Click to collapse
I'm guessing they insisted because of the previous problems with flashing modems for TWRP. Flash the latest 3.0.2.0 and I guarantee it'll work for every ROM only issue that still exists is if you want encryption on CM13 and that's present on all current TWRP versions
Sent from my A0001 using Tapatalk
Renosh said:
I'm guessing they insisted because of the previous problems with flashing modems for TWRP. Flash the latest 3.0.2.0 and I guarantee it'll work for every ROM only issue that still exists is if you want encryption on CM13 and that's present on all current TWRP versions
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Well doesn't matter, I flashed Sultan's unofficial CM13 build via Kumajaya's TWRP 3.0.0.0 and it works fabulously! jgcaap can wait, I'm sure it's not much different in features and stuff! :3
Hey folks; I'm hoping I can get some advice or pointers, or maybe just a slap upside the head with something I've missed.
I have one of the original Shield tablets, and played around with it quite a lot, installing various custom ROMs from the marvelous directions I've found here. When the battery thing happened, I submitted the required info and happily received my new tablet. The original was rooted and customised still, kill-switch averted, and I had two working tablets. I gave the new stock one to my wife.
But then, about three months ago, I was playing with mine again installing a newer ROM than the one I was using (I *think* I was going from an older Bliss rom to one of the Cyanogen), and ... Something Happened (tm). The tablet rebooted in the middle of everything, and now won't boot to an image.
I'm on Windows 10 now, and had some fun getting the drivers working, but they seem to. I can communicate with the tablet through Fastboot, but ADB doesn't see it. I've flashed several versions of TWRP to the tablet, and can boot into that recovery - both through Fastboot and the tablet's power+vol-dn buttons. I've used TWRP to flash several different ROMs, and it *appears* to work (there are no errors), but when I reboot the tablet .... nada. Nothing but the Nvidia boot screen for days.
So now... what have I missed? I'm a little reluctant to flash a stock ROM, but I'm at a loss. I used to have more time to fiddle and figure, and I'm afraid that my impatience is going to kill the thing.
Format system and data see if that works
You need to have the latest bootloader to run the latest roms.
Sent from my ZTE A2017U using Tapatalk
skooter32 said:
Format system and data see if that works
Click to expand...
Click to collapse
Have done, but I'll try it again. Thanks
lafester said:
You need to have the latest bootloader to run the latest roms.
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
I've tried the latest and the not-so-latest, all with similar results.
Hnefatafl said:
I've tried the latest and the not-so-latest, all with similar results.
Click to expand...
Click to collapse
so you wan t your "burning" tablet set again stock?
Did you read about "recovery images" for shield tablet?
If fastboot is working you can flash the recovery image and all will update to the latest(blob,system,boot, etc)
flash latest twrp for shieldtablet.
after that use the nomoreota.zip to prevent the software brick from nvidida
Hnefatafl said:
Have done, but I'll try it again. Thanks
Click to expand...
Click to collapse
Also format data system to something other than ext4 then re format it back
skooter32 said:
Also format data system to something other than ext4 then re format it back
Click to expand...
Click to collapse
can I ask what that should bring?
wiQbold said:
so you wan t your "burning" tablet set again stock?
Did you read about "recovery images" for shield tablet?
If fastboot is working you can flash the recovery image and all will update to the latest(blob,system,boot, etc)
flash latest twrp for shieldtablet.
after that use the nomoreota.zip to prevent the software brick from nvidida
Click to expand...
Click to collapse
No, I don't want it stock at all, I was just worried that was my only option to get this thing to respond again. I was running BlissPop v.somethingorother, but wanted to update. That's when things went awry.
Right, well it looks like I've got this thing going. I could flash TWRP 3.1.0-0, but not any 3.1.1. Cyanogenmod 12 worked. Reading up a little more (it got slow at work for a couple of days...) I flashed the firmware to 5.0, and could now install TWRP 3.1.1-1! Then I could install (in this case) Lineage 14.1, which *almost* worked. It booted, but there's no wifi.
Then I found a suggestion - I think it was on these forums somewhere - and restarted. Wiped all data again, flashed Cyanogenmod 12, no gapps. Restarted, checked everything including wifi, and is good. Rebooted back into recovery, performed a factory reset, then installed Lineage 14.1 and gapps. When it rebooted, everything is working!
So. Firmware. Huh.
Thanks all.
Hnefatafl said:
No, I don't want it stock at all, I was just worried that was my only option to get this thing to respond again. I was running BlissPop v.somethingorother, but wanted to update. That's when things went awry.
Click to expand...
Click to collapse
do not know if you need the bootloader(blob) from nougat to boot up, that lafester told you. but that sounds plausible. skooter says something from re-formating. so if you tried that all and nothing changes? cache and data partition you wiped also, so it has to be work for my understanding.
went always stock, so can t help you..
but you can use recovery images > twrp > bliss/linage. no need to boot up stock?
wiQbold said:
can I ask what that should bring?
Click to expand...
Click to collapse
I have had similar issues and I tried everything even this plus what harm is it going to be and as the fellow below said if ur in fastboot and recovery with no issues then surely u should be flashing stick to fix Ur problem ?