Way late in the game to get a Note 5, but Sprint gave our company the right price for a batch of 'em with a deal. So... here I am, rooting my Note 5. And all was well until I went to backup in TWRP my rooted stock rom.
The error message "e: recv error on uevent" occurred four or five times.
After trying again, I went googling and found some folks with a different make of phone had gone back to the older 3.1.1 version of TWRP. I did so as well and - sure enough - no errors.
I don't know what to make of that. Perhaps the "e: recv error on uevent" is one of those messages not to worry about. But I'm not going to be the guinea pig for that test. Heh. So... if you run into this issue, try TWRP 3.1.1 and see how it goes.
Blessings.
You don't need to backup the stock ROM, the latest one in 4 file format can always be downloaded with SamFirm (Latest build is DRG1)
That error is present (AFAIK) in the 2 or 3 latest TWRP builds. I'm on the 3.2.3-0 and its still there. Backups are restored OK.
Related
Late last week I tried flashing a new rom onto my CDMA (Verizon) Galaxy Nexus. I've done it before (I am using AOKP), however I tried a few new things and now my phone is stuck in the state it was in before this all started.
What I am on: Galaxy Nexus (CDMA, Verizon), AOKP build 28, franco Kernel
What I wanted: AOKP build 31 OR CM9 alpha nightly (for this device). I tried CM9 first.
What I did NEW: Installed ROM Manager, Flashed Clockword Mod Touch, "fix permissions" in CMW touch, mounted /system after flashing my Titanium update.zip. I may have mounted /system before fixing permissions.
What happened? The startup logo changed from the AOKP one to the CM9 one, but when the system booted up everything was exactly the same as before. This is the state I am talking about. No matter what I do it always reverts to this exact state upon reboot. I can install new apps, take pictures, etc. and it will revert to this upon reboot with all the apps, pics, etc. gone as if it never happened. The phone also reboots randomly. I also can't delete anything off of the sdcard partition. I've gotten messages saying /system is read only, and I think /sdcard has become read-only as well.
What I've tried to fix this so far:
Via the Galaxy Nexus Toolkit for Windows AND adb/fastboot:
Flashing the old CWM (no errors, but doesn't work)
Restoring an old nandroid (no errors, but doesn't work)
Flashing the stock rom for the Verizon Galaxy Nexus, released by google (no errors, but doesn't work)
Fixing permissions via CWM (no errors, but doesn't work)
Via Odin I also tried flashing the 4.0.2 stock rom. I got no errors (it said successful), but it didn't work. I am still stuck with the same exact state when I reboot.
I'm at my wit's end here.
Did you try a full wipe before the new installation?
JonSchimmy said:
Did you try a full wipe before the new installation?
Click to expand...
Click to collapse
I'm not sure. It's been a couple of weeks ago. I want to say I did, but it's entirely possible that I didn't.
My Tab has been collecting dust for most of the year, so I figured I'd dust it off and update it to a shiny 4.3 rom. I wiped everything (no nandroid, stupid I know) and tried to flash, but I got a "status 7" error. It wasn't tied to the device, but to symlinks (I did try to remove the assert lines in the updater script first, just to make sure). According to some of the error lines in TWRP, it was the permissions (set_perm some changes failed). This result was the same from CWM, to TWRP, and finally to Philz recoveries.
I just couldn't flash anything. I tried a few 4.3 roms, and then assumed that perhaps something changed with 4.3 firmware-wise that I didn't have, tried something 4.2 like what was on before. Nothing. Same status 7 errors. I've been doing some research and can't find anything that will work for me. I've noticed, however, that I can't unmount the data partition. I'm wondering if this is my problem, and I can't find the solution for this either. Help the noob?
EDIT: I managed to flash a stock ICS image via Odin, then attempted to install TWRP and try again. Same errors. Not sure what could be going on.
Anybody? I'm not sure how often the second page gets glanced at around here. Even an inkling of an idea might put things in motion.
I believe Status 7 usually indicates the wrong update file.
You might try...
androidforums.com/nexus-s/588179-jelly-bean-update-status-7-error.html
highonandroid.com/android-roms/how-to-fix-status-7-error-with-cwm-recovery-on-rooted-android
ibtimes.co.uk/articles/499093/20130814/galaxytab2-p3100-p3110-p3113-android43-jellybean-cyanogenmod102. htm
Best of luck.
Bennyboy371 said:
My Tab has been collecting dust for most of the year, so I figured I'd dust it off and update it to a shiny 4.3 rom. I wiped everything (no nandroid, stupid I know) and tried to flash, but I got a "status 7" error. It wasn't tied to the device, but to symlinks (I did try to remove the assert lines in the updater script first, just to make sure). According to some of the error lines in TWRP, it was the permissions (set_perm some changes failed). This result was the same from CWM, to TWRP, and finally to Philz recoveries.
I just couldn't flash anything. I tried a few 4.3 roms, and then assumed that perhaps something changed with 4.3 firmware-wise that I didn't have, tried something 4.2 like what was on before. Nothing. Same status 7 errors. I've been doing some research and can't find anything that will work for me. I've noticed, however, that I can't unmount the data partition. I'm wondering if this is my problem, and I can't find the solution for this either. Help the noob?
EDIT: I managed to flash a stock ICS image via Odin, then attempted to install TWRP and try again. Same errors. Not sure what could be going on.
Click to expand...
Click to collapse
True, this is usually the case, but not this time. I tried all these, but the root of this issue is with the symbolic links and setting permissions. I am starting to really think it's all about getting data to unmount, but I haven't been able to get this to happen.
back to the stock rom
---------- Post added at 04:20 PM ---------- Previous post was at 04:17 PM ----------
[/COLOR]
Bennyboy371 said:
My Tab has been collecting dust for most of the year, so I figured I'd dust it off and update it to a shiny 4.3 rom. I wiped everything (no nandroid, stupid I know) and tried to flash, but I got a "status 7" error. It wasn't tied to the device, but to symlinks (I did try to remove the assert lines in the updater script first, just to make sure). According to some of the error lines in TWRP, it was the permissions (set_perm some changes failed). This result was the same from CWM, to TWRP, and finally to Philz recoveries.
I just couldn't flash anything. I tried a few 4.3 roms, and then assumed that perhaps something changed with 4.3 firmware-wise that I didn't have, tried something 4.2 like what was on before. Nothing. Same status 7 errors. I've been doing some research and can't find anything that will work for me. I've noticed, however, that I can't unmount the data partition. I'm wondering if this is my problem, and I can't find the solution for this either. Help the noob?
EDIT: I managed to flash a stock ICS image via Odin, then attempted to install TWRP and try again. Same errors. Not sure what could be going on.
Click to expand...
Click to collapse
try to get back to the stock rom firmware, I have the same
problem few days ago, cant flash any rom
n I think the problem b'cause wrog flash when rooting or
flashing the image cwm/bootloader
that's all I know,
Well it's good to know that I'm not the only person who has had this problem. I managed to get back to stock. I'm not sure what I can do from here, though. I don't want to try anything because I don't want to break it.
Howdy all. Having a little trouble and hoping that someone out there will have an idea or two.
I'm on an 8013. I've been running Gnabo v3, and as an experiment decided to try CM11 instead. Downloaded CM11 unofficial from here: http://forum.xda-developers.com/showthread.php?t=2637079
and it was the 8013 rom. Did all my backup and wiping stuff as usual, but when I tried to flash CM11 I get this message.
This package is for "c0, p4notewifi, p4notewifiww, n8013, GT-N8013" devices; this is a "p4noterf".
E:Error in /sdcard/0/Download/cm-11-20140818-UNOFFICIAL-n8013.zip
(Status 7)
Installation aborted
What I think is happening is this; the Gnabo rom was for a couple of different Note 10.1 devices, modified during installation for the 8013. The model number would show up as GT-N80xx, or something similar, I can't remember exactly and can't get to it to confirm. But it didn't read as an N8013. It appears CWM is seeing the mismatch and not allowing me to flash.
On a perhaps unrelated note (no pun intended), when I try to restore it says there's an MD5 mismatch and wont' restore my backup. So that's a non-starter as well.
Questions:
1. Is there a way to force CWM to ignore the mismatch and flash CM11 anyway? I know the hardware is 8013, so is the CM11 rom, so I'm guessing that would work if I could make it happen.
2. In the past, I had a similar problem and just restored stock with Odin. That's the next plan, but the Gnabo rom is KK and stock would be JB. I've heard there have been problems going from KK to JB due to different bootloaders. Is that going to be an issue here?
I'm open to any suggestions you all might have. TIA.
Further investigation leads me to believe that it is the model number mismatch that is preventing CWM from flashing the rom. I've read that TWRP doesn't do that check. I may install TWRP through Odin, but as that is device specific as well I'm a little nervous about that. Still looking...
Alright, here goes.
So one day I was interested in flashing a new custom ROM (Preferably LineageOS) to my Huawei Mate 10 Lite. Long story short, it's now soft bricked. Only TWRP is working.
But, that's not enough information. Here's the fully story.
After realizing I could not get the Bootloader unlock code using the official method, I've tried DCUnlocker. I paid, and got my code.
I've installed HiSuite, 274829 drivers and finally unlocked the Bootloader. Now, the phone said "This device is unlocked and can't be trusted", but it booted fine. YES!
After that, I downloaded LineageOS 15.1 and flashed it. Before flashing it, I formatted everything, wiped cashe, davlick ect... And.. made my biggest mistake.
Not making a nandroid backup (dammit).
Don't ask me why, I thought it would go well (ugh).
Anyways, I flashed it, error 7. Alright, removed the assert lines. Flashed it again, and it worked, but right at the end, another error? It was error 7, again, but a little different.
This time, it said "failed to mount /dev/block/bootdevice/by-name/vendor at /vendor: device or resource busy"
Okay, now I'm starting to get worried. Like, REALLY WORRIED.
It also said it failed to execute a line in the updater script, one of the last lines. But I would not delete it, just in case.
When I tried to boot, nothing. Went back to Google.
At this point, I learned that any Treble ROM will NOT work with Android version of 7.1. shhhiiii
I was on EMUI 5.1 aka 7.0, and this was worrying. At this point, I tried to return to EMUI 5.1, but since there was no backup, well...... To Google we go!
I did not find any stock room that running EMUI 5.1, but only found EMUI 8.0. I did find a stock room on 7.1, but I'm not paying 15 dollars for it. Not about that life.
I tried the dload method, but apparently my sdcard is on FAT32, and because of that I cannot upload the UPDATE.APP to it.
I've also tried eRecovery, but to no avail. "Failed to get package".
So now I'm stuck on a couple of options, and I need help from you, the XDA community.
1) Remove the line that's causing the issue but at the cost of it maybe not working
2) Somehow format the sdcard and somehow upload the update.app to it
3) Somehow update Android's system to Project Treble, although not sure it's possible since there is no OS.
4) ?????????????????
Please, help me. I'm in hell right now.
Cant flash twrp nor the patched magisk boot img to both slot a and b.
Bootloader is unlocked.
Flashing scripts via .bat files for stock zips of both android 10 and 12 results in "FAILED (remote: Partition product not found)" or "FAILED (remote: variable not found)" respectively.
I have no recovery.
When I had twrp, I've made the mistake of wiping my whole android 12 data, storage, and system and flashing an android 10 rom without reading up of the separate a and b boot slots nor the effects of my actions leading to bootlooping. (I've done with this other devices before with no problems). This in turn wiped the twrp recovery I had flashed and left me only fastboot commands and a twrp version up to 3.3 and 3.2 with no hope of getting usb otg to work as it was only available with the later versions of twrp and since I and now technically on an android 10 bootloader, any attempt at that time to flash twrp 3.6 was met with a (remote: Error calling AvbLoadAndVerifyBootImages Load Error) or some kind of other error I have no logs for. Now I cant even tetherboot to twrp 3.2 nor 3.3 and I get that error regardless.
[Boots to bootloader no matter what. Shows as UFS:Micron, Error reason - reboot bootloader - bootloader version is b1c1-0-4-7617406]
I believe I can get access to internal storage to flash these updates once I get a recovery tethered from the bootloader. I do not know if its possible to boot to fastbootd or whatever its called (used for write permissions/sideload update zips) even if I hadn't gotten into this predicament. I will be buying another Pixel 3 in the meantime as I have money to burn and like to hurt myself financially, and emotionally to get to my goal with this device. ( Didn't buy another one, I was committed to the cause!)
I am not a noob nor a pro, but somewhere in between. My biggest point of failure is not reading up on how the partitions are set up and the various issues others had when flashing android 10 and 11 roms. Any suggestions other than "uPdAtE tHe fAsTbOoT aNd AdB dRiVeRs" are not welcomed. Thank you. I will update once I find a soluton to my problem Which I Will.
Again, my main concern right now is getting tethered twrp to work again and need suggestions. I have older versions of platform tools and the latest so please non of those comments I see on literally every other thread.
Edit: I didn't mention this before, but I did have the ability yo sideload when I had twrp at the time before crapping everything out the window, but nothing would work and gave up. Just wanted to add if anyone was wondering.
First update, I used the propriatary "Tool All In One Tool" and I was able to boot to fastbootd, and wipe my data and storage, while updating my stock zip to android 12. Now I can tetherboot twrp 3.6.1_11-0 with the option for usb otg, wish me luck boys. I'm in.
Second update. Still stuck on first update, but weighing my options in the meantime. I flashed twrp via the flash current twrp option, but when I boot to it, touch is disabled so thats great... I can fast boot to only the twrp versions after 3.6+, so not so bad. I have no os installed, but I will try my hand again at that tool all in one tool again. I'll update tomorrow if anything comes of it.
3rd update. FROM THE BRINK OF DEATH!!! WHOOOOOOOOOO!!!!! I got the pixeldust rom flashed and working like a BOSS!!!!! You won't believe the 2 days I've had trying to get this thing to work. All in all 1 out of my 3 flashdrives finally worked with otg. I had a windows recovery drive premade on it so I just copied and pasted the files there without a hitch! Thank you Google for having to make me miss work and actually do research to get this thing working again! Thank you for the guys at Tool All In One Tool for making this recovery possible, I will shout out your thread. If anyone who's in a similar situation needs any help from me or any info, I'll be glad to help. This will be the second to last update. I can also make phone calls and use data so Pixel Dust rom is good to go if that was one of your concerns. See ya!
Final update, I got crdroid flashed with root and safetynet passed, I just found out that google Pay was imbedded in gapps so now I don't need the pay app anymore to do transactions! My banking app also works, got vanced finally installed (couldn't do it on regular stock ROM) some glitches with the ROM here and there but no worries. For who ever reads this. There's hope. I fd up as bad as you can get shy of a hard brick. I still don't know too much but learned near twice as much as I knew just a few days ago. If you need help just DM me and I'll work my hardest to bring the light. This phone is absolutely amazing and on god wished google was a better company to praise. I have more plans for these phones and hope more Roms come out to support it.
I have one question however, how do I make a backup of my system/system_ext partitions? I can make a back up of everything else but that with these two Roms... I have a backup of it with my stock ROM, but it resumed to mount when I used otg... Didn't try internal yet but I'll assume the same, is it a glitch with current twrp?