Related
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.
Need link to download the specific software specified in the title of this thread. Came across the one loaded on Google by another xda member but having difficulties downloading it. If you have it mirrored to another cloud service please provide me with the link. I am mostly gunning to get my hands on all of the .img files which come inside it so that I may review them via a hex editor and unlock my bootloader the sneaky way since Huawei refuses to reply back to my emails. Many thanks in advance.
Update: I was able to get my hands on the update.app file. So now will begin extraction and making my changes to hack the bootloader status on my device. If Huawei has responded back to you with your proper bootloader unlock code then you were fortunate. I myself have run out of patience with them and am now handling this on my own personal level.
Modding.MyMind said:
Need link to download the specific software specified in the title of this thread. Came across the one loaded on Google by another xda member but having difficulties downloading it. If you have it mirrored to another cloud service please provide me with the link. I am mostly gunning to get my hands on all of the .img files which come inside it so that I may review them via a hex editor and unlock my bootloader the sneaky way since Huawei refuses to reply back to my emails. Many thanks in advance.
Update: I was able to get my hands on the update.app file. So now will begin extraction and making my changes to hack the bootloader status on my device. If Huawei has responded back to you with your proper bootloader unlock code then you were fortunate. I myself have run out of patience with them and am now handling this on my own personal level.
Click to expand...
Click to collapse
Having trouble getting the bootloader unlock code? Try this:
Most of the issues are that emails sent outside of Shenzhen China business time during the week are not answered. They go into an email black hole. You'd have to send in the bootloader unlock request email really late here in the US or set up some way to send your email later automatically like I did with the Chrome extension Boomerang to get the code for my second HAM2. Currently sending in a request around 9pm EST to 4am EST Sunday - Thursday is the best time to email for the unlock code Sun-Thurs corresponds to Monday-Friday at Huawei in China.
I have emailed outside of those times and not gotten a response. After figuring out the time difference and setting up boomerang for an automated send later feature with my email the code arrived a couple hours after it was sent and I saw it when I woke up the next morning.
Sent from my MT2L03 using Tapatalk
@arcadesdude, thanks for your input, but unfortunately that route has failed me as well. Been at it with these emails since late last year. My guess is that my emails are getting lost in middle of a bunch of other emails they may be receiving or I'm going to their spam mail which they probably ignore. Either case, all attempts have not been successful. I found the EFI image and boot image inside the update.app last night. So far so good as it looks like I can easily hack this update and finally get my bootloader unlocked so I may do what I need to do with it.
Modding.MyMind said:
@arcadesdude, thanks for your input, but unfortunately that route has failed me as well. Been at it with these emails since late last year. My guess is that my emails are getting lost in middle of a bunch of other emails they may be receiving or I'm going to their spam mail which they probably ignore. Either case, all attempts have not been successful. I found the EFI image and boot image inside the update.app last night. So far so good as it looks like I can easily hack this update and finally get my bootloader unlocked so I may do what I need to do with it.
Click to expand...
Click to collapse
You can unlock the bootloader without the bootloader unlock code?
Did you try another email address? Another member on here used another address and got through to Huawei.
Sent from my MT2L03 using Tapatalk
arcadesdude said:
You can unlock the bootloader without the bootloader unlock code?
Did you try another email address? Another member on here used another address and got through to Huawei.
Sent from my MT2L03 using Tapatalk
Click to expand...
Click to collapse
No, the bootloader code is still required. All I am going to do is modify the source via a hex editor so that I can input a code of my choosing and force it to accept that code and thus unlock my bootloader. That is very possible . Should of done this already but I wanted to give Huawei a chance - but they failed.
Modding.MyMind said:
No, the bootloader code is still required. All I am going to do is modify the source via a hex editor so that I can input a code of my choosing and force it to accept that code and thus unlock my bootloader. That is very possible . Should of done this already but I wanted to give Huawei a chance - but they failed.
Click to expand...
Click to collapse
I didn't know you could do that. Is it essentially just flashing your modified bootloader partition to the phone using adb like we flash the recovery partition?
arcadesdude said:
I didn't know you could do that. Is it essentially just flashing your modified bootloader partition to the phone using adb like we flash the recovery partition?
Click to expand...
Click to collapse
Pretty much, but not with adb. Using fastboot.
also, i guess you also need disable the verification chain? but how? I heard it probably start from very beginning, ROM, a real read only rom. if you flash hacked aboot, sbl probably refuse to boot it, right?
xordos said:
also, i guess you also need disable the verification chain? but how? I heard it probably start from very beginning, ROM, a real read only rom. if you flash hacked aboot, sbl probably refuse to boot it, right?
Click to expand...
Click to collapse
With a bootloader being locked you are presumably limited on what can and cannot be flashed. With that in mind should a modification be incorrectly done for a device with a locked bootloader then it would be safe to say that the flash would be denied and no harm done. Because I will be modifying the source to accept my personal code then this will not have any affect towards flashing. The device will even accept it. Then, when I enter my code and reboot, the device will simply say it is unlocked. The only catch to this though is that if I flash back to the original then the bootloader should technically relock itself. I will open a thread on this procedure down the road when I get time and even include my mods so others may compare it with the stock to see the differences.
Modding.MyMind said:
With a bootloader being locked you are presumably limited on what can and cannot be flashed. With that in mind should a modification be incorrectly done for a device with a locked bootloader then it would be safe to say that the flash would be denied and no harm done. Because I will be modifying the source to accept my personal code then this will not have any affect towards flashing. The device will even accept it. Then, when I enter my code and reboot, the device will simply say it is unlocked. The only catch to this though is that if I flash back to the original then the bootloader should technically relock itself. I will open a thread on this procedure down the road when I get time and even include my mods so others may compare it with the stock to see the differences.
Click to expand...
Click to collapse
Regarding the limitation, early I thought you are going to modify/repackage the UPDATE.APP, as that way, if (a big if) it works, ideally you can flash to any partition. (There is some thread in xda that discussion about read/repackage the huawei UPDATE.APP)
But as we discussed briefly long time back, this whole thing is really really risky, if the booting path to fastboot got damage, then pretty much the phone is hard bricked.
Probably if you stick with flash with fastboot, then the risk will be lesser but man, this is scary stuff..
Regarding the validation chain, I got info from following article:
http://www.newandroidbook.com/Articles/aboot.html
A few paragraph after the Figure One.
Let's see...
PS, maybe you can continue try some different email address and sent at correct time to Huawei for the code...
PS2, another thought, maybe inject a superSU to the UPDATE.APP system image will work? not sure how strict they are validating when flashing UPDATE.APP and/or when booting the system partition.
xordos said:
Regarding the limitation, early I thought you are going to modify/repackage the UPDATE.APP, as that way, if (a big if) it works, ideally you can flash to any partition. (There is some thread in xda that discussion about read/repackage the huawei UPDATE.APP)
But as we discussed briefly long time back, this whole thing is really really risky, if the booting path to fastboot got damage, then pretty much the phone is hard bricked.
Probably if you stick with flash with fastboot, then the risk will be lesser but man, this is scary stuff..
Regarding the validation chain, I got info from following article:
http://www.newandroidbook.com/Articles/aboot.html
A few paragraph after the Figure One.
Let's see...
PS, maybe you can continue try some different email address and sent at correct time to Huawei for the code...
Click to expand...
Click to collapse
I won't be using the update.app parsay. Merely needed it so I can locate the images I want by viewing it with a hex editor and then extracting them so that I can solely focus on those images using a hex editor and once I make my patch(s) then I will use fastboot to flash those images to their respective partitions on the device. It really isn't that risky as long as you know what to look for. I won't be that guy that says "oops" in this case lol. So, I'm not worried about possibly bricking this device one bit .
Modding.MyMind said:
I won't be using the update.app parsay. Merely needed it so I can locate the images I want by viewing it with a hex editor and then extracting them so that I can solely focus on those images using a hex editor and once I make my patch(s) then I will use fastboot to flash those images to their respective partitions on the device. It really isn't that risky as long as you know what to look for. I won't be that guy that says "oops" in this case lol. So, I'm not worried about possibly bricking this device one bit .
Click to expand...
Click to collapse
Just curious, what are you planning to do that requires an unlocked bootloader?
ScoobSTi said:
Just curious, what are you planning to do that requires an unlocked bootloader?
Click to expand...
Click to collapse
Something lol
I'm not sure why you can't get the code from Huawei ...but I'm kinda glad you can't. seems your gathering nice info about this phone.
Sent from my MT2L03 using XDA Free mobile app
Modding.MyMind said:
Something lol
Click to expand...
Click to collapse
Just in case you're being super extremely nice and kind and trying to make a ROM for us, the other developer has hit a huge roadblock on CM11/12 you should know about.
ScoobSTi said:
Just in case you're being super extremely nice and kind and trying to make a ROM for us, the other developer has hit a huge roadblock on CM11/12 you should know about.
Click to expand...
Click to collapse
Even he is not plan to build CM, but as the man who build first recovery for us, I think he wont stop until he can play with his own baby in his phone.
Modding.MyMind said:
I won't be using the update.app parsay. Merely needed it so I can locate the images I want by viewing it with a hex editor and then extracting them so that I can solely focus on those images using a hex editor and once I make my patch(s) then I will use fastboot to flash those images to their respective partitions on the device. It really isn't that risky as long as you know what to look for. I won't be that guy that says "oops" in this case lol. So, I'm not worried about possibly bricking this device one bit .
Click to expand...
Click to collapse
1. How are you going to flash image via fastboot if your bootloader is locked?
2. You have to hack fastboot image to pass throuth unlock code verification without or with some random code. But even if you do so, you won't be able to flash fastboot image via fastboot even with unlocked bootloader.
I would'nt touch fastboot at all 'cause it's a high risk to get a hard brick.
I have found unlock code in some partition of my device, but I dunno was it there initially or was written there after unlocking. If the first case is and fastboot just compares entered code with saved one in device, then you can try to make update.app with injected su, as xordos offered, to be able to read this partition.
Injecting su into the update.app woukdnt work. The update.app has it's own crc and such. So to simply say, it won't work. You also answered your questions with remarks 1 and 2. One exception is that yes, you can flash the image. As for risks, it's only there if you mess something up - development typically is about taking risks . The fastboot image won't technically brick the device anyways. At best a soft brick may occur, but to be honest since "bricking" is up for discussion; bricking can occur simply by making a change to the build.prop file and not fixing it's permissions prior to rebooting. Unless you "hard" brick the device, then it can always be recovered.
You said the image or images can't be flashed with a locked bootloader, while yes is technically true, but understand that it isn't 100%, because you see, when your device recieves an update initially the devices bootloader is expected to be locked, right? Yet, magically enough the update goes through, the phone reboots, you either hate or love the new update. Something to think about before actually saying an image can't be flashed . Instead, I would have you ask yourself, "how?".
xordos said:
Even he is not plan to build CM, but as the man who build first recovery for us, I think he wont stop until he can play with his own baby in his phone.
Click to expand...
Click to collapse
And best believe, I want to play
Hi all,
I installed CM11 onto my S5830i (GB) and managed to get it all working. I had to install S5360_XXMK1 modem and a newer version of CWM to prevent the "Status 7" error. Anyway, it all worked and I had CM11 up and running. Unfortunately, I had to remove it, I couldn't click any links in the browser and the browser was slow as all buggery even on a fast wifi connection. So I fired up Odin and tried to put the stock firmware on (i don't have an original state backup, the phone came with a custom rom on it already). I got these files
CSC_S5830i_BTUMD1.tar.md5
MODEM_S5830i_XXMD1.tar.md5
PDA_S5830i_XXMD1.tar.md5
But something's messing up, after Odin does its thing and the phone restarts, I notice something on the screen during restart saying it failed to format the /data partition. When I let the phone boot up normally it just stays on the "Samsung" startup animation forever. If I go into samsung recovery and try to do a factory reset, this is what I see
Code:
-- Wiping data...
Formatting /data...
E:format_volume: rfs format failed on /dev/stl11
Formatting /cache...
Data wipe complete.
Obviously, something's wrong there, can anyone tell me how to fix it pleeeeese, I'd be eternally grateful.
Thanks
NS
EDIT: I think the CM install may have messed around with my partitioning. I do not have a pit file for the phone (GB Version) and am reluctant to be using the re-partition option in Odin. I can find pit files online, but they're either not the correct version or the poster doesn't even say what version it is. I am just so lost and confused with all this.
@NicSure, Flashing wrong base band into your Ace-i is ill advised mate, go to CM11 discussion topic and read my comments . ( You will damage your EFS partition,thus device may become hard bricked in many cases)
As for troubleshooting : Already explained all of the instructions in details in many places, So I will provide links/hints for now. If your problem persisted, let us know
Here we go mate:
1. Official source for your stock firmware CSC/MODEM/PDA >> this page (sammobile.com)
2. Study this topic to get the hang of Wipe flash-able packages,,, How to produce them, Boot looder and pit files required for the process , etc etc,, all well instructed here
3. Read few last pages of this topic; my comments; for more insight into your problem. Please be advised you have already converted your partitions into MTD ,therefore formatting /data ( concerting back into RFS partitions ) might be failure through CWM/e3 recovery >> Odin process is required for"stl11" .
Hope I did help you
ehsanotaku said:
@NicSure, Flashing wrong base band into your Ace-i is ill advised mate, go to CM11 discussion topic and read my comments . ( You will damage your EFS partition,thus device may become hard bricked in many cases)
As for troubleshooting : Already explained all of the instructions in details in many places, So I will provide links/hints for now. If your problem persisted, let us know
Here we go mate:
1. Official source for your stock firmware CSC/MODEM/PDA >> this page (sammobile.com)
2. Study this topic to get the hang of Wipe flash-able packages,,, How to produce them, Boot looder and pit files required for the process , etc etc,, all well instructed here
3. Read few last pages of this topic; my comments; for more insight into your problem. Please be advised you have already converted your partitions into MTD ,therefore formatting /data ( concerting back into RFS partitions ) might be failure through CWM/e3 recovery >> Odin process is required for"stl11" .
Hope I did help you
Click to expand...
Click to collapse
Thanks but you were too technical. I have been to a lot of those pages you linked and it's not all obvious what's going on. You spoke about "base band", I have no idea what that is. I have no idea what RFS, MTD
are (file systems?), not do I know where to get a bootloader from. Sam mobile won't let me download anything without paying and/or signing up which I'm reluctant to do. I'll re-read the posts you linked to (I had already seen them) and see if something starts to make more sense.
For instance:
"Please be advised you have already converted your partitions into MTD ,therefore formatting /data ( concerting back into RFS partitions ) might be failure through CWM/e3 recovery >> Odin process is required for"stl11"
May as well have been in Klingon, I didn't understand a word of it.
EDIT:
I've reviewed those threads again. Seems I need to use split fus on the downloaded file from SamMobile (which I had to register to download, not happy about that) and use the "wipe" versions. I need a pit file, there's no info anywhere on how to get that. So I've just done a general google and hopefully I've downloaded one (more info on that is needed in the tuts). And the bootloader is attached to the unbrick thread, but, is that the ONLY bootloader? Do I need a specific one for my region? Do I need a specific pit file for my region? All this info is not supplied anywhere, Newcomers are not going to know this stuff and it needs to be made clear in the tutorials. Most of the tuts have broken links (split fus for instance), so I'm not sure if the stuff I googled is actually the same. Absolute nightmare.
NicSure said:
You spoke about "base band", I have no idea what that is.
Click to expand...
Click to collapse
Please read the link was provided for your convenient. ( Absolutely suitable for beginners).
NicSure said:
I have no idea what RFS, MTD
are (file systems?)
Click to expand...
Click to collapse
"Robust File System" is more or less equivalent to your FAT/FAT32 of your PC ( Samsung file system Format,, not going to add "Journalling system" to the mix, since you are not a sport ,,FYI : You are supposed to know common terms such as MTD , RFS when you are massing with CM11 mate >> Read the first page thoroughly, before start experimenting with Cyanogen stuff,,,
MTD (Memory Technology Device) supports YAFFS2 as a file system residing on it and is considered some type of of Partition Map.
NicSure said:
not do I know where to get a boot loader from. Sam mobile won't let me download anything without paying and/or signing up which I'm reluctant to do
Click to expand...
Click to collapse
Again actually start reading this topic ( quite self explanatory).
NicSure said:
Seems I need to use split fus on the downloaded file from SamMobile (which I had to register to download, not happy about that) and use the "wipe" versions.
Click to expand...
Click to collapse
This topic contains well made Wipe packages ( European version is compatible with your device, If you are reluctant to register though).
NicSure said:
I need a pit file, there's no info anywhere.
Click to expand...
Click to collapse
Again, Read the topic I mentioned above. You are on Cooperve device, so be aware of wrong file ( "cooperve_0623.pit" resided inside Odin3.v3.07.Cooperve folder) All of the related links already provided , Just take your time and read mate.
I'd already read the posts you linked to multiple times thank you. They may be "straight forward" to you, but I can assure you they are certainly not so for a newcomer. Too many things are vague, missing or not explained properly.
In any case, I managed to get the stock firmware back on after trawling the internet for a .pit file, downloading the firmware, splitting it, taking the wipe versions with the pit and the bootloader and using Odin to fully flash the phone back to stock firmware, Finally. The tuts here are indeed a lot of help, but so so so disjointed.
Also, why would changing the base band effect the file system? How could it cause physical damage to NAND memory. I'm confused. I assume you mean physical damage, because if not, why would it be ill-advised to change it if it could just be changed back with no ill-effects?
@NicSure, First of all Thanks button implanted here for a good reason and most likely you are the first person who was complaining about my assistance (How information is organized and distributed for new commers is not my responsibility nor distribution of step-by-step instructions ) . Second of all You were complaining about the technical terms and jargon, But know you are asking for technical reason in regard of the consequences of flashing Galaxy Y GT-S5360 inside your ACE-i device !
I did mention about EFS partition corruption, which renders your device mobile network communication useless and hard bricking of your device.which is a phone that shows no signs of power-on and will not access download mode with button combo. You did assume wrong mate.
Generally speaking, Carriers use different radio frequencies in our respective countries , Different Devices do contain different modem hardware inside, So you are not encouraged to do what you have done in the first place.
If you are not flashing the correct versions for your phone , or if the flash gets interrupted there’s a good chance you will Hard Brick your device, thus we may need hardwired access to modify/erase and rewrite chip's code ( Service is required).
When a phone is in a hard-bricked state it’s most likely that the bootloaders, which is the phones initial code to launch the phones ROM, becomes corrupted.
The only way to revive the phone is to rewrite the bootloader code, because the phone does not power on ., So you see so many things could go wrong :silly:
ehsanotaku said:
@NicSure, First of all Thanks button implanted here for a good reason and most likely you are the first person who was complaining about my assistance (How information is organized and distributed for new commers is not my responsibility nor distribution of step-by-step instructions ) . Second of all You were complaining about the technical terms and jargon, But know you are asking for technical reason in regard of the consequences of flashing Galaxy Y GT-S5360 inside your ACE-i device !
I did mention about EFS partition corruption, which renders your device mobile network communication useless and hard bricking of your device.which is a phone that shows no signs of power-on and will not access download mode with button combo. You did assume wrong mate.
Generally speaking, Carriers use different radio frequencies in our respective countries , Different Devices do contain different modem hardware inside, So you are not encouraged to do what you have done in the first place.
If you are not flashing the correct versions for your phone , or if the flash gets interrupted there’s a good chance you will Hard Brick your device, thus we may need hardwired access to modify/erase and rewrite chip's code ( Service is required).
When a phone is in a hard-bricked state it’s most likely that the bootloaders, which is the phones initial code to launch the phones ROM, becomes corrupted.
The only way to revive the phone is to rewrite the bootloader code, because the phone does not power on ., So you see so many things could go wrong :silly:
Click to expand...
Click to collapse
Firstly, I'm not complaining, I'm criticizing, there's a difference. I was critical of your language and terminology as it didn't match the links you posted. Also the level of technical talk you used toward a clear newbie who would obviously never understand it without clarification. If that offends you then I'm sorry, I'm just speaking my mind. Help offered, no matter how kindly or freely is useless if it cannot be understood. I generally take a very irritated approach to people who post links (with the implication that the information is freely available if you'd bother to look) in response to perfectly polite questions, especially when I'd already read ALL the posts you linked to before and had trouble with them, that is why I posted, to get a little more basic understanding, not be presented with links to material I'd already read and needed help with. Also, after some researching, with regard to the base-band, I think you're wrong, there's no way flashing a different base-band separately could effect the bootloader, no way at all. I seriously doubt it could even cause corruption, that's liek saying installing the incorrect driver for a graphics card on a PC could corrupt the file system, just no. So far I've flashed many many different MODEM types onto my phone to try to test this, in some caes the phone boots, in some cases it doesn't etc.. Not once has the phone failed to go into Odin flash mode, and if it can get to that, it can be restored. So based on research and some experimental evidence conducted to test your assertion, I'd have to say that my initial findings are that your assertion is probably incorrect.
Also I learn very quickly. My knowledge of the subject had increased dramatically from my first post to my second. I learned c++ in a day for example, and was posting similar newbie questions on programming forums to which I was later replying with a level of knowledge that wasn't consistent with my initial post. It's just me, sorry about that. And thanks for trying to help, but I got it myself.
NicSure said:
... I can assure you they are certainly not so for a newcomer. Too many things are vague, missing or not explained properly. In any case, I managed to get the stock firmware back on after trawling the internet for a .pit file, downloading the firmware, splitting it, taking the wipe versions with the pit and the bootloader and using Odin to fully flash the phone back to stock firmware, Finally. The tuts here are indeed a lot of help, but so so so disjointed.
Click to expand...
Click to collapse
Dear NicSure, I am in the same situation as yours, I was planning to "simply" (or maybe wrongly?) use Odin 3.09 and flash the Splitted files from here (http://forum.xda-developers.com/galaxy-ace/s5830i-develop/stock-rom-odin-flashable-firmware-t3002776).
But you mentioned that also the ".pit" file is needed. Could you guide me through the process you followed to have back a Stock from CM11 ROM?
Thank you in advance!
thePanz said:
I was planning to "simply" (or maybe wrongly?) use Odin 3.09 and flash the Splitted files from here (http://forum.xda-developers.com/galaxy-ace/s5830i-develop/stock-rom-odin-flashable-firmware-t3002776).
But you mentioned that also the ".pit" file is needed. Could you guide me through the process you followed to have back a Stock from CM11 ROM?
Thank you in advance!
Click to expand...
Click to collapse
Per your request/confirmation @ development section/twr topic i would resume troubleshooting .
What is your device variation (5830i/C/M/V/5839i ) ? Do you have any Nandroid back up left inside your SD card from your original stock firmware partitions ? Can you see your IMEI number , when you are dialing "*#06#" ? Your original stock CSC/PDA/MODEM you are coming from ? Your Region / Country / carrier you are staying with at the moment and please give me the Totoro Modem part you did flash to get into the CM11 ? and for addressing part of your primary queries , Odin 3.07 works very well with variation I mentioned above ( you could use 3.09 with no harm though , but not recommended ) . Pit file also must be relevant, otherwise you will hard brick your device in many cases I observed .
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
Ok so I acciedently deleted my efs file and can't get any connection or make any calls. I deleted it while in factory binary mode. My Imei says 00000000024 now. Please please help this is my daily phone. Spent hours doing research can't find a way. I have a g965u model att
You shouldnt make a new thread to ask the same thing you asked in a different thread.
Also someone already answered that question. In the other thread you made you mentioned that a repair shop can do it for you. I would suggest going that route to avoid any further issues.
Link to a reply on the same question below:
https://forum.xda-developers.com/showpost.php?p=77779892&postcount=5
scottusa2008 said:
You shouldnt make a new thread to ask the same thing you asked in a different thread.
Also someone already answered that question. In the other thread you made you mentioned that a repair shop can do it for you. I would suggest going that route to avoid any further issues.
Link to a reply on the same question below:
https://forum.xda-developers.com/showpost.php?p=77779892&postcount=5
Click to expand...
Click to collapse
While I figured since it's a different question than the original thread it would be OK but I guess I could have just changed the title And I know I can go do it in a shop but I'd rather learn how to do it myself and save money and learn some more at the same.
It's so frustrating because I see all these people on craigslist YouTube and all over the internet that restore imei so I knows it's possible but I can not find one tutorial I think because my firmware is so dang new
[email protected] said:
While I figured since it's a different question than the original thread it would be OK but I guess I could have just changed the title And I know I can go do it in a shop but I'd rather learn how to do it myself and save money and learn some more at the same.
It's so frustrating because I see all these people on craigslist YouTube and all over the internet that restore imei so I knows it's possible but I can not find one tutorial I think because my firmware is so dang new
Click to expand...
Click to collapse
Well it's not really a different question as much as it is a natural progression over the issue you posted on originally. Thread title is ok, unless the issue you were having was the missing efs and not where you couldn't find the arg8 firmware
For example if a person who had no idea what too do made a thread asking "my phone is acting up" and it was suggested to do a complete backup of the phone (and factory reset) the original poster would ask "how do I factory reset and backup my phone" in that thread rather then in a new one.
This way all information on the issue is kept in the same place, as opposed to several different places.
Now you keep reading those things and it may be possible because they have experience, tools or resources you don't. Places said they could unlock my phone and they did, but this is not something i could have done myself. I highly doubt having new firmware is the case here.. If there are special steps because of this being a Galaxy S9+ maybe another thing.
If it was that simple where a tutorial was all it took someone would have put it on the internet. If you cant find one then it just may mean this isn't something a tutorial can solve.
Personally I would suggest taking/sending your phone into a repair place and having them fix it. You may be at a point where this is beyond what your capable (whether by knowledge, tools, resources, skill, etc) of doing
Well I'm broke right now I will keep digging reaserching and trial and error until I find a way or get the money.
Try running these commands on adb make sure you got USB debugging enabled
adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2'adb reboot
Good Luck
JacobTB said:
Try running these commands on adb make sure you got USB debugging enabled
adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2'adb reboot
Good Luck
Click to expand...
Click to collapse
Will that work with locked boot loader? But I'll give it a try anyway when I get home I hope it works but I doubt its gonna be that easy on this phone because they haven't even got root yet
[email protected] said:
Will that work with locked boot loader? But I'll give it a try anyway when I get home I hope it works but I doubt its gonna be that easy on this phone because they haven't even got root yet
Click to expand...
Click to collapse
It should work on locked bootloader without route because it's through adb
JacobTB said:
It should work on locked bootloader without route because it's through adb
Click to expand...
Click to collapse
I pray this works im gonna try it now. Thank you
It says not found for either modem. Damn it ughhhh fml
Okay the last thing I recommend you do is go to https://updato.com/firmware-archive-select-model and download the firmware for your device then Odin flash with the phone efs clear option selected and flash the firmware. remember to backup your stuff as it will perform factory reset.
This will not trip Knox as it's official firmware and can be done without the need for root or unlocking the bootloader
JacobTB said:
Okay the last thing I recommend you do is go to https://updato.com/firmware-archive-select-model and download the firmware for your device then Odin flash with the phone efs clear option selected and flash the firmware. remember to backup your stuff as it will perform factory reset.
This will not trip Knox as it's official firmware and can be done without the need for root or unlocking the bootloader
Click to expand...
Click to collapse
Unfortunately I already did this actually how i lost the efs, i hit back up and i guess it never did. Then when i flashed the stock firmware it ware gone.
Anybody else? I wish i could figure this out I wana use my phone so bad.
I know I could do it with xposed framework but I need root and this phone is unrootable
[email protected] said:
Unfortunately I already did this actually how i lost the efs, i hit back up and i guess it never did. Then when i flashed the stock firmware it ware gone.
Anybody else? I wish i could figure this out I wana use my phone so bad.
I know I could do it with xposed framework but I need root and this phone is unrootable
Click to expand...
Click to collapse
What region are you in? And what model number is your phone?
JacobTB said:
What region are you in? And what model number is your phone?
Click to expand...
Click to collapse
G965USQU3ARG8 s9+
And I am in the United States.
Oh god I'm am a United Kingdom user and everything here exynos is easy to replace I would recommend a repair or replacement from Samsung themselves as long as you say you device broke during upgrade and your Knox isn't tripped you should be fine
Thats out of the question for me because i got it from a private seller and insurance is up. Hey btw when i typed in the code you gave me in adb it said unathorized. I think if i can get it to authorize adb can fix it. Any idea about that error. And i cant believe flashing back into factory and back into stock wont bring it back.
Perhaps it might work if you use adb. Make sure you go into the developer options on your phone you can do this by going to the build number in about phone in the settings and tapping it 5 times developer options will be a new menu on the settings page then go in and enable usb debugging. From there plug your phone into the computer open adb and type adb devices and grant permission on your phone when the prompt pops up then try and run the commands again
JacobTB said:
Perhaps it might work if you use adb. Make sure you go into the developer options on your phone you can do this by going to the build number in about phone in the settings and tapping it 5 times developer options will be a new menu on the settings page then go in and enable usb debugging. From there plug your phone into the computer open adb and type adb devices and grant permission on your phone when the prompt pops up then try and run the commands again
Click to expand...
Click to collapse
This never worked for me. Fml 2 weeks now with my s9 out of the picture. I know somebody knows a way help a man use his 900+ phone lmao I'm to broke right now to take it to a shop.
I don't know any other methods to fix this ?
[email protected] said:
Ok so I acciedently deleted my efs file and can't get any connection or make any calls. I deleted it while in factory binary mode. My Imei says 00000000024 now. Please please help this is my daily phone. Spent hours doing research can't find a way. I have a g965u model att
Click to expand...
Click to collapse
You deleted efs while in factory binary?
You typed in a dialer code to delete efs?
So now only samsung or a special repair shop can rewrite your imei.
It is gone and also other data which all has to be rewritten.