So today I decided I wanted to root my nord, so I downloaded Magisk and a boot.img file but the boot.img was the wrong version. It installed okay at first. It rebooted and everything worked, but Magisk said that it hadn't been rooted fully and to restart, and this is where the problems began. I got stuck in a boot loop, so I went to recovery and factory reset it. When it was booted up, the wifi wasn't working at all. I restarted the phone and nothing happened, so I reset it again and had the same result. Then I thought to have a look at the files I used and finally realized that my boot image was two updates behind. I then got the boot image from the latest release on oneplus website and flashed it, but had the same result. The device is not currently rooted after I installed the stock image but wifi problems are still persisting. I tried relocking the bootloader, but it said my device is corrupt so it couldn't boot. So I unlocked the bootloader again and this is where I am now. Any advice/ help would be hugely appreciated.
Spinningtop22 said:
So today I decided I wanted to root my nord, so I downloaded Magisk and a boot.img file but the boot.img was the wrong version. It installed okay at first. It rebooted and everything worked, but Magisk said that it hadn't been rooted fully and to restart, and this is where the problems began. I got stuck in a boot loop, so I went to recovery and factory reset it. When it was booted up, the wifi wasn't working at all. I restarted the phone and nothing happened, so I reset it again and had the same result. Then I thought to have a look at the files I used and finally realized that my boot image was two updates behind. I then got the boot image from the latest release on oneplus website and flashed it, but had the same result. The device is not currently rooted after I installed the stock image but wifi problems are still persisting. I tried relocking the bootloader, but it said my device is corrupt so it couldn't boot. So I unlocked the bootloader again and this is where I am now. Any advice/ help would be hugely appreciated.
Click to expand...
Click to collapse
Reflash the rom but erase everything then flash.
Spinningtop22 said:
So today I decided I wanted to root my nord, so I downloaded Magisk and a boot.img file but the boot.img was the wrong version. It installed okay at first. It rebooted and everything worked, but Magisk said that it hadn't been rooted fully and to restart, and this is where the problems began. I got stuck in a boot loop, so I went to recovery and factory reset it. When it was booted up, the wifi wasn't working at all. I restarted the phone and nothing happened, so I reset it again and had the same result. Then I thought to have a look at the files I used and finally realized that my boot image was two updates behind. I then got the boot image from the latest release on oneplus website and flashed it, but had the same result. The device is not currently rooted after I installed the stock image but wifi problems are still persisting. I tried relocking the bootloader, but it said my device is corrupt so it couldn't boot. So I unlocked the bootloader again and this is where I am now. Any advice/ help would be hugely appreciated.
Click to expand...
Click to collapse
You needs msmtool to restore the phone to a stock image. Search in xda and follow the steps, its easy
Related
I successfully installed SafeStrap and flashed the Liquidsmooth ROM. It came up and booted once, but I could not login as the password I had set for the phone all of a sudden didn't work.
I restarted it again, tried again, no luck.
I then got it into download mode, ran Odin3, tried to flash the s3vzw_4.4.2.tar file, said it was successful, but is stuck at the Liquidsmooth boot screen.
Booted into recovery, tried to do a factory wipe, it was unsuccessful.
So . . . I am stuck with it at the boot screen.
Am I screwed now? Or is there a way to get it back?
Any and all help is appreciated.
UPDATE -- I was able to format Data and I seemed to have gained some traction. From there I wiped the cache as well and loaded the ROM again and it boots.
I'm actually trying to figure out how I can load an older factory ROM.
jaypeetee said:
I successfully installed SafeStrap and flashed the Liquidsmooth ROM. It came up and booted once, but I could not login as the password I had set for the phone all of a sudden didn't work.
I restarted it again, tried again, no luck.
I then got it into download mode, ran Odin3, tried to flash the s3vzw_4.4.2.tar file, said it was successful, but is stuck at the Liquidsmooth boot screen.
Booted into recovery, tried to do a factory wipe, it was unsuccessful.
So . . . I am stuck with it at the boot screen.
Am I screwed now? Or is there a way to get it back?
Any and all help is appreciated.
Click to expand...
Click to collapse
jaypeetee said:
UPDATE -- I was able to format Data and I seemed to have gained some traction. From there I wiped the cache as well and loaded the ROM again and it boots.
I'm actually trying to figure out how I can load an older factory ROM.
Click to expand...
Click to collapse
You can't flash any custom roms with the 4.4.2 NE1 bootloader, your currently soft bricked because of it
Sent from my Nexus 5
It seems I am missing something
Was on stock rooted MM, TWRTP 3.0.2-2.
Downloaded full OTA, flashed, rebooted, works fine, no root (naturally).
Back to TWRP, flashed SuperSU-v2.79-201612051815.zip, reboot system, stuck on NVidia logo forever.
Back to TWRP, flashed full OTA again, rebooted, works fine again.
Back to TWRP, flashed SR3-SuperSU-v2.79-SR3-20170114223742.zip, same, stuck on logo.
Tried doing adb sideload SuperSU-v2.79-201612051815.zip, same, stuck on logo.
So just flashed the full OTA again and the tablet is working fine, but not rooted.
Any advice?
ali4ek said:
It seems I am missing something
Was on stock rooted MM, TWRTP 3.0.2-2.
Downloaded full OTA, flashed, rebooted, works fine, no root (naturally).
Back to TWRP, flashed SuperSU-v2.79-201612051815.zip, reboot system, stuck on NVidia logo forever.
Back to TWRP, flashed full OTA again, rebooted, works fine again.
Back to TWRP, flashed SR3-SuperSU-v2.79-SR3-20170114223742.zip, same, stuck on logo.
Tried doing adb sideload SuperSU-v2.79-201612051815.zip, same, stuck on logo.
So just flashed the full OTA again and the tablet is working fine, but not rooted.
Any advice?
Click to expand...
Click to collapse
Not sure I got any advice since you've already tried what I would've suggested. I sideloaded SuperSU-v2.79-201612051815.zip by booting into TWRP through fastboot and it worked for me. I read in another thread that some people were stuck on the nvidia logo for a good 15 mins and then it was fine. How long did you wait? I flashed TWRP after rooting because flashing it through fastboot wouldn't stick, but I can't see how that could matter.
I flashed the full OTA with Flashfire on my K1 and it kept root. I already did for the last update and it worked well.
Now, however I'm having issues with charging. Not sure whether it is related to root. It hasn't been enough of a pain yet to remove root.
Sokraates said:
I flashed the full OTA with Flashfire on my K1 and it kept root. I already did for the last update and it worked well.
Now, however I'm having issues with charging. Not sure whether it is related to root. It hasn't been enough of a pain yet to remove root.
Click to expand...
Click to collapse
I've been following the threads throughout the day and it seems to be a common problem after using flashfire. There's a thread on a potential fix here:
https://forum.xda-developers.com/shield-tablet/help/k1-fix-able-to-charge-tablet-ac-adapter-t3554261
so yesterday, I decided to root my tablet. Everything was working nicely after I rooted and downloaded clockwork mod. The whole problem started when I used an app called quick boot, and I booted into recovery mode. As it was rebooting, it asked for permissions(I accepted obviously), and I haven't been able to get past the logo screen ever since. I tried wiping everything, but it still doesn't work. Any solution to this?
Reflash stock firmware with odin should probably work.
I managed to fix it by using the adb sideload thing in twrp.
hey there,
so i had my lgg6 h870 rooted 100% fine, until i yesterday stumbled upon the bug that mobile hotspot turns itself off. so i troubleshooted and i could outsorce that my root is doing that. so i deinstalled magisk and then reset my phone via adb. everything worked perfectly. then i tryed re flashing twrp and it wouldnt at first but then it did after turning on uzb debugging. so then i wanted to boot into twrp, but it only showed me the twrp logo and then booted up into my system as if nothing ever happened. then i deleted EVERYTHING (system, dalvik, cache,.....) and then the fun began, i had no OS on it, so i flashed a lg g6 h870 stock rom onto it and it sayed it worked, so i rebooted to system but i ended up in twrp. so i rebooted again to system and ended up in twrp. so i tryed using adb to get into fastboot, but not even that works. so now im out of ideas what to do, and i hope someone can help me out with this.
thanks
Well, not fully bricked, but it's completely non-working just the same.
I've had the K1 for a few years now and have been fine with the standard, stock OTA updates. Recently though I've been seeing constant notifications that I'm short on ram and after uninstalling apps, deleting old files, it would work ok for a few days and then start complaining about low memory again. So I figured that something must be corrupt and now is a good a time as any to root and see about flashing a new rom.
I've owned many android devices over the years and have rooted and patched most of them. so I'm familiar with the tools.
This time however, I think I must have crossed something up somewhere.
What I did was this:
Grabbed the minimal ADB package and fastboot drivers.
Booted into the bootloader and ran the fastboot oem unlock. No problem.
From the nVidia site, I then grabbed and flashed the latest stock image and recovery, just to ensure I was on a clean slate. No problem.
Flashed the latest TWRP for the device. No problem.
Flashed SuperSU. No problem.
Booted into the stock system to make sure everything was still working and it was. But, this is the start of where I maybe hosed things up(?).
While running stock, I converted the SD card to internal memory, just so I wasn't having to mess with it later, not thinking that I'd have to do it again anyway after flashing a new rom.
Rebooted back to TWRP and proceeded to flash the new rom (AOSP Extended (AEX) 5.8).
I flashed it by way of the sideload method rather than from a zip file sitting on the SD card. This all seemed to work just fine.
Next I went ahead and flashed OpenGapps Mini. This resulted in an error 70 and after reading about it, it was a simple matter of going into the advanced settings in TWRP and extending the system partition. Did that and OpenGapps then flashed with no problem.
Finally I wrapped it up by flashing tegra124-tn8-p1761-1270-a04-e-battery.dtb and rebooted.
... Nothing. Now I know that when flashing a new rom, the first boot can take some time, but I let it sit for about 2 hours with no result. It didn't appear to be boot looping, but instead just stuck on the nVidia boot screen. Forced it to boot back to the bootloader and brought up TWRP. I obviously did something wrong, so I prepared to reflash the stock image.
Did the wipe, flashed the files and rebooted. Again, nothing.
This time however, not only can I not boot to the system, I now also can't get back into recovery.
No matter how many times I reboot, or attempt to reflash anything, it hangs on the boot screen when attempting to get back into recovery.
So I'm stuck. I've tried reflashing TWRP, stock recovery and stock system, with the SD card in and out, a number of times, all with no joy.
I can access the bootloader, so I can at least run fastboot commands, but that's all I can do. Without being in recovery, I can't access an ADB shell if I need to repair anything.
If you're still with me after this rambling mess, do I have any hope at all in recovering this thing?
Hi,
I think the problem is in the modified .dtb try flash the original file.
Or : https://forum.xda-developers.com/showpost.php?p=82359331&postcount=39
greetings
kozaqu said:
Hi,
I think the problem is in the modified .dtb try flash the original file.
Or : https://forum.xda-developers.com/showpost.php?p=82359331&postcount=39
greetings
Click to expand...
Click to collapse
That got me in the right direction and I can at least get back into recovery now. Thanks! :good:
Also in the same boat
mkhopper said:
Well, not fully bricked, but it's completely non-working just the same.
I've had the K1 for a few years now and have been fine with the standard, stock OTA updates. Recently though I've been seeing constant notifications that I'm short on ram and after uninstalling apps, deleting old files, it would work ok for a few days and then start complaining about low memory again. So I figured that something must be corrupt and now is a good a time as any to root and see about flashing a new rom.
I've owned many android devices over the years and have rooted and patched most of them. so I'm familiar with the tools.
This time however, I think I must have crossed something up somewhere.
What I did was this:
Grabbed the minimal ADB package and fastboot drivers.
Booted into the bootloader and ran the fastboot oem unlock. No problem.
From the nVidia site, I then grabbed and flashed the latest stock image and recovery, just to ensure I was on a clean slate. No problem.
Flashed the latest TWRP for the device. No problem.
Flashed SuperSU. No problem.
Booted into the stock system to make sure everything was still working and it was. But, this is the start of where I maybe hosed things up(?).
While running stock, I converted the SD card to internal memory, just so I wasn't having to mess with it later, not thinking that I'd have to do it again anyway after flashing a new rom.
Rebooted back to TWRP and proceeded to flash the new rom (AOSP Extended (AEX) 5.8).
I flashed it by way of the sideload method rather than from a zip file sitting on the SD card. This all seemed to work just fine.
Next I went ahead and flashed OpenGapps Mini. This resulted in an error 70 and after reading about it, it was a simple matter of going into the advanced settings in TWRP and extending the system partition. Did that and OpenGapps then flashed with no problem.
Finally I wrapped it up by flashing tegra124-tn8-p1761-1270-a04-e-battery.dtb and rebooted.
... Nothing. Now I know that when flashing a new rom, the first boot can take some time, but I let it sit for about 2 hours with no result. It didn't appear to be boot looping, but instead just stuck on the nVidia boot screen. Forced it to boot back to the bootloader and brought up TWRP. I obviously did something wrong, so I prepared to reflash the stock image.
Did the wipe, flashed the files and rebooted. Again, nothing.
This time however, not only can I not boot to the system, I now also can't get back into recovery.
No matter how many times I reboot, or attempt to reflash anything, it hangs on the boot screen when attempting to get back into recovery.
So I'm stuck. I've tried reflashing TWRP, stock recovery and stock system, with the SD card in and out, a number of times, all with no joy.
I can access the bootloader, so I can at least run fastboot commands, but that's all I can do. Without being in recovery, I can't access an ADB shell if I need to repair anything.
If you're still with me after this rambling mess, do I have any hope at all in recovering this thing?
Click to expand...
Click to collapse
I'm also sort of in the same boat i had a custom rom installed and decided to go back to stock os and now i'm stuck at either the Nvidia Logo or the Fastboot menu there's nothing else it let's me do i'd take any advice at this point. I can use Fastboot commands and I've tried Flashing Twrp.img and also flashing all the stock os which goes through with no problems i reboot the device and it's just stuck at the Nvidia logo
Ps: how did you manage to get back into recovery
Hello.
I think i had the same Problem.
I Flashed a Custom Rom, MiniGapps and the tegra...Battery file and since then i had boot loop an the NVidia Logo.
The Problem was: i flashed the tegra-Battery.ZIP file!!!
I noticed that i have to unzip it and flash teh tegra-..battery.DTP file.
since then it booted up again.
the OpenGappMini was buggy. it worked with the Nano!
Hope this helps for you as well!
OMG you guys. I did the exact same damn thing. Flashed the ZIP instead of the DTP file. 100 million thanks to you. I'm going to give it a shot now.
It worked! I wonder how many other folks didn't realize it wasn't a zip to flash to dtb and bricked their devices.