Related
So I unlocked this without much trouble, and then when I was attemoting to use adb to flash images to recovery partition, one would just not work, and I stupidly tried to force it, and now it boots and just sits there.
I've seen a different website saying the Q can run Jellybean, and it also has info on getting the stock rom back .. but NO files. I know how to use the damn recovery tools once theyre booted up - those articles were completely useless. I don;t know what else to do. I tried to get the files that argghhhh jad posted to dropbox but they are not available anymore.
Stuck and been trying to fix this for the last 12 hours
EDIT:
Found stock recovery stuff, but I dont think it's going to help any...
Nevermind I suppose
I see that I can try the stock rar file posted for someone else in here to put into recovery, hope it works, I just dont know if the nernel is ok, but I would think so. It stops at the "unlocked"notificaton screen. anyay, yeah. If I get jellybean on instead ill share the info,
I believe you need to fastboot your recovery, not adb. Then you may be able to flash something back on there.
Sent from my XT897 using xda premium
tetrabyt said:
I believe you need to fastboot your recovery, not adb. Then you may be able to flash something back on there.
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
Thanks for the repl! S I actually have been using fastboot because adb for some reason just will not see the device (I checked the version and its correct supposedly). So what I did was take the WWRP rar, pull the contants out and make them into a .zip.and instaled with fastboot flash. The output looked ok:
sending 'userdata' (319120 KB)... OKAY [ 29.814s]
writing 'userdata'... OKAY [ 92.421s]
finished. total time: 122.235s
but what about all the other partitions? I jad done system earlier frok out of the stock zipfile. i think i may just try the entire Stock file insead, or maybe I am missing the fact that I beed to install the kernek into /boot, Any thoughts Thanks much!
EDIT: first im going to fastboot the recovery wit tue TWRP zip file, and try to install it from
I am a little confused, did you manage to get the recovery working? Looks like you were trying to flash the recovery img to your user data partition... Am I misreading your post.
-Saint
Whoaa just saw that. should have unzipped the recovery image and flashed it to the recovery partition with
Fastboot flash recovery recoveryfile.img
Then you can boot into recovery and flash one of the system dumps that these devs have generously posted for when we mess up like this...
Sent from my XT897 using xda premium
tetrabyt said:
Whoaa just saw that. should have unzipped the recovery image and flashed it to the recovery partition with
Fastboot flash recovery recoveryfile.img
Then you can boot into recovery and flash one of the system dumps that these devs have generously posted for when we mess up like this...
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
is this the basic method at present for a stock restore? i was looking at the thread with the files for RSD lite, but i was confused as to whether that was working. thx!
ok so I messed up what to flash from recovery. I had grabbed copies of the system, data, boot, etc for all the partitions thinking i needed to do them all from outside using fastboot,
Herby6262 said:
ok so I messed up what to flash from recovery. I had grabbed copies of the system, data, boot, etc for all the partitions thinking i needed to do them all from outside using fastboot,
Click to expand...
Click to collapse
Ok, the easiest way to get your phone up and running again is to push the newest TWRP from here, put it in your tools folder and push w fastboot:
fastboot flash recovery openrecovery-twrp-2.3.1.0-asanti_c.img
fastboot reboot recovery
Make a backup to your external sd card so that TWRP creates the directory needed to restore the stock system & boot. You should delete this first backup later since it will be broken.
Then download a system & boot image from here, unzip to the /TWRP/BACKUPS/"serial#"/ folder on your external sd. Do full wipes for system, dalvik, & factory reset; then restore Stock from within TWRP. Should be good to go.
:edit:
Just saw that tetrabyt already hit on this, consider this post a more detailed revision.
i must be retardedly doing this the wrong way, i quickly get twrp into recovery and can get in there, and I have the stock photon .zip in 1 big zip and in separate pieces, but how do you get them to the external card.. windows 7 fails to recognize the phone with some message MTP device unknown so I can't transfer it that way ... I dont know. Im about to chuck this thing out the window and be done with it. The whole purpose was to be able to install apps to the sdcard, originally. Only fastboot works from a command prompt, adb doesnt do a damn thing, trying multiple versions of it. I give up
Herby6262 said:
i must be retardedly doing this the wrong way, i quickly get twrp into recovery and can get in there, and I have the stock photon .zip in 1 big zip and in separate pieces, but how do you get them to the external card.. windows 7 fails to recognize the phone with some message MTP device unknown so I can't transfer it that way ... I dont know. Im about to chuck this thing out the window and be done with it. The whole purpose was to be able to install apps to the sdcard, originally. Only fastboot works from a command prompt, adb doesnt do a damn thing, trying multiple versions of it. I give up
Click to expand...
Click to collapse
Do you have an sd adapter or another device you can plug the sd into to transfer from your pc? Does adb fail when booted into TWRP also? Tried uninstalling/re-installing drivers?
Might be able to make a data img you could flash through fastboot, so long as the folder structure was correct... then use recovery from internal storage. Not certain on this: /data/media/sdcard/TWRP/BACKUP/"serial#"/
Maybe someone else can jump in here, this would be my last resort. Use any way possible to get it on external sd first.
-Saint
fallnSaint said:
Do you have an sd adapter or another device you can plug the sd into to transfer from your pc? Does adb fail when booted into TWRP also? Tried uninstalling/re-installing drivers?
Might be able to make a data img you could flash through fastboot, so long as the folder structure was correct... then use recovery from internal storage. Not certain on this: /data/media/sdcard/TWRP/BACKUP/"serial#"/
Maybe someone else can jump in here, this would be my last resort. Use any way possible to get it on external sd first.
-Saint
Click to expand...
Click to collapse
I believe there is a system.img floating around here somewhere.
Check out this thread
http://forum.xda-developers.com/showthread.php?t=1894575
Sent from my XT897 using xda premium
tetrabyt said:
I believe there is a system.img floating around here somewhere.
Check out this thread
http://forum.xda-developers.com/showthread.php?t=1894575
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
Thanks a ton for the help Saint, and others. I finally got it back in working order .. yay! Now to install that powermenu update someone made, and see about making android 4 opeate like the older versions, where you could install apps onto the external SD card. Am I correct in assuming they just F'ed it up by changing the /mnt names, while the software was not updated to accomodate those changes? Why the hell is internal memory now "sdcard" ... so odd. I have a friend whose internal storage is named "USB storage" on his phone. It's USB accessible .. but its a freakin flash card. So odd, and stupid. I really felt like 4.0 was a downgrade, personally. What improved? I see nothing, only things taken away (Im sure the underlying scheduler and thread management/memory mgmt is better, but you know what I mean .. anything visible?)
Herby6262 said:
Thanks a ton for the help Saint, and others. I finally got it back in working order .. yay! Now to install that powermenu update someone made, and see about making android 4 opeate like the older versions, where you could install apps onto the external SD card. Am I correct in assuming they just F'ed it up by changing the /mnt names, while the software was not updated to accomodate those changes? Why the hell is internal memory now "sdcard" ... so odd. I have a friend whose internal storage is named "USB storage" on his phone. It's USB accessible .. but its a freakin flash card. So odd, and stupid. I really felt like 4.0 was a downgrade, personally. What improved? I see nothing, only things taken away (Im sure the underlying scheduler and thread management/memory mgmt is better, but you know what I mean .. anything visible?)
Click to expand...
Click to collapse
Good to hear, glad you got her working again. As for how she runs, definitely snappier than older versions of android. Maybe just hardware, but I still see improvements w the wifes epic running ics, guessing that we will see better results once CM is dropped for this phone.
-Saint
Tried this, still stuck on Bootloader Unlocked Screen. TWRP restores don't seem to work right. I tried restoring an old backup I had of the boot/recovery/system with no luck. Everytime I wiped system/dalvik/cache/factory reset before restore. No errors show up.
So, I can go into fastboot, and I can flash files.
I tried RSD Lite 5.7 with this Zip
It flashes everything until RSD wants me to reboot. Then it reboots and gets stuck on the bootloader unlocked screen.
Any ideas?
[Edit] I flash CWM and found out that I can't mound /sdcard which doesn't seem right...
fallnSaint said:
Ok, the easiest way to get your phone up and running again is to push the newest TWRP from here, put it in your tools folder and push w fastboot:
fastboot flash recovery openrecovery-twrp-2.3.1.0-asanti_c.img
fastboot reboot recovery
Make a backup to your external sd card so that TWRP creates the directory needed to restore the stock system & boot. You should delete this first backup later since it will be broken.
Then download a system & boot image from here, unzip to the /TWRP/BACKUPS/"serial#"/ folder on your external sd. Do full wipes for system, dalvik, & factory reset; then restore Stock from within TWRP. Should be good to go.
:edit:
Just saw that tetrabyt already hit on this, consider this post a more detailed revision.
Click to expand...
Click to collapse
After RSD Lite, it might not have booted up because the system image was removed from the file to make it work. Probably if you flash TWRP after doing the RSD file, and restore Rangerbry's system backup, you might be good..
No Luck.
Just tried this.
Got the following Errors during only system restore:
E:Unable to mount '/cache'
E:unable to mount '/data'
Still stuck on Unlocked bootloader screen.
My emmc might be corrupted I think
I do have sprint insurance. Think they can reflash stock?
yogi2010 said:
After RSD Lite, it might not have booted up because the system image was removed from the file to make it work. Probably if you flash TWRP after doing the RSD file, and restore Rangerbry's system backup, you might be good..
Click to expand...
Click to collapse
coolroman123 said:
No Luck.
Just tried this.
Got the following Errors during only system restore:
E:Unable to mount '/cache'
E:unable to mount '/data'
Click to expand...
Click to collapse
Was that in CWM or TWRP recovery? Just trying to make sure the process was correct, haha. I have only started using TWRP on this device, but i think the 2 recoveries use different backup formats?
coolroman123 said:
Tried this, still stuck on Bootloader Unlocked Screen. TWRP restores don't seem to work right. I tried restoring an old backup I had of the boot/recovery/system with no luck. Everytime I wiped system/dalvik/cache/factory reset before restore. No errors show up.
So, I can go into fastboot, and I can flash files.
I tried RSD Lite 5.7 with this Zip
It flashes everything until RSD wants me to reboot. Then it reboots and gets stuck on the bootloader unlocked screen.
Any ideas?
[Edit] I flash CWM and found out that I can't mound /sdcard which doesn't seem right...
Click to expand...
Click to collapse
Can you boot to bootloader or just to fastboot? There are two control files in that RSD zip, one doesn't flash bootloader, try removing that one and forcing the reflashed bootloader. Then try restoring again. About all I can think of if it successfully flashes the other components... Maybe just restore system and not boot or data?
-Saint
Everything you need is here to return to stock WITH ota update.
http://forum.xda-developers.com/showthread.php?t=2001226
The only thing simple is the belief in simplicity.
Hello everybody, today I have installed twrp 2.8.6.0 for n8000 through odin. for odin the flash was corrected because the program say "pass" but when my tablet have turned on, I haven't cellular signal so I went to settings if there was problem and my baseband is now unknown and in consequence my imei is null/null.
I have tried to reinstall again the twrp but nothing and also I have tried to install the original recovery but nothing, I havent' signal.
What can I do to recover baseband and imei?
I have Note n8000 4.4.2 buid n8000xxudof1. In EFS folder there is all files (nv_data.bin, nv_data.bin.md5)
Restore your backed up EFS folder as per forum identical posts .
I have strong reasons to believe latest TWRP is bigger than portion size that hold recovery and by flashing it you ruined modem partition. It happened to me few times. So do following: find older smaller size TWRP or other recovery like CM or based on it. Find correct modem for your model and region which is flashable in recovery. Boot into your recovery and flash first alternative recovery, reboot into recovery and flash modem. You should be OK and no data will be lost in that way. Flashing just modem in your TWRP will produce boot loop with very high probability and you would need to use flashing tools on PC, so be careful. Good luck and nice weekend.
Sent from my A0001 using Tapatalk
JJEgan said:
Restore your backed up EFS folder as per forum identical posts .
Click to expand...
Click to collapse
I haven't a backup of efs folder because first I installed the recovery and then I have done the root so I haven't the possibility of efs backup, probably in this way I made a mistake
AndriiG said:
I have strong reasons to believe latest TWRP is bigger than portion size that hold recovery and by flashing it you ruined modem partition. It happened to me few times. So do following: find older smaller size TWRP or other recovery like CM or based on it. Find correct modem for your model and region which is flashable in recovery. Boot into your recovery and flash first alternative recovery, reboot into recovery and flash modem. You should be OK and no data will be lost in that way. Flashing just modem in your TWRP will produce boot loop with very high probability and you would need to use flashing tools on PC, so be careful. Good luck and nice weekend.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Ok, I'll try. I have finded an old twrp and now I'll search for modem. Thanks for suggestion
Hello All:
I have been using and tinkering with phones for years now, note 2,3,4 and 5. I say this so you understand I'm not new to fixing usual issues with rooting and flashing custom roms, etc. There may be a solution to this, but I haven't been able to find it after weeks of searching and trying different things.
After flashing Tek's Rom with COJ -> COK my phone gets the "This phone has been flashed with unauthorized software and has been locked..." error no matter what I do. I have completely wiped, formatted, Odin'd stock firmware and flashed and flashed every bit of software I can find, including using at least ten fresh md5 verified new downloads of the firmware, etc. I have tried arter97's kernels including last several versions, and several other kernels I can't remember.
Anyway, when I complete wipe and format, and then Odin flash the stock firmware (COK), my phone never leaves the Samsung Note 5 boot screen. If I flash a kernel, I can get to the setup mode, but I get the error message that my device has been locked and cannot make calls or register my phone on the tmobile network. My sim card works just fine with other phones. I am using it as we speak on a Lumia 950, but I cannot stand not having the spen.
I have tried flashing kernels through philz, twrp, and the stock recovery. I have tried OTG and flashing kernels from the internal SD card once I flash a kernel and get past the setup. Since I use two step verification, and cannot receive texts, it's a real pain to get into my google account.
When I try to login to my Samsung account, it says, "processing failed," each time. Tmobile has been less than helpful. I am at wit's end. Anyone have any thoughts? I'd really appreciate the help.
Thanks.
Make sure you have everything backed up. Odin to stock be sure OEM unlocking is on. Do a full wipe in stock recovery. then try to root again.
steve97ta said:
Make sure you have everything backed up. Odin to stock be sure OEM unlocking is on. Do a full wipe in stock recovery. then try to root again.
Click to expand...
Click to collapse
Forgive me, and thank you for your reply, but I am not sure if I could have been any more clear that I have full wiped, odin'd back to the stock firmware, etc. no less than a hundred times. Not only that, but I have tried COJ, COK, all three recoveries, different kernels, etc. I can assure you OEM unlocking is on, and has been on each and every time.
In ODIN Mode (Download Mode), my phone reads:
Download Speed: Fast
Product Name: SM-N920T
Current Binary: Samsung Official
System Status: Custom
FRP LOCK: OFF
Secure Download: Enabled
KNOX WARRANTY VOID: 1 (0x0301)
RP SWREV: B:2 K:0 S: 0
It does not change much when I flash a kernel or a custom rom, other than current binary to "Custom"
Anyway, I want to be clear:
I have turned on OEM unlocking, no fingerprint lock or any lock mechanism, full wiped through philz recovery, twrp, etc. and ODIN flashed the STOCK firmware from this forum, from Tek's thread, from Sammobile (I even paid the $10.00 to make sure), and I absolutely cannot get my Sim card to register on the network.
I tried again this morning. First, I full wiped and ODIN'd COJ. Then, I full wiped and ODIN'd COJ w/NAND Erase All. I should note that each time I boot to recovery, I get the same old message, "DM-Verity Verification Failed... Need to check DRK first..."
I also get this error when I wipe, "preload checkin... E: failed to mount /preload (no such file or directory)"
I then full wiped and ODIN'd COK. I rinsed and repeated. I still get the exact same errors I mentioned above. The phone sits still at the Samsung boot screen (it does not get to the colored logo screen or the T-Mobile screen, just the black and white) for as long as I will allow it (sometimes hours).
Update:
I have now individually full wiped and flashed the BL, AP, CP, CSC, and PIT files multiple times with no changes. I have read somewhere that I may need to unpack the firmware file itself and remove the cache.img file?
If you are using odin you should only need to put the tar in the AP slot. Are you using the factory note 5 cable? Also what version of odin?
steve97ta said:
If you are using odin you should only need to put the tar in the AP slot. Are you using the factory note 5 cable? Also what version of odin?
Click to expand...
Click to collapse
Yes. I am trying additional methods because, as I have said, I have already tried to do the basic methods of wipe data / internal storage / system / cache /dalvik cache (10x), ODIN stock firmware, rinse repeat.
Yes, I am using the factory cable.
Odin version 3.10.7
I am however having additional issues caused by my efforts. My E:/data partition seems to be missing.
Thanks
er0k02 said:
Yes. I am trying additional methods because, as I have said, I have already tried to do the basic methods of wipe data / internal storage / system / cache /dalvik cache (10x), ODIN stock firmware, rinse repeat.
Yes, I am using the factory cable.
Odin version 3.10.7
I am however having additional issues caused by my efforts. My E:/data partition seems to be missing.
Thanks
Click to expand...
Click to collapse
That happened to me if you have a backup of your efs partition you can restore and it should fix verify your imei that is the same as the one it has on the box on a sticker @Jammol can help in here he is the one that helped me he is good at this kind of stuff and remember to always do a backup i learned from this thing too
This only means your imei is messed up same things that you mention happened to me even that samsung account failed stuff and all it was the imei lol
Sent from my SM-N920T using Tapatalk
Ok, thanks. What happens if I do not have an EFS backup? I may have a NANDROID from TWRP somewhere, but I doubt it.
I know you did a million things.
For me, after I flash stock unrooted thru Odin, I will get bootloop until I wipe in Stock recovery.
I appreciate that, but yes I had also tried that. At this point I think the poster above is correct in that I need to restore the EFS partition. I have read tricks of switching the mount point, and also about using some "magic" tools online. Does anyone know how I can fix the missing partition? Tmobile isn't helpful, and I can't get on the phone with anyone from Samsung.
Also, update: I was able to successfully flash the android 6.0 rom on cokc firmware last night, but it is still giving me the same problems not recognizing my sim and not working as far as registering on the network. I also cannot login to my Samsung account.
I really appreciate the help.
er0k02 said:
I appreciate that, but yes I had also tried that. At this point I think the poster above is correct in that I need to restore the EFS partition. I have read tricks of switching the mount point, and also about using some "magic" tools online. Does anyone know how I can fix the missing partition? Tmobile isn't helpful, and I can't get on the phone with anyone from Samsung.
Also, update: I was able to successfully flash the android 6.0 rom on cokc firmware last night, but it is still giving me the same problems not recognizing my sim and not working as far as registering on the network. I also cannot login to my Samsung account.
I really appreciate the help.
Click to expand...
Click to collapse
Just as cautionary reminder, always make sure that OEM Unlock is turned on before flashing anything whatsoever. Even if you're on a custom rom already. I flash almost daily and I check every single time before I flash something. YOU NEVER KNOW!
You said earlier up that you have a TWRP right? If you still do check it to see if it has a backup of the EFS partition. If you do have the EFS partition backed up, try and remember what firmware you were on. You'll need to be on that firmware when you restore it. In other words, if you were on COKC when you made it, you'll have to be on that when you restore it. Also try restoring it on TekHD rom if you were on COKC when you made the backup. Don't wipe anything, and reboot after the restore. ONLY RESTORE THE EFS, NOTHING ELSE!!! Upon reboot, if you have a fully working phone again, do a factory reset from inside the rom. Once it reboots, if it works still, download his Stock Rooted Rom in post 5. Do a full wipe and flash that, your EFS should not wipe. Once rom is done flashing, reboot and see if you still have a fully working device. If you do, go ahead and try an Odin flash to full stock. Do a full wipe before using Odin.
Jammol said:
Just as cautionary reminder, always make sure that OEM Unlock is turned on before flashing anything whatsoever. Even if you're on a custom rom already. I flash almost daily and I check every single time before I flash something. YOU NEVER KNOW!
You said earlier up that you have a TWRP right? If you still do check it to see if it has a backup of the EFS partition. If you do have the EFS partition backed up, try and remember what firmware you were on. You'll need to be on that firmware when you restore it. In other words, if you were on COKC when you made it, you'll have to be on that when you restore it. Also try restoring it on TekHD rom if you were on COKC when you made the backup. Don't wipe anything, and reboot after the restore. ONLY RESTORE THE EFS, NOTHING ELSE!!! Upon reboot, if you have a fully working phone again, do a factory reset from inside the rom. Once it reboots, if it works still, download his Stock Rooted Rom in post 5. Do a full wipe and flash that, your EFS should not wipe. Once rom is done flashing, reboot and see if you still have a fully working device. If you do, go ahead and try an Odin flash to full stock. Do a full wipe before using Odin.
If you need further help, add me to Google Hangouts [email protected]mail.com
Click to expand...
Click to collapse
Thanks, I'll add you to hangouts. I don't have a backup EFS, for sure.
Possible to fix a corrupt EFS partition without a backup?
Man, I am in the same boat. I do not have an EFS backup. Any help would be appreciated.
I've done it. I am no longer locked out of the network, no longer getting the error, EFS fixed without a backup, Samsung account accessed.
I'll write out the steps and post in a bit. Battery is dying.
Thanks
Do you have the steps to recover the EFS? I've been stuck for few days now and feel it is a crime to exhaust every option as you already figured it out. Thanks for the share either way!
just throwing in my two cents...I have this same bizarre boot loop, Odin not sticking crap. the fact it still says your system is custom tells me it's in the same ball park.
do everything you usually do, then reset twrp settings to default, reboot to recovery, wipe all cache blah blah, then reformat to ext4, repair, resize every partition. to get davlik, select it and system together, then file system to ext4, to get the internal storage, select it with data. then reboot recovery...MOUNT SYSTEM...do it all again...
reboot, let it get stuck at logo...reboot to recovery clear caches, MOUNT SYSTEM, DO IT AGAIN.. just the caches...
you're welcome
you're
er0k02 said:
I've done it. I am no longer locked out of the network, no longer getting the error, EFS fixed without a backup, Samsung account accessed.
I'll write out the steps and post in a bit. Battery is dying.
Thanks
Click to expand...
Click to collapse
It would be interesting to know how you solved this. I just made sure I have an efs backup.
I completely forgot about this thread. I apologize to everyone for the delay.
To recap:
My phone was cellular bricked. It turns out I had a corrupted EFS partition. The way I managed to "fix" the problem was tedious and may not work for everyone.
1. I ODIN flashed the stock firmware multiple times;
2. I erased the data in my Samsung account. I had to do this online through their website. I think this was crucial.
3. During each initial ODIN flash, I selected Phone EFS clear, Phone Bootloader Update, Nand Erase All, Repartition, etc. in ODIN.
4. I then re-flashed stock COJ without selecting EFS clear, Phone Bootloader Update, Nand Erase All, Repartition, etc. I just let it select the normal options.
5. I then ODIN flashed TWRP, and flashed Jovy's ROM after flashing the Stock Modified Kernel.
6. I used the tool inside Jovy's Aroma installer [Fix Corrupt EFS Partition, or whatever it is called];
7. I didn't install any of the Samsung apps.
8. I then installed the ROM.
9. As soon as the ROM booted, I connected to WiFi as quickly as possible and ran through the steps as fast as I could before I gave T-Mobile the chance to display the message that my phone had been rooted and would no longer be able to connect to the cellular network. I logged into my google account and rebooted quickly before anything else happened. This took less than 30 seconds.
10. I went back into TWRP, full wiped and formatted.
11. Back to ODIN flashing Stock COJ.
12. ODIN flash TWRP.
13. Flash Jovy's ROM + Stock Modified Kernel.
14. Restore EFS partition.
15. Install ROM.
16. Finished.
It has been working since the day I posted above.
Try this tool
You might want to verify if Smart Switch tool by Samsung works on your device. I had a problem flashing my note 5 with the oem lock and this program saved the day. Is free and you can google it, I hope it helps.
Sorry, thanks, but no, if you choose to read this thread, you will understand that Samsung (in this situation), including Smart Switch, Kies, and other utilities, not only fail to rescue the firmware, but get in the way of ODIN, require resetting your Samsung account additional times, take up hours of bandwidth, ram, proc power, and gigs of hdd space. At best, Smart Switch is horrible, worthless, and stupid waste of time for those with an actual corrupted EFS partition, no backup, tripped Knox, and the other deets mentioned herein.
Hello,
I have an issue with my phone and any help or insight is appreciated!
I have a Oneplus One. Rooted with TWRP and MultiROM installed. I have two CyanogenMod ROMs installed. One is my primary one where I have all my apps, and another one that is almost empty (has few apps).
Few days ago, my battery drained and I charged it. Then when I turned it on, the phone started booting, passed through the MultiROM window (where you choose the booting ROM), then passed through the Boot animation, and then a screen appears where it says "Preparing Apps x of xxx". After the phone goes through all of my apps (optimizing/preparing them), it shuts down and starts all over again.
This was random. I didn't install a new update or anything. Note, that this only happens with my primary ROM. When I boot to my secondary ROM everything works fine. I had a backup of all my app data (~ 6GB) using Titanium Backup. However, I was running out of space and I deleted the backup from Google Drive few days earlier. I am very unlucky.
I tired the following to fix this issue and nothing helped:
1. Cleared chase and Dalvik chase.
2. Installed a CyanohenMod update. Apparently, my phone wasn't up to date.
3. Drained the battery completely and charged the phone.
4. Booted the phone while charing and while not charging.
I just want to get my apps data back. So is there anyway to fix this issue so that I can boot to my primary ROM?
If not, is there a way to fully backup my apps data in the primary ROM (the one that is not booting) and transfer this backup (install these apps with their data) to another ROM?
I can't back up my apps data using TWRP and save the backup in Internal Storage, because I don't have enough space. Maybe I can back up my apps data to my laptop somehow? Also, if I do a backup through TWRP, will the issue still persist when I do a restore (I am backing up a broken ROM)? I am afraid to do this step because in order to restore through TWRP (after backing up the ROM), I have to delete this broken Primary ROM first due to insufficient amount of space. If it ends up not working I will lose all my data! So I prefer to fix the ROM if possible instead of going through all of this.
Any help is appreciated. Sorry for the long post.
Thank you in advance.
@ali282h
Sorry for the delay and for the issue you are having at the first place.
I read your post completely.
I will answer Your Questions in points:
1)You can take Apps backup , dont worry if the roms works or not.
2)i will suggest you to use a single rom first , dont use multi rom that can make it difficult to analyse the root cause of the bootloop,
3)Use a toolkit called Wug fresh and flash a stock firmware and then check if itss booting correctly or not.If not ???
Follow the 4 step
4)U can boot into the Twrp, then use ADB commands.
Fastboot erase persist
fastboot flash persist persist.img
Again If you have problem You can follow the next step
5)You can type these commands in adb
adb shell
make_ext4fs /dev/block/mmcblk0p15
Report back..... Gudluk
Hello.. I actually ended factory resetting my phone. Thanks for taking the time to write a very helpful answer.
adarsh58 said:
@ali282h
Sorry for the delay and for the issue you are having at the first place.
Report back..... Gudluk
Click to expand...
Click to collapse
Hey thanks for the reply. I am also facing the same issue. Where can I get this persist.img to flash it from fastboot?
This issue keep on popping every week and almost every week I am wiping everything completely and installing new ROM. Kindly help. I am currently using Resurrection Remix 5.7.4 MM. No MutiRom.
Thanks.
i had it, but i dont think it is related to persist as after each update i flash i erase wipe persist folder, tho i did a titanium backup and wiped data/cache/dalvik/system and flashed it all over again.
badboy4a2 said:
Hey thanks for the reply. I am also facing the same issue. Where can I get this persist.img to flash it from fastboot?
This issue keep on popping every week and almost every week I am wiping everything completely and installing new ROM. Kindly help. I am currently using Resurrection Remix 5.7.4 MM. No MutiRom.
Thanks.
Click to expand...
Click to collapse
Hi ali,
Follow this link and get to the post no 8, u will find
https://forums.oneplus.net/threads/afx-zip-containing-persist-img-reserve4-img.198286/
guidoido004 said:
i had it, but i dont think it is related to persist as after each update i flash i erase wipe persist folder, tho i did a titanium backup and wiped data/cache/dalvik/system and flashed it all over again.
Click to expand...
Click to collapse
Ya You may be right :angel::angel:, but correct me if i am wrong
Persist partition is not like other partitions in android like /system,/data,/cache etc.
so integrity checks wont run on it ,results into
"if its get corrupted it will remain corrupted"
in that case we need erase and flash it all over again,
You can do it by typing one line cmd in ur twrp terminal emulator
make_ext4fc /dev/block/mmcblk0p15.
:good::good::good:
LINKS:
http://droid-bug.blogspot.in/2014/10/oneplus-one-boot-loop-0mb-no.html
adarsh58 said:
Ya You may be right :angel::angel:, but correct me if i am wrong
Persist partition is not like other partitions in android like /system,/data,/cache etc.
so integrity checks wont run on it ,results into
"if its get corrupted it will remain corrupted"
in that case we need erase and flash it all over again,
You can do it by typing one line cmd in ur twrp terminal emulator
make_ext4fc /dev/block/mmcblk0p15.
:good::good::good:
LINKS:
http://droid-bug.blogspot.in/2014/10/oneplus-one-boot-loop-0mb-no.html
Click to expand...
Click to collapse
i use commands in the Recovery terminal to do so, as theres not a easy way to do it on the recovery itself
Hello friends, when I flash Combination file, or stock file , my phone boots and hang at start up logo, while I restart to recovery I see this error (E:Failed to mount efs, Invalid Argument)?
Can anyone help?
What have you done ? Trying to root and lost your IMEI ?
If so, then go to recovery and do all of the wipes and format Data. Once done, then just flash the exact same ROM as the one which is already installed on your phone.
TheRealKeyserSoze said:
What have you done ? Trying to root and lost your IMEI ?
If so, then go to recovery and do all of the wipes and format Data. Once done, then just flash the exact same ROM as the one which is already installed on your phone.
Click to expand...
Click to collapse
This steps does not work, I need EFS for A8 2018.
I'm having the same problem, I've tried everything. z3x, Odin , won't even let me flash from sd card. Won't load into Oreo just keeps rebooting. I can get into recovery but does nothing as well as boot loader. I did have a utility im pretty sure was made by FACTORY BINARY that was it's own little OS with a bunch of little tools. I have a sm-a530w flashed with boot loader 4 ugggg. If anyone can help find that utility that will wipe the whole thing and let me flash from scratch that would be awesome. I've tryed miracle, Uni-Android, samsung tools 29.5 and flashing with odin. Lets me flash factory FIRMWARE but still error's out on the "Failed to mount EFS" HELPPLEASE
A quick suggestion you probably tried, but i've had failure at boot in the past after returning to stock via odin if i used home_csc. So, if you haven't already tried, use just csc. No home. On home it does system.img until the end, no user_data . Not sure at all what the deal is but it's all i can suggest. Get 'er goin'!
:Failed to mount EFS
Yes I think I tried that, but at this point, I try again. Any more suggestions would be greatly appreciated. An A8 in mint shape just hurts LOL.