Related
I am sitting dead in the water with an EVGA Tegra Note 7 that can't turn on Wireless and won't let me install drivers to move further or even do a restore.
First off I am using Tomsgt Super Tool: http://forum.xda-developers.com/showthread.php?t=2627654
So my device was continuing to fail an OTA update so I was going to use this device to reinstall the basic 4.4.2. However during the process Fastboot.exe gave a failed message in Windows, but it showed fastboot after the device name. I continued to let it Restore Tegra Note 7 to Android 4.4.2 and first of all it did it way too fast and once it was finished I couldn't get the Wireless to enable. I read another person with the same problem that had to redo the process. Well I can't get past reinstalling ADB and Fastboot, now not even ADB..
I tried uninstalling the device from Windows letting it reinstall and then checking it again. No matter what I do the USB Driver Scan fails over and over. I got this issue the first time, but somehow I got it to catch the device once and install ADB.
1) Yes USB Debugging in Enabled
2) Yes Anti-Virus is Off
3) Bootloader unlocked
4) Tried Different USB Ports
So what the hell is going on here?? All I wanted to do was run a damn OTA update.. Now I have a tablet with no wireless and I obviously can't do an OTA update now.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I was thinking about not using the tool and doing it all manually like I used to do, but all the tool does is auto execute files/folders in specific orders, basically an elaborate .bat file. So if it is failing at ADB, it is going to fail for me manually too.
Please give me some idea of what to do. I don't see how relocking the bootloader would do anything, but aside from that it was a non-rooted stock 4.4.2 OS running.
Is there something I need to do in order to get Impactor to work?
So then I plug the device into a 9 year old laptop with Windows XP and Impactor sees the device on the first try and installs the driver (it takes 2-3 minutes). Then it finishes and I close impactor, but I get an error next saying device not found. I restart the machine and now it is exactly like my desktop, Impactor can't see the device at all.
What in the hell is going on here? If I had known all this was going to happen I would have skipped their damn OTA update that continued to fail.
BTW with XP I can prevent Windows from installing any type of driver, so I did. Should I let XP search for a driver and see what happens?
Someone throw me some ideas, you can see a full explanation of what is happening if you scroll up to my screenshot. I basically have a dead device because I wanted to use this tool to do a recovery...
Wireless refuses to turn on, it just sits there for hours if I let it.
Someone please give me guidance, I was out of the Android scene for a while and I've forgotten a lot of the tricks I used to know.
If your computer is recognizing the fastboot mode that is all you need. Forget the supertool for now.
Can you use the tablet to get into the Fastboot Protocol? It so that will put it in fastboot mode even if it doesn't look like it.
If that works, you can run TWRP or a custom recovery by using ADB and the fastboot command "fastboot boot TWRP_recover.img"
Notice the fastboot "boot", that will only run TWRP once so if you want to on your tablet for good you replace boot with "flash". fastboot flash TWRP_recover.img
You have to make sure the filename is correct with the custom recovery you downloaded.
At this point, put the update you want on your SD card, put that card in the tablet, and go to TWRP or your custom recover and upload the new software.
It sounds complicated but it isn't.
share_needles said:
If your computer is recognizing the fastboot mode that is all you need. Forget the supertool for now.
Can you use the tablet to get into the Fastboot Protocol? It so that will put it in fastboot mode even if it doesn't look like it.
If that works, you can run TWRP or a custom recovery by using ADB and the fastboot command "fastboot boot TWRP_recover.img"
Notice the fastboot "boot", that will only run TWRP once so if you want to on your tablet for good you replace boot with "flash". fastboot flash TWRP_recover.img
You have to make sure the filename is correct with the custom recovery you downloaded.
At this point, put the update you want on your SD card, put that card in the tablet, and go to TWRP or your custom recover and upload the new software.
It sounds complicated but it isn't.
Click to expand...
Click to collapse
Thanks for the suggestions, but I don't think Fastboot has completely installed on my tablet. When I hit Fastboot kernel all I get is a black flash and back to the bootloader again. I believe there is a quick message that flashes the first time I try to select Fastboot, however it's way too fast to read. When I do it again after that is when I will see a black flash, but apparently from what I have heard that is all Fastboot kernel is supposed to do??
How do I verify Fastboot is working before I flash the damn thing?
NCSUZoSo said:
Thanks for the suggestions, but I don't think Fastboot has completely installed on my tablet. When I hit Fastboot kernel all I get is a black flash and back to the bootloader again.
How do I verify Fastboot is working before I flash the damn thing?
Click to expand...
Click to collapse
That is what I was saying when I said you wouldn't even know you're in fastboot. The black-screen with message flashes for a milisecond and goes back to the same screen so it looks like nothing happened when it is actually in fastboot mode.
You can verify this by running your super tool and it will say "fastboot device"
Do you know how to use the ADB command prompt?
Using that, I flashed a custom recovery and then put the below 4.3 zip file on my SD card and going through the tablet I used the TWRP custom recovery to upload 4.3 on the tablet.
I used this old backup of 4.3:
Forum post and links: forum.xda-developers.com/showthread.php?t=2580287
Backupfile name: productionbl_signed_tn7_114gp_2923379__4.3.zip
FYI,
I was in your same situation and that worked for me. I could not get my computer to recognize my device in anything other than fastboot mode.
share_needles said:
That is what I was saying when I said you wouldn't even know you're in fastboot. The black-screen with message flashes for a milisecond and goes back to the same screen so it looks like nothing happened when it is actually in fastboot mode.
You can verify this by running your super tool and it will say "fastboot device"
Do you know how to use the ADB command prompt?
Using that, I flashed a custom recovery and then put the below 4.3 zip file on my SD card and going through the tablet I used the TWRP custom recovery to upload 4.3 on the tablet.
I used this old backup of 4.3:
Forum post and links: forum.xda-developers.com/showthread.php?t=2580287
Backupfile name: productionbl_signed_tn7_114gp_2923379__4.3.zip
FYI,
I was in your same situation and that worked for me. I could not get my computer to recognize my device in anything other than fastboot mode.
Click to expand...
Click to collapse
Can I get some official links for the newest/compatible versions of TWRP and the latest stock ROM I can install that is the most up to date (with Google Apps)?
Sorry to ask, but I am short on time most of the time and I might have an hour or so to work on it tomorrow.
Sorry I don't have official links but it would take you 10mins to find them through google. Good luck.
I have two files which I believe are correct except the TWRP file has an odd extension..
"Shaky156-TWRP-recovery.img.exe"
the other that is supposed to have GApps is: Stock-4.4.2-2.5-TegraNote7.zip
If that zip is only like 440 MB is that even possible? Can someone point me in a better direction if this sounds wrong.
Sources, TWRP: http://forum.xda-developers.com/showthread.php?t=2586432
Actually thinking about it and I bet with having things specific to img files like IMGBurn and other software it may create a .exe so it's easier to emulate it as a disk.
Do we have any good custom ROMs these days you'd suggest over stock? Are any that stable yet? If not can anyone find me a complete download if a 440MB zip is too small to have GApps in it.
I used Fastboot commands to get TWRP installed and Android is "upgrading.." now, so hopefully this will fix it.
I have the tablet up and running going into Google Play now.
I used this thread's link for the latest TWRP (2.7.1.0): http://forum.xda-developers.com/showthread.php?t=2586432
I got a completely stock version of 4.4.2 and OTA shows this as the most up to date version. I got my copy of the 4.4.2 ROM out of the Super Tool's folder that you can find here: http://forum.xda-developers.com/showthread.php?t=2627654
The tricky part to this my first time was I forgot you can open a command window inside the folder that contains TWRP/Fastboot/etc. (hold Shift and Right Click in the folder where all the data is and hit open command window)
Obviously everything came off a SD Card installed into the TN7.
answer for dummies
Hi
Is anyone able to explain how to rectify wifi being turned off constantly in basic non technical talk?
I am not a tech pro and am unsure what to do
All of the above answers are like a different language to me .
Thansks
aimeymarie said:
Hi
Is anyone able to explain how to rectify wifi being turned off constantly in basic non technical talk?
I am not a tech pro and am unsure what to do
All of the above answers are like a different language to me .
Thansks
Click to expand...
Click to collapse
Your best bet is to find someone you know who the above is not a foreign language to. I mean it could be broken down step by step as basic as possible and you may still not understand parts.
Hi,
I initially soft bricked my LG G2 D801 by clearing everything in TWRP. Tried to fix it, went through a bunch of threads and tried different tools but ended up just screwing it up more, now a hard brick. Currently will not go into download mode or TWRP. In device manager it is listed as "LG Android USB Device". Also will continuously restart unless I go into "recovery mode" where it will go into Demigod crash. I basically give up because I dont know what I'm doing.
My proposal:
I will ship you the phone, you fix it and ship it back to me
I will pay you $50 for your trouble via paypal or check
Any other information you need from me to see if it is unbrickable?
Unbricked my g2 two days ago
Hey pal! I hardbricked my lg g2 d802 two days ago. The screen was dim and dark; I was already thinking about buying a new phone. Now im replying with it lol.
I went basically nuts because i couldnt enter into download or recovery mode
I thought everything was lost but through a tool called "srk tool" I was able to force download mode on the phone. (You have to toggle "nuke download mode")
Furthermore, if you happen to plug the G2 to the PC and come across the phone being recognized as 13 drives, srk tool has an option to unbrick the phone.
It would be great if you unbricked the phone. If you can only enter download mode, flash a stock rom. Ill leave you with the two threads which have guided me:
http://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076 (SRK TOOL thread, download latest version 2.1 and proceed according to your situation)
http://forum.xda-developers.com/showthread.php?t=2797190 (lg flash tool. Download your preferred rom or carrier stock, and flash the kdz freshly)
This is what has worked for me. Good luck
Hey!
Just wondering if you got it fixed. If not let me know. I know how crappy it is just let me know which carrier you have and message me if you want me to try n repair it. I screwed mine up badly after trying to get cyanogenmod to work too once. All I would get is an lg symbol then some texts. But I fixed mine.
cuenta_clon1234 said:
Hey pal! I hardbricked my lg g2 d802 two days ago. The screen was dim and dark; I was already thinking about buying a new phone. Now im replying with it lol.
I went basically nuts because i couldnt enter into download or recovery mode
I thought everything was lost but through a tool called "srk tool" I was able to force download mode on the phone. (You have to toggle "nuke download mode")
Furthermore, if you happen to plug the G2 to the PC and come across the phone being recognized as 13 drives, srk tool has an option to unbrick the phone.
It would be great if you unbricked the phone. If you can only enter download mode, flash a stock rom. Ill leave you with the two threads which have guided me:
http://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076 (SRK TOOL thread, download latest version 2.1 and proceed according to your situation)
http://forum.xda-developers.com/showthread.php?t=2797190 (lg flash tool. Download your preferred rom or carrier stock, and flash the kdz freshly)
This is what has worked for me. Good luck
Click to expand...
Click to collapse
thanks cuenta, i've tried those before and the computer doesnt read the phone so i cant use SRK tools (as far as i can tell anyways), also can't flash because cant find phone. basically ive come up with "im not smart enough to fix this myself" haha. ty for the help anyways.
Fix for everything happen to the os http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
Please donate to developer george7565 who find that way to unbrick
amin44 said:
Fix for everything happen to the os http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
Please donate to developer george7565 who find that way to unbrick
Click to expand...
Click to collapse
thanks admin44, i'm def not smart enough for this. would rather pay someone $50 to fix it than have a disassembled phone that I cant put back together. =)
It is so easy just need some time and good eyes see some video on yotube how to open it .i do that before 2 month and i think i will need to do it again in futur becuase i love play on this phone i will search for some video that can help you
Can you take a shot of the demigod crash screen?
It's still a soft brick, hard brick is when the phone boots but the screen is black (panel gives light no image)
Can you double check in Device manager does it say something like Qhsusb_bulk?
@dudeimstoked , I've successfully unbricked the deepest of bricks on my G2 (demigod CH). I can help you. Sending you a PM.
Hey, as far as the it recognizing it as something else in download mode or whatever. Right click "this pc" on your file explorer and hit manage, it'll pop up a window and hit device manager then locate the phone and right click it and hit update driver software and hit select from currently installed drivers (could be worded different, doing this off head) and on the left it'll give you some manufacturers/corporations, select google and select on the right the one that has fastboot on it. Now if you don't see google in that list on left, that means you need to download and install the google usb drivers. This will help the computer recognize that it's in fastboot/download mode ready to get files flashed to it with the several programs listed above. I've had this issue before. Let me know if this worked!
My lg was not properly detected
My lg was not properly detected by windows 7 (plugged it in and nothing happened) and i was still able to use the srk tool. If you have qhusb... detected as the g2 you can unbrick. If it is not detected at all I would still try nuked download mode.
Good luck!! :good:
I really appreciate the tips here guys. I used to have the Qhusb_bulk or whatever reading in device manager, but in my trying to fix that I screwed it up more I think. Now I currently have what is shown in the images below. I've had a few offers to have this fixed for me, so I'll basically go in the order I received the PMs/posts. I'll do my best to provide everyone with enough info to make sure he/she can fix it without too much trouble.
Device manager (after choosing dload mode in Demigod)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Demigod crash (after trying to enter recovery)
The only way your gonna fix it is to use above mention link done it many time g2 is unbrickable with said link i crossed roms models radios everything on mine takes like 10 or 15 minnacter youve done it a few times fairly easy even for people thats not technicly in inclined
dudeimstoked said:
Hi,
I initially soft bricked my LG G2 D801 by clearing everything in TWRP. Tried to fix it, went through a bunch of threads and tried different tools but ended up just screwing it up more, now a hard brick. Currently will not go into download mode or TWRP. In device manager it is listed as "LG Android USB Device". Also will continuously restart unless I go into "recovery mode" where it will go into Demigod crash. I basically give up because I dont know what I'm doing.
My proposal:
I will ship you the phone, you fix it and ship it back to me
I will pay you $50 for your trouble via paypal or check
Any other information you need from me to see if it is unbrickable?
Click to expand...
Click to collapse
Man I know how you feel, it sucks having a bricked phone. Anyways, I totally can relate to your situation. I had a hard bricked (Verizon G2), which I did repair on my own. At first I did spend hours on end going through forum after forum, method after method. All of them stumped me. Well after all the forums, I pretty much sat there on my own and tried to figure out the pieces. I knew that when we flash something to our phone, it has to flash to the motherboard. So a bad flash (hard bricked phone) means oh no the motherboard is dead since the phone is totally unresponsive. I ended up doing a motherboard replacement (yes I did take the phone apart myself and it was my first time), and success! The phone was revived. The process is definitely possible, but again it might not be the right solution for everyone. Just wanted to share my thoughts regarding this issue!
Side note: If you want to go this route I will need to order a motherboard for your model. Depending on how long it could take to arrive, it might be awhile before you get it back repaired. I will have to use the money to purchase the board.
all fixed. thanks to xmayhemreturnsx for the good work.
Please try enter to download mode and flas to stock kdz or enter to twrp and plug your pc if your computer seem the phone same mtp device copy a cyanegonmod rom and install
Hi, I was trying to update my LG G2 D800 to Lollipop using this guide:
http://webtrickz.com/how-to-update-lg-g2-to-official-lollipop-os/
However, after the device rebooted, it went to the LG logo screen, displayed this message in the top left corner, and went to an indefinite black screen.
boot certification error
secure booting error
cause: boot certification verify
Holding down the power button for about 15 seconds turns the device off, but sometimes it turns itself back on and does it again. Turning it off, then quickly holding volume down and power button, releasing on logo, then holding again brings it to a "Factory Data Reset" screen, however, doing a reset does nothing and puts me immediately back to the same problem.
Holding volume up and plugging it into my PC does the same thing, and when plugged in, windows recognizes about 20 "unformatted drives", and shows it as QHSUB_BULK in device manager, under other devices.
Before this, I was running stock 4.4.2, D80020y, rooted with towelroot. I had attempted to create a TWRP recovery, and it said it succeeded, however it was unable to boot to recovery.
I was going to try to fix it using this thread: http://forum.xda-developers.com/showthread.php?t=2582142
However, I am unable to find an img for D80020y.
I have access to a Win 8..1 desktop, and I can run whatever OS necessary in a VM.
Does anyone know where to find one? Or, can anyone provide me with one? Or, is there another way to fix this?
I'm just worried that my device is totally gone at this point, and considering I bought it used, I have no warranty, nor a phone to replace it, currently.
Thanks so much to anyone who can help me!
First off, why didn't you just do an OTA update to Lollipop (via settings/about phone) instead of trying to manually do it? It's a lot easier and you could of avoided all of this...
Anyways, I am not sure what exactly happened (maybe it was a bad flash or maybe you screwed up somewhere), but it looks like you've gotten yourself in a real mess.
Did you triple check that you followed the article step by step? Did other people state in the comments about any problems they faced when using the method?
I have tried that method you linked before, and I used Ubuntu, which is best for that method. However, it did not work for me. I remember going on and on with that and ultimately just flat out replaced my logic board when I had a bricked G2.
And I can totally relate to to the twenty unformatted drives, I have been in same exact situation with the endless windows popups when I plug in my phone, but I never really figured out the issue. I remember before I was stuck in fast boot mode, and after awhile I couldn't even get to fast boot.
Can you get into recovery? Is the phone still alive? If so, you can use this to get back to stock http://forum.xda-developers.com/showthread.php?t=2432476
Hope this helps a bit, I have never been in your situation but if you want a real, simple solution to this: I would purchase and replace your logic board (phone's motherboard). It is a definite fix. If you are not comfortable with that, then I would advise to go ahead and do some research about this. Unfortunately, I have no idea where you can get that img (I do not have a D800, but rather a VS980), but I am sure with some Google searches you can find it.
I have bricked a couple phones in the past, and we all learn from our mistakes!
Best of luck!
fischer12345 said:
*snip*
Click to expand...
Click to collapse
I couldn't do an OTA update, as it's an AT&T phone, unlocked, and was running on TMobile. (Sorry, could've sword I specified that)
I was very careful that I followed all the steps of that article, to the period, but, again, Murphy's Law. I'm not sure what could have gone wrong.
And currently, I've tried every button combination I know and every one I could find from searching, and the only thing I can get into is the hard reset mode, but I cannot actually do a hard reset (just reboots with the same issue).
I've been unable to find specific d80020y img files after quite a bit of searching, but I will continue, and I've also contacted LG support in the event that by some act of god they can provide me with the files or another fix.
Jtpetch said:
I couldn't do an OTA update, as it's an AT&T phone, unlocked, and was running on TMobile. (Sorry, could've sword I specified that)
I was very careful that I followed all the steps of that article, to the period, but, again, Murphy's Law. I'm not sure what could have gone wrong.
And currently, I've tried every button combination I know and every one I could find from searching, and the only thing I can get into is the hard reset mode, but I cannot actually do a hard reset (just reboots with the same issue).
I've been unable to find specific d80020y img files after quite a bit of searching, but I will continue, and I've also contacted LG support in the event that by some act of god they can provide me with the files or another fix.
Click to expand...
Click to collapse
Gotcha. I haven't ran into the issue you have been describing at all before, but I just wanted to try to understand this situation a little better, I wish I could tell you what exactly happened.
As far as your problem, here's what I would do. The phone is still alive correct? Contact LG and send that bad boy in. Tell them you used it for a couple of months and all of a sudden it does not work anymore. I think that would be your best bet. However, do not tell them you modified it or whatever you tried to do with it.
Be aware if you do send it in to LG, make sure you have not tried to open up the phone and screw around with it internally. They will not fix it if that is the case. Also, it can be quite pricey depending on your current condition.
Oh, and LG will not provide you with those files, they are there to help you with any kind of phone issue, but not these kinds of issues.
This my friend is the best advice I can give you! Again, another option would be replacing the logic board, but that is ONLY a last resort.
BTW, you didn't hard brick it so that's a plus
I've not got a warranty, nor do I have the funds currently to have it repaired. That would be my last option.
Also, I'm not sure if this is helpful or relevant, but when I plugged it in to my PC just now, and it "recognized" the whole bunch of drives, I clicked through each one to see if it actually accessed anything. The "drive" it labeled "G:" had a single "image" folder in it, containing a bunch of .b00, .b01, .b02, etc files, and some .mdt files. (See picture)
Is this relevant at all? Could this help me?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Jtpetch said:
I've not got a warranty, nor do I have the funds currently to have it repaired. That would be my last option.
Also, I'm not sure if this is helpful or relevant, but when I plugged it in to my PC just now, and it "recognized" the whole bunch of drives, I clicked through each one to see if it actually accessed anything. The "drive" it labeled "G:" had a single "image" folder in it, containing a bunch of .b00, .b01, .b02, etc files, and some .mdt files. (See picture)
Is this relevant at all? Could this help me?
Click to expand...
Click to collapse
can you enter download mode? pressisng VOL UP and then plug your phone and keep button press. does it goes to usb icon with curved arrows?
No download mode for me. Trying to boot to it just brings me the same error, and black screen.
Jtpetch said:
No download mode for me. Trying to boot to it just brings me the same error, and black screen.
Click to expand...
Click to collapse
in device manager whats it says mine said QHSUSB _BULK
i know there are 2 different errors 9006- and 9008 i think.. have you try skr tools? it has the required files. for unbrick read thread. maybe you can use it.. try my link in signature and go to tools and check skr tools. its a 700 mb download as it has most variants needed files laf/boot ect those files you need.
raptorddd said:
in device manager whats it says mine said QHSUSB _BULK
i know there are 2 different errors 9006- and 9008 i think.. have you try skr tools? it has the required files. for unbrick read thread. maybe you can use it.. try my link in signature and go to tools and check skr tools. its a 700 mb download as it has most variants needed files laf/boot ect those files you need.
Click to expand...
Click to collapse
It says the same, QHSUSB_BULK. I've not tried skr tools (never heard of it before now). I'll try that out tomorrow, thank you.
Jtpetch said:
It says the same, QHSUSB_BULK. I've not tried skr tools (never heard of it before now). I'll try that out tomorrow, thank you.
Click to expand...
Click to collapse
do the QHUSB_BULK Fix when u try it (its in 4)
anyway i got my g2 in a much heavier brick,
i have a third party lab that can possibly fix my g2...
its not that expensive....
so I just need to hope they can fix it
Jtpetch said:
It says the same, QHSUSB_BULK. I've not tried skr tools (never heard of it before now). I'll try that out tomorrow, thank you.
Click to expand...
Click to collapse
this happened to me had HQSUSB_BULK showed many drives . but i could enter download mode and flashed KDZ all i had to do was change port 5 to 41.
are you sure you try download mode.? pres VOL UP keep presssing. then plug usb cable . if it shows the usb icon and a bar metter then you can KDZ
raptorddd said:
this happened to me had HQSUSB_BULK showed many drives . but i could enter download mode and flashed KDZ all i had to do was change port 5 to 41.
are you sure you try download mode.? pres VOL UP keep presssing. then plug usb cable . if it shows the usb icon and a bar metter then you can KDZ
Click to expand...
Click to collapse
Yes, I am sure. I just tried it again, though, to confirm. Held volume up, plugged in USB, and it went to the LG logo screen, showed the same error text in the top left, and went to a black screen.
I am downloading the SRKtool right now, and will try as soon as i have it.
Alrighty, so, progress (?).
I did the procedure with SRKtool, and at the end it told me to unplug it from USB and restart it, So i did that, and it went to the download mode screen, then it gave an error (Regrettably, it went too quick for me to read it), and now it's on the LG logo and has been for maybe 5 minutes, and the notification light is flashing multicolor.
EDIT: YES! I turned it off, since it wasn't doing anything, and i am able to get into download mode! Miracle!
So, is there anything else i need to to, or can i just flash Lollipop to it now, with download mode?
Jtpetch said:
Alrighty, so, progress (?).
I did the procedure with SRKtool, and at the end it told me to unplug it from USB and restart it, So i did that, and it went to the download mode screen, then it gave an error (Regrettably, it went too quick for me to read it), and now it's on the LG logo and has been for maybe 5 minutes, and the notification light is flashing multicolor.
EDIT: YES! I turned it off, since it wasn't doing anything, and i am able to get into download mode! Miracle!
So, is there anything else i need to to, or can i just flash Lollipop to it now, with download mode?
Click to expand...
Click to collapse
am not sure but there isnta kdz for lollipop right? you may need to go to KK KDZ
ooo you have d800 same as me. you need to download this and use the kitkat
Download Installer - KitKat 4.4.2 D80020c
http://forum.xda-developers.com/showthread.php?t=2663369 do that and once you in KITKAT ill tell you
if you need helps just ask
Ah, ok, will do. And thanks so much for all the help!
Jtpetch said:
Ah, ok, will do. And thanks so much for all the help!
Click to expand...
Click to collapse
no problem just hit thanks it i helped, once you in KK ill tell you how to go from there.
Wow, it flashed and everything without a hitch. I'm in KK now, and everything seems all good. So how would I go about upgrading to lollipop?
Thought I'd post back to share the conclusion.
Everything's working perfectly now, I flashed Lollipop through the flash tool, worked perfectly, and now I'm rooted, got a proper TWRP recovery set up, Xposed installed, and everything is good. Seems to run smoother on Lollipop too, and I was skeptical about the battery life, but it seems great
Jtpetch said:
Thought I'd post back to share the conclusion.
Everything's working perfectly now, I flashed Lollipop through the flash tool, worked perfectly, and now I'm rooted, got a proper TWRP recovery set up, Xposed installed, and everything is good. Seems to run smoother on Lollipop too, and I was skeptical about the battery life, but it seems great
Click to expand...
Click to collapse
am glad you liked it, just pass the knowledge when someone is in the same shoes as you were..
i have the same problem as you please help
Jtpetch said:
Alrighty, so, progress (?).
I did the procedure with SRKtool, and at the end it told me to unplug it from USB and restart it, So i did that, and it went to the download mode screen, then it gave an error (Regrettably, it went too quick for me to read it), and now it's on the LG logo and has been for maybe 5 minutes, and the notification light is flashing multicolor.
EDIT: YES! I turned it off, since it wasn't doing anything, and i am able to get into download mode! Miracle!
please guide me through what you did to get back to download
Click to expand...
Click to collapse
Hi Dear Community ,
I have here a problem with the Razer Phone 2 ,
Its it possible somehow to unlock the bootloader without OEM Activating because it wont boot into the rom?
1 :Normal booting not possible (stuck at the Razer Logo)
2:Fastboot possible but locked bootloader (For Reflashing)
3:Recovery Menu its not possible
I let the phone for 30 minutes to try boot up but not signes of progess.
I am thankfull for every Information of possibilities.
Best regards
SimpleGek
Have you tried sideloading stock rom? through recovery you should be able to do "adb sideload xxxxx.zip" xxxxx feing the filename of the stock rom.
also maybe factory resetting.
Twiggy000b said:
Have you tried sideloading stock rom? through recovery you should be able to do "adb sideload xxxxx.zip" xxxxx feing the filename of the stock rom.
also maybe factory resetting.
Click to expand...
Click to collapse
The problem is it wont boot to Recovery
Its only possible to go into "Fastboot"
The options
Recovery dont work because its stuck again at Razer Logo and Wipe Userdata too
simplegek said:
The problem is it wont boot to Recovery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Its only possible to go into "Fastboot"
The options
Recovery dont work because its stuck again at Razer Logo and Wipe Userdata too
Click to expand...
Click to collapse
Do you have AT&T?
Boot into bootloader/fastboot
If you have AT&T just go ahead and download this zip then unzip and use the flash_all.bat
https://s3.amazonaws.com/cheryl-factory-images/bolt-o-att-1240.zip
Or flash global use same steps. https://s3.amazonaws.com/cheryl-factory-images/aura-o-global-2009.zip
Bootloader Locked
Warrior1988 said:
Do you have AT&T?
Boot into bootloader/fastboot
If you have AT&T just go ahead and download this zip then unzip and use the flash_all.bat
Or flash global use same steps.
_________
'Flashing through Fastboot is impossible because the bootloader is locked :crying:
Click to expand...
Click to collapse
simplegek said:
Warrior1988 said:
Do you have AT&T?
Boot into bootloader/fastboot
If you have AT&T just go ahead and download this zip then unzip and use the flash_all.bat
Or flash global use same steps.
_________
'Flashing through Fastboot is impossible because the bootloader is locked :crying:
Click to expand...
Click to collapse
You should be allowed to flash stock img just not custom img with locked bootloader.
Click to expand...
Click to collapse
I don't think they can without unlock critical.
Warrior1988 said:
simplegek said:
You should be allowed to flash stock img just not custom img with locked bootloader.
Click to expand...
Click to collapse
Unfortunately not , at the Razer Page is the same description that i should unlock bootloader, i cant believe what a joke OEM unlock activating in the Rom is when stuck at the boot and cant unlock bootloader.
Click to expand...
Click to collapse
What were you trying to do that resulted in it being unable to boot? Factory reset should at least allow it to boot if the firmware isn't corrupted
Edit: Yeah it seems like Razer doesn't have a way to flash stock images without bootloader unlock first. Thats...weird. Like if this thing's firmware is corrupt I'm pretty sure even the factory won't be able to recover it with opening it up or something.
CurtisMJ said:
What were you trying to do that resulted in it being unable to boot? Factory reset should at least allow it to boot if the firmware isn't corrupted
Click to expand...
Click to collapse
Before happend all things i Factory Reset over Settings Menu after that Phone has restarted and pop out ereasing and stuck after new restart got stuck at the logo.
I downloaded already Factory Image , set everything up for flashing , only the locked bootloader is front of me.
and i cant unlock the bootloader because cant activate oem unlock in rom setting. i lose my hope and thinking about if something possible over emergency download (edl) but i dont wanna open the phone or something like that and i am not sure that edl is possible for Razer Phone 2.
i never had so complicated situation like that.
Best regards
SimpleGek
Hmm. So from what I understand you did a factory reset from the settings app and it wouldn't boot afterwards? Are you sure you waited long enough for the first boot? It needs to regenerate some ART caches for system apps or something after a reset if I remember right. Usually it comes pre-generated from the factory but when a user resets it it takes like 5-10min to reboot the first time. I imagine if you force shutdown during the cache generation it breaks something which results in it failing to boot outright.
Maybe try a data wipe from the bootloader, and then give it 15mins to do the first boot? It doesn't sound like you messed with the firmware so I doubt corruption is an issue.
Solve it by replace a device under warranty
CurtisMJ said:
Hmm. So from what I understand you did a factory reset from the settings app and it wouldn't boot afterwards? Are you sure you waited long enough for the first boot? It needs to regenerate some ART caches for system apps or something after a reset if I remember right. Usually it comes pre-generated from the factory but when a user resets it it takes like 5-10min to reboot the first time. I imagine if you force shutdown during the cache generation it breaks something which results in it failing to boot outright.
Maybe try a data wipe from the bootloader, and then give it 15mins to do the first boot? It doesn't sound like you messed with the firmware so I doubt corruption is an issue.
Click to expand...
Click to collapse
Thanks for everybody that has invest energy to give me Infos and think about all this , i call my provider and they offer me to replace the device so i dont wanna bricking our heads with this situation anymore.
Best Regards
SimpleGek
May be solved under a warrenty (im doing the same thing) but ive done some reasearch and if we can get someone to boot up my twrp image and do DD commands we can get the program and patch files. then use miflash or qfil and flash files with locked bootloaders, though mines unlocked.
How I did it.
sudo fastboot flashing unlock_critical
Took me right out of that limbo.
have you solved this problem?
simplegek said:
Hi Dear Community ,
I have here a problem with the Razer Phone 2 ,
Its it possible somehow to unlock the bootloader without OEM Activating because it wont boot into the rom?
1 :Normal booting not possible (stuck at the Razer Logo)
2:Fastboot possible but locked bootloader (For Reflashing)
3:Recovery Menu its not possible
I let the phone for 30 minutes to try boot up but not signes of progess.
I am thankfull for every Information of possibilities.
Best regards
SimpleGek
Click to expand...
Click to collapse
have you solved this problem?I got the same problem,but I can enter both bootloader and recover mode,but with a locked bootloader I can do nothing.
Since OP can get into fastboot, OP should try the flash-all script found in the source
blackknightavalon said:
Since OP can get into fastboot, OP should try the flash-all script found in the source
Click to expand...
Click to collapse
Tried handrurds times .It just got stuck at the beginning.
capxcom said:
have you solved this problem?I got the same problem,but I can enter both bootloader and recover mode,but with a locked bootloader I can do nothing.
Click to expand...
Click to collapse
I solved it by Warranty. Hope you can a new Device ,i brick my head was still trying to fix it . so try to give it back and get new one.
simplegek said:
I solved it by Warranty. Hope you can a new Device ,i brick my head was still trying to fix it . so try to give it back and get new one.
Click to expand...
Click to collapse
Unfortunately my back glass is cracked I don't think they will swap a new one for me :crying:
capxcom said:
Unfortunately my back glass is cracked I don't think they will swap a new one for me :crying:
Click to expand...
Click to collapse
That hurts , maybe if you can repair it , probably you can get swap it. actually there are to less replacements parts at the market for razer phone 2.
Thats seems complicated for you :\
Best Regards
SimpleGek
Hello everyone, I have bricked my OnePlus 6T...well, actually it wasn't me who is the reason this happened. :/ Open Beta 3 user.
On Thursday, I was using my phone like I normally would, I was sending a screenshot to a friend which I cut down, and after I cut the picture down, I was writing a text to support the picture, now here is what the big issue comes in. The phone was freezing - I was like, ''alright I am on a beta afterall'', and this wasn't the first time this freezing happened. Suddenly, the phone just shut itself down and went black. After a few seconds, it boot up, but while doing so, it went into Qualcomm Crash Dump Mode, which I knew I've seen before, but not on my ''old'' 5T, which had - and still has the Open beta installed on it, for well over a year now.
This was a first time thing, I have never seen this mode on my phone before and i was panicking a bit and immediately went up to my laptop. I googled a bit, and I saw that this issue isn't a first time issue, it happened before on the OnePlus 6's Open beta firmware. And I was somewhat relieved, since I thought I may be able to fix this easily without loosing any data. Wrong thought.
After this, I tried reflashing the OS in fastboot, i downloaded fastboot ROM's and tried flashing them - one after another, none of them worked.
Then I tried to ask some friends at the OnePlus forum, since some of them have more knowledge than me, a lot more actually. They tried giving me solutions without losing any data, no luck. Then I was like ''alright, I'm f**ked, I need to give up on my data''. And since all of this happened suddenly without me having a chance to predict, I had no chance to backup any important data. Then I tried the msmdownloadtool, which firstly was a mistake, as I (as stupid as I am) used the OnePlus 6 msmdownloadtool, then i realized that I was using the wrong tool, and I downloaded the OP6T msmdownloadtool, too. After the download finished, I ran the tool with my 6T plugged in, it went through in about 300 seconds and my 6T was not booting up. Sometimes, it came to the boot animation and just crashed while booting.
Friday came and I tried the same thing over and over, no luck. I was busy doing other things, so I had not much time doing this all day.
Saturday was in and I tried the same stuff, but this time, I downloaded the msmdownloadtool with OOS 9.0.5 instead of 9.0.11, which made a very good first impression, the phone was booting up! But - I couldn't do anything and it froze on me and crashed. It was booting up, but...the system was unusable, I could drag the statusbar down and tap onto the navbar, but thats all I could do before it froze.
After this, the phone rebooted and went into Qualcomm Crashdump Mode, again! But this time, there was the usual text you get while the phone is in this mode, which was NOT there before. ''Normally'', the phone went into that mode with only the Qualcomm Crash Dump Mode showing up.
I tried everything i could, but no luck. The bootloader is locked again, so I can't flash anything over fastboot, recovery has been changed with the 6/6T anyway, so no OS flashing possible with that either, I am clueless right now and i would like you guys to help me out before having to send the phone back.
And as I could no see a thread regarding this particular issue, I was sure I could open up a new one.
If there are any language mistakes or whatever, bear with me, English is not my primary language.
Oh, now I kind of forgot to edit this - My phone is back working again after RMA.
no no,it's cool,it's readable, English is fine.Msm tool should fix it..good thing is that its not hardbricked,it's still alive and sometimes booting.thats a good sign.in my opinion some partition is cousing problems and is probably corrupt.Try flashing latest MSM for 6T few times in a row,let it overwrigh,and while I bootloader try to unlock bootloader ,and then before you let phone boot,in bootloader fastboot boot TWRP img.if TWRP works,you can try flash something ,maybe OOS again and TWRP zip and try it boot.
shawek said:
no no,it's cool,it's readable, English is fine.Msm tool should fix it..good thing is that its not hardbricked,it's still alive and sometimes booting.thats a good sign.in my opinion some partition is cousing problems and is probably corrupt.Try flashing latest MSM for 6T few times in a row,let it overwrigh,and while I bootloader try to unlock bootloader ,and then before you let phone boot,in bootloader fastboot boot TWRP img.if TWRP works,you can try flash something ,maybe OOS again and TWRP zip and try it boot.
Click to expand...
Click to collapse
Hi! Thank you for your answer, but everything you mentioned, i have tried it already, every time I try to do a fastboot command, it'll not work, as Oem unlocking is disabled in the OS, and I'm not able to enable it, as mentioned, I'm not able to enter the OS.
xnutzii said:
Hi! Thank you for your answer, but everything you mentioned, i have tried it already, every time I try to do a fastboot command, it'll not work, as Oem unlocking is disabled in the OS, and I'm not able to enable it, as mentioned, I'm not able to enter the OS.
Click to expand...
Click to collapse
Can you sideload the OOS zip via stock recovery?
MarcoLK said:
Can you sideload the OOS zip via stock recovery?
Click to expand...
Click to collapse
Let me see, what's the cmd command for doing so?
xnutzii said:
Let me see, what's the cmd command for doing so?
Click to expand...
Click to collapse
Just type
Code:
adb sideload nameofthefile.zip
while you are in sideload mode of the recovery
MarcoLK said:
Just type
Code:
adb sideload nameofthefile.zip
Click to expand...
Click to collapse
Oh, alright, thanks. I'l try
xnutzii said:
Oh, alright, thanks. I'l try
Click to expand...
Click to collapse
Did not work. It says ''cannot read (name).zip''
MarcoLK said:
Just type
Code:
adb sideload nameofthefile.zip
while you are in sideload mode of the recovery
Click to expand...
Click to collapse
Also, there is no sideload on the 6T's stock recovery.
xnutzii said:
Did not work. It says ''cannot read (name).zip''
Click to expand...
Click to collapse
Even I have the same problem while sideloading zips.
I thought it was just my PC. And I never found any working solution for it.
Have you tried the HydrogenOS msmdownloadtool?
This is the chinese Version of OxygenOS (the system is in english I think)
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-hos-9-0-4-t3875673
Edit:
There should be an option.
It should look like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MarcoLK said:
Even I have the same problem while sideloading zips.
I thought it was just my PC. And I never found any working solution for it.
Have you tried the HydrogenOS msmdownloadtool?
This is the chinese Version of OxygenOS (the system is in english I think)
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-hos-9-0-4-t3875673
Click to expand...
Click to collapse
Yes, I have tried it as well, I was hoping it'd do anything, but it didn't. The phone gets to the boot screen sometimes, but mostly it'll go to the Qualcomm Crashdump Mode again
xnutzii said:
Yes, I have tried it as well, I was hoping it'd do anything, but it didn't. The phone gets to the boot screen sometimes, but mostly it'll go to the Qualcomm Crashdump Mode again
Click to expand...
Click to collapse
I am sorry but I am out of ideas.
Maybe other people have other ideas.
But you can request a repair and ask if they can repair it and if it is free.
MarcoLK said:
I am sorry but I am out of ideas.
Maybe other people have other ideas.
But you can request a repair and ask if they can repair it and if it is free.
Click to expand...
Click to collapse
No problem, thanks for your support.
That was my last option, if nothing helped.
Also, I just saw your edit, there is no option like this, there are ''wipe data and cache'', '' Advanced'' ''Exit''
You said MSM tool 9.0.11 doesn't recognize your device.. did you try to press start on the tool anyway with your device plugged in via USB?
Most times it doesn't seem to recognise my phone either but then I press start and it takes some time before it start doing is thing..
Hey m8 use MSM tool took about 10 attempts plus for the files to start downloading not sure why? But that is your answer just stick with it
xnutzii said:
Hello everyone, I have bricked my OnePlus 6T...well, actually it wasn't me who is the reason this happened. :/ Open Beta 3 user.
On Thursday, I was using my phone like I normally would, I was sending a screenshot to a friend which I cut down, and after I cut the picture down, I was writing a text to support the picture, now here is what the big issue comes in. The phone was freezing - I was like, ''alright I am on a beta afterall'', and this wasn't the first time this freezing happened. Suddenly, the phone just shut itself down and went black. After a few seconds, it boot up, but while doing so, it went into Qualcomm Crash Dump Mode, which I knew I've seen before, but not on my ''old'' 5T, which had - and still has the Open beta installed on it, for well over a year now.
This was a first time thing, I have never seen this mode on my phone before and i was panicking a bit and immediately went up to my laptop. I googled a bit, and I saw that this issue isn't a first time issue, it happened before on the OnePlus 6's Open beta firmware. And I was somewhat relieved, since I thought I may be able to fix this easily without loosing any data. Wrong thought.
After this, I tried reflashing the OS in fastboot, i downloaded fastboot ROM's and tried flashing them - one after another, none of them worked.
Then I tried to ask some friends at the OnePlus forum, since some of them have more knowledge than me, a lot more actually. They tried giving me solutions without losing any data, no luck. Then I was like ''alright, I'm f**ked, I need to give up on my data''. And since all of this happened suddenly without me having a chance to predict, I had no chance to backup any important data. Then I tried the msmdownloadtool, which firstly was a mistake, as I (as stupid as I am) used the OnePlus 6 msmdownloadtool, then i realized that I was using the wrong tool, and I downloaded the OP6T msmdownloadtool, too. After the download finished, I ran the tool with my 6T plugged in, it went through in about 300 seconds and my 6T was not booting up. Sometimes, it came to the boot animation and just crashed while booting.
Friday came and I tried the same thing over and over, no luck. I was busy doing other things, so I had not much time doing this all day.
Saturday was in and I tried the same stuff, but this time, I downloaded the msmdownloadtool with OOS 9.0.5 instead of 9.0.11, which made a very good first impression, the phone was booting up! But - I couldn't do anything and it froze on me and crashed. It was booting up, but...the system was unusable, I could drag the statusbar down and tap onto the navbar, but thats all I could do before it froze.
After this, the phone rebooted and went into Qualcomm Crashdump Mode, again! But this time, there was the usual text you get while the phone is in this mode, which was NOT there before. ''Normally'', the phone went into that mode with only the Qualcomm Crash Dump Mode showing up.
I tried everything i could, but no luck. The bootloader is locked again, so I can't flash anything over fastboot, recovery has been changed with the 6/6T anyway, so no OS flashing possible with that either, I am clueless right now and i would like you guys to help me out before having to send the phone back.
And as I could no see a thread regarding this particular issue, I was sure I could open up a new one.
If there are any language mistakes or whatever, bear with me, English is not my primary language.
Click to expand...
Click to collapse
Try fastboot boot twrp but when in fastboot go to reboot bootloader screen and push power button rite before u hit enter on the keyboard so when u push enter it says waiting for device. Then when it connects it should boot to twrp.
hagar006 said:
You said MSM tool 9.0.11 doesn't recognize your device.. did you try to press start on the tool anyway with your device plugged in via USB?
Most times it doesn't seem to recognise my phone either but then I press start and it takes some time before it start doing is thing..
Click to expand...
Click to collapse
I never said it doesn't recognize my phone though. I know how the phone gets recognized by msmdownloadtool, thanks for your input though.
MRobbo80 said:
Hey m8 use MSM tool took about 10 attempts plus for the files to start downloading not sure why? But that is your answer just stick with it
Click to expand...
Click to collapse
I have flashed the sh*t outta my phone already, it doesn't work out sadly enough. I have tried everything besides this ↓
twinnfamous said:
Try fastboot boot twrp but when in fastboot go to reboot bootloader screen and push power button rite before u hit enter on the keyboard so when u push enter it says waiting for device. Then when it connects it should boot to twrp.
Click to expand...
Click to collapse
This seems very unlikely, but I thank you for your input, let's see if this actually works for me. Hope I get the timing right.
twinnfamous said:
Try fastboot boot twrp but when in fastboot go to reboot bootloader screen and push power button rite before u hit enter on the keyboard so when u push enter it says waiting for device. Then when it connects it should boot to twrp.
Click to expand...
Click to collapse
Alright, I've tried this now and it still says "boot is not allowed in lock state" :/
xnutzii said:
Alright, I've tried this now and it still says "boot is not allowed in lock state" :/
Click to expand...
Click to collapse
Sorry about your luck. The only thing I can recommend is trying the patched msmtool that is for converting from T-Mobile to global.
I had problems getting it to connect but what I did was power off device and held volume up and volume down even after plugging it in and pushing start.
Then when I got the error it didn't connect I unplugged it and plugged it back in all while still holding volume up and volume down. It took a few tries but it will connect.
twinnfamous said:
Sorry about your luck. The only thing I can recommend is trying the patched msmtool that is for converting from T-Mobile to global.
I had problems getting it to connect but what I did was power off device and held volume up and volume down even after plugging it in and pushing start.
Then when I got the error it didn't connect I unplugged it and plugged it back in all while still holding volume up and volume down. It took a few tries but it will connect.
Click to expand...
Click to collapse
The problem is not that the phone doesn't connect, it connects right away without any issues with the volume buttons clicked together, the msmtool runs through too! But the phone does NOT boot up after all of this is finished. It goes straight to Qualcomm crashdump mode.