Database Info

Am I screwed? (bricked)

I've been flashing different roms for awhile, and decided to go from OpenEclair to one of the "new" ones that requires the new SPL and radio. Went fine. No problem. Used the new rom for about a week, but really got screwed by a massive bug I found in it today, so I wanted to go back to my OE nandroid backup.
I went to reflash to my original SPL. It was a ZIP, so I treated it like a ROM and used AmonRa's recovery to flash it. Said it went fine. Rebooted, expecting to get back into fastboot and flash my radio.
I can't get into fastboot. All it does is show Rogers then HTC Magic in a boot loop. ADB devices shows nothing, fastboot devices shows nothing. Back and Power doesn't work. Home back and power doesn't work. Vol down doesn't work.
Am I as bricked as I think I am?

Yes, it sounds bricked. The proper method to go from 6.x --> 3.x radios and matching SPL is to use fastboot. You have to flash radio and SPLs in matching pairs, you can only use the update.zip format for SPL when it already matches your radio (ie. 1.33.2005 ---> 1.33.2010 w/ the 3.22.20.17 radio).

I believe you should normally flash radios first as well. If you don't get it fixed id like to buy it, need parts. Anyways, most the time when you can't get into fastboot or anything else, it is bricked. Best bet is to get warranty if you still have it. Unfortunately the new phones won't be rootable yet

its best to follow guides when downgrading/upgrading spl/radio (cursordroids for example) when not knowing completely what your doing.. sorry my friend.. sounds like your phone is now a boat anchor

i flashed a 1.33.2010 SPL with a 3.?? radio and now all i get is the logo screen no fast boot, i can enter debug mode (action button) but nothing else sounds like its bricked, but hey its been fun

to be honest i was in this situation last week after leaving my phone off for a hour fastboot was working

oh this is sounding more promising, see what happens when i get home, i see there have been a few people about that have been in the same situation and got out of it so fingers crossed

unfortunantly none of the above worked, wow after 10 years of flashing **** i finally killed something !!.... mind you i still have to make up the serial cable this weekend and see if i can fix it like that

Oh well, you guys should know better ... radio/spl/recovery upgrade/downgrade is a child play, if you do it with fastboot and in the correct order (radio - spl - recovery).
I just hope you can get your Magic back to life.

yeah i was a little distracted at the time, never mind, im going to boot into the radio bootloader and see if i can fix it this weekend, fingers crossed

ruimoura said:
Oh well, you guys should know better ... radio/spl/recovery upgrade/downgrade is a child play, if you do it with fastboot and in the correct order (radio - spl - recovery).
I just hope you can get your Magic back to life.
Click to expand...
Click to collapse
i have flashed not in that order and never bricked and also i have flash different things like radios in different orders and no brick

Just a (long) update on trying to get the phone repaired...
First thanks to bcrook, KAwAtA and digitaljeff for the prompt replies at confirming my screw up.
Ruimoura, why even post? Nothing helpful, and not even commiserating. "Oh well, you guys should know better ...". I hope someone is there when you make a mistake to rub it in.
Anyway...
This was a Rogers Magic used in the states on AT&T.
Heres what happened if anyone is interested:
I searched the forums and tried every trick I could find, including the gold card method; no luck. To be honest, I'm not sure I did the gold card right, but I tried my best. I even looked into the jtag idea, but it seems like more work then its worth to me, and no one seems to have been successful with it yet.
I then called HTC to find out what a repair would cost. HTC said they don't have that phone in their parts list and can't service it because it is a Rogers phone and they don't work with Rogers. They told me I would have to call Rogers for service.
Called Rogers and explained the situation (carefully; blaming the 911 update ). Rogers lectured me on how dare I take their phone off their network, and that they have no interest in helping me at all and "contacting HTC is easy. Whats wrong with you?". I explained that I contacted HTC and they said to contact Rogers. They said (after some fighting) call this number and then gave me the same number HTC has on their website.
Called HTC again and explained the situation. After checking their parts database, the person I was talking to this time confirmed what the person I previously talked to said. HTC doesn't service the Rogers Magic but he felt, like I, that was kinda crazy and called the repair location directly to confirm. After a bit of time on hold, he came back and said that Rogers phones are serviced through a place called FutureTel in canada, and gave me their contact number.
I called FutureTel and it was a very short conversation. "What store are you calling from?" I Explained I wasn't calling from a store and why I was calling. "We only work with Rogers directly. We won't support you." and they hung up.
I have to say, both times I called HTC the people I talked to were incredibly polite and honestly seemed like they wanted to help. Rogers and FutureTel seemed like they truly resented having to pick up the phone. Maybe its a cultural thing I'm not aware of, but it honestly seemed, from the first word, that they hated talking to me.
So, as near as I can tell, you can't even pay someone to fix a Rogers HTC Magic.
At this point I'm back suffering on my old WinMo phone and desperately hoping that the rumored March 23 release date for the Verizon Nexus One is legitimate since T-Mobile isn't really an option.

