Related
Hi,
I have an LG G2 D802 and already installed TWRP 2.6.3.4 for installing zip-files. But now there is an update (only browser, but 4.4 shouldn't be that far away), but without stock recovery it's impossible to install it I know the way how to get back to stock completely, but I don't want to go back to stock every time there is an update, installing all of them and then reinstall TWRP. I think on CWM the problem is the same, but i don't want to miss the camera tweak and splitwindow, so I need an custom recovery for the zip-files:crying: Is there any way to get the stock recovery back without installing complete stock or at least a possibility, to only "boot" the custom recovery when I'm back on stock, like on Nexus devices, and only use it for the flashing and then lose it on the next reboot?
You should be able to push stock recovery via adb or even flashify ( I prefer adb tho). What build number do you have?
Sent from chdhsheh fhhdud
simon_lefisch said:
You should be able to push stock recovery via adb or even flashify ( I prefer adb tho). What build number do you have?
Sent from chdhsheh fhhdud
Click to expand...
Click to collapse
I have D80210a-EUR-XX. But where can I find the stock recovery? And btw: what was the adb command for flashing? With my Nexus 4 I only used the ToolKit, because I was never able to use adb through the normal Win7 cmd, only through the toolkit...
most likely, but cannot confirm it, you ooen a stock kdz, and try flashing the kernel .img thats inside, I am not sure
anyone confirm it works that way
Sent from my LG-D802 using xda app-developers app
for all I know, the kernel doesn't contain any recovery... but I will test it tomorrow, when I downloaded the kdz if you could say me how to open a kdz-file.
Artim_96 said:
I have D80210a-EUR-XX. But where can I find the stock recovery? And btw: what was the adb command for flashing? With my Nexus 4 I only used the ToolKit, because I was never able to use adb through the normal Win7 cmd, only through the toolkit...
Click to expand...
Click to collapse
here is a link to D802 recovery.img file i found, however its for the 10B build. you should be ok as i dont think the recovery has changed much from 10A to 10B, however i cannot confirm this. use this at your own risk, unless someone can confirm this will recovery will work.
simon_lefisch said:
here is a link to D802 recovery.img file i found, however its for the 10B build. you should be ok as i dont think the recovery has changed much from 10A to 10B, however i cannot confirm this. use this at your own risk, unless someone can confirm this will recovery will work.
Click to expand...
Click to collapse
If it's not working, I have a backup of the current. but I will test it tomorrow, then I have more time. But thanks for the quick answers.
Flashing the 10B recovery image worked well. But installing the update I only get an error so I go back to stock now.
I saw that flashify can flash zip files. Does it flash them itself or does it also need a custom recovery to flash them with it and flashify is only some sort of automtatisation? Then I could use this when I'm back on stock 10A (there seems to be no 10B for my device).
Artim_96 said:
Flashing the 10B recovery image worked well. But installing the update I only get an error so I go back to stock now.
I saw that flashify can flash zip files. Does it flash them itself or does it also need a custom recovery to flash them with it and flashify is only some sort of automtatisation? Then I could use this when I'm back on stock 10A (there seems to be no 10B for my device).
Click to expand...
Click to collapse
I've had similar problem, i think I just installed the KDZ file trough the way they showing: http://forum.xda-developers.com/showthread.php?t=2432476
It just erased the rooy and TWRP, and all of the apps and settings did not change, its like a repach.
at least it should be. but I can't take the last step. "By turning off, Holding down power and Vol Down until it comes up on the screen." doesn't works, there only starts the normal software, and that's the old one. And unpacking the kdz file with 7zip or Peazip also don't work. Peazip can do ist, but I have to find out how to let it extract it. After installing it, there is another file with the same name, but it's an .cab file with password. If I boot over widgetsoid into recovery (I think this is what the manual means) there is only a little droid with a read sign. How to get further?
EDIT: found out how to come into that menu. It wants to make a hard reset so I make an backup first.
Finally I was able to install the complete new software version (D80210e-EUR-XX) over the LG PC Suite. The file downloaded from the manual seemed to be corrupted or so as it only caused an unpacking error in the programm.
Does anybody knows a way how to flash a zip without a custom rom? Flash Gordon seems to not work.
Hi I'm looking for the recovery of the stock LG G PAD tablet 7 "LTE I am root backup with TWRP but I can not go back to Recovery Stock.
Before flashing the TWRP I forgot to make a backup of Recovery
Sorry for my bad English.
thanks
exebuera said:
Hi I'm looking for the recovery of the stock LG G PAD tablet 7 "LTE I am root backup with TWRP but I can not go back to Recovery Stock.
Before flashing the TWRP I forgot to make a back of Recovery
Sorry for my bad English.
thanks
Click to expand...
Click to collapse
here's a link to an image I made before flashing twrp on my v410. I've restored it with dd and flashify and it works fine. https://docs.google.com/file/d/0B1l3W9XHAqEgX0ZCUWc1QTlfWjg/edit?usp=docslist_api
jason2678 said:
here's a link to an image I made before flashing twrp on my v410. I've restored it with dd and flashify and it works fine. https://docs.google.com/file/d/0B1l3W9XHAqEgX0ZCUWc1QTlfWjg/edit?usp=docslist_api
Click to expand...
Click to collapse
hey @jason2678 thanks, but how did i flash this if i dont have twrp installed? can i use fastboot or adb?
dreamtheater17 said:
hey @jason2678 thanks, but how did i flash this if i dont have twrp installed? can i use fastboot or adb?
Click to expand...
Click to collapse
I'd recommend flashify to flash recovery images. You can download it from the play store. So easy to make a typo and mess things up with adb and dd.
You could do it with a terminal or adb shell. Say you store the image in /sdcard
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p14
Verify mmcblk0p14 is recovery before you try this. I'm pretty sure that's right, but I don't have my tablet right now and you can make a serious mess of your device this way if you overwrite the wrong partition. Check it by listing your partitions with this:
Code:
su
ls -al /dev/block/platform/*/by-name
By default this little tablet does not have fastboot, but you can enable it with this method. I've zeroed out my laf partition and verified I can boot into fastboot mode, but I've never actually used it to flash anything. It just seemed like a good idea to have fastboot available to fall back on rather than LG download mode since there was no kdz available for the V410 for a long time.
jason2678 said:
I'd recommend flashify to flash recovery images. You can download it from the play store. So easy to make a typo and mess things up with adb and dd.
You could do it with a terminal or adb shell. Say you store the image in /sdcard
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p14
Verify mmcblk0p14 is recovery before you try this. I'm pretty sure that's right, but I don't have my tablet right now and you can make a serious mess of your device this way if you overwrite the wrong partition. Check it by listing your partitions with this:
Code:
su
ls -al /dev/block/platform/*/by-name
By default this little tablet does not have fastboot, but you can enable it with this method. I've zeroed out my laf partition and verified I can boot into fastboot mode, but I've never actually used it to flash anything. It just seemed like a good idea to have fastboot available to fall back on rather than LG download mode since there was no kdz available for the V410 for a long time.
Click to expand...
Click to collapse
Thank you! the thing is i bricked my g pad, i really dont know much about the tab because the lack of support it has. I was using it with cm12.1 and i use a stock recovery founded in Android central to revert back to stock, but in TWRP i flashed the img as recovery and also as boot, so the g pad entered in a bootloop were only enters in stock recovery, my Windows 10 laptop doesn't recognize the tab when in adb sideload, and doesn't know much about adb Shell, i'm following the comandas you wrote but i'm always getting error: closed.
i know how to get back to stock using the kdz, but using the kdz will make the partition issue and will have to folllow a looong looong process.
If you could give me a hand with this i would really apprecciate it
Sorry I've never encountered the adb closed problem myself, but I have heard about it before. Some people have reported the following series of commands fixes it:
Code:
adb usb
adb devices
adb kill-server
adb start-server
The first two commands normally don't really do anything and its pretty obvious what the second two do, but some people have reported success doing this.
Some people have reported the closed error was fixed by updating their adb binary. If you're using the android-sdk update platform-tools, or if you're using a standalone adb consider looking for an update for it.
Good luck. That procedure to get things back to normal following using the kdz to restore sounds messy.
dreamtheater17 said:
Thank you! the thing is i bricked my g pad, i really dont know much about the tab because the lack of support it has. I was using it with cm12.1 and i use a stock recovery founded in Android central to revert back to stock, but in TWRP i flashed the img as recovery and also as boot, so the g pad entered in a bootloop were only enters in stock recovery, my Windows 10 laptop doesn't recognize the tab when in adb sideload, and doesn't know much about adb Shell, i'm following the comandas you wrote but i'm always getting error: closed.
i know how to get back to stock using the kdz, but using the kdz will make the partition issue and will have to folllow a looong looong process.
If you could give me a hand with this i would really apprecciate it
Click to expand...
Click to collapse
hi, i have the same problem than u, i wanna know if i can flash the US CELLULAR kdz for solve the partition issue? because i already flash the kdz test from ATT
jason2678 said:
here's a link to an image I made before flashing twrp on my v410. I've restored it with dd and flashify and it works fine. https://docs.google.com/file/d/0B1l3W9XHAqEgX0ZCUWc1QTlfWjg/edit?usp=docslist_api
Click to expand...
Click to collapse
I flashed stock rooted 4.4.2, and I want to OTA to Stock Lollipop, but it says there is no update. Any ideas of how I can get back to fully stock? Would flashing this stock recovery make it work? Is being rooted blocking the OTA update from seeing an available update?
mxpxboi said:
I flashed stock rooted 4.4.2, and I want to OTA to Stock Lollipop, but it says there is no update. Any ideas of how I can get back to fully stock? Would flashing this stock recovery make it work? Is being rooted blocking the OTA update from seeing an available update?
Click to expand...
Click to collapse
If you applied an OTA with a custom recovery installed it might soft brick your tablet, but I don't see why that would stop it from detecting and downloading the update. It is always safest to flash stock recovery, fully unroot, and undo any modifications you've made to /system before taking an OTA, but some devices are more picky than others. With what you're describing I'm afraid that even if you do unroot and flash stock recovery your tablet still won't find the OTA.
Do you have a nandroid backup of an unmodified stock ROM you could restore?
And just so you know that lollipop bootloader is not vulnerable to the bump exploit, so no custom recovery or ROMs if you get it to apply.
Whenever I type "reboot recovery" in terminal emulator, it boots straight to factory reset. I have tried this multiple times with both dd and flashify. Do you know what causes this? I'm downloading the OTA right now, I hope it doesn't wipe then too...
please help
i was a dumbass and accidently flashed my boot instead of recovery do you by chance have a boot.img that i can use to reflash my boot.img please help as im really stuck..thanks in advance
Devil911 said:
i was a dumbass and accidently flashed my boot instead of recovery do you by chance have a boot.img that i can use to reflash my boot.img please help as im really stuck..thanks in advance
Click to expand...
Click to collapse
Download the timmytim stock ROM, and extract the boot.img from it. There are probably quicker ways, but having the stock ROM on hand is a good idea.
Sent from my Amazon Fire using XDA Labs
Thank you...
I resolved my issue i had forgotten in my haste i posted the same question in two different sections. However after fixing everything my tablet was broke not the out glass but the inner display. I cant afford another one or a replacement part to even fix mine. So unless i can find one someone who bricked theirs completely or get a handme down im tabless for awhile.... Thank you though for the reply. The original boot file wouldnt work properly i had to use the boot file from the stock rooted rom and not the timmytim deoxedized rom.. i dont know why unless the bootfile is specific to each rom. Maybe i did something wromg during the flash. But i had gotten it fixed nevertheless.
Devil911 said:
I resolved my issue i had forgotten in my haste i posted the same question in two different sections. However after fixing everything my tablet was broke not the out glass but the inner display. I cant afford another one or a replacement part to even fix mine. So unless i can find one someone who bricked theirs completely or get a handme down im tabless for awhile.... Thank you though for the reply. The original boot file wouldnt work properly i had to use the boot file from the stock rooted rom and not the timmytim deoxedized rom.. i dont know why unless the bootfile is specific to each rom. Maybe i did something wromg during the flash. But i had gotten it fixed nevertheless.
Click to expand...
Click to collapse
The stock rooted is by timmytim ?
I forgot about deodexed, actually.
Glad you fixed boot, shame your tablet broke ?
Sent from my Amazon Fire using XDA Labs
I posted this in the original DEV discussion and I also posted it as a reply to some people with the question. I'm only making this thread to save people from searching through hundreds and hundreds of posts. As you may know there is no kdz or tot for the v410 gpad. Without any clue as to why I woke up and my v410 was in twrp, tried a restore, a wipe, installing custom roms, each time it would say it was successful yet each time it would just boot right back into TWRP. Then i stumbled across a thread made by "Thecubed" in 2013 that had nothing to do with this device, it was a thread about being stuck in TWRP after OTA, so I thought id give it a shot and it worked like a charm 8) here are my instructions
1. if you dont have adb setup adb you can get a minimal adb here
https://www.androidfilehost.com/?fid=385035244224386526
install it, navigate to program files (Or if your on a 64bit system program files(x86)
Right click and click "Open command window here"
2. plug in your device if it isnt already pluged in, and type the following commands pressing ENTER after each line
DO NOT COPY PASTE THE WHOLE THING EACH LINE MUST BE PRESSED ENTERED separately
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
exit
adb reboot
Your phone should boot into your rom now
You can hit thanks for my effort of days of searching and you can also thank the dev of the thread that I got these instructions from "thecubed" here at this link http://forum.xda-developers.com/show....php?t=2451696 Hope this helps someone
Saved my ass tonight! Thanks bud!!
I'm stuck in your boat as well, only booting to twrp. The google docs link dead... but I was able to find the minimal adb. I haven't been able to get a working v410 driver though. Any ideas? I'm on Win10, so perhaps that's my problem.
Edit: I tried another v410 and my pc recognized it, so it's something to do with this tab being stuck in twrp and not getting recognized. if that helps.
I'm in the same boat, nothing I have tried, including the steps listed here seems to work.
If you check the first page of the link majicmazo provided, there are instructions for using the TWRP terminal command, which will start the process of getting it out of its current state.
mikiemc73 said:
If you check the first page of the link majicmazo provided, there are instructions for using the TWRP terminal command, which will start the process of getting it out of its current state.
Click to expand...
Click to collapse
Both links are broken, which is a special feat given the post is only 4 months old and edited on 8/26. Anyway the link you mentioned is correctly posted here: http://forum.xda-developers.com/showthread.php?t=2451696
However, if like me, your device cannot be recognized in Windows, and you're stuck in TWRP, you should run try and run the following command while in TWRP by clicking "Advance" then "Terminal Command" and "Select"
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
The command should run, then tap the return button until you're back to the main screen. Reboot without installing SuperSU.
I have 6 v410 devices with nearly exact same setups. I say nearly, because there must be something different that I'm not aware of. 4 out of 6 updated fine, 2 were bricked. 1 had to be sent to LG for warranty replacement. Go figure.
"I have 6 v410 devices with nearly exact same setups."
Good day, Sir! I have v410 and accidentally bricked it when I tried to change something in build.prop. I have no recovery installed. Nothing at all. The only change I did is the root and I cannot flash it due to some errors. A friend of mine told me I should find back up of other good v410 (.tot file if I'm not mistaken) and it could be applied to my bricked v410. Will it work? What method should be used for the .tot file? Are there anyway I could unbrick it without returning it to service centre? I have no warranty since I bought it abroad. I'm looking forward for your answers. Thank you!
I also have a stock recovery image if anyone needs it. Performing the above steps while in twrp will allow you to reboot back into device, but any updates from ATT will cause the device to brick back to TWRP.
If you flash the stock recovery here using flashify,: https://drive.google.com/open?id=0B9ztRll4cXJyTWktNXJLU2VDLU0, you will be able to install the ATTT updates without softbricking into twrp.
ChristopherXDA said:
I also have a stock recovery image if anyone needs it. Performing the above steps while in twrp will allow you to reboot back into device, but any updates from ATT will cause the device to brick back to TWRP.
Click to expand...
Click to collapse
Good!
Sir could you please provide an LG G Pad 7 v410 stock recovery image? I'll try to use it. Thank you!
The Krugz said:
Sir could you please provide an LG G Pad 7 v410 stock recovery image? I'll try to use it. Thank you!
Click to expand...
Click to collapse
Here is the v410 stock recovery: https://drive.google.com/open?id=0B9ztRll4cXJyTWktNXJLU2VDLU0
It worked for me but your mileage may vary. I'm not responsible for any issues.
Thank you, kind sir! I'll inform you if it does worked. :good:
Unfortunately, it didn't work. Perhaps you have v410 stock rom I can flash using lg flash tool?
V410 KDZ or stock recovery request.
ChristopherXDA said:
Here is the v410 stock recovery: //drive.google.com/open?id=0B9ztRll4cXJyTWktNXJLU2VDLU0
It worked for me but your mileage may vary. I'm not responsible for any issues.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Hello,
I have been flashing v410 lately and I have been unable to find a STOCK v410 kdz anywhere.
A stock recovery file would be great!. However, the one one at the above url looks pretty small (at 13MB) or am I missing something?
triathleteninja said:
Hello,
I have been flashing v410 lately and I have been unable to find a STOCK v410 kdz anywhere.
A stock recovery file would be great!. However, the one one at the above url looks pretty small (at 13MB) or am I missing something?
Click to expand...
Click to collapse
That file is just the recovery partition, not a whole system image.
To the best of my knowledge there has been no kdz released for the V410. Thank your carrier for that, because LG provides it for the V400.
please help my when i command adb shell have error device not found i have Qualcomm HS-USB QDLoader 9008 mode on lg gpad v410 ((
Alright this post is almost a year old...But i still went back and updated the Minimul ADB link, the second link on my post is simply a thanks to the original person, yes it was deleted theres nothing I can do but you guys do not need it it was only there for you guys to say thanks to him. This thread is only the solution to being stuck in TWRP, some people here asked me for the stock rom,At the time i wrote this thread no one had a kdz for the v410 however now there in fact is one, its android 4.4.2 http://www.mediafire.com/file/2433xqabj1k8b8d/V41007h_0.kdz and I found it here https://forum.xda-developers.com/g-pad-10/general/unbrick-v410-t3105091. Probably easier then my thread to simply flash this with the flash tools but If you decide to follow my old outdated method, and follow the steps %100 it should theoretly get you out of the TWRP bootloop, it worked for me and I was simply sharing, However if it doest work for you dont bite my head off, there are many reasons why you might be in a boot-loop and many factors that come into play so My solution might not be the best for you. Anyway I dont know why I'm reviving an almost year old thread but I just never read the responses as I havent been on XDA for a while and figured I would post in case anyone still wanted it. Again there is a much easier way now because there is a KDZ so this is outdated.
I had attempted to update by bootloader via TWRP to B32 (and modem) and installed a new rom. After I installed the rom per instructions, I reboot and it got caught in a loop where it would restart in Recovery Mode.
I had lost everything on the phone's storage.
I then tried to Flash back to stock, but none of my computers will recognize the phone in MiFlash. It displays the com port, but the serial is f1*****.
When I hit flash, i get an error regarding "cannot found file flash_all_except_storage.bat"
I have reinstalled all the drivers and it still doesn't work. In ADB, when i do "adb devices" the list is blank.
I've tried in bootloader mode as well as download mode (black screen after vol+, vol -, and power)...Same results
I have little experience with Axon 7, so my apologies for the lack of terminology. Any help would be greatly appreciated.
Thanks,
What model phone? Which rom?
I would start by flashing stock rom in recovery.
lafester said:
What model phone? Which rom?
I would start by flashing stock rom in recovery.
Click to expand...
Click to collapse
It is A2017U model and it was the Project New World rom.
Could you provide a link to a rom to try flashing in recovery?
Thank you for the reply and assistance!!!
deviecb said:
It is A2017U model and it was the Project New World rom.
Could you provide a link to a rom to try flashing in recovery?
Thank you for the reply and assistance!!!
Click to expand...
Click to collapse
I believe you have TWRP? If so, you should have adb while on the main screen.
Try one thing before doing the next: Format data. Maybe the ROM will boot after that.
Do you have an SD card, or maybe an USB OTG? If you have any of those you can get Lineage 14.1, the B15 universal bootloader, and the A2017U modem, plus Magisk 15.2, and flash them all. Then try again to flash PNW.
One more thing: You tried to keep data when going from N to O? Don't... Start with a clean slate when changing Android versions!
deviecb said:
It is A2017U model and it was the Project New World rom.
Could you provide a link to a rom to try flashing in recovery?
Thank you for the reply and assistance!!!
Click to expand...
Click to collapse
If you have TWRP installed and no nandroid backup the easiest way to get back to B32 is with the TWRP B32 flash files. Just search Drakenfx on androidfilehost.com Guaranteed to work.
Not sure if it's proper etiquette to post external links.
2CanSan said:
If you have TWRP installed and no nandroid backup the easiest way to get back to B32 is with the TWRP B32 flash files. Just search Drakenfx on androidfilehost.com Guaranteed to work.
Not sure if it's proper etiquette to post external links.
Click to expand...
Click to collapse
yeah, just post the links
You're not a junior member, so you can post whatever you want
2CanSan said:
If you have TWRP installed and no nandroid backup the easiest way to get back to B32 is with the TWRP B32 flash files. Just search Drakenfx on androidfilehost.com Guaranteed to work.
Not sure if it's proper etiquette to post external links.
Click to expand...
Click to collapse
https://androidfilehost.com/?w=files&flid=211544
Dear all,
first of all I would like to be sorry if I'm saying something worng. I'm not so expert about Android world.
I've got a OnePlus 6T that I've rooted with the help of a friend some months ago.
Not it's a lot that I keep see the notification abount the OS update and I keep skipping it but it's bothering me so... I searched for a guide and I found this (https://oneplus.gadgethacks.com/how...thout-losing-root-no-computer-needed-0192638/) (I hope I can post it also if it's from another website).
It seems so simple, I've downloaded the OTA update, the TWRP and the Magisk. My issue is that whene I reboot to the recovery I'm not booting into TWRP but I suppose into the OnePlus recovery instead.
I searched angain and found this other guide (https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953) that is more complete but I can't understand if it's the proper guide I need to follow to update my device keeping it rooted and most of all without loosing any data.
Thanks,
Riki
The first guide you linked to is wrong. Do not follow that. That is why you don't have TWRP anymore. The second guide you linked to on XDA is correct. Follow the TWRP guide. Once you have TWRP reinstalled.
You must download the zip from the second link you posted here at XDA.
Flash the Zip in TWRP. This flash the update to the opposite slot. It also wipes out TWRP and replaces it with the stock recovery.
Now you must reinstall TWRP. Flash the TWRP installer. This will flash TWRP to both slots.
Now reboot to recovery. This will reboot to the new slot where you update was just flashed.
This is when you install Magisk to the updated slot. You MUST do this.
Now reboot to system after you installed Magisk.
Now you have updated without losing any data.
The guide in the second link says to use the Magisk uninstaller. I've personally never done this. This is probably for people who use all sorts of weird add-ons and such. I don't know. Never uninstalled Magisk, never had a problem. That's all I can say. You can try it, or you can follow the official instructions.
OhioYJ said:
The first guide you linked to is wrong. Do not follow that. That is why you don't have TWRP anymore. The second guide you linked to on XDA is correct. Follow the TWRP guide. Once you have TWRP reinstalled.
You must download the zip from the second link you posted here at XDA.
Flash the Zip in TWRP. This flash the update to the opposite slot. It also wipes out TWRP and replaces it with the stock recovery.
Now you must reinstall TWRP. Flash the TWRP installer. This will flash TWRP to both slots.
Now reboot to recovery. This will reboot to the new slot where you update was just flashed.
This is when you install Magisk to the updated slot. You MUST do this.
Now reboot to system after you installed Magisk.
Now you have updated without losing any data.
The guide in the second link says to use the Magisk uninstaller. I've personally never done this. This is probably for people who use all sorts of weird add-ons and such. I don't know. Never uninstalled Magisk, never had a problem. That's all I can say. You can try it, or you can follow the official instructions.
Click to expand...
Click to collapse
Thanks OhioYJ,
so, before I can follow the TWRP guide, I must reinstall it. Could you please give me a link to a guide on how to do it?
Thanks again,
Riki
RikiBez said:
Thanks OhioYJ,
so, before I can follow the TWRP guide, I must reinstall it. Could you please give me a link to a guide on how to do it?
Click to expand...
Click to collapse
[Guide] OnePlus 6T [Fajita]: Unlock | Flash TWRP | Root | Nandroid & EFS Backup !!
Thanks to Funk Wizard again. Don't forget the section about backing up your modem, this is always important in case something really goes wrong. You'll probably never need it, but if you ever do you'll be really glad you have it.
OhioYJ said:
[Guide] OnePlus 6T [Fajita]: Unlock | Flash TWRP | Root | Nandroid & EFS Backup !!
Thanks to Funk Wizard again. Don't forget the section about backing up your modem, this is always important in case something really goes wrong. You'll probably never need it, but if you ever do you'll be really glad you have it.
Click to expand...
Click to collapse
I followed the guide but I get stucked into a loot without been able to boot into TWRP. I'm only able to enter the recovery mode and the fastboot mode but when I launch the command from Windows it finish with no error but the phone still stuck on the fastboot logo or the oneplus logo. After many tryes now I've got only this and also errors on PC:
Old_video_link_removed
EDIT: At the moment I'm not event able to enter the recovery mode, I keep restarting it and it will only boot to the fastmode.
RikiBez said:
I followed the guide but I get stucked into a loot without been able to boot into TWRP. I'm only able to enter the recovery mode and the fastboot mode but when I launch the command from Windows it finish with no error but the phone still stuck on the fastboot logo or the oneplus logo. After many tryes now I've got only this and also errors on PC:
https://youtu.be/7Re-p7Z1yhc
EDIT: At the moment I'm not event able to enter the recovery mode, I keep restarting it and it will only boot to the fastmode.
Click to expand...
Click to collapse
It's booting into recovery, but the OnePlus recovery. That is what the menu that is asking you to select a language is. When you enter the command fastboot boot trwp.img you don't get any sort of error? Or the phone doesn't respond?
OhioYJ said:
It's booting into recovery, but the OnePlus recovery. That is what the menu that is asking you to select a language is. When you enter the command fastboot boot trwp.img you don't get any sort of error? Or the phone doesn't respond?
Click to expand...
Click to collapse
At the beginning I had no error nor on PC not on phone. Now that I’m stuck into the fastboot I keep getting the error on windows that say he donno the fastboot command but the phone stand still.
RikiBez said:
At the beginning I had no error nor on PC not on phone. Now that I’m stuck into the fastboot I keep getting the error on windows that say he donno the fastboot command but the phone stand still.
Click to expand...
Click to collapse
Is fastboot installed? Are you typing the commands correctly?
Sent from my OnePlus 6T using XDA-Developers Legacy app
RikiBez said:
At the beginning I had no error nor on PC not on phone. Now that I’m stuck into the fastboot I keep getting the error on windows that say he donno the fastboot command but the phone stand still.
Click to expand...
Click to collapse
Sounds like you're not running the command from the folder where fastboot.exe is located.
Makes me wonder why you did it this way in the first place. And why people suggested it. Easiest way to install updates on a rooted 6T is to install the update through the normal updater without rebooting, going to Magisk Manager and selecting install to inactive slot and rebooting only after that. That's really all there is to it.
CazeW said:
Sounds like you're not running the command from the folder where fastboot.exe is located.
Makes me wonder why you did it this way in the first place. And why people suggested it. Easiest way to install updates on a rooted 6T is to install the update through the normal updater without rebooting, going to Magisk Manager and selecting install to inactive slot and rebooting only after that. That's really all there is to it.
Click to expand...
Click to collapse
If I want to clean flash my 9.0.13 rooted TWRP. What do I need to uninstall or wipe? Im on 9.0.13 currently
Sent from my OnePlus 6T using XDA-Developers Legacy app
i7vSa7vi7y said:
Is fastboot installed? Are you typing the commands correctly?
Sent from my OnePlus 6T using XDA-Developers Legacy app
Click to expand...
Click to collapse
Fastboot was working until I reinstalled adb and OnePlus drivers.
CazeW said:
Sounds like you're not running the command from the folder where fastboot.exe is located.
Makes me wonder why you did it this way in the first place. And why people suggested it. Easiest way to install updates on a rooted 6T is to install the update through the normal updater without rebooting, going to Magisk Manager and selecting install to inactive slot and rebooting only after that. That's really all there is to it.
Click to expand...
Click to collapse
I didn’t know any other way. That’s why I asked how to do it. Anyway I’m running the command from the right folder. Maybe something broke on my laptop.
Yesterday evening I tried from a new laptop windows 10, installed adb and OnePlus driver for the first time and I was able to run the commands without the error not finding the command but:
Fastboot boot twrp.image returned me an error
If I run fastboot flash boot twrp.image it does not give me error but the phone does not response. It only boot to the boot loader.
RikiBez said:
I didn’t know any other way. That’s why I asked how to do it. Anyway I’m running the command from the right folder. Maybe something broke on my laptop.
Yesterday evening I tried from a new laptop windows 10, installed adb and OnePlus driver for the first time and I was able to run the commands without the error not finding the command but:
Fastboot boot twrp.image returned me an error
If I run fastboot flash boot twrp.image it does not give me error but the phone does not response. It only boot to the boot loader.
Click to expand...
Click to collapse
Try uninstalling adb. Delete the whole folder and install it again. Try updating your netframework on your PC and the latest C++
Sent from my OnePlus 6T using XDA-Developers Legacy app
I'm creating a new tread about the issue and the state where I am because now I can't update or keep data, I just need to recover the phone to a normal state.
RikiBez said:
I'm creating a new tread about the issue and the state where I am because now I can't update or keep data, I just need to recover the phone to a normal state.
Click to expand...
Click to collapse
Use the msm tool for that
Sent from my OnePlus 6T using XDA-Developers Legacy app
Flashing the fastboot rom would probably have gotten you back in and maybe with your data in tact. Now fair warning I'm a Linux user anyways, but really fastboot and adb are so much easier in Linux. For people that have issues, it sometimes is easier just to make a bootable USB / CD of Linux Mint or Ubuntu and then from Synaptic or the Package manager install adb and fastboot. No drivers or anything else to install, everything will just work.
Last time I got stuck in fastboot I just used the fastboot ROM to get back to bootable.
OhioYJ said:
Flashing the fastboot rom would probably have gotten you back in and maybe with your data in tact. Now fair warning I'm a Linux user anyways, but really fastboot and adb are so much easier in Linux. For people that have issues, it sometimes is easier just to make a bootable USB / CD of Linux Mint or Ubuntu and then from Synaptic or the Package manager install adb and fastboot. No drivers or anything else to install, everything will just work.
Last time I got stuck in fastboot I just used the fastboot ROM to get back to bootable.
Click to expand...
Click to collapse
Those fastboot roms have sure saved me from raging before
I would also recommend using migrate, it's in the play store and it backs up all your data and then puts it in a flashable zip
i7vSa7vi7y said:
If I want to clean flash my 9.0.13 rooted TWRP. What do I need to uninstall or wipe? Im on 9.0.13 currently
Sent from my OnePlus 6T using XDA-Developers Legacy app
Click to expand...
Click to collapse
Do a factory reset from TWRP and flash the full ROM.
One best method...and the method that works 100% tested for upgrading a rooted OOS to new OOS version without any loss of data, without any issues.
I'll mention the guide that I have used to upgrade from 9.0.12 rooted to 9.0.13 rooted. Without any loss of data
Download latest OOS full ROM
Boot to TWRP
Flash OOS 9.0.13
Flash TWRP installer zip
Reboot system
Phone will boot.
Now go back to recovery mode
Flash Magisk if u want root again
Done
No confusion. No data loss. Not being stuck. Sweet and Simple.
sanjeev7 said:
One best method...and the method that works 100% tested for upgrading a rooted OOS to new OOS version without any loss of data, without any issues.
I'll mention the guide that I have used to upgrade from 9.0.12 rooted to 9.0.13 rooted. Without any loss of data
Download latest OOS full ROM
Boot to TWRP
Flash OOS 9.0.13
Flash TWRP installer zip
Reboot system
Phone will boot.
Now go back to recovery mode
Flash Magisk if u want root again
Done
No confusion. No data loss. Not being stuck. Sweet and Simple.
Click to expand...
Click to collapse
So I don't have to wipe my system data or anything. I heard some people had the problem of getting stuck or that there was a red warning screen that popped up when booting, and I'm not talking about the bootloader message. I'm currently on 9.0.11. Also should I download the latest version of TWRP or should I use the one I'm using currently. Don't wanna mess anything up. Another guide I read said I should flash the oos rom, then TWRP, than magisk