Related
Hey guys.
I just got a very nice condition used TF700T. I am trying to get recovery to install so I can flash a rom. I used the Transformer Toolkit to unlock it, which worked, it says device unlocked when booting.
But I absolutely cannot get it to Root, or flash recovery. If I try using debugfs root generic 2.3 it fails to write everything. If I try to flash any recovery with the toolkit it downloads and says flashing but just sits at about 25%, it boots my device into the screen that says usb fastboot mode with the three icons that say RCK Android and factory wipe. If I click the RCK it says rebooting and then goes to android mascot installing icon, but then the one with an X and error appears. What on earth am I doing wrong?
Is it the latest 4.2 update locking me out? Can I downgrade? I just can't get anything to root or flash recovery no matter what I do. I feel a little defeated being a long time member and 3 phone habitual rom flasher :crying:\
Any ideas what i'm missing?
benjmiester said:
Hey guys.
I just got a very nice condition used TF700T. I am trying to get recovery to install so I can flash a rom. I used the Transformer Toolkit to unlock it, which worked, it says device unlocked when booting.
But I absolutely cannot get it to Root, or flash recovery. If I try using debugfs root generic 2.3 it fails to write everything. If I try to flash any recovery with the toolkit it downloads and says flashing but just sits at about 25%, it boots my device into the screen that says usb fastboot mode with the three icons that say RCK Android and factory wipe. If I click the RCK it says rebooting and then goes to android mascot installing icon, but then the one with an X and error appears. What on earth am I doing wrong?
Is it the latest 4.2 update locking me out? Can I downgrade? I just can't get anything to root or flash recovery no matter what I do. I feel a little defeated being a long time member and 3 phone habitual rom flasher :crying:\
Any ideas what i'm missing?
Click to expand...
Click to collapse
What custom recovery are you installing? You may want to try with fastboot or adb method to flash your custom recovery which doesn't require rooted device, good luck....
LetMeKnow said:
What custom recovery are you installing? You may want to try with fastboot or adb method to flash your custom recovery which doesn't require rooted device, good luck....
Click to expand...
Click to collapse
Well I tried TWRP 2.7.1.1 I believe and also CWM , and Phil's custom touch CWM that all three are options to flash with the all in one ADB Toolkit app via USB from windows (http://forum.xda-developers.com/showthread.php?t=2094746)
How do I do the Fastboot method? I read about that, but have no idea how the process goes. I'm ok with skipping root and going straight to recovery and a rom because I can just flash superuser after if the rom isn't rooted already.
benjmiester said:
Well I tried TWRP 2.7.1.1 I believe and also CWM , and Phil's custom touch CWM that all three are options to flash with the all in one ADB Toolkit app via USB from windows (http://forum.xda-developers.com/showthread.php?t=2094746)
How do I do the Fastboot method? I read about that, but have no idea how the process goes. I'm ok with skipping root and going straight to recovery and a rom because I can just flash superuser after if the rom isn't rooted already.
Click to expand...
Click to collapse
I wanted to try an app I used to get twrp onto my LG G2 for the first time called "flashify" that worked like a charm. I just installed the app, downloaded the twrp file and flashed it then it reboots to recovery, but it requires root as far as I know. Does unlocking the boot loader allow things like this?
benjmiester said:
I wanted to try an app I used to get twrp onto my LG G2 for the first time called "flashify" that worked like a charm. I just installed the app, downloaded the twrp file and flashed it then it reboots to recovery, but it requires root as far as I know. Does unlocking the boot loader allow things like this?
Click to expand...
Click to collapse
Unlocked bootloader is allowed you to install the custom recovery so you can install the custom ROM, I believed..... You can check this guide out to see if you can setup your fastboot/adb. It is very easy to follow for the beginners, good luck....:fingers-crossed:
http://forum.xda-developers.com/showthread.php?t=2688891
benjmiester said:
I wanted to try an app I used to get twrp onto my LG G2 for the first time called "flashify" that worked like a charm. I just installed the app, downloaded the twrp file and flashed it then it reboots to recovery, but it requires root as far as I know. Does unlocking the boot loader allow things like this?
Click to expand...
Click to collapse
Once you unlocked the bootloader you can flash a custom recovery and after that - the sky's the limit.
Flashify works great, and it is a wonderful tool as long as you're able to boot into Android.
My problem with Flashify and Goomanager and TwrpManger is that it saves users from setting up a proper ADB/fastboot connection from PC to tablet.
As long as you can boot Android, these apps are great. But what if you can't? Once the tablet doesn't boot it's so much harder (and often too late) to get the correct drivers installed for ADB and fastboot.
So if you flash your recovery with any of those apps still make sure you have access with ADB and fastboot from your PC.
You will regret it if you don't - I (almost) guarantee it.
That's an excellent point. Thanks. I did actually get the Fastboot method to work. The problem was that I kept clicking into RCK recovery when I ws supposed to just leave it on that screen to push twrp instead. I got recover and just got done doing a backup. I'm about the flash my first rom (http://forum.xda-developers.com/showthread.php?t=2672751). Do we need to do factory reset / wipe data/system etc? The instructions on the ROM post say to just flash it from twrp so I'm guessing it has a built in wipe feature during install?
benjmiester said:
That's an excellent point. Thanks. I did actually get the Fastboot method to work. The problem was that I kept clicking into RCK recovery when I ws supposed to just leave it on that screen to push twrp instead. I got recover and just got done doing a backup. I'm about the flash my first rom (http://forum.xda-developers.com/showthread.php?t=2672751). Do we need to do factory reset / wipe data/system etc? The instructions on the ROM post say to just flash it from twrp so I'm guessing it has a built in wipe feature during install?
Click to expand...
Click to collapse
The instructions in the OP actually say that you have to do a full wipe (Factory Wipe) in TWRP coming from a different rom base. Which would be you unless you had a version of CROMBi-KK installed prior to this.
It's the default selection under the Wipe menu in TWRP. Just do that and then flash the rom and your ok.
Do not use the Factory Reset option from Settings or the Wipe Data option from the BL menu! Do this in TWRP only!
Cool thanks. I figured so because that's the norm with roms on all my phones. Thanks a lot for the help guys. So happy to be get KK running on my new toy!
Just wanted to update. KK 4.4.3 rom flashed and booted in. It's much nicer. The stock was a little laggy, and KK breathed a lot of new life into my ancient single core 1.0 ghz Galaxy S that I use as a music player so I figured it would help make the tab real nice and snappy too. Gotta go now, much fun to be had!!
Hi,
Just for you to know:
Model: r7plusf
Recovery: TWRP 3.0.2-0
----------------------------------------
So earlier today I did an OTA update (cm-14.1-20161205-NIGHTLY-r7plus.zip), but couldn't get my phone to boot.
So naturally, I tried wiping Cache and ART cache, but was still bootlooping.
Thought there might be someting wrong with my ROM and data, so I formated data and Installed ROM and GAPPS again after ADB pushing them onto my phone.
Now, and although CM14.1 and GAPPS are successfully installed on my Oppo R7 Plus, I can't boot into the OS. Every time I try reboot system, whether through POWER_BUTTON, RECOVERY or ADB, I just boot into Recovery.
Worst of all, for some unknown reason, I can't get into BOOTLOADER, neither through button combination, nor through Recovery nor ADB.
I found this article (http://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386) in the LG G3 thread about executing some shell commands, but I haven't tested testing it with my phone's variables because it might hard brick it...
Please Help!
[EDIT] I now have access to fastboot but still recovery looping like crazy.
I installed the same update via CyanDelta , worked like a charm ! hopefully you get back up and running.
[UPDATE] strangely I tried to flash stock recovery and boot CM13 and it worked!
Will try to flash twrp again and insall CM14
keep you up to date
Same thing happened to me! Where did you get a copy of the stock recovery? Link?
resverse said:
[UPDATE] strangely I tried to flash stock recovery and boot CM13 and it worked!
Will try to flash twrp again and insall CM14
keep you up to date
Click to expand...
Click to collapse
I had the same problem. Can't remember exactly how I resolved it. But I think, I use CM recovery to flash nightly. Then flash TWRP to flash gapps. For some strange reason, using CM recovery also show no enough disk space whenever I try to flash opengapps. But TWRP recovery can flash opengapps successfully.
Don't use the OTA, use adb sideload to flash the nightly next time. So far, adb sideload has not given me any issue to flash nightly.
Same problem...
I tried a lot of things nothing works and now I've installed the cm recovery but I have the "unauthorized phone" in terminal when I try to flash the ROM... I can do nothing because I can't enable the usb debugging. I don't know what to do.
If somebody can help I appreciate.
corbalan12 said:
Same problem...
I tried a lot of things nothing works and now I've installed the cm recovery but I have the "unauthorized phone" in terminal when I try to flash the ROM... I can do nothing because I can't enable the usb debugging. I don't know what to do.
If somebody can help I appreciate.
Click to expand...
Click to collapse
Since then I found how to fix it :
first of all I flashed cm13 through TWRP,
Then I flashed the stock recovery (Google it, I found it in OPPO forums) with fastboot,
After that I did a factory reset in the stock recovery,
Booted cm13 with stock recovery,
Then re-flashed TWRP,
From TWRP, I wiped both data and system partitions,
Then fresh installed cm14 and Gapps
And it worked!
Not sure if those are the exact steps I followed because all I did was a hole lot of messing around and trying absurd things out, but think this is how I fixed it.
Let me know if it worked for you or if you still can't fix your problem
Best of luck
Resverse
resverse said:
Since then I found how to fix it :
first of all I flashed cm13 through TWRP,
Then I flashed the stock recovery (Google it, I found it in OPPO forums) with fastboot,
After that I did a factory reset in the stock recovery,
Booted cm13 with stock recovery,
Then re-flashed TWRP,
From TWRP, I wiped both data and system partitions,
Then fresh installed cm14 and Gapps
And it worked!
Not sure if those are the exact steps I followed because all I did was a hole lot of messing around and trying absurd things out, but think this is how I fixed it.
Let me know if it worked for you or if you still can't fix your problem
Best of luck
Resverse
Click to expand...
Click to collapse
Thank you very much!!!! I'll try tomorrow and tell you.
I appreciate a lot!
First of all now works but to be honest, I don't know if the way I fix makes sense or if is correct but not for the same reason I do but I'll try to explain...
I had cm-14.1-20161218-NIGHTLY and I tried to update via OTA to 20161220 the phone reboot and I get the bootloop. The first I thought, install again the ROM making wipe data and blabla... nothing work.
I tried to "reflash" the recovery, nothing. Flashed cm recovery, it always gave me error trying to flash the rom. I tried to install with stock recovery, errors too.
I was reading hundred of post looking for my issues, device unauthorized, "error 7" in twrp... I was crazy.
At last I thought, I've been trying to install from SDcard, if I try to install from internal memory? and I install again the twrp to transfer the ROM and Gapps to the internal memory and... it worked!!!!
Long story but with happy ending.
Thank you for your help I appreciate and sorry for my english.First of all now works but to be honest, I don't know if the way I fix makes sense or if is correct but not for the same reason I do but I'll try to explain...
I had cm-14.1-20161218-NIGHTLY and I tried to update via OTA to 20161220 the phone reboot and I get the bootloop. The first I thought, install again the ROM making wipe data and blabla... nothing work.
I tried to "reflash" the recovery, nothing. Flashed cm recovery, it always gave me error trying to flash the rom. I tried to install with stock recovery, errors too.
I was reading hundred of post looking for my issues, device unauthorized, "error 7" in twrp... I was crazy.
At last I thought, I've been trying to install from SDcard, if I try to install from internal memory? and I install again the twrp to transfer the ROM and Gapps to the internal memory and... it worked!!!!
Long story but with happy ending.
Thank you for your help I appreciate and sorry for my english.
I got my OnePlus 7 Pro today and tried to install Magisk by patching the boot.img. After trying to flash the patched image, I now have an issue where rebooting the devices leads me straight back to the bootloader. Trying to enter recovery also leads me straight back to the bootloader. I tried flashing the original boot.img I extracted from the OTA update file provided by OnePlus, but it still isn't working. I do not have TWRP or any custom recovery installed. Any help would be much appreciated. I noticed similar threads, however they all installed twrp, though I haven't yet as trying to run "fastboot boot twrp.img" always resulted in it booting to a screen saying "fastboot mode" which wasn't terribly helpful.
Edit: Its not the tmobile/5g/carrier version. I purchased it through OnePlus' website though I forget the exact model number.
Well, "fastboot boot twrp.img" does not work on all devices, sometimes you have to use: fastboot flash boot insert_twrp_img_name_here.imgLearned that the hard way, also use the unofficial twrp from mauronofrio.
Had the same problem as you have, and fixed it with that unofficial twrp.
Faith1105 said:
Well, "fastboot boot twrp.img" does not work on all devices, sometimes you have to use: fastboot flash boot insert_twrp_img_name_here.imgLearned that the hard way, also use the unofficial twrp from mauronofrio.
Had the same problem as you have, and fixed it with that unofficial twrp.
Click to expand...
Click to collapse
Did you need to completely revert to stock after the issue, or did flashing twrp fix the fastboot loop?
Edit: Trying to flash the stock fastboot rom currently as flashing twrp did nothing probably because me trying to fix it broke everything. Hopefully the stock rom will get everything back to a working state where I can try again, just this time flashing twrp.
Also using windows this time instead of linux....
mnbvcxzl90 said:
Did you need to completely revert to stock after the issue, or did flashing twrp fix the fastboot loop?
Edit: Trying to flash the stock fastboot rom currently as flashing twrp did nothing probably because me trying to fix it broke everything. Hopefully the stock rom will get everything back to a working state where I can try again, just this time flashing twrp.
Also using windows this time instead of linux....
Click to expand...
Click to collapse
Ok, so, trying to restore stock seems to have failed miserably.... any advice is most welcomed qq
OK.... so trying to unbrick the device using the msm stuff, I couldn't even make it to the downloader screen. After holding volume +/- and powering off, my screen is now black HOWEVER the phone gets detected by windows when I plug & unplug it. I have no idea what to do anymore. Someone please help
Figured I'd give the solution here in case someone else is in the same exact problem as me:
Follow the instructions over at https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
I tried to de-brick it using the fastboot roms and all that, no dice. The only thing that seems to have worked was following the above and using the msm tool. Everything wiped, but hey, at least the phone is bootable again and now I have a way to fix it should this happen again. Yay for happy endings.
Edit: Also, following Faith1105's advice, flashing twrp to boot instead of trying to just boot it first worked successfully and from there I was able to install magisk.
Edit 2: Now wifi isn't working.... why life, why...
Edit 3: OK: EVERYTHING IS GOOD NOW. Twrp ran into a boot loop issue, used twrp to flash the most recent android 10 zip, rebooted and was greeted by stock recovery, then used that to wipe absolutely everything and reboot. After skipping through initial setup and making use wifi was working I rebooted again and this time tried booting twrp the way the usual instructions say to, this time it worked for whatever reason so once that started I used twrp to flash twrp's installer and magisk. It looks like everything is working correctly now. If you have the same issue maybe this stuff will work for you or maybe not: I don't know, and honestly I'm now brain dead lol.
Hi guys,
so since a few days I have a really strange problem. No matter what I do, everytime I flash the TWRP installer after the rom I get stuck in a recovery loop.
I found out that if I do not install TWRP it will boot into the ROMs recovery. If I do a factory reset (erase everything) in there it will boot again just fine into the system.
If I install TWRP afterwards, for example through Magisk it will stay and work without any problem.
I've also tried a restore with the MSMDownloadTool multiple times (which worked without any problem) however after that, again, everytime I want to install a ROM and flash the TWRP installer afterwards
I'm stuck in the recovery.
I've never had this problem before and am at my wits end, because I just can't figure out what is causing this problem.
Did anyone of you also had this problem and found a way to resolve it? Any help would be much appreciated!
Note: I'm using this TWRP (3.3.1-71) -> https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Observed same behavior.
ROM: 10.0.1 GM21AA
TWRP: 3.3.1-71 q
Magisk: v20.1
EDIT: seems the problem is related to F2FS, after formatting data back to ext4 my phone booted.
aqua_hopps said:
Observed same behavior.
ROM: 10.0.1 GM21AA
TWRP: 3.3.1-70 q
Magisk: v20.1
EDIT: seems the problem is related to F2FS, after formatting data back to ext4 my phone booted.
Click to expand...
Click to collapse
Good to know, however in that case it seems that my problem is unrelated to this, as I have never used F2FS.
TheExoduser said:
Hi guys,
so since a few days I have a really strange problem. No matter what I do, everytime I flash the TWRP installer after the rom I get stuck in a recovery loop.
I found out that if I do not install TWRP it will boot into the ROMs recovery. If I do a factory reset (erase everything) in there it will boot again just fine into the system.
If I install TWRP afterwards, for example through Magisk it will stay and work without any problem.
I've also tried a restore with the MSMDownloadTool multiple times (which worked without any problem) however after that, again, everytime I want to install a ROM and flash the TWRP installer afterwards
I'm stuck in the recovery.
I've never had this problem before and am at my wits end, because I just can't figure out what is causing this problem.
Did anyone of you also had this problem and found a way to resolve it? Any help would be much appreciated!
Note: I'm using this TWRP (3.3.1-71) -> https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Click to expand...
Click to collapse
Sounds like your using bad command. fastboot boot whatever.img, it's better if after the word boot, drag and drop TWRP.img into command line. Oh, try 3.3.1-70, then upgrade TWRP to 71, I was having the same issue.
I have two devices where install TWRP dont work.
They are unlocked and i try many times to flash it via fastboot but booting into recovery ends in stock recovery.
Is there any solution to install TWRP or lineageos another way?
it was the issue that recovery is overwritten on stock rom start if the system has ever made an update