Related
I tried rooting my phone, but when I flashed CWM my Nexus S stopped booting... it freezes on the Google screen in the intro. I can boot into Fastboot, and cwm, but I cant connect the Internal memory to the computer without it booting like it is supposed to. Does anybody know of anything I can do to fix my phone and bring it back to stock??
There are guides for returning to stock stickied in the Nexus S 4G Android Development forum.
Before you do that though, try flashing a different recovery, like the one linked to here or here.
Btw, which guide did you use? You're not the first person to have this problem, and it's really bugging me (though probably not as much as it's bugging you :-o).
Maximilian Mary: I tried to post the link, but since I'm a new member I have to wait 8 posts before I can post a URL.... :/
I will try a different recovery, but how would I flash a rom if I can connect my phone via usb mount?
deadzunehd said:
Maximilian Mary: I tried to post the link, but since I'm a new member I have to wait 8 posts before I can post a URL.... :/
Click to expand...
Click to collapse
What's the title of the thread?
.
I will try a different recovery, but how would I flash a rom if I can connect my phone via usb mount?
Click to expand...
Click to collapse
I'm a little out of my depth here, but I think it's
fastboot flash system system.img.
You don't need to put the rom image on the sdcard. Just put it in the same folder as fastboot.
It was titled "How to Root Nexus S!"
And I will try to flash recovery and try that rom command, thank you )
deadzunehd said:
It was titled "How to Root Nexus S!"
And I will try to flash recovery and try that rom command, thank you )
Click to expand...
Click to collapse
Hmmm. I can't find that exact title. Could you pm me the link?
deadzunehd said:
thank you )
Click to expand...
Click to collapse
There's a button for that.
I got the link. Thanks. I looks like you flashed a boot image that is incompatible with your phone. That guide was for the T-Mobile Nexus S. (Why they're screwing with the boot.img to begin with, I really don't understand.)
Download the attached file, and unzip it to the same folder as fastboot. The md5 sum is d4a9508f9321eb25df3383f00f571e8b. Then
Code:
fastboot flash boot boot.img
You'll probably also want to use one of the recoveries listed above to
Code:
fastboot flash recovery recovery.img
, but leave system alone for now. Flash that only as a last resort.
deadzunehd said:
I tried rooting my phone, but when I flashed CWM my Nexus S stopped booting... it freezes on the Google screen in the intro. I can boot into Fastboot, and cwm, but I cant connect the Internal memory to the computer without it booting like it is supposed to. Does anybody know of anything I can do to fix my phone and bring it back to stock??
Click to expand...
Click to collapse
I had this problem after flashing the wrong ROM onto my phone. I got the phone back to stock using ODIN.
My thread can be found here
http://forum.xda-developers.com/showthread.php?p=14172335#post14172335
hope it helps
Acnescar said:
I had this problem after flashing the wrong ROM onto my phone. I got the phone back to stock using ODIN.
My thread can be found here
http://forum.xda-developers.com/showthread.php?p=14172335#post14172335
hope it helps
Click to expand...
Click to collapse
OMG!! im having the same issue. could you please post the link for ODIN so i can return to stock and take it from there please? I rely on my phone so much and i need it asap thank you.
same problem with me.
but in my case, the phone not only freeze after the google logo before boot. I tried several times to pull the battery and start the phone again, it took several times until the phone can boot normally again.
After that, my nexus s can work as usual. but it only takes 3-4 hour until it freeze/hangs or reboot automatically and show image of green robot lay down with red alert triangle...
sometimes I noticed all application force closed like gmail, gtalk, etc. (its a basic apps instead of 3rd party app)
History :
- root GB 2.37 using superoneclick
- upgrade OTA to ICS 4.04
- problem happens
- root using guide : nexusshacks.com
- unroot using guide : nexusshacks.com
- back to factory setting on GB 2.34
- upgrade OTA to ICS 4.04
- Still got that problem.....
I'm using Nexus S 4G Sprint, pls help me guys...
nexus s won't boot
I had the same problem and read elsewhere that heating the phone with a hairdryer solves the problem.
I must say, indeed it did.
I removed the battery and the SIM card, then heated up the phone (so it really feels warm) put back the battery and sim and simsalebim the phone started again. and is still working since (now already a few day's)
It seems that a component in the phone is heat sensitive, the question in my mind is when will this show again and do I need to consider buying a new phone.
But sofar it works
PS I also tried hard reset factory reset the lot, but in the end only heating up helped.
Good luck, David
I fixed this problem! but I had to wipe all user data by rooting it using nexusrootICS. It finally boots up and the phone works now... that's all I need.
Hi all,
My stock ROM Oneplus 6 (3 weeks out of warranty :crying: ) became unresponsive today and crashed.
It failed to boot back in to the OS so I cleared cache - no better, then system settings - no better, then data - no better - but this time I got the Qualcomm crash dump mode.
I've used MSMDownloadtool to flash first - enchilada_22_O.09_180517, then after that did not boot i tried - enchilada_22_O.30_190403.
MSMDownloadtool 'worked' as far as I can tell, as all messages were positives (no errors) and the phone restarted
But unfortunately both have the same result, the phone is stuck on the android spinning dots - no Qualcomm crash dump anymore - small blessings.
I can get into both recovery and fastboot, but I'm at a loss as to what to try next.
I thought the MSMDownload tool was the nuclear option and would work - but no.
Would anyone have any suggestions ?
Thank you!
Dan
Try to flash a stock rom with fastboot, you can find a stock one in the forum and will find a batch file that will flash all the partitions for you, good luck
Chinaroad said:
Try to flash a stock rom with fastboot, you can find a stock one in the forum and will find a batch file that will flash all the partitions for you, good luck
Click to expand...
Click to collapse
Thank you Chinaroad,
I'm sorry for the stupid question, but I thought the MSMDownloader tool was a stock ROM installed through fastboot - this is all new to me - do I need to follow a different method ?
Thanks again
Dan
The msm is a tool that flashes the stock rom at another level than fastboot, and yes as you said it's the ultimate solution and it's strange that it doesnt work for you, so since you can access to fastboot, try to flash it that way without using msm
Chinaroad said:
The msm is a tool that flashes the stock rom at another level than fastboot, and yes as you said it's the ultimate solution and it's strange that it doesnt work for you, so since you can access to fastboot, try to flash it that way without using msm
Click to expand...
Click to collapse
I'm trying the flash-all.bat method, but the guide I'm using (and the program output) tells me the bootloader must be unlocked - of course it isn't.
I've tried Tool All in one to unlock the bootloader - but I get the error message Failed (remote: 'Flashing unlock is not allowed')
What step am I missing...
Sorry, and thanks again
Dan
it says flashing unlock is not allowed cuz i think it needs to be activated in dev menu of the phone, but since you can't power it up ..... . So lets comeback to MSM, are you sure all the files are there and you get no output error?
Chinaroad said:
it says flashing unlock is not allowed cuz i think it needs to be activated in dev menu of the phone, but since you can't power it up ..... . So lets comeback to MSM, are you sure all the files are there and you get no output error?
Click to expand...
Click to collapse
I've weakened and gone for an RMA - in some vain hope that they'll offer a warranty repair :fingers-crossed:
I've followed the guides for MSM to the letter, and it gave only positive feedbacks - but then just wouldn't complete the boot.
From reading these forums - anyone at the stage / with the symptoms I found myself with seems to have been resolved with an RMA
I guess if I'm an idiot and it was software, then the charge won't be huge, I'll suck it up - if I'm not and the issue was hardware then I'll make a descision when I know.
Thanks for your time, and I'll be sure to feedback !
Dan
Goodluck hope you fix it for free or at least not too much
Chinaroad said:
Goodluck hope you fix it for free or at least not too much
Click to expand...
Click to collapse
One plus honoured my (technically expired) warranty and replaced the main board.
Great news, if a little late, I did already buy a OnePlus 7 Pro...
Dan1Dan2 said:
One plus honoured my (technically expired) warranty and replaced the main board.
Great news, if a little late, I did already buy a OnePlus 7 Pro...
Click to expand...
Click to collapse
Nice from them and good for you xD
Dan1Dan2 said:
Hi all,
My stock ROM Oneplus 6 (3 weeks out of warranty :crying: ) became unresponsive today and crashed.
It failed to boot back in to the OS so I cleared cache - no better, then system settings - no better, then data - no better - but this time I got the Qualcomm crash dump mode.
I've used MSMDownloadtool to flash first - enchilada_22_O.09_180517, then after that did not boot i tried - enchilada_22_O.30_190403.
MSMDownloadtool 'worked' as far as I can tell, as all messages were positives (no errors) and the phone restarted
But unfortunately both have the same result, the phone is stuck on the android spinning dots - no Qualcomm crash dump anymore - small blessings.
I can get into both recovery and fastboot, but I'm at a loss as to what to try next.
I thought the MSMDownload tool was the nuclear option and would work - but no.
Would anyone have any suggestions ?
Thank you!
Dan
Click to expand...
Click to collapse
your problem is now fix or still faceing this problem????beoouse i have also same issue becouse i erase persist partiton..when my bootloader unlock after flashing official full firmware via msm download tools my phone stuck on bootloop..won't boot
btuhin17 said:
your problem is now fix or still faceing this problem????beoouse i have also same issue becouse i erase persist partiton..when my bootloader unlock after flashing official full firmware via msm download tools my phone stuck on bootloop..won't boot
Click to expand...
Click to collapse
The motherboard was replaced, this was the only fix for my problem.
Dan1Dan2 said:
The motherboard was replaced, this was the only fix for my problem.
Click to expand...
Click to collapse
only motherboard replace solved this problem??
Today I was using my OnePlus 7 (OOS Beta 10, TWRP 3.3.1-70, Magisk 20.3) and I accidentally rebooted it to bootloader through the advanced reboot feature. Somehow, I know not how, this soft bricked the device. I could get to the unlocked bootloader warning screen but no further. I could also boot to TWRP and Fastboot still. I tried several different things to fix this, including disabling all Magisk Modules through TWRP, but to no avail. I also tried switching to slot A (I was previously on slot B), but I only booted to the OxygenOS logo and accompanying animation, which lasted 15 minutes or more. Impatient, I began trying several other methods (instead of making a backup :facepalm. Long story short, I ended up wiping all the partitions (including Vendor and System) and I am stuck. I followed the guide here, which allowed me to boot to the OxygenOS logo and animation again, but no full OS boot. I have also reinstalled TWRP (3.3.1-79 now) which works as well, but try as I might I cannot get anything to boot besides that. I have tried installing the images from OnePlus' website, LineageOS 17.1, AOSiP, and custom kernels, but nothing works besides their own respective boot animations which loop forever.
And so, I have come to you, the best Android modding community I know of, to help me fix my problem. I can offer you no incentive besides my eternal gratitude.
Thanks in advance,
Michael
Edit: forgot to mention I use exclusively Linux so I cannot use the MSM tools. Sorry!
DrRayThe2nd said:
Today I was using my OnePlus 7 (OOS Beta 10, TWRP 3.3.1-70, Magisk 20.3) and I accidentally rebooted it to bootloader through the advanced reboot feature. Somehow, I know not how, this soft bricked the device. I could get to the unlocked bootloader warning screen but no further. I could also boot to TWRP and Fastboot still. I tried several different things to fix this, including disabling all Magisk Modules through TWRP, but to no avail. I also tried switching to slot A (I was previously on slot B), but I only booted to the OxygenOS logo and accompanying animation, which lasted 15 minutes or more. Impatient, I began trying several other methods (instead of making a backup :facepalm. Long story short, I ended up wiping all the partitions (including Vendor and System) and I am stuck. I followed the guide here, which allowed me to boot to the OxygenOS logo and animation again, but no full OS boot. I have also reinstalled TWRP (3.3.1-79 now) which works as well, but try as I might I cannot get anything to boot besides that. I have tried installing the images from OnePlus' website, LineageOS 17.1, AOSiP, and custom kernels, but nothing works besides their own respective boot animations which loop forever.
And so, I have come to you, the best Android modding community I know of, to help me fix my problem. I can offer you no incentive besides my eternal gratitude.
Thanks in advance,
Michael
Edit: forgot to mention I use exclusively Linux so I cannot use the MSM tools. Sorry!
Click to expand...
Click to collapse
Download a Fastboot ROM and extract the images.zip. CD into that directory. Get your device into fastboot and manually flash them in Linux. The instructions for doing this are in that post. I needed to do this when I first got my OP7 as I also do not use Windoze. Worked without issue.
Edit:
I just saw that you said you tried this I guess. Give the first boot time. It takes awhile.
spookcity138 said:
Download a Fastboot ROM and extract the images.zip. CD into that directory. Get your device into fastboot and manually flash them in Linux. The instructions for doing this are in that post. I needed to do this when I first got my OP7 as I also do not use Windoze. Worked without issue.
Edit:
I just saw that you said you tried this I guess. Give the first boot time. It takes awhile.
Click to expand...
Click to collapse
It has been 20 minutes and still no response. Should I wait longer?
Edit: 30 Minutes
DrRayThe2nd said:
It has been 20 minutes and still no response. Should I wait longer?
Edit: 30 Minutes
Click to expand...
Click to collapse
Nope,it takes awhile, but not that long if I remember correctly. Sorry man, don't know what else to say. I've done this a couple of times. Once outta necessity and once just to test something. Worked for me both times, so IDK.
Sent from my OnePlus 7 using Tapatalk
spookcity138 said:
Nope,it takes awhile, but not that long if I remember correctly. Sorry man, don't know what else to say. I've done this a couple of times. Once outta necessity and once just to test something. Worked for me both times, so IDK.
Sent from my OnePlus 7 using Tapatalk
Click to expand...
Click to collapse
I'll try some more things. Thanks for your help.
DrRayThe2nd said:
I'll try some more things. Thanks for your help.
Click to expand...
Click to collapse
Np, no idea why this doesn't work for you. Worse case, install Windows via virtualbox or something and use MSM tool like that. Good luck!
Sent from my OnePlus 7 using Tapatalk
Unbrick tool for OnePlus 7 (MSMTOOL Hydrogen Version)
As long as there's no hardware damage, your device can be unbricked through this tool. URL is banned in this forum so I can't give you the link, you can find it in OnePlus 7 Guides, News, & Discussion section.
Patrickzhong said:
Unbrick tool for OnePlus 7 (MSMTOOL Hydrogen Version)
As long as there's no hardware damage, your device can be unbricked through this tool. URL is banned in this forum so I can't give you the link, you can find it in OnePlus 7 Guides, News, & Discussion section.
Click to expand...
Click to collapse
Yeah, but not everyone uses or likes Windows. Myself included. So this tool is not useful for those people.
Sent from my OnePlus 7 using Tapatalk
spookcity138 said:
Np, no idea why this doesn't work for you. Worse case, install Windows via virtualbox or something and use MSM tool like that. Good luck!
Sent from my OnePlus 7 using Tapatalk
Click to expand...
Click to collapse
Patrickzhong said:
Unbrick tool for OnePlus 7 (MSMTOOL Hydrogen Version)
As long as there's no hardware damage, your device can be unbricked through this tool. URL is banned in this forum so I can't give you the link, you can find it in OnePlus 7 Guides, News, & Discussion section.
Click to expand...
Click to collapse
spookcity138 said:
Yeah, but not everyone uses or likes Windows. Myself included. So this tool is not useful for those people.
Sent from my OnePlus 7 using Tapatalk
Click to expand...
Click to collapse
Well guys, I bit the bullet, booted up an old Windows computer, and ran the MSM tool. It successfully installed HydrogenOS, so from there I could install LineageOS. My phone is working again. Thanks for your help.
DrRayThe2nd said:
Well guys, I bit the bullet, booted up an old Windows computer, and ran the MSM tool. It successfully installed HydrogenOS, so from there I could install LineageOS. My phone is working again. Thanks for your help.
Click to expand...
Click to collapse
Thanks for the update. I was curious how this turned out. Guess windows has some use after all [emoji3]
Jk windows users.
Still wonder why manually flashing the partitions via fastboot didn't work. Oh well,unimportant now. Glad ya got it working!
Sent from my OnePlus 7 using Tapatalk
DrRayThe2nd said:
Well guys, I bit the bullet, booted up an old Windows computer, and ran the MSM tool. It successfully installed HydrogenOS, so from there I could install LineageOS. My phone is working again. Thanks for your help.
Click to expand...
Click to collapse
there's also a OOS msmtools if you want, just search for that, it has been posted by @Some_Random_Username
Removed
Reserved for Links and Firmwares
It turns out a permissive Kernel helps with the Storage Problems. I will edit the Guide later with a Link
Nice guide brother, this works also on xperia 1 i think ?
Sorry for my guide, i have no time to update it anymore so thats why its kinda outdated and i found those files on a chinese site in my guide so i shared it only
Xperia
This method has problem if 55.1.A.3.149 is flashed. The "Start" screen freeze with no touchscreen function on reboot after the procedures completed.
Pandemic said:
Nice guide brother, this works also on xperia 1 i think ?
Sorry for my guide, i have no time to update it anymore so thats why its kinda outdated and i found those files on a chinese site in my guide so i shared it only
Click to expand...
Click to collapse
Same Steps, different Files like You can imagine. I made two Folders on Google Drive to keep them seperated. :angel:
I was wondering if we can use the TWRP Installer Zips from like for example the Pixel 2 XL which is almost the same as what we flash actually. Our TWRP is actually from a One Plus 2 or so, while using an old Lazy Flasher with old Magisk Boot File. While the newer TWRP Installers are using a Magisk kind of Installer to do the Ramdisk changes. Only thing i wonder is if the included ramdisk cpio is Device specific or a general thing which shares between different devices!? I'm really about to just try a flash on risk but i would like to here if You know that...
@MartinX3 can hopefully look at this
The ramdisk also contains device specific files
I put the twrp 1/5 on my to-do list
Pandemic said:
@MartinX3 can hopefully look at this
Click to expand...
Click to collapse
MartinX3 said:
The ramdisk also contains device specific files
I put the twrp 1/5 on my to-do list
Click to expand...
Click to collapse
We found together @Pandemic just asked @MartinX3 some Hours ago if he can invite us to the Xperia TWRP Family on his XZ2 Thread, and You mentition him over to this Thread. Funny
It's really no fun actually to recover my Xperia after Bootloops with Fastboot instead of TWRP. Really throw my Hat in the air once we get a working Recovery. If i can help in any way, let Me know Martin!
Wish You a good Start in the coming Week Guys! :fingers-crossed:
Miustone said:
We found together @Pandemic just asked @MartinX3 some Hours ago if he can invite us to the Xperia TWRP Family on his XZ2 Thread, and You mentition him over to this Thread. Funny
It's really no fun actually to recover my Xperia after Bootloops with Fastboot instead of TWRP. Really throw my Hat in the air once we get a working Recovery. If i can help in any way, let Me know Martin!
Wish You a good Start in the coming Week Guys! :fingers-crossed:
Click to expand...
Click to collapse
Yeah haha and i spoke him also in private
I honestly cant wait to see what lineage looks like on the Xperia 5. The stock UI is good but it feels out of place compared to my other Xperia phones
Does this require unlocked bootloader?
BuyXRPnow! said:
Does this require unlocked bootloader?
Click to expand...
Click to collapse
Yes
TWRP freezes when i try step 18, until i hard reboot. I also can't mount the storage to put the zips on my phone. Don't know what else to do. Also my touchscreen has stopped working in android, but still works on twrp.
Joran95 said:
TWRP freezes when i try step 18, until i hard reboot. I also can't mount the storage to put the zips on my phone. Don't know what else to do. Also my touchscreen has stopped working in android, but still works on twrp.
Click to expand...
Click to collapse
Please try : "fastboot flash boot_a ..." instead of just "fastboot flash boot ..." and repeat with "fastboot flash boot_b ...". This will flash the Recovery to both booth Slots. after that do "fastboot -w" which will format Your Device. Reboot into the Recovery and repeat Step 18 if possible. Would be nice to hear from You again!
Edit: You need to pass Step 18 to use Your Storage. After flashing the Zips will Your System start to work normally again. (Touch and everything else)
VIdeo Guides coming this Weekend! Stay tuned!
Miustone said:
Please try : "fastboot flash boot_a ..." instead of just "fastboot flash boot ..." and repeat with "fastboot flash boot_b ...". This will flash the Recovery to both booth Slots. after that do "fastboot -w" which will format Your Device. Reboot into the Recovery and repeat Step 18 if possible. Would be nice to hear from You again!
Edit: You need to pass Step 18 to use Your Storage. After flashing the Zips will Your System start to work normally again. (Touch and everything else)
Click to expand...
Click to collapse
Thank you for the advice! I actually got my phone working with (just) magisk with your other tutorial, that also had the a and b slots. I'll edit it to see if this works too!
Also thank you for supporting a lesser known phone!
edit-
I've tried your new steps, but the phone still freezes when formatting it. Am I doing something stupid?
Joran95 said:
Thank you for the advice! I actually got my phone working with (just) magisk with your other tutorial, that also had the a and b slots. I'll edit it to see if this works too!
Also thank you for supporting a lesser known phone!
edit-
I've tried your new steps, but the phone still freezes when formatting it. Am I doing something stupid?
Click to expand...
Click to collapse
Just a clue, did You Set TWRP to English before doing the Format? That caused Problems for Me...
Miustone said:
Just a clue, did You Set TWRP to English before doing the Format? That caused Problems for Me...
Click to expand...
Click to collapse
Oh.. that might be it. I will try again this weekend.
Joran95 said:
Oh.. that might be it. I will try again this weekend.
Click to expand...
Click to collapse
Good luck, i will investigate some time in this to figure out whats going on... But that might be it :fingers-crossed:
Okay... I've been searching all over the net for this problem and I keep getting posts that skirt the issue. At least, that's what it seems. So I will begin and you can decide... and thanks for whatever info you can throw my way.
Brand new OnePlus 8T. I want to root it. Duh. So, Got the Tiny ADB and Fastboot package and all the rest, but the issue is with unlocking the bootloader. Other problems may appear later, but this is the issue now.
So, connect phone to PC (Windows 8.1) and the only way that ABD recognizes my phone is when the USB prefs are set to 'No Data Transfer". Yes, I have installed the proper drivers from the phone. So, when the 'No Data Transfer' is selected, ADB recognizes the phone and will issue the command, ABD Reboot Bootloader and the phone reboots to the bootloader. Nice! Unfortunately, it appears that once the phone has booted to the bootloader, it has changed the USB Prefs and now ADB and fastboot do not see the phone. Obviously this sucks. And here is the problem. As far as I know, I have ticked off on all the proper settings. USB Debugging, etc. No joy!
I found a post elsewhere that showed how to set the default USB mode and that didn't work either. My experience has been that ADB used to see the phone under the 'File Transfer' and PTP options before, but it doesn't now. I can't explain this.
So, pretty frustrated. This shouldn't be so bloody difficult. It's only a couple of commands and I have done this with other phones in the past so it's not like I have no previous experience. But I have already wasted way too much time here this go around. Anyone have an answer? I'll be your best friend!!
Thanks all..
R
Try nother USB C cable. Some not able to handle data.
rogerebert said:
Try nother USB C cable. Some not able to handle data.
Click to expand...
Click to collapse
Thanks man... ya, I did try that to no avail.. but.. the fact that the original command works.. well. Don't think that is the problem, but thank you for taking the time to consider my problem. Cheers!
Ran Doid said:
Thanks man... ya, I did try that to no avail.. but.. the fact that the original command works.. well. Don't think that is the problem, but thank you for taking the time to consider my problem. Cheers!
Click to expand...
Click to collapse
I had to install drivers for both ADB and bootloader mode. I documented what I did here: https://forum.xda-developers.com/t/...t-fastbootd-driver-guide-for-windows.4282241/
BillGoss said:
I had to install drivers for both ADB and bootloader mode. I documented what I did here: https://forum.xda-developers.com/t/...t-fastbootd-driver-guide-for-windows.4282241/
Click to expand...
Click to collapse
Hey Thanks, Bill. I"ll give this a whirl and see how it goes. I'll report back after. Cheers!
Ok, that appears to have solved the driver problem. I was able to finally unlock the bootloader and flash twrp. Now it is stuck in a boot loop.. fun fun!
I had been following this guide
How to Install Official TWRP Recovery on OnePlus 8 and OnePlus 8T and Root it
OnePlus 8 and OnePlus 8T (codename: instantnoodle/kebab) was launched in the year April and October 2020 with Android 10 and 11 respectively. Recently
www.getdroidtips.com
to root my 8T, but it appears that this fellow was missing some info? I take it ya can't just flash twrp to recovery like usual. The picture is slowly coming together.. much more complex than the last few times I have rooted phones.
So I assume that flashing twrp writes over the stock recovery.. and that leads to this crashdump mode popping up. To fix this, I will need the stock recovery.img and flash that back into place? Feel free to chime in and thanks in advance!
R
Ran Doid said:
Ok, that appears to have solved the driver problem. I was able to finally unlock the bootloader and flash twrp. Now it is stuck in a boot loop.. fun fun!
I had been following this guide
How to Install Official TWRP Recovery on OnePlus 8 and OnePlus 8T and Root it
OnePlus 8 and OnePlus 8T (codename: instantnoodle/kebab) was launched in the year April and October 2020 with Android 10 and 11 respectively. Recently
www.getdroidtips.com
to root my 8T, but it appears that this fellow was missing some info? I take it ya can't just flash twrp to recovery like usual. The picture is slowly coming together.. much more complex than the last few times I have rooted phones.
So I assume that flashing twrp writes over the stock recovery.. and that leads to this crashdump mode popping up. To fix this, I will need the stock recovery.img and flash that back into place? Feel free to chime in and thanks in advance!
R
Click to expand...
Click to collapse
Flashing TWRP doesn't cause CrashDumps. They happen when you try to boot the system and something's not right.
You could try changing slots and then rebooting. That sometimes works (depending on what else you've done). You can do this in either TWRP or bootloader.
PS: if you use the reply button, then I'll be advised that you've posted a reply. Otherwise you'll have to wait until the next time I look to see if there's new posts in a thread.
BillGoss said:
Flashing TWRP doesn't cause CrashDumps. They happen when you try to boot the system and something's not right.
You could try changing slots and then rebooting. That sometimes works (depending on what else you've done). You can do this in either TWRP or bootloader.
PS: if you use the reply button, then I'll be advised that you've posted a reply. Otherwise you'll have to wait until the next time I look to see if there's new posts in a thread.
Click to expand...
Click to collapse
Alrighty! Changing the slots did bring the phone back and it is now booting properly. But if I try to boot into recovery, it fails and goes to crashdump. Any ideas? Bad twrp image??
Ran Doid said:
Alrighty! Changing the slots did bring the phone back and it is now booting properly. But if I try to boot into recovery, it fails and goes to crashdump. Any ideas? Bad twrp image??
Click to expand...
Click to collapse
Sorry, I've no idea about that. Try flashing TWRP again.
BillGoss said:
Sorry, I've no idea about that. Try flashing TWRP again.
Click to expand...
Click to collapse
Okay, well.. I'll have to figure it out then. Thanks much, Bill. Appreciate your help. Happy Holidays!
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Mickade said:
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Click to expand...
Click to collapse
What I like about TWRP is that I can do things without needing a PC. So rooting, back up and restore, install new ROMs, ...
And now, with version 3.6.0, TWRP works well on Android 11
BillGoss said:
What I like about TWRP is that I can do things without needing a PC. So rooting, back up and restore, install new ROMs, ...
And now, with version 3.6.0, TWRP works well on Android 11
Click to expand...
Click to collapse
Yes, that works,
but don't be surprised to have instabilities in the ROM!
I already had some,
by magisk patch it's more cleaner,
But you are a big boy.
Good luck,
Mickade said:
Yes, that works,
but don't be surprised to have instabilities in the ROM!
I already had some,
by magisk patch it's more cleaner,
But you are a big boy.
Good luck,
Click to expand...
Click to collapse
Lol!
I've been using Magisk and TWRP for years, so I'm not only a "big boy" but also an "old dog".
BillGoss said:
Lol!
I've been using Magisk and TWRP for years, so I'm not only a "big boy" but also an "old dog".
Click to expand...
Click to collapse
that's not the problem to use it for years,
myself with android 10, I was using it, I was already using magisk in 2015, on my Sony z5c (with lineage 7.0.2/ base is the ROM Orange Telecom owner... )
but since Android 11, the data decryption is no longer the same.
just the 30 second twrp boot, I don't really like it, so restored a system with something like that ... lol
Magisk is the best Root solution!
I like this!
Since the magisk_patched has become root's solution, to A11.
an old dog!!
You like croquettes and the mash?
Thx,
Mickade said:
that's not the problem to use it for years,
myself with android 10, I was using it, I was already using magisk in 2015, on my Sony z5c (with lineage 7.0.2/ base is the ROM Orange Telecom owner... )
but since Android 11, the data decryption is no longer the same.
just the 30 second twrp boot, I don't really like it, so restored a system with something like that ... lol
Magisk is the best Root solution!
I like this!
Since the magisk_patched has become root's solution, to A11.
an old dog!!
You like croquettes and the mash?
Click to expand...
Click to collapse
If they could fix the interminable start up time for TWRP that would be brilliant. But I believe the problem is with a file system check rather than the actual decryption which is quite fast.
Sorry, croquettes and mash aren't in my menu. But empanadas - absolutely!
Sorry, I had to leave this for a day or so, but I am back. BillGoss, looking at the guide I posted a link to earlier, would you say that guide is acceptable or are there issues with it? Theoretically that is? And does it depend on what build you are using?
Or if you know of a better process and files, please feel free to point me at it.
Many thanks
R
Ran Doid said:
Sorry, I had to leave this for a day or so, but I am back. BillGoss, looking at the guide I posted a link to earlier, would you say that guide is acceptable or are there issues with it? Theoretically that is? And does it depend on what build you are using?
Or if you know of a better process and files, please feel free to point me at it.
Many thanks
R
Click to expand...
Click to collapse
Sorry, I have no interest in checking out non-XDA guides. We have enough (too many?) of them on XDA as it is.
BillGoss said:
Sorry, I have no interest in checking out non-XDA guides. We have enough (too many?) of them on XDA as it is.
Click to expand...
Click to collapse
There-in why I asked if you might point me at something reliable. But I guess not...
Thanks anyway..
Mickade said:
Hi guys, to root the 8T it's by magisk_patched.img via magisk manager, not twrp (it's old school),
Root FR (sorry a'm frenche, and better explain to me.)
since Android 11 twrp is less good ...
Click to expand...
Click to collapse
Actually a trick you can use is in twrp if you have the magisk APK change the ext to zip and install in twrp it patches the boot img for you in right slot so you don't have to pull img from phone