Hey all,
I've had my OnePlus for a while now and have flashed many a ROM, Kernel and Modem. Last night I flashed a rom and somehow my EFS corrupted. I had no IMEI and no baseband, but had WiFi. Then the constant reboots happened. I tried to do a nandroid backup but apparently the nandroid I had did not have the EFS data. I followed the directions HERE and got Oxygen up and running by
fastboot erase modemst1
fastboot erase modemst2
fastboot erase persist
Now, using the unofficial TWRP, I am unable to mount '/persist'. I get the error when trying to backup, format or anything else. I am currently trying to flash a new ROM and I can't seem to get anything to flash without bootlooping. I tried Exodus and SlimLP but both just sit and spin at the boot animation. I let Slim sit and spin for 10 minutes to no avail.
Unless someone can figure out a fix, I think I am going to totally return to stock and try again. I figure a full data wipe and return to stock is my last shot really. Any other ideas though?
UPDATE
OK so that didn't work. I returned to stock using WUG's toolkit and am stuck on the Cyanogen boot animation.
So now I'm going to try THIS TOOL and see if I can get a boot up.
UPDATE
I finally got 38r to boot. I have imei and all. Now it's a matter of getting it unlocked, TWRP and everything else.
Hopefully last UPDATE
After fighting with WUG again, (stupid Windows 8.1!), I am unlocked, rooted, and unofficial TWRP'd once again. After doing a backup, (with EFS), I installed SlimSaber. Booted up just fine. Thank Baby Jesus!!!
SO ... I guess this just ended up being a troubleshooting diary. Hopefully someone else finds it useful if they end up in a similar situation.
newbk said:
UPDATE
OK so that didn't work. I returned to stock using WUG's toolkit and am stuck on the Cyanogen boot animation.
So now I'm going to try THIS TOOL and see if I can get a boot up.
UPDATE
I finally got 38r to boot. I have imei and all. Now it's a matter of getting it unlocked, TWRP and everything else.
Hopefully last UPDATE
After fighting with WUG again, (stupid Windows 8.1!), I am unlocked, rooted, and unofficial TWRP'd once again. After doing a backup, (with EFS), I installed SlimSaber. Booted up just fine. Thank Baby Jesus!!!
SO ... I guess this just ended up being a troubleshooting diary. Hopefully someone else finds it useful if they end up in a similar situation.
Click to expand...
Click to collapse
Hi newbk, I have a very similar issue with xiaomi mi4c device. Stock ROM seems to be running fine, but having endless boot animation with all other ROMs. Also TWRP error "Failed to mount /persist" during ROM zip install.
I don't really understand what persist is and how can this be sorted out. any help is appreciated...
Related
Hi guys, I did something really dumb and I can't seem to learn from my mistakes. Basically I rooted my 1+ with TWRP recovery. Everything was going great until I get these really bad lags. So I decided to do a factory reset but it didn't work! It booted me into TWRP recovery every time I tried to do that. So this is where the stupid mistakes begin. I wiped everything, I mean everything while I was in TWRP, without any backups. Now I get this message in TWRP "No OS installed" and my phone is stuck in the 1+ loading screen. I have tried doing a fastboot oem flash stock recovery but that didn't work. It said that my "device is not unlock, cannot flash or erase." I also have tried flasing 25R in TWRP, it said successful, but when I go to reboot, it still give me the message "No OS installed." I tried doing adb sideload, but i'm not quite familiar with that. It gave me some error in cmd prompt. Is there anything else I can try to fix this issue? Sorry, I am such a noob at this.
******************************* FIXED
In my last attempt before I give up on this phone, I downloaded all the ROMs I came across and flashed them through TWRP. All the one's I tried did not work but it finally work with the last one. I don't know how or what happened there but I'm glad it work again!
**tears of joy
Can you please tell us what rom you used? Thank you
Hello all!
I was running stock 5.1 rooted when I rebooted my phone and it got stuck in a bootloop. I've faced this with many Android phones so I wasnt concerned until I tried everything and still have yet to find a solution.
I have tried to fully flash the stock images, use Wugfresh's toolkit to return to stock, format system and data, and even try to go back to kiKat all without luck. The bootloop is still present.
I used the one-click unbrick tool that took me back to an early Kitkat build and the phone booted but everything kept crashing. Screenshots say they can't be saved which is weird.
I just want to get back to stock lollipop and I'm at a loss. Any help is appreciated!
EDIT: I followed the instructions here here and was able to repair my /persist partition.
babalonius508 said:
Hello all!
I was running stock 5.1 rooted when I rebooted my phone and it got stuck in a bootloop. I've faced this with many Android phones so I wasnt concerned until I tried everything and still have yet to find a solution.
I have tried to fully flash the stock images, use Wugfresh's toolkit to return to stock, format system and data, and even try to go back to kiKat all without luck. The bootloop is still present.
I used the one-click unbrick tool that took me back to an early Kitkat build and the phone booted but everything kept crashing. Screenshots say they can't be saved which is weird.
I just want to get back to stock lollipop and I'm at a loss. Any help is appreciated!
Click to expand...
Click to collapse
My advice if you already have not tried clean flash.
Download right factory image from https://developers.google.com/android/nexus/images and rund flash-all.bat. ( if adb is already installed, if not then install it also ) . If after flash you get again bootloop try to boot in recovery and wipe cache only.
Thanks for the response, Mairo. I tried that out and I'm still getting a bootloop. When I try and flash a zip in recovery or factory reset I get an error in mounting /persist and then the script will finish. I'm not sure if this will help diagnose the problem...
That was fast
I got my new K1 tablet, I Unlocked bootloader (didn't reboot after unlock) and flashed twrp 2.8.7.3. I am not able to boot into OS, It opens up twrp for some recovery script that keeps showing cannot mount partitions and fails and repeats.
Please advice
edit- FIXED IT Flashed stock recovery and it took care of things.
Bet that was a worrying time for you ?, glad to hear its sorted ?
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.
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.