Database Develop

[BRICKED] I managed to brick my N4 just 12hours after purchase

Hi all,
The day before yesterday I decided to move from my GNex to the new N4, but my time with it was short, because I have managed to accomplish an incredible feat: brick a N4 just 12hours after purchase :laugh:.
Now, I'm not creating this topic to moan about it, I'm fully aware that bricking is a possibility for every flash, and the phone is already sent back to LG. I just want to tell you all what I did, so we can, possibly, find what I did wrong and help other people to avoid it :highfive:. And a little bit of background, I got Gnex for a year, before that is a G1, with flashing almost become a daily job (not so with the Gnex, as I prefer the stock experience, but still a lot of rom switching and kernel flashing every few months).
My N4, right of the bat, I put it into fastboot unlock, root (the usual thingies). It's still working as normal, but the battery life is not so stellar, so I decided to try franco's kernel. I flashed r53 to my phone, it boot up normally, I feel the performance is too slow compare to stock, so I flashed the latest test version r61, too. It's still working without a hitch, abeit not as smooth as stock.
So I decided to get back to stock. I'm too lazy to do fastboot with stock image, so I download the stock kernel CWM package from this topic, and just to be safe, I flashed faux's kernel reset from here before that. The flashing was succeed, no error, but when I reboot, the phone failed to boot up, just black screen. If I plug it into my computer, it show up as qhsusb_dload, which is a telltale sign of a corrupt internal memory aka definite brick.
To put it short, the sequel is: stock -> unlock -> root -> franco r53 -> franco r61 -> faux reset -> stock kernel flash -> brick.
I guess I did something wrong between the faux reset and stock kernel flashing. can anyone tell me what I did wrong? I did happen to flash wrong kernel build on my Gnex before but the worst I got is a boot loop, not straight up brick like this. And I'm very surprised that a core part of the phone (fastboot) can be corrupted that easy.
And, flash safely :good:

interesting, ive been having problems with my kernel, and used faux reset plenty of times. hopefully someone can chime in for you. Mine is still up and running with faux kernel too

I swear this phone is getting bricked a lot more than a y other nexus
Sent from my Nexus 4 using Tapatalk 2

italia0101 said:
I swear this phone is getting bricked a lot more than a y other nexus
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I swear you are a complete moron.
As for the OP's problem download nexus tool kit , Put the phone in bootloader mode and flash stock factory image.

italia0101 said:
I swear this phone is getting bricked a lot more than a y other nexus
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Are u serious Every phone has a chance of that alot of times
Soon To Be A Nexie

berz said:
I swear you are a complete moron.
As for the OP's problem download nexus tool kit , Put the phone in bootloader mode and flash stock factory image.
Click to expand...
Click to collapse
Yea ... im a complete moron.. iv not seen this " red light " problem with any other Nexus device, have you? of course i know theres a chance of bricking with anything , but iv never seen a nexus device die so easily just by running a benchmark ?!? thats all im saying
i know this isnt the problem the op is having , but its just strange..
either way , maybe chill out a bit before you start pulling out the names yea...

I want to chime in ^_^
I think the kernel reset screwed everything up IMO. I think there was maybe some left over files on the ram disk that didn't get wiped out 100% (I'm assuming you didn't wipe completely, regardless of a kernel reset) and when you flashed stock kernel it couldn't rearrange them correctly and you ended up with a bricked device.
Just my thoughts.
Sent from my Nexus 4 using xda app-developers app

when going back to stock just flash the factory image. it is very easy once you have the files and learn how to do it and always work,

juliano_q said:
when going back to stock just flash the factory image. it is very easy once you have the files and learn how to do it and always work,
Click to expand...
Click to collapse
Bricking Nexus? lol? this is a joke? just reinstall the stock firmware and you're done.
as long as u didnt fscked up the bootloader or the partition scheme then you shall be not affraid and its fairly easy to recover.
Adam

Any chance you flashed N7 kernel? Read somewhere that the kernel partition of N7 has same id as bootloader partition of N4. So what happens is kernel overwrites the bootloader resulting in brick.
Sent from LG Google Nexus 4 using XDA Premium

AdamLange said:
Bricking Nexus? lol? this is a joke? just reinstall the stock firmware and you're done.
as long as u didnt fscked up the bootloader or the partition scheme then you shall be not affraid and its fairly easy to recover.
Adam
Click to expand...
Click to collapse
I still dont have my N4 but I always thought this. Coming from previous devices the only reason Ive seen a true brick is someone screwing up flashing radios or dicking with the boot-loader. I didn't think you could actually brick a device with ROMS/Kernels.

