Hi,
I am struggling with my new Nord (AC2003), basically I have OEM unlocked fine, I have managed to boot TWRP etc... without issues and I can flash the phone this also works. I have tried the Lineage OS install flashing the IMG files, that left the biggest mess! TWRP couldn't even read my system partition anymore so I had to restore via EDL, I then tried PixysOS-v4.0.3 followed the instructions to the letter twice through, both times same result the phone boots straight to fastboot screen! If I hit start or tell it to boot normally it just does it again,
I have been on Samsung for a few years and to be honest haven't flashed an Android phone for about 4 years now but prior to that I was flashing custom ROMS nearly every day, so am no stranger to these processes albeit just a little rusty.
Anybody got any ideas what I could be doing wrong? Getting bored of going through system setup over and over again! All I want is a custom ROM with no Gapps in it
Thanks
Related
I've got quite a peculiar problem with my Nexus 5.
Last night, I left my phone on charge. It was working normally and the software was functional etc. However, once I woke up, the phone was constantly restarting itself, and wouldn't load past the boot animation. I tried to load up fastboot to enter the TWRP recovery, however, the phone froze on the load screen. I should also add that my custom boot animation was replaced by the CyanogenMod mascot.
This problem has never occurred before, and I really haven't got a clue how to fix it. I tried to use WugFresh's NRT to flash a factory image of Android 6, however, the command terminal indicated that each process had failed. This did not restore the phone to its original condition.
I should also point out that I have been running a CM 12.1 nightly, which has been very stable and I have been using this nightly, without major problems (bar the infrequent system UI crashes) for a couple of months. It is obviously rooted and I have a Nandroid backup, which I can't access for aforementioned reasons.
Please could you help me with resurrecting my phone? I would be happy to clarify and elaborate upon any point of information.
Kind regards,
Sami
Have you tried manually wiping cache in fastboot or manually flashing a stock ROM in fastboot mode?
audit13 said:
Have you tried manually wiping cache in fastboot or manually flashing a stock ROM in fastboot mode?
Click to expand...
Click to collapse
I actually have tried to flash stock Android ROMs, from KitKat to Marshmallow, however, this didn't work as there was a 'write failure' and CyanogenMod wasn't removed. I did erase the cache, but to no luck.
Sounds like the memory module on the phone is defective. I had a Nexus 5 that would constantly re-lock the bootloader after I reboot. I had another N5 where the bootloader remains unlocked and a full wipe in recovery would finish in about 3 seconds which is far too short.
I could only solve both problems by replacing the motherboard.
Hello -
I tried installing LineageOS using this guide:
https://forum.xda-developers.com/honor-6x/development/rom-lineageos-14-1-honor-6x-t3713906
Since I am relatively new to this, I was having some confusion using ADB so I used various tutorials I found on other websites that involved using tools like SDK tools and Huawei tools to flash image on to the phone. I unlocked to bootloader, enabled USB debugging etc. Anyway, ultimately I installed LineageOS along with GAPPS and SU using TWRP. I cleared cache every time and the first time I booted the phone after flashing it was stuck at the LineageOs boot screen. Being the impulsive person I am - I tried flashing recovery images on the phone like from various tutorials and at this point I lost track on how many times I`ve written images like recovery images and boot images etc.
All in all - I am now only able to get to fastboot.
Is there a way for me to completely just wipe everything of the phone like all images every change and then recover to stock? This is because I think I`ve unsuccessfully written so many images on here that it`s harder to get the phone to a working state.
Edit:
Found the guide I used like 90% of this from Unlocking bootloader to flashing images
https://www.reddit.com/r/Huawei/comments/50ooh5/unlocking_bootloader_rooting_and_flashing_custom/
TWRP opened fine the first time like I said but upon realizing I had done something wrong I was not able to get back to TWRP and that`s when sh*t hit the fan.
Edit2:
Tried flashing TWRP using fastboot and when I reboot device it goes into either EMIUI, Fastboot, or it gets stuck in "Your device is booting now" depending on the button combo but never TWRP
I was finally able to unlock my bootloader today after the 72-hour waiting period, but am having a problem getting TWRP flashed. I can flash the stock ROM (perseus_images_8.12.13_20181213.0000.00_9.0_cn_21f4637335.tgz) no problem, get through setup, enabling ADB, etc, but as soon as I flash TWRP, the device stops booting. It flashes successfully, but then attempting a reboot always ends up with the device back at the bootloader. Key combos for other modes doesn't make a difference. I'm working on trying the Global ROM too, just to see how that runs, but I have not been able to get TWRP at all or get the device booted to anything other than fastboot after a TWRP flash (tried official & unofficial versions).
I've seen other posts with a similar issue, but that usually seemed to be about users accidentally ended up in Fastboot & not knowing how to get out of it. That's not the case here.
I've been using Android & custom ROM's for years, so I know my way around ADB, Fastboot, & everything rooting & custom ROM's entail, I just seem to be missing something here.
Thanks for any help you can provide.
EDIT:
Not sure why flashing the Global Dev ROM (perseus_global_images_9.5.17_20190517.0000.00_9.0_global_134d3070e5.tgz) made any difference, but after that, ran through the first run wizard, I was able to flash TWRP from the bootloader & actually boot into it so I could flash a custom ROM.
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.