Related
Hi
I have a question before sending my HTC back for the wifi repair to HTC.
If I make a nandroid backup of my existing custom rom, then unroot the phone, when I reroot the phone once i get it back, can I simply use the nandroid backup I had made to restore everything once I have re-rooted?
Thanks
Manny
mannysroot said:
Hi
I have a question before sending my HTC back for the wifi repair to HTC.
If I make a nandroid backup of my existing custom rom, then unroot the phone, when I reroot the phone once i get it back, can I simply use the nandroid backup I had made to restore everything once I have re-rooted?
Thanks
Manny
Click to expand...
Click to collapse
Yep, ofcourse you can.
To be honest you need to re-lock your bootloader also.
And hopefully your lucky enough to be one of the people that gets a warranty fix even though your unlocked and rooted.
As many people get turned away.
Wilks3y said:
Yep, ofcourse you can.
To be honest you need to re-lock your bootloader also.
And hopefully your lucky enough to be one of the people that gets a warranty fix even though your unlocked and rooted.
As many people get turned away.
Click to expand...
Click to collapse
Ok, thanks, its worth a try
I made a nandroid backup of my stock rom and also have the boot.img for the stock rom. I assume that if I flash these 2 first and then lock the bootloader? Is that correct?
if it is correct - is it simple to lock the bootloader?
mannysroot said:
Ok, thanks, its worth a try
I made a nandroid backup of my stock rom and also have the boot.img for the stock rom. I assume that if I flash these 2 first and then lock the bootloader? Is that correct?
if it is correct - is it simple to lock the bootloader?
Click to expand...
Click to collapse
Hi, yeah thats correct mate.
Easiest way is to flash the correct RUU for you phone. Im sorry but I don't know how to get the correct RUU perhaps someone else could help.
What I do know is that you can never fully "lock" the bootloader again, it will say "Re-Locked" and not "Locked" all you can do is hope they do not check the bootloader.
Hope this helps
Wilks3y said:
Hi, yeah thats correct mate.
Easiest way is to flash the correct RUU for you phone. Im sorry but I don't know how to get the correct RUU perhaps someone else could help.
What I do know is that you can never fully "lock" the bootloader again, it will say "Re-Locked" and not "Locked" all you can do is hope they do not check the bootloader.
Hope this helps
Click to expand...
Click to collapse
If they check it and see it says relocked and then refuse to repair it is the same as me leaving it unlocked?? So i may as well leave it as it is?
Thanks
Manny
mannysroot said:
If they check it and see it says relocked and then refuse to repair it is the same as me leaving it unlocked?? So i may as well leave it as it is?
Thanks
Manny
Click to expand...
Click to collapse
TO be honest yeah, your right you may as well leave it as unlocked.
But definately return it to stock as much as poss, using the RUU or flashing the stock images etc.
Hope this helps
Wilks3y said:
TO be honest yeah, your right you may as well leave it as unlocked.
But definately return it to stock as much as poss, using the RUU or flashing the stock images etc.
Hope this helps
Click to expand...
Click to collapse
ok cool, in that case will just flash the nandroid back up of the stock img and the boot.img and leaver the bootloader unlocked - should be sufficient. should i also uninstall the clockwork mod etc?
mannysroot said:
ok cool, in that case will just flash the nandroid back up of the stock img and the boot.img and leaver the bootloader unlocked - should be sufficient. should i also uninstall the clockwork mod etc?
Click to expand...
Click to collapse
Definately, if they boot the phone and see CWM, TWRP, Titanium, SuperSU/SuperUSer they'll know straight away you are rooted.
Remove anything you possibly can that will identify a rooted unit.
Wilks3y said:
Definately, if they boot the phone and see CWM, TWRP, Titanium, SuperSU/SuperUSer they'll know straight away you are rooted.
Remove anything you possibly can that will identify a rooted unit.
Click to expand...
Click to collapse
silly question - i know what the rest are but what is TWRP?
mannysroot said:
silly question - i know what the rest are but what is TWRP?
Click to expand...
Click to collapse
Just another CWM mate.
I sent mine off for repair yesterday. The bootloader is relocked but everything else is completely stock, we'll see how it goes
Michealtbh said:
I sent mine off for repair yesterday. The bootloader is relocked but everything else is completely stock, we'll see how it goes
Click to expand...
Click to collapse
hi
if you dont mind could you update to let me know how u got on?
also how long did they say before you should get it back etc?
thanks
manny
mannysroot said:
hi
if you dont mind could you update to let me know how u got on?
also how long did they say before you should get it back etc?
thanks
manny
Click to expand...
Click to collapse
Well they haven't even received it yet, since it was only sent on Thursday. I think they said it could take up to 7 working days
Michealtbh said:
Well they haven't even received it yet, since it was only sent on Thursday. I think they said it could take up to 7 working days
Click to expand...
Click to collapse
HI
Any news on your repair?
Thanks
Manny
mannysroot said:
HI
Any news on your repair?
Thanks
Manny
Click to expand...
Click to collapse
Using their repair tracking page, the current status is "in repair" so it's looking good. The status just changed an hour ago though so there's still plenty of time for them to call with bad news.
mannysroot said:
HI
Any news on your repair?
Thanks
Manny
Click to expand...
Click to collapse
Got my tracking number so it looks like it's been fixed
Warranty VOID?
I needed to send my phone in, but I don't have the sticker on the back, or the box, and there's no way for me to get to the settings on the phone, because the screen stopped working.
Will HTC still be able to service my phone, or is the warranty considered void?
gtmaster303 said:
I needed to send my phone in, but I don't have the sticker on the back, or the box, and there's no way for me to get to the settings on the phone, because the screen stopped working.
Will HTC still be able to service my phone, or is the warranty considered void?
Click to expand...
Click to collapse
if you are looking for your serial number i think its engraved on the micro-sim tray
HTC Repair SUCKS
mannysroot said:
hi
if you dont mind could you update to let me know how u got on?
also how long did they say before you should get it back etc?
thanks
manny
Click to expand...
Click to collapse
HTC repair is bull**** just for the record. I have 4G Slides on the rest of my lines, ALL of which had to be sent in.
2 of those phones took nearly 45 [FORTY FIVE] days to get back to me. Apparently there was a hold for parts coming in from Taiwan. They wouldn't tell me which parts. They wouldn't even give me an estimate time. HTC didn't apologize or update me on my repair. I found all this out after numerous calls day after day.
But if you thought that was bad service, you'll love this...
The third phone was sent out and came back fairly quickly. Within a week. I was so happy to get my phone back.
Opened the box and GUESS WHAT?
HTC SENT ME THE WRONG PHONE
They sent me a completely different phone for a different carrier (HTC Evo 4G for Sprint). It was very beat up as well.
I swear, if it wasn't for their designs (which I love dearly) I would've dropped the company by now...
Sorry for the rant/threadjack. Thought you guys would like to hear a horror story. I'm done
does anyone know how to remove the super su app and the clockwork recovery? everything else is now back to stock as i did a nandroid back up immediately after rooting initially
thanks
manny
First of all sorry for adding yet another question onto the Q&A, but researching around I can not find much information on this problem.
So anyway I've been having the following problems with my HOX, and now to add to it all Im stuck in APX mode. I left my phone powered off in my bag and when I went to look at it later on I noticed it was stuck on the HTC Boot screen, and the back of the device was VERY warm (battery?) I got it home and plugged into USB and the device just came under APX and as I'm sure you've read, nothing seems to get out of it so I am stuck (Cant enter bootloader)
However;
When I have the device plugged in and hold power+vol up I get the USB connection sounds played in windows, first the new device one (DUN DIN) followed after a second by (DUN DUN) the unplugged sound. THIS time I unplugged between sounds and left he phone for about a minute, plugged it back in and I only heard the new device sound, and now instead of APX my phone is listed under USB Controllers>Unknown Device. Not sure if this is an improvement or not? But I'm hoping its gaining charge from this and will attempt to restart in a while and see if I can enter the bootloader.
Does anyone have any suggestions here?
APX mode means it's dead, nobody here has recovered their phone from that.
An actual brick, sorry.
yeah, that's right, APX is = to seriously hard HW damage...
BenPope said:
APX mode means it's dead, nobody here has recovered their phone from that.
An actual brick, sorry.
Click to expand...
Click to collapse
matt95 said:
yeah, that's right, APX is = to seriously hard HW damage...
Click to expand...
Click to collapse
You're kidding? I can't believe this it was powering on and working (slightly) earlier today! I thought I saw a post
saying someone got out of it just by leaving it for a while
GOOD GOD
I plugged it into charge, left it for about 5 minutes and it has booted back into the phone!!
Resolved I guess
[★] said:
I plugged it into charge, left it for about 5 minutes and it has booted back into the phone!!
Resolved I guess
Click to expand...
Click to collapse
Flash it to stock ASAP, I suspect it's on its way out, and you'll want to use the warranty.
BenPope said:
Flash it to stock ASAP, I suspect it's on its way out, and you'll want to use the warranty.
Click to expand...
Click to collapse
I'm on 1.28 so I cant flash it to stock! Or can I?
[★] said:
I'm on 1.28 so I cant flash it to stock! Or can I?
Click to expand...
Click to collapse
You can install a nandroid backup of stock ROM, boot.img, stock recovery, and relock.
BenPope said:
You can install a nandroid backup of stock ROM, boot.img, stock recovery, and relock.
Click to expand...
Click to collapse
Ok thanks, I have a couple questions though:
I have looked around and can't find a nandroid backup for my CID HTC__001, however I did just find this thread which claims it is possible without a nandroid backup! Am I right?
Also, I'm assuming this wont revert hboot to an older version will it? So won't HTC (if i send it in for repair) see the later hboot and
just work out that I have obviously unlocked my bootloader at some point? Also won't the bootloader say Relocked as appose to
Locked?
Cheers pal!
Yes, you're right, but if it gets stuck on APX, none of that'll matter, unless it manages to magically work again whilst at the repair centre, in which case at least you have HTC signed software on it, so it should be covered.
BenPope said:
Yes, you're right, but if it gets stuck on APX, none of that'll matter, unless it manages to magically work again whilst at the repair centre, in which case at least you have HTC signed software on it, so it should be covered.
Click to expand...
Click to collapse
Ok, you say atleast I will have HTC signed software on it, but still redundant considering it will be 'RELOCKED' right?
On on a side note, member Vcek says that my initial issue sounds more hardware related, so if everything goes tits
up again I may just try invoke the hardware warranty, which apparently isn't effected by unlocking the bootloader
[★] said:
Ok, you say atleast I will have HTC signed software on it, but still redundant considering it will be 'RELOCKED' right?
On on a side note, member Vcek says that my initial issue sounds more hardware related, so if everything goes tits
up again I may just try invoke the hardware warranty, which apparently isn't effected by unlocking the bootloader
Click to expand...
Click to collapse
It's not redundant, they have been known to refuse warranty when unsigned software is installed. It'll make your life easier to install stock software before sending it off to HTC.
It depends where you bought it, but often the retailer is responsible, not HTC, so HTC would be within their rights to refuse a repair if you don't meet their terms. The retailer might not be able to refuse, though. Either way, I'm advising you on creating your own luck.
BenPope said:
It's not redundant, they have been known to refuse warranty when unsigned software is installed. It'll make your life easier to install stock software before sending it off to HTC.
It depends where you bought it, but often the retailer is responsible, not HTC, so HTC would be within their rights to refuse a repair if you don't meet their terms. The retailer might not be able to refuse, though. Either way, I'm advising you on creating your own luck.
Click to expand...
Click to collapse
Ok well I bought it off Amazon so I will get in contact with them in terms of hardware faults. Surely they will need some sort of proof?
[★] said:
Ok well I bought it off Amazon so I will get in contact with them in terms of hardware faults. Surely they will need some sort of proof?
Click to expand...
Click to collapse
I dunno, in the UK, you're pretty safe. Great consumer protection laws.
The phone is less than a year old, so HTC won't need any proof of purchase, but ask Amazon what to do with it.
BenPope said:
I dunno, in the UK, you're pretty safe. Great consumer protection laws.
The phone is less than a year old, so HTC won't need any proof of purchase, but ask Amazon what to do with it.
Click to expand...
Click to collapse
Ok will do.
Stuck in APX mode again.
[Q] Radio and OpenDSP have "INVALID-VER-INFO" beside them. Is this normal? Need help
I just recently purchased the m8. I did lots of research learning everything I could before doing any modding. So today I decided to unlock my boot-loader so it was my first time getting into recovery. But when I get into recovery I see both radio and OpenDSP have "INVALID-VER-INFO" beside them. Its never been modified and I got it from t mobile and was the first to open the device. Not a second hand phone. Is this normal? I've been googling for hours and cant find any information. Its been sort of difficult getting any help in the htc M8 help threads honestly. If anyone can shed any information I would greatly appreciate it. I haven't noticed any thing wrong with my phone out of the box and everything about the functionality of the phone has been stellar.
ahfu25 said:
I just recently purchased the m8. I did lots of research learning everything I could before doing any modding. So today I decided to unlock my boot-loader so it was my first time getting into recovery. But when I get into recovery I see both radio and OpenDSP have "INVALID-VER-INFO" beside them. Its never been modified and I got it from t mobile and was the first to open the device. Not a second hand phone. Is this normal? I've been googling for hours and cant find any information. Its been sort of difficult getting any help in the htc M8 help threads honestly. If anyone can shed any information I would greatly appreciate it. I haven't noticed any thing wrong with my phone out of the box and everything about the functionality of the phone has been stellar.
Click to expand...
Click to collapse
Is that on the bootloader screen? What are u trying to accomplish?
twinnfamous said:
Is that on the bootloader screen? What are u trying to accomplish?
Click to expand...
Click to collapse
In the bootloader screen it says invalid ver info next to both. I want to know if this is normal on an unmodified device. I dont want to mod my phone with it saying invalid version next to radio and opendsp.
ahfu25 said:
In the bootloader screen it says invalid ver info next to both. I want to know if this is normal on an unmodified device. I dont want to mod my phone with it saying invalid version next to radio and opendsp.
Click to expand...
Click to collapse
I think something is off on that phone. I unlocked and s-offed mine and the only thing different was the os is blank but everything else was fine.
But if u have no actual problems with cell reception or audio then maybe u just need to update the firmware to latest after u s-off and that Will fix u up. More than likely.
Let me know I have done a lot on my phone allready. I even switched it to a dev edition just to get the 4.4.3 firmware and then flashed my backup back to my Rom of choice.
I'll help if I can. I notice there ain't many people helping on this forum there all on the international forum
twinnfamous said:
I think something is off on that phone. I unlocked and s-offed mine and the only thing different was the os is blank but everything else was fine.
But if u have no actual problems with cell reception or audio then maybe u just need to update the firmware to latest after u s-off and that Will fix u up. More than likely.
Let me know I have done a lot on my phone allready. I even switched it to a dev edition just to get the 4.4.3 firmware and then flashed my backup back to my Rom of choice.
I'll help if I can. I notice there ain't many people helping on this forum there all on the international forum
Click to expand...
Click to collapse
I appreciate that. I just didn't want to s-off since I dont do any heavy modding. I was just gonna unlock the boot-loader, install custom recovery root and flash arhd. I don't think this is normal either for a brand new phone that hasn't been touched software wise. I might go exchange it at t mobile. This is my screen
ahfu25 said:
I appreciate that. I just didn't want to s-off since I dont do any heavy modding. I was just gonna unlock the boot-loader, install custom recovery root and flash arhd. I don't think this is normal either for a brand new phone that hasn't been touched software wise. I might go exchange it at t mobile.
Click to expand...
Click to collapse
I understand about the s-off but really it's the best thing to do because if something ever goes wrong there will be nothing stopping u from fixing it.
Also I was gonna suggest taking it back but they might trip on the unlocked bootloader and if u fastboot oem lock it Will say relocked. So they will know. But it's worth a try. T-Mobile doesn't seem like they know anything about technical stuff. so if you try to explain to them they might look at you like they don't know what your talking about.
I seen the picture if it is still locked take it back. And show them
Your firmware is allready the latest so that's a factory f-up.
twinnfamous said:
I understand about the s-off but really it's the best thing to do because if something ever goes wrong there will be nothing stopping u from fixing it.
Also I was gonna suggest taking it back but they might trip on the unlocked bootloader and if u fastboot oem lock it Will say relocked. So they will know. But it's worth a try. T-Mobile doesn't seem like they know anything about technical stuff. so if you try to explain to them they might look at you like they don't know what your talking about.
I seen the picture if it is still locked take it back. And show them
Your firmware is allready the latest so that's a factory f-up.
Click to expand...
Click to collapse
How would they know the bootloader is unlocked at the tmobile store? Would they check on that before exchanging the device?
ahfu25 said:
How would they know the bootloader is unlocked at the tmobile store? Would they check on that before exchanging the device?
Click to expand...
Click to collapse
More than likely. I got charged 50 bucks one time and I couldn't even fight it because they sent it in and my Bill went up I wondered why so I asked and they said because of modifications all they did was exchange it but I still had to pay. Try it or relock it and do the ruu for that firmware. And see if it will take off the tampered flag and fix the ver info
twinnfamous said:
More than likely. I got charged 50 bucks one time and I couldn't even fight it because they sent it in and my Bill went up I wondered why so I asked and they said because of modifications all they did was exchange it but I still had to pay. Try it or relock it and do the ruu for that firmware. And see if it will take off the tampered flag and fix the ver info
Click to expand...
Click to collapse
I dont have a tampered flag in bootloader. Just "Unlocked"
ahfu25 said:
I dont have a tampered flag in bootloader. Just "Unlocked"
Click to expand...
Click to collapse
So then u never flashed recovery yet. So u should try to take it back.
If they are tripping just tell them the facts that the software was not properly installed on device.
twinnfamous said:
So then u never flashed recovery yet. So u should try to take it back.
If they are tripping just tell them the facts that the software was not properly installed on device.
Click to expand...
Click to collapse
whats that RUU you mentioned? Is there one specifically for the tmobile version that I can flash via stock recovery?
ahfu25 said:
whats that RUU you mentioned? Is there one specifically for the tmobile version that I can flash via stock recovery?
Click to expand...
Click to collapse
Sorry about taking a while.
Here's the link to what u will need http://forum.xda-developers.com/showthread.php?t=2754063
twinnfamous said:
Sorry about taking a while.
Here's the link to what u will need http://forum.xda-developers.com/showthread.php?t=2754063
Click to expand...
Click to collapse
No apology needed. Thank you for helping me out. I was able to s-off and get everything back to stock. Boot loader locked not "relocked" , s-on, unrooted. But the "invalid version" message was still there. I just came back from the tmobile store and they ran some diagnostics and said there was a problem with the software. They exchanged it for me and I checked it before I left the store and this one is perfect. I even asked for them to run the same diagnostics and everything checked out fine. I'm gonna do even a little more research before modding this one. I'm a little nervous now ..lol....but again thank you!!! I really love the M8. I came from the galaxy note 3 from att and sadly att locks the boot-loader on it. I love the note 3 just not on AT&T. I'm trying to sell my AT&T note 3 to buy a tmo version.
ahfu25 said:
No apology needed. Thank you for helping me out. I was able to s-off and get everything back to stock. Boot loader locked not "relocked" , s-on, unrooted. But the "invalid version" message was still there. I just came back from the tmobile store and they ran some diagnostics and said there was a problem with the software. They exchanged it for me and I checked it before I left the store and this one is perfect. I even asked for them to run the same diagnostics and everything checked out fine. I'm gonna do even a little more research before modding this one. I'm a little nervous now ..lol....but again thank you!!! I really love the M8. I came from the galaxy note 3 from att and sadly att locks the boot-loader on it. I love the note 3 just not on AT&T. I'm trying to sell my AT&T note 3 to buy a tmo version.
Click to expand...
Click to collapse
That's great problem solved.
now u know u got a good device.
I love the m8 too. I got mine first day it came out at T-Mobile.
First thing I did was unlock and s-off then recovery and root. Till some roms came out then I went to Bad Seed Customs Rom and that's it.
I've tried a lot of the roms even the new stock with elementalx kernel will last all day.
There's a whole lot u can do but most of the info is in the international forum.
Anyways glad I could help.
twinnfamous said:
That's great problem solved.
now u know u got a good device.
I love the m8 too. I got mine first day it came out at T-Mobile.
First thing I did was unlock and s-off then recovery and root. Till some roms came out then I went to Bad Seed Customs Rom and that's it.
I've tried a lot of the roms even the new stock with elementalx kernel will last all day.
There's a whole lot u can do but most of the info is in the international forum.
Anyways glad I could help.
Click to expand...
Click to collapse
Weird bro...now I go into boot loader with this phone and I'm getting the invalid ver message again. I'm still unmodified with bootloader still locked. I haven't even connected the phone to my computer yet.
ahfu25 said:
Weird bro...now I go into boot loader with this phone and I'm getting the invalid ver message again. I'm still unmodified with bootloader still locked. I haven't even connected the phone to my computer yet.
Click to expand...
Click to collapse
That's crazy what are you gonna do?
twinnfamous said:
That's crazy what are you gonna do?
Click to expand...
Click to collapse
Lol....I'm gonna keep it. I think it's software related. Nothing wrong functionality wise just like the other one. And I went to a different tmobile store for inventory purposes and lessen the chances of me getting a bad phone. Like I said I checked it at the store it didn't have that message. And they ran diagnostics and it read clean. I'm just gonna flash away lol
ahfu25 said:
Lol....I'm gonna keep it. I think it's software related. Nothing wrong functionality wise just like the other one. And I went to a different tmobile store for inventory purposes and lessen the chances of me getting a bad phone. Like I said I checked it at the store it didn't have that message. And they ran diagnostics and it read clean. I'm just gonna flash away lol
Click to expand...
Click to collapse
That's cool. I would do the same thing. Have a great time
twinnfamous said:
That's cool. I would do the same thing. Have a great time
Click to expand...
Click to collapse
Some research needs to be done to figure it out. I know I'm not the only one
ahfu25 said:
Some research needs to be done to figure it out. I know I'm not the only one
Click to expand...
Click to collapse
Probably not but everybody just gets to unlocking and s-offing so fast they probably don't notice.
It's probably just the ones coming with that firmware out of the box.
When I got mine it had a different version.
Hi guys,
Yesterday I got sweaty hand palms.
My EU 815 G4 is unlocked, the official way, and I had rooted it.
Then I tried to install xposed from twrp and I did something wrong, and ended up in bootloop...
I have just updated to v20b before, and forgot to connect the phone to the PC, and allow the PC debug access before installing xposed, so i could see the phone in ADB mode, but couldn't access it.
Of course I hadn't made a backup before this - I like to cry
Just as a desperate try, when everything else had failed, i thought about using the new tool provided by shakeyabooti LG UP to flash the factory KDZ all over
I put the phone in SW. update mode by:
1. Turning off the phone
2. connecting USB cable to the PC
3. Press and hold vol. up while connecting the USB cable to the phone
Then i downloaded the v20b KDZ file, provided by Autoprime (since this was what i where allready running)
Opened LG UP, loaded the H81520B_00.kdz, marked REFURBISH
Lastly i pressed "Start" and waited for about 15-20 minutes and "TADAAAA"
The phone where up and running again... only things lost where root and TWRP
- Sharing since I'm properly not the only one ending up in this kind of mess :laugh:
Just tried it no luck :/
So just to confirm...unlocking bootloader official way does void warranty and we can not send it in for repairs?
rakinisbat said:
Just tried it no luck :/
So just to confirm...unlocking bootloader official way does void warranty and we can not send it in for repairs?
Click to expand...
Click to collapse
Indeed. Maybe you'll find a cool employee at your vendor who will still do it, but your warranty is definately void and they don't need to do anything. Depends on how acommodating the employee is. If you're stuck in a bootloop @rakinisbat just follow the steps in this thread.
And please keep in mind that there's a way to get out of bootloops 99% of the time (in fact 100% if it's a software related problem), you just have to do a good search on xda. Furthermore there's an uninstaller app for xposed in the official rovo89 thread, which you can flash via recovery and it which undos the xposed installation and your phone will boot fine (if you can access TWRP - just flash it). If you have further questions you can PM me, always happy to help
Follow_and_Feel said:
Indeed. Maybe you'll find a cool employee at your vendor who will still do it, but your warranty is definately void and they don't need to do anything. Depends on how acommodating the employee is. If you're stuck in a bootloop @rakinisbat just follow the steps in this thread.
And please keep in mind that there's a way to get out of bootloops 99% of the time (in fact 100% if it's a software related problem), you just have to do a good search on xda. Furthermore there's an uninstaller app for xposed in the official rovo89 thread, which you can flash via recovery and it which undos the xposed installation and your phone will boot fine (if you can access TWRP - just flash it). If you have further questions you can PM me, always happy to help
Click to expand...
Click to collapse
Thanks Mate, I guess ill have to try my luck with LG,
I have that batch of H815 with the faulty motherboard, unfortunately I'm in that 1% *Sigh* :crying:
Tried literally everything i could with the software, pretty much confirmed it is the motherboard.
It looks like the KDZ is flashing properly, as LGUP shows whichever kdz i put on, but the actual hardware is not capable of booting into the OS.
rakinisbat said:
Thanks Mate, I guess ill have to try my luck with LG,
I have that batch of H815 with the faulty motherboard, unfortunately I'm in that 1% *Sigh* :crying:
Tried literally everything i could with the software, pretty much confirmed it is the motherboard.
It looks like the KDZ is flashing properly, as LGUP shows whichever kdz i put on, but the actual hardware is not capable of booting into the OS.
Click to expand...
Click to collapse
Ugh, okay that's bad luck. Sorry to hear. If it's a motherboard problem I can't help you unfortunately Sorry for that. What is exactly happening when you try to flash via LGUP? Just curious
Follow_and_Feel said:
Ugh, okay that's bad luck. Sorry to hear. If it's a motherboard problem I can't help you unfortunately Sorry for that. What is exactly happening when you try to flash via LGUP? Just curious
Click to expand...
Click to collapse
It flashed perfectly fine, once completed it reboots and just literally sits on the LG logo.....FOREVER or till the battery dies.
So much disappointment in LG
rakinisbat said:
It flashed perfectly fine, once completed it reboots and just literally sits on the LG logo.....FOREVER or till the battery dies.
So much disappointment in LG
Click to expand...
Click to collapse
Oh yeah that really sounds like a hardware problem. Damn it LG! But is your bootloader still locked? You might have a chance to get a new one if it is And if it's a hardware prob you still have your warranty, haven't you?
Follow_and_Feel said:
Oh yeah that really sounds like a hardware problem. Damn it LG! But is your bootloader still locked? You might have a chance to get a new one if it is And if it's a hardware prob you still have your warranty, haven't you?
Click to expand...
Click to collapse
Nope, my bootloader is unlocked, im a flash-a-holic, longest i have lasted without rooting or unlocking a bootloader is about 2 weeks. I would have never imagined such a massive hardware issue with a flagship phone. I'll probably get a nexus 6P atleast it has better support than a LG. I'm in Australia, I imported this phone when it was released, so i have to send this phone overseas if i want it repaired, which they will most likely deny.
Sooooo over LG now! There are like hundreds if not thousands that are effected they are not even acknowledging it or providing a viable solution.
rakinisbat said:
Nope, my bootloader is unlocked, im a flash-a-holic, longest i have lasted without rooting or unlocking a bootloader is about 2 weeks. I would have never imagined such a massive hardware issue with a flagship phone. I'll probably get a nexus 6P atleast it has better support than a LG. I'm in Australia, I imported this phone when it was released, so i have to send this phone overseas if i want it repaired, which they will most likely deny.
Sooooo over LG now! There are like hundreds if not thousands that are effected they are not even acknowledging it or providing a viable solution.
Click to expand...
Click to collapse
Haha! I can completely subscribe to the flash-a-holic :laugh: Well ok. So it's even worse than i thought Sorry for ya. At least you live on a continent everyone here desires to go to :laugh: Going to Australia is very popular in germany But sorry that you're experiencing trouble with your LG. Good luck with that nexus - it's an awesome phone, too. Bye bye
I've got the bootloop issue. Phone was turning on or not, just vibrating etc. I've dissassembled it, assembled again and it started working don't know why...Now I've flashed CM I was on Genisis ROM earlier maybe that was the issue
zwodziarz said:
I've got the bootloop issue. Phone was turning on or not, just vibrating etc. I've dissassembled it, assembled again and it started working don't know why...Now I've flashed CM I was on Genisis ROM earlier maybe that was the issue
Click to expand...
Click to collapse
Hi sir
I decide to buy lg g4.
If i flash cm ,bootloop not happend again?
Thank you
It doesn't matter what firmware you have got. Bootloop is happening because of hardware failure.
Odesláno z mého LG-H815 pomocí Tapatalk
I was on 8.1 with Flash Kernel installed using images...I wanted to get back to stock...so unchecked OEM Unlocking in Developer Options, went to bootloader and locked bootloader using fastoboot flashing lock..and now I am getting "Can't find valid operating system. The device will not start". I can't unlock the bootloader now as I unchecked OEM unlocking in Developer Options and can't flash factory images also as it says Flashing is not allowed in Lock State, Did I brick the device?
Update: I have returned my device to Google and they processed a replacement
i am just curious, how were planning on flashing a rom with locked bootloader?
ram4ufriends said:
I was on 8.1 with Flash Kernel installed using images...I wanted to get back to stock...so unchecked OEM Unlocking in Developer Options, went to bootloader and locked bootloader using fastoboot flashing lock..and now I am getting "Can't find valid operating system. The device will not start". I can't unlock the bootloader now as I unchecked OEM unlocking in Developer Options and can't flash factory images also as it says Flashing is not allowed in Lock State, Did I brick the device?
Click to expand...
Click to collapse
Yea, I think you may have turned it into a fancy paperweight. Been there, done that. You should have waited to uncheck OEM unlocking until after you locked the bootloader, which wiped your phone. About the only thing I can suggest is to try and run Deuces script to see if you can rescue your device. Best of luck to you.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
ram4ufriends said:
I was on 8.1 with Flash Kernel installed using images...I wanted to get back to stock...so unchecked OEM Unlocking in Developer Options, went to bootloader and locked bootloader using fastoboot flashing lock..and now I am getting "Can't find valid operating system. The device will not start". I can't unlock the bootloader now as I unchecked OEM unlocking in Developer Options and can't flash factory images also as it says Flashing is not allowed in Lock State, Did I brick the device?
Click to expand...
Click to collapse
Sorry for your loss, but you indeed have a fancy paperweight.
However I wonder if there isnt the QCom USB mode or something like that that exist on older devices, where you can access the phone partitions at a lower level and then restore whatever partitions is broken.
Paradoxxx said:
Sorry for your loss, but you indeed have a fancy paperweight.
However I wonder if there isnt the QCom USB mode or something like that that exist on older devices, where you can access the phone partitions at a lower level and then restore whatever partitions is broken.
Click to expand...
Click to collapse
With the new partitioning no idea if it still works. But OP has nothing to loose anyway i guess.
gee2012 said:
With the new partitioning no idea if it still works. But OP has nothing to loose anyway i guess.
Click to expand...
Click to collapse
Yeah at that point... Not sure what is Google saying about that. Maybe RMA it ?
Saying something like that should work.
"I was using my device, and suddenly it froze and nothing responded. It suddenly rebooted and shown this error message."
gee2012 said:
With the new partitioning no idea if it still works. But OP has nothing to loose anyway i guess.
Click to expand...
Click to collapse
Sorry didn't get, What do you mean by OP has nothing to loose?
Badger50 said:
Yea, I think you may have turned it into a fancy paperweight. Been there, done that. You should have waited to uncheck OEM unlocking until after you locked the bootloader, which wiped your phone. About the only thing I can suggest is to try and run Deuces script to see if you can rescue your device. Best of luck to you.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
How did you recover your devices from that state earlier when you did the same thing?
ram4ufriends said:
Sorry didn't get, What do you mean by OP has nothing to loose?
Click to expand...
Click to collapse
since your phone is now essentially a brick, you can try just about anything without worry of bricking your phone.
ram4ufriends said:
I was on 8.1 with Flash Kernel installed using images...I wanted to get back to stock...so unchecked OEM Unlocking in Developer Options, went to bootloader and locked bootloader using fastoboot flashing lock..and now I am getting "Can't find valid operating system. The device will not start". I can't unlock the bootloader now as I unchecked OEM unlocking in Developer Options and can't flash factory images also as it says Flashing is not allowed in Lock State, Did I brick the device?
Click to expand...
Click to collapse
You cannot flash full images, but you can still flash OTAs... download the full OTA instead, and install (sideload) it from the stock recovery. Be sure to select the SAME build number you were on to begin with- eg. If you were on 8.1, use the 8.1 OTA. There will be a mode there for "Apply update from ADB". You put the phone into "sideload mode" and then send the OTA to the phone via adb. This will work regardless whether you have usb debugging enabled or not. Follow the directions given on the included link.
ram4ufriends said:
How did you recover your devices from that state earlier when you did the same thing?
Click to expand...
Click to collapse
I didn't. They are still paperweights sitting in a drawer!
I got the same message yesterday after doing... God knows what. I can't even remember what went wrong.
My first thought was to flash a factory image. But it didn't helped at first. Probably, because i was trying to flash another factory image and not the one that came as stock on my phone.
So if you don't remember, which image it was, try all of them Hopefully, you'll get your phone booted again.
My first reaction was, is this april fools day? Is this an xda style joke? unchecked oem unlock?
dontbeweakvato said:
My first reaction was, is this april fools day? Is this an xda style joke? unchecked oem unlock?
Click to expand...
Click to collapse
Meh...you know how it is bro....**it happens!
Call google and just tell them your device wont boot all of a sudden; they will probably ask you to factory restore in the recovery, say the phone wont get past the google image. They will RMA that boy for you. You totally bricked. For future reference if you unlock the bootloader, dont waste your time trying to lock it again. Should have just fastboot flashed a factory image in the bootloader and called it a day. Having a unlocked bootloader doesn't effect you in anyway negatively.
ArminasAnarion said:
Call google and just tell them your device wont boot all of a sudden; they will probably ask you to factory restore in the recovery, say the phone wont get past the google image. They will RMA that boy for you. You totally bricked. For future reference if you unlock the bootloader, dont waste your time trying to lock it again. Should have just fastboot flashed a factory image in the bootloader and called it a day. Having a unlocked bootloader doesn't effect you in anyway negatively.
Click to expand...
Click to collapse
Why is this Google's problem? This guy is at fault. Google shouldn't have to pay for it.
This is part of the reason these phones are so expensive.
Sent from my taimen using XDA Labs
mitchdickson said:
Why is this Google's problem? This guy is at fault. Google shouldn't have to pay for it.
This is part of the reason these phones are so expensive.
Sent from my taimen using XDA Labs
Click to expand...
Click to collapse
Well I never said it was the moral thing to do haha; but this guys best bet is to call Google and see if they will RMA it. They RMA'ed my Nexus 6p after the Android 7 twrp brick; and I told them my pone wouldn't boot anymore; they asked me to go to recovery and factory restore, I told them I couldn't boot into recovery and they RMA'ed it. It was my fault for the brick but they didn't care.
ArminasAnarion said:
Well I never said it was the moral thing to do haha; but this guys best bet is to call Google and see if they will RMA it. They RMA'ed my Nexus 6p after the Android 7 twrp brick; and I told them my pone wouldn't boot anymore; they asked me to go to recovery and factory restore, I told them I couldn't boot into recovery and they RMA'ed it. It was my fault for the brick but they didn't care.
Click to expand...
Click to collapse
Did you tell them it was your fault for the brick?
Sent from my taimen using XDA Labs
mitchdickson said:
Did you tell them it was your fault for the brick?
Sent from my taimen using XDA Labs
Click to expand...
Click to collapse
I told them I had an unlocked boot-loader and installed twrp. I had to send them back my old phone and they put a $500 hold on my account, once they received the device and determined the issue was real, they released the hold on my account. In that period of time they could have determined "Oh he bricked the device with twrp" lets charge him $500 for a new one, but they didn't. I mean whats wrong with calling Google and seeing if they will RMA it; sure the OP made a bad mistake but you have not because you ask not.
ArminasAnarion said:
I told them I had an unlocked boot-loader and installed twrp. I had to send them back my old phone and they put a $500 hold on my account, once they received the device and determined the issue was real, they released the hold on my account. In that period of time they could have determined "Oh he bricked the device with twrp" lets charge him $500 for a new one, but they didn't. I mean whats wrong with calling Google and seeing if they will RMA it; sure the OP made a bad mistake but you have not because you ask not.
Click to expand...
Click to collapse
What's wrong with it? You're telling him to call Google and say that for some reason, all the sudden his device won't boot.
This is why I don't fault Verizon for selling bootloader locked phones.
Sent from my taimen using XDA Labs