linh1987 said:
Hi all,
The day before yesterday I decided to move from my GNex to the new N4, but my time with it was short, because I have managed to accomplish an incredible feat: brick a N4 just 12hours after purchase :laugh:.
Click to expand...
Click to collapse
Power off. Hold "volume down" and press power button. This should get you to the bootloader. If it does, your phone is not bricked and there's loads of info on here to put it right again (stock factory image would be my first call here). If it doesn't work, I'd be tempted to remove the battery (IIRC, quite easy once you remove the screws at the bottom) and repeat the above instructions. (if you can get to the bootloader one way or another, your phone is most certainly not bricked!)
If this doesn't work, it's probably dead and you'll need to send back.
Daern
---------- Post added at 01:34 PM ---------- Previous post was at 01:27 PM ----------
berz said:
I swear you are a complete moron.
Click to expand...
Click to collapse
Didn't your mother ever teach you - "If you can't say anything nice, say nothing at all"?
This is not a site for trolling. Please go away.

I flashed different kernels many many times.
Never a problem.
OP should check for human error instead of blaming the device.
Sent from my Nexus 4 using xda premium

atulalvenkar said:
Any chance you flashed N7 kernel? Read somewhere that the kernel partition of N7 has same id as bootloader partition of N4. So what happens is kernel overwrites the bootloader resulting in brick.
Sent from LG Google Nexus 4 using XDA Premium
Click to expand...
Click to collapse
Sorry but i don't know what are you talking about ? what the same ID as bootloader? erm?
partition name in case of bootloader is bootloader, for case of kernel is boot
Adam

linh1987 said:
Hi all,
The day before yesterday I decided to move from my GNex to the new N4, but my time with it was short, because I have managed to accomplish an incredible feat: brick a N4 just 12hours after purchase :laugh:.
Now, I'm not creating this topic to moan about it, I'm fully aware that bricking is a possibility for every flash, and the phone is already sent back to LG. I just want to tell you all what I did, so we can, possibly, find what I did wrong and help other people to avoid it :highfive:. And a little bit of background, I got Gnex for a year, before that is a G1, with flashing almost become a daily job (not so with the Gnex, as I prefer the stock experience, but still a lot of rom switching and kernel flashing every few months).
My N4, right of the bat, I put it into fastboot unlock, root (the usual thingies). It's still working as normal, but the battery life is not so stellar, so I decided to try franco's kernel. I flashed r53 to my phone, it boot up normally, I feel the performance is too slow compare to stock, so I flashed the latest test version r61, too. It's still working without a hitch, abeit not as smooth as stock.
So I decided to get back to stock. I'm too lazy to do fastboot with stock image, so I download the stock kernel CWM package from this topic, and just to be safe, I flashed faux's kernel reset from here before that. The flashing was succeed, no error, but when I reboot, the phone failed to boot up, just black screen. If I plug it into my computer, it show up as qhsusb_dload, which is a telltale sign of a corrupt internal memory aka definite brick.
To put it short, the sequel is: stock -> unlock -> root -> franco r53 -> franco r61 -> faux reset -> stock kernel flash -> brick.
I guess I did something wrong between the faux reset and stock kernel flashing. can anyone tell me what I did wrong? I did happen to flash wrong kernel build on my Gnex before but the worst I got is a boot loop, not straight up brick like this. And I'm very surprised that a core part of the phone (fastboot) can be corrupted that easy.
And, flash safely :good:
Click to expand...
Click to collapse
If you took the same amount of time to search that you took to write this terrible OP you would have already fixed your phone....

tweaked said:
If you took the same amount of time to search that you took to write this terrible OP you would have already fixed your phone....
Click to expand...
Click to collapse
Hey tweaked, thanks for your contribution, but if you take 5 secs to search for a black screen issue with qhsusb_dload show up in windows, you will know that I went to a dead end.
@all: yes it's 100% my fault, I just double check and I DID flash grouper (aka N7) kernel to my N4, but I just feel it's so much easier to flash N7 kernel to N4 without any error. And again, I just want to repeat that I'm not moaning about it, it's totally my fault. I just want to help other people to avoid it :highfive:

