Currently, I'm using TWRP 3.2.1-0 and I managed to get it to flash a ROM only once so far. I've already done some searching on what this error means which apparently just says that it fails checking for the proper make/model of the device so that it won't flash something its not suppose to. Except, I have a ROM for the device...
When I first flashed, I had no choice but to do a factory reset which is really a given anyway. But now... its another story. Trying to flash a an updated LineageOS ROM for instance to the latest nightly for instance, will always result in an Error 7. I don't really want to do a factory reset again if I can help it though, even though I do have two points of backup just in case... Not sure if anyone else is having issues about this or not, but figured I'd point it out for now.
TwinShadow said:
Currently, I'm using TWRP 3.2.1-0 and I managed to get it to flash a ROM only once so far. I've already done some searching on what this error means which apparently just says that it fails checking for the proper make/model of the device so that it won't flash something its not suppose to. Except, I have a ROM for the device...
When I first flashed, I had no choice but to do a factory reset which is really a given anyway. But now... its another story. Trying to flash a an updated LineageOS ROM for instance to the latest nightly for instance, will always result in an Error 7. I don't really want to do a factory reset again if I can help it though, even though I do have two points of backup just in case... Not sure if anyone else is having issues about this or not, but figured I'd point it out for now.
Click to expand...
Click to collapse
Downgrade to twrp 3.1.1-0 and try again...
No dice. Actually this was the second time I tried doing it like that. Doesn't matter which recovery I use be it 3.1.1, or 3.2.1. Both results in the same error regardless. Its like TWRP downgraded after it hit v3 because never once had I ever encountered a problem when I used it back on 2.8.7 (or 2.8.6, I can't recall back when Moto X (ghost) was my main device).
TwinShadow said:
No dice. Actually this was the second time I tried doing it like that. Doesn't matter which recovery I use be it 3.1.1, or 3.2.1. Both results in the same error regardless. Its like TWRP downgraded after it hit v3 because never once had I ever encountered a problem when I used it back on 2.8.7 (or 2.8.6, I can't recall back when Moto X (ghost) was my main device).
Click to expand...
Click to collapse
What is your exact model - what's written on the box and what is the model shown in Settings on your stock firmware (if you remember).
I have a sneaking suspicion that it may not be the exactly same device as ours - E5823, creating a conflict somewhere between Firmware/Recovery. Generally, it should get the device data from prop files but you never know I guess...
Here is what you can try: Install latest firmware for E5823 from XperiFirm in Flashtool and wipe everything. If you don't wipe old files are still going to stay! Also, make a backup of all your stuff so you don't lose it. There are guides how to do it here and what things to not wipe in any case.
The device model is indeed a E5823. This has been reported as such in the official firmware as well.
Currently I don't have any of the official firmware files, and I would like to avoid having to set up my phone again if I can help it; even with a nandroid of my current install handy... Its simply just a pain to get all that done.
The last 2 nightlys don't work properly!! I have clean installed, wiped everything and gone back to stock and tried and tried again and again!! 20180318 is the one that is true!! Try flashing that build!!
TwinShadow said:
The device model is indeed a E5823. This has been reported as such in the official firmware as well.
Currently I don't have any of the official firmware files, and I would like to avoid having to set up my phone again if I can help it; even with a nandroid of my current install handy... Its simply just a pain to get all that done.
Click to expand...
Click to collapse
The thing is some partitions get updated only in that way - like baseband for example. Ensuring everything is the latest version and on a clean slate will remove the chance of weird bugs that nobody knows about or can help you with.
Well, here's the irony. I reflashed your TWRP again, twice for that matter.. (I've had random cases where fastboot won't flash it the first time even though it said it did) and all of a sudden it started working. Android never ceases to amaze me when things want to work, and when things don't...
TwinShadow said:
Well, here's the irony. I reflashed your TWRP again, twice for that matter.. (I've had random cases where fastboot won't flash it the first time even though it said it did) and all of a sudden it started working. Android never ceases to amaze me when things want to work, and when things don't...
Click to expand...
Click to collapse
Lol. I have never had that :d and that is from years and years of use and multiple Sony devices...
My guess is a bad flash. That happens rly rarely but maybe u have a bad PC or cable that makes an unreliable connection...
Same thing happened on my old Moto X (2013) on my last system and the new tower I built. For some reason its something to do with fastboot for me, I really don't know. Either that, or its just Windows trying to fight me every which way it possibly can before something wants to work. Its a daily thing I have to deal with, no idea why. Must be my disdain for Windows perhaps..
TwinShadow said:
Same thing happened on my old Moto X (2013) on my last system and the new tower I built. For some reason its something to do with fastboot for me, I really don't know. Either that, or its just Windows trying to fight me every which way it possibly can before something wants to work. Its a daily thing I have to deal with, no idea why. Must be my disdain for Windows perhaps..
Click to expand...
Click to collapse
You might wanna ensure you have the latest fastboot drivers installed under 'Disable driver verification' mode.
Related
Man, I've been out of the Android loop like never before. Probably since right when kit-kat builds started hitting. Anyways, I've been running Venom for months, and just last night my phone started crashing like crazy. Every time it would turn on, just the smallest bit of interaction would make it restart. At some point I must have deleted the ROMs off my storage, because I finally got into TWRP and wiped my data. But couldn't find any ROMs, so LUCKILY I was able to flash through ADB Sideload. Thank god I set up the SDK on this new computer months ago. Anyways, I was able to flash an old SlimBean I had on my hard drive. The DNA is still having issues. Its not restarting every time I do something like last night, but close to it. Any time I get a phone call, I'm able to pick up and talk for 5 seconds, then it restarts. Can anyone help me out here? I thought about wiping internal storage but I'm not sure what problems that will cause. I'm still on JB with an old version of TWRP. The phone is not messing up while in recovery, so I was thinking about flashing new version of TWRP and installing a newer ROM. I don't know if that will help, anyone got any ideas?
ALSO, I no longer have insurance on my device and my screen is cracked. However, it has been less than 12 months since I purchased, so I may still have the one-year warranty, but unless I could get back to stock really easy, I doubt I could pass it off for a warranty replacement.
Does anyone know how I can get fastboot to work? I don't mean in general, I have never had a problem really using fastboot, but when I get into fastboot and check with devices, I'm returning nothing, and I want to flash a new recovery. I know on some ROMs there is a way to turn fastboot on and off, but I'm not seeing anything in this ROM (slimbean-dlx)
Also, just now updating this, but adb won't return a device ID either. I'm not sure why. I believe in recovery it recognizes the device. it did last night. that's how I was able to flash a ROM
lemonoid said:
Does anyone know how I can get fastboot to work? I don't mean in general, I have never had a problem really using fastboot, but when I get into fastboot and check with devices, I'm returning nothing, and I want to flash a new recovery. I know on some ROMs there is a way to turn fastboot on and off, but I'm not seeing anything in this ROM (slimbean-dlx)
Also, just now updating this, but adb won't return a device ID either. I'm not sure why. I believe in recovery it recognizes the device. it did last night. that's how I was able to flash a ROM
Click to expand...
Click to collapse
I would suggest ruu the device back to stock and then try. But I never get my device to show in fastboot and I send recoveries to it all the time. So just flash one at and if it goes you should be able to boot into it and then flash rom.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
thanks I'll try it. Even though it wouldn't show my device in fastboot yesterday, i tried flashing the newest TWRP but it didn't do anything. However, the phone has become somewhat stable. It is still rebooting on phone calls, and the UI is REALLY weird. I've never seen it before, the entire UI is really small and zoomed out. Everything operates like normal, but EVERYTHING is about 1/10 the size its supposed to be. I've flashed two different old ROMs and re-flashed the one I am using now (Beanstalk)
lemonoid said:
thanks I'll try it. Even though it wouldn't show my device in fastboot yesterday, i tried flashing the newest TWRP but it didn't do anything. However, the phone has become somewhat stable. It is still rebooting on phone calls, and the UI is REALLY weird. I've never seen it before, the entire UI is really small and zoomed out. Everything operates like normal, but EVERYTHING is about 1/10 the size its supposed to be. I've flashed two different old ROMs and re-flashed the one I am using now (Beanstalk)
Click to expand...
Click to collapse
Hopefully performing the ruu will fix that. Sounds like a system file may have become corrupted.
Sent from my Droid DNA. If I have helped you in any way please press the thanks button.
I have never had to RUU before. The DNA was my first HTC since Eris, and I've never really messed up to the point of RUU'ing. Should I just download the most recent RUU and run that? Or would I need to flash anything else with it? such as hboot or recovery?? I have the 3.06 radio/recovery/hboot's downloaded. my brain still operates in samsung and moto modes. I have only managed to irreversibly brick one device out of at least 30 and I would not want that to be my daily driver
Maybe the cracked screen is messing with the digitizer and then causes ROM havoc?
---------- Post added at 05:28 PM ---------- Previous post was at 05:26 PM ----------
What Windows version are you using?
maybe, I mean, the screen has been cracked for at least 8 months. I'm using 8.1. unfortunately. I didn't realize when I bought this computer how hard it would be for me to get back to Ubuntu which is my preferred. It is so much easier to do anything with Android on Ubuntu IMO.
Am I correct in reading a comment somewhere that Fastboot drivers don't work on Windows 8.1??? Does this mean I can't RUU?
I think there's some way to get it working on Windows 8, but you would have to search. Most people just find a W7 computer and get it done.
orangechoochoo said:
I think there's some way to get it working on Windows 8, but you would have to search. Most people just find a W7 computer and get it done.
Click to expand...
Click to collapse
yeah I have W7 downstairs I guess I'll just use that. Thanks tho.
Ive posted once already, and even sent a message to someone on the site who's been around longer....here's my problem....
1. I have AT&T
Here is what my bootloader says.....
Software status: Official
unlocked
s-off
CID-1111111
I bootload hbooted FW 3.28.XXX.6 when it came out (ive done it twice now)
I do not have the complete android sdk package, all I have is hasoon's all in one toolkit
im on Captain Throwback's Multirom Recovery ( latest) ( I was using his latest standard recovery, but switched to his MB one a few moments ago)
Here's my problem.......I downloaded both the latest MaximusHD OTA update as well as the MaximusHD rom. I then booted into recovery, and could not wipe anything (all i got were red error messages while trying to do the wipe's)....ive seen this before, so while still in recovery, I dirty flashed MaximusHD rom, but before It completed in Aroma the device automatically rebooted to where it was stuck on the white HTC screen. Now going back to Hasoon's AIOT.....Im able to use fastboot on my computer, the bootloader is reading fastboot usb, and my computer is able to recognize my phone; however, as I said earlier i do not have the complete android sdk.......
main problem: I can not use my phone, as recovery continuously reboots before finishing the wipe process and screen get's stuck on HTC white screen....i have no idea what to do now
OK, no one is helping....ive tried some things, learned a few but this seems to be over my head....can anyone really help ? I managed to get past the white HTC screen by fastboot flashing a new recovery (philz then dees troy version of twrp)....I got a bootable commotio build....I also flashbooted 2.22.401.5, i thought it had fixed everything but in recovery i am getting the following errors.....
unable to mount /cache
failed to wipe dalvik
did I somehow mess up my partitions ? I need to wipe dalvik cache and cache in order to get a working rom on this damn phone.....
The issue has been fixed....
jxcorex28 said:
The issue has been fixed....
Click to expand...
Click to collapse
Please post the solution (for possible info for others) and mark the thread title [SOLVED].
In any case, glad you sorted it out. I would have tried to help, but I'm usually not on XDA on the weekends.
Couple things:
Sounds like you got some kind of adb environment running on your own. But this is one of the reasons I advise against toolkits. They put you in the position to screw up your phone; but don't arm you with the proper tools and knowledge to get out of those jams.
Also, I don't recommend international firmware (3.28) if you are using AT&T as your carrier. You'll likely encounter some reception issues, as the AT&T band support is built into the radio firmware. Although since you are already there, I'd be curious to hear your experience on the 3.28 firmware.
redpoint73 said:
Please post the solution (for possible info for others) and mark the thread title [SOLVED].
In any case, glad you sorted it out. I would have tried to help, but I'm usually not on XDA on the weekends.
Couple things:
Sounds like you got some kind of adb environment running on your own. But this is one of the reasons I advise against toolkits. They put you in the position to screw up your phone; but don't arm you with the proper tools and knowledge to get out of those jams.
Also, I don't recommend international firmware (3.28) if you are using AT&T as your carrier. You'll likely encounter some reception issues, as the AT&T band support is built into the radio firmware. Although since you are already there, I'd be curious to hear your experience on the 3.28 firmware.
Click to expand...
Click to collapse
Im not exactly sure what went wrong in the first place. I never pulled a logcat (from an app or through adp) since the problem no longer exists it looks like I never will unless I go through another similar thing. I wish I did know because it's killing me to know. I wasnt on 3.28 for long maybe a few days, but for the times I was
a. the reception in tuscaloosa, alabama where we have 4G LTE everywhere gave me a decent signal
b. I didnt notice a battery drain compared from other firmware bands
I have flashed atleast 500 times over a 8 year period on 4 different android phones, and Ive never once experienced the problem I had 2 days ago. Ive had 2 HTC phones, although, the experience with basebands were similar they were actually very different in every aspect. I had a TMO HTC G1 back in the day ( I had to learn how to do everything back when scripts or programs werent doing the grunt work (root)...
I had a TWRP backup of beanstalk saved (so kiddies, do your backups) that is what saved my ass. I couldnt wipe anything and my internal storage had been wiped and TWRP wasnt recognizing my SDcard. Everything that could go wrong went wrong....I flashed 3.28 (twice), went through 3 different recoveries (Captain Throwback's Multiboot Recovery, Captain Throwback's TWRP, and Philz Touch CWM Recovery). I looked all over for the answers, but none came to my rescue. It was ultimately finding that backup that saved me.....
I actually had to repartition my computer's hard-drive and reinstall windows 7 home edition, so I had to start over with practically everything...Im not going to use toolkits anymore. As you said earlier, it's just the easy way out. You wont learn anything about how to use ADB or Fastboot (although I applaud the one's who make the scripts or toolkits for those of us on the go).....
P.S.......If I can ever manage to break away from my dueling school schedule and my other priorities in life I plan on learning more about starting from the ground up and building roms, and not just throwing a few things together in the kitchen.....
While my mind is fresh, which linux distro would you recommend for a dual boot machine ? Im currently on windows 7 home edition
jxcorex28 said:
I wasnt on 3.28 for long maybe a few days, but for the times I was
a. the reception in tuscaloosa, alabama where we have 4G LTE everywhere gave me a decent signal
b. I didnt notice a battery drain compared from other firmware bands
Click to expand...
Click to collapse
Yeah, I'm going to pull back on my previous statement that "3.28 will likely cause reception issues on AT&T's network" to instead say "may cause issues". And feel free to try it at your own discretion.
Reason being, I've seen maybe 3 reports now of this firmware working ok on AT&T, and no reports to the contrary so far.
Although, when folks tried the 2.22.401 "international" firmware on AT&T, there were several (even numerous reports) of signal issues, even NO SIGNAL. No reports of this so far on 3.28, so I'll be cautiously optimistic for the time being (until I see reports otherwise). Haven't personally tried it, and not sure I will as I don't really have time ATM to mess around with the possibility of signal issues or no signal.
jxcorex28 said:
I couldnt wipe anything and my internal storage had been wiped and TWRP wasnt recognizing my SDcard. Everything that could go wrong went wrong....I flashed 3.28 (twice), went through 3 different recoveries (Captain Throwback's Multiboot Recovery, Captain Throwback's TWRP, and Philz Touch CWM Recovery). I looked all over for the answers, but none came to my rescue. It was ultimately finding that backup that saved me.....
Click to expand...
Click to collapse
Did you try fastboot erase cache before trying to re-install recovery, or a different recovery? I've seen this simple step alleviate some pretty drastic issues with recovery.
---------- Post added at 10:41 AM ---------- Previous post was at 10:38 AM ----------
jxcorex28 said:
While my mind is fresh, which linux distro would you recommend for a dual boot machine ? Im currently on windows 7 home edition
Click to expand...
Click to collapse
I can't speak personally, I'm not a Linux PC person. But my friends that are, seem to split among various distros: Ubuntu, Kubuntu, and Arch. One friend that is a particular Linux aficionado is on Arch, and said he was very happy with it.
I did...I also tried fastboot -w...to no avail...the past few days I've been learning more about adb and fastboot commands...
I've heard a majority of users tend to swing towards Ubuntu. I might take a look into it...
jxcorex28 said:
I did...I also tried fastboot -w...to no avail...the past few days I've been learning more about adb and fastboot commands...
I've heard a majority of users tend to swing towards Ubuntu. I might take a look into it...
Click to expand...
Click to collapse
Id highly rrecommend Linux Mint 17 Qiana MATE Edition .I use it with Windows 7. It is my favorite Linux OS. Not to mention that its perfect for Linux beginners.
That info would of been great a few days ago, but my laptop is screwed up now. Earlier I tried logging on,and couldn't because of some kind of remote error near the password field box on win7 HE...So I tried a system restore,and it failed so I f8 into recovery options and try using HP Recovery..everything went smooth into the first boot. I ended up getting a recovery installation incomplete and a 205 UIA failed 3 times. I believe my laptops recovery partition is corrupt,and I don't have a HP recovery disk, a win7 recovery DVD / Win7 recovery USB stick... I found what I need on HPs website, but its 30 bucks...BestBuy GS wants to charge me $69.99 for a diagnostics test and a retail version of win7 cost like 130
Its a 2011 HP Pavilion G-series laptop with windows 7 Home edition. What makes matters worse is I just partitioned the system a few weeks ago by using the recovery option HP makes for their devices...
Everything was great til about 10pm tonight...FML...now I actually gotta go to school to do my damn school work
jxcorex28 said:
Ive posted once already, and even sent a message to someone on the site who's been around longer....here's my problem....
1. I have AT&T
Here is what my bootloader says.....
Software status: Official
unlocked
s-off
CID-1111111
I bootload hbooted FW 3.28.XXX.6 when it came out (ive done it twice now)
I do not have the complete android sdk package, all I have is hasoon's all in one toolkit
im on Captain Throwback's Multirom Recovery ( latest) ( I was using his latest standard recovery, but switched to his MB one a few moments ago)
Here's my problem.......I downloaded both the latest MaximusHD OTA update as well as the MaximusHD rom. I then booted into recovery, and could not wipe anything (all i got were red error messages while trying to do the wipe's)....ive seen this before, so while still in recovery, I dirty flashed MaximusHD rom, but before It completed in Aroma the device automatically rebooted to where it was stuck on the white HTC screen. Now going back to Hasoon's AIOT.....Im able to use fastboot on my computer, the bootloader is reading fastboot usb, and my computer is able to recognize my phone; however, as I said earlier i do not have the complete android sdk.......
main problem: I can not use my phone, as recovery continuously reboots before finishing the wipe process and screen get's stuck on HTC white screen....i have no idea what to do now
Click to expand...
Click to collapse
I had that exact same issue yesterday... Twrp couldn't wipe anything and eventually kept rebooting after 20 or 30 sec in recovery.
I had to download the 1.58 RUU and run that, then flash Twrp back, reroot, then restore one of my backups from earlier in the day.
As far as fw goes, I had updated to 2.22.401.4, had that for a couple days, then updated to the 3.xx fw to install arhd 20.3. I liked it, but decided I love my dirty unicorns rom so decided to go back to the 2.xx fw. I tried to flash renovate 4.5.0, and that's when all the issues in twrp started. From what you're saying, it sounds like the issue could be caused from the fw updates.
How did you end up restoring your backup when they issue happened? I tried to restore mine with fastboot, but it was compressed and I couldn't extract the img files from the win files
I had a beanstalk twrp backup. I'm not 100% sure if I sent you my backup that It would work for you...where did you get the firmware you flashed ?
jxcorex28 said:
I had a beanstalk twrp backup. I'm not 100% sure if I sent you my backup that It would work for you...where did you get the firmware you flashed ?
Click to expand...
Click to collapse
I got it from skulldreamz thread on flashing fw by renaming it and putting it on root of ext SD card
Did you look into the contents of that zip to see if there was a recovery.img or boot.img file ? Those files usually overwrite the custom recovery (ie...TWRP or CWM). There are two ways to correct those red error messages you get in TWRP...
1. by flashing partition-fixer.zip (I have a copy if you need it)
2. By using a terminal emulator,and typing this command...
mke2fs /dev/block/mmcblk0p46
I believe this command is essentially what's included in the flashable partition fixer ( I haven't actually taken a look in that zip,so I could be wrong)...
I haven't had any problems as of late...either I'm starting to get back in the hang of dealing with HTC devices or I'm just lucky...
As stathis,skull, & sneaky pointed out...sometimes the firmware packages contain recovery.img/boot.img that will overwrite existing images. Its best to download whatever fw zip you want and scan these zips for said files. Its OK to delete those files,rezip em and flash. If you didn't remove these images. You would have to fastboot flash recovery name-of-recovery.img after flashing the fw zips
jxcorex28 said:
As stathis,skull, & sneaky pointed out...sometimes the firmware packages contain recovery.img/boot.img that will overwrite existing images. Its best to download whatever fw zip you want and scan these zips for said files. Its OK to delete those files,rezip em and flash. If you didn't remove these images. You would have to fastboot flash recovery name-of-recovery.img after flashing the fw zips
Click to expand...
Click to collapse
With the ones I got from skulldreamz' thread, I believe they were modified bc I didn't have to flash a custom recovery again after I flashed the fw. I never fastboot flashed them, I've always just renamed it 0P6BIMG.zip and put it on the root of the ext SD card
That's probably because skull removes those 2 files before uploading for download. I'm not sure if he does that for every zip....
I'm using an LS990 that I've had since about when they came out. When Stumproot came out I rooted it, and I had installed the original TWRP Bump when that came out, but I've been running the rom it came with (ZV4 I believe, though I cannot check). Nothing had been unusual until today, when I put the phone in my pocket after using it for normal daily stuff, then when I later took it out it seemed to be in TWRP. I had almost never even booted into it on the G3 other than a very few times when I first installed it (I had been waiting for a CM12 that was stable enough for my liking).
No matter what I do, it seems to be stuck in recovery. I've updated to the latest TWRP (2.8.4.0) and that seemed to take just fine. However, when I try flashing a rom, it just flashes like normal, log says it's great, then....reboot takes me back into recovery. I tried the ZV4 base at first, then the ZV6 base, both with and without wiping all the appropriate partitions, but nothing seems to change. I am getting ready to try non-stock roms, but I thought I'd ask here first to see if anyone has any ideas? Any help much appreciated!
(not worried about my data, I had daily TB backups running which uploaded to Dropbox, so it's all saved, willing to wipe anything and everything)
Click "format data" under the "wipe" section this will wipe EVERYTHING so make sure you have the latest twrp then on your computer save a rom. Wipe the phone via twrp and then plug the phone it and wait for either Adb sideload or mtp. Personally I feel that mtp is the best just because you can move anything to your phone. Then just move the rom you want to the root of the sdcard (Every folder will be gone). Then flash it and hope that fixes it but if it dosent you may need to use the lg flash tool (windows) and flash the zv4 files. This will make you back on zv4 meaning restump root reflash twrp. The whole nine yards, just try the twrp thing first and if that dosen't work then do the flash tool. I am not responsible if you listen to me and your device breaks
bucketachicken said:
I'm using an LS990 that I've had since about when they came out. When Stumproot came out I rooted it, and I had installed the original TWRP Bump when that came out, but I've been running the rom it came with (ZV4 I believe, though I cannot check). Nothing had been unusual until today, when I put the phone in my pocket after using it for normal daily stuff, then when I later took it out it seemed to be in TWRP. I had almost never even booted into it on the G3 other than a very few times when I first installed it (I had been waiting for a CM12 that was stable enough for my liking).
No matter what I do, it seems to be stuck in recovery. I've updated to the latest TWRP (2.8.4.0) and that seemed to take just fine. However, when I try flashing a rom, it just flashes like normal, log says it's great, then....reboot takes me back into recovery. I tried the ZV4 base at first, then the ZV6 base, both with and without wiping all the appropriate partitions, but nothing seems to change. I am getting ready to try non-stock roms, but I thought I'd ask here first to see if anyone has any ideas? Any help much appreciated!
(not worried about my data, I had daily TB backups running which uploaded to Dropbox, so it's all saved, willing to wipe anything and everything)
Click to expand...
Click to collapse
Have you tried this?
http://forum.xda-developers.com/lg-...trying-ota-t2907508/post56061720#post56061720
Thanks, I did get it working. I have no idea how, but my data was all still there, despite wiping several times....but the recovery fix is what worked. I also got that lg flash tool setup so hopefully that will be helpful if I run into future problems. I honestly think after all that mess I may try the CM12 roms now, even if they still have some daily bugs, cause I was almost sad to see it boot back up into the LG stock rom...
Thanks again!
I honestly think after all that mess I may try the CM12 roms now, even if they still have some daily bugs, cause I was almost sad to see it boot back up into the LG stock rom...
Thanks again![/QUOTE]
Here is a cm12 rom that is almost perfic: http://forum.xda-developers.com/sprint-lg-g3/orig-development/cyanogenmod-12-beta-ls990-t2958197
It's the one I use everyday and I have seen almost no bugs
So I've been rooting all my devices for a while now. I've been able to figure out many issues, including times where I've accidentally soft bricked my device. I've always loved Nexus devices, and have rooted nearly every one I've had. I've had the 7 (2012), 5, 6, and 9, so I'm not new to this. However, the issue I'm having now is something I've never had before...
I rooted my 9 just a couple of days after getting it, and I was successful. I used the nexus root toolkit, which has always been my go to (and yes, I've made sure to configure my drivers and they all function just fine.) I was running CM12 and 12.1. After some time, I decided to try and go back to stock, due to things beginning to slow down on my tablet. I used a stock image from Google (and ensured it was the right one too) and flashed it with the nexus root toolkit. However, just before doing this, I messed up and instead of doing a normal wipe, I also did a full wipe, taking everything off. I figured reverting to stock could undo my error. After flashing stock through my PC, I became shocked to see the CM boot logo and the build being a CM one. I noticed that gapps were installed already (not sure if they were from the factory image, or from a failed wipe) and they crash any time I attempt to log in with my Google account. TWRP is still installed, so I've tried to do a clean install of CM with fresh gapps and continues to be the same issue. It's like it's constantly being dirty flashed. At this point, I'm probably just gonna revert to stock, but have no idea how. Someone please help!
Sent from my Nexus 6 using XDA Free mobile app
Download a stock image, and flash it manually with fastboot. Toolkits are cool for their ease, but honestly, if you're flashing things, you need to know how to do them manually first, so you actually know what's being done.
Sent from my Nexus 9 using Tapatalk
dictionary said:
Download a stock image, and flash it manually with fastboot. Toolkits are cool for their ease, but honestly, if you're flashing things, you need to know how to do them manually first, so you actually know what's being done.
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
So even if the tool kit uses fast boot and stuff to flash back, manual flashing will be more successful?
I won't say that that'll solve your problems for sure, but you'll know exactly where your problem is.
dictionary said:
I won't say that that'll solve your problems for sure, but you'll know exactly where your problem is.
Click to expand...
Click to collapse
I appreciate it! I'm waiting for an OTG cable to arrive in the mail because the only Windows machine I have is a tablet.. I like Linux and Hackintosh a tad too much on my daily driver, but don't feel comfortable enough using terminal to try and flash through Linux.. But I'll be sure to report my findings when possible!
So just to update, I used the nexus root toolkit and disabled any checks when reverted to stock. It worked, and it seems to have been related to the boot issue CM originally had. Planning on going to CM again soon
This is a Backup of the PH1 ROM's system and modem partitions. This is a Pre-Rooted ROM with the SD Card write permissions fix. This is different from my other post in those two differences.
You will need a custom recovery to install this ROM. (http://forum.xda-developers.com/note...lipop-t3089382)
Always perform the appropriate backups and other steps just in case something messes up. If you are on Lollipop, you should be able to just flash and go without any data loss (except custom system apps), but no promises.
Extract the folder (ES File Explorer or 7 Zipper) to "extsdcard/TWRP/backups/[serial number]" then boot into recovery and restore the image. The easiest way to get this folder is to simply perform a backup first, then unzip this folder next to the one for the backup you just created.
I didn't factory reset prior to this backup because it's just system partitions, so let me know if there's anything weird.
https://drive.google.com/open?id=0B2iEgzRTFjrQa2JEbE1DSE9qNHM
Here's the Odin ROM:
http://forum.xda-developers.com/note-3-sprint/general/rom-odin-ph1-update-t3463178/page1
Here's my non-rooted TWRP ROM:
http://forum.xda-developers.com/not...stom-recovery-rom-stock-rooted-t3449321/page1
Still 5.0 this is probably just a security update
RDF
http://device.sprintpcs.com/Samsung/SM-N900P-SPRINT/PH1.rdf
evilvoice said:
Still 5.0 this is probably just a security update
RDF
http://device.sprintpcs.com/Samsung/SM-N900P-SPRINT/PH1.rdf
Click to expand...
Click to collapse
Yep, just a security update most likely. Looks like some of the stock (Sprint) apps may have been updated as well . The update file was only about 190 megabytes if I remember correctly.
Quick question on updating modem & firmware.. I'm stock rooted ok2, and i dont have this update yet. I am working toward flashing the newly released and highly anticipated DL Modded N5N7 v4 which requires the PH1 updated firmware.
Do I need to ODIN flash the update files from the other PHI ROM thread or can I just do a full wipe and flash this backup with TWRP?
Thanks in advance.
Sent from my SM-N900P using XDA Labs
MeAtKeRtN said:
Quick question on updating modem & firmware.. I'm stock rooted ok2, and i dont have this update yet. I am working toward flashing the newly released and highly anticipated DL Modded N5N7 v4 which requires the PH1 updated firmware.
Do I need to ODIN flash the update files from the other PHI ROM thread or can I just do a full wipe and flash this backup with TWRP?
Thanks in advance.
Sent from my SM-N900P using XDA Labs
Click to expand...
Click to collapse
You can just flash the rom you want and keep your current bootloader/modem. But it's always suggested to keep current with any bootloader/modem, that the OP mentioned. That way if there is a issue with the install, it wouldn't be that.
Sent from my Nexus s using XDA-Developers mobile app
jhunt75 said:
You can just flash the rom you want and keep your current bootloader/modem. But it's always suggested to keep current with any bootloader/modem, that the OP mentioned. That way if there is a issue with the install, it wouldn't be that.
Sent from my Nexus s using XDA-Developers mobile app
Click to expand...
Click to collapse
The preferable answer would have been 'NO' or 'I'M NOT SURE' as a direct answer to my very specific question... as I now have a phone that doesn't make phone calls.
MeAtKeRtN said:
The preferable answer would have been 'NO' or 'I'M NOT SURE' as a direct answer to my very specific question... as I now have a phone that doesn't make phone calls.
Click to expand...
Click to collapse
Hey, I've seen you in a few threads and figured I ask before I made the same mistake. I'm looking to upgrade to DL Modded N5N7 v4 like yourself. I have a exploding Note 7 still and I'm anticipating being blacklisted at some point. As crazy as it sounds I like my Note 3's snappiness and everything else over the 7. My issue is my Note 7 radio gets 4g in my job and my Note 3 radio is 3g or spotty. I'm sure my modem and baseband is outdated and may help being updated
I'm on a older Moars Rom Baseband Nk4 android version 4.4.2. Did you figure out where things went bad. I was thinking of following these instructions http://forum.xda-developers.com/note-3-sprint/general/rom-odin-ph1-update-t3463178 don't want to mess this up.
What did you use and what should you have used?
Thanks
Lyvewire said:
Hey, I've seen you in a few threads and figured I ask before I made the same mistake. I'm looking to upgrade to DL Modded N5N7 v4 like yourself. I have a exploding Note 7 still and I'm anticipating being blacklisted at some point. As crazy as it sounds I like my Note 3's snappiness and everything else over the 7. My issue is my Note 7 radio gets 4g in my job and my Note 3 radio is 3g or spotty. I'm sure my modem and baseband is outdated and may help being updated
I'm on a older Moars Rom Baseband Nk4 android version 4.4.2. Did you figure out where things went bad. I was thinking of following these instructions http://forum.xda-developers.com/note-3-sprint/general/rom-odin-ph1-update-t3463178 don't want to mess this up.
What did you use and what should you have used?
Thanks
Click to expand...
Click to collapse
My mistake was following bad advice and flashing the TWRP Backup of PH1 in the OP of this thread instead of ODIN flashing the full ROM-ODIN-PH1- Update- t3463178.
I was able to get TWRP to restore my backup to OK2. From there I did a full wipe 3x and ODIN flashed the full PH1 update, immediately rooted with CFautoroot and reinstalled TWRP 2.8.7.0.
From there I followed the OP instructions in the DL Modded N5N7 thread which require the ROM, Kernel Cleaner, MVNO Buzbee2, Sprint VVM, and I installed the DL MM UIX Kernel.
The ROM and kernel are both really well put together except my mobile network connection to Sprint has been intermittent... the phone was stuck roaming and was connecting in spurts with Verizon, sprint, or the network was unavailable.
I just dirty flashed the Rom, Kernel, and MVNO fix an hour or so ago and the APNs seem to be sticking now. We'll see.
I have three Note 3's and each has its own quirky 'personality'- not especially playing nicely with most of the Port ROMs available these days. Hope this answers your questions and helps someone else trying to keep their Note 3 thriving.
MeAtKeRtN said:
The preferable answer would have been 'NO' or 'I'M NOT SURE' as a direct answer to my very specific question... as I now have a phone that doesn't make phone calls.
Click to expand...
Click to collapse
I am not trying to start any trouble, but from reading your comment it seems you are suggesting I gave you bad or wrong advice. So I want to explain myself just in case it was a misunderstanding. All roms are capable of being flashed with older bootloaders and modems. But the proper thing to do, is to always be up to date with all bootloader/modem files. This way you will not run into any problems. Now I didn't mention anything about flashing the OP'S twrp backup method. I figured you may have been experienced enough to flash these BL/modem files from a source like sammobile. Then proceed to flash your rom of choice. As you experienced you lost your signal. It may have been a few reasons why this happen. 1. The way the OP mentioned to flash wasn't meant for your phone. Every phone response differently. 2. The rom for whatever reason can only be used if you dirty flashed over your current system. This will not be the only time you may have to do it this way. So instead of being sarcastic with your reply, maybe try and ask the one who is helping you to explain themselves more. We are all here to help each other, and by no means was my response to your question was meant to harm your phone.
Sent from my SM-N920C using XDA-Developers mobile app
jhunt75 said:
I am not trying to start any trouble, but from reading your comment it seems you are suggesting I gave you bad or wrong advice. So I want to explain myself just in case it was a misunderstanding. All roms are capable of being flashed with older bootloaders and modems. But the proper thing to do, is to always be up to date with all bootloader/modem files. This way you will not run into any problems. Now I didn't mention anything about flashing the OP'S twrp backup method. I figured you may have been experienced enough to flash these BL/modem files from a source like sammobile. Then proceed to flash your rom of choice. As you experienced you lost your signal. It may have been a few reasons why this happen. 1. The way the OP mentioned to flash wasn't meant for your phone. Every phone response differently. 2. The rom for whatever reason can only be used if you dirty flashed over your current system. This will not be the only time you may have to do it this way. So instead of being sarcastic with your reply, maybe try and ask the one who is helping you to explain themselves more. We are all here to help each other, and by no means was my response to your question was meant to harm your phone.
Click to expand...
Click to collapse
No misunderstanding here... I asked a specific either/or question directly related to the thread topic (twrp custom recovery version) and you either misunderstood my question or decided it required an answer other than a 'yes or no' As a result of your longwinded answer, I lost several hours working through how to get a signal back on my phone. Was pretty annoying.
MeAtKeRtN said:
No misunderstanding here... I asked a specific either/or question directly related to the thread topic (twrp custom recovery version) and you either misunderstood my question or decided it required an answer other than a 'yes or no' As a result of your longwinded answer, I lost several hours working through how to get a signal back on my phone. Was pretty annoying.
Click to expand...
Click to collapse
I never knew giving someone detailed information was a problem. It's funny how I never had an issue with the install, but you did. It seems you lack enough experience to realize a few things. But I will make it a point to never help you again. Whether that's to long-winded or not for you, oh well.
Sent from my SM-N920S using XDA-Developers mobile app
MeAtKeRtN said:
No misunderstanding here... I asked a specific either/or question directly related to the thread topic (twrp custom recovery version) and you either misunderstood my question or decided it required an answer other than a 'yes or no' As a result of your longwinded answer, I lost several hours working through how to get a signal back on my phone. Was pretty annoying.
Click to expand...
Click to collapse
Did you get it all figured out?
I did get it figured out. Wasn't much more than an unnecessary inconvenience that someone else might be able to avoid.
Ok, so something weird...
Im running KK4.4.2 with the NC5 baseband on Sprint.
I upgraded my TWRP to 2.780 to flash the recovery both first time 'dirty flashing' and the 2nd time doing a facory wipe.
I removed the battery after the flash.
When I reboot, the phone stays on the Yellow Sprint screen and the LED pusles blue slowly. So far been doing it for 15 mintues.
What am I missing?
Dave
Unidave199 said:
Ok, so something weird...
Im running KK4.4.2 with the NC5 baseband on Sprint.
I upgraded my TWRP to 2.780 to flash the recovery both first time 'dirty flashing' and the 2nd time doing a facory wipe.
I removed the battery after the flash.
When I reboot, the phone stays on the Yellow Sprint screen and the LED pusles blue slowly. So far been doing it for 15 mintues.
What am I missing?
Dave
Click to expand...
Click to collapse
Give it 30 minutes? It seriously takes a long time. Are you sure you want to upgrade to lollipop? In just asking because you've been on Kit Kat long after support for lollipop or this phone has long stopped. I'd suggest downloading the latest Odin and flashing that instead, unless there is something here you wanted? I'm rooted on PL1 and have no issues other than my phone being as old as it is and how many times it's been flashed.
evilvoice said:
Give it 30 minutes? It seriously takes a long time. Are you sure you want to upgrade to lollipop? In just asking because you've been on Kit Kat long after support for lollipop or this phone has long stopped. I'd suggest downloading the latest Odin and flashing that instead, unless there is something here you wanted? I'm rooted on PL1 and have no issues other than my phone being as old as it is and how many times it's been flashed.
Click to expand...
Click to collapse
30 minutes? Woah that is a long time. Ok I will give it a try sometime when I go to bed.
I am mainly trying to get the PL1 update and not mess with Odin if I can get around it. I would like to try and port the Darklord Marshmellow ROM and take advantage of built in google assistant
So I thought I would try them. And always get back if I need to but wanted to keep the PL1 modem updates.
I only have one problem with one other phone user... She doesnt always get my texts and I dont always get hers. I dont know if others arent getting them and just dont know but my 1 friend I text a lot so she notices when there is a gap.
Anyways. Just feeling out how I can maximize this phone's performance. NO plans on changing phones anytime soon.
Unidave199 said:
30 minutes? Woah that is a long time. Ok I will give it a try sometime when I go to bed.
I am mainly trying to get the PL1 update and not mess with Odin if I can get around it. I would like to try and port the Darklord Marshmellow ROM and take advantage of built in google assistant
So I thought I would try them. And always get back if I need to but wanted to keep the PL1 modem updates.
I only have one problem with one other phone user... She doesnt always get my texts and I dont always get hers. I dont know if others arent getting them and just dont know but my 1 friend I text a lot so she notices when there is a gap.
Anyways. Just feeling out how I can maximize this phone's performance. NO plans on changing phones anytime soon.
Click to expand...
Click to collapse
I still use my note 3. Granted not for main phone as I switched to iPhone, but I use it every day. I don't really know the hesitation of using Odin, but to each their own. If you did decide to use Odin, I'd flash the ROM, boot it, go to download mode again, flash TWRP, boot recovery (so it sticks and doesn't go back to stock recovery), flash SuperSU, done. You're rooted on PL1. Hopefully you have already backed up your text messages and other various things to either SDCard or something else. I'm not sure if that survives whether you wipe and flash clean or Odin. Depending on provider, that could be your issue with text messages. If you're with Sprint, check that you are on latest PRL. If not, make sure APN settings are correct.
If you're only looking for Assistant, I had it running on stock PL1. XDA did a blog post about enabling it in Lollipop, so once you upgrade, check it out. I couldn't stay on Marshmallow. Being that these are ports and not specifically built for our phone, I ran into issue with every single ROM either not being able to place calls, text (MMS actually), or wireless/data not working. No matter what I changed APN to, I would always have issues. Some do not. I just can't recommend a port when they haven't worked for me. Some roms have been abandoned, which meant if I found one that I could at least handle, it was so outdated that it was unusable (issues had arisen and the developer had moved on so they weren't being fixed). By handling a rom, I mean that after I upgraded to iPhone, I only needed wireless to work (to connect to hotspot) and it not go into a boot loop or crash all the time (some do). Those roms I have no idea if calls or text work because I wasn't using that. A lot have issues with wireless working.
One more thing you can try is to do a flash, wait about 30 minutes. If it still doesn't boot, pull the battery and reboot into recovery. Wipe data and cache and reboot again. It should boot. It'll still take a long time. Make sure you wait the 30 minutes before pulling the battery (it should have finished upgrading your system by then). Do note that first boot from now on will take forever no matter if it's a port or stock. Lollipop and higher take a long time to upgrade. I've only had 1 or 2 roms take around 5 minutes and that's because they were minimalist and without Google apps. The phone does get a little warm and uses a lot of battery, so I'd keep it plugged in.
Please report back if you got it to work and how. Like I said, I still use mine. I still visit this forum every day even though I've had an s5 and an s7 edge. I love this phone. I need to get mine replaced because I've worn it out: broken charger port so I have to make sure the cable is plugged in a certain way and I can't touch the phone while charging, side molding is broken off in places, some of my partitions can't be changed which means the memory is failing (not even Odin flashes correctly anymore let alone custom roms). But, it still keeps on ticking.
evilvoice said:
I still use my note 3. Granted not for main phone as I switched to iPhone, but I use it every day. I don't really know the hesitation of using Odin, but to each their own. If you did decide to use Odin, I'd flash the ROM, boot it, go to download mode again, flash TWRP, boot recovery (so it sticks and doesn't go back to stock recovery), flash SuperSU, done. You're rooted on PL1. Hopefully you have already backed up your text messages and other various things to either SDCard or something else. I'm not sure if that survives whether you wipe and flash clean or Odin. Depending on provider, that could be your issue with text messages. If you're with Sprint, check that you are on latest PRL. If not, make sure APN settings are correct.
If you're only looking for Assistant, I had it running on stock PL1. XDA did a blog post about enabling it in Lollipop, so once you upgrade, check it out. I couldn't stay on Marshmallow. Being that these are ports and not specifically built for our phone, I ran into issue with every single ROM either not being able to place calls, text (MMS actually), or wireless/data not working. No matter what I changed APN to, I would always have issues. Some do not. I just can't recommend a port when they haven't worked for me. Some roms have been abandoned, which meant if I found one that I could at least handle, it was so outdated that it was unusable (issues had arisen and the developer had moved on so they weren't being fixed). By handling a rom, I mean that after I upgraded to iPhone, I only needed wireless to work (to connect to hotspot) and it not go into a boot loop or crash all the time (some do). Those roms I have no idea if calls or text work because I wasn't using that. A lot have issues with wireless working.
One more thing you can try is to do a flash, wait about 30 minutes. If it still doesn't boot, pull the battery and reboot into recovery. Wipe data and cache and reboot again. It should boot. It'll still take a long time. Make sure you wait the 30 minutes before pulling the battery (it should have finished upgrading your system by then). Do note that first boot from now on will take forever no matter if it's a port or stock. Lollipop and higher take a long time to upgrade. I've only had 1 or 2 roms take around 5 minutes and that's because they were minimalist and without Google apps. The phone does get a little warm and uses a lot of battery, so I'd keep it plugged in.
Please report back if you got it to work and how. Like I said, I still use mine. I still visit this forum every day even though I've had an s5 and an s7 edge. I love this phone. I need to get mine replaced because I've worn it out: broken charger port so I have to make sure the cable is plugged in a certain way and I can't touch the phone while charging, side molding is broken off in places, some of my partitions can't be changed which means the memory is failing (not even Odin flashes correctly anymore let alone custom roms). But, it still keeps on ticking.
Click to expand...
Click to collapse
Come back to Android! We miss you!!!!
Yes I am backed up and also have a Titanium Backup of everything so I am pretty much covered... I have even backed up the backups to my PC!
You have much wisdom in what you are saying. I thought I would play around with some other ROM's and see what the potential is.
I hear good things about the Darklord Reborn by Midevil and JCorderno so thought I would investigate.
I am not opposed to using Odin, but I was at work, and no access to a computer so wanted to see if I could do the upgrade 'on the fly' since I am already rooted and with recovery.
Man, waiting 30 minutes for a phone to boot sounds like a anxiety attack waiting to happen! But still wanna give it a try.
As to your USB port. Have you thought of going wireless charging? I did and haven't looked back! You can get a wireless charging back and a case that will fit at...
for the charging back
https://smile.amazon.com/Samsung-Ga...=8-2&keywords=samsung+note+3+wireless+charger
for the case
https://smile.amazon.com/gp/product/B00F3KP156/ref=oh_aui_search_detailpage?ie=UTF8&psc=1
Clone Wars....
Just wanted to put out a big THANKS for this.. I broke my Note 3 after 2,433 days (long story) but had bought a stock spare on Ebay last year... Making the switch now, but your PH1 Flashable update is making it super easy!
To let everyone who needs to use this nowdays... you will need to Flash an older TWRP (I used 2.7.8) in order to allow the Modem partition to be overwritten. Then you can flash up to 3.x to load a Android 10 based rom.