So I messed up big time messing around with my phone thinking I knew how to do something that I obviously didn't!!
So here I am without an imei and could not recover or repair it because for some reason my phone wasn't able to boot into stock and would only work on SM-N920T or C ROMs. Actually worked perfect with lineage ROMs and older. Anyways moving on.... I pulled my efs folder to modify it after reading some post on another web site and I pushed it back, set the correct permissions and rebooted my device.. well that's when all hell broke loose and my note 5 started going A-Wall!!! Some how FRP lock was activated or Reactivation lock (not sure if there is a difference or not?) Then to top it off stock recovery started displaying " DM-Verity failed need to check DRK first ". So unable to flash TWRP to perform a restore , unable to flash any stock modified without getting "FRP LOCK (bootloader, kernel, recovery and so on). I've done almost every worthy post on the first 10 pages of Google and have yet to fix this. Any tips or preferably exactly what to do would make my day and be very appreciated
any luck?
Related
Please could someone help ! I'm trying to unlock my XT1032. I have the correct Sim-Unlock (network unlock) code from my old telco, but... it won't work because the phone is rooted, bootloader unlocked (S-ON) running CM13.
I figured that returning it to a stock build would allow me to unlock the phone, then I could re-root and return to CM13 on my new network.
However..... there are about a dozen guides on returning a Moto G to stock and the first one I tried left the phone stuck on the 'Warning: Bootloader is unlocked' message. Since then, I've tried several other guides and have got nowhere fast. I've been on this for four hours now and the only thing I seem to be able achieve is to get TWRP or CWM recovery on there by flashing from fastboot. Every other image I try either gives 'preflash validation failed' messages, sticks on the Bootloader Unlocked screen or gets it stuck in a bootloop!
I just want to switch networks... Why is this so bloody difficult ?
What Firmware did your XT1032 originally come with? or which Carrier?
Kitkat I think, and it's Tesco (UK).
I subsequently did the OTA update to Lollipop and then.... WHOAAAAA.... hold on... it's booting !!!
I don't know how, or what I've done to get this far, but the only thing I can think of that's changed is that the battery is now at 100% charge. It appears as though it's successfully flashed the 5.1 untouched ROM from http://forum.xda-developers.com/devdb/project/?id=7981#downloads
But, I've tried flashing that loads of times this evening and it's failed everytime.
Having said that it's booting, it's sitting here on the Motorola logo - and it hasn't got that far in the last five hours.... I'll be back shortly !
Update: It worked ! It completed the boot, I put the new SIM in, it asked for the unlock code and this time it worked OK. Now I'm tackling putting CM13 back on it. I think I'll stick with TWRP rather than CWM recovery, as long as TWRP can handle the automatic updating for the CM nightlies.
I have no idea what went wrong there - maybe it was just that the battery had to be at 100% ?? Who knows... Thankfully I doubt I'll be tackling that again !
I don't know if things have changed, but I would be careful with OTA Updates in CM. People have hard-bricked (phone is effectively destroyed) applying updates in this way. I also suggest you avoid official Motorola updates, rather use the factory firmware images available here: (which already include the content of OTA Updates)
[INDEX] Moto G [Falcon][Peregrine] Factory Firmware Images​
Thanks for replying anyway mate. In the end, it's all good now. Unlocked and back on CM13 and on my new network !
Ahhh... not so good after all. The phone reboots every time you try to uninstall an app. I've tried flashing back to CM12.1, the latest stable release, and it does the same, so I've obviously screwed something up along the way.
Could someone help me flatten this thing completely and get it working normally please?
I've tried reflashing loads of times, even tried Cyanogen Recovery instead of TWRP but nothing I do gets rid of this reboot problem.
Can anyone assist please?
OK, so I've followed the procedure detailed here: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510 and flashed the Untouched 5.0.2. EU Stock ROM successfully, but it still reboots when you try to uninstall any app.
Whatever it is that's causing this is not getting overwritten by the flashing procedures I'm using is it ?
HELP !!!!!
@aneng64 - You have not done what I told you to do. Read my post again.
Yes I did... and I still had the same problem. It was only once I stopped trying to flash zips from TWRP and used mfastboot to flash the whole set individually (non-hlos, motoboot etc) that I got it to behave. The issue, incidentally, seemed to be the same one mentioned elsewhere here that also causes settings to crash when you try to go into settings, security.
Once it was stable with a stock ROM, I was able to flash CM13 again and it's now sorted. Thanks for your help anyway.
I have an HTC One M9 (Sprint) software version 2.11.651.19 (OPJA2) with Android v5.1
Within the last couple months I unlocked the devices bootloader, and rooted it. Last night I left the phone under my laptop and I'm thinking it got way way way too hot, somehow the thing is still alive, however when I went to turn it on in the morning, I had no wifi or cellular capabilities. At first I assumed this was a hardware issue, however I then unrooted the device on a whim, and this fixed it (Until I turned it off again, to my dismay).
I'm thinking somehow my phone overheated (Which explains why my battery life won't go over 47%) and somehow my flash memory must have been corrupted because I can no longer boot into recovery mode, which is my serious catch 22. Since I figure this is some issue related to my firmware, which I would LIKE to reflash (This is my goal here). To my dismay, in order to flash a stock RUU or firmware to the device, you must have your bootloader relocked. However in order to relock your bootloader you must have root, and like an idiot I unrooted it. I can't reinstall SuperSU through my TWRP recovery because my phone refuses to boot into recovery mode. I attempted to re-flash TWRP to the device through download mode, the flashing is completed successfully, however I still cannot boot into my recovery. To break it down simply:
-Want to reflash stock firmware
-Must have root to reflash stock firmware/RUU
-Don't have root because I uninstalled it
-Can't re-root because my recovery is corrupted
-Can't re-flash TWRP (Already tried and it's not working)
-Can't re-root because I can't flash TWRP
-Can't reflash stock firmware because I can't disable it with root
Regardless of this I attempted to use adb and echo to relock the bootloader however instead of getting # I get $, so I'm not really able to do this either. Is there ANY way I can repair my recovery, has anyone ever run into an issue like this before? Or am I just completely screwed, hahaha.
Do you think I might be able to reflash Android V5.1 to try and fix the corruption and then maybe that would allow me to get into recovery mode so I can flash Super SU so I can at least factory reset my device with TWRP, or possible reload stock firmware and factory reset from there?
Thanks guys for any help you can provide.
*EDIT
If anyone wants to provide any advice great, but for now I'm going to try using HTC Sync Manager to load Marshmallow (v6.0) onto the HTC and see if this may allow me to actually get into recovery mode. Downloading the file from here: *nevermind can't post links yet, under 10 posts, you can find it on HTC's website* (This is for the HTC One M9, Sprint) in case anyone else EVER has to run into this awful issue, lol.
Moderators please feel free to update the thread to SOLVED status, I was able to update my phone to marshmallow to resolve the issue. This time around I WILL be backing up my phone, probably not going to root it this time around either, I have like 3 other phones so I'll just root them instead, lol. If you would like the download link I am happy to provide it VIA PM so you can update my OP with the link for the full fix. My phone is able to get wifi and texts now without an issue, unfortunately all my data is wiped but honestly I don't really care!!
Thanks everyone!
Good job on solving your issue.
If you have further questions or want to help out others, you can do so here
http://forum.xda-developers.com/sprint-one-m9/help
http://forum.xda-developers.com/sprint-one-m9
Thread closed
Hey Guys,
Long story short, I had my Sprint Note 5 rooted a while ago! due to some apps screwing me over and not allowing to use them due to being rooted I unrooted (via supersu)
Realized ever since I rooted my battery was totally crap and figured after I unroot it would help (it didn't) read about how it trips the Knox and it affects the deep sleep of the phone (thus **** battery life)
I read on here to just load a kernel in order to fix the deep sleep issue. I've rooted and loaded kernels before on other phones (no issues everrrrr).
When I looked up the TWRP version to use and flash via Odin it said successful. Phone restarted and it never came back up again. I downloaded literally all of the TWRP versions they had on their site, flashed all of them via odin and none of them would get me out of the boot loop. I got completely screwed and had to load a stock firmware from that sam site to get my phone working again. Everything was completely lost on my phone. pics that were never backed up
Due to that, I have been totally hesitant to try this again as that was the only way to fix my phone. I am willing to try again but really want to go into this prepared and have it be a smooth process ( I already backed up ALL of my files on my computer) I don't really care for TWRP or Kernels but I just want to fix the stupid deep sleep issue. I read somewhere on here that people having bootloops from twrp on note 5s was due to not being rooted first? I've also seen (as I did this almost 8 months ago) there are new TWRP versions since then, but afraid to even do those.
Is there a solution I can do to just fix the damn deep sleep issue? phone literally last 2-3 hours idle. Willing to donate via paypal to someone to help walk through it. This is a sprint variant note 5
thanks in advance
Let me explain, I can get into the bootloader, I can get into and flash recovery if needed, I can flash custom roms just fine and the stock rom (even on Beta currently) however I am having issues. Certain roms I couldn't get DHCP from Wifi (it all used 192.168.10.x for an IP usually .20) so it never actually got DHCP or looks to even request DHCP.
I have a message when I boot the phone up as well "SMT Download Failed, Please check your download flow is right". This stays on the screen longer if I do not unlock my bootloader vs locked.
I also am getting a notification inside Android that says "NV Backup Warning - Dynamic Partition Invalid"
Auto Rotate does not work on any rom and looks like GPS or Sensors has completely **** the bed to so maybe the vendor partition is shot?
This is all started after I was going to flash dual boot TWRP, I never flashed it from the TMP folder. I then flashed LineageOS 17. Checked the part table and it looked wrong so I did the manual recovery (thought the dual boot flash did its thing didnt obviously read it needed to be flashed regardless from the tmp folder). This has obviously broke something. Either way the Part table looks like it should Ive ran the MSMtool with different versions nothing seems to correct this. Hoping someone can help me out here. My gut is telling me I need to run SMT mode on the MSMtool but until I can backup my IMEI info I am hesitant in doing that (QFIL is not allowing me to back up for whatever reason).
Velrix said:
Let me explain, I can get into the bootloader, I can get into and flash recovery if needed, I can flash custom roms just fine and the stock rom (even on Beta currently) however I am having issues. Certain roms I couldn't get DHCP from Wifi (it all used 192.168.10.x for an IP usually .20) so it never actually got DHCP or looks to even request DHCP.
I have a message when I boot the phone up as well "SMT Download Failed, Please check your download flow is right". This stays on the screen longer if I do not unlock my bootloader vs locked.
I also am getting a notification inside Android that says "NV Backup Warning - Dynamic Partition Invalid"
Auto Rotate does not work on any rom and looks like GPS or Sensors has completely **** the bed to so maybe the vendor partition is shot?
This is all started after I was going to flash dual boot TWRP, I never flashed it from the TMP folder. I then flashed LineageOS 17. Checked the part table and it looked wrong so I did the manual recovery (thought the dual boot flash did its thing didnt obviously read it needed to be flashed regardless from the tmp folder). This has obviously broke something. Either way the Part table looks like it should Ive ran the MSMtool with different versions nothing seems to correct this. Hoping someone can help me out here. My gut is telling me I need to run SMT mode on the MSMtool but until I can backup my IMEI info I am hesitant in doing that (QFIL is not allowing me to back up for whatever reason).
Click to expand...
Click to collapse
I'm right there with you. I, too, tried to flash the dual boot TWRP and somehow after it didn't work and I was trying the recovery steps in that Github I screwed up my partition table. I just used the patched MSM tool to flash the Tmo brick recovery and while it booted it is showing the same error. Really hope this is fully recoverable.
Hi all,
Before you jump at me telling me I haven't searched the forum, I DID and I couldn't solve my issue even with these solutions. To get you up to speed on what exactly I did.
Briefing (not very important):
I was doing my own business and I was free, I use my phone daily and it served me well. But I noticed that the last security patch I got was on 2020 and got me thinking. Why not just use custom ROMs to update my phone and get a year or two from my MIX3 (2018). I just recently flushed my brother's phone (Samsung) with a custom ROM and I liked it. I already installed TWRP 3 years ago on my brother's phone and I just had to install a zip file and boom new Android 12 on a 2014 phone.
The problem:
after reading here on the forums, it seemed that it is more complicated to do. I'm up to the challenge, I have done it before and the reward is worth it.
+Unlocking the Bootloader
this was a bit easy other than the connection issues but I got it unlocked eventually. (use the QR code to sign it. it is much easier)
I had an issue where after unlocking the bootloader the phone didn't allow me to install TWRP and do a backup, it immediately went into erasing the entire phone.
+Installing TWRP
I downloaded the files from TWRP website and everything was smooth other than the Mi Recovery popping every time I restart (install Magisk to plant TWRP then remove it if you don't need root)
+The downhill
after restarting, the phone worked fine I installed all the apps and restored everything. Afterward, I noticed that the camera does not work. It gives me an error. I reinstalled TWRP again since it was reverting to its Mi Recovery and I think here was the problem I flashed the recovery.img into the boot partition by mistake (I didn't notice at first) but after going back to the command I saw I made a mistake and reflashed the recovery with recovery.img and installed the Magisk and everything was ok. At the initial start, the SIM and the WIFI are not working.
after several attempts at reinstalling different flashable stock ROMs, I saw that the issue is consistent. I read online that you have five .img files that control the different parts of your phone. I got tired and decided to reflash the stock ROM via the Mi flasher and get it back to stock.
Even after flashing the stock ROM, I'm still having the same issue.
I reflashed the modem.img in the modem and still wifi and sim card are not working
I read that some phones have an A/B partition and my phone does NOT have it.
I'M AT A LOSS I CAN NOT FIX IT. IT'S BEEN 3 DAYS ON THIS AND I CAN NOT FIGURE IT OUT!!
Ok, If anyone was passing by I think I found what was the problem.
First, check if your problem matches mine. Go to Settings and check your IMEI. Or just dial *#06# ,if your phone did not return with a number then you lost your IMEI number.
follow this guide and I hope it helps. this is only for some phones so don't try it, it might break your phone
[GUIDE] Backup, edit and restore QCN. Fixing lost IMEI.
Introduction This is a guide to backup and restore the QCN, and to edit other's QCN in case you lost your IMEI and you don't have a backup of your QCN. There are other ways to do some steps (the most popular is via Fastboot) but I'm gonna...
forum.xda-developers.com