atulalvenkar said:
Any chance you flashed N7 kernel? Read somewhere that the kernel partition of N7 has same id as bootloader partition of N4. So what happens is kernel overwrites the bootloader resulting in brick.
Sent from LG Google Nexus 4 using XDA Premium
Click to expand...
Click to collapse
Hey atulalvenkar, yes, I just did what you say. How stupid I'm. Guess we learn new thing every day

linh1987 said:
Hey atulalvenkar, yes, I just did what you say. How stupid I'm. Guess we learn new thing every day
Click to expand...
Click to collapse
You are the first person I heard that flashed a wrong KERNEL.
Congratz.
Sent from my Nexus 4 using xda premium

linh1987 said:
Hey atulalvenkar, yes, I just did what you say. How stupid I'm. Guess we learn new thing every day
Click to expand...
Click to collapse
Saw couple of posts on reddit where many people did the same thing. The problem is franco develops for both N7 and N4 and his XDA thread subject doesn't have any indication of the device. Because of this it's easy to get pointed to the wrong thread and download wrong kernel.

My phone bricked spontaneously. I had installed CM 10.1, with the stock kernel, about 12 hours earlier and was actually browsing facebook when the phone spontaneously rebooted. I could get into fastboot, but no matter what I tried, I couldn't flash a stable recovery or full image. Constant boot loops with the occasional successful system boot, only to reboot within a few seconds.. starting the whole process over again.
Flashed and formatted every accessible partition, followed every "how to" I could find. Absolutely no success. Luckily Google sent me a replacement and I had a new phone in 2 days. Running the same CM 10.1/stock kernel now, no issues.
My first phone (a Rev_11) always ran somewhat hot, and the battery wouldn't last a day. The replacement phone (also a Rev_11) runs much cooler and the battery lasts for 2 days easy, with the exact same software. I'm thinking the old phone just somehow toasted itself. Just speculation. Oh, the old phone was also a "slow" binned CPU.
Anyway, the point of my story is that is ISN'T entirely true that the ability to boot into bootloader/fastboot will guarantee you success when trying to resurrect a dead phone.

[Q] help!!!

Hello! I use Google translation, I do not know where I wrote) get to the point I have a very buggy phone does not know what to do ... I have nothing to firmware and kernel did not help ((who knows what to do tell me

benn9 said:
Hello! I use Google translation, I do not know where I wrote) get to the point I have a very buggy phone does not know what to do ... I have nothing to firmware and kernel did not help ((who knows what to do tell me
Click to expand...
Click to collapse
I believe we are getting lost in translation so to speak, let's try for a little more information.
Have you unlocked your boot loader?
Have you rooted your device?
Have put a custom kernel on your device? If so which?
Have you put custom firmware on your device? If so which?
When you say your phone is buggy, that is very vague. What exactly are the issues your experiencing? Is it rebooting, or is it not making to the boot animation and starting at all? Or is this more of a lag issue, feels sluggish and certain applications force close or cause the phone to restart. Have you had issues with the device prior to flashing, if you have flashed a custom firmware already?
With a little more information I'm sure there are a lot of people on the forums that are able to help, but without a little bit of detail as to whats going on the best anyone can say is the standard tech support response: Did you turn the device off and back on again. And I assume that is not the answer you are looking for.

1
barbrick said:
I believe we are getting lost in translation so to speak, let's try for a little more information.
Have you unlocked your boot loader?
Have you rooted your device?
Have put a custom kernel on your device? If so which?
Have you put custom firmware on your device? If so which?
When you say your phone is buggy, that is very vague. What exactly are the issues your experiencing? Is it rebooting, or is it not making to the boot animation and starting at all? Or is this more of a lag issue, feels sluggish and certain applications force close or cause the phone to restart. Have you had issues with the device prior to flashing, if you have flashed a custom firmware already?
With a little more information I'm sure there are a lot of people on the forums that are able to help, but without a little bit of detail as to whats going on the best anyone can say is the standard tech support response: Did you turn the device off and back on again. And I assume that is not the answer you are looking for.
Click to expand...
Click to collapse
Yes, I unlocked bootloader
yes I have is Nameless Rom v7.3
yes I have a hard core at 800MHz
I mean such as logs: twitching, brakes, very long time thinking ...
it happened a month ago, I thought, and did not bother about it, and now I do not like it.
HELP ME PLEASE

You tried flashing ruu? I also had this problem I solved it with ruu but for ruu to work I had to relock the boot loader! You just have to connect your phone in bootloader mode open adb and type fastboot oem lock. Then just install latest ruu!
Sent from my HTC Desire C using xda premium

benn9 said:
Yes, I unlocked bootloader
yes I have is Nameless Rom v7.3
yes I have a hard core at 800MHz
I mean such as logs: twitching, brakes, very long time thinking ...
it happened a month ago, I thought, and did not bother about it, and now I do not like it.
HELP ME PLEASE
Click to expand...
Click to collapse
Honestly, my device won't run the 806 Kernel, and has lots of trouble running the 767 Kernel, it seems some Desire C devices were made to a higher quality than others, looks like I got a Friday Phone!
Did you have it running successfully on the 806 Kernel previously?
On my device the 722 runs smoother than the 600, so I would try flashing that or the 600 stock Kernel and see if that resolves the issues.

1
noahvt said:
you tried flashing ruu? I also had this problem i solved it with ruu but for ruu to work i had to relock the boot loader! You just have to connect your phone in bootloader mode open adb and type fastboot oem lock. Then just install latest ruu!
Sent from my htc desire c using xda premium
Click to expand...
Click to collapse
thank you kind help! further not know what will

[Q] HTC One gaming no luck help

Hi there,
I have tried everything from custom roms to different kernals to scripts to try fix stutter lag in games, i even tried benchmarks and my gpu is having problems with everything, sonic dash as an example constant fps issues, benchmarks im only getting say 20 fps while other phones are around 50-60 fps. I am lost for ideas there must be something?

georgetbt said:
Hi there,
I have tried everything from custom roms to different kernals to scripts to try fix stutter lag in games, i even tried benchmarks and my gpu is having problems with everything, sonic dash as an example constant fps issues, benchmarks im only getting say 20 fps while other phones are around 50-60 fps. I am lost for ideas there must be something?
Click to expand...
Click to collapse
So have you modded your GPU UI rendering during any flashing? Might be the reason, try to re-flash your rom, or another (viper and ARHD are the ones i've used) one good luck

THeHopelessPainter said:
So have you modded your GPU UI rendering during any flashing? Might be the reason, try to re-flash your rom, or another (viper and ARHD are the ones i've used) one good luck
Click to expand...
Click to collapse
lots of things could be wrong.. did you change your GPU speed? are you running power saver mode.? do you have always draw in 2D setup in developer mode settings? have you tried a fresh wipe?

syaoran68 said:
lots of things could be wrong.. did you change your GPU speed? are you running power saver mode.? do you have always draw in 2D setup in developer mode settings? have you tried a fresh wipe?
Click to expand...
Click to collapse
This was happening before i modded my phone, i thought this would fix it, the steps i have taken are: fully factory reset, full wipe even wiped every folder there was including my OS ... oops! tried2 ROMSs, now using Viper 5.7.0
checked developer option it isn't forcing 2D. tried scripts for GPU with smanager that done nothing lol, using vipers stock that came with 5.7.0 also tried the ARHD

georgetbt said:
This was happening before i modded my phone, i thought this would fix it, the steps i have taken are: fully factory reset, full wipe even wiped every folder there was including my OS ... oops! tried2 ROMSs, now using Viper 5.7.0
checked developer option it isn't forcing 2D. tried scripts for GPU with smanager that done nothing lol, using vipers stock that came with 5.7.0 also tried the ARHD
Click to expand...
Click to collapse
your last bet is to RUU and see if that will work. then after you can reflash any rom but thats about the best i can offer you if you've flashed other roms and updated and checked of everything else.

syaoran68 said:
your last bet is to RUU and see if that will work. then after you can reflash any rom but thats about the best i can offer you if you've flashed other roms and updated and checked of everything else.
Click to expand...
Click to collapse
Yep tried the RUU, no luck my brothers iphone 4s runs games better, either this phone has a bad gpu chip or the phones faulty? very disappointed.

georgetbt said:
Yep tried the RUU, no luck my brothers iphone 4s runs games better, either this phone has a bad gpu chip or the phones faulty? very disappointed.
Click to expand...
Click to collapse
like you said the issue was there before you modded your phone, so im guessing it is a bad processor. How old is your One? And has this issue been present since you got your phone?

yea then i would totally get it replaced under warranty if you still have it. thats your last option.

syaoran68 said:
yea then i would totally get it replaced under warranty if you still have it. thats your last option.
Click to expand...
Click to collapse
ok thanks

Q&A for [KERNEL][ROOT]The Ultimate Kernel for the HTC Desire 500

Q&A for [KERNEL][ROOT]The Ultimate Kernel for the HTC Desire 500
Finally mine!

kernel with a record of the line
hello dear! and you could not build a kernel with a record of the line, it is very necessary! many will be grateful!
---------- Post added at 02:20 PM ---------- Previous post was at 01:59 PM ----------
hello! and you could not build a kernel with a record of the line, it is very necessary! many will be grateful!

Is it possible add thermal control, fiops scheduler etc. to the kernel?

anatoly72 said:
hello dear! and you could not build a kernel with a record of the line, it is very necessary! many will be grateful!
---------- Post added at 02:20 PM ---------- Previous post was at 01:59 PM ----------
hello! and you could not build a kernel with a record of the line, it is very necessary! many will be grateful!
Click to expand...
Click to collapse
To hard.
blitzzkrieg said:
Is it possible add thermal control, fiops scheduler etc. to the kernel?
Click to expand...
Click to collapse
Thermal control is done by thermald (/system/bin/thermald), I'm pretty happy with it.
fiops is already there
btw with two junior members posting in my thread, you triggered something that automatically added a Q&A forum, so my kernel thread is now a fancy devdb thread

dummie999 said:
To hard.
Thermal control is done by thermald (/system/bin/thermald), I'm pretty happy with it.
fiops is already there
btw with two junior members posting in my thread, you triggered something that automatically added a Q&A forum, so my kernel thread is now a fancy devdb thread
Click to expand...
Click to collapse
I'm watching forum since 2010, i used to have Desire but couldn't sign up some reason in that time. I see google+ account is to be accepted and signed up :angel:
I'm saying with fiops, all other schedulers and cpu governments like smartmax,intellidemand etc.
Btw i love your kernel, my dad very thankful to it. Do you think to improve DTW? sometimes it can be a little laggy. Thank you for your effort btw

blitzzkrieg said:
I'm watching forum since 2010, i used to have Desire but couldn't sign up some reason in that time. I see google+ account is to be accepted and signed up :angel:
I'm saying with fiops, all other schedulers and cpu governments like smartmax,intellidemand etc.
Btw i love your kernel, my dad very thankful to it. Do you think to improve DTW? sometimes it can be a little laggy. Thank you for your effort btw
Click to expand...
Click to collapse
:laugh:
I got intellidemand working, it just needs some tweaking. As for the rest, well, submit a feature request in the brand new devdb
The lags have been fixed in version 8.

dummie999 said:
:laugh:
I got intellidemand working, it just needs some tweaking. As for the rest, well, submit a feature request in the brand new devdb
The lags have been fixed in version 8.
Click to expand...
Click to collapse
Sorry, I.m takin your time but i forgot something to ask before. With your kernel camera app uses phone's storage and does not let use the sd card. So, i can take approx. 75 photo and 3 min. lenght video. Tried stock,clean rom, if i flash original boot.img i can use sd card for camera storage. Did i miss something to change in kernel settings? Thank you sooooo much for the answer, this is last i promise And i give it a shot v8

blitzzkrieg said:
Sorry, I.m takin your time but i forgot something to ask before. With your kernel camera app uses phone's storage and does not let use the sd card. So, i can take approx. 75 photo and 3 min. lenght video. Tried stock,clean rom, if i flash original boot.img i can use sd card for camera storage. Did i miss something to change in kernel settings? Thank you sooooo much for the answer, this is last i promise And i give it a shot v8
Click to expand...
Click to collapse
I am quite sure the problem is not in the kernel, but I don't know what the problem is. What rom are you on?

dummie999 said:
I am quite sure the problem is not in the kernel, but I don't know what the problem is. What rom are you on?
Click to expand...
Click to collapse
Stock. But i can't flash original odex or deodex, i think the problem was updater script. So i extract clean rom's meta.inf folder and added odexed's zip. Maybe its the problem. But why i can not to able flash stock odex or deodex? s-off,unlocked,cwm i have.
If i flash your boot7, i lose sd card destination on camera, with stock boot.img i can use it. Interesting

blitzzkrieg said:
Stock. But i can't flash original odex or deodex, i think the problem was updater script. So i extract clean rom's meta.inf folder and added odexed's zip. Maybe its the problem. But why i can not to able flash stock odex or deodex? s-off,unlocked,cwm i have.
If i flash your boot7, i lose sd card destination on camera, with stock boot.img i can use it. Interesting
Click to expand...
Click to collapse
You have dualsim phone?

ufonek said:
You have dualsim phone?
Click to expand...
Click to collapse
Yes.
I'm looking for a full system dump of dual sim but nobody have it i guess.

blitzzkrieg said:
Yes.
I'm looking for a full system dump of dual sim but nobody have it i guess.
Click to expand...
Click to collapse
This not work? https://docs.google.com/file/d/0B6WBFlAKqe30QVNYelN1UzZhUHc/edit

ufonek said:
This not work? https://docs.google.com/file/d/0B6WBFlAKqe30QVNYelN1UzZhUHc/edit
Click to expand...
Click to collapse
Yes, i tried that odex and deodex. I install from recovery, cwm or twrp says installed with success,but process takes 4-5 second. If i try to boot, there is a warning 'No OS installed, do you really wanna boot?' i had download 4-5 times each zip,don't think files are corrupted

blitzzkrieg said:
Yes, i tried that odex and deodex. I install from recovery, cwm or twrp says installed with success,but process takes 4-5 second. If i try to boot, there is a warning 'No OS installed, do you really wanna boot?' i had download 4-5 times each zip,don't think files are corrupted
Click to expand...
Click to collapse
Try putting the files on your phone manually via adb. It always works :fingers-crossed:

dummie999 said:
Try putting the files on your phone manually via adb. It always works :fingers-crossed:
Click to expand...
Click to collapse
I forgot try adb thing, thank you for advice :highfive:
Can be removed 7 vibration at the time? Or can we install original hboot again? I read somewhere, rumrunner changes something about hboot, so it cause 7 vibration. Boot problems are because of it i think

blitzzkrieg said:
I forgot try adb thing, thank you for advice :highfive:
Can be removed 7 vibration at the time? Or can we install original hboot again? I read somewhere, rumrunner changes something about hboot, so it cause 7 vibration. Boot problems are because of it i think
Click to expand...
Click to collapse
7 vibration is caused by s-off.

ufonek said:
7 vibration is caused by s-off.
Click to expand...
Click to collapse
It start when i unlocked the bootloader. I grant s-off like a month after. Before s-off it vibrates 7 time only before boot up. Now vibrates when i enter and exit recovery too. So it vibrates 7 times short after exit recovery and 7 times long vibrates before booting. And it became 14 vibrates at all
It(vibration) can not be removed then?

blitzzkrieg said:
It start when i unlocked the bootloader. I grant s-off like a month after. Before s-off it vibrates 7 time only before boot up. Now vibrates when i enter and exit recovery too. So it vibrates 7 times short after exit recovery and 7 times long vibrates before booting. And it became 14 vibrates at all
It(vibration) can not be removed then?
Click to expand...
Click to collapse
Not at the moment

Change the frequency band in HTC desire 500
Hi,
I bought a HTC desire 500 dual sim in India which supports the following frequency
2G/ 2.5G - GSM/GPRS/EDGE: 900/1800/1900 MHz
3G/ 3.5G - UMTS/ HSPA: 900/2100 MHz with HSDPA up to 7.2 Mbps
Now I came to US and here they use 805MHz. Is there any way to change the frequency. Please help...

Successful s-off htc desire 500 dual sim
Finally i managed to successfully s-off my desire 500 dual sim by using rumrunner 0.71 proto (rumrunner 0.5 from official website won't work only makes funny 7 vibrations)..But i don't get it all advantages from it i tried installing stock rom odex 1.06 either from cwm twrp or with ruu mode and it wont install..Only significiant advantage is that i don't need anymore custom kernels for full root access i tried to install busybox and update supersu from playstore with binaries with stock boot from firmware.zip and i did it..Very important before s-off is to kill-server in adb and be ensured that phone is connected to usb 2.0 port on pc and turn off firewall..Very important is that fastboot in power options is turned off..But great disadvantage is that phone becomes test device and you cant turn-off tell HTC

[ROM] Stock with all updates [NWS2.170620.003]

Manually extracted stock ROM after all updates for now, include boot.img, recovery.img and system.img for LG Warch Urbane 1st gen.
GOOGLE Drive

The link is broken, my friend

Link is working here. Hopefully the author of the 998 mhz 4 core mod can get this boot image and get that going. I miss having that little boost in speed.

DrRyder said:
Link is working here. Hopefully the author of the 998 mhz 4 core mod can get this boot image and get that going. I miss having that little boost in speed.
Click to expand...
Click to collapse
how can i downgrade to 5.1 from 2.0 on my lg urbane?

kaosar said:
how can i downgrade to 5.1 from 2.0 on my lg urbane?
Click to expand...
Click to collapse
There are a lot of threads out there on how to downgrade from 2.0 to 1.5. Do a little searching and you can find them. I havent needed to downgrade.

DrRyder said:
There are a lot of threads out there on how to downgrade from 2.0 to 1.5. Do a little searching and you can find them. I havent needed to downgrade.
Click to expand...
Click to collapse
How to install? There is no specific way install. Can u provide me link how to downgrade 1.5 without any problem?

kaosar said:
How to install? There is no specific way install. Can u provide me link how to downgrade 1.5 without any problem?
Click to expand...
Click to collapse
This maybe? https://www.reddit.com/r/AndroidWear/comments/651ijs/how_to_downgrade_the_urbane_from_20_to_15/
I take no responsibility lol. I had no need to downgrade back to 1.5 so I really couldn't help you further. You'll have to do some digging on your own, bud. 2.0 with the unlocked 4 core 998 mhz boot image has made my watch enjoyable again. I also disabled a bunch of apps that I didnt need running like other watch faces, etc to help conserve battery.

When i plug with charger it turns on but if i unplug it turn off automatically. I reset everything couple of time. I thought its a battery problem but when i go recovery with charger and unplug the charger it runs with battery backup. When i select rebot now it shut down automatically and never run until i plug charger. I dont know what should i do.

i have same issue. some times it stays longer out of charger but goes off once i do a
i have same issue. some times it stays longer out of charger but goes off once i do a
kaosar said:
When i plug with charger it turns on but if i unplug it turn off automatically. I reset everything couple of time. I thought its a battery problem but when i go recovery with charger and unplug the charger it runs with battery backup. When i select rebot now it shut down automatically and never run until i plug charger. I dont know what should i do.
Click to expand...
Click to collapse

kaosar said:
When i plug with charger it turns on but if i unplug it turn off automatically. I reset everything couple of time. I thought its a battery problem but when i go recovery with charger and unplug the charger it runs with battery backup. When i select rebot now it shut down automatically and never run until i plug charger. I dont know what should i do.
Click to expand...
Click to collapse
your issue same with me

inuer said:
your issue same with me
Click to expand...
Click to collapse
same here. Happened a week ago

zul8er said:
same here. Happened a week ago
Click to expand...
Click to collapse
Just got this issue on mine too right after flashing this kernel

liam_davenport said:
Just got this issue on mine too right after flashing this kernel
Click to expand...
Click to collapse
Reflashing stock img fixed it for me

liam_davenport said:
Reflashing stock img fixed it for me
Click to expand...
Click to collapse
Sadly it didn't work for me.
I have tried flash stock boot, rec, sys, and wipe everything, but no luck.
At least you fixed yours, so worth a try for others

liweichen6 said:
Sadly it didn't work for me.
I have tried flash stock boot, rec, sys, and wipe everything, but no luck.
At least you fixed yours, so worth a try for others
Click to expand...
Click to collapse
Damn not sure then I was thinking maybe a partition is f**ked you could format partitions and retry the img that might work

liam_davenport said:
Damn not sure then I was thinking maybe a partition is f**ked you could format partitions and retry the img that might work
Click to expand...
Click to collapse
Later I found this guide in Watch R forum, which might be related.
Since it requires mod on battery I'm not so sure if I should proceed (or I can try to replace a battery).
Or I could switch something new. It has been years and I always want to try something new lol.
Anyway thanks for effort

liweichen6 said:
Later I found this guide in Watch R forum, which might be related.
Since it requires mod on battery I'm not so sure if I should proceed (or I can try to replace a battery).
Or I could switch something new. It has been years and I always want to try something new lol.
Anyway thanks for effort
Click to expand...
Click to collapse
thanks for the link , i did this on my urbane and it fixed the problem

I like this post...

Link down... Has anybody got a link for latest stock recovery.img (after 2017 version NXGC47?)