Related
While most people are ecstatic that custom kernels can be flashed I prefer to have absolutely no digital signature requirements whatsoever at the hardware level. Does the Xoom allow for custom bootloaders?
Master Melab said:
While most people are ecstatic that custom kernels can be flashed I prefer to have absolutely no digital signature requirements whatsoever at the hardware level. Does the Xoom allow for custom bootloaders?
Click to expand...
Click to collapse
You've never been able to fastboot flash the bootloader partition anyway, if you could, it could be a convenient way to hose the entire device.
If you want to replace a bootloader, you have to look at what the device firmware offers you, like nvflash mode on Tegra devices. I don't know how one would get into that mode. Pre 3.1, some Wi-Fi Xooms had this option, I don't know if anyone ever got it working or not.
I'm pretty sure you can.
I'm not sure what the benefit of this would be...other than a good way for noobs to brick
Sent from my SPH-D700 using XDA Premium App
Master Melab said:
I'm pretty sure you can.
Click to expand...
Click to collapse
Not through fastboot.
http://android.git.kernel.org/?p=pl...0174a98c71e302c030856e3de1d8c1b48;hb=HEAD#l81
This obviously doesn't exclude other means, though.
And anyway, where are you going to get the source to build a proper bootloader? Are you going to write one from scratch?
What would be the point of new bootloaders? This seems to me to entail an enormous amount of risk for little if any gain.
Sent from my GT-I9000 using XDA Premium App
Well, I assume that the bootloader will only be able to initialize kernels with a specific structure, that structure being of Linux or Linux-like kernels. In order to boot Linux on the iPhone they had to write a new bootloader instead of modifying the Apple one.
Sent from my DROID2 GLOBAL using XDA App
Master Melab said:
Well, I assume that the bootloader will only be able to initialize kernels with a specific structure, that structure being of Linux or Linux-like kernels. In order to boot Linux on the iPhone they had to write a new bootloader instead of modifying the Apple one.
Sent from my DROID2 GLOBAL using XDA App
Click to expand...
Click to collapse
Why?
The Android kernel images have a specific structure, that's true (see http://android.git.kernel.org/?p=platform/system/core.git;a=blob;f=mkbootimg/bootimg.h), but it should not be necessarily Linux-specific. All a bootloader does is have enough initialization logic in order to find a kernel image, load it into memory, and then jump execution from itself to that kernel image's location in memory. The bootloader doesn't _care_ what operating system is running. However, without bootloader source, you can't know _for sure_ -- someone has to try another operating system kernel to find out.
As for Apple -- if you're referring to OpeniBoot (http://www.idroidproject.org/wiki/OpeniBoot), "It allows booting of unsigned code such as linux kernels on the device." -- so this is not a concern for Android-platform devices with unlocked bootloaders.
Is there any place I can download the Xoom firmware so I can examine the bootloader and see if it is digitally sign?
I've been wondering this for a while but I couldn't find the answer anywhere.
I understand that when a ROM is flashed that is meant for a different carrier, it will cause a hard brick and the phone is unbootable. My question is what physically happens to the motherboard that causes this to happen? Also, if there is something that happens to the motherboard causing it not to boot, how does a USB jig get around that and force the phone into download mode?
A definition of a "hard brick" from what I understand is a hardware malfunction.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
I've been wondering this for a while but I couldn't find the answer anywhere.
I understand that when a ROM is flashed that is meant for a different carrier, it will cause a hard brick and the phone is unbootable. My question is what physically happens to the motherboard that causes this to happen? Also, if there is something that happens to the motherboard causing it not to boot, how does a USB jig get around that and force the phone into download mode?
A definition of a "hard brick" from what I understand is a hardware malfunction.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
USB Jig won't work for hard brick as it meant for soft brick. As you said something does happen to the motherboard which why there are Jtag services available for those who hardware bricked their phone.
jmxc23 said:
USB Jig won't work for hard brick as it meant for soft brick. As you said something does happen to the motherboard which why there are Jtag services available for those who hardware bricked their phone.
Click to expand...
Click to collapse
Whoops, That's what I meant, I didn't mean usb jig I meant a jtag. Wrong term.
So a jtag is used for debugging, does it essentially just provide an alternative flow of data into the system partition? I'm still confused because if there is a problem with the hardware, I don't understand how something can be fixed by any sort of debugging. I'm confused how using a jtag would effectively restore function to the phone.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Whoops, That's what I meant, I didn't mean usb jig I meant a jtag. Wrong term.
So a jtag is used for debugging, does it essentially just provide an alternative flow of data into the system partition? I'm still confused because if there is a problem with the hardware, I don't understand how something can be fixed by any sort of debugging. I'm confused how using a jtag would effectively restore function to the phone.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I guess a very basic way to think of it is that a hard brick occurs when the base coding of the parts gets overridden/erased/corrupted. For example, the coding that tells the phone to boot when the physical power button is pressed no longer exists, therefore you cannot boot your phone. To my understanding, JTAG uses the ports on the MB and a controller box(?) to manually inject the code into the phone to allow it to power on and flash the necessary files in order to recover.
If I'm wrong on any of that, someone please call me out. I've built/worked on desktops but mobile tech is pretty new to me.
corbn89 said:
I guess a very basic way to think of it is that a hard brick occurs when the base coding of the parts gets overridden/erased/corrupted. For example, the coding that tells the phone to boot when the physical power button is pressed no longer exists, therefore you cannot boot your phone. To my understanding, JTAG uses the ports on the MB and a controller box(?) to manually inject the code into the phone to allow it to power on and flash the necessary files in order to recover.
If I'm wrong on any of that, someone please call me out. I've built/worked on desktops but mobile tech is pretty new to me.
Click to expand...
Click to collapse
You got the gist of it.
corbn89 said:
I guess a very basic way to think of it is that a hard brick occurs when the base coding of the parts gets overridden/erased/corrupted. For example, the coding that tells the phone to boot when the physical power button is pressed no longer exists, therefore you cannot boot your phone. To my understanding, JTAG uses the ports on the MB and a controller box(?) to manually inject the code into the phone to allow it to power on and flash the necessary files in order to recover.
If I'm wrong on any of that, someone please call me out. I've built/worked on desktops but mobile tech is pretty new to me.
Click to expand...
Click to collapse
Great explanation, so a custom rom from a different carrier would essentially overwrite the specific boot commands for the phone. So that would explain why a specific jtag would have to be made for each phone model to rewrite the booting commands.
I think that pretty much answers both of my questions.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Great explanation, so a custom rom from a different carrier would essentially overwrite the specific boot commands for the phone. So that would explain why a specific jtag would have to be made for each phone model to rewrite the booting commands.
I think that pretty much answers both of my questions.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I have bricked my tablet while rooting and swapping. It doesn't turn on now. Pls help me how can I use the jtag to recover my tab??
I also have an identical working tab with me.
This thread was meant for the op to know what a hard brick is and the purpose of jtag as well as what causes a hard brick. It will be much better if you post your issues in your own thread so we can help you without reviving an old thread.
HTC One S Brick
I understang what you said, but how can a HTC One S get hard bricked after I connected it to windows 10 pc? The sync manager started and when I checked the device nothing happened. It remaind black, no charging light, no button or combo of buttons working. Before this i never tried to unlock the bootloader or to flash any other mod. Since then my device is unresponsive and is recognized by any windows pc as QHSUSB_DLOAD.
What may be the cause of this error?
Hi Im a complete Noob for doinf this :silly:
Coming from Htc One there was a method posted on the Htc one forums to get the bootloader locked.
http://forum.xda-developers.com/showthread.php?t=2475914
And stupid me without thinking I used the command echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
to reset the unlocked to lock stats.
Well now the phone doesnt even turn on no booloader no recovery nothing, pc detects it as an unkown device but I dont know what to do with it.
is there anyway possible to bring this brick back to life or do i have send it back to google?
Any suggestions or Advice is welcome.
Thanks
If it doesn't turn on I think you're hosed. You messed up one the partitions running the commands you did Please read the pinned (stickies) threads on the general forum before you do anything on your new device.
You wiped an important partition of the phone, and now it won't boot. Looks like you are out of luck. You can probably call Google and tell them your phone won't turn on, but technically that would be lying because you broke it without reading.
If you do get a replacement, and want to unlock the bootloader just get fastboot and type 'fastboot oem unlock'. That's it. This is a Nexus.
You kinda asked for it by attempting to follow a guide that is not for your device. HTC One =/= Nexus 5.
Like the above said, you wiped a partition essential to the function of your device. No way to fix it. Gonna have to send it back to Google, hopefully when you do they won't charge you and will just send you another. They might be used to having a million returns because when a device launchers there is a massive amount of nitpicking customers trying to get replacements and/or their are legit issues with the devices and they won't bother to check whats wrong with your phone. Most likely they will though, and who knows what you'll be charged. Good luck!
xXxG0dzRAgexXx said:
You kinda asked for it by attempting to follow a guide that is not for your device. HTC One =/= Nexus 5.
Like the above said, you wiped a partition essential to the function of your device. No way to fix it. Gonna have to send it back to Google, hopefully when you do they won't charge you and will just send you another. They might be used to having a million returns because when a device launchers there is a massive amount of nitpicking customers trying to get replacements and/or their are legit issues with the devices and they won't bother to check whats wrong with your phone. Most likely they will though, and who knows what you'll be charged. Good luck!
Click to expand...
Click to collapse
I hope I do get a replacement , Im in the Uk so i cant get in contact with Google support till Monday now. I was stupid for doing that and I have learned a valuable lesson.
That's what happens when you do not read. Good luck.
xXxG0dzRAgexXx said:
You kinda asked for it by attempting to follow a guide that is not for your device. HTC One =/= Nexus 5.
Like the above said, you wiped a partition essential to the function of your device. No way to fix it. Gonna have to send it back to Google, hopefully when you do they won't charge you and will just send you another. They might be used to having a million returns because when a device launchers there is a massive amount of nitpicking customers trying to get replacements and/or their are legit issues with the devices and they won't bother to check whats wrong with your phone. Most likely they will though, and who knows what you'll be charged. Good luck!
Click to expand...
Click to collapse
this just scares me about android. I am getting a nexus 5 soon, and love tweaking with my phones, so im pretty sure theres nothing to worry about, but still.... not trying to troll or anything, but on iPhone, its ridiculously hard to "hard brick". I've seen posts online, but most of the time its just users who end up thinking they've done a fix with no result, when in reality, ive had to fix plenty of iphones in the past, and some have come in horribly screwed up. always been able to fix them and restore though, even if it meant wiping a users data. With android, while I understand there are options to restore and such, it still seems rather easy to totally brick if you miss a step or something were to happen.
hoping I will never have this issue.... :-\
unvaluablespace said:
this just scares me about android. I am getting a nexus 5 soon, and love tweaking with my phones, so im pretty sure theres nothing to worry about, but still.... not trying to troll or anything, but on iPhone, its ridiculously hard to "hard brick". I've seen posts online, but most of the time its just users who end up thinking they've done a fix with no result, when in reality, ive had to fix plenty of iphones in the past, and some have come in horribly screwed up. always been able to fix them and restore though, even if it meant wiping a users data. With android, while I understand there are options to restore and such, it still seems rather easy to totally brick if you miss a step or something were to happen.
hoping I will never have this issue.... :-\
Click to expand...
Click to collapse
iPhone's are pretty much impossible to hard brick. Was in the jailbreak scene for 2 and a half years, and there is no way to hard brick one. Very early on it was possible, but not anymore. Android devices are pretty hard to brick usually. Just make sure you follow a guide for your device and all should be well. Only risky thing really is flashing the wrong firmware or radio on a device. Flashing roms, mods, or wiping the entire device is always fixable (not important partitions though, but that's only possible via command terminal like in this case). I was at first scared with my HTC One since it was my first android device, but realized as long as you know what your doing all should go well.
unvaluablespace said:
this just scares me about android. I am getting a nexus 5 soon, and love tweaking with my phones, so im pretty sure theres nothing to worry about, but still.... not trying to troll or anything, but on iPhone, its ridiculously hard to "hard brick". I've seen posts online, but most of the time its just users who end up thinking they've done a fix with no result, when in reality, ive had to fix plenty of iphones in the past, and some have come in horribly screwed up. always been able to fix them and restore though, even if it meant wiping a users data. With android, while I understand there are options to restore and such, it still seems rather easy to totally brick if you miss a step or something were to happen.
hoping I will never have this issue.... :-\
Click to expand...
Click to collapse
Don't be too scared. Honestly bricking a nexus device is quite hard as long you are somewhat literate. With most situations (if you have access to the bootloader) you have the option of flashing the factory images which will get your phone up and running 95% of the time. Basically if you can access the bootloader, there is nothing to panic or worry about.
The only reason this guy bricked his phone is because he thought it was a good idea to root his nexus 5 using a guide that teaches you how to unlock the bootloader on an HTC One.
Just make sure you read a bit, understand what you are doing, and don't blindly follow random instructions that you find on the interwebz. If you follow that advice i doubt you will have any problems.
Sent using xda-developers app
uronfire said:
Hi Im a complete Noob for doinf this :silly:
Coming from Htc One there was a method posted on the Htc one forums to get the bootloader locked.
http://forum.xda-developers.com/showthread.php?t=2475914
And stupid me without thinking I used the command echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
to reset the unlocked to lock stats.
Well now the phone doesnt even turn on no booloader no recovery nothing, pc detects it as an unkown device but I dont know what to do with it.
is there anyway possible to bring this brick back to life or do i have send it back to google?
Any suggestions or Advice is welcome.
Thanks
Click to expand...
Click to collapse
Still having issues? I've got a couple of ideas you could try. I managed to fix my nexus after I completely screwed up the bootloader, willing to share how I fixed it
daniel.kusy said:
Still having issues? I've got a couple of ideas you could try. I managed to fix my nexus after I completely screwed up the bootloader, willing to share how I fixed it
Click to expand...
Click to collapse
How did you manage to fix yours? Mine's still bricked but can only get access to the bootloader. Have tried every option of flashing factory but still no luck.
How do you brick a Nexus?
I wish I could feel pity but man....
Tell them it won't turn on. Send it back I'm sure they won't know. Hope they don't at least. Better than keeping a paperweight.
sent from my Nexus 5
jphilippon said:
How do you brick a Nexus?
I wish I could feel pity but man....
Tell them it won't turn on. Send it back I'm sure they won't know. Hope they don't at least. Better than keeping a paperweight.
sent from my Nexus 5
Click to expand...
Click to collapse
I used ChainFires auto root and it quite simply did not work and bricked my phone. Nothing else to it… it just bricked my N5. No interruptions, all correct drivers installed. Now I'm stuck with a phone displaying unlocked boot loader (which I can lock temporarily using fast boot command.) but when the device restarts into fast boot it's back saying unlocked. Nightmare really.
Meakii said:
I used ChainFires auto root and it quite simply did not work and bricked my phone. Nothing else to it… it just bricked my N5. No interruptions, all correct drivers installed. Now I'm stuck with a phone displaying unlocked boot loader (which I can lock temporarily using fast boot command.) but when the device restarts into fast boot it's back saying unlocked. Nightmare really.
Click to expand...
Click to collapse
there is a person in the franco's thread who even corrupted the bootloader he managed to recover using some lg flsh tool something like kdz
it was some kind of methord used to unbrick nexus 4
Meakii said:
How did you manage to fix yours? Mine's still bricked but can only get access to the bootloader. Have tried every option of flashing factory but still no luck.
Click to expand...
Click to collapse
have you tried the flash-all.bat (factory image using command prompt from the sdk/platform-tools folder )?
Sent from my Nexus 5 using Tapatalk
floxrin said:
have you tried the flash-all.bat (factory image using command prompt from the sdk/platform-tools folder )?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yea mate. No luck.
Meakii said:
Yea mate. No luck.
Click to expand...
Click to collapse
If you can get into bootloader does fastboot work? If you can get into the bootloader virtually anything can be fixed. What happens when you click the flash all.bat file?
Try LG download mode
Sent from my Nexus 5 using Tapatalk
daniel.kusy said:
If you can get into bootloader does fastboot work? If you can get into the bootloader virtually anything can be fixed. What happens when you click the flash all.bat file?
Click to expand...
Click to collapse
See the attached. I can't do anything. Every attempt to write anything to the internal SD fails. I wish it could be fixed but have tried everything. Worst part is even after fastboot oem lock cmd when it restarts it's unlocked again. Meaning when I return it warranty will probably be void.
This guy has the same problem. http://forum.xda-developers.com/showthread.php?p=315800
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
So as Im sure everyone already knows I done messed up. I literally had the tablet(asus tf700) for less than a day. Im not very linux savvy but i know enough about electronics that i can usually get by, well not this time. I had rooted and unlocked my device, downloaded cm 11 that was to be installed via twrp recovery. Everything went gravy and then i had a loop problem with cyanogenmod, im guessing i didnt have the correct bootloader to use cm 11 in the first place. So i tried to just go back to stock only to find out that my backups had been corrupted and the names of the files were there but nothing on them. So I looked around for a bit and tried to figure out how to just flash a new rom in there, low and behold my pc laptop stopped working leaving me with only a mac to use right now. The pc will turn on and work for a bit but there is a fan out so it overheats very quickly. So i tried to use the nexus toolkit to possibly go back to stock via the nexus 10 or nexus 7 options they have. Needless to say this was very stupid and now instead of being in a bootloop with cyanogenmod I am stuck looking at the asus letters when it starts up, it doesnt even bootloop it just stays there and to top it off i now have a bootloader error 0x00000000 and i cant do anything other than the sync looking thing hich i am assuming is fast boot. I can plug it in and the computer shows the device as fastboot but just dont know what to try anymore. I have read the buster post and i know this is kind of a repost but i just dont understand the linux portion of his response. Im guessing my tablet still has a fighting chance but im just devastated at this point to have lost its use within a day of having it. Ive really learned a lot by this happening so i dont beieve i will make these mistakes again but can someone please help me get this beauty back to her prime " pun intended ".
Try writing in smaller paragraphs - that is really hard to read
From what I can tell you appear to have flashed something form a nexus into your bootloader partition?
If so I think you can say goodbye to the device unless you previously did the flatline nvflash backups to make it unbrickable?
ah wait! you said you have fastboot? Can you fastboot devices from a cmd prompt and get a device id back?
NobleXperiment said:
So as Im sure everyone already knows I done messed up. I literally had the tablet(asus tf700) for less than a day. Im not very linux savvy but i know enough about electronics that i can usually get by, well not this time. I had rooted and unlocked my device, downloaded cm 11 that was to be installed via twrp recovery. Everything went gravy and then i had a loop problem with cyanogenmod, im guessing i didnt have the correct bootloader to use cm 11 in the first place. So i tried to just go back to stock only to find out that my backups had been corrupted and the names of the files were there but nothing on them. So I looked around for a bit and tried to figure out how to just flash a new rom in there, low and behold my pc laptop stopped working leaving me with only a mac to use right now. The pc will turn on and work for a bit but there is a fan out so it overheats very quickly. So i tried to use the nexus toolkit to possibly go back to stock via the nexus 10 or nexus 7 options they have. Needless to say this was very stupid and now instead of being in a bootloop with cyanogenmod I am stuck looking at the asus letters when it starts up, it doesnt even bootloop it just stays there and to top it off i now have a bootloader error 0x00000000 and i cant do anything other than the sync looking thing hich i am assuming is fast boot. I can plug it in and the computer shows the device as fastboot but just dont know what to try anymore. I have read the buster post and i know this is kind of a repost but i just dont understand the linux portion of his response. Im guessing my tablet still has a fighting chance but im just devastated at this point to have lost its use within a day of having it. Ive really learned a lot by this happening so i dont beieve i will make these mistakes again but can someone please help me get this beauty back to her prime " pun intended ".
Click to expand...
Click to collapse
Wow, you beat me on the unlock your new device within one day of usage...
You can see the post above to see if you still can use your fastboot. If your fastboot is still working, you can download the full latest firmware from Asus website and install it with fastboot command...good luck....:fingers-crossed:
Yeah sorry bout the length, i know a lot of times everyone asks for more details so i figured id get that out of the way, honestly didnt even know if i would get a response so much appreciated, i will be home shortly to try the download, def a huge failblog learning experience at best. when you do that what exactly is the point of making two blops. ?
To be honest with all the amazing kits that have come out of this forum Im quite baffled there is not one to reestablish things like the nexus toolkit. With my computer overheating i basically only have time to install a kit and run it before it stops working, so hopefully i have enough time to cmd prompt, but thats really the stuff i dont get. Is it possible to go into a little depth as far as the command prompts?the busters solution would be an easy guide to work from i would imagine.
NobleXperiment said:
To be honest with all the amazing kits that have come out of this forum Im quite baffled there is not one to reestablish things like the nexus toolkit. With my computer overheating i basically only have time to install a kit and run it before it stops working, so hopefully i have enough time to cmd prompt, but thats really the stuff i dont get. Is it possible to go into a little depth as far as the command prompts?the busters solution would be an easy guide to work from i would imagine.
Click to expand...
Click to collapse
Yes the are a number of tool kits in the dev forum But unlocking and setting up recovery and the bootloader on the asus transformer is different to the nexus devices so you can't have such a simple route I'm afraid.
sbdags said:
Yes the are a number of tool kits in the dev forum But unlocking and setting up recovery and the bootloader on the asus transformer is different to the nexus devices so you can't have such a simple route I'm afraid.
Click to expand...
Click to collapse
Would I be able to us nvflash to install custom bootloader and then progress towards installing new rom? or does tht not really have anything to do with my situation? the asus website isnt working for me either so I cant download the proper firmware.
NobleXperiment said:
Would I be able to us nvflash to install custom bootloader and then progress towards installing new rom? or does tht not really have anything to do with my situation? the asus website isnt working for me either so I cant download the proper firmware.
Click to expand...
Click to collapse
Your tablet is very close to becoming a paper weight - not the ideal situation to generate your nvflash blobs.
First step should be to get a working fastbooot connection. Either fix the PC or get fastboot set up on your Mac. http://forum.xda-developers.com/showthread.php?t=1917237
A half-dead tablet and non-working PC is just a little more challenge than you need right now.
Without fastboot you cannot fix this. So get that set up and we can help more.
Sent from my K00C using Tapatalk
berndblb said:
Your tablet is very close to becoming a paper weight - not the ideal situation to generate your nvflash blobs.
First step should be to get a working fastbooot connection. Either fix the PC or get fastboot set up on your Mac. http://forum.xda-developers.com/showthread.php?t=1917237
A half-dead tablet and non-working PC is just a little more challenge than you need right now.
Without fastboot you cannot fix this. So get that set up and we can help more.
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
I got fast boot setup on the Mac and it did show that it connected but I can't download the asus firmware on my Mac for some reason?
NobleXperiment said:
I got fast boot setup on the Mac and it did show that it connected but I can't download the asus firmware on my Mac for some reason?
Click to expand...
Click to collapse
You tried all the links? I use Global and it works.
Which SKU are you? I think I have the US .10 firmware lying around somewhere - can upload it to Dropbox.
Sent from my K00C using Tapatalk
Thank you for the firmware offer but I went thru and fixed my pc and then got everything working with busters mothod:victory: I had to try it about 3 times and use my eSATA usb for some reason but i actually ended up going from stock 4.1.1 to 4.2.1 so all in all great success. honestly baffled that i pulled this off.
NobleXperiment said:
Thank you for the firmware offer but I went thru and fixed my pc and then got everything working with busters mothod:victory: I had to try it about 3 times and use my eSATA usb for some reason but i actually ended up going from stock 4.1.1 to 4.2.1 so all in all great success. honestly baffled that i pulled this off.
Click to expand...
Click to collapse
:Good:
Now generating your NVflash blobs will be a breeze
Sent from my K00C using Tapatalk
berndblb said:
:Good:
Now generating your NVflash blobs will be a breeze
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
Should i go the route of NVflash now? I only mentioned it because I saw you could download blob files but does it really make you device unbrickable? Is this something i should go for or just be happy i fixed the tablet?
NobleXperiment said:
Should i go the route of NVflash now? I only mentioned it because I saw you could download blob files but does it really make you device unbrickable? Is this something i should go for or just be happy i fixed the tablet?
Click to expand...
Click to collapse
It makes it unbrickable. You can recover from any brick with the nvflash blob files.
NobleXperiment said:
Should i go the route of NVflash now? I only mentioned it because I saw you could download blob files but does it really make you device unbrickable? Is this something i should go for or just be happy i fixed the tablet?
Click to expand...
Click to collapse
Entirely up to you. You were a half-step away from hard bricking your tablet. If this is a typical pattern for you (try first - ask/read later) it may be a very good idea to get those blobs squared away
You have to flash a modded bootloader and modded recovery just for generating the blobs (and flash back afterwards), so it may be a good idea to get this done before you get everything set up.
Sent from my K00C using Tapatalk
With all of this being a first to me I certainly underestimated how easy it is to brick a device, but I did manage to fix it which seems much harder to do so i would have to think i can get the nvflash done. Appreciate the support here and everything people do within the forums, if somebody could direct me to an approved guide that would be quite nice, im assuming its very similar to what i just went through?
NobleXperiment said:
With all of this being a first to me I certainly underestimated how easy it is to brick a device, but I did manage to fix it which seems much harder to do so i would have to think i can get the nvflash done. Appreciate the support here and everything people do within the forums, if somebody could direct me to an approved guide that would be quite nice, im assuming its very similar to what i just went through?
Click to expand...
Click to collapse
Follow these instructions to the letter.
https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
I anything is unclear, ask in this thread:
http://forum.xda-developers.com/showthread.php?t=1901479
Sent from my K00C using Tapatalk
So yeah while i thought the upgrade to 4.2.1 was a lucky mistake but now i cant use kingo to root my phone, any suggestions without having to go back to an earlier firmware?
or would getting the nvflash unroot the device again anyway?
Hello everyone,
I'm helping a far less android savvy friend with his bricked AT&t G3. He has never rooted or installed anything custom but he has an unexplained bootloop. I know my HTC One inside and out but this is the first LG3 I've ever worked on. Essentially, I'm trying to save his data if at all possible but it's seeming less and less likely as I read more about how the recovery and download mode work on this phone.
It seems like the only way I can get TWRP or any custom recovery onto this phone is if I can get it to boot, so any hope of using adb commands might be ruled out at this point. My question is: Is there any way to get a custom recovery onto this phone through download mode? If not, it seems that a full re-flash to stock might be my only option.
Thanks in advance.
The_mamba said:
Hello everyone,
I'm helping a far less android savvy friend with his bricked AT&t G3. He has never rooted or installed anything custom but he has an unexplained bootloop. I know my HTC One inside and out but this is the first LG3 I've ever worked on. Essentially, I'm trying to save his data if at all possible but it's seeming less and less likely as I read more about how the recovery and download mode work on this phone.
It seems like the only way I can get TWRP or any custom recovery onto this phone is if I can get it to boot, so any hope of using adb commands might be ruled out at this point. My question is: Is there any way to get a custom recovery onto this phone through download mode? If not, it seems that a full re-flash to stock might be my only option.
Thanks in advance.
Click to expand...
Click to collapse
If it's "bricked" brick cannot be brought back brick means it's dead. But if you have download mode it's not fully bricked. But no download mode mainly meant for official use and official firmwares only. Only really suggestion is to use the tot method to fix the phone. But it will indeed wipe everything.
Sent from my iPhone using Tapatalk
hyelton said:
If it's "bricked" brick cannot be brought back brick means it's dead. But if you have download mode it's not fully bricked. But no download mode mainly meant for official use and official firmwares only. Only really suggestion is to use the tot method to fix the phone. But it will indeed wipe everything.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I guess I should have specified that it's soft bricked, not hard bricked. Thanks for the help though, that seems to corroborate most of what I've read. I'll be flashing new firmware, was just hoping to save the data if I could but I knew it was unlikely.
Thanks again.
The_mamba said:
I guess I should have specified that it's soft bricked, not hard bricked. Thanks for the help though, that seems to corroborate most of what I've read. I'll be flashing new firmware, was just hoping to save the data if I could but I knew it was unlikely.
Thanks again.
Click to expand...
Click to collapse
Especially if it's soft brick sadly there's no way of pulling files off the phone.
Sent from my iPhone using Tapatalk
hyelton said:
Especially if it's soft brick sadly there's no way of pulling files off the phone.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Quick question again if you don't mind, and first let me say thanks a lot for the detailed thread about the tot method:
When I'm in device manager under ports I don't see LGE Modem, I just have LGE Mobile USB Port. LGE modem is actually under "modems". Which one should I change the port settings on?
Thanks again man
The_mamba said:
Quick question again if you don't mind, and first let me say thanks a lot for the detailed thread about the tot method:
When I'm in device manager under ports I don't see LGE Modem, I just have LGE Mobile USB Port. LGE modem is actually under "modems". Which one should I change the port settings on?
Thanks again man
Click to expand...
Click to collapse
As long as it's under commutation ports it's fine. It can differ sometimes.
Sent from my iPhone using Tapatalk
hyelton said:
As long as it's under commutation ports it's fine. It can differ sometimes.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
So I want to modify "LGE Mobile USB Serial Port" right? Since that's the one under Com ports? "LGE Mobile USB Modem" is listed higher up under "modems", not under com ports.