Noob root now slightly bricked G Flex 2

Hi all. My new phone was going greatish. It was a little laggy, so thought I would root it and remove some of the preinstalled junk. All went fine no problem.
I removed some of the vodafone (UK) stuff, and all was well. Some time later though, I get a message:
"Unfortunately, the process com.android.phone has stopped"
And now my phone won't find the network and message pops up every couple of seconds. I tried a factory reset, but I suspect this made it worse as I have now lost my backups from Titanium app. The phone is basically unusable as it is due to constant error message and no network.
I have tried to access the recovery menu, but i get an empty robot with "no command".
I have seen some mention of CIDs on other forums but haven't got a clue how to go about fixing it or even where to start.
Any help would be greatly appreciated as obviously the phone is absolutely brand new, and I'm very very upset about the whole thing! Not to mention the fact that I feel like an idiot!
Anyway, thanks in advance.

You deleted something that was not suppose to be deleted. Don't the stock tot file on this forum and follow the steps to Flash back to factory
http://forum.xda-developers.com/g-flex2/general/guide-lg-g-flex-2-stock-firmware-to-t3037593 follow the video and you should be up in running in no time . make sure this link support your version not sure which g flex2 Version you have.

Still no tot files available for the LG G Flex 2 (any variant). Sorry got to wait for some to become available.

Thanks for the input. I figured it would be something like that. Any idea when the files might be available? I don't mind being a guinea pig at this stage. My phone is LG H955 on Vodafone UK.
I am going to try and play dumb in Vodafone shop today and see if they'll replace it there and then (doubtful).
I suppose my other alternative is to return it to LG for Firmware Flash. Anyone know if this is possible and potential cost?
Strangely, I'm not so bothered about (temporarily) destroying my brand new phone too much, it's my sudden lack of connectivity that hurts the most.
Thanks guys

Further update; I have spoken to LG tech support / repair department, and I told them the phone had been rooted etc. (I didn't leave any identifying details!) They informed me that as the phone was now out of warranty, I should speak to their service partner SBE.
After calling SBE, they informed me that LG or their partner have no obligation to fix rooted phones, so apparently they just won't do it, even though I'm certain they could, which kind of sucks, as I was obviously willing to pay.
So it looks like I'm waiting for the TOT files. I hope they come along soon!
Lesson well and truly learned!

djjag1 said:
Further update; I have spoken to LG tech support / repair department, and I told them the phone had been rooted etc. (I didn't leave any identifying details!) They informed me that as the phone was now out of warranty, I should speak to their service partner SBE.
After calling SBE, they informed me that LG or their partner have no obligation to fix rooted phones, so apparently they just won't do it, even though I'm certain they could, which kind of sucks, as I was obviously willing to pay.
So it looks like I'm waiting for the TOT files. I hope they come along soon!
Lesson well and truly learned!
Click to expand...
Click to collapse
Stay positive. Hopefully those tot files come soon. I on the other hand what to experiment with my phone but need a tot file just in case I mess anything up.
If it's just your dialer that's acting up, have you tried a third party dialer to make phone calls?

djjag1 said:
Further update; I have spoken to LG tech support / repair department, and I told them the phone had been rooted etc. (I didn't leave any identifying details!) They informed me that as the phone was now out of warranty, I should speak to their service partner SBE.
After calling SBE, they informed me that LG or their partner have no obligation to fix rooted phones, so apparently they just won't do it, even though I'm certain they could, which kind of sucks, as I was obviously willing to pay.
So it looks like I'm waiting for the TOT files. I hope they come along soon!
Lesson well and truly learned!
Click to expand...
Click to collapse
Lets see if we can work on this.
Is it working ok, just not picking up the network?
How long exactly have you had it?

If you put what you all deleted meaning what folders they were in i could make a copy of that folder or apps you deleted and upload them on dropbox for you that might help get you going worth a shot
Be better if someone had the same variant as you i have the Sprint model.

Thanks again for input. I have hopefully managed to sort this with my provider. I was just within the 14 day cancellation period, so I have arranged for a brand new handset. I know its a little bit naughty but if the phone wasnt so laggy to begin with, I would never have rooted it.
I'm guessing it makes no difference to them as the phone will go back to lg for wipe and reflash as a matter of course once returned.
Thanks folks, I will remain on this forum and hopefully not do anything quite so stupid again!

Unfortunately this is my last day with this device . Great phone but i was wrong the 810 processor is dangerously hot to the point it felt like my pockets were on fire. This my second g flex2 and I'm moving on to something more reliable. Love this phone but this heat issue i can't risk. After 14 days i would be stuck with this phone and i can't take the risk of hoping of getting a device that function fine bye everyone.

:victory::victory::victory:

Today, I've gotten myself in a similar pickle after applying noob root.. Data OK but no phonecalls and no txts. When I tried to make a call, the thing said the phone is not activated. Sprint tech supp was of course no help, so after some digging I found this: ##72786#
Factory reset, keep the data (and all apps).
That solved it.
I guess I'm old enough to know that being lazy doesn't pay.

Stank0 said:
Today, I've gotten myself in a similar pickle after applying noob root.. Data OK but no phonecalls and no txts. When I tried to make a call, the thing said the phone is not activated. Sprint tech supp was of course no help, so after some digging I found this: ##72786#
Factory reset, keep the data (and all apps).
That solved it.
I guess I'm old enough to know that being lazy doesn't pay.
Click to expand...
Click to collapse
so you had root, and while doing this factory reset you were able to go back to full stock unrooted rom? if so, were you able to install updates? i too have a sprint version and i was rooted and tried installing an update but failed, i then unrooted my phone tried the update again and still got an error. im just wondering if this method would actually help people who have the same problem as i do.

gothikzoul said:
so you had root, and while doing this factory reset you were able to go back to full stock unrooted rom? if so, were you able to install updates? i too have a sprint version and i was rooted and tried installing an update but failed, i then unrooted my phone tried the update again and still got an error. im just wondering if this method would actually help people who have the same problem as i do.
Click to expand...
Click to collapse
Unfortunately, that wasn't the case.
I tried every possible way to install this damn update. Rooted, unrooted, factory reset 4 times, tried to install from the system update in settings, from recovery (which is, at least for me, very tricky to get into) all efforts errored out.
I posted a link to the update.zip in other thread.
So then I gave up and used this noob root which killed voice calls and text.
This code I posted says it does a factory reset but is resetting something else than other factory resets because almost all my settings, passwords and all apps remained intact.. Then I used the original root method and everything works like it's supposed to.
I guess we'll have to wait until someone finally starts developing for our phone.

So after a few days I just received a notification for the update for the third time. Any suggestions as to how I should proceed? I've tried it while being rooted and failed, also tried it the second time after unrooting and failed too. Also, what is the default location where the update is downloaded to, so I can back it up.

So far nothing has worked. The update should be in the cache folder. There is also a link to download the update that someone posted in another thread here about the update.

FYI - I forced the update through recovery over root and bricked my phone. Like all the way bricked. I can get to recovery and download mode, but no fastboot even. Luckily I was within my 14 days and there is no way to tell it is rooted... because it doesn't even get that far, so I got a replacement. My sincere advice would be to wait to root until we have custom recovery and stock firmware available, and if you have root now, wait to update until a dev can release a "root safe" version.
I'm not an expert but I'm not new either. I got the original Evo on launch day and have done all kinds of dumb stuff to every phone since. This is the first time I haven't been able to recover it.

austontatious said:
FYI - I forced the update through recovery over root and bricked my phone. Like all the way bricked. I can get to recovery and download mode, but no fastboot even. Luckily I was within my 14 days and there is no way to tell it is rooted... because it doesn't even get that far, so I got a replacement. My sincere advice would be to wait to root until we have custom recovery and stock firmware available, and if you have root now, wait to update until a dev can release a "root safe" version.
I'm not an expert but I'm not new either. I got the original Evo on launch day and have done all kinds of dumb stuff to every phone since. This is the first time I haven't been able to recover it.
Click to expand...
Click to collapse
=( *hug. That sucks man, thankfully you were able to get it replaced. *pfew I dodged a bullet there. I was actually thinking about doing the same thing getting home from work. Yeah its best we don't mess with the phone any longer those that have root at the moment. Until custom recovery and stock rom is out like he says.

Wow. How did you manage to "force" the update through recovery? I tried it through recovery but it would error out. (Error 7)

I will tell you, as a cautionary tale.
The error when you flash from recovery references a specific file that is incompatible with the update. I used root explorer to investigate further and found that the root script had overwritten a system file. The original was saved as "original" so I deleted the file causing the error and renamed the original one. After that, the update went through and I thought I was golden... Only now nothing else works.

[Q] A few questions about the H810 if anyone has a moment

Ok, so I happened upon an LG G4 H810 AT&T variant at a pawn shop a few weeks ago, they couldn't get it working because of the boot loop issue (person that pawned it probably did so knowing it was defective and had it working just long enough to demo it to get the cash). I took a look at it, great shape overall, no damage noted, plain old "ceramic" back cover, battery had a date of January 15 2016 on it so it's tough to say if the battery was just newer or the device itself since I couldn't get it to boot. Date code was 508 so obviously one of the well known defective models.
Long story short: got it for a pittance because they couldn't get anyone else to buy it, got it home, registered it at LG's website on my account, waited 2 days then chatted their support up and got them to accept it for RMA, shipped it out last week and it should be back tomorrow. I'm not sure if they repaired it or replaced it - the limited info I have says they "Swap Board (Main/RF)" so I'm guessing the entire motherboard was swapped for (hopefully) a newer one made this year that might not fail but probably will.
So, I had a question or two and I've done quite a bit of research the past few days and never found specific answers so at this point I'm just going to ask them and be done with it:
1) There's apparently no working root at all for the H810 that I've been able to find. I'm going to assume that the unit I'll be getting tomorrow or Tuesday will have been upgraded to Marshmallow unfortunately but that's just how it goes so there's no rolling back as I understand things. If there's a working root I'd be interested in knowing which one that happens to be. Also with no root there's probably no recovery either but I will keep researching to find out more as I'm able.
2) There's apparently no custom ROMs available because of the locked bootloader which will never get unlocked obviously as well. I've read that the PR (Puerto Rico) ROM could be installed on an H810 that was still running Lollipop with the v2 rollback but if this repaired board is Marshmallow that means it's been upgraded to v3 rollback and so that's dead in the water too.
3) I'm also going to assume that if the board has been replaced and hopefully is one made in 2016 (with a 6xx serial number) then it could last a while but there's no guarantee of it. I've seen people say the 6xx versions have not failed but then I find a post or two from someone that claims to know someone with a 6xx model and it failed at least once on them but I can't get any actual verification on it, that's just hearsay to me if there's no direct proof so all I can do is continue hoping it's a 6xx revision board and that it's not going to fail anytime soon.
This will be my second G4, had a Sprint variant last year and never had problems with it, sold it to a gent from Australia when he visited Las Vegas and as far as I know he's still using it, who knows.
If anyone can offer some info related to those questions I'd be grateful so thanks in advance if anyone can.
Have fun, always...
EDIT:
Seems that if I get very lucky and the replacement board comes with H81020n on it - the original Marshmallow build - there's a chance I can roll it back to H81010o using the TOT method from the other thread for it, that would at least get me root potential I suppose. Guess I'll find out tomorrow if the replacement arrives. Can't find any absolutely verified info about later builds, looks like the very latest patch build is H81022b from September and I'm going to assume if that happens to be on the board then all hope is lost, basically. Ugh...

br0adband said:
Ok, so I happened upon an LG G4 H810 AT&T variant at a pawn shop a few weeks ago, they couldn't get it working because of the boot loop issue (person that pawned it probably did so knowing it was defective and had it working just long enough to demo it to get the cash). I took a look at it, great shape overall, no damage noted, plain old "ceramic" back cover, battery had a date of January 15 2016 on it so it's tough to say if the battery was just newer or the device itself since I couldn't get it to boot. Date code was 508 so obviously one of the well known defective models.
Long story short: got it for a pittance because they couldn't get anyone else to buy it, got it home, registered it at LG's website on my account, waited 2 days then chatted their support up and got them to accept it for RMA, shipped it out last week and it should be back tomorrow. I'm not sure if they repaired it or replaced it - the limited info I have says they "Swap Board (Main/RF)" so I'm guessing the entire motherboard was swapped for (hopefully) a newer one made this year that might not fail but probably will.
So, I had a question or two and I've done quite a bit of research the past few days and never found specific answers so at this point I'm just going to ask them and be done with it:
1) There's apparently no working root at all for the H810 that I've been able to find. I'm going to assume that the unit I'll be getting tomorrow or Tuesday will have been upgraded to Marshmallow unfortunately but that's just how it goes so there's no rolling back as I understand things. If there's a working root I'd be interested in knowing which one that happens to be. Also with no root there's probably no recovery either but I will keep researching to find out more as I'm able.
2) There's apparently no custom ROMs available because of the locked bootloader which will never get unlocked obviously as well. I've read that the PR (Puerto Rico) ROM could be installed on an H810 that was still running Lollipop with the v2 rollback but if this repaired board is Marshmallow that means it's been upgraded to v3 rollback and so that's dead in the water too.
3) I'm also going to assume that if the board has been replaced and hopefully is one made in 2016 (with a 6xx serial number) then it could last a while but there's no guarantee of it. I've seen people say the 6xx versions have not failed but then I find a post or two from someone that claims to know someone with a 6xx model and it failed at least once on them but I can't get any actual verification on it, that's just hearsay to me if there's no direct proof so all I can do is continue hoping it's a 6xx revision board and that it's not going to fail anytime soon.
This will be my second G4, had a Sprint variant last year and never had problems with it, sold it to a gent from Australia when he visited Las Vegas and as far as I know he's still using it, who knows.
If anyone can offer some info related to those questions I'd be grateful so thanks in advance if anyone can.
Have fun, always...
EDIT:
Seems that if I get very lucky and the replacement board comes with H81020n on it - the original Marshmallow build - there's a chance I can roll it back to H81010o using the TOT method from the other thread for it, that would at least get me root potential I suppose. Guess I'll find out tomorrow if the replacement arrives. Can't find any absolutely verified info about later builds, looks like the very latest patch build is H81022b from September and I'm going to assume if that happens to be on the board then all hope is lost, basically. Ugh...
Click to expand...
Click to collapse
I haven't kept up with root, but I doubt anything MM latest or not you won't be able to root it. Also never flash wrong model firmware like the PR version. In the past that was a last resort firmware (before we got a back to stock for the actual AT&T model. You could get lucky but chances are you'll get a board with the latest or just the last previous firmware especially if it has a newer serial.
Pretty much the AT&T G4 is a device you want if you don't tinker with the device. I honestly love the G4, until certain apps even new apps ran worse on the G4 than they do on my G2.
Sent from my iPhone using Tapatalk

Just got the H810 back, checking on the board info here in a bit (if I can even detect anything) but it's running H81022b so I'm guessing that means I'm stuck with it as is but that was somewhat expected. I'm not going to even bother attempting a rollback at this point, will just wait for the yellow leather cover to arrive in the next few days then I'll put it up for sale on craigslist I suppose and go from there.
I have to wonder exactly what they did because the board info that I can detect using the LG Info tool from the Play Store still lists the same info for board date/etc (January 2016) so I don't know what the hell they actually did.
Kinda sucks but it's how things go sometimes.

Unlocked Verizon Phone. Nougat 7.0. Want To Downgrade and root. A few questions.

I just bought a new unlocked Verizon G920V phone from eBay to use with my Verizon prepaid account. (Well actually the hardware version under About Phone lists it as G920V.07). I can't say for sure if Marshmallow or Nougat shipped on this phone but it's currently running Nougat. As soon as I got it and it connected to my home wifi it wanted to update so I decided (maybe like an idiot) to let it. It appeared to download a giant file and flash itself a new firmware. This leads me to believe that it maybe shipped with Marshmallow but it obviously now has Nougat on it.
FWIW, I've rooted my own phones and a couple of my wife's phones in the past, but I'm by no means an expert. I'm fairly technically inclined in other areas of technology, but when it came to rooting various phones it amounted to carefully researching (usually through this site) and simply following a set of steps. I've always been successful. Long story short, I'm kind-of confused as to whether or not I can root. Like I said, I'm a bit confused, but it would appear that not only is there no root for the S6 running Nougat, but I believe I read where someone mentioned that Verizon released a security patch that prevents any sort of downgrading. Right after getting cellular service transferred the phone wanted to do a security patch so I assume that I've now got that patch installed as well.
So, can I downgrade this phone and root? I don't care about marshmallow I'll go to version 5 (whatever wonky name that one is called) if I have to. I would really just like to get root on this phone. Mainly so I can block ads more effectively and try to milk more battery life out of this thing because the battery life is horrible in my opinion.
Also FWIW, the software build/baseband number is G920VVRS4DQE1 if that helps or matters.
Anyway, this long-time lurker but first-time poster thanks you in advance for any replies.

It's been a few days and no replies, but from the additional information I've found since posting, I'm thinking that root ain't gonna happen. At this point I don't think it's even possible to roll back to an earlier version. Oh well I'll just live with this phone for awhile. I really like the phone despite not being able to get root. I suppose I'll just live with ads.

You can go to Samsung apps, if you have a Samsung account and download there ad block app. That is what I am using. It under Galaxy apps that came with phone
Sent from my Verizon Samsung Galaxy S6 using XDA Labs

You actually can downgrade your firmware should you so desire. The following two threads have links to firmwares flashable via odin.
https://forum.xda-developers.com/ve...20vvrs4dqd1-odin-nougat-7-0-firmware-t3597007
https://forum.xda-developers.com/verizon-galaxy-s6/general/downgrade-6-0-1-to-5-1-1-t3489816
At this point I don't think you can downgrade any lower than the OK7 firmware.

Needing help putting phone back to stock

I have a verizon branded s7 edge. I ran a combination file on it to try to get rid of FRP. Long story short on why is because my buddies wife ended up having a psychotic break and changed all of his passwords and accounts to his bills, started seeing things that weren't there, thought he was out cheating, and destroyed all his possessions. He tried to have her committed but since they weren't married and some stuff I don't know of she was never put in the hospital for treatment so he left her. Basically went crazy. So he had just bought the phone and after she changed all the account information and emails, the passwords were lost and the phone has been a paperweight. The phone is brand new and had only 2 weeks of use. End of backstory of phone.
I tried running a combination file on it and got it to boot up with that. For model number it says SM-G935A but shouldn't it be a V since it is verizon branded? I can't find a file to run in odin that works and get different errors with each firmware I try verizon and att.
Model is Samsung-SM-G935! [SS]
PDA is FA60_G935AUCU8ARJ2
Phone is G935AUCU8ARJ1
H/W is REV0.7
CAL.D is 2017.07.31
Android security patch January 1, 2016
Build # is MMB29M.FA60_G935AUCU8ARJ2
I have tried different versions of odin and tried the following firmware files
AP_G935VVRUACSH1_CL14274526_QB25694462_REV02_user_low_ship_MULTI_CERT_meta.tar
AP_G935VVRU4CRE5_CL13527029_QB18290732_REV02_user_low_ship_MULTI_CERT_meta.tar
and a few more but deleted them.
I am currently downloading 6.0.1+Marshmallow+S7+Edge+Firmware+Files and SM-G935V_1_20160804145414_ocj96ulu4y_fac.zip
to see if that helps. Did I use the wrong combination file and making the phone think it is att or is it really a G935A? I can download and give any information just might take a little bit to download. I even tried using Frija I believe it is called to get the firmware but go an error when updating the phone.
Am I doing something wrong or is the phone still a brick. If I don't get it working that is fine but I am interested in how this stuff works but there is so much information that it is a little overwhelming.
Edit: Got back to default firmware but still have frp enabled. That was a let down but at least I am not stuck in Combination.