Just finished my 2nd time flashing. Been having some issues with FC's and some functionality of apps not working as it should, so I did a few things and wanted to restart from a clean install. So the first issue isn't uncommon, I think i read like 50 people talking about it already lol Keeps saying there is no Boot.sig, System.sig, Recovery.sig and so on. Generally the fix has been to just extract the Boot-Recovery-System, etc files out of the archive, drop it in with the others, and just flash them each individualy i.e /fastboot flash system system.img etc.
These last 2 times, that did not work. When ever I go to flash the radio/modem, I get this error saying the partition doesn't exist. Not sure what I did wrong. Did it the exact way I've been doing it since the beginning of me doing it lol*
So yea just wanted to see if anyone else was getting *"Error flashing Partition, Partition Does Not Exist"*
So what does work for me tho, is with the original error, where it says the archive doesn't contain Boot.sig and so on, if i just let it sit for like 2-3 min, then hit enter, it jumps back to life and finishes the process and my phone boots right into 4.4 lol*
Kit *Kat is playin tricks on me*
Anyone else ?*
Related
Ok i know the fourm is somewhat littered with these posts, and i've tried to do as much myself as i can.
Last night my phone offered the KitKat OTA update.
Its a Nexus 4, with unlocked bootloader, TWRP recovery and root, but no system modifications.
I accepted the update, thinking that it would simply update to kitkat and lose my root. On rebooting to install, the phone launched TWRP by itself, and TWRP ran the update, it went thru various stages of patching things before getting to a step saying something about permissions, where it stopped with an error.
I rebooted the phone and ended up stuck at the new 4.4 boot animation.
I went back into TWRP and tried clearing the caches, and also using the "fix permissions" option but still it hung at the boot animation.
So needing to get the phone working, with minimal data loss, i downloaded the 4.3 stock image, and flashed the boot and system files on in fastboot mode. Hoping to get the phone rolled back to 4.3 where it was before.
Partial Success, in so far as the phone booted, but things are somewhat "weird".
Some data has vanished, such as my call log, and my SMS inbox. Other data seems fine, such as my email client, my wifi settings, google login info, backgrounds etc. But on top of that there are weird quirks, for instance if i swipe down the notification bar, the settings button doesnt work, and i think notifications arent actually showing up either. Similarly, the home button is broken and does nothing. And even more strangely the keyboard appears to be missing!
I'm thinking we're probably at the stage of having to flash a complete factory image, and at least the phones booted so i can pull off my images and things. I'm somewhat pissed about my SMS as i didnt even think of backing them up because it was an OTA update and i assumed it would Just Work.
Any thoughts on what has happened here?
Regards
Kevin
ok, so i decided to reflash 4.4, and things are still weird.
Same faults as before, no keyboard, no notifications etc etc.
I did fastboot update image image-occam-krt16s.zip, but that doesnt seem to have erased by Apps etc.
I presume i'm going to have to do a full wipe with -w switch and start from scratch?
Same case, mi phone only works with 4.3. Download the 4.3 image, and only flash boot and system, dont flash userdata.
Try flashing the images and making it wipe your device so you don't have any data left. (AKA Clean flash, you did a dirty flash)
ok, so i decided to reflash 4.4, and things are still weird.
Same faults as before, no keyboard, no notifications etc etc.
I did fastboot update image image-occam-krt16s.zip, but that doesnt seem to have erased by Apps etc.
I presume i'm going to have to do a full wipe with -w switch and start from scratch?
Aragorn84 said:
ok, so i decided to reflash 4.4, and things are still weird.
Same faults as before, no keyboard, no notifications etc etc.
I did fastboot update image image-occam-krt16s.zip, but that doesnt seem to have erased by Apps etc.
I presume i'm going to have to do a full wipe with -w switch and start from scratch?
Click to expand...
Click to collapse
Yes you do. A clean flash is a full wipe.
Yeh that sorted it, Sorry about the double post above, i tried to edit it but it wouldnt let me.
I copied my images off and did a full wipe and now its working again.
It seems like the forum is littered with these messages, but no-one seems to know the actual cause? I presume its somehow related to the modified recovery not applying the update properly?
Sometime last night, my AT&T G2 (D800) decided to go from being powered on and idling, to going into TWRP recovery mode. All by itself. I saw this, unplugged it from USB, and tried to reboot into system mode. But it simply won't do anything except boot into recovery. Powering off, trying to get to the bootloader, none of that works.
This is not a custom ROM, it's 4.2.2 stock from LG. I only rooted the phone, which was several weeks ago, and haven't had any problems, aside from TWRP not wanting to back up anything. I've been using Android since the original TMO G1 with JesusFreke's ROM, so I have a pretty good idea of what I'm doing, hopefully.
The only recent changes I've made are:
I updated busybox about 3 days ago (but have rebooted fine since)
I grabbed several legit apps from the market last night
Last night I also DL'ed, but did not apply, a ~50MB OTA update that has been pending. I don't think that would install without explicit permission anyway, which I didn't give it?
This phone was encrypted from the start. Maybe that;'s what prevents TWRP backups,, but right now I'm seeing TWRP errors/logs saying something like "Unable to mount \data". And yet I can browse to other folders, and see filenames in \etc for example. However, I don't see any files at all in \boot.
Since this phone has no external memory, and it's customized and has numerous configured apps, I really really don't want to have to wipe it. Although at this point, that may not even fix the problem? Even if it did, since I haven't been able to make backup images, it would be a Bad Thing™ either way. (Yes, I do have a secondary plan with Titanium, with backups going to cloud storage, but these are tedious and now a few weeks old. And wouldn't restore the ROM & system en masse.)
Please help.
Solved?
I'm not sure what caused this to occur, but I found somewhat of a solution after digging deep into my Google-fu.
I followed the instructions in this XDA thread and it actually worked. I didn't have adb access, but I was able to use dd successfully. It allowed me to boot into the device, unencrypt it, then arrive at the lock screen.
However, when I put in the lock code, it went apesh!t and played multiple notification sounds, with a blue circular wait symbol. It also flashed the LED from green to blue, as it normally only does during boot. Once I pressed the power button, I was back back into TWRP.
So then I followed Step 2 again, and once in the phone, I used terminal to run the dd command from inside the OS. This might be what it ultimately needs, because the prior attempt in TWRP had an error to the effect of "no space left on device".
I can't call it Solved yet, but it looks good to at least be able to get in and use the phone. I'm backing up with Titanium before I do anything else and will reboot and test its permanency later.
I'm gonna close this thread now that I think I have a handle on what is going on. The fix does survive a reboot, so I believe it's possible to repair the issue permanently per the instructions above. I also ran the phone for 3 hours with heavy app usage and no problems.
I believe what may have happened is my OTA decided to override my choice to NOT update the ROM, as some have reported in this Reddit thread. There's a lot of good info in that one, including how to stop getting nagged by turning the OTA notifications off, or to freeze it entirely with Titanium Backup if rooted.
Anyway, what apparently happens is that when the OTA/upgrade goes to reboot, and encounters a custom recovery, it gets confused... when you try to power cycle or reboot again, it sees the stock recovery still hasn't run whatever it wanted, so it starts recovery again Lather, rinse, repeat.
Fun times.
So I seem to have a strange issue with my Moto XPE. I have liveboot installed so I can see the Kernel log (I think that's what it's called, if not then please excuse my lack of knowledge). Sometimes when I reboot, the phone will start to boot like normal, then at some point through the process, this error will keep showing up.
"msm_rngata not available!" <-- That's not supposed to be an emoticon, but rather "msm_rng : Data not available" only without those extra spaces.
It will repeat over and over along with some other things that mean nothing to me because of my lack of technical knowledge on the matter. It will keep doing that until the battery dies if I were to let it.
If it decides it's going to boot normally that error will still show up a few times but the phone will continue to boot and it won't hang up on it.
My concern is this: What if I have a random reboot and this happens and I don't know about it and it ends up damaging my phone in some way (runs the battery down past the point of return or it overheats, etc).
I'm on TruPurX ROM with Frankenkernel. I've observed the issue with multiple stock based kernels. Any idea what this is or how to fix it?
-Manually booting into TWRP, then rebooting to system usually makes it boot correctly.. but not always.
Have you tried another custom ROM to determine if it is an issue with the current one you are running? Could be a corrupted download our install.
I received an update push from Motorolla that installed Nougat. After that, my phone would crash every 3-10 minutes. I did all the troubleshooting I could find online. I contacted support and they wanted me to spend $150 to get it "refurbished." Of course, it sure seems like a software problem, so that wouldn't help me anyways...
I turned to custom. After rooting, installing SuperSU and TWRP, I couldn't get several versions of AICP or Lineage to ever boot (stuck on loading screens). I also tried all the advice from this thread.
I went back and installed the stock Rom using f2fs , and the phone would get to the "hello moto" part of the boot up, then crash and reboot. I tried again using EXT4, and it worked, but just like before I ever begun, my phone was crashing every 3-10 minutes. However, the first crash wasn't until after I made a phone call, and my phone had been crash free for about 20 minutes before that call.
I'm a I.T. guy, but I'm not a "phone" guy. But it seems to me that there must be some other software that was modified during the update that is causing the problems that isn't part of ROMs. Something in the Kernal, or a driver folder or something?
Also, is there a way to get crash reports? So maybe if I at least go back to the default ROM and wait for it to crash, I have some info to work with?
Any help is greatly appreciated, thanks!
Flash full stock 6.0x for your model/region.
Important:
Without bootloader, gpt. Don't try locking BL.
Links you can find in my signature.
Try normal boot and after success any custom.
You cannot allow any ota update after it.
Some customs are only for Nougat modem/radio - don't flash it. @Kaivian
Ok, I got most of that, except I don't know what gpt refers to and am not getting any hits on search.
My signature - flashing stock - without bootloader & gpt.
So, I installed a 6.0 stock ROM and got tons of errors. I tried a 2nd time, still got tons of errors. Needless to say, stock 6.0 didn't boot. I decided, "The heck with it" and tried installing Lineage 7.1 again... and it worked! It finally booted up entirely. However, now I get a "Sim card missing" notification. Can I just reinstall part of something... like the modem? so I can keep this "working" lineage boot? Or am I starting over yet again?
Repeat
from
fastboot flash modem ...
to
...fsg.
dzidexx said:
Repeat
from
fastboot flash modem ...
to
...fsg.
Click to expand...
Click to collapse
This caused it to not boot.
I went back to 6.0 and turned off auto-updates. I'll try again sometime when I have time. I did like the custom rom a lot, just couldn't use it as a phone xD
Hi guys. I have a very frustrating issue. I flashed (dirty) the new 5.0.1 rom through twrp but it never booted for some reason (idk why really although the flashing process ended up successfully). then I tried to go back completely stock (official recovery,flash official OxygenOs, and go unroot) by flashing the official recovery and sideload the newest rom (after that i would oem lock/unlock but i didnt get there just yet), which is something i've already done like dozens of times without ANY issue. Everything seemed good until i reached the 47% of the sideload process where it ended giving me the Total xfer: 1.00x error. I tried flashing a previous rom, i tried using other recoveries (twrp) but the result was the same every single time (all of them stuck at 47%). So I thought that i bricked my phone or smth since i couldnt install any rom and boot inside the phone. Then i just did "fastboot oem lock" (i dont know why i did it in case someone asks, i just did it in my frustration since it was one of the few things i could do in fastboot mode), so it ended up giving me the wiping data screen (from the original recovery) although i really didnt know what was wiping (my sdcard folders were not the "usual" one but it was a number of folders named randomly with big strings containing letters and numbers, not the usual "pictures", "download" etc etc) . Then it booted into the phone having installed the newest android and no error messages or something like that! After this weird incident i thought to try to reflash the same rom since everything was looking good now but hell no! again the same error at the same point exactly! so i dont think i will be able to flash any other roms official or not. Has anyone found a solution to this guys or why this error suddenly appeared??
Dude, i have te EXACT same problem. I wanted to clean up an sideload the current OTA that was on my device to return to stock and accept OTA updates again, but got the Total xfer: 1.00x at ~47%!! I have tried everything to no avail. i even made my own trhead about it since no one seemed to have a solution for it. Did you fix it since? I really don't want to be stuck on the same OxygenOS version for ever.
Here's a link to my Thread : https://forum.xda-developers.com/on...oading-ota-t3844469/post77663999#post77663999
Hope you respond soon!
Luuk
Fixed it!
Luuk271 said:
Fixed it!
Click to expand...
Click to collapse
Hi Luuk ! I've quite the same issue, how did you fix yours ?
Can you please tell how you fixed this!? I still have this issue and it drives me nuts