Related
Did something very silly when trying to convert to F2FS and flash a new ROM. I managed to root my N7 and was following instructions here;
http://forum.xda-developers.com/showthread.php?t=2678140
to convert to F2FS. Only problem was, I was having a lot of trouble getting my computer to connect reliably. Sometimes it would work and sometimes it wouldn't. Anyway, I managed to push the FormatPartitions.zip and flashed it in TWRP. Stupidly, I figured I would flash the partitions zip first then push and flash the ROM and Gapps. Dumb mistake. Thinking now, I realise that I have converted the file system to F2FS without a ROM to work on it.
I can boot to either TWRP or fastboot mode, but thats about it. I have found plenty of information stating that to overcome this, I just need to flash back to stock, but the thing is, neither Windows or Wugs toolkit recognises that I have the Nexus connected. So I'm unable to push any files to my N7 to get around this.
When I'm in TWRP and I reboot, it says No OS installed. I attempted to change the file system back to EXT4 in TWRP, but that didn't seem to do anything.
Have I stuffed it compeltely? If not, how do I fix it?
Sorry about my earlier freakout. I managed to get it sorted. As is nearly always the case, it just took patience and a lot of reading.
It seems to be booting into my custom ROM (SlimKat) now, although it is taking a very long time. I'll be patient this time, hopefully all is well.
Hello, i decided to open new thread because I nowhere find solution. My problem is that after flashing my moto g2 with omni 6.0.1 it get stuck on warning message (about unlocked bootloader). Now I can only get into bootloader menu, connect phone to PC (it's showing dewice as motorola dadb interface),I can only flash twrp using fastboot (fastboot boot twrp.img) and that's it. I can not flash anything permanently to the phone: any custom recovery, any rom,can't fix it with logofix.It just look like phone doesn't accept any flash. I tried also to change boot and other img but with no succes, always after any operation when I reboot phone it's get to warning message.
My phone is motorola 2G xt1068, 8gb, bootloader ver 48.87. Once I tried to flash it with retail rom from sd card via twrp 3.8.0.1 it shows that previous system was omni-titan 6.0.1 and retaildsdsall can not be flash,always shows error 7.
I wonder if I can flash it with upper version of omni: 7.0.1 to fix the problem with booting the phone.
If You could give me any advise how to solve the problem, I would be very appreciate.
Waitng for your reply Guys.
After a lot of tryes I found that anythig I do on the phone after restart it's getting to the same state, even if I manually deleted folder "Firmware", after reboot it's going back. When I prepared Moto for installing new rom using Philz recovery, all the data stay on it's place ( I mean private data like thumbnails in DCIM folder etc), nothing dissapeared. It's look like it have some copy of the system in internal storage and always after rebooting it's recovering it back, even if the system is flashed by new rom.
Have U any idea what's wrong with this phone?
Additinally I found that a lot of internal memory is busy: over 4500MB and free is only 780MB. Even after wiping everything, also formatting system.Should it be like this?
Edit: 2018-02-15
Ok, if noone could help me let's treat it as a blog.
Digging in google I found spanish site with a lot of custom roms for motorola. Now I'm trying one by one till I found the right one.
It's a pitty that Father's of the omni rom leaving me lonely in that situation, I think that they are the best of source of informations about that rom.
2018.02.19
I tried to install OmniRom 6.0.1 Homemade but on the beginning I had the infothat installation failed with error 7. So I found the solution to change the information in meta-info folder.I did it but when instalation started after "symlinkig" it stopped with error: some symlinks failed, error 7. And again I stucked.I feellike I'm very close of the solution but I need help. I'm using twrp 3.2.1.0 running via fastboot (boot twrp.img).
Hi,
as the title says, my phone is not booting anymore, after I transplanted the motherboard from a frame with a broken screen into a new frame (from china).
Abbreviations used:
RR => Resurrection Remix 5.8.5
CWM => ClockWorkMod Recovery 6.0.4.6-kitkat
TWRP => TeamWinRecoveryProject 3.2.1-1
I was using RR from the Rock Stable Setup on it before and it worked beautifully.
What happened:
I performed the mainboard-transplantation according to the iFixit guide
I held the power button to boot the phone:
It vibrated
It showed this screen for a couple of seconds
It vibrated
Back to step 1
And that until I removed power.
Then I tried to boot into recovery mode by holding the key combination on boot:
Same as above, but with this bootscreen
Then I tried to boot into download mode by holding the key combination on boot:
The warning to confirm download mode poped up and I got to see this screen.
I connected it to my PC and opened odin 3.09 and it recognized the device.
I tried to get adb and fastboot to see the device, but nothing worked. (In the old frame and before I broke the screen, it would be recognized at this stage)
I flashed TWRP with odin, odin showed the green "PASS!", but booting to recovery still failed.
I proceeded to flash a stock ROM, which had worked when I had issues with RR.
It worked, I went through the Android 5 setup process, enabled debug and connected adb.
adb saw the phone.
I rebooted to recovery and stock recovery booted correctly.
Sideloading anything with adb failed due to signature verification.
I then went back to download mode and flashed CWM successfully.
It now boots into recovery, but whenever I try to flash anything with CWM, it fails showing this screen
Or something similar (the photo comes from flashing RR 5.8.5)
I have both linux and windows properly setup and used both with adb, fastboot and odin (only windows)/heimdal (only linux).
I checked drivers and usb cables.
I opened the phone back up and checked all connections.
But I can't get any version of RR, CyanogenMod or LineageOS on there.
I've searched the internet, but people that have these kinds of problems after replacing parts of their phones, seem to only have driver issues or skipped steps in the manuals of custom ROM installations.
If you have any idea on what I could try or what I'm doing wrong or not doing, please leave an answer.
I'll keep this post updated below here:
(no updates, yet)
Thanks so much in advance
Simon
Your picture shows stock recovery not CWM .
Try flashing TWRP recovery through Odin .
I did flash TWRP and afterwards there was no recovery anymore.
When I flash CWM, I get the recovery shown in the photo.
The stock recovery has a black background and no touch controls for me.
What you saw must have been CWM.
Update: I can flash twrp-2.8.7.0-hlte-4.4.img.tar and it works. It's the only image that works, but I still can't boot into or flash any custom OS.
The only working OS I have at the moment is a stock android 5.0, which is not all that useful...
If anyone has an idea, why I can't or how I can find out what is causing it, please say so.
I can flash twrp-2.8.7.0-hlte-4.4.img.tar and it works. It's the only image that works, but I still can't boot into or flash any custom OS. )
What do you mean by ANY ??
Well, exactly that.
Regardless of what zip I flash, I end up with a bootloop.
If I flash a recovery zip, the recovery bootloops, but the OS still boots.
If I flash a custom ROM, I can still boot into recovery fine, but booting normally results in a bootloop.
The only way to get software onto my phone has been via odin and only an old CWM, Philz Touch, TWRP (Version 2.8.7.0 and below) and STOCK Android (Versions 4.3, 4.4.2, 5).
Anything else I have tried so far did not result in an error, but I couldn't boot into it either.
If you have ideas for software I can try flashing, please tell. I really have no idea how to get the damn thing to work again...
What happens when you flash correct stock rom via Odin ??
I mean that I can boot into it after flashing it via Odin.
But its terribly slow and bloated compared to ROMs like ResurectionRemix, so I don't want to use it.
AnyTimeTraveler said:
I mean that I can boot into it after flashing it via Odin.
But its terribly slow and bloated compared to ROMs like ResurectionRemix, so I don't want to use it.
Click to expand...
Click to collapse
In that case phone is OK .
Usual is that user is failing to follow instructions .
Not sure what you mean by fastboot on a N9005 .sounds like not a N9005 .
Personally with TWRP 2.8.70 i would be flashing something like .
https://forum.xda-developers.com/galaxy-note-3/development/rom-magma-nx-rom-t3508672
as its correct TWRP .
I am able to follow instructions.
Thank you very much.
I followed exactly the same procedure that has worked many times when switching between custom ROMs.
Also, the phone has a perfectly working version of Ressurection Remix installed at the time my frame broke and it did get stuck in the same bootloop after replacing the frame, even thogh the software was exactly the same.
I am looking for help analyzing the boot process and some way of capturing the kernel log when booting to determine where the error occures that traps the phone in a bootloop.
AnyTimeTraveler said:
I am able to follow instructions.
Thank you very much.
I followed exactly the same procedure that has worked many times when switching between custom ROMs.
Also, the phone has a perfectly working version of Ressurection Remix installed at the time my frame broke and it did get stuck in the same bootloop after replacing the frame, even thogh the software was exactly the same.
I am looking for help analyzing the boot process and some way of capturing the kernel log when booting to determine where the error occures that traps the phone in a bootloop.
Click to expand...
Click to collapse
Dear Mate..
Have you solved your problem? I have same problem after transplating N900 frame.
Sorry, I gave up, since I dearly needed a working phone and bought a OnePlus 3 cheaply from ebay second hand. It's been working like a charm and I threw the note into my museum after I softbricked it for the n-th time and couldn't get it out of a bootloop that didn't leave me time to go into Fastboot.
Sorry friend, but I can't help with this.
after reading a lot of similar threads, seems like the hardware is the cause of us not able to update to higher versions of twrp(& custom roms)
I’ve tried looking for solutions online, but to no avail I can’t seem to fix by myself I have recently installed LineageOS 16 , been using it for months until recently it started to slow down, and die down what i mean is the booting process takes time and after booting there is some random crashes and it reboots , I was able to solve the problem using TWRP by wiping out the cache and resetting back to factory settings, but it was taking so long to boot after and then I decided to flash it once again, started from scratch and it worked for some time until it crashed once again leaving me to unfixable bootloop, it stays on LineageOS logo, then screen dims and then just bootloops, so i decided to flash the STOCK ROM using odin which apparently worked It booted and the process was painful because every boot im doing it got slower and slower until it would be stuck at Samsung Logo and then reboots once again, so I reflashed it once again and when it booted, I was bombarded by system apps not reponsing properly, icon like ‘System UI has stopped’ and then most of the In-built app would do the same and it crashed this time, this time when it booted it is stuck to samsung logo, so i tried wiping the cache and formatting data on stock recovery and it is still stuck on boot-loop, if lucky it goes to samsung logo and just literally in that state forever, i left it for hours and it is still the same. and then when i tried booting to stock rom there was a message below that says (dm-verity verification failed), I googled it and it is a cause for tampering system files and I just couldn’t get to work it out and find a proper solution. I hope you all can help me out. Every-time i try to flash the stock rom the message is , (Installing system updates, error, goes to recovery then it has the problem below) If anyone has encountered the same problem, or has a solution I would appreciate it. Thank you.
Samsung Galaxy Note 4 (SM-N910C) treltex
A dm-verity (device mapper verification) is most likely related to a DRK (device root key) fail as well. Contrary to popular belief, flashing the Samsung official factory firmware does not fix all. As I'm sure you have already come to realize nite even flashing a previous nandroid backup resolves the issues.
There are many YouTube vids of fixing dm-verity but the comments are mixed. Some recommend using 4files with and additional file in the pit (partition information table) but that is also very risky and you could wind worse off than you already are.
Your best bet is to flash a "no opt encryt .zip" and follow the introductions. If this is successful you will need to flash the .zip with every no rom or you'll get dm-verity error. The .zip is not a permanent fix but more like a patch, so to speak. The link below is for general info and I can't vouch for the downloads provided from the site. Its best to download your .zips from XDA.
https://www.androidinfotech.com/no-verity-opt-encrypt-versions/
https://www.google.com/search?ie=UT...e=android-browser&q=xda+no-verity-opt-encrypt
There is also a force encrip .zip you could look into. Good luck
Thank you. I hope this fixes my problem.. But where do I flash it through odin or TWRP??
I tried flashing the zip i got error 1
Mr. JAVI said:
A dm-verity (device mapper verification) is most likely related to a DRK (device root key) fail as well. Contrary to popular belief, flashing the Samsung official factory firmware does not fix all. As I'm sure you have already come to realize nite even flashing a previous nandroid backup resolves the issues.
There are many YouTube vids of fixing dm-verity but the comments are mixed. Some recommend using 4files with and additional file in the pit (partition information table) but that is also very risky and you could wind worse off than you already are.
Your best bet is to flash a "no opt encryt .zip" and follow the introductions. If this is successful you will need to flash the .zip with every no rom or you'll get dm-verity error. The .zip is not a permanent fix but more like a patch, so to speak. The link below is for general info and I can't vouch for the downloads provided from the site. Its best to download your .zips from XDA.
https://www.androidinfotech.com/no-verity-opt-encrypt-versions/
https://www.google.com/search?ie=UT...e=android-browser&q=xda+no-verity-opt-encrypt
There is also a force encrip .zip you could look into. Good luck
Click to expand...
Click to collapse
I tried flashing the zip file in TWRP after installing the stock rom, and I got a Error 1 code
kenesuuu said:
I tried flashing the zip file in TWRP after installing the stock rom, and I got a Error 1 code
Click to expand...
Click to collapse
Try this, read threw the entire tread, follow the instructions. I'd alsoblike to add dm-verity and drk are some of the most difficult to solve, at least in my experience. Furthermore, I would highly recommend making a nandroid backup of all your partitions, especially EFS, boot. I'll see if I can find the no opt encrypt .zip in the meantime. I believe it was 6.0 or 6.1 .
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Error 1
https://forum.xda-developers.com/galaxy-s7/help/error-installing-verity-opt-encrypt-zip-t3436385
scroll down to
JUST WANT TO DISABLE VERITY/ENCRYPTION
https://www.google.com/amp/s/forum....azyflasher-tool-flashing-custom-t3549210/amp/
read threw the rest of the thread.
I don't believe you'll have any success on pure stock firmware. Chances are you'll need to flash a custom kernel for your specific device and/or root package. Unfortunately, theres no one size fits all when it comes to dm-verity or drk.
there are some instructions how to install twrp or lineage on nnthe samsung galaxy a20e. it took me a while to manage it, for one part because it seems sometime i did not do everything exactly like it was described (old fault of mine...) sometimes i found some explication in another instruction.
this is why i post my experiences, to encourage those who also struggle with problems, don't hesitate, sometimes it only takes a bit longer, but also because some things i still don't understand, maybe somebody can explain me what happened..
naturally, firsty of all i first had to install twrp. so i searched for instructions and found some, including liks to download the twrp.tar for my model. some of them i was able to flash by odin, but when i then restarted the phone it only showed a black screen with some pink in the middle, with some fantasy i could read a slight samsung or samsung a20 in it. this happened when i tried to restart in recovery to flas disable-dm-verity, also when i tried to restart direct to system. with all the attempts i got very experienced in flashin back stock rom...
then i found a working recover after restart to recovery i got my twrp screen and was able to flash the no-dm-verity or magisk.
so next i tried to flash the lineage (unofficial lineage 17.zip) but always got the message invalid zip format. tried to unzip and zip again but no way. so i thought i might get lucky with adb sideload, entered the twrp advanced and clicked adb sideload, the screen told me starting adb sideload but the phone could not be detected by the computer. the computer detected it when switched on or in fastboot, so it seems the sideload did not really start.
so i searched the interenet for roms because i really wanted to get rid of google and a million of apps in the stock that i don't need. i found the links to andyyans gsi and several other zips.
as i was not used to the gsi installation i thought i better stick on what i know and tried to install another zip. but most of the time i got the invalid zip message or the zip is for another phone although i downloaded it for the a20e. but then twrp accepted the crdroid.zip (eureka) i downloaded, i was very happy, after the instalation was finished i restarted the phone and the screen went black, turned off and it seemed not pressing to download, to recovery or to start changed anything. i also tried with pressing vol up, vol down and conecting with computer but also no downloadmode started. so i pressed very long always several buttons and after a while the phone vibrated by pressing long vol down and power, but no screen. after it vibrated sometimes like this i turned to vol up and power, it vibrated again and finally twrp started. although the phopne was fully charged when i started the process, it now had only 8% battery.
so i charged the phone again, flashed the stock rom and twrp to try again to find a solution. at this time i also found an instruction that explained why after flashing twrp the system can't recognize the folders (downloads, music... ) and only gives them combinations of letters and ciffers, i have to decrypt it in twrp, wipe, format data, yes and this problem is solved. i don't know it happens always and who made the instructions to flash twrp thought this is common knowledge but in the first innstructions i read it was not mentioned.
i tried again to flash zips and now got a funny eroor message from twrp, unable to zip, this zip is for a20 but this phone is a a10. i tried another zip, the installation started and in the text i could see that it was for a10... so somehow twrp was sure to live on na a10, how could this be??? i thought maybe the twrp was for the a10 (it was a 3.4.x), so i again downloaded a tar directly from the page of twrp for the a20. but when flashed this twrp (3.5.x) and tried to restart to recovery (or to system) the phone was still in downloadmode and refused the custom rom. i had to flash back to stock, then flash again the twrp3.4 that thought my device is a a10, then i could flash the new twrp3.5 i was sure it was from the original site and for my device. i don't know the 3.4 was patched, i got the downloadlink from one how-to-site, but i did not read anything that it was patched...
but after testing all the zips that did not work, and also with the new twrp i was not able to sideload i decided it is time to learn how to handle the xz. so i extracted first the lineage 18, installed it by clicking install image (after wiping) but again the phone turned black and i had to press a while to get twrp restarted and the battery again was nearly down.
the same process worked with the lineage 17, so this is what is now innstalled. both where the correct ab versions, i checked before with treble info what version i need.
so, can anybody explain me
-what happened with my battery when the phone turned to apparently death?
-why could twrp think my phone is a a10, would a twrp for a10 work on my phone?
-is it possible that the sideload feature does not work on this phone?
¡¡¡and many thanks to all those who upload roms and instructions so people like me can make their phones a bit more like they want them!!!
The first time I flashed my A20e (SM-A202F) had the same problems with finding the right TWRP. I cannot answer your questions, but I can tell you what I do.
Beforhand: unloock the bootloader. Upgrade to the latest Samsung firmware. Download AndyYan's 18.1 LineageOS GSI arm64_bvS. Thought arm64_bvS-vndklite can work as well, I found that bvS has less bugs.
After installing the Samsung drivers and the adb stuff on a PC with Windows, I install Odin and flash with Odin the attached TWRP (AP), while phone is in Download mode.
I then go to recovery (TWRP) and if the folders and files are encrypted, I format, then yes. I wipe 4 things: dalvik, catche, system and data.
I then move the GSI image file inside the zip (not the zip) by drag and drop on my PC. Then in TWRP I click install, select image, not zip, select system and flash. Then I reboot to system.
I never had any problems with this installation process. The bvS has a bug with the Lineage music app, but simply install a local music app, such as Musicolet or AIMP from the Aurora Store (from F-droid).
On the camera side I haven't seen any app that significantly improves photo quality. My recommendation would be FreeDcam from F-droid. Use it on special occasions, as it tends to heat the phone.