hi
i have problem in my wifi
i trued to flash Rogers rom by fastboot and when its start its flashed the boot.img and recovery.img only and stop to flash the system.img
after that my WIFI starting give me error and i cant swith it on
so please any one can upload the boot.img for AT&T version so i can able to reflash it again
is that how its called? boot.img?
i can't seem to find such a file (in root explorer)
do you know where can i find it?
Here you go...
I extracted these from the PG09IMG_Puccini_LTE_Cingular_US_1.17.502.3_Radio_1.04.550I.15v2_30.60.550I.10_release_210183_signed ROM file... hope it helps.
boot.img
wifi_htc_bcmMFG248_ag_tx_rx_swap.img
yes you can use it from footballs topic. or the puccini leak topic. extract from the zip file. btw. I cannot flash that whole zip anyhow.
Thanks i have done from the boot. mg from PG09IMG_Puccini_LTE_Cingular_US
I dont know why we cannot download an official RUU for ATT devices. WHY? it will makes thing easier. If your device went wrong, you can easily flash it back to factory state.
Hi, I got this wifi error now,
Is the solution and correct conditions and commend as described in below steps: -
boot into fastboot
connnect USB and it shows the USB word behind fastboot.
then from dos prompt enter commend
fastboot flash wifi_htc_bcmMFG248_ag_tx_rx_swap.img
done?
end?
Thanks.
cx5 said:
Hi, I got this wifi error now,
Is the solution and correct conditions and commend as described in below steps: -
boot into fastboot
connnect USB and it shows the USB word behind fastboot.
then from dos prompt enter commend
fastboot flash wifi_htc_bcmMFG248_ag_tx_rx_swap.img
done?
end?
Thanks.
Click to expand...
Click to collapse
When using fastboot flash you have to specify a partition to flash, so that command will not work. The correct command is:
Code:
fastboot flash boot wifi_htc_bcmMFG248_ag_tx_rx_swap.img
I am not guaranteeing that it will solve your problem, only that it will actually flash your boot partition. The best outcome is that it fixes your problem. The worst outcome is that your tablet will no longer boot due to mismatched /boot and /system partitions.
If the latter occurs then I recommend that you install a custom ROM. Let us know if it comes to that and someone will guide you.
Don't forget to backup what you have on the tablet before you do anything.
Thanks finniest, I have performed…Fastboot flash boot boot_signed.img
And solved temporarily. Got wifi not to say error. Allows me to turn on, but then immediately shuts off and display error again.
On another note, i also relocked bootloader. Run RUU, but error 155, means I can't restock.
Currently has TWRP, root, SU, all OK. Able to change custom rom anytime. But wifi error. CWrecovery flashed doomlord's wifi fix but not working.
The wifi.img hasn't been tried yet. feels strange to flash wifi.img going into the boot partition. Am I just being paranoia?
Sent from my GT-P1000 using xda app-developers app
cx5 said:
The wifi.img hasn't been tried yet. feels strange to flash wifi.img going into the boot partition. Am I just being paranoia?
Click to expand...
Click to collapse
I would give it a try. Beyond wasting five minutes of your time I don't see a downside. You can always flash another /boot image if it doesn't work.
It is good to know that you are familiar with unlocking bootloaders and have a custom recovery. That gives us a lot more options to solve this.
As far as I know the wifi module paired with the kernel by DooMLoRD is incompatible with all other kernels. So if you aren't using that kernel then you will have to use whatever bcm4329.ko file is included with the ROM that you are using. It is easy to forget that his custom wifi module is still in your /system/lib/modules directory when you flash a new kernel.
I suggest trying El-Diablo ROM and the boot.img that comes with it. This is a known working kernel and ROM pair. If you install them then first make certain to format /boot, /system and /data in whatever ways TWRP allows you to.
You should also consider that there might be something wrong with your wifi hardware. This is most likely if you have gotten your tablet wet and/or dropped it.
Hi finniest, you're right about not loosing too much time, I will give it a try now, and if it doesn't work, god bless it's OK I will read up more here, do more homework, then ask again, hahahah. Thanks !!!!!!!
finniest said:
I would give it a try. Beyond wasting five minutes of your time I don't see a downside. You can always flash another /boot image if it doesn't work.
Click to expand...
Click to collapse
Done, but not because I dare the above.
After realizing kernel + wifi (must be paired), knowing I am no OSIMOND's lightest rom, then I went back to CAREFULLY read his instructions specifically asking for doomlord's kernel v1 then flash the wifi correction ZIP via CWM. Hence I FASTBOOT FLASH BOOT kernelname.img then CWM recovery flash doomlord's wifi ZIP correction, then done. All my own fault for not reading carefully. Thanks still finniest and so many others who replied to various thread.
Where to read step by step?
cx5 said:
Hi finniest, you're right about not loosing too much time, I will give it a try now, and if it doesn't work, god bless it's OK I will read up more here, do more homework, then ask again, hahahah. Thanks !!!!!!!
Done, but not because I dare the above.
After realizing kernel + wifi (must be paired), knowing I am no OSIMOND's lightest rom, then I went back to CAREFULLY read his instructions specifically asking for doomlord's kernel v1 then flash the wifi correction ZIP via CWM. Hence I FASTBOOT FLASH BOOT kernelname.img then CWM recovery flash doomlord's wifi ZIP correction, then done. All my own fault for not reading carefully. Thanks still finniest and so many others who replied to various thread.
Click to expand...
Click to collapse
---
Kernel (ZIP) or Kernel as an Kernel Folder (organized like Linux kernel release 2.6.xx). I do not know how to use this last one
BTW, I am stuck whit my WiFi since a few weeks... Accidentally I wiped the System(Original) and other stuff, and happily installed the Diablo Version make my Jetstream to come alive. but never never can make the wifi work again.
I read a lot of Android and lear a bit about it, but I can't find the way to make WiFi works again. So Please... A jetstream whitout WiFi is like a die tablet... I need some help.
I need those links where they say how to, and the link to dowload IMG or ZIP. or a page teaching step by step how to install this Kernel (Organized like folders in a Linux like). thank in advance.
try downloading this:
https://dl.dropboxusercontent.com/u/5952907/Stock_wifi_modules.zip
and flash it thru the recovery
It said FAIL...
guru_shastri said:
try downloading this:
https://dl.dropboxusercontent.com/u/5952907/Stock_wifi_modules.zip
and flash it thru the recovery
Click to expand...
Click to collapse
Thanks for Helping.
I reboot into recovery using TWRP and tried to install it from Install Options. it said [FAIL]
Surely I'm just learnig about Android, I should use a commad from bootloader like this?
<fastboot flash recovery Stock_wifi_modules.zip> or
<fastboot flash boot Stock_wifi_modules.zip>
or something like this?
or perhaps use another tool instead TWRP...
flashing thru recovery should have worked. maybe the file is corrupted, I can't really tell
I downloaded and visually inspected the contents of the archive that @guru_shastri provided and everything looks okay. If you want to revert to revert to the stock WiFi module then this appears to be what you need.
Be aware that I have frequently witnessed instances where transfers to internal_sdcard via USB mount caused the file(s) to be corrupted. You should verify that a transfer worked by using MD5, cmp or (at least) a visual inspection.
WiFI OK!, SIM, not!
finniest said:
When using fastboot flash you have to specify a partition to flash, so that command will not work. The correct command is:
Code:
fastboot flash boot wifi_htc_bcmMFG248_ag_tx_rx_swap.img
I am not guaranteeing that it will solve your problem, only that it will actually flash your boot partition. The best outcome is that it fixes your problem. The worst outcome is that your tablet will no longer boot due to mismatched /boot and /system partitions.
If the latter occurs then I recommend that you install a custom ROM. Let us know if it comes to that and someone will guide you.
Don't forget to backup what you have on the tablet before you do anything.
Click to expand...
Click to collapse
Finally.. WiFI Works!... but not exactly with described... I had to read pretty much about all the things that concerns to adb/bootloader/flashing/installig>img>zip/ partition of each thing and so on before being succesfull with WiFi...
Not totally Sure, but the process that worked was:
WIPE all but recovery (using TWRP toosl)...
INSTALL el Diablo (zip) ROM Posted into the forums...(do not reboot)
INSTALL Stock_wifi_modules.zip
reboot into system...
Using USB debbuging reboot into bootloader.
Flash boot_signed.img >[fastboot flash root boot_signed.img]
(in this point the prompt said <waiting for device>, so I reboot into bootloader using Volume and Power buttons...)
Once flashed, reboot...
Now WiFi is working. Happily!
----
BTW... My SIM is not reconigzed (why???)... I saw it working the first time I istalled "El Diablo", but now... nothing happens.
I mean, the Sim Card appear to be reconigzed bye the system, but I don't get signal from the Phone Network (Like if it was from an unreconized carrier.. and my phone is Unlocked). I tried the sim in other phones and works well. What Can I Do at this point?
----- Soon I gonna move to another country, where I gonna use another SIM, with another carrier... --- Will the SIM work??
Adolyep said:
My SIM is not reconigzed (why???)... I saw it working the first time I istalled "El Diablo", but now... nothing happens.
Click to expand...
Click to collapse
Are you sure that you are carrier unlocked and not just bootloader unlocked? The former involves submitting your IMEI and paying a small sum of money, so it is usually easy to remember. They are completely different animals.
Make sure that you have checked Wireless & networks-->Mobile network [x]. If it is enabled then check Mobile networks for information. The SIM Toolkit app can also be a source of information.
Strangely, the lock screen is a source of information for your SIM card, so make sure you have it enabled. It is the only gateway (that I am aware of) to submitting your unlock code.
Adolyep said:
Soon I gonna move to another country, where I gonna use another SIM, with another carrier... --- Will the SIM work??
Click to expand...
Click to collapse
If your Jetstream is carrier unlocked then probably. The answer is probably because the Jetstream radio does not support every provider available.
Silly me! I did not realize look at this!
finniest said:
Are you sure that you are carrier unlocked and not just bootloader unlocked? The former involves submitting your IMEI and paying a small sum of money, so it is usually easy to remember. They are completely different animals.
Make sure that you have checked Wireless & networks-->Mobile network [x]. If it is enabled then check Mobile networks for information. The SIM Toolkit app can also be a source of information.
Strangely, the lock screen is a source of information for your SIM card, so make sure you have it enabled. It is the only gateway (that I am aware of) to submitting your unlock code.
If your Jetstream is carrier unlocked then probably. The answer is probably because the Jetstream radio does not support every provider available.
Click to expand...
Click to collapse
I just read your answer y I realized that I should carried out this simple step. look for networks in the area. This command "activate" the SIM to perform usual commands like Call or sending codes with * or # and numbers.
At this point my Jetstream is pretty much like it eas before wiping the system. but I can not fix the issue: <<Connection Problem or Invalid MMI Code>> every time that I send an command code (*111#) that is the network commad to access a few services. To perform those commads I have to take the SIM CARD and install it in another phone, Perform the network command, and return the SIM to my JETSTREAM. it is annoying. (but works)
Why in this world the network commands can not be performed by the Jetstream! (any advice?)
Adolyep said:
I just read your answer y I realized that I should carried out this simple step. look for networks in the area. This command "activate" the SIM to perform usual commands like Call or sending codes with * or # and numbers.
At this point my Jetstream is pretty much like it eas before wiping the system. but I can not fix the issue: <<Connection Problem or Invalid MMI Code>> every time that I send an command code (*111#) that is the network commad to access a few services. To perform those commads I have to take the SIM CARD and install it in another phone, Perform the network command, and return the SIM to my JETSTREAM. it is annoying. (but works)
Why in this world the network commands can not be performed by the Jetstream! (any advice?)
Click to expand...
Click to collapse
You will need to enable the MMI Code setting in the build.prop using root explorer. Without that MMI Codes do not work.
Related
Hey all,
I have a CWM backup of my current rom and have backups of apps and data but am stuck at a bootloop.
As I have read countless articles, it seems my error is because I have a locked bootloader(not actually sure). Though, I only tried to flash
clockcycle's wiped v20d cwm backup file. It failed part way saying it couldn't write to /system.
Since then, I haven't been able to fully enter CWM. just see the red triangle with the droid guy on his back.
I have read Cmahendra's unbricking guide but it doesn't work as I have installed JB and even the tips to unplug, wait 10s and reopen the program to flash again it still won't work. Still stops at 15% saying error connecting to the phone.
There is a similar thread which had this exact problem which said to
use the online method to recover your phone since I had already installed JB. I edited the hosts file to remove the fake offline server and opened up the b2CAppsetup.exe, clicked on customer support,
entered my model LGP769BK and my S/N and it began to start the process and 'analyze' then crashed and said "updating is not possible any longer due to a fatal error while the LG mobile phone software Update"
I've tried to search this out myself and not waste any space but I'm at loss here. If anyone has any help, it would be much appreciated
as I don't have a phone while this is not working.
I've tried all the ways to to hard reset, master reset and still I get the droid guy on his back. I can get to S/w mode like all the other posts say to do but none of those fixes seem to work for me. Am I missing something?
Do I have any options here? I have kind of read that I should just unlock the bootloader but I don't think that applies in my case as I can't turn on my phone fully.
edit: for the online method(LG support tool), it basically cancels when it goes to the 'downloading' phase --> this is what I've seen as most of the answers but doesn't work
Upon further reading,
many seemed to need to replace their u-boot and x-loader
I did so and installed fastboot using Lelus' script here:
http://forum.xda-developers.com/showpost.php?p=41768774&postcount=1
I used option 6 which allowed me to flash the u-boot and x-loader from p760(works with my 769 and others as it says in the options) for JB
I'm not sure if I needed this as I don't have an unlocked bootloader.
I'm not sure of commands in fastboot but I ran
fastboot devices and it showed something
I also ran: fastboot flash recovery recovery.img
and I put one of my cwm backups in the "yours" folder
After I activate fastboot, it brings me to the C:\fastboot\yours folder
I assume this is for me to put my intended files in but I'm unsure if I should use my cwm backup or something else?
After it flashed the recovery img, I sent a fastboot reboot command
but it still went back to the droid lying down with a red triangle.
As some of you may see, I'm not too great with this but I feel like I'm close. Does anybody have an idea of what I should be doing?
should I flash an update.zip?
I don't know many commands but hopefully this gets me going in the right direction.
PLEASE HELP ME!!!!
I guess your cmw restore formatted your system but couldnt load the new system
the recovery you run with a locked bootloader uses a technique called 2nd init which i think is somewhere stored in the system partition. so when the recovery formatted the system, it lost itself too.
I've had a similar problem. the way out would be booting into the SW upgrade mode--switch off the device, remove the battery, remove the usb cable. press the volume up button and connect the phone to the computer. wait for a couple of seconds and then insert the battery.
you should be in the SW upgrade mode
now use the B2C client. if it gives an option to upgrade, use that otherwise, go to the customer support menu and press recovery phone
I have already done earlier. It may have gotten lost in my frenzy of information. I have put the phone into software mode, as you said, and it won't work either; There's no option to click upgrade because it's JB(V20D) and when I click recovery phone and enter my imei, LG mobile support tool(B2capp.exe) analyzes and then has a 'fatal error'
Since I flashed the new u-boot and x-loader my screens are all backwards/mirrored. Maybe the tool flashed an unlocked u-boot and x-loader if that's possible.
Is a recovery possible by fastboot?
I have a clean and full copy of my cwm recovery as well as apps and data backed up, I just need to get this phone in working order
shockah486 said:
I have already done earlier. It may have gotten lost in my frenzy of information. I have put the phone into software mode, as you said, and it won't work either; There's no option to click upgrade because it's JB(V20D) and when I click recovery phone and enter my imei, LG mobile support tool(B2capp.exe) analyzes and then has a 'fatal error'
Since I flashed the new u-boot and x-loader my screens are all backwards/mirrored. Maybe the tool flashed an unlocked u-boot and x-loader if that's possible.
Is a recovery possible by fastboot?
I have a clean and full copy of my cwm recovery as well as apps and data backed up, I just need to get this phone in working order
Click to expand...
Click to collapse
If you fastboot flash the u-boot and x-loader from p769(ICS) it should go thru with the offline flash detailed in cmahendras guide.
http://forum.xda-developers.com/showthread.php?t=2085344
Use the KDZ_FW_UPD.zip from this thread
Or try this
Remove all of the stuff you have downloaded for this. Download the original B2C client from LG's site and use that
Tablechair said:
If you fastboot flash the u-boot and x-loader from p769(ICS) it should go thru with the offline flash detailed in cmahendras guide.
Click to expand...
Click to collapse
Thanks.I'll try this. if I have the ICS bootloader, does that mean I'll have to flash the V10G kdz? or can i do the v20d kdz
dhruvbatra205 said:
http://forum.xda-developers.com/showthread.php?t=2085344
Use the KDZ_FW_UPD.zip from this thread
Or try this
Remove all of the stuff you have downloaded for this. Download the original B2C client from LG's site and use that
Click to expand...
Click to collapse
I have the updated kdz fw upd .zip from the unbrick and root thread as well as downloaded a new, official B2C client but they all still hang at the download part during phone recovery.
Tablechair, that did the trick.
Is this because the tool we use to flash for the offline method doesn't recognize the x and u-boot loaderse of JB?
After I installed the ICS boot loaders, my software upgrade mode wasn't mirrored anymore.
I did as tablechair and flashed the V20D.
Does anyone understand why this problem happened in the firstplace? Maybe I didn't get a full copy of clockcycle's backup cwm
or should I have not flashed his recovery in the first place since I didn't have an unlocked bootloader?
Again thank you for all your help and if anyone can provide answers to my other supplemental questions, that'd be great.
Off to root and probably unlock bootloader to be sure.
edit: I can't find the thanks button. but thank you very much tablechair. much appreciated. Hope this can help someone else
p.s. also big thanks to those who made the fastboot program for p769(Artas182x and sguerrini97). really an invaluable tool as I now know.
shockah486 said:
Tablechair, that did the trick.
Is this because the tool we use to flash for the offline method doesn't recognize the x and u-boot loaderse of JB?
After I installed the ICS boot loaders, my software upgrade mode wasn't mirrored anymore.
I did as tablechair and flashed the V20D.
Does anyone understand why this problem happened in the firstplace? Maybe I didn't get a full copy of clockcycle's backup cwm
or should I have not flashed his recovery in the first place since I didn't have an unlocked bootloader?
Again thank you for all your help and if anyone can provide answers to my other supplemental questions, that'd be great.
Off to root and probably unlock bootloader to be sure.
edit: I can't find the thanks button. but thank you very much tablechair. much appreciated. Hope this can help someone else
p.s. also big thanks to those who made the fastboot program for p769(Artas182x and sguerrini97). really an invaluable tool as I now know.
Click to expand...
Click to collapse
Things don't always go according to plan, maybe his Clockworkmod backup was made from the touch version and he didn't have artas182x second init recovery installed. So when the cwm failed the first time, did you try to restore your cwm backup?
kuma82 said:
Things don't always go according to plan, maybe his Clockworkmod backup was made from the touch version and he didn't have artas182x second init recovery installed. So when the cwm failed the first time, did you try to restore your cwm backup?
Click to expand...
Click to collapse
Not yet. having problems flashing a kdz again. I've tried the 2 different software modes, as well as setting emerg and diag but still getting stuck at 15% again.
Do i have to replace my uboot and xloader with the ICS ones every time I want to use the offline flash method?
edit: yup, after replacing with ICS loaders again i'm able to flash using software upgrade. will update on whether I can restore cwm
kuma82 said:
Things don't always go according to plan, maybe his Clockworkmod backup was made from the touch version and he didn't have artas182x second init recovery installed. So when the cwm failed the first time, did you try to restore your cwm backup?
Click to expand...
Click to collapse
I realized I misread your question. When I flashed before the incident, it failed to write to system and I didn't restore my other folder. I rebooted and it was all missed up. Anyway, now that I've got everything back and now with an unlocked bootloader, i was able to recover my old image. However, data isn't working so I have to find the radio to flash as I recall reading in other threads.
Can someone explain in laymen terms why this is? recap, i was on unlocked bl rooted jb and I flashed my old cwm backup when I was rooted but had a locked bl. My apps and messages were all there but the radio was different. I'd understand if I was going from ICS to JB but I was on JB both times. The only difference being a locked BL. It's got to be something about the Radio from p760 or V20B that didn't work on my earlier backup or something like that because the layout status bar is different with a "data" button and showing H instead of 4g(which are the same afaik).
Since, I restored to my backup from after my bootloader unlock and root so data is working showing 'H' with the different layout
Also, I had problems backing up and restoring until I noticed that it works better when I power off the phone and do the manual commands to enter recovery as opposed to using the app to send me to recovery(where I incurred /system backup errors).
My last question is which cwm recovery should I use? I currently have the one for a locked bootloader installed as per Artas182x's website. On that post he has a link for an unlocked bootloader recovery on the xda forums but that thread was updated to not working. Are there any disadvantages to me using a locked bootloader cwm recovery?
I don't think I have any option but to try it as I want to flash CM10.1 for p769. I also read that if your bootloader is unlocked, you can download the cwm from the googleplay. If this is true, can I just install over or should I uninstall the Artas182x locked bootloader one????
update: have to remove l9 recovery by deleting the appropriate system folders and then flash the appropriate .img through adb commands
Help.
shockah486 said:
I realized I misread your question. When I flashed before the incident, it failed to write to system and I didn't restore my other folder. I rebooted and it was all missed up. Anyway, now that I've got everything back and now with an unlocked bootloader, i was able to recover my old image. However, data isn't working so I have to find the radio to flash as I recall reading in other threads.
Can someone explain in laymen terms why this is? recap, i was on unlocked bl rooted jb and I flashed my old cwm backup when I was rooted but had a locked bl. My apps and messages were all there but the radio was different. I'd understand if I was going from ICS to JB but I was on JB both times. The only difference being a locked BL. It's got to be something about the Radio from p760 or V20B that didn't work on my earlier backup or something like that because the layout status bar is different with a "data" button and showing H instead of 4g(which are the same afaik).
Since, I restored to my backup from after my bootloader unlock and root so data is working showing 'H' with the different layout
Also, I had problems backing up and restoring until I noticed that it works better when I power off the phone and do the manual commands to enter recovery as opposed to using the app to send me to recovery(where I incurred /system backup errors).
My last question is which cwm recovery should I use? I currently have the one for a locked bootloader installed as per Artas182x's website. On that post he has a link for an unlocked bootloader recovery on the xda forums but that thread was updated to not working. Are there any disadvantages to me using a locked bootloader cwm recovery?
I don't think I have any option but to try it as I want to flash CM10.1 for p769. I also read that if your bootloader is unlocked, you can download the cwm from the googleplay. If this is true, can I just install over or should I uninstall the Artas182x locked bootloader one????
update: have to remove l9 recovery by deleting the appropriate system folders and then flash the appropriate .img through adb commands
Click to expand...
Click to collapse
Although I might be late, I have the same problem and the same phone and I really need help. I have a soft bricked phone lg optimus l9 and I had the same problems that you had exactly... Which is weird exept I don't have Clock Work Mod or anything ... If you get this I would really appreciate some help. Thanks
yup me too
I finally got software upgrade to work with my lg p769 that was security error cuz i still haven't unlocked the bootloader, if i knew what a good job lg and T-Mobile did in locking it i would have waited and got a g3 that my buddy rooted in like 5 min and unlocked the boot....
What worked for me is this LG FLASH TOOL 2014 THREAD ON XDA
http://forum.xda-developers.com/showthread.php?t=2797190
flashed both the 20H and 20D successfully i uninstalled everything lg in the control panel first though.
Hope this works for you cuz i was struggling on and off for a month to get this far lol
the 2014 tool ultimately worked for me too, once I fixed a couple things. I had rooted and forgotten to unlock, so it was at Security Error, and it would also disconnect at 15% .. in the 2014 tool, I had to install all the updates even though I'm in windows 7 or it would keep doing it. All good now.
I have been trying all these methods and I am still not able to get in the S/W upgrade mode. The only thing I am getting from the device is being able to put it fastboot mode (The inverted one). I really want to revive this phone
Thanks in advance for any help given
Liger878 said:
I have been trying all these methods and I am still not able to get in the S/W upgrade mode. The only thing I am getting from the device is being able to put it fastboot mode (The inverted one). I really want to revive this phone
Thanks in advance for any help given
Click to expand...
Click to collapse
Hey, it's been ages since I have done any of this but IIRC, if you can get into fastbood mode u can still get into software mode,
- turn phone into fastboot mode
- open the software upgrader thing as you normally do
- maybe switch emerg to diag or something like that
- this part is where it's slightly different than the normal way(same program but u select a different option than the default 1st option on
I think if yoiu look through the tutorials it does mention an alternative method for getting into software mode
in one instance in my past, i had to reflash the ICS boot drivers so the software installer would recognize that
the flashing of the ICS boot drivers is done through fastboot. Should be a post in my history where I asked a question regarding this.
Sorry for the chaos but maybe this will help you get in the right direction since I don't know any of your phone history and what you've done etc
best of luck mate
shockah486 said:
Hey, it's been ages since I have done any of this but IIRC, if you can get into fastbood mode u can still get into software mode,
- turn phone into fastboot mode
- open the software upgrader thing as you normally do
- maybe switch emerg to diag or something like that
- this part is where it's slightly different than the normal way(same program but u select a different option than the default 1st option on
I think if yoiu look through the tutorials it does mention an alternative method for getting into software mode
in one instance in my past, i had to reflash the ICS boot drivers so the software installer would recognize that
the flashing of the ICS boot drivers is done through fastboot. Should be a post in my history where I asked a question regarding this.
Sorry for the chaos but maybe this will help you get in the right direction since I don't know any of your phone history and what you've done etc
best of luck mate
Click to expand...
Click to collapse
Thanks, Never tried switching to DIAG before but I will try it and let you know what is the outcome.
Hopefully you find the thread that states the exact steps bc that is off the top of my head and over a year ago by memory . GL bud
Liger878 said:
Thanks, Never tried switching to DIAG before but I will try it and let you know what is the outcome.
Click to expand...
Click to collapse
Hey, I have been trying it with the fastboot but it keeps timing out and not allowing me to finish. One thing I should let you know is that, ever since I had put the device in fastboot, I am not able to get back the S/W upgrade mode. Dont know if that will help in seeing what my problem is or if you want me to explain everything from the beginning again, I am more than happy to.
Have you followed the steps that I linked to in the first 3 posts of this thread?
Follow the steps to flash the ICS bootloaders in fastboot and then you can do the fastboot trick for getting the software to recognize your device.
Right now your phone has the JB boot loader on it and is thus not recognized by the software.
recap:
step 1: flash the ICS bootloaders in fastboot (look at the linked thread in post 2)
step 2: use the software in emerg or diag mode but sitll follow the same steps as the tutorial. I think my earlier posts should explain precisely.
if you dont flash the ICS bootloaders, it won't be recognized by the KDZ installer
Hi everybody.
Actually there are two issues to solve. I've read the thread "please, help!' related to WiFi error and saw a possible solution, but I can't perform any Bootloader command. I already done: Change Settings>Programs>USB Debbuging marked, (my device is unlooked and has a Diablo-version)
I think I wiped some else by mistake (even the original System), and I recover the system using Diablo ROM.
How Can I make bootloader works again?, and then fix the WiFi issue?
I am using TWRP access to install ZIP ROMs but none fixed WiFi...
you need to explain this part better: "but I can't perform any Bootloader command"
what can't you perform and what do u see when trying
guru_shastri said:
you need to explain this part better: "but I can't perform any Bootloader command"
what can't you perform and what do u see when trying
Click to expand...
Click to collapse
I mean "ADB" command. I was reading a lot about it and learning a bit more. I know now that ADB commands are use to copy, push, install and more from a Command Window. I didn't realize that those command can be done from a specific directory (Am I right?).
So, I copied ADB and two DLL files into a TWRP directory in my Device, and from this folder performed a few commands... and Voilá.. it worked.
But still can't make WiFi works and my System is still rebooting ramdomly when is not in use...
thanks for any Help ... any advice....
search the forum..you need to flash the wifi module to fix that.
as for the crashes, check on which kernel the device is running. the doomlord one is problematic
guru_shastri said:
search the forum..you need to flash the wifi module to fix that.
as for the crashes, check on which kernel the device is running. the doomlord one is problematic
Click to expand...
Click to collapse
Ok. stuck again. I've downloaded some ZIP and IMG files that I tried to "install" using fastboot or TWRP tools. in both cases FAILED.
there is someways to install usig fastboot commands to SEND (install) a ZIP directly to the device, but I am not sure how to do this.
Do you need to specify a Partition to install a ZIP file? Which one?
how to? [I mean Syntaxis of the command]
...
I m pretty upset with this device. I'm running El Diablo ROM pretty well, but Tetter (the game) and WiFi never worked...
Thanks in advance!
Can anyone tell me where to get my At One M8 repairs?
I can't take it to AT&T since they will say it's been tampered. I would appreciate any advice because I couldn't get any ROM into it. Only cyanogen would work but no WiFi.
ricm68 said:
Can anyone tell me where to get my At One M8 repairs?
I can't take it to AT&T since they will say it's been tampered. I would appreciate any advice because I couldn't get any ROM into it. Only cyanogen would work but no WiFi.
Click to expand...
Click to collapse
Not enough information. What about it is "broken" requiring repair? In what way is it "tampered"?
Oh, and HTC will most likely refuse to repair it directly, telling you that if you bought it from AT&T, that AT&T needs to act as the agent for repair. You can always try to head over to HTC's website (I'm sure you can find it), find the support section, and make a support inquiry from them directly.
garyd9 said:
Not enough information. What about it is "broken" requiring repair? In what way is it "tampered"?
Oh, and HTC will most likely refuse to repair it directly, telling you that if you bought it from AT&T, that AT&T needs to act as the agent for repair. You can always try to head over to HTC's website (I'm sure you can find it), find the support section, and make a support inquiry from them directly.
Click to expand...
Click to collapse
Well I don't know how but I erased the internal memory completely and now it won't take any roms. No matter what I try in recovery it always fails. The only thing I can install is cyanogenmod. There is no wifi also.
i'll try to go to at&t or htc. I hope they don;t charge me too much to repair.
Thanks.
ricm68 said:
Well I don't know how but I erased the internal memory completely and now it won't take any roms. No matter what I try in recovery it always fails. The only thing I can install is cyanogenmod. There is no wifi also.
i'll try to go to at&t or htc. I hope they don;t charge me too much to repair.
Thanks.
Click to expand...
Click to collapse
Did you flash the google play edition ruu? If so, the phone was repartitioned, and sense will no longer "fit" on the system partition. There's a way to deal with that if that's the case...
garyd9 said:
Did you flash the google play edition ruu? If so, the phone was repartitioned, and sense will no longer "fit" on the system partition. There's a way to deal with that if that's the case...
Click to expand...
Click to collapse
I flashed the one found at the post: [RUU] att ruu 1.58.502.1 posted
Hmm.. Not sure what to suggest in that case. I'm not very familiar with the whole RUU thing myself...
Sent from my Nexus 7 using Tapatalk
Download the ota update. Extract the firmware.zip from it but don't extract firmware.zip. boot to fastboot.
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
Do it again
Fastboot flash zip firmware.zip
Fastboot reboot-bootloader
Fastboot flash recovery twrp.img
Fastboot erase cache
Load recovery
Wipe, advanced wipe
Select dalvik, cache, data, system, internal. Wipe.
Put Rom on ext sd card or
Adb push Rom.zip /sdcard/
Install zip this will obviously erase everything on your phone.
Click thanks.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
ricm68 said:
Well I don't know how but I erased the internal memory completely and now it won't take any roms. No matter what I try in recovery it always fails. The only thing I can install is cyanogenmod. There is no wifi also.
i'll try to go to at&t or htc. I hope they don;t charge me too much to repair.
Thanks.
Click to expand...
Click to collapse
You don't need to repair. You just need to troubleshoot. You are throwing the baby out with the bath water, if you go for a hardware repair for what is likely a software issue that is easy to resolve.
You also need to provide more details, and be specific as possible. Namely:
What recovery and version number?
S-on or off?
What exactly have you tried to flash?
Did you factory reset in bootloader?
Do you have working adb?
What happened when you ran the RUU?
Hi redpoint73, I have twrp 2.7.1.0, unlocked, s-off.And I have adb.
I tried to ruu, then install a recovery, a stock rom and don't know how many things more and can't bring it back. They told me I should install cwm and try from there but don't know how. Please advice me on what to do and if you can, guide me step by step.
Thanks so much for your help.
ricm68 said:
Hi redpoint73, I have twrp 2.7.1.0, unlocked, s-off.And I have adb.
I tried to ruu, then install a recovery, a stock rom and don't know how many things more and can't bring it back. They told me I should install cwm and try from there but don't know how. Please advice me on what to do and if you can, guide me step by step.
Thanks so much for your help.
Click to expand...
Click to collapse
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
You wont need the whole thing but some of it might pertain to you
ricm68 said:
Hi redpoint73, I have twrp 2.7.1.0, unlocked, s-off.And I have adb.
I tried to ruu, then install a recovery, a stock rom and don't know how many things more and can't bring it back.
Click to expand...
Click to collapse
I've already asked what happened when you ran the RUU, and you didn't answer. Any error messages, etc.? This is very critical information, so its hard to help when you don't provide the answers requested (especially this one).
RUU is meant to recover the device in most cases. So if it didn't work, its very posible you have a fundamental USB connectivity issue. What response do you get when you type the adb command:
adb devices
What happens when you try to install recovery or a stock ROM? You need to give more information and specifics if you really want help.
And "don't know how many things" is not meaningful information. You need to list all the things you tried, and the results. Again, the lack of specific info makes it hard to help. I literally typed more asking you questions, than you bothered typing the answers. This does not bode well if you really want help.
You did not even answer all the questions I asked:
- What exactly have you tried to flash? (list the ROMs)
- Did you factory reset in bootloader?
ricm68 said:
They told me I should install cwm and try from there but don't know how. Please advice me on what to do and if you can, guide me step by step.
Click to expand...
Click to collapse
Who is "they"? Again, you are being too vague.
I am personally more familiar with TWRP, so I would advise staying with that if you want help from me. Nothing against CWM. But again, its just what I'm more familiar with.
redpoint73 said:
I've already asked what happened when you ran the RUU, and you didn't answer. Any error messages, etc.? This is very critical information, so its hard to help when you don't provide the answers requested (especially this one).
RUU is meant to recover the device in most cases. So if it didn't work, its very posible you have a fundamental USB connectivity issue. What response do you get when you type the adb command:
adb devices
What happens when you try to install recovery or a stock ROM? You need to give more information and specifics if you really want help.
And "don't know how many things" is not meaningful information. You need to list all the things you tried, and the results. Again, the lack of specific info makes it hard to help. I literally typed more asking you questions, than you bothered typing the answers. This does not bode well if you really want help.
You did not even answer all the questions I asked:
- What exactly have you tried to flash? (list the ROMs)
- Did you factory reset in bootloader?
Who is "they"? Again, you are being too vague.
I am personally more familiar with TWRP, so I would advise staying with that if you want help from me. Nothing against CWM. But again, its just what I'm more familiar with.
Click to expand...
Click to collapse
I Hi, thanks a lot. I did the factory reset from bootloader and tried to install Android_Revolution_HD-One_M8_5.0 and after doing the process it returns failed. Also One_M8_1.54.401.10_odexed and Jmz_M8_StockRootedOdex-ATT and I just tried with cyanogenmod 11. While I installed this in twrp recovery it said failed but when I reboo0ted in stared loading. I installed gapps and now my phone is working at least. But I still can't flash a snse rom or a gpe rom because it fails in twrp.
That's about all I can tell you. Oh, and I see it's in android 4.4.4.
ricm68 said:
I Hi, thanks a lot. I did the factory reset from bootloader and tried to install Android_Revolution_HD-One_M8_5.0 and after doing the process it returns failed. Also One_M8_1.54.401.10_odexed and Jmz_M8_StockRootedOdex-ATT and I just tried with cyanogenmod 11. While I installed this in twrp recovery it said failed but when I reboo0ted in stared loading. I installed gapps and now my phone is working at least. But I still can't flash a snse rom or a gpe rom because it fails in twrp.
That's about all I can tell you. Oh, and I see it's in android 4.4.4.
Click to expand...
Click to collapse
I don't understand how its so difficult for you to answer the basic questions I've asked multiple times now What happens when you run the RUU?
The RUU should restore the phone to full functionality, albeit with stock recovery, no root, etc. (if that is what you want).
Of course, this is not ideal if you want to install custom ROMs (which I assume is the case).
What I would try is to re-install TWRP. I'm not aware of any bugs in the newest version (which it appears you have) that would prevent flashing all the ROMs you mentioned. So maybe its just an improper install:
Re-download the latest TWRP img file. Place file in your fastboot folder. Open command prompt (navigate to the fastboot folder) and type:
fastboot erase cache
fastboot flash recovery "filename.img"
(where "filename.img" is the actual file name of the TWRP img file, with no quotes)
From there, load a ROM to your device, boot into TWRP and try flashing the ROM.
---------- Post added at 04:09 PM ---------- Previous post was at 03:10 PM ----------
Also, it is becoming apparent to me that doing a factory reset in bootloader corrupts the internal memory. My advice is to never do this (factory reset within the OS settings or in recovery if you need to).
But if the internal memory was corrupt, you shouldn't be able to load any files onto the phone (including ROMs). It seems that your internal memory is ok (you can transfer files to the phone, access them, etc)?
redpoint73 said:
I don't understand how its so difficult for you to answer the basic questions I've asked multiple times now What happens when you run the RUU?
The RUU should restore the phone to full functionality, albeit with stock recovery, no root, etc. (if that is what you want).
Of course, this is not ideal if you want to install custom ROMs (which I assume is the case).
What I would try is to re-install TWRP. I'm not aware of any bugs in the newest version (which it appears you have) that would prevent flashing all the ROMs you mentioned. So maybe its just an improper install:
Re-download the latest TWRP img file. Place file in your fastboot folder. Open command prompt (navigate to the fastboot folder) and type:
fastboot erase cache
fastboot flash recovery "filename.img"
(where "filename.img" is the actual file name of the TWRP img file, with no quotes)
From there, load a ROM to your device, boot into TWRP and try flashing the ROM.
---------- Post added at 04:09 PM ---------- Previous post was at 03:10 PM ----------
Also, it is becoming apparent to me that doing a factory reset in bootloader corrupts the internal memory. My advice is to never do this (factory reset within the OS settings or in recovery if you need to).
But if the internal memory was corrupt, you shouldn't be able to load any files onto the phone (including ROMs). It seems that your internal memory is ok (you can transfer files to the phone, access them, etc)?
Click to expand...
Click to collapse
The phone was working ok but suddenly wifi wouldn't turn on and mobile network stopped again!!!
I tried to intall android revolution but when it gets to installing the apps is says "set_perm: some changes failed". I click next and reboot and it just takes me back to recovery
redpoint73 said:
I don't understand how its so difficult for you to answer the basic questions I've asked multiple times now What happens when you run the RUU?
The RUU should restore the phone to full functionality, albeit with stock recovery, no root, etc. (if that is what you want).
Of course, this is not ideal if you want to install custom ROMs (which I assume is the case).
What I would try is to re-install TWRP. I'm not aware of any bugs in the newest version (which it appears you have) that would prevent flashing all the ROMs you mentioned. So maybe its just an improper install:
Re-download the latest TWRP img file. Place file in your fastboot folder. Open command prompt (navigate to the fastboot folder) and type:
fastboot erase cache
fastboot flash recovery "filename.img"
(where "filename.img" is the actual file name of the TWRP img file, with no quotes)
From there, load a ROM to your device, boot into TWRP and try flashing the ROM.
---------- Post added at 04:09 PM ---------- Previous post was at 03:10 PM ----------
Also, it is becoming apparent to me that doing a factory reset in bootloader corrupts the internal memory. My advice is to never do this (factory reset within the OS settings or in recovery if you need to).
But if the internal memory was corrupt, you shouldn't be able to load any files onto the phone (including ROMs). It seems that your internal memory is ok (you can transfer files to the phone, access them, etc)?
Click to expand...
Click to collapse
I did the factory reset from within cyanogenmod and it didn't wipe it. It restarted back to cyanogenmod. I copied andoid revolution to my internal memory and try to install from there.
ricm68 said:
The phone was working ok but suddenly wifi wouldn't turn on and mobile network stopped again!!!
I tried to intall android revolution but when it gets to installing the apps is says "set_perm: some changes failed". I click next and reboot and it just takes me back to recovery
Click to expand...
Click to collapse
You need to try the things I've suggested. I've made some definitive recommendations, and you seem to have ignored them. Honestly, I don't see a point in trying to help anymore, if you don't read what I'm taking the time to post; or you don't try what I've suggested.
Worst case is RUU and start over (install custom recovery again, etc.). But again, I have no idea what happened when you tried to RUU since you still haven't answered that.
You aren't going to make any progress, if you keep ignoring the advice that is given to you.
I'm doing what you told me!!!
I reinstalled twrp and tried but it failed again. Believe me, I've been doing what you suggested.
Can you please give me the steps to RUU and what ruu file to download and use. I really appreciate all you're doing for me and the time you are taking to help.
Sent from my One M8 using XDA Premium 4 mobile app
I was able to install cyanogen mod again and I am using the phone but I want to install sense again.
Sent from my One M8 using XDA Premium 4 mobile app
Requirements:
[ROOT REQUIRED]
[OEM Unlocking must be allowed under the developer options before flashing this file AND stay activated
as long as you want the device to stay unlocked (OnePlus implemented security features which locks the device on reboot with the switch off)]
* I am not responsible for bricked devices, thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about this method before using it!
* YOU are choosing to make these modifications.
* And if you point the finger at me for messing up your device, I will laugh at you.
Click to expand...
Click to collapse
WARNING: THESE FILES ARE BASED ON THE OXYGEN OS 2.1.1 FIRMWARE, PLEASE ANALYZE YOUR DEVINFO IF THE VERSION IS DIFFERENT TO MAKE SURE NOT BRICKING SOMETHING!
I have not upgraded my device to 2.1.2 yet because there have been some issues with the newest firmware.
Tested and confirmed working on:
OxygenOS 2.2.0 - thanks to @pryggi
OxygenOS 2.1.1
Hydrogen OS 1.2.0 - thanks to @fareed_xtreme
I looked at this thread, thanks to Naman Bhalla for this great work.
and found out that the file attached to this post is the answer to my problem, described in another thread.
After the whole day of work analyzing and dumping and saving via adb from my device to the pc and the other way around i finally did it.
On the frist screenshot is my situation before flashing the new devinfo, on the second after flashing the devinfo from the thread mentioned above.
By changing the bits with a Hex Editor of your choice, or by flashing the files below via dd:
Code:
dd bs=4096 of=/dev/block/bootdevice/by-name/devinfo if=/sdcard/oneplus2-devinfo-factory.img
The output should look like the following:
Code:
0+1 records in
0+1 records out
1024 bytes transferred in 0.005 secs (204800 bytes/sec)
You can restore your OnePlus 2 to a factory state while still having root or unlock your phone again without having to wipe it! :highfive:
Credits:
Naman Bhalla
Also to segv11 who already managed this in the OnePlus One and Nexus devices
wow nice job m8
sent from rooted phone
Modified the same location using a HEX Editor (root) whilst on the Hydrogen OS 1.2.0 and I must say it works.
Screenshot Attached. Good Find @thedropdead
Thank you and thanks for testing it out on Hydrogen OS @fareed_xtreme
It is not a Revolution like CM13 on the 1+2, but its helpful for people like me who use their developer devices as daily drivers and still want to lock and unlock the device because of security reasons without wiping the whole device.
fareed_xtreme said:
Modified the same location using a HEX Editor (root) whilst on the Hydrogen OS 1.2.0 and I must say it works.
Screenshot Attached. Good Find @thedropdead
Click to expand...
Click to collapse
thedropdead said:
Thank you and thanks for testing it out on Hydrogen OS @fareed_xtreme
It is not a Revolution like CM13 on the 1+2, but its helpful for people like me who use their developer devices as daily drivers and still want to lock and unlock the device because of security reasons without wiping the whole device.
Click to expand...
Click to collapse
I needed it for resetting the tamper flag. I have certain issues with my phone and might have to return it in the near future and hence this was important. So thanks again.
fareed_xtreme said:
I needed it for resetting the tamper flag. I have certain issues with my phone and might have to return it in the near future and hence this was important. So thanks again.
Click to expand...
Click to collapse
Thats another good thing to do with it
It was a pleasure to help you out mate
Thanks, I was waiting for this for securing my OPT. Has anyone tested, if it works also on OOS 2.2.0?
Just to clarify, the dd command should be executed in TWRP console?
Would be cool if someone could make an app for this like the Nexus devices have:
https://play.google.com/store/apps/details?id=net.segv11.bootunlocker
pryggi said:
Thanks, I was waiting for this for securing my OPT. Has anyone tested, if it works also on OOS 2.2.0?
Just to clarify, the dd command should be executed in TWRP console?
Would be cool if someone could make an app for this like the Nexus devices have:
https://play.google.com/store/apps/details?id=net.segv11.bootunlocker
Click to expand...
Click to collapse
Hello pryggi,
It should also work on OOS 2.2.0, you could check that by dumping the partition (by reversing the dd command) like this:
Code:
dd bs=4096 if=/dev/block/bootdevice/by-name/devinfo of=/sdcard/oneplus2-devinfo-oos220.img
And looking at the file in the hex editor for differences or by posting it here and i can check it for you.
I have executed the dd command from ADB Shell with the Phone connected via wireless ADB.
You can also execute dd in the Android Terminal Emulator App.
Thanks for your reply. My device is already unlocked. As I don't have a computer with ADB/drivers at hand right now, I managed to run the dd command in Terminal Emulator app after elevating with su. Result is attached. Viewing it in hex seems to confirm, that at least the locking bit seems to be in the same position.
pryggi said:
Thanks for your reply. My device is already unlocked. As I don't have a computer with ADB/drivers at hand right now, I managed to run the dd command in Terminal Emulator app after elevating with su. Result is attached. Viewing it in hex seems to confirm, that at least the locking bit seems to be in the same position.
Click to expand...
Click to collapse
Thank you for the Dump, i can confirm that the bit is at the same position and the unlock bit is the same.
I compared the file attached at my first post with yours and they are identical ( see attachment, sorry its german, meaning is they are identical).
So by flashing the factory.img from my first post or unchecking OEM Unlock allowed in the developer Settings your device should be locked again and can be unlocked by flashing the unlock.img via dd in ADB or the Android Terminal Emulator within the Phone.
Thanks for the further explanation. I was just wondering about this OEM Unlocking switch in dev options. What would happen, if one would use dd and the factory image file to lock the bootloader and leave the OEM Unlocking switch still unlocked...
I also am interested if this type of locking-unlocking can be done in TWRP... If it can be done there, then it does not offer any benefits in security, if my logic is correct. Although, I might be drifting off topic here.
pryggi said:
Thanks for the further explanation. I was just wondering about this OEM Unlocking switch in dev options. What would happen, if one would use dd and the factory image file to lock the bootloader and leave the OEM Unlocking switch still unlocked...
I also am interested if this type of locking-unlocking can be done in TWRP... If it can be done there, then it does not offer any benefits in security, if my logic is correct. Although, I might be drifting off topic here.
Click to expand...
Click to collapse
As i can remember i tried that too, by flashing the factory image partition via dd and leaving the switch on, the switch gets toggled off when rebooting, because the switch is just the representation of the unlocking bit in the partition. So when it is turned off, the software will set the bit to zero, means the device will get locked on reboot. Turning the switch on will not override the bit and the device can boot unlocked and the switch will stay on.
It is hard to explain
Your Idea about doing the same thing in TWRP since the ADB is available there is interesting.
I think the problem here is, that once you onlock and flash a custom recovery via fastboot, and relock the device, you already tampered with it, and twrp does provide much more options than the stock recovery image (ADB commands, ...).
So the problem here lies in flashing twrp.
I solved this problem by keeping the stock recovery and locking the device via the image file.
Once i want to use twrp, i unlock the phone by using the unlock.img and use "fastboot boot twrp.img" to boot twrp to backup my device or some other action.
I know that this means if my device gets bricked in this locked state with stock recovery i will have to unlock it normally, but before making any important changes to my software i always unlock my device first in case something goes wrong and with the stock recovery i could not even flash anything so making huge software changes requires me to unlock my device and boot twrp
Hope that this post helps somehow
FYI: The HEX hack must work on almost all OPT OS Releases.Kinda universal
fareed_xtreme said:
FYI: The HEX hack must work on almost all OPT OS Releases.Kinda universal
Click to expand...
Click to collapse
That is right, i just included the notice in the first post so nobody can tell me i have not told them
It is also possible that OnePlus changes the layout of that partition in one of the upcoming updates/releases and that is why it is still mentioned in the first post, thank you anyway.
@thedropdead I've a question: I should use the "modified" devinfo.img AFTER I go back to stock, if I want to unlock my phone without wiping data, right ? So I go back to stock, flash in fastboot or in terminal emulator the .img, and that's good ? I'me unlocked without data wiped ?
casual_kikoo said:
@thedropdead I've a question: I should use the "modified" devinfo.img AFTER I go back to stock, if I want to unlock my phone without wiping data, right ? So I go back to stock, flash in fastboot or in terminal emulator the .img, and that's good ? I'me unlocked without data wiped ?
Click to expand...
Click to collapse
That should be the plan if i have understood everything right.
So you are on the custom ROM, want to go back to the stock ROM?
If that is the case i do not see why you should want to flash any image.
You can use TWRP to wipe and then flash the stock ROM, your phone should still be unlocked right?
Please someone correct me if i am wrong.
It would be great if you could tell me what you are trying to achieve.
The unlock image had the purpose to help someone unlock their device if they have a rooted device but have locked it after flashing everything for security reasons.
thedropdead said:
That should be the plan if i have understood everything right.
So you are on the custom ROM, want to go back to the stock ROM?
If that is the case i do not see why you should want to flash any image.
You can use TWRP to wipe and then flash the stock ROM, your phone should still be unlocked right?
Please someone correct me if i am wrong.
It would be great if you could tell me what you are trying to achieve.
The unlock image had the purpose to help someone unlock their device if they have a rooted device but have locked it after flashing everything for security reasons.
Click to expand...
Click to collapse
Well, for now I'm under CM13, and, yeah, I know I could wipe and flash stock in TWRP, I just want to know in case .
casual_kikoo said:
Well, for now I'm under CM13, and, yeah, I know I could wipe and flash stock in TWRP, I just want to know in case .
Click to expand...
Click to collapse
Okay thanks for the clarification.
In the Case of using some unbrick Tool and thus resetting everything including recovery to stock your phone should lock on the first stock boot.
Once it is locked and you do not have root, which would be the case, you have no possibility to flash the img via fastboot or the emulator.
so in conclusion you are better off with wiping and flashing via twrp so you can still flash something if anything goes wrong
It works on OxygenOS 3.0.2 too. I edit the same location using a HEX Editor. And everything is fine.
Hey guys, sounds like this is exactly what I've been looking for. Thanks for figuring this out.
But, I'm a bit of a noob, so can you break it down into like a hundred very clear steps?
OFFICIAL ONEPLUS 2 STOCK RESET
SOURCE : OnePlus L2 Support Team
VERSION : OxygenOS 2.2.0
DOWNLOADS
1. OnePlus2 Stock Reset Oxygen OS 2.2.0 Google Drive | Mediafire
2. Qualcomm Drivers Version 1.00.11 Google Drive | Mediafire
INSTRUCTIONS
You are doing this on your own responsibility. I take no responsibility whatsoever.
(THIS WILL WIPE YOUR ONEPLUS INCLUDING INTERNAL SD)
Download both the files from above and extract them (WinRAR, WinZIP, 7ZIP etc). You should have 2 folders: "OnePlus2_14_A.11_151211" and "qc"
A. Install the Certificates followed by the Qualcomm drivers.
1. Restart your computer with Driver Signature Enforcement Disabled (Advanced Startup) Let me Google it For You
2. Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
3. Run the Qualcomm setup wizard (also located in the qc folder)
4. When completed, restart your PC again with Driver Signature Enforcement Disabled (Advanced Startup)
5. Turn off your phone and disconnect the USB cable from the phone.
6. Hold vol-up and plug in the USB(Do not press Power button). The screen will stay black but you will hear a sound from windows that a device is attached.
7. The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install. (Got the RELINK issue? Take a look here: http://forum.xda-developers.com/show...1&postcount=46)
B. Flashing Process
1. Open the OnePlus2_14_A.11_151211 folder and open "MSM8994DownloadTool.exe"
2. Look if your phone is detected in the list. everything is Chinese but you will see one row with different chinese text from the rest within the list. If not, recheck if driver is detected in Device Manager (If not, go back to Step A - Line 4).
3. First click the right square Chinese button. This will perform an integrity check on the downloaded files by verifying the MD5 hash values.
4. The system will seem to hang for a bit but should give you a pop up with the results of the above verification. When everything is ok. Press the start button. and let the progress finish. (If something is not ok, you will have to re-download the images. Google Drive can help extract only the necessary files.)
5. When it's done. Disconnect the USB cable and turn on the device.
C. Reset TAMPER Flag (Optional)
(This may potentially change your SmartPhone to a rather large paperweight and I will just laugh at you bearing no responsibility)
+ This part of the guide is not an Official Procedure and is in no way affiliated to OnePlus
+ It is advisable to do this before any of the above mentioned operations.
+ Prerequisites:
Root
HEX Editor with root features
Root File Manager
+ BEWARE: You are modifying partitions which cannot be restored regardless of what you flash. You have been warned AGAIN
1. In File Manager browse to the devinfo partition (dev/block/bootdevice/by-name/)
2. Open devinfo using the HEX Editor.
3. Modify the TamperBit (attached screenshot) from 01 to 00.
4. Save and reboot to fastboot.
5. Type fastboot oem device-info to confirm.
CREDITS
OnePlus Team for the Files.
@paultje162 for adaptation of Instructions. Refer his thread here if you are looking for an older version of stock reset (2.1.1).
@thedropdead for his work on Tamper Reset
If this thread has helped you, do press the THANKS button. Should you have issues, questions or doubts, write in this thread.
Just need to confirm that these files are actually official
Pm me the s3 support link
---------- Post added at 13:14 ---------- Previous post was at 13:10 ----------
And my friend
You need to install the test certificate first !
Edit:- file confirmed legit ! Totally official, way to go, @fareed_xtreme !
[email protected] said:
Just need to confirm that these files are actually official
Pm me the s3 support link
---------- Post added at 13:14 ---------- Previous post was at 13:10 ----------
And my friend
You need to install the test certificate first !
Click to expand...
Click to collapse
Thanks for spotting the error. I have fixed the heading. S3 Link PMed.
fareed_xtreme said:
Thanks for spotting the error. I have fixed the heading. S3 Link PMed.
Click to expand...
Click to collapse
Whenever you get drivers like this, dig into their folders and you'll find important documents and instructions to use
That is how I found out about this certificate
Is there any similar process por ONEPLUS ONE?
I only have fastboot mode, without recovery and bootloader locked (fastboot oem unlock doesn't work)
http://forum.xda-developers.com/showthread.php?t=2970390
@xbit
xbit said:
Is there any similar process por ONEPLUS ONE?
I only have fastboot mode, without recovery and bootloader locked (fastboot oem unlock doesn't work)
Click to expand...
Click to collapse
Quick search and: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
beaverhead said:
http://forum.xda-developers.com/showthread.php?t=2970390
@xbit
Click to expand...
Click to collapse
This didn't work for me:
fastboot oem unlock didn't work because I had a corrupt bootloader.
Spannaa said:
Quick search and: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
But this was great! My OPO is alive now. Thanks
Thank you!!!! this worked.
I was eventually able to get the restore program to recognize it and restore it so it could boot normally. Thank you!
Download from your Link
https://drive.google.com/folderview?id=0BxFd4Zc3_d1CWDdOSFFIVG42VTg&usp=sharing
the File:
OnePlus2_14_A.11_151211.rar
Extract it.
But where is the "QC Folder"
found only "OnePlus2_14_A.11_151211"
Your Link to:
http://forum.xda-developers.com/show...1&postcount=46
is wrong. (Not complete) Error 404
Wagi99 said:
Download from your Link
https://drive.google.com/folderview?id=0BxFd4Zc3_d1CWDdOSFFIVG42VTg&usp=sharing
the File:
OnePlus2_14_A.11_151211.rar
Extract it.
But where is the "QC Folder"
found only "OnePlus2_14_A.11_151211"
Your Link to:
http://forum.xda-developers.com/show...1&postcount=46
is wrong. (Not complete) Error 404
Click to expand...
Click to collapse
Yep, the qc folder is missing from the zip.
The link should be: http://forum.xda-developers.com/showpost.php?p=64674951&postcount=46
I suspect these are both down to copying & pasting the instructions from @paultje162's thread and I'm sure @fareed_xtreme will sort it out when he gets the chance.
Wagi99 said:
Download from your Link
https://drive.google.com/folderview?id=0BxFd4Zc3_d1CWDdOSFFIVG42VTg&usp=sharing
the File:
OnePlus2_14_A.11_151211.rar
Extract it.
But where is the "QC Folder"
found only "OnePlus2_14_A.11_151211"
Your Link to:
http://forum.xda-developers.com/show...1&postcount=46
is wrong. (Not complete) Error 404
Click to expand...
Click to collapse
Thanks for spotting the errors. I have updated them. It is indeed a miss on my part in regards to the QC. Hence I have uploaded it separately and updated the instructions.
Spannaa said:
Yep, the qc folder is missing from the zip.
The link should be: http://forum.xda-developers.com/showpost.php?p=64674951&postcount=46
I suspect these are both down to copying & pasting the instructions from @paultje162's thread and I'm sure @fareed_xtreme will sort it out when he gets the chance.
Click to expand...
Click to collapse
Yup, A copy paste is not the right way to copy a link. Haven't been around these threads for quite some time and guess i did not remember that the links are trimmed down. Thanks for the correct link.
Updated Information with UnTamper Guide
Hello
Doing the anti tamper method you did. Shouldn't this be easier by doing "fastboot oem lock" ?
I think it should have the same effects. Of course, this command must be done when an official ROM is on the phone, doing this in a custom ROM can cause unexpected behaviour, including bricking.
albertocastillo2001 said:
Hello
Doing the anti tamper method you did. Shouldn't this be easier by doing "fastboot oem lock" ?
I think it should have the same effects. Of course, this command must be done when an official ROM is on the phone, doing this in a custom ROM can cause unexpected behaviour, including bricking.
Click to expand...
Click to collapse
From my personal experience, if the Tamper Flag trips, then no matter how official you go it will not go back to Device Tamper= False.
The files in my First Post restores your phone back to an out of box phone state even locking the bootloader but it will not change the tamper flag. Those files are used by OnePlus Support to fix OS issues. Also the fastboot oem lock has not managed for me personally to get the tamper flag back to default (Same as in OPO once down, its down). So the only way for now for the OPT is by modifying the bit that handles the tamper flag.
You are right. Tamper Flag usually trips when you try to relock the bootloader when having root and other non-stock partitions (custom kernel, recovery etc). (Learned the hard way with my old OnePlus 2. Got it swapped for a new one though as the old one was faulty )
Hope this helps.
fareed_xtreme said:
From my personal experience, if the Tamper Flag trips, then no matter how official you go it will not go back to Device Tamper= False.
The files in my First Post restores your phone back to an out of box phone state even locking the bootloader but it will not change the tamper flag. Those files are used by OnePlus Support to fix OS issues. Also the fastboot oem lock has not managed for me personally to get the tamper flag back to default (Same as in OPO once down, its down). So the only way for now for the OPT is by modifying the bit that handles the tamper flag.
You are right. Tamper Flag usually trips when you try to relock the bootloader when having root and other non-stock partitions (custom kernel, recovery etc). (Learned the hard way with my old OnePlus 2. Got it swapped for a new one though as the old one was faulty )
Hope this helps.
Click to expand...
Click to collapse
Thanks for your reply. I noticed that these are the files that OnePlus team sends you when they want to remote into your device to flash the system. I noticed these are password encrypted. I have a session with them on Monday 6th.
I sent the files they sent me to decryption to get the password to a website that does this. However, they couldn't. My other plan was just to catch the password when having the remote session with them.
Since you already posted the files here, this is no longer needed. Seems you did this earlier than me.
The reason they want to do a full flash on my phone is due to the fact that I have a dual SIM issue. At the beginning both SIMs worked until I had to do a change on the second SIM network (it's an international SIM card that works in every country so you must set up the network manually). Since I tried to change the network. Something got messed up and now only one SIM works at a time. I tried restoring the network settings to automatic with no go. And I also tried to do hard restore on the phone to start over to ensure this would solve the issue.
This didn't solve the issue. So it probably means the settings were done in a partition which is not "/data". So a hard reset obviously wouldn't work. But a full flash surely will.
I asked them if I could do this myself by just sending me the files. I have a good expertise on fastboot, ADB and Linux, and I also understand the partition list and partition images. However, since the phone is not rooted or modified in anyway. I decided I will let them do it for me.
I do have a question thought. How did you find about the anti tamper thing? I assume you had remote session with them, and this is why you have those files. Did they "relock" this for you?
I assume they look at this when they get defective devices returned.
Thanks
albertocastillo2001 said:
Thanks for your reply. I noticed that these are the files that OnePlus team sends you when they want to remote into your device to flash the system. I noticed these are password encrypted. I have a session with them on Monday 6th.
I sent the files they sent me to decryption to get the password to a website that does this. However, they couldn't. My other plan was just to catch the password when having the remote session with them.
Since you already posted the files here, this is no longer needed. Seems you did this earlier than me.
The reason they want to do a full flash on my phone is due to the fact that I have a dual SIM issue. At the beginning both SIMs worked until I had to do a change on the second SIM network (it's an international SIM card that works in every country so you must set up the network manually). Since I tried to change the network. Something got messed up and now only one SIM works at a time. I tried restoring the network settings to automatic with no go. And I also tried to do hard restore on the phone to start over to ensure this would solve the issue.
This didn't solve the issue. So it probably means the settings were done in a partition which is not "/data". So a hard reset obviously wouldn't work. But a full flash surely will.
I asked them if I could do this myself by just sending me the files. I have a good expertise on fastboot, ADB and Linux, and I also understand the partition list and partition images. However, since the phone is not rooted or modified in anyway. I decided I will let them do it for me.
I do have a question thought. How did you find about the anti tamper thing? I assume you had remote session with them, and this is why you have those files. Did they "relock" this for you?
I assume they look at this when they get defective devices returned.
Thanks
Click to expand...
Click to collapse
Please note that the Tamper part of the guide is NOT done by OnePlus. Please note that OnePlus is in no way affiliated to the Tamper part of the guide. The Tamper guide is a result of comprehensive research conducted by thedropdead (information provided in the First Post). The guide is an easier interpretation of all the research that went in there.
OnePlus will only reflash this package which will re-lock the Bootloader only. Tamper Flag is not modified. So sit tight and let them reflash it for you.
You are right to assume I had a session with them earlier and that's how i have the files.
Thanks for your reply.
I would say that if the remote support doesn't untamper the device then it might mean they don't even look at it if the device is returned.
Thanks!
albertocastillo2001 said:
Thanks for your reply.
I would say that if the remote support doesn't untamper the device then it might mean they don't even look at it if the device is returned.
Thanks!
Click to expand...
Click to collapse
Remote Support didn't look into mine. However, not very sure about whether it is checked on returning it. Mine went untampered.
fareed_xtreme said:
Remote Support didn't look into mine. However, not very sure about whether it is checked on returning it. Mine went untampered.
Click to expand...
Click to collapse
Oh, then what happened? I thought the remote support tried to fix your phone. Since you said they didn't untamper the device after I expected they remoted to your phone. What happened then?
Thanks