Related
Help!!!!
I bricked my phone with rom manager when i installed CWM over Rom manager i picked the wrong phone it was some huawei model my phone was ginger 2.3.4 galaxy mini stock rom
That's what happens when you don't know that rom manager bricks galaxy mini...
Go buy a new phone there nothong to do and now you know must not use ROM manager!
Sent from my GT-I9400 using XDA Premium
can you go into download mode
No way he can enter download mode when he flashed CWM for the wrong phone...
If you are aware you hard bricked your device, why are you calling for help? Hard bricks can only be repaired with JTAG, not something you can do at home.
time for a new phone... if it's hard bricked then just bin it and learn from you're mistake. remember research before you do anything with you're new phone.
If your phone is under warranty, go get it fixed in samsung service centre for free( Act innocent- say you set the alarm and your phone never started or rang in the morning)
If its not, say FML and use your phone as paper weight.
another victime of ROM MANAGERS ......lol
Never use ROM manager! Many people had brick with it!
Do you still have the guarantee? Go to SSC (Samsung Service Center).
Write a story and lied there. lol.
My friend do the similar thing with his Galaxy W, and got his part replaced by SSC. for free.
Damn!
OK guys im getting it to the ssc and ill tell you the results btw no download mode
LOL .
Sent from my GT-XPERIA S using xda premium
Many days back when I didn't know anything I was in same situation I was just about to press on any other phone model then I stopped my self , thought for a second and then decided not to do Anything without knowledge about it
Thank god my decision saved my lovely SGM
Sent from my Mobile Phone
lonestrider said:
Do you still have the guarantee? Go to SSC (Samsung Service Center).
Write a story and lied there. lol.
My friend do the similar thing with his Galaxy W, and got his part replaced by SSC. for free.
Click to expand...
Click to collapse
Sent from my GT-S5570 using Tapatalk 2
Lol n00bs :]
'Tom Manager' should be banned for g.mini. No?
wawingandroid said:
Help!!!!
I bricked my phone with rom manager when i installed CWM over Rom manager i picked the wrong phone it was some huawei model my phone was ginger 2.3.4 galaxy mini stock rom
Click to expand...
Click to collapse
Have you revived your phone?
I bricked my phone by using rom manager.
I can't boot normally nor enter recovery.
I can enter download mode but after I flashed stock roms by odin, nothing happened.
Anyone can help?
wm_shi said:
Have you revived your phone?
I bricked my phone by using rom manager.
I can't boot normally nor enter recovery.
I can enter download mode but after I flashed stock roms by odin, nothing happened.
Anyone can help?
Click to expand...
Click to collapse
Some useful info: Read before you bcrick your phone...
Sent from my GT-S5570 using Tapatalk 2
Xenagirl83 said:
Wow, I guess the guy who sold me his GT-S6500 must have done something like this, because the exact same things are happening to this phone. It's true: before using strange programs or downloading any firmware without being sure it will suit your phone model, you have to read all the appropriate guides, as other users just recommended before. Or just ask for help to someone with more experience. :fingers-crossed:
Now it's almost 3 days I'm trying to solve the problem with this poor Mini 2. I'm afraid the seller could have used that ROM Manager, and if it wasn't enough, he also destroyed the battery.
Remember that if the phone shows a boot loop with the samsung writings but it still can go into Download Mode (but not into Recovery), the phone isn't bricked yet. It's called "soft brick" but it's still recoverable.
If not, you have to buy a device called JTAG (expensive option) or build you own small "Jig" device (cheap option), following some guides you can find on Google. That will "resurrect" your phone. Good luck
Click to expand...
Click to collapse
As you said, my phone should be soft-bricked because it can still go into download mode.
But I can't revive it from flashing any stock rom via odin.
So it seems hard-bricked.
should not use rom manager if still using stock rom. especially in the rom manager menu choose reboot into recovery. do not do this you will galaxy mini hard brick. This is my experience. but if you still can get downloads in flash mode can be through odin. but if you can not get into download mode . take it to the samsung service centre
This is my experience
Sent from my GT-S5570 using xda app-developers app
Hello guys, today i have ported PhilZ recovery to General Mobile 4G which is an Android One Second Generation Phone. And i would like to share that with you on xda because after i flashed custom recovery there was an OTA update and unfortunately the custom recovery tried to install that OTA and before i backup stock rom it has bricked my General Mobile 4G. Now i need stock rom via other people's help. After that we will have stock rom and we can try to compile CM and other kinds of ROMs. So if anybody wants to help please pm me.
And if someone wants to use the PhilZ recovery:
http://meteberkergun.me/recovery-cwm.img
sad to hear that I do hope you resolve your problem right away btw sorry I don't have the 2nd gen device yet so I can't test your recovery
Today i went to a shop and borrowed a General Mobile 4G and at home backed it up and flashed it to my phone and it was successful. It went so smooth now I have recovered my phone.
Sadronis said:
Today i went to a shop and borrowed a General Mobile 4G and at home backed it up and flashed it to my phone and it was successful. It went so smooth now I have recovered my phone.
Click to expand...
Click to collapse
It's good to hear that. this phone deserves more developement!
Sadronis said:
Today i went to a shop and borrowed a General Mobile 4G and at home backed it up and flashed it to my phone and it was successful. It went so smooth now I have recovered my phone.
Click to expand...
Click to collapse
Hi Sadronis, Glad you got your phone successfully restored, This is jan 17 -2016, but I just read your thread , My problem is getting any custom recovery to install,,My phone is Cherry Mobile H220 (2nd gen), but after much playing about with it, it now works on IQii (thai version), ,On switching on , it shows the original G1 motto on screen,but in everything else in settings it shows it as IQii, Its now updated to latest upgrade (mmb28O), everything seems to be working as far as I can tell, but I just cant seem to get twrp into phone,, In device manager it shows that adb is working,, In portable devices in device manager, it says model H220, , so I think that part of windows operation is working ok, (drivers etc),,. I would like to install Philz recovery into phone, , I tried your link in first post, but link seems dead, ,Can you direct me to where I can download that version, that you used in General Mobile G4 ?, Hope You can help me in my search, Thank you Sir.
Hi there eveyone, thank you for reading this.
a friend of mine has an HTC Desire OPM1100 D626ph (says on the back of the phone)
when he tries to update to the newer version (the official way) He faces an error, the phone restarts and its stuck now on an endless loop. the options he had was htc recovery menu. he has tried all the options there in hope of fixing the problem.(he doesn't know english) and he probably ruined everything. now the phone doesn't have a back up, nothing works. ADB wasn't turned on in the begining. no fast boot. the only options i think i have is to download a rom via sdcard.(not even sure if it's external)
these are the options on the menu:
reboot system now:
apply update from adb
apply update from sdcard
apply update from cache
wipe /data/factory reset
wipe cache partition
backup user data
restore user data
any help on this would be appreciated, any ideas what should be my next step? i have history of using fastboot/adb. i don't know which rom i should download and from where? htc website confused me and the onlyy thread i found on the internet was this one and there are several links on there. not sure which one should i use?
thanks again guys.
Which carrier is he on? Also, we would need to know if it's a 626, 626s, 626x, 626g, etc... Not sure which model it is from the info posted above. If it's a 626s, the only way to recover is if it's a T-Mobile 626s (no other versions have an RUU to restore it to stock).
Sent from my HP SlateBook 10 x2 PC using Tapatalk
jtrosky said:
Which carrier is he on? Also, we would need to know if it's a 626, 626s, 626x, 626g, etc... Not sure which model it is from the info posted above. If it's a 626s, the only way to recover is if it's a T-Mobile 626s (no other versions have an RUU to restore it to stock).
Sent from my HP SlateBook 10 x2 PC using Tapatalk
Click to expand...
Click to collapse
thank you for your response
it's an HTC Desire 626G+ (dual sim) and the carrier is "Telecommunication Company of Iran"
Hmm - I would have him contact his carrier and see if they have an "RUU" available for that phone. An "RUU" is Windows application that will reset the phone back to the way it came from the factory - and can typically restore any phone - unless it has a hardware issue.
Otherwise, let's see if anyone else has any input (I'm not familiar with the 626g myself).
Sorry that I couldn't be more helpful!
Sent from my HP SlateBook 10 x2 PC using Tapatalk
jtrosky said:
Hmm - I would have him contact his carrier and see if they have an "RUU" available for that phone. An "RUU" is Windows application that will reset the phone back to the way it came from the factory - and can typically restore any phone - unless it has a hardware issue.
Otherwise, let's see if anyone else has any input (I'm not familiar with the 626g myself).
Sorry that I couldn't be more helpful!
Sent from my HP SlateBook 10 x2 PC using Tapatalk
Click to expand...
Click to collapse
i don't think the carrier would help out with this. though it made me think he didn't do anything wrong so do you think that warranty will accept the phone?
The carrier are the ones that need to supply the RUU (either directly or via HTC), which I why I mentioned that he should contact the carrier.
I would agree that it's a warranty issue if he we just trying to install an OTA update and it caused all of this...
Sent from my HP SlateBook 10 x2 PC using Tapatalk
i have same problem with D626ph. I was rooted phone with kingroot after this try to update with ota and result was error and phone boot only to recovery menu
Ahhh - yeah, if you are rooted (and unlocked bootloader), you cannot apply OTA updates. Although, usually, they fail right away and you can just boot right back into the phone normally (without the update, obviously). It's kinda strange that the OTA is bricking the phone like that.
Sent from my HP SlateBook 10 x2 PC using Tapatalk
i wasnt unlock bootloader. phone was trying updating itsef, but failed. cant revive anymore.
i was repair my phone after many hours by flashing with SP FLASH TOOL and with
this file:
https://mega.nz/#!qFgAUQTI
regards!
Cant download the file, post full link.
bossko said:
i wasnt unlock bootloader. phone was trying updating itsef, but failed. cant revive anymore.
i was repair my phone after many hours by flashing with SP FLASH TOOL and with
this file:
https ://mega .nz/#!qFgAUQTI
regards!
Click to expand...
Click to collapse
Your link requires an decryption key.
pl provide key. facing the same problem with htc 626g+. Updated via official OTA. Sad that they rolled it without thoroughly testing it.
Have you guys contacted HTC and/or the carrier? They should resolve this issue for you (via an RUU or some other means)!
Sent from my HP SlateBook 10 x2 PC using Tapatalk
diml0rd said:
Hi there eveyone, thank you for reading this.
a friend of mine has an HTC Desire OPM1100 D626ph (says on the back of the phone)
when he tries to update to the newer version (the official way) He faces an error, the phone restarts and its stuck now on an endless loop. the options he had was htc recovery menu. he has tried all the options there in hope of fixing the problem.(he doesn't know english) and he probably ruined everything. now the phone doesn't have a back up, nothing works. ADB wasn't turned on in the begining. no fast boot. the only options i think i have is to download a rom via sdcard.(not even sure if it's external)
these are the options on the menu:
reboot system now:
apply update from adb
apply update from sdcard
apply update from cache
wipe /data/factory reset
wipe cache partition
backup user data
restore user data
any help on this would be appreciated, any ideas what should be my next step? i have history of using fastboot/adb. i don't know which rom i should download and from where? htc website confused me and the onlyy thread i found on the internet was this one and there are several links on there. not sure which one should i use?
thanks again guys.
Click to expand...
Click to collapse
Check this out, hope it helps: http://forum.xda-developers.com/desire-626/help/fix-htc-desire-626g-update-command-t3243510
Guys thank you for your replies. I'm kinda new to xda forum. Should i reply one by one and quote people's names or just reply in one comment? Are there any rules?
About the post, it's weird that many people are experiencing the same problem! And where i live phone carriers don't care about phone problems and it's the first time I'm hearing that i should contact my carrier for my bricked device. But things are differently in different countries ?? to @tpr0 i might try your solution when i get my hands on the device againand if no one provides a better suggestion. Because i gave it back to my friend and told him to try the warranty. After a day turned out he has bought the device without a warranty! They sell phones without warranty in iran for a cheaper price. I think it's worth paying 50 more dollars for a 1-2 years warranty. Anyway I'll let you guys know as soon my friend returns his phone (which will be pretty soon I'm guessing. Meanwhile ill wait if anyone has a link for the ROM or a solution.
try this:
https://drive.google.com/file/d/0B-19rlZr42VQVzNzdEV2MkpQQzA/view?usp=sharing
can u tell me the procedure for working with this file ??
diml0rd said:
Hi there eveyone, thank you for reading this.
a friend of mine has an HTC Desire OPM1100 D626ph (says on the back of the phone)
when he tries to update to the newer version (the official way) He faces an error, the phone restarts and its stuck now on an endless loop. the options he had was htc recovery menu. he has tried all the options there in hope of fixing the problem.(he doesn't know english) and he probably ruined everything. now the phone doesn't have a back up, nothing works. ADB wasn't turned on in the begining. no fast boot. the only options i think i have is to download a rom via sdcard.(not even sure if it's external)
these are the options on the menu:
reboot system now:
apply update from adb
apply update from sdcard
apply update from cache
wipe /data/factory reset
wipe cache partition
backup user data
restore user data
any help on this would be appreciated, any ideas what should be my next step? i have history of using fastboot/adb. i don't know which rom i should download and from where? htc website confused me and the onlyy thread i found on the internet was this one and there are several links on there. not sure which one should i use?
thanks again guys.
Click to expand...
Click to collapse
Im facing the same problem with desire 626 dual sim,after update phone back me to the recovery menu and giving me message update fail.After phone reboot stuck me on recovery menu and thats is. With 2 hours reading forums,the only way was to flash stock rom via Spflash tool..Afterall banned update from phone ! I dont know why is that issues if someone knows tha answer please let tell us ?
If you're using a phone from Iran I think you have bigger things to worry about.
Good evening from Indonesia guys, okay i've post my problem here before, this is my last post about my problem http://forum.xda-developers.com/showthread.php?t=2768357 , it's about 2 years ago, and now i'm still working hard to find the way how to unbrick my Gnote, i've tried so many way on Google, but there is no result again (like 2 years ago), okay guys, i'm give up for 1 years about my problem, but now i think there is still a way for me to unbrick my Gnote, can you guys help me??
My Gnote problem :
My Gnote stuck on "Samsung Galaxy Note GT-N7000" logo
I've back up my data using Clockworkmod (CWM Recovery) before it's bricked, and i have a copy on my Laptop
I can go to Download Mode
I Can't go to Recovery Mode, my recovery mode was TWRP
When i go to Recovery Mode, its stuck in "TEAMWIN" logo
I can charge my Gnote
My Gnote was unidentified on Samsung Kies
But my Gnote still can be read on Odin or Heimdall
I hope you guys tell me what i have to do to resolve this phone, and give me a solution for my Gnote problem, i know its too late, and you guys asking me about why i don't buy another one after its bricked for 2 years? its because my Gnote was my dad's present when i got a scholarship on junior high school, and i'm so appreciate this present, Thank you guys for the time, sorry about my english, and sorry if I violate the rules of this forum....
Faprillah said:
Good evening from Indonesia guys, okay i've post my problem here before, this is my last post about my problem http://forum.xda-developers.com/showthread.php?t=2768357 , it's about 2 years ago, and now i'm still working hard to find the way how to unbrick my Gnote, i've tried so many way on Google, but there is no result again (like 2 years ago), okay guys, i'm give up for 1 years about my problem, but now i think there is still a way for me to unbrick my Gnote, can you guys help me??
My Gnote problem :
My Gnote stuck on "Samsung Galaxy Note GT-N7000" logo
I've back up my data using Clockworkmod (CWM Recovery) before it's bricked, and i have a copy on my Laptop
I can go to Download Mode
I Can't go to Recovery Mode, my recovery mode was TWRP
When i go to Recovery Mode, its stuck in "TEAMWIN" logo
I can charge my Gnote
My Gnote was unidentified on Samsung Kies
But my Gnote still can be read on Odin or Heimdall
I hope you guys tell me what i have to do to resolve this phone, and give me a solution for my Gnote problem, i know its too late, and you guys asking me about why i don't buy another one after its bricked for 2 years? its because my Gnote was my dad's present when i got a scholarship on junior high school, and i'm so appreciate this present, Thank you guys for the time, sorry about my english, and sorry if I violate the rules of this forum....
Click to expand...
Click to collapse
Soft-bricked is good, download mode and Odin recognisable is better so don't worry we can fix this for you. First though, your English is understandable so keep it up and you didn't violate anything. You even posted in the correct section so +5 for reading.
Looks like your recovery is broken so you need to first make sure your phone is boot-able. Therefore Odin flash a stock rom (this uses the download mode) to reset everything. From there, two ways are available to install recovery, stock update or Odin flash again so choose which one suits you best. Don't use the old KitKat roms (except NightOwl) since they're unsupported. Stable ones are NightOwl roms as it's still in active development.
AutumQueen92 said:
Soft-bricked is good, download mode and Odin recognisable is better so don't worry we can fix this for you. First though, your English is understandable so keep it up and you didn't violate anything. You even posted in the correct section so +5 for reading.
Looks like your recovery is broken so you need to first make sure your phone is boot-able. Therefore Odin flash a stock rom (this uses the download mode) to reset everything. From there, two ways are available to install recovery, stock update or Odin flash again so choose which one suits you best. Don't use the old KitKat roms (except NightOwl) since they're unsupported. Stable ones are NightOwl roms as it's still in active development.
Click to expand...
Click to collapse
Thank you so much for being honest, i'm so appreciate it, okay, i've flash so many recovery system (like Philztouch), but it still stuck in TEAMWIN logo, and there is no result, and i've flash another stock rom from sammobile, i choose the one for Indonesia region, but still no result, there is no difference, or should i try to flas the ginger bread stock rom??i try so many times to find another Dr Ketan Ginger bread stock rom, because the website where he upload the data (hotfile.com) were not open in indonesia (it has been blocked for a reason) so i have to find another website that provide the data, and there is no result again, or might be it's caused by the hardware or not??
Faprillah said:
Thank you so much for being honest, i'm so appreciate it, okay, i've flash so many recovery system (like Philztouch), but it still stuck in TEAMWIN logo, and there is no result, and i've flash another stock rom from sammobile, i choose the one for Indonesia region, but still no result, there is no difference, or should i try to flas the ginger bread stock rom??i try so many times to find another Dr Ketan Ginger bread stock rom, because the website where he upload the data (hotfile.com) were not open in indonesia (it has been blocked for a reason) so i have to find another website that provide the data, and there is no result again, or might be it's caused by the hardware or not??
Click to expand...
Click to collapse
Right now you ignore all of that. Odin flash a stock rom from sammobile, then install the correct recovery based on your stock ROM from this thread http://forum.xda-developers.com/showthread.php?t=1901191. Get the Jellybean rom, it's safer and easier.
I'll gladly leave lg g4 forum been the most un helpful experience ever between 140 views on both threads ..and even from the most recognized devs with nothing but simplistic answers and guides that ive read already yet the needed answers are known ..... must be considered extra work to explain and help out with my indepth matter .The minute you run across a forum with someone who had this issue almost exactly they say oh edit...fixed now .
But the most stupidest of questions can get answered on here .
Had to waist money on a nexus 5x all cause no one can explain how this great Lg up tool works but apparently it is a botched process if your device shows as Unknown model with no fix no in depth explanation Lg bridge does not work for a true soft brick it only meant to upgrade a device that actually as a bootable O.S
So where does that leave me
Sent from my Nexus 5X using XDA Free mobile app
Did you post your issue in the official LG UP thread or in the back to stock marshmallow kdz thread where the file that you need to get this back to stock using LG Up is listed. If you would have searched in the kdz back to stock thread you would have seen that another user helped me with the exact same issue ss you. Was ready to turn my phone in for warranty before finding my answer there. Your phone is still able to boot into recovery manually but you have to do it a few times then you install a rom that's saved on your sd card and your phone will boot up. Hopefully you still have your G4 and can try this method.
Sent from my LG-H811 using Tapatalk
srod562 said:
Did you post your issue in the official LG UP thread or in the back to stock marshmallow kdz thread where the file that you need to get this back to stock using LG Up is listed. If you would have searched in the kdz back to stock thread you would have seen that another user helped me with the exact same issue ss you. Was ready to turn my phone in for warranty before finding my answer there. Your phone is still able to boot into recovery manually but you have to do it a few times then you install a rom that's saved on your sd card and your phone will boot up. Hopefully you still have your G4 and can try this method.
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
Really I'm thinking not explain to me how my lg g4 phone can boot into recovery manually when i relocked the boot loader through adb.
All I have is down load mode No regular O.s boot no fast boot mode
Its all secure boot error 1003
I download the kdz 20i from auto primes code fire link that's the only kdz for 20i around .
The issue is lg up tool sees my device as Unknown model because I was on a ROM when this happened apparently there's no fix unless you can boot into the O.s and edit the ROM
Sent from my Nexus 5X using XDA Free mobile app
srod562 said:
Did you post your issue in the official LG UP thread or in the back to stock marshmallow kdz thread where the file that you need to get this back to stock using LG Up is listed. If you would have searched in the kdz back to stock thread you would have seen that another user helped me with the exact same issue ss you. Was ready to turn my phone in for warranty before finding my answer there. Your phone is still able to boot into recovery manually but you have to do it a few times then you install a rom that's saved on your sd card and your phone will boot up. Hopefully you still have your G4 and can try this method.
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
What do you mean a few times power and volume down and release power and press it again then choose wipe with YES
Yea I tried all that its secure boot error because my boot loader is re-Locked while I was rooted and with twrp
Sent from my Nexus 5X using XDA Free mobile app
I'm wanting to believe that I need to just forget I have the g4 and break it in 3 half's and toss it
So the headache goes away
Sent from my Nexus 5X using XDA Free mobile app
androidddaaron said:
I'll gladly leave lg g4 forum been the most un helpful experience ever between 140 views on both threads ..and even from the most recognized devs with nothing but simplistic answers and guides that ive read already yet the needed answers are known ..... must be considered extra work to explain and help out with my indepth matter .The minute you run across a forum with someone who had this issue almost exactly they say oh edit...fixed now .
But the most stupidest of questions can get answered on here .
Had to waist money on a nexus 5x all cause no one can explain how this great Lg up tool works but apparently it is a botched process if your device shows as Unknown model with no fix no in depth explanation Lg bridge does not work for a true soft brick it only meant to upgrade a device that actually as a bootable O.S
So where does that leave me
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
I actually posted my solution in the 20I thread relatively early. I am sorry no one helped you sooner.
If you used an iternational Rom and have an unrecognized model LGBridge is able to update your phone through update error recovery.
Vseprz said:
I actually posted my solution in the 20I thread relatively early. I am sorry no one helped you sooner.
If you used an iternational Rom and have an unrecognized model LGBridge is able to update your phone through update error recovery.
Click to expand...
Click to collapse
0fx
This is impossible lg bridge is not a semi brick or full brick fix tool its a upgrade tool from what I see
lts for a device that's in a bootable operating state allowing firmware upgrade .
It can only read in a device in mtp mode If you only have download mode that doesn't help at all Withp lg bridge The unknown device model issue is only seen with the Other tool Caller Lg up.
I go on and on and on and noone takes my exact scenario and breaks it down .
Sent from my Nexus 5X using XDA Free mobile app
androidddaaron said:
0fx
This is impossible lg bridge is not a semi brick or full brick fix tool its a upgrade tool from what I see
lts for a device that's in a bootable operating state allowing firmware upgrade .
It can only read in a device in mtp mode If you only have download mode that doesn't help at all Withp lg bridge The unknown device model issue is only seen with the Other tool Caller Lg up.
I go on and on and on and noone takes my exact scenario and breaks it down .
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
Did you even try it? My phone was in the 1003 boot error with unknown model in LGUp. I only had download mode. Give it a shot before you dismiss it.
Vseprz said:
Did you even try it? My phone was in the 1003 boot error with unknown model in LGUp. I only had download mode. Give it a shot before you dismiss it.
Click to expand...
Click to collapse
I did once I couldn't get bridge to connect with update recovery error
Then difference here is was you boot loader relocked or still unlocked mine is re locked in this state
Sent from my Nexus 5X using XDA Free mobile app
androidddaaron said:
I did once I couldn't get bridge to connect with update recovery error
Then difference here is was you boot loader relocked or still unlocked mine is re locked in this state
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
Actually my bootloader was locked at the point I used LGBridge.
Not being able to connect suggests driver problems. Reload them and try again.
Vseprz said:
Actually my bootloader was locked at the point I used LGBridge.
Not being able to connect suggests driver problems. Reload them and try again.
Click to expand...
Click to collapse
So you had twrp plus rooted and relocked boot loader all before attempting lg bridge that's my exact scenario but what about bridge trying to install then Lg bridge AIR Drivers
Sent from my Nexus 5X using XDA Free mobile app
Vseprz said:
Actually my bootloader was locked at the point I used LGBridge.
Not being able to connect suggests driver problems. Reload them and try again.
Click to expand...
Click to collapse
No that's not true I guarantee you wasn't
Relocked boot loader u couldn't have been
I am for sure about this and lg bridge sees my device when I choose update recovery error it tells me there are No update errors that can be recovered
So how does that prove it fixed yours when we was in the same scenario?
Sent from my Nexus 5X using XDA Free mobile app
androidddaaron said:
No that's not true I guarantee you wasn't
Relocked boot loader u couldn't have been
I am for sure about this and lg bridge sees my device when I choose update recovery error it tells me there are No update errors that can be recovered
So how does that prove it fixed yours when we was in the same scenario?
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
I made a mistake when upgrading my phone from LP to MM and accidentally left my Bootloader locked when trying to upgrade, nearly bricking my phone. I was receiving a 1003 error every time I tried to boot. I posted this in a different thread last month for someone else who had the same problem.
I had this exact same issue when upgrading my phone. Didn't do it correctly and it took me about 3 hours before I got my phone working again. It was about a week ago on another computer, but I'll try to recall what I did when it finally clicked in my mind.
Download H81120i_00_0201.kdz flashable zip from here (1.6GB Feb-04-16):
http://downloads.codefi.re/autoprime.../H811/H81120i/
Download LGUP and install it. I used the DropBox link in this thread:
http://forum.xda-developers.com/g4/h...mm-lp-t3249803
Remember to install the LGUP_8994_DLL file BEFORE LGUP_Install
Download and install LG Bridge (for the USB drivers) here:
http://www.lg.com/uk/support/pc-suite
Select the LG 815 model, the drivers will work. I only used the LG Bridge to install the USB drivers. Nothing else.
OK, now here's where your phone comes in.
Step 1: Turn off your phone (pull the battery if you must, but put it back in).
Step 2: Hold the VOLUME UP button and plug the USB cable into your PC. This puts your phone into DOWNLOAD MODE.
Step 3: On your PC, open up LGUP. The program shoud recognize the phone as H811 in COM3 or COM4. Highlight it and click the SELECT button.
Step 4: Under the "Process" row, select UPGRADE
Step 5: Click the blank space under File Path, it will pop up a [...] [X] at the end. Click the [...].
Step 6: Select the H81120i_00_0201.kdz and click on Start. The program will push the STOCK H811 MM ROM to your phone. This will bring your phone out of Brick mode, but you will have to go through the entire rooting process again.
Click to expand...
Click to collapse
Donut42 said:
I made a mistake when upgrading my phone from LP to MM and accidentally left my Bootloader locked when trying to upgrade, nearly bricking my phone. I was receiving a 1003 error every time I tried to boot. I posted this in a different thread last month for someone else who had the same problem.
Click to expand...
Click to collapse
Once again I was on a ROM when in did all this if it wasn't for that fact Lg Up would see my device model as h11 not unknown
So tell me how to get past the Unknown device model issue due to bring on a Custom Rom when this happened
Sent from my Nexus 5X using XDA Free mobile app
Donut42 said:
I made a mistake when upgrading my phone from LP to MM and accidentally left my Bootloader locked when trying to upgrade, nearly bricking my phone. I was receiving a 1003 error every time I tried to boot. I posted this in a different thread last month for someone else who had the same problem.
Click to expand...
Click to collapse
The issue lies in step 3
The phone doesn't recognize as h811 it is as unknown model
If you know a way around that I'd love to know because every day I Go to snap the phone in half and recycle it as trash I stop my self thinking maybe one person will get that I was on a ROM when this happened and have a solution for Lg up to see my device as h811
Sent from my Nexus 5X using XDA Free mobile app
androidddaaron said:
The issue lies in step 3
The phone doesn't recognize as h811 it is as unknown model
If you know a way around that I'd love to know because every day I Go to snap the phone in half and recycle it as trash I stop my self thinking maybe one person will get that I was on a ROM when this happened and have a solution for Lg up to see my device as h811
Sent from my Nexus 5X using XDA Free mobile app
Click to expand...
Click to collapse
That sounds like a driver issue. When I did mine I was also on a custom ROM. I had to manually remove all LG drivers via the Device Manager and install the LG Bridge for its LG USB drivers before the LGUP tool would recognize it. Before I did that it wouldn't even see my phone.
Donut42 said:
That sounds like a driver issue. When I did mine I was also on a custom ROM. I had to manually remove all LG drivers via the Device Manager and install the LG Bridge for its LG USB drivers before the LGUP tool would recognize it. Before I did that it wouldn't even see my phone.
Click to expand...
Click to collapse
I would like to think that butt LG up is evidently seeing a connection from my phone to the PC it's just reading the device model as unknown because if I unplug the phone it goes back to reading nothing I plug it back in pops up red box model unknown I know it's reading the phone in LG up because it actually tells you the ROM it detects which is Xtreme ROM by micro mod
Not only that LG Mobile support tool read my phone and says software is up-to-date LG flash tool 2014 attempts to flash but fails because it is not compatible apparently with Android 6.0
Nlg bridge when I try to use that tool sees my phone when I choose update recovery error and says there are no recoveries to update I don't believe it's a driver issue I think it's the fact that I'm stuck on a ROM that is edited in some fashion that will not allow the tool to to proceed to the next step and if you look at the LG up thread it talks about a member explaining about the unknown device model issue is due to the ROM developer editing his ROM name somehow
Everyone that has gotten past the unknown device model happen to have an unlocked bootloader or was just trying to do a regular upgrade and still had an OS to boot into there's just no way around this mess
Sent from my Nexus 5X using XDA Free mobile app
Guess this thread has run its course
Closed at OP's request