Related
Hello, Guys. So I did a stupid thing today - I was poking around in the build.prop in my v20d P769. I changed the value of a line concerning the battery, something like "battery_genuine" - My thought was that it was going to enable some sort of alternate battery notification or icon or whatever, I'm not sure what I was thinking.
Anyway, long story short, I rebooted after editing build.prop and now when the phone turns on it just says "use genuine battery - powering off" and shuts off. I had previously uninstalled CWM (getting ready to manually apply v20f) so I can't get to recovery to mount /system. I have been trying all day to get the offline flash method to work and the damn thing won't work half the time. I went through the thread instructions to install small server and edit hosts file - then reboot - when the loopback ip's are in the hosts file the test link on the thread (127.0.0.1:9002) doesn't work and neither LG application will work. If I comment out the loopback lines and restart both of them will open but neither of them will do anything useful. LG Updater tool just says I have the latest software and the UptestEX_mod2_marwin application won't flash anything.
Hoping someone can help me out here so I can recover this phone.
boot the phone in fastboot mode, don't know how to do that with your model though
use fastboot to boot into any custom recovery by typing 'path_to_adb_toolkit_files\fastboot.exe boot your_recovery_image.img'
if fastboot hangs on <waiting for device> install usb drivers
then pull off build.prop, change that field to original value and push it back into the phone
sorry mate, can't explain more detailed
Either flash ICS uboot and xloader in fastboot mode and unbrick it after, or if you can access adb, try sometjing like the following:
cd to your adb directory on your PC
adb pull /system/build.prop (in a command prompt on your PC)
Modify the file (it will be in the adb folder)
adb push pathto/thefile/build.prop > /system/build.prop (again in the cmd)
Hope it helps
Sent from my LG-P760 using xda app-developers app
N00BY0815 said:
Either flash ICS uboot and xloader in fastboot mode and unbrick it after, or if you can access adb, try sometjing like the following:
cd to your adb directory on your PC
adb pull /system/build.prop (in a command prompt on your PC)
Modify the file (it will be in the adb folder)
adb push pathto/thefile/build.prop > /system/build.prop (again in the cmd)
Hope it helps
Sent from my LG-P760 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply man - yeah I can't get to adb, that was my first though so i'm going to try fastboot, only problem is, I don't know how to boot fastboot. Is s/w upgrade mode the fastboot screen (volume up + plug in cable)?
Also, would anyone mind explaining why the small server only outputs "file not found" when attempting to start up the flash tool? The only way I can get the flash tool to even launch is to comment out the loopback lines in hosts. lol man it's times like this when I miss motorola!
*Edit - In case anyone wants to help on this front, here is the output I receive from small server when trying to open B2CappClient or UpTest or even hit the test link in the offline flash thread:
Accept-Language: en-US,en;q=0.8
^!!
!->02/08 23:54:39 [127.0.0.1:2173>9002] (t1 4) >\favicon.ico(Undefined/default)
Error. File not found.
!->02/08 23:54:39 [127.0.0.1:2173>9002] (t1 5) >HTTP in:279 out:1993 Time:31
!->02/08 23:54:41 [127.0.0.1:2177>9002] (t1 6)
GET /favicon.ico HTTP/1.1
Host: 127.0.0.1:9002
Connection: keep-alive
Accept: */*
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.95 Safari/537.36
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
^!!
!->02/08 23:54:41 [127.0.0.1:2177>9002] (t1 7) >\favicon.ico(Undefined/default)
Error. File not found.
!->02/08 23:54:41 [127.0.0.1:2177>9002] (t1 8) >HTTP in:279 out:1995 Time:94
!->02/08 23:55:43 [127.0.0.1:2184>9002] (t1 9)
GET /client/app/live_update.jsp HTTP/1.1
Host: csmg.lgmobile.com:9002
Cache-Control: no-cache
^!!
!->02/08 23:55:43 [127.0.0.1:2184>9002] (t1 10) >\client\app\live_update.jsp(Undefined/default)
Error. File not found.
!->02/08 23:55:43 [127.0.0.1:2184>9002] (t1 11) >HTTP in:99 out:2012 Time:62
I recommended removing all lg drivers and etc. Redownload all files, disable firewall and antivirus. But first you need to install fastboot and flash the u-boot for ice cream.
Inside the fastboot zip by lelus is more instructions on how to set it up. And checkout the original thread about fastbooting the l9
And you might want to try on another PC,
You need a good and clean windows environment for all to work well. This is the problem with many people. Plus a lot of antivirus programs don't like the small server.
Sent from my LG-P769 using xda app-developers app
well, if you boot into a screen that is neither android nor recovery, it should be fastboot at least this applies to my phone
since the combination is one button + plug in cable i guess it's the right one
does it say fastboot mode in the top of the screen?
SuicideFlasher said:
well, if you boot into a screen that is neither android nor recovery, it should be fastboot at least this applies to my phone
since the combination is one button + plug in cable i guess it's the right one
does it say fastboot mode in the top of the screen?
Click to expand...
Click to collapse
Well I managed to get to fastboot with the p940 script. The screen that comes up with "S/W Upgrade Please wait while upgrading...". this may be some sort of fastboot derivative but there's no response to "fastboot devices" at the prompt. Can I flash cwm through fastboot if my bootloader is locked? I had it installed with the bootstrap method.
peoplegetpeople said:
Well I managed to get to fastboot with the p940 script. The screen that comes up with "S/W Upgrade Please wait while upgrading...". this may be some sort of fastboot derivative but there's no response to "fastboot devices" at the prompt. Can I flash cwm through fastboot if my bootloader is locked? I had it installed with the bootstrap method.
Click to expand...
Click to collapse
Fastboot is an inverted lg logo.
This will offer some more help,
http://forum.xda-developers.com/showthread.php?p=43703982
Hey don't flash ice cream and ect.
All you have to do is flash (in fastboot) the boot.IMG for the kdz you are on, and you're good to go.
Extract the boot.img from the kdz
Look at my guide. Or just wait until later tonight for me to upload it.
To tell you the truth, Lol, I did the same thing you did with the battery. I was fast enough to edit it before it shutoff. I had toolbox lite app installed.
CM 10.1 P769
Finally got it! :laugh: Turns out, the default path for small server is c:\shttps\www - the problem I gave myself is that when I didn't extract to the c root, I copied from my L9 directory - when I copied none of the contents of \www copied with it, once I moved those files to the correct position it all went through as it should!
Thanks for your help guys!!
kuma82 said:
Fastboot is an inverted lg logo.
This will offer some more help,
http://forum.xda-developers.com/showthread.php?p=43703982
Hey don't flash ice cream and ect.
All you have to do is flash (in fastboot) the boot.IMG for the kdz you are on, and you're good to go.
Extract the boot.img from the kdz
Look at my guide. Or just wait until later tonight for me to upload it.
To tell you the truth, Lol, I did the same thing you did with the battery. I was fast enough to edit it before it shutoff. I had toolbox lite app installed.
CM 10.1 P769
Click to expand...
Click to collapse
hahaha I saw this about 10 mins after I got it to boot! lol - oh well, I'm running 20f now, getting ready to root and see about unlocking the bootloader. Now that the flash tool is working correctly, the only thing I have to do is get a feel for the mirrored, wonky screen. I've been researching the bootloader method but could never get that flash tool to work correctly. I'm in the game now! WOOT!
Thanks for all your help man!
peoplegetpeople said:
hahaha I saw this about 10 mins after I got it to boot! lol - oh well, I'm running 20f now, getting ready to root and see about unlocking the bootloader. Now that the flash tool is working correctly, the only thing I have to do is get a feel for the mirrored, wonky screen. I've been researching the bootloader method but could never get that flash tool to work correctly. I'm in the game now! WOOT!
Thanks for all your help man!
Click to expand...
Click to collapse
Just be sure you are ready for everything,
I recommended flashing 20d then 20b.
Hold up I'll give you all the help I gave to someone in a p.m.
kuma82 said:
I didn't have a hard time, but then again I've studied my a** off, and I knew how to fix all problems that popped up. My advice to you is read all the threads about unlocking the bootloader. The video is good but it doesn't break it down enough.
Let me tell you about everything that can go wrong and how to fix it
Problems
1. After flashing the euro kdz your phone won't boot past the logo.
Okay, this problem will make things harder(but do able), because you have to hard reset the device by pressing/holding the vol (-) + home + power (let go of power button when the lg logo comes up)
Plus after a hard reset all data will be wiped and you will have to enable USB debugging on the wonky touch screen.
The chance of this happening is rare because you are not coming from a custom ROM.
2. After flashing you get a security error (or an error during the flashing process).
Now this one sucks because you will need to fastboot and flash the ice cream u-boot. Then put the phone in the s/w upgrade mode and perform the offline flash again.
I had this happen to me once, while flashing the wind kdz. Messing with fastboot is not hard but it takes time to understand it. Get familiar with it first before trying to unlock. I'll send you a link with some more info.
3.After flashing the euro kdz you find out you don't have root.
Sometimes rooting fails (dam computers)
Now I had this happen to me after flashing euro kdz (so no cwm) but I wasn't really worried about that because I had a signal and I could make/receive calls. I had a signal because when I was flashing I swapped out the euro radio (p760.fls) with the metropcs one (lgms769.fls)
Note: you have to extract the radio from the metro kdz and rename it to p760.fls
When flashing replace the 11th bin (with hex edited 11th bin for 20b) & the radio (from metro renamed).
Another thing don't rush the unlock. I waited about 3 to 4 hours before trying, plus I took a couple of calls on the 20b kdz. And I was on wifi.
I flashed the euro kdz at work and when I got home I turned on WiFi and waited another hour.
I'm not to sure about what the video says about turning off and flashing the radio.
When the unlock first came out, the instructions were to not turn off the device before unlocking.
When I flashed the euro kdz I was on the metropcs ROM.
This is what I recommend and did.
Enable USB debugging, show all touches, & allow install from unknown sources.
Leave your phone on normally(don't put it in s/w mode) and flash the euro kdz and hopefully no problems.
After waiting a couple of hours try the unlock command with Adb on your PC.
If all goes good the phone will take you to an inverted unlock screen, just press the volume up (make sure you press the Up button!)
This will take you to the official fastboot (but it's inverted), now in fastboot flash the cwm recovery image.
In cwm flash the touch screen fix and restore a backup.
Another thing make your own backup with the locked bl cwm (just in case you have to erase all data) make backup on external SD. Another thing, Lol ,make sure the backup is good, try to restore it. I have had several corrupted backups with cwm.
I know it's a lot to learn, but then again you want to be prepared.
Think of it like a final exam, Lol and you won't go wrong.
If you get lost just holla at me.
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
CM 10.1 P769
kuma82 said:
Just be sure you are ready for everything,
I recommended flashing 20d then 20b.
Hold up I'll give you all the help I gave to someone in a p.m.
CM 10.1 P769
Click to expand...
Click to collapse
Wow man! Awesome response, really appreciate your input and explanations. It really takes some of the unknown out of it. Thanks!
Sent from my LG-P769 using xda app-developers app
httGeneric Procedure - Turn on " Fake Battery Mode " ( Bypass Genuine Battery Test ).
Boot Error ( " Use Genuine Battery " -power off- )
Entered here since procedure seems to be generic " Turn on Fake Battery Mode " (Bypass Genuine Battery Test).
>> Also called Service Menu: Type in: ##LGSERVICEMENU send (##5473784296368) on the dialpad.
>>enter the security code: 000000, locate: SW/HW Tests or HW test or SW/HW Versions
>> find "bypass booting" in menu locate "fake battery mode" select it and choose on.
--- My phone LG Optimus G Pro E980 (note: the 980 in code refers to model)
when approx 90-95%, with new gold 4200mAh battery Boot up Error ( " Use Genuine Battery " -power off- )
so, i went into hidden menu 3845#*980# ->Settings->Battery->Battery Fake Mode (Turned it ON), seems to be fixed.
By the way, the gold battery tested WORSE THAN 3140mAh OEM, Save yourself time, buy the Quality LG OEM.
so here is the deal i got root on the lg l769 and wanted to recover so i tried to unlock boot loader i cant get anywhere cant even get recover so i finally said screw it and took the ota update just to get rid of everthing well here is my problem screen is still reversed and messed up and i honeslty have no idea how to fix this any help would be great
nckfrs said:
so here is the deal i got root on the lg l769 and wanted to recover so i tried to unlock boot loader i cant get anywhere cant even get recover so i finally said screw it and took the ota update just to get rid of everthing well here is my problem screen is still reversed and messed up and i honeslty have no idea how to fix this any help would be great
Click to expand...
Click to collapse
screen is now normal but touch is backwards and stilll offf now
nckfrs said:
screen is now normal but touch is backwards and stilll offf now
Click to expand...
Click to collapse
Flash lelus cwm touch.
Sent from my LG-P769 using Tapatalk 4
geeshiet said:
Flash lelus cwm touch.
Sent from my LG-P769 using Tapatalk 4
Click to expand...
Click to collapse
this isn't working for me, not by the cmw method or by the v6.bin method
screen is now normal but touch is backwards and stilll offf now Flash lelus cwm touch
geeshiet said:
Flash lelus cwm touch.
Sent from my LG-P769 using Tapatalk 4
Click to expand...
Click to collapse
i did the following but when i got to the cmd part to reboot the phone, it only did a full reboot, no the option to unlock the bootloader,
any help please thank you all in advance:good:
Any fix for this yet?
hawkvalentine said:
Any fix for this yet?
Click to expand...
Click to collapse
Do you have root?
You can't fix it without rooting
Sent from my LGMS769 using XDA Premium 4 mobile app
I had a similar problem, and fixed it with the following:
kuma82 said:
Do you have root?
You can't fix it without rooting
Sent from my LGMS769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
From the following thread:
[Q] LG L9 P769 Bootloader not Unlocking
This will require some practice if your screen is already wonky, so patience grasshopper...
OK, I followed a process and got my phone back to square one, but also rooted and it goes as follows:
Verify both LG SW Update mode is sellected in PC connections settings, and that USB debugging is also selected
1 flash V20D_00.kdz (via the Up TestEX mod2_marwin application)
2 master reset
3 re-root device (by this time, you should be familiar with the correct touch locations on the wonky touch screen); LgPWN.apk used
5 device successfully restarted without further human interaction (if this does not happen, device is not successfully rooted; possibly try another rom in the same V20 designation
5 install SU
6 confirm phone set to LG SW mode in PC Connections setting
7 run Lelus firmware fix:
8 wait for device to promt for SU access and allow
9 On the command line: (always run as administrator)
cat /sdcard/external_sd/v6.bin > /sys/devices/virtual/input/lge_touch/firmware
reboot
10 device restored to original stock
It's not bootloader unlocked yet, but better than near softbrick...and still rooted.
mven45 said:
From the following thread:
[Q] LG L9 P769 Bootloader not Unlocking
This will require some practice if your screen is already wonky, so patience grasshopper...
OK, I followed a process and got my phone back to square one, but also rooted and it goes as follows:
Verify both LG SW Update mode is sellected in PC connections settings, and that USB debugging is also selected
1 flash V20D_00.kdz (via the Up TestEX mod2_marwin application)
2 master reset
3 re-root device (by this time, you should be familiar with the correct touch locations on the wonky touch screen); LgPWN.apk used
5 device successfully restarted without further human interaction (if this does not happen, device is not successfully rooted; possibly try another rom in the same V20 designation
5 install SU
6 confirm phone set to LG SW mode in PC Connections setting
7 run Lelus firmware fix:
8 wait for device to promt for SU access and allow
9 On the command line: (always run as administrator)
cat /sdcard/external_sd/v6.bin > /sys/devices/virtual/input/lge_touch/firmware
reboot
10 device restored to original stock
It's not bootloader unlocked yet, but better than near softbrick...and still rooted.
Click to expand...
Click to collapse
you quoted the wrong person, lol.
Still cant manage to unlock bootloader
kuma82 said:
you quoted the wrong person, lol.
Click to expand...
Click to collapse
Ive run adb reboot oem-unlock many, many times with no success; device just restarts. I've gotten CWM installed but still cannot flash roms. Its rooted, carrier unlocked, and otherwiseready to go; but no luck. I've updated the adm device log with the LG device identifier hex that I found in a link to google's adm help and troubleshooting section, and the device is recognized by adm again, but the command only restarts the device. It is interesting to note that I now get the flashing nav buttons when it boots however. If I hold down the vol down button it'll boot in CWM recovery, but holding the vol up button seems to do nothing. Any clues?
mven45 said:
Ive run adb reboot oem-unlock many, many times with no success; device just restarts. I've gotten CWM installed but still cannot flash roms. Its rooted, carrier unlocked, and otherwiseready to go; but no luck. I've updated the adm device log with the LG device identifier hex that I found in a link to google's adm help and troubleshooting section, and the device is recognized by adm again, but the command only restarts the device. It is interesting to note that I now get the flashing nav buttons when it boots however. If I hold down the vol down button it'll boot in CWM recovery, but holding the vol up button seems to do nothing. Any clues?
Click to expand...
Click to collapse
The cwm with the blinking lights at boot is a second init recovery (bootstrap). Meaning it was made for locked bootloader. It not a true custom recovery. I can't help you with the unlock, to many unknown stuff. It has only worked for some.
Sent from my LGMS769 using XDA Premium 4 mobile app
Hello,
I recently purchased the H960A model (European Version). I've read several threads about rooting this phone, but I want to be absolutely certain I'm following the proper procedure.
1) Do I need to unlock the bootloader prior to rooting? My understanding is that this model recently had the bootloader unlocked by LG Developer.
2) Once I've followed the instructions to unlock the bootloader, I'm assuming I need to go into the developer options of my V10 and enable "Enable OEM unlock" and "USB debugging"?
3) Once I've done the above two items (if all of that is necessary), what next? Can someone direct me to the correct process for root?
I was hoping to add TWRP but it seems that there is only an unofficial process currently.
Any help on accomplishing root (safely) with this phone would be greatly appreciated. Just want to be certain I'm following the proper steps so I don't brick my beautiful new international V10.
Thanks
You need to enable usb debugging and OEM unlock before unlocking the bootloader then flashing twrp unofficial then flashing supersu file
Hi,
yes, you need to unlock the bootloader before you can root your phone. Please be aware that this will also initiate a factory reset of the phone, so if you have already a lot of apps installed and data on the internal SD card be sure to make a backup. For the apps you can use LG Backup. You need to have an external SD card and be sure to select this as destination for the backup. Otherwise it will be deleted during the factory reset (if it is on the internal memory; that gets deleted as well).
Then just follow the description on the LG developer page step by step and then the TWRP thread to get root. As vip57 already pointed out you need to set USB debug and OEM unlock before trying to unlock the bootloader but that is also described in detail on the LG developer page (step 7 and 8).
Thanks to all who responded. I unlocked the bootloader successfully. Then installed TWRP, rooted, and installed XPosed. All went perfectly, no problems or glitches. LOVE MY V10!!!
More clarification please
Hi, I need more clarification, not the OP, though.
I read some of the guides explaining how to root this phone. Thanks for the info regarding the bootloader, I didn't know that. I also don't know what this TWRP is.
I want the stock LG ROM, I just want the root, is this possible? I want the standard camera, galery, capture+, all the standard LG things. I also want the standard updates, so I want to get a
system update via LG bridge, when my friend (unrooted phone) gets one.
Is this possible, or do I have to install an unofficial "kinda like the stock" ROM, to get root access?
Thanks in advance!
Hi everyone ;
I have a problem to reboot in bootloader mode ; LG USB drivers are installed ; debug mode and OEM unlock are ON ; H960A still with original firmware (5.1)
When I type 'adb devices', my phone is listed.
When I type 'adb reboot bootloader' the phone reboots, but in android, not in a fastboot mode
when I turn the phone OFF, press Volume Down and attach a USB cable from PC : it reboots to android
when I turn the phone OFF, press Volume Up and attach a USB cable from PC : it reboots to some download mode (firmware upgrade, don't disconnect the cable....). I have to remove battery as it's unresponsive then.
Any idea to help me ?
thank you
edit : it was simply not possible to access the bootloader from android 5.1.
I updated to android 6 (with LG Bridge), and then 'adb reboot bootloader' rebooted in bootloader mode.
The story begins when I had twrp. i flashed the oneplus_x_oxygenos_3.1.1_community_build usb debugging turned on, and oem unlocking. I was successful, I had stock oxygen OS but I lost twrp in doing so.
retried to install twrp, it did not work, when i tried going to recovery it's stuck on oneplus logo. i tried to fix it with this , did't notice it was for Oneplus 2, so.... hard bricked my phone, i was able to recover with this but i could not install twrp. so i installed the stock recovery MM which works now. OS does not work anymore. for some reason when i try to flash the oxygenos_3.1.1 with stock recovery, it still fails. even when i tried installing a lower version rom.
Can anybody help me? this is my daily driver phone. currently using my nokia feature phone for calls and texts......
what I have:
Stock recovery
nandroid backup that i cannot use because i don't have twrp,
usb debugging turned off,
and oem unlocking off.
can access fastboot, sideload.
no access to OS.
Hatred for Pokemon Go
yay it's alive!!
this worked for me! http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
moderator kindly delete my post. Thanks!
Don't know why people are still flashing community build with twrp. So much information on this. Yes we have a working twrp for 3.1.1 but that's for after its installed.
Exodusche said:
Don't know why people are still flashing community build with twrp. So much information on this. Yes we have a working twrp for 3.1.1 but that's for after its installed.
Click to expand...
Click to collapse
I guess some confusion might have been caused when it was posted on the OnePlus forums (and apparently a quote from a OnePlus rep) that the new build was "compatible" with TWRP. This was later clarified (by a poster, not OnePlus) to mean V41 of the blu-spark TWRP.
Chat with support confirms.
Kashaila said:
Sorry to keep you waiting. I apologize for the confusion. I have just confirmed from the specialist that TWRP is compatible with the new rollout.
Click to expand...
Click to collapse
https://forums.oneplus.net/threads/...nity-beta-for-oneplus-x.464812/#post-15231909
Perhaps the mistake arises because it is not clear was that whilst TWRP is compatible, you couldn't actually flash the new community build with it! TWRP is only compatible (like you say) AFTER the flash!!
https://tapatalk.com/shareLink?url=...share_tid=3464987&share_fid=3793&share_type=t
[guide] unbrick device
This should help...
The solution for OPX hardbrick is similar to OPO and OP2 - you just need a Qualcomm driver and a recover package.
So,here we go !!
Step 1 :- DOWNLOADS :-
1.) Drivers :- https://www.androidfilehost.com/?fid=24052804347799753 (Extract these files to a folder on desktop.)
2.) Recovery Tool :- https://drive.google.com/folderview?...XM&usp=sharing (Download all files inside this folder and put them in a folder on desktop.)
Step 2 :- If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :- http://www.howtogeek.com/167723/how-...igned-drivers/
Step 3 :- Press the power button for 40 seconds to turn off the phone.
Step 4 :- Press only volume up button for 10 sec and then power button. While keeping them pressed,connect OPX to PC.Hold volume up until your PC finds a new hardware .
Step 5 :- Go to device manager in your PC, find the new "QUALCOMM-HS USB Diagnostics xxxx" device or something like this (It must be Unknown Devices as QHUSB_BULK or under COMs and Ports as Qualcomm xxxx). Update its driver in property page using the Qualcomm driver provided (for 32bit windows, select x86 folder; for 64bit windows, select x64 folder).
Step 6 :- After installing the drivers,"Run As Administrator" the MSMDownloadToolV2.0 in the recovery tools folder.
Step 7 :- Click start at top left corner and wait for it to finish (Download Complete will come)
Step 8 :- Disconnect phone from PC and boot into system.
Now you can again do anything you wish to (unlock bootloader,etc).To unlock bootloader,go to developer options and tick "Enable OEM Unlock" first.
When you will need this guide ? :-
1.) If your phone is totally black (no racism)
2.) When you have locked the bootloader by mistake . (This happens when you flash a rom without having oem unlocking enabled.)
PS:- This method will wipe all data and restore your phone to OxygenOS and English Bootloader.
Thanks.
Hi, i can' get the qualcomm driver installed. It says like the hash isn't in the catalog and that it is damaged or messed with.
The Driver Signature is turned off in W10, so do you know something?
Also there is no communication with fastboot, i can boot to it, to the fb logo on the opx, but no way to get contact.
Thanks
tjeus said:
Hi, i can' get the qualcomm driver installed. It says like the hash isn't in the catalog and that it is damaged or messed with.
The Driver Signature is turned off in W10, so do you know something?
Also there is no communication with fastboot, i can boot to it, to the fb logo on the opx, but no way to get contact.
Thanks
Click to expand...
Click to collapse
Change computer.
Try with an old windows 7.
Or, try this: http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
Iirc, it's the same for Windows 10.
Sent from my ONE E1003 using Tapatalk
Himanshu Gusai said:
The solution for OPX hardbrick is similar to OPO and OP2 - you just need a Qualcomm driver and a recover package.
So,here we go !!
Step 1 :- DOWNLOADS :-
1.) Drivers :- https://www.androidfilehost.com/?fid=24052804347799753 (Extract these files to a folder on desktop.)
2.) Recovery Tool :- https://drive.google.com/folderview?...XM&usp=sharing (Download all files inside this folder and put them in a folder on desktop.)
Step 2 :- If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :- http://www.howtogeek.com/167723/how-...igned-drivers/
Step 3 :- Press the power button for 40 seconds to turn off the phone.
Step 4 :- Press only volume up button for 10 sec and then power button. While keeping them pressed,connect OPX to PC.Hold volume up until your PC finds a new hardware .
Step 5 :- Go to device manager in your PC, find the new "QUALCOMM-HS USB Diagnostics xxxx" device or something like this (It must be Unknown Devices as QHUSB_BULK or under COMs and Ports as Qualcomm xxxx). Update its driver in property page using the Qualcomm driver provided (for 32bit windows, select x86 folder; for 64bit windows, select x64 folder).
Step 6 :- After installing the drivers,"Run As Administrator" the MSMDownloadToolV2.0 in the recovery tools folder.
Step 7 :- Click start at top left corner and wait for it to finish (Download Complete will come)
Step 8 :- Disconnect phone from PC and boot into system.
Now you can again do anything you wish to (unlock bootloader,etc).To unlock bootloader,go to developer options and tick "Enable OEM Unlock" first.
When you will need this guide ? :-
1.) If your phone is totally black (no racism)
2.) When you have locked the bootloader by mistake . (This happens when you flash a rom without having oem unlocking enabled.)
PS:- This method will wipe all data and restore your phone to OxygenOS and English Bootloader.
Thanks.
Click to expand...
Click to collapse
Hello, i have similar problem.
I tried to flash sultan rom on top of cm13 nightly, but before flashing i wiped everything, system,data, cache etc.
Then i went to flash sultan(with twrp, can't remember the version but i think it was new one), i had to change update script in .zip file to ONE before i could flash it.
Then when it flashed i tried to restart but it said no system.
I decided not to restart and flash OOS 3.1.3, it flashed and restarted...but it was constantly restarting, logo would show and 1 sec after it would restart, and it stuck in a loop. No recovery, no fastboot...
With a guide above i managed to get it to install recovery and rom, but when booting, after loading android apps, it would just say finishing boot and restart again...
So i had recovery and tried to flash a new recovery but bootloader is locked, and cannot be unlocked because, oem unlock is disabled....
I tried to flash OOS 3.1.3 with stock recovery but after clicking YES for flashing phone turned off. When i tried to turn it on it only shows logo, nothing booting....
And now when i try to use MSM Download tool everything is done but phone still doesn't boot anything at all......now it won't even get to the part with loading android apps.....
Can anyone help?? Could someone please upload recovery.img and system.img that i could put in MSM folder, maybe if it would flash that files it would work?
Is there any other way to set oem unlock to enabled without developer options???
help help help
Ovakisan said:
Hello, i have similar problem.
I tried to flash sultan rom on top of cm13 nightly, but before flashing i wiped everything, system,data, cache work?
Is there any other way to set oem unlock to enabled without developer options???
help help help
Click to expand...
Click to collapse
The part when it said no system you would of been fine if you just let it boot. Did you wipe before flashing 3.1.3 after Sultan? You need to get old stock recovery to flash 3.1.3. Whether that be thru fastboot or using the unbrick guide.
Once you have booted 3.1.3 you can continue with fastboor flashing one of the updated twrp's (Sultans,blu sparksv41,Nachets.)
Exodusche said:
The part when it said no system you would of been fine if you just let it boot. Did you wipe before flashing 3.1.3 after Sultan? You need to get old stock recovery to flash 3.1.3. Whether that be thru fastboot or using the unbrick guide.
Once you have booted 3.1.3 you can continue with fastboor flashing one of the updated twrp's (Sultans,blu sparksv41,Nachets.)
Click to expand...
Click to collapse
I did wipe yes, but within twrp not stock recovery, so that is what f**ed it up :/
Thru fastboot i can't do anything because bootloader is locked and cannot be unlocked. unbrick guide just boots, updates and starts android applications and then restarts.
A few minutes ago it managed to get into setup wizard, and i went skip skip skip just to get into settings and before i got in freaking thing restarted and now is again starting aplications in a loop......
Could i use different img files with MSM downloader? Where can i read more about msm downloader app and what it does?
Ovakisan said:
I did wipe yes, but within twrp not stock recovery, so that is what f**ed it up :/
Thru fastboot i can't do anything because bootloader is locked and cannot be unlocked. unbrick guide just boots, updates and starts android applications and then restarts.
A few minutes ago it managed to get into setup wizard, and i went skip skip skip just to get into settings and before i got in freaking thing restarted and now is again starting aplications in a loop......
Could i use different img files with MSM downloader? Where can i read more about msm downloader app and what it does?
Click to expand...
Click to collapse
Can't you go through the steps to unlock bootloader now that you've done the hard brick guide? I'm not sure bro someone will help you.
Exodusche said:
Can't you go through the steps to unlock bootloader now that you've done the hard brick guide? I'm not sure bro someone will help you.
Click to expand...
Click to collapse
The problem is that after going through guide, MSM downloader would say that its done, and it wouldn't boot in android, sou you can't get into developers options to enable OEM unlocking. And throught fastboot you can't do anything because its not enabled...
anyway if anyone is reading this that has same issue, just don't stop restarting, this little fu**** just managed to boot into android and i managed to get into dev options(after 3-4 restart, and 1 wipe cache data in stock recovery). after setting OEM unlock to enabled i tried to shut down phone through normal shutdown procedure but it got stuck, but force shut down with button worked and it saved OEM unlocking option on enabled. so i managed to unlock bootloader with fastboot.
So im with stock recovery now, lollipop ROM, should i try to flash OOS 3.1.3 now, or do i have to do something else prior to flashing????
I'm kind of scared now to do anything :'D
EDIT: ok, i ran into problem again -.-
twrp is flashed, latest. now when i try to flash cm13 or sultans cm13 i get this error.
http://imgur.com/a/BSpK1
I'm looking to do this later today. I've done quite a bit of reading and would like a confirmation (or correction) on the steps I plan to do.
Goal:
Upgrade my Note 4 (n910v) from Android 5.0.1 to use an NSeven rom.
Here is my phone information:
Model: SM-N910V
Android Version: 5.0.1
Baseband: N910VVRU2BOG5
USA carrier - changing from Verizon service to TMobile
My current plan:
Use Odin 3 to upgrade from N910VVRU2BOG5 to N910VVRU2BPA1 using the full firmware here. Is this guide adequate for the manual update?
Once upgrade to 5.1.1, I want to root and unlock the bootloader using this guide.
After that, I want to update the rom to NSeven using the guide here.
Questions:
Are there any issues with the steps above?
Are the guides adequate? Or are the other ones preferred?
Do I need to flash to Android 6.0.1 after rooting & unlocking the bootloader prior to using NSeven?
Thank you for taking the time to read and hopefully reply. I just want to be sure I have the right idea before I get started.
Sorry to bump this, but any chance someone has time for a response?
Bllur said:
I'm looking to do this later today. I've done quite a bit of reading and would like a confirmation (or correction) on the steps I plan to do.
Goal:
Upgrade my Note 4 (n910v) from Android 5.0.1 to use an NSeven rom.
Here is my phone information:
Model: SM-N910V
Android Version: 5.0.1
Baseband: N910VVRU2BOG5
USA carrier - changing from Verizon service to TMobile
My current plan:
Use Odin 3 to upgrade from N910VVRU2BOG5 to N910VVRU2BPA1 using the full firmware here. Is this guide adequate for the manual update?
Once upgrade to 5.1.1, I want to root and unlock the bootloader using this guide.
After that, I want to update the rom to NSeven using the guide here.
Questions:
Are there any issues with the steps above?
Are the guides adequate? Or are the other ones preferred?
Do I need to flash to Android 6.0.1 after rooting & unlocking the bootloader prior to using NSeven?
Thank you for taking the time to read and hopefully reply. I just want to be sure I have the right idea before I get started.
Click to expand...
Click to collapse
OK. I don't know about those steps, as I took a different route to get to the Nseven rom. Make sure you have the ADB/Odin 3.09 or 3.10 and Samsung drivers already installed on your PC. You might want to get/DL Kingroot.apk aswell.
Step 1.
Download the 5.1.1 BPA1 full firmware, this should be a all in one file. None of these separate files eg.BL AP CSC..
"I downloaded this from Sammobile"
Step 2.
Open Odin and add the firmware file to the AP tab by clicking on it and navigating to where file is located. This takes a little while to show as Odin checks the file before adding it( Make sure Auto reboot and F.Reset Time are ticked)
Step 3.
Make sure you have unlocked "DEVELOPER MODE" and "USB DEBUGGING" is ticked before powering down your phone and putting it into download mode by holding the 3 keys Vol Down,Power,Home then Vol Up to continue, once your in DL mode connect to PC. There may be a little pause as your PC may install further driver files before Odin recognizes you phone and adds it under "ID;COM". Once your phone has been added into the ID:COM you can go ahead and press START. Allow Odin to do its stuff and once your phone reboots you can unplug from the PC.
Now you should be on the 5.1.1 BPA1 firmware.
Allow your phone to boot completely, you can skip the whole setup process but you'll need to be connected to WiFi for the next process.
GAINING TEMP ROOT.
Step 1.
Transfer the "KINGROOT.APK" to your phone and install but don't open it yet.
Step 2.
Unlock Developer Mode again and tick USB DEBUGGING. * This is necessary for ADB.
Step 3.
Open Kingroot and allow it to check for root this can take awhile just be patient. Once it throws up the results it'll ask if you want to try "TRY TO ROOT". click on the tab and watch the process. " Your phone will reboot a few times during the process" I just reopened Kingroot each time it did until the process was done. ******You'll have to repeat this process again***** as your Phone reboots while your pushing the command file through ADB. Losing root in the process.
Now that you've repeated the process again and you have gained TEMP root. You can confirm this with "ROOT Checker" you can reconnect your phone to your PC.
Step 4.
Make sure you have the "Samsung_unlock_n4-fix script file in your FASTBOOT folder located in the extracted files of ADB.
Now open a ADB command window *Open this in the same folder where you exacted ADB. to do this hold Shift and click Right mouse button on any clear area of the ADB folder and scroll down to "Open command window here"
Step 5.
Within the command window type "CD Fastboot"
To confirm your device is added type" ADB devices"
You should see a random number listed under "List of devices"
If you do your set to go.
For this next step its best you have the Notepad open with these commands to make it easier. ****COPY & PASTE*****
The commands are.....* without the numbers in front of it
#1. adb push samsung_unlock_n4-fix
#2. adb shell
#3. su
#4. cd/data/tmp/
#5. chmod 777 samsung_unlock_n4-fix
#6. chown root. root samsung_unlock_n4-fix
#7. . / samsung_unlock_n4-fix
OK time to push the file. Start with the 1st command and press enter. Then the 2nd and press enter. Then the 3rd and press enter. Then the 4th, then the 5th and 6th then the 7th.
Now once you've enter the 7th command you'll be presented with a warning just type YES ****USING THE SHIFT KEY WHILE DO SO****** and wait while the process completes. Your phone will reboot to confirm the process is complete.
******NOTE*******
Your phone will reboot but reboot into a Bootloop, don't worry just pull the battery and memory card. Replace the battery but not the memory card. Reboot into DL mode to confirm that you are now in/a Developer Mode.
**********CONGRATULATIONS YOU JUST UNLOCKED THE BOOTLOADER********
*****NOW HERE COMES THE STINK PART*******
You'll need to flash the N910VVRU2BPA1_N910VVRU2CPD1 full firmware with Odin this will update the Bootloader to CPD1 required for Nseven to boot. But in doing so will LOCK the bootloader again. ARRRGGGGG!!!!!!
So.....
Step 1.
Put your newly unlocked phone into DL mode again and reconnect to Odin.
Step 2.
Place the BPA1/CPD1 firmware into the AP slot and press start
Disconnect when the phone reboots. Allow it to fully boot/skip the setup process. ******Note you will need Mobile Data as WiFi is non usable due to the updated firmware.
Step 3.
Reformat your memory card using your PC and place back into your phone, reconnect your phone to PC and transfer ROOTKING.APK over again.
Step 4.
Turn on Mobile data. Install KINGROOT and open, follow the same process you did to unlock 5.1.1. This time it may take a little longer and there's a chance Kingroot will fail to root just try again.
*It did it to me.
*There's a chance your phone will reboot when it comes to pushing the command file, unfortunately that's just the way it is. Just repeat the Kingroot process again.
Step 5.
Now that you've gained TEMP ROOT again, You'll need to run ADB and push the scripts again. Just follow the same process you did for 5.1.1 BPA1.
Even down to pulling the Batt & Memory card.
Step 6.
Now that the bootloader is unlocked, place phone into DL mode and reconnect to PC and Odin. Now again AP slot navigate to where you placed your Custom recovery.
****NOTE. I used TWRP 2.8.7.0 trltevzv.img as TWRP 3.0.2.0 Didn't work for me. And flash disconnecting when phone reboots.
********Congrats you now have a UNLOCKED BOOTLOADER and a CUSTOM RECOVERY on 5.1.1 with a CPD1 bootloader.
Time to flash Nseven. *don't forget to reformat your memory card.
To flash Nseven, just copy over the Nseven zip file to your memory card and flash using TWRP.......ENJOY.
* Note. I didn't flash anything else apart from the CPL1 Nseven
Even though I had all the files DL. Just follow the Nseven forum if you experience any problems.
Hope this helps getting you into/onto Nseven.