Hey all,
I'm not a total noob, but I do this so infrequently that I can't commit it to memory. Would really appreciate some help here.
I followed the official LineageOS Guide for Herolte, over here.
I had done this previously on my Nexus 7 so I was fairly confident.
Everything worked well, I got TWRP installed using Heimdall from Linux, and successfully pushed the latest LineageOS and open_Gapps images to the phone.
Rebooted into TWRP, and followed the recommendation to wipe System, Cache and data partitions. This failed with red text stating that ti was unable to mount data.
I googled some, and found a suggestion to reformat the partitions, first to a different file system and then back to their original file systems again. I tried formatting /data to exFat, and it took forever, eventually erroring out with an error message. After this I can't get into TWRP anymore. When I try the phone boots to the TWRP startup screen, and just freezes there.
I have tried reflashing TWRP using Heimdall and this does nothing. Flash succeeds, nut still freezes at TWRP splash screen.
I googled some more and found a suggestion to flash stock Samsung firmware, and then try again, this time formatting data system and cache without trying to first wipe them. Problem is I can't successfully flash stock firmware.
I tried using this method in Heimdall, but it complains "Local and device PIT files don't match and repartition wasn't specified!" and fails.
I've also tried booting into Windows and using Odin, but it never works. The screen turns grey, and no progress indicators ever start. I assumed this was because I had the incorrect drivers for the phone, and tried using zadiag.exe to replace them, but the driver install fails.
I'd greatly appreciate any help. I can't seem to force the phone to shut off, it just keeps rebooting and getting stuck on either the TWRP spash screen or on the download mode screen. I know this is solveable, but unless I figure it out fast, I'm worried I am going to burn in the screen.
Any suggestions appreciated!
Never mind. I must just have had a bad stock image.
I downloaded a different one, and retried heimdall and it flashed properly.
I am now able to re-flash and boot into TWRP again.
Hopefully I won't have the same problem again when I try to wipe the partitions...
Alright,
So I solved this issue by (once I reflashed stock, and then reflashed TWRP again) formatting the data partition twice, first to ext3, and then back to ext4. This looks to have cleared the encryption issues that were causing thsi problem ,and allowed everything to continue working as expected.
Related
I'm having a bit of an issue with my SM-P900. I rooted using Odin 3.9, installed TWRP 2.7, and then tried to install custom rom. The custom room (Link Here) But, I noticed something a bit strange while it was installing, it was unable to mount cache, data, etc, but it showed to be successful so I didn't think anything of it. I tried to boot into it, got past the initial Samsung screen, but then afterwards it was just black. I reflashed TWRP 2.7 but nothing happened. I also tried reflashing a stock rom I found using Odin 3.9 which let my device go past the initial samsung screen and into the second one(the one with the sound) but it just hung there. I booted back into TWRP and found that now only data and storage are unable to mount.
I've been searching all day, and I'm stuck. Does anyone have any idea how to fix this?
Hi there, first post on here!
I've bought a nexus 5 off of eBay from some person who tried to root it and failed, thinking it would be an easy matter of restoring it.
However, the standard stock recovery process did not work, and I've encountered a number of issues:
When the device gets to erasing 'cache', it stays there for upwards of half an hour with no results.
With stock recovery flashed, pressing power + volUp immediately makes it erase /data, with no other options given.
It also does not show the stock recovery icon, instead a standing up android figure with a spinning poly in front of it.
Flashing TWRP and booting into recovery, it says 'e' is locked and goes into a boot loop.
Also no options in CWM recovery
I thought I would ask on here because it's out of my league now, I've tried on both windows and mac with no luck and I'm not sure what to try next, maybe just leave it until cache finally erases?
Thanks in advance!
You need to read read and read some more.
Start here:
http://forum.xda-developers.com/google-nexus-5/general/resource-guides-info-threads-linked-read-t2784527
It sounds like the bootloader is locked.
It's almost impossible to brick a nexus.
I've managed to get a version of CWM loaded.
Performing factory reset gives the error that /data cannot be mounted for wiping.
Bootloader is definitely open.
M1kesky said:
I've managed to get a version of CWM loaded.
Performing factory reset gives the error that /data cannot be mounted for wiping.
Bootloader is definitely open.
Click to expand...
Click to collapse
Ok :good:. That means you can install TWRP 3.0.
Try this: flash back to a completely stock MM or LP ROM by manually flashing each partition, inlcuding the userdata.img file. When you have finished flashing all partitions, boot directly to recovery from fastboot mode, perform a factory wipe, and reboot.
I've tried doing that but it just results in the standing up android icon, with power+up leading to it trying to wipe data again. no option to do a factory wipe.
I put TWRP 3.0.0 on just to test and ended up in a worse bootloop, which failed to load TWRP but occasionally got into it and displayed this:
imgur.com/RKyZIJf
Sorry as I am a new user it doesn't let me use links
audit13 said:
Try this: flash back to a completely stock MM or LP ROM by manually flashing each partition, inlcuding the userdata.img file. When you have finished flashing all partitions, boot directly to recovery from fastboot mode, perform a factory wipe, and reboot.
Click to expand...
Click to collapse
Thanks, I gave it another try and did the recovery partition last, and made sure I manually put it into recovery mode from bootloader.
The red triangle and recovery menu are back, I can't thank you enough!
Glad you got it to work. I suggest using TWRP 2.8.7.1. For some reason version 3.0 does not work properly with all N5 phones.
It's still happening.
I've been away for a few days so only had the chance to respond now.
I got into the ususal recovery screen as mentioned previously and tried to do a factory reset, but it had problems with /data again.
I left it the entire night while I slept and it was still saying formatting /data in the morning, nothing had changed.
Anybody got any more suggestions? It's also back to the android with the rotating poly instead of the android with the exclamation mark.
EDIT: when flashing userdata, no matter what version of android I try, it always hangs.
It started on 6.0.1 if that helps.
The userdata.img file is included with each stock rom. I advise against mixing userdata.img files from different stock ROMs.
Sorry, I mean that I've flashed completely whole different versions of android and the result is the same across all of them, not that I've used different userdata img's on the same version of android.
Could be an emmc problem which would require a motherboard swap.
Is that likely to happen when the previous owner said it was fine before they tried to root?
Long story short I was running latest nightly of cm13, I decided to flash to cm14 to try nougat. I had backups, during the process I pulled an idiot and wiped everything dalvik, system,data,internal storage,cache . So now I have no backups, I can still get into TWRP and attempt to flash Roms but I've tried countless ones and same outcome, TWRP just restarts half a second after it tries to flash, I've even tried the stock rom with no luck.it starts and gets to MTP enabled installing "name of rom" and then reboots . I've been using a tablet to install the Roms onto an sdcard and then using the sdcard to flash, I'm hoping it's an sdcard issue and I'm waiting to get the laptop to try and put the Roms on internal phone storage and try. I'm hoping I won't have to go back to unroofed stock using kdz tot. If anyone knows what's wrong please help.
Well I tried flashing to stock and can't get into download mode, computer won't recognize phone. So I decided to try updating Twrp flashed the image, rebooted and now I'm stuck on [11050] fast boot mode started. Nothing gets me out of that.
I've got an old Samsung Galaxy Note 10.1 (N8010) which was flashed to a custom ROM (Cyanogenmod) in 2016. I'm not sure what version because I'm unable to boot it. A few weeks ago, the tablet rebooted without reason and got stuck on the Cyanogenmod bootscreen forever. I've let it run for 24 hours without result.
So this is what I tried:
Reboot into recovery mode (TWRP 2.8.6.0) and wipe everything. Then I tried to flash a different ROM, but when the device reboots, everything seems to be reset and it tries to boot the old corrupted ROM again. I also tried a newer version of LineageOS. But for that, I need a newer TWRP version. So I download and put the newest TWRP version on it using ODIN mode. Flash Passes says ODIN, but after reboot, TWRP 2.8.6.0 is still being loaded. I tried it again without 'reboot' checked so I can reboot directly back into recovery manually, but this also, didn't worked. (by the way, ADB works when loading TWRP, FASTBOOT doesn't work when loading ODIN mode, fastboot doesn't recognize the device)
I tried to flash stockrom back onto the device, also using ODIN mode. Flash passes, no errors. Device reboots and.. nope! It still tries to load the old Cyanogenmod forever.
I'm basically stuck here. I can't update to a newer Recovery and I cant flash the rom because everytime I reboot the device, everything change i made is gone.
I noticed that when I list files in /data the folder seems to be empty.
I also tried to reformat /data to fat and back to ext4 but formatting to fat fails and formatting to ext4 succeeds, however, after a reboot, everything i did seems to be undone by the device. Even the time and date is reset.
Is there a way I can bring back my tablet back to life? Thank you!
I have pulled the recovery.log file and uploaded it to pastebin.
I can't post a link to it because I do not have made 10 posts yet.. (very anoying). So i put the adress here:
https://pastebin.com/3muqPMzz
FSCK check on /data returned this:
Code:
~ # e2fsck /dev/block/platform/dw_mmc/by-name/USERDATA
e2fsck 1.41.14 (22-Dec-2010)
/dev/block/platform/dw_mmc/by-name/USERDATA: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway<y>? y
yes
e2fsck: unable to set superblock flags on /dev/block/platform/dw_mmc/by-name/USERDATA
And Odin mode: NAND ERASE ALL returns
Code:
<ID:0/006> Complete(Write) operation failed.
It seems like my Note 10.1 tablet is suffering from the emmc brick bug.
niquedegraaff said:
I've got an old Samsung Galaxy Note 10.1 (N8010) which was flashed to a custom ROM (Cyanogenmod) in 2016. I'm not sure what version because I'm unable to boot it. A few weeks ago, the tablet rebooted without reason and got stuck on the Cyanogenmod bootscreen forever. I've let it run for 24 hours without result.
So this is what I tried:
Reboot into recovery mode (TWRP 2.8.6.0) and wipe everything. Then I tried to flash a different ROM, but when the device reboots, everything seems to be reset and it tries to boot the old corrupted ROM again. I also tried a newer version of LineageOS. But for that, I need a newer TWRP version. So I download and put the newest TWRP version on it using ODIN mode. Flash Passes says ODIN, but after reboot, TWRP 2.8.6.0 is still being loaded. I tried it again without 'reboot' checked so I can reboot directly back into recovery manually, but this also, didn't worked. (by the way, ADB works when loading TWRP, FASTBOOT doesn't work when loading ODIN mode, fastboot doesn't recognize the device)
I tried to flash stockrom back onto the device, also using ODIN mode. Flash passes, no errors. Device reboots and.. nope! It still tries to load the old Cyanogenmod forever.
I'm basically stuck here. I can't update to a newer Recovery and I cant flash the rom because everytime I reboot the device, everything change i made is gone.
I noticed that when I list files in /data the folder seems to be empty.
I also tried to reformat /data to fat and back to ext4 but formatting to fat fails and formatting to ext4 succeeds, however, after a reboot, everything i did seems to be undone by the device. Even the time and date is reset.
Is there a way I can bring back my tablet back to life? Thank you!
I have pulled the recovery.log file and uploaded it to pastebin.
I can't post a link to it because I do not have made 10 posts yet.. (very anoying). So i put the adress here:
https://pastebin.com/3muqPMzz
Click to expand...
Click to collapse
Some of what you describe seems to suggest that your internal sdcard is corrupted, but, you still have TWRP booting. I would think that TWRP wouldn't boot if the internal was damaged.
Sent from my LGL84VL using Tapatalk
I can boot twrp but anything I do in there is temporary. I can't write to the internal SD. Only read. Seems like the emmc brick bug to me. I wish there was a way to check if this is absolutely true.
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.