OMG! I'm not going into details on what I did, I'd just like to request the Stock ROM that came with it so I could restore my phone. It has android 4.1.2 and I just want to install it using the "Apply Update From sdcard." And if you must know, I edited the Build.prop file (The internet told me to.) And it messed up and wouldn't start up and got stuck in "Bootloop" so I tried factory reset and it didn't and I really need my phone because if I don't fix it I'll have to try to send it in to Huawei or T-Mobile or who ever. Plllllllz help.
Solution may be here soon.
No one has the stock rom on hand yet. We are working on building a custom recovery for the phone, so please be patient.
Hopefully we can have a working recovery by this weekend, then you will have a way to still access your phone.
What files did you mess up on your phone? If i know the files, I can get someone to upload the files and then you can push the files to your phone using adb. If you haven't yet, I would recommend unlocking your bootloader via the instructions here:
http://forum.xda-developers.com/showthread.php?t=2546455
By unlocking the bootloader, you will be eligible to test the custom recovery as soon as it is available. Also, list the foiles you messed up, so that we can possibly upload them for you.
It will be a while until someone can form a stock rom update.zip for you.
Also, you can view the progress that we are making on the custom recovery.
amamartin999 said:
OMG! I'm not going into details on what I did, I'd just like to request the Stock ROM that came with it so I could restore my phone. It has android 4.1.2 and I just want to install it using the "Apply Update From sdcard." And if you must know, I edited the Build.prop file (The internet told me to.) And it messed up and wouldn't start up and got stuck in "Bootloop" so I tried factory reset and it didn't and I really need my phone because if I don't fix it I'll have to try to send it in to Huawei or T-Mobile or who ever. Plllllllz help.
Click to expand...
Click to collapse
You don't want to go into details but you still want someone to help you? Hahahahaha!!!
Good luck with that plan!
CtrlAltDelIrl said:
You don't want to go into details but you still want someone to help you? Hahahahaha!!!!
Click to expand...
Click to collapse
Show some compassion - I'm sure most of the people here have messed up, and hit their heads against the wall for it.
Deeeno said:
Show some compassion - I'm sure most of the people here have messed up, and hit their heads against the wall for it.
Click to expand...
Click to collapse
Yes and in those cases they're usually eager to share all the details required, unlike the OP.
When the proper details are supplied it's easy to help, nobody likes to mindread here.
CtrlAltDelIrl said:
When the proper details are supplied it's easy to help, nobody likes to mindread here.
Click to expand...
Click to collapse
Probably doesn't know exactly what they did to mess up.. so doesn't know how to explain it.
Merely asked for the stock application to try and fix it themselves is what I gathered.
But Whatever
Explanation.
Was using Android tweaker 2 and accidentally hit the "On Screen Navigation Keys" and then when I went to turn it off it wouldn't switch. It stayed on. Updated the T weaker app, hoping for a fix but the option disappeared and I was stuck with them. Searching the internet I found a option that allowed to disable the soft keys in the Build.prop. But when I save it and restarted the phone was stuck at the T-Mobile screen.
Also I never figured out how to do ABD it tried for a long time but it didn't work. Since I got it in October, I need to know who to send it to be repaired, since I have a warranty (But I don't really want to send it away so that's why I asked.) So, there's and explanation. I'd tell you what I edited if I could find the website.
ADB
Okay, I got ADB working. But if I unlock Bootloader, does that that void my warranty?
And basically I need a default Build.Prop. Thats the only file I edited.
Return the phone since you are under warranty, you won't be without a phone
If you are under warranty with tmobile, you should be able to get a replacement if you are on their JUMP insurance, even if it was accidental.
I would recommend first going to your tmobile store and asking them to send you a replacement(and to waive the restock fee). They will send you one by mail in a few days, then all you have to do is send the old phone back to them in the prepaid shipping package(instructions are included).
I would recommend doing this instead of unlocking your bootloader and waiting for a recovery and custom rom to come out. My belief is that unlocking your bootloader does NOT directly void your warranty, unless the company can prove that the unlocking directly bricked your phone(which it doesn't). A thread with the legality of unlocking your bootloader is found here: http://forum.xda-developers.com/showthread.php?t=2250113
Again, I recommend just bringing in your phone and saying your phone just refuses to boot anymore since an update or something of that like. You won't have to wait long. Also, the phone is $63 on ebay, if you are uneasy about going to tmobile to return it.
build.prop for Android 4.1.1
default Prism 2 build.prop file for Android 4.1.1 attached below. Don't know if this will work with 4.1.2, so make a backup of your build.prop before replacing it!
Prism 2 said:
default Prism 2 build.prop file for Android 4.1.1 attached below. Don't know if this will work with 4.1.2, so make a backup of your build.prop before replacing it!
Click to expand...
Click to collapse
Dont do this, you will brake it even more, every version has specific build prop.
Okay, but no.
Not on insurance....
They didn't offer it at Walmart, that I know of. The real reason I got it was that I was sick of my unlocked Pantech Link (An AT&T on T-Mobile...)
And plus, I'm just broke right now -_-
Are you sure you have Android 4.1.2? I have the latest stock T-mobile rom (just tried updating today) and I'm "up to date" with 4.1.1
How do you have 4.1.2?
That's strange. Can any other users confirm that their Prism Ii has 4.1.2?
Well...
Well.. I may be mistaken. But I can't check =/
Almost certain you have 4.1.1
Doubt they would push an OTA just to upgrade from 4.1.1 to 4.1.2, but if someone can verify they have 4.1.2 i am open for correction.
I think pushing the new build.prop to your phone is worth the shot, and it would not effect your bootloader since it is locked, and you are already softbricked.
To push the build.prop to your phone, you have to rename the old one in adb, and then use the adb push command to push the file into the appropriate folder ( /system )in this case.
If you need help organizing the files or using the actual commands, let me know. Also, you want to place the build.prop file in the same folder you installed adb.
Also, to run adb, you have to open cmd and change your directory(the command is cd) to the folder you installed adb to, in order to use the adb command.
The adb command only runs when you are in that folder in the command prompt, because adb is not a systemwide command
streetdev22 said:
Doubt they would push an OTA just to upgrade from 4.1.1 to 4.1.2, but if someone can verify they have 4.1.2 i am open for correction.
I think pushing the new build.prop to your phone is worth the shot, and it would not effect your bootloader since it is locked, and you are already softbricked.
To push the build.prop to your phone, you have to rename the old one in adb, and then use the adb push command to push the file into the appropriate folder ( /system )in this case.
If you need help organizing the files or using the actual commands, let me know. Also, you want to place the build.prop file in the same folder you installed adb.
Also, to run adb, you have to open cmd and change your directory(the command is cd) to the folder you installed asb to, in order to use the adb command.
The adb command only runs when you are in that folder in the command prompt, because adb is not a systemwide command
Click to expand...
Click to collapse
Pushed the Build.Prop, but still does the same thing. Lost the old one though, because I forgot to rename it.
Try Factory Reset once more
You are stuck in a bootloop? Try factory resetting once more.
If that does not work, you may be our first live install recovery image tester, and you'd just have to wait until a custom ROM was released.
Reseted... Still stuck.
Omg. They must make these phones just to make us upset when they break.
Wait until I get the unlock code from Huawei, also some other things to try
It should be any minute now, and I will see if there are other fixes. For now, unlock your bootloader according to the guide.
We will need access to recovery anyway, through recovery, we will try wiping cache/dalvik cache if available, and that may be the fix you need.
Also: I think you may need to change the permissions on the build.prop you pushed!
You would have to change the permissions to 644 according to this thread: http://forum.xda-developers.com/showthread.php?t=2152850&page=2
To do this, we would still need to use adb.
Commands in adb:
adb shell
remount rw
chmod 644 /system/build.prop
Also, are you sure that the file actually pushed successfully?
Related
Its been done on the Incredible and Evo, now the Slide. This SHOULD BE IT. Here is their post with exact method. Adjust for the N1 and test on an unrooted phone. ASAP. This should be it!!!!!
QUOTED FORM EUGENE373 @ MT3GS FORUM:
Originally Posted by brokensanity
How-TO Root the Slide
First!! - Go to Settings > Application > Development and turn on USB Debugging. This should save you headaches.
NOW… Power Off the Slide
Download This Package > Slide Root.zip
kingofyo1's Video How-to > http://www.youtube.com/watch?v=sVjoKvy-YZg
Step 1.
Place the Contents of "Slide Root.zip" into your Android SDK Tools folder.
Step 2.
Open Command Prompt or Terminal and CD to the SDK/Tools Directory.
Step 3.
Power on the Slide into the bootloader by Holding Down ( Volume Down + Power Button )
Step 4.
Now run your loop file from the prompt (either type "loop" in windows or "./loop.sh" in a *nix like)
Step 5.
Once your loop is running in your prompt, select Recovery from the bootloader menu.
Step 6.
When recovery loads, you should Have an Offline Device. You can use ctrl+c to stop your script & see.
If this doesn't happen, Power Off and try again..
Step 7.
Un-plug your USB cable from the back of your phone & Plug it back in for it to Detect ADB Correctly!!! This is an important step. At this point you can adb devices to see if you can see your device and that it is in recovery mode.
Step 8.
Select Update.zip from the menu. (This will fail, but we already know that! Select it anyway).
Step 9.
adb push ota.zip /sdcard/update.zip (*nixlike users add a ./ in front of all terminal commands please.)
Step 11.
adb push slideroot.zip
Step 12.
This is Very important!! Have this Command ready in your prompt before applying update.zip again!!
adb push update.zip /sdcard
step 13.
Hit run update.zip, as soon as you see a Little Bar appear under the text push Enter to execute the command in your prompt (adb push update.zip /sdcard )
Step 14.
In successful, you should see Clockwork Recovery. If unsuccessful, repeat steps 12 & 13.
Step 15.
Now, go to the Partitions menu and Mount System
step 16.
Go back one level & select install any zip from sdcard. Select slideroot.zip & apply update from zip (This will finish the Root process).
Step 17.
Reboot your phone & wait for it to load completely. To confirm that your slide is connected as a device use the command adb devices. If this works, you will see it as a device. Your prompt will say something like:
$ ./adb devices
List of devices attached
HT05YUP12710 device
Step 18.
adb install Superuser.apk (If this looks like it works, but says it cannot locate directories, make sure you can find your device using adb devices… If things still don't work, my best advice is to start over)
Step 19.
After Superuser is installed try to use adb to shell to your device.
adb shell
you will get a $
Then type su
Superuser should pop-up asking if you give permission, do so.
Your $ should turn into a #. If so, you have root.
Congrats.
Special Thanks to:
Paul O'Brien:
Koushik K. Dutta:
&
The Guys using the Incredible OTA Spoofing Method
Why don't you test it out and let us know the results? ;-)
why do we care about the bootloader since both HTC and Google are ok with us unlocking it?
Im waitn for someone to try this out... hahaahah
b9nez said:
why do we care about the bootloader since both HTC and Google are ok with us unlocking it?
Click to expand...
Click to collapse
If people don't unlock the bootloader they get to keep their warranty
PhantomRampage said:
If people don't unlock the bootloader they get to keep their warranty
Click to expand...
Click to collapse
Most of the time, they'll replace our equipment. It's been done before, i'm witness to that.
I don't argue this would be a good idea but it's not THAT necessary. :\
Edit: only real upside i can see is getting rid of that annoying unlock icon but since i'm already unlocked there's no point.
This would be pretty good for people like me, who has an unrooted Nexus One
whorehay said:
This would be pretty good for people like me, who has an unrooted Nexus One
Click to expand...
Click to collapse
The key is that we need a DEV with an unlocked phone in hand. I can switch my purple-tinted screen out and get it over to a good one, but that could take a few weeks, anyone else have the tools ready?
I read that whole thread and there was no mention of bootloader at all. If someone can confirm it isn't touched I might be willing to give this a go with my new ATT N1.
If I somehow manage kill it, is there a way to recover a stock image without root?
Santoro said:
I read that whole thread and there was no mention of bootloader at all. If someone can confirm it isn't touched I might be willing to give this a go with my new ATT N1.
If I somehow manage kill it, is there a way to recover a stock image without root?
Click to expand...
Click to collapse
If it is messing with just the image then im 99% sure yeah you can.
I have a mytouch slide also and this method works. Were having problems getting a recovery to stick on the phone though. I have no idea if this works on n1. Id try but my bootloaders already unlocked.
Santoro said:
I read that whole thread and there was no mention of bootloader at all. If someone can confirm it isn't touched I might be willing to give this a go with my new ATT N1.
If I somehow manage kill it, is there a way to recover a stock image without root?
Click to expand...
Click to collapse
I can say that it wont hurt the phone. I tried a process similar to this before I had the details with one of the better known devs from XDA this weekend for a few hours. Even though we couldn't get the timing right, at the end of the day, I still had my original Rom, and it haven't even been hit with a recovery.
i have exchanged my N1 with an unlocked bootloader without any issues. and many other people have as well. if its a hardware issue they will ALWAYS honor warranty. if your phone is bricked by something you flashed they won't honor that
FishFan319 said:
I can say that it wont hurt the phone. I tried a process similar to this before I had the details with one of the better known devs from XDA this weekend for a few hours. Even though we couldn't get the timing right, at the end of the day, I still had my original Rom, and it haven't even been hit with a recovery.
Click to expand...
Click to collapse
So I know just enough to be dangerous. I need to understand a little more before I try this on my N1.
This slide_root.zip, are it's contents phone-specific? You said we should modify the process for the N1, are you saying that the contents of the file need modification? Or just the navigation around the recovery?
I am pretty leery until I understand what the slide_root file does and if it is compatible with my phone. Anyone know?
If I do it and it fails, does anyone have a link to how I would reinstall a stock image via USB?
edit: grammar
I developed a screen problem and had to pay to get it repaired because the bootloader was unlocked. Nothing to do with ROM or anything, a section accross the top of the screen went unresponsive to touch. So I know for a fact that they DON'T always honor warranty after unlock. I guess I must've gotten the a*hole operator/technician then for my call...
Jr33 said:
i have exchanged my N1 with an unlocked bootloader without any issues. and many other people have as well. if its a hardware issue they will ALWAYS honor warranty. if your phone is bricked by something you flashed they won't honor that
Click to expand...
Click to collapse
That really is a matter of interpretation by the tech you get at HTC. Based on the poster just above this, the warranty is not ALWAYS honored. Right?
Santoro said:
That really is a matter of interpretation by the tech you get at HTC. Based on the poster just above this, the warranty is not ALWAYS honored. Right?
Click to expand...
Click to collapse
right. I could not get mine repaired for the dusts under screen problem with unlocked bootloader.
I think most of them slipped through since they could swap in US
kaiser_tytnii said:
right. I could not get mine repaired for the dusts under screen problem with unlocked bootloader.
I think most of them slipped through since they could swap in US
Click to expand...
Click to collapse
I stupidly got mine etched. Had I thought about the fact that it would preclude me from getting cross-shipped warranty work, I'd have reconsidered.
I WISH I COULD TYPE IN ALL CAPS IN TITLES TOO...
Anyway....
I'm assuming the OP didnt intend for yet another thread to devolve into the warrantly debate.
bobtentpeg said:
I WISH I COULD TYPE IN ALL CAPS IN TITLES TOO...
Anyway....
I'm assuming the OP didnt intend for yet another thread to devolve into the warrantly debate.
Click to expand...
Click to collapse
yep, i agree. let's stop the warranty debate here.
i probably will find someone who has a unrooted phone to try it out
Hi there everyone, i am in need of assistance.
I have follwed the guide on here for downgrading my phone usin the ADB commands and all is good up until the actual downgrading stage. After a few attempts i had managed a temp root (i think) using command line.
" adb shell " brought back the # so i know i did that right, but when it comes to pushing the rom file to my sd card it comes back adb not found in which case i cannot reboot the bootloader if that doesnt work.
Is there something i am doing wrong or is the file im uusing just not compatible, "PC10IMG.zip"
If there is another way to downgrade after temp root with maybe a different rom file i would be very grateful if someone could help me.
Any questions you have to help me, just let me know
Thanks
Sent from my HTC Vision using XDA App
Im still very new at this but i'll thrown in my two cents here.
After you've gotten temporary root status '#' and you've set your version to 1.00.000.0 following the guide, your next step is it push the stock ROM used to downgrade into your sd card.
At this point make SURE you are not in the adb shell, (aka you dont see the #)
so make sure you exit first.
Another thing is to make sure the ROM you want to push, the "...._PC10IMG.zip" file is in the correct directory, same directory as your CMD.
Lastly the push process takes time so dont be impatient, unlike the other files you pushed before which were more or less instant, this one will take at least a minute and the CMD may look idle so really just have to wait.
when the results show, you can then proceed with reboot bootloader command.
hope it helps.
i got stuck after this point, i keep getting a cid error, which is a totally differnt issue from your above question.
Hi guys my girlfriend bought a LG Viper 4G LTE and she told me to root it to remove the sprint crap, so I was wondering if anyone has already done this and if yes, can they tell me how to s-off + root + custom recovery + and probably custom ROM.
If anyone can help, please I'll appreciate it. Since I searched here for that phone and is not even listed.
The phone is running android 4.0.4, is this ICS or Jelly bean?
I do not know how to get into fast boot boot loader cause I don't think it is POWER + VOL DOWN.
Thanks in advanced
Have a nice day
:what::what::what::what::what::what:
Sent from my Nexus 10 using Tapatalk HD
Im trying to root mine right now and can't seem to get it to work, I've tried Root_with_Restore_by_Bin4ry_v21 and LG-Viper-ICS-Root-tool with no luck. If i get it to run all the way though and reboot it still comes up without root and with no super user. I am starting to think I may have to find a way to downgrade it and root from there.....Did you ever have any luck?
Update:
Check out post 17 here
http://forums.androidcentral.com/lg-viper-4g-lte/253022-cannot-root-viper-ics.html
here is the link for LS840ZVI :https://docs.google.com/file/d/0BzPBX7oKPGLOcno0dFVNUXByMVE/edit
I've downgraded and rooted so far and its working, I may look for a rom before i upgrade again.
Confirmed above!
jared_schaefer said:
Im trying to root mine right now and can't seem to get it to work, I've tried Root_with_Restore_by_Bin4ry_v21 and LG-Viper-ICS-Root-tool with no luck. If i get it to run all the way though and reboot it still comes up without root and with no super user. I am starting to think I may have to find a way to downgrade it and root from there.....Did you ever have any luck?
Update:
Check out post 17 here
http://forums.androidcentral.com/lg-viper-4g-lte/253022-cannot-root-viper-ics.html
here is the link for LS840ZVI :https://docs.google.com/file/d/0BzPBX7oKPGLOcno0dFVNUXByMVE/edit
I've downgraded and rooted so far and its working, I may look for a rom before i upgrade again.
Click to expand...
Click to collapse
I can confirm that the above will work. I have a refurbished Viper from Sprint that I got because my 3G radio quit sending. It would receive great, but couldn't send any MMS or upload anything while on 3G. 4G was great, just no joy on 3G. Strangest thing. Anyway, got the phone replaced, and on the replacement was of course the dreaded unrooted ZVK. Gotta have my root back...
So I decided to try all this stuff out, and It worked.
To add a little further info, if you've got a relatively bare install of Windows, especially XP, you might need BOTH the VisualC++ Runtime Redistributables from 2010 (mentioned in the above thread) AND the one from 2008! If you don't have both, the LG FlashTool will not run. You can find them on Microsoft's site.
Once the flash tool has successfully downgraded your Viper, make sure you perform a factory reset, as indicated in the instructions for the FlashTool. Then use the "Activate" app to get your 3G/4G on. After that, set up your Google account under "Accounts and Sync" in "Settings".
I did the whole operation completely on a linux system, using a virtual machine running Windows XP for the FlashTool, then the bash script from here: http://forum.xda-developers.com/showpost.php?p=43530152&postcount=3253 with the v.31 rooting tool from the original post in that thread.
I had to edit the script in a very minor way, as was pointed out by its author, so it could find my adb command. I just placed the path to that command in the line that said:
Code:
for test_adb in "adb" "stuff/adb"
in the place of the first "adb", so I got:
Code:
for test_adb in "/home/user/android-sdk-linux/platform-tools/adb" "stuff/adb"
Make sure to replace "user" with your username, without the quotes.
Then I stuck the script in the same folder as the runme.bat file. After the script and root tool had done their work, my phone had rebooted a total of three times, and I had a perfectly functional Superuser app!
Huge thanks to LoveMyAndroid2010 in the post linked above. Great script - some love for linux!
Now to get RootKeeper and upgrade back to ZVK...
The aforementioned root method worked for me. Since I've rooted, I've compiled my findings into another thread. I haven't been able to unlock the bootloader yet, unfortunately.
how to upgrade LG Viper to Jelly bean or higher
After I root as per instructions, how can I upgrade the OS?
Please help. I'm a newbie and would appreciate any help you may offer. Haven't rooted any phone before.
Hi all,
I have been through douzens of threads and forums looking for a solution to this.
I followed some instructions to modify the build.prop file on my Huawei G535-L11 to disable Huawei theme manager in order to get Xsposed working fully (changed ro.config.hwtheme: 0). I did a backup of my original build.prop before hand, and my phone was rooted and unlocked but running the stock rom.
Unfortunately, it rebooted but won't go past the first 'EE' splash screen (just turns off again).
I can inconsistently get in to both fastboot and Android recovery, so I have been trying to use adb to push the original build.prop to /system/ on the phone.
However, this fails as /system/ is apparently RO. I have now discovered that I can't get SU permissions despite my phone being rooted.
If I try:
adb shell
$ su
nothing happens and it goes back to a $ prompt.
If I try:
adb root
I get the message (paraphrased):
adb cannot run as root in production builds.
So I can't push or do any adb method of restoring the build.prop file?! I don't understand why it is acting as if it is not rooted. I had Link2sd, Gravity Box, No Frills Cpu Controller all set up and working before, so I'm fairly sure I did truly have root.
I have also tried flashing a TWRP recovery, which apparently is successful, but when I go in to recovery it is still the Android Recovery.
Does anyone have any ideas what I could do to get my phone working again please?! This is my last gasp before the phone gets filed under 'B' in the cylindrical cabinet in the corner of the room!
Any assistance greatly appreciated!
Some systems are very finicky with modded build.props, or you didn't set the file's permissions correctly. I'm afraid without being able to boot or a working custom recovery, then adb won't work, much less root enabled adb functions. adb works in some stock recoveries, but only for sideloading files directly signed by the manufacturer. In regards to TWRP, is the bootloader unlocked? If not, that would explain why it didn't work. Other than that, I don't believe you'll have any other options besides reloading the stock firmware.
Hi,
Thanks for the reply. Yes, the bootloader was / is unlocked.
Unfortunately, there isn't any stock firmware available anywhere. Unless someone out there has a backed up rom image from the EE Kestrel?
This is supposed to be a working TWRP for your device http://forum.xda-developers.com/showpost.php?p=58522448&postcount=117 - if you get it loaded, there might be a chance to push the working build.prop back to the phone. I would read that thread too and see if there isn't more useful info there or another member with your phone that could make a backup for you. Good luck.
Thanks.
Unfortunately, I'm pretty sure that is the TWRP I've tried. I'll double check when I'm on my PC.
I might try requesting a rom image on that thread, but the community for this phone seems to be pretty dead :/
I've just gone and ordered a new phone anyway, but it seems like a waste of a good phone just for the sake of one line of bad code!
Thanks for your help. I'll post again if I have any success.
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.