http://forum.xda-developers.com/showpost.php?p=7975002&postcount=4
A few days ago I flashed to JPC, but in my opinion it has way to much bugs so I flashed to JM7. I followed the guide to recover the orginal product code and, for as far as I know, it worked succesfully. But... After that I installed some applications and flashed the the voodoo lagfix to my device. I also tried to flash the OC-kernel but that didn't work, probably because the voodoo lagfix uses zImage too, so my phone didn't boot anymore. I went to download mode and flashed JM7 again. After that I flashed the voodoo lagfix to my phone and then I wiped the data and cache using the recovery mode. When I booted up my phone, the apps I installed earlier(eBuddy, Root Explorer) were still installed on the phone. I thaught it would be no problem, but when I tried to install some other applications from the market they didn't download. Then I tried to connect my phone to my computer to check the product code in Kies, but my computer didn't recognize my device, neither did Kies. I flashed to JM6, hoping that would fix the problem, but after following the same steps as I did after I flashing to JM7(applying voodoo,wiping data) and booted my phone, the applications were still installed and my phone was still not recognized by my computer! So now I can't connect my phone to my computer and I can't wipe the data and cache, although it seems to work when I'm in recovery mode. Can somebody please help me? I really don't know what to do now..
Thanks in advance,
Jasper
Do a factory reset in Settings > Privacy.
BaalBehrit said:
Do a factory reset in Settings > Privacy.
Click to expand...
Click to collapse
Doing right now, I'll post the results in a moment.
[Update]
The applications have been removed, but my computer does still not recognize my phone. Any advice?
[Update]
Flashing to JM7 at the moment, maybe it'll work now.
[Update]
I can connect my phone to my computer now. Thanks
Bump!
I just updated my post saying everything was working fine, but right after I flashed the Voodoo lagfix to my device the same problems occured again. Almost 100% sure Voodoo is causing them! Anyone else experiencing these symptoms?
Now I'm 100% sure. I connected my phone to my computer, turned my phone of and rebooted into download mode, flashed Voodoo onto it, rebooted and tried to connect again. Didn't work
you should join #project-voodoo on freenode ( IRC even on webchat.freenode.net )
as the developer says:
<curio_> forum is really innefficient for beta debugging kind of stuff
Ok, let's be clear.
Voodoo lagfix can't do harm to your phone.
Beta 1 meant to be a private beta, beta 2 will deal better with some stupid scenarios when you flash something and then something else etc..
Voodoo causing problems connecting to computer and wiping data < WTF is this topic title
I removed beta1 from the download site.
very misleading title , im sure you could have picked some nicer words for it considering supercurio hasnt released anything yet and you used a private beta file which is private for a reason, its still being tested.
I do have to say that I've had some issues with my computer connecting via USB. It only works through Kies- ADB gives me a device not found whenever I try to use it (Yes Kies is closed =P and it's in debug mode). I also have been unable to mount drives for mass transfer.
I had chalked this all up to running a Captivate with a I9000 kernel though- and it still might be, just figured I'd chime in since it sounds like someone has a similar problem- but what can you expect? It's beta 1 Just something to look out for curio in case it ISN'T just because of my unholy amalgamation of firmware pieces
No wiping of my data though =P
hmmm works fine here.
Although b4 doing all these I did do a full format of internal storage and factory reset. I did the hard reset through the service mode codes as well.
Everything's working smoothly and I do have the voodoo fix as well
Voodoo is in private beta!! You should not mention it on the forum I think, especially when discussing issues...someone should remove this thread asap! Issues with it should be discussed on irc only as per developer request (and better feedback also)! ...you should also apologize to supercurio who is working very hard for us all...
Sent from my GT-I9000 using XDA App
Forum Fail.
could you clarify the intention of your thread? this is a private beta, by downloading and installing it you are implicitly agreeing to be a tester, and report issues on the irc. This would cause unnecessary noise. mod should remove this thread.
japperrrr said:
Bump!
I just updated my post saying everything was working fine, but right after I flashed the Voodoo lagfix to my device the same problems occured again. Almost 100% sure Voodoo is causing them! Anyone else experiencing these symptoms?
Now I'm 100% sure. I connected my phone to my computer, turned my phone of and rebooted into download mode, flashed Voodoo onto it, rebooted and tried to connect again. Didn't work
Click to expand...
Click to collapse
Sent from my GT-I9000 using XDA App
Well, if it cause you problem, then don't install. This is BETA release!!! It is absolutely ludricrous to give such a sweeping statement that xxx cause this or yyy cause that. There is a reason the dev has not released it here.
Just because it worked for others, and you can't get what you want, and just start ranting. This won't do, OP! Go figure....
100% agree with others that this topic is totally out of line. It's a private BETA - report the issues to the dev in the appropriate place.
Zilch25 said:
I do have to say that I've had some issues with my computer connecting via USB. It only works through Kies- ADB gives me a device not found whenever I try to use it (Yes Kies is closed =P and it's in debug mode). I also have been unable to mount drives for mass transfer.
Click to expand...
Click to collapse
I have had issues connecting my SGS to my Mac via USB since day one out of the box. The drivers on the phone are flakey, in my opinion.
distortedloop said:
I have had issues connecting my SGS to my Mac via USB since day one out of the box. The drivers on the phone are flakey, in my opinion.
Click to expand...
Click to collapse
Yeah that's also true, though it never manifested before this point. I never bothered to report this to supercurio because I'm not even using the hardware that's compatible with the kernel in the first place It's working fantastically anyway, I just figured I'd throw my 2 cents into the hat that it's worth keeping an eye out for just in case it *isn't* related to my cross pollination of firmwares.
Keep up the fantastic work supercurio I've nothing but good things to say about the project and the performance on my phone!
OP: You might want to change the thread title to something a little less scary =P It kind of paints the project in a negative light, and most people won't read through the thread to see what's really going on.
delete thread.
The people who are blaming me for starting a topic to report a bug in the Voodoo lagfix should read my startpost. I was experiencing problems with recovery mode and connecting my phone to my computer, and could not find another topic about it. That's why I started this topic, not to report bugs in Voodoo. After I found out Voodoo was causing it, I changed the topic title to possibly warn other people who're using of planning to use it.
japperrrr said:
The people who are blaming me for starting a topic to report a bug in the Voodoo lagfix should read my startpost. I was experiencing problems with recovery mode and connecting my phone to my computer, and could not find another topic about it. That's why I started this topic, not to report bugs in Voodoo. After I found out Voodoo was causing it, I changed the topic title to possibly warn other people who're using of planning to use it.
Click to expand...
Click to collapse
Wow, you sounded so noble. :speechless:
trash it!/change title/ erase post.
First rule of closed beta: you dont talk about closed beta.
Second rule of closed beta: you dont talk about closed beta.
Third rule of closed beta: you dont talk about closed beta.
xan said:
trash it!/change title/ erase post.
First rule of closed beta: you dont talk about closed beta.
Second rule of closed beta: you dont talk about closed beta.
Third rule of closed beta: you dont talk about closed beta.
Click to expand...
Click to collapse
Didn't know it was a closed beta since I downloaded it from another forum where no one said it was.. Sorry?
Related
Hello
I just switched from the Evo to the Epic and love it so far. My ? is I can not for the life of me root the epic. I downloaded everything it says and still nada. If there is someone on these forums that can walk me through because it may have to do something with my computer I dont know but it is just so frustrating. I had the Omnia at one time with Verizon and I learned how to root with that but I just need someone to help me I have read all the post on the topic still no luck its just so frustrating
Thanks
Jeff
Well 1st question what kind of os do you have on your computor?
2nd did you download one clock root and recovery?
3rd did you turn your phone onto debugging mode?
Sent from my SPH-D700 using XDA App
Don't forget the samsung drivers need to be installed on your pc..
sent from epic 4g
1st you need the samsung galaxy s drivers
2nd download the one click root and recovery FINAL with clockwork mod 2.5 or something
Then plug your phone in with usb debugging on, let it insall whatever on your computer, and then run the run.bat or whatever file in the one click recovery folder and it'll root it right in front of your eyes
Sent from my SPH-D700 using XDA App
hey
Hey
I keep getting an error come up saying I do not have privelleges and I did download everything that was needed and it seems like it will only let me download anything only from the market maybe I need to switch to allow 3 rd party applications or something alont that lines and thanks for the fast responses Ill figure it out and my operation system is Windows Vista eternity if that means anything diff than normal windwos vista 2209 64 x with a quad core proc
Intle R Core Quad cpu Q9300 thats given me no problems in the past I rooted the samsung omnia with this ok its prob just one stupid thing im doing wrong
Please post questions in Q&A section. Everyone please remember to click the "Report Post" button on the original post to have immediate action taken by the moderators. Also do not post in the thread itself telling the user that he made a mistake or broke a rule as it doesn't contribute to the thread and is unnecessary.
http://forum.xda-developers.com/showthread.php?t=803682
try this. it has just worked on a droid and the intercept. it is a pretty informed thread, no guarantee's
Hey everyone that responded thanks for all your help will let yall know when I get it or not but thanks a bunch
Z4Root from Android Market will work too.
Electrofreak said:
Z4Root from Android Market will work too.
Click to expand...
Click to collapse
I thought they pulled z4root from the market?
Welcome!!
As it has been stated before, you'll need those drivers.
I've rooted 2 epics, the first one was done slowly and worked fine.
2nd one. I thought I got everything, but rushed it, and kept getting errors.
Had to re-read instructions,.. Make sure you follow everything, I remember I had to mount the SD card. (or was that flashing recovery...)
steps might have changed as this was so long ago.. I remember that kept getting me stuck.
Previously I had installed on my phone (I believe, but could be mistaken) a Twilight Kernel and Hurricane v1.6 Rom. Well, I had nothing but problems with the rom, and put up with them for some time, just because I didn't have time to go through and find a rom I liked and flash it. I decided to do just that yesterday.
Apparently my mind broke and I did something wrong (probably numerous things). I had first attempted to put the shiney new CWM9 with Shadow Kernel on, rather, I made the mistake of trying to just put the Shadow Kernel on after having done a full (triple) wipe on my phone. I got the boot loop for the kernel since there was no rom (duh) loaded. Okay, no problem, I'll toss a rom on the SD and boot into CW3 and flash it? Yeah, not so much. I got a short "Samsung" logo boot loop and could not get into CW3 after that.
So, I Odin'd it back to EL30, thinking I'll just start from fresh, right?
Wrong.
Next in the series of mistakes I made, I forgot that I had already downloaded and installed the Samsung drivers (don't ask, my brain was apparently on leave yesterday) and attempted to re-install them. They did not like this and would not progress and I had to End Process the install from Task Manager. I then uninstalled the drivers completely fearing that I may have corrupted them by trying to re-install and then EP'ing them.
I then re-installed them, or so I thought. Plug phone in and start again with One Click Root. Fail. The script couldn't find my device.
Hours of searching and trying different things later, script still couldn't find my device, though I now have both the phone recognizing there is a USB connection, and the computer has stopped yelling at me that there are no drivers (I believe it finally gave up and installed the Windows drivers for it). But still can't get it rooted or do anything but stock stuff.
So..
1:Samsung drivers won't install, running Windows 7-64 Ultimate; error at end of install just states: "The MMS InstallWizard was not successfully installed SAMSUNG USB Driver for Mobile Phones v1.3.450.0."
2hone previously recognized USB Debug mode, but no longer. Will only Recognize standard USB connection, and with the connection made to PC, the script will not recognize the device.
3:adb for all intensive purposes does not appear to be loading..per the message from the script "Root was not obtained after 60 seconds. Make sure the phone is connected and that adb is working. If adb shell isn't root, reboot the phone and try the script again." I've rebooted numerous times, but I'm pretty certain that since it's not going into Debug, it's just not being recognized.
I have even tried Gingerbreak with no luck, just continuously sits on the rooting screen, but never proceeds (upwards 45 minutes I let it go).
Please please please please help me fix all the mistakes I did and get this thing working again and get the damned drivers installed proper.
(Baseband-S: D700.0.55.EL30, Kernel version 2.6.35.7, Build number: Gingerbread.EL30)
Note* I am happy with any root/kernel/rom at this point, I don't care, I just want the damned thing rooted again.
And of course after I finally cave and post for help, I find the thread where it clearly states OneClick Root no longer works for Gingerbread...so we'll add that into the mistakes I made...
Question still stands, how do I get this rooted again?
Qbking77 youtube him...
Or I could do it for you remotely via teamviewer... either way
Sent from my SPH-D700 using xda premium
AtrophiedAnnie said:
And of course after I finally cave and post for help, I find the thread where it clearly states OneClick Root no longer works for Gingerbread...so we'll add that into the mistakes I made...
Question still stands, how do I get this rooted again?
Click to expand...
Click to collapse
If you are up and running EL30 just Google How to Root Samsung Epic on EL30 and a qbking77 youtube video will pop up and all the links are there as well for the files you need. If you are not up and running then you need to go into the Roll Up sticky thread in Development and click on How to Restore a semi-bricked Samsung Epic....all links are there for that including 64bit drivers.
Sent from my SPH-D700 using xda premium
Found it all, getting it working now. Thanks all. We'll chalk this up to ...noobi-ness....(ignoring that I've been rooted and doing this for a year now... >.> )
AtrophiedAnnie said:
Found it all, getting it working now. Thanks all. We'll chalk this up to ...noobi-ness....(ignoring that I've been rooted and doing this for a year now... >.> )
Click to expand...
Click to collapse
Sounds more like serious root rust to me. Gotta keep up...lol. Samsung tries to make it harder to root...that works for 5 minutes around here...LOL.
Sent from my SPH-D700 using xda premium
IT'S DONE!!! Again thank you both so much1
I recently picked up a D851 (TMobile). I rooted it, but did not replace the ROM or install a custom bootloader.
Last weekend, the phone started randomly rebooting. Watching logcat via adb showed me several random apps throwing sig11s, after which the phone would give up and reboot. Cycle repeats.
This looks like a hardware issue, as the apps that crash change on each boot cycle.
I arranged with TMobile to swap the device, but they cautioned me that the phone must be returned to an unrooted state.
I've had a hell of a time with it from here. My first try was to install the LG drivers and the PC Suite under a Windows VM, as I do not run Windows at home. Enabling USB passthrough for the phone to the VM let Windows see the phone, but the LG drivers would invariably fail with 'Device cannot start. Code 10.'. Likewise, the PC Suite couldn't find the phone.
Next step was to throw together some spare hw and install Windows 7 on that (a desparate move, to be certain. ). The LG drivers can now recognize the phone, so that's a definite plus. The LG PC Suite, though, claimed that my phone could not be upgraded. Wonderful.
Next step was to try this tutorial: http://www.androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html . I was able to get further with this method, but as it begins to flash SYSTEM, it pauses, and then dies with 'We can't communicate with Phone'. End result - I now have a soft bricked phone. On the phone, I see the port - COM41 - appear, and the usb animation starts to spin ... and after a few seconds, stops. It's at this point that Flashtool throws the Can't Connect error.
I next tried following this tutorial: http://forum.xda-developers.com/showthread.php?t=2785089 to flash a KDZ. The newer LG Flash tool used here can't create a connection to my phone for flashing.
I've run into a wall here. Any ideas on where to go next? I need to reset this phone back to a working stock state so that I can send it back.
http://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/
Use this and follow video carefully. Has worked many times. Use all his links not what you have downloaded.
NOTE 4
BACARDILIMON said:
http://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/
Use this and follow video carefully. Has worked many times. Use all his links not what you have downloaded.
NOTE 4
Click to expand...
Click to collapse
Also - as silly as it sounds, make certain you're using the USB cable that came with the phone. This has solved problems for a lot of people when trying to revert to stock.
etawful said:
Also - as silly as it sounds, make certain you're using the USB cable that came with the phone. This has solved problems for a lot of people when trying to revert to stock.
Click to expand...
Click to collapse
I wasn't initially, but I did switch to it last night. Still no go.
I suspect it's either the phone itself (see above: re suspected hw failure), or the PC in question (nVidia chipset on this old motherboard, and I've had more than a few problems with adb talking to phones on nVidia motherboards). I'm going to try Bacardilimon's suggestion tonight, on a PC that has *nothing* nVidia-related in it, before I throw in the towel. As it is, the failing phone needs to be back to TMO by the middle of next week, so I'm all but out of time to resolve this.
Drake Maijstral said:
I recently picked up a D851 (TMobile). I rooted it, but did not replace the ROM or install a custom bootloader.
Last weekend, the phone started randomly rebooting. Watching logcat via adb showed me several random apps throwing sig11s, after which the phone would give up and reboot. Cycle repeats.
This looks like a hardware issue, as the apps that crash change on each boot cycle.
I arranged with TMobile to swap the device, but they cautioned me that the phone must be returned to an unrooted state.
I've had a hell of a time with it from here. My first try was to install the LG drivers and the PC Suite under a Windows VM, as I do not run Windows at home. Enabling USB passthrough for the phone to the VM let Windows see the phone, but the LG drivers would invariably fail with 'Device cannot start. Code 10.'. Likewise, the PC Suite couldn't find the phone.
Next step was to throw together some spare hw and install Windows 7 on that (a desparate move, to be certain. ). The LG drivers can now recognize the phone, so that's a definite plus. The LG PC Suite, though, claimed that my phone could not be upgraded. Wonderful.
Next step was to try this tutorial: http://www.androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html . I was able to get further with this method, but as it begins to flash SYSTEM, it pauses, and then dies with 'We can't communicate with Phone'. End result - I now have a soft bricked phone. On the phone, I see the port - COM41 - appear, and the usb animation starts to spin ... and after a few seconds, stops. It's at this point that Flashtool throws the Can't Connect error.
I next tried following this tutorial: http://forum.xda-developers.com/showthread.php?t=2785089 to flash a KDZ. The newer LG Flash tool used here can't create a connection to my phone for flashing.
I've run into a wall here. Any ideas on where to go next? I need to reset this phone back to a working stock state so that I can send it back.
Click to expand...
Click to collapse
There is a link in the general thread on how to return to stock including a method using twrp. It's a sticky thread at the top I've never done the twrp method myself but it can more than likely be done without a computer. Twrp can be installed via Playstore if you don't already have it
BACARDILIMON said:
httx://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/
Use this and follow video carefully. Has worked many times. Use all his links not what you have downloaded.
NOTE 4
Click to expand...
Click to collapse
Holy hell. That site's links are absolutely infuriating. Anyone who puts each and every download link for software referenced by a howto behind separate timed appearance links that you have to ALSO enter an annoying captcha to enable should be shot out of a cannon - or, at the very least, have their howto ignored by the rest of the world.
Suffice it to say, the quality of that page doesn't give me much confidence that this will work any better than what I've tried already. Since I've already wasted a crapload of time on this project, and more on following those damned links, I'll give it a try tonight, but I'm not going to hold my breath.
Is the author of that page an XDA member? If so, please let me know who he is, so I can berate him personally. Thanks.
Toneman07 said:
There is a link in the general thread on how to return to stock including a method using twrp. It's a sticky thread at the top I've never done the twrp method myself but it can more than likely be done without a computer. Twrp can be installed via Playstore if you don't already have it
Click to expand...
Click to collapse
I'd consider doing that, except as I mentioned, the G3 in question disconnected during a run of Flashtool, rendering it without a working OS to boot to. The phone now boots straight to download mode. The good news is, it's now officially unrooted. The bad news is, it's also officially bricked until I can get an OS flash to work.
Drake Maijstral said:
Holy hell. That site's links are absolutely infuriating. Anyone who puts each and every download link for software referenced by a howto behind separate timed appearance links that you have to ALSO enter an annoying captcha to enable should be shot out of a cannon - or, at the very least, have their howto ignored by the rest of the world.
Suffice it to say, the quality of that page doesn't give me much confidence that this will work any better than what I've tried already. Since I've already wasted a crapload of time on this project, and more on following those damned links, I'll give it a try tonight, but I'm not going to hold my breath.
Is the author of that page an XDA member? If so, please let me know who he is, so I can berate him personally. Thanks.
Click to expand...
Click to collapse
OK I gonna keep it real with you. You can either enter the captcha and fix the issue or throw the phone away. Yes he is a member and for every phone that is out their he has its own page doing this for us. If you can't fix your phone with his method then it not the method but you. I have used this for many bricks. It works and it works great. Sorry if he making you do a little typing but like I said u can use his method or keep trying the other methods. Good luck
NOTE 4
BACARDILIMON said:
OK I gonna keep it real with you. You can either enter the captcha and fix the issue or throw the phone away. Yes he is a member and for every phone that is out their he has its own page doing this for us. If you can't fix your phone with his method then it not the method but you. I have used this for many bricks. It works and it works great. Sorry if he making you do a little typing but like I said u can use his method or keep trying the other methods. Good luck
NOTE 4
Click to expand...
Click to collapse
After going through the painful process of clicking his links, I found that everything I downloaded is the same thing I already had, except for Flashtool - lgg3root's is actually older. Even the TMO firmware for my phone and the dll are both exactly the same, and I checked by running md5sum on them.
But hey, it must be me. There's clearly no other technology-related cause for this issue. I obviously don't know how to follow a howto, right?
Thanks for 'keeping it real'.
Drake Maijstral said:
After going through the painful process of clicking his links, I found that everything I downloaded is the same thing I already had, except for Flashtool - lgg3root's is actually older. Even the TMO firmware for my phone and the dll are both exactly the same, and I checked by running md5sum on them.
But hey, it must be me. There's clearly no other technology-related cause for this issue. I obviously don't know how to follow a howto, right?
Thanks for 'keeping it real'.
Click to expand...
Click to collapse
See we agree.
NOTE 4
BACARDILIMON said:
See we agree.
NOTE 4
Click to expand...
Click to collapse
Not likely.
In any case, it failed again. The video he did gave me the exact same steps I followed elsewhere, and unsurprisingly, it failed with 'We can't communicate with Phone', after beginning the flash process. There is something else wrong here, though I'm not certain if the failing phone is at fault or the PC in question is causing the issue. To be crystal clear, the flash process starts, and then, at a random point during the flash, it completely stops, and Flashtool eventually gives up and throws the aforementioned error.
Any other ideas? If not, I'm going to have to try another PC to rule that out as the culprit. Sigh.
Mine gave the same error as well as couldn't communicate with server but the flash process continued running and the phone rebooted took about 3 minutes u learned not to touch any of the popups on the screen during flash and sorry I missed the part about no OS I thought you were booting to recovery... Driving while reading not the best idea
Toneman07 said:
Mine gave the same error as well as couldn't communicate with server but the flash process continued running and the phone rebooted took about 3 minutes u learned not to touch any of the popups on the screen during flash and sorry I missed the part about no OS I thought you were booting to recovery... Driving while reading not the best idea
Click to expand...
Click to collapse
Nope, the phone is definitely not doing anything - the usb animation on the G3 completely stops before Flashtool throws the error.
And damnit, quit reading while driving. You can do that later.
Moved the hdd Windows is installed on to another PC with a different chipset. After it updated drivers, I tried again. Flash proceeded partway, then died. Reset phone, Flashtool reststarted flash from scratch, flash died at 15%.
15% is interesting. While I've seen the flash die at various points, 15% is the one that was most often repeated. This tells me the failure follows the phone, not the PC - which makes sense, as the phone has a suspected RAM failure.
At this point, it appears that flashing this phone is impossible due to faulty hw. Hopefully TMO (and eventually, LG) will accept the faulty phone back with no OS, because there's no way an OS is being written to this device ever again.
Thank you for answering
yanowman said:
Thank you for answering
Click to expand...
Click to collapse
No problem. There's nothing I hate more than stumbling across a thread where the OP has the same problem I have, only to find it was never updated with the solution.
Good luck man let us know what tmobile says
I've done many dumb things to this phone but I've finally found something I have not been able to recover from. Let's start with the list of things you guys will have me try that I've already done.
- FlashAll to the latest as well as the "Return to Stock" thread here on XDA
- Lenovo's Recovery Tool (I thought someone on XDA might be wrong about something and went with the Mfg's software, sorry I doubted you guys.)
I'm using linux so I convert your Flash bat to an sh but I've never had issues doing so before. I've rooted this and three other phones and I'd like to think I know what I'm doing I've spent about two weeks on here and other Android forums but this time I need to actually ask for your help.
Now on to my issue.
I installed Lineage OS using their lovely guide and everything was great until I found out my WiFi isn't working. Well can't have that, return to stock! Oh my WiFi is still dead. Wait now I can't even enable dev options because I cannot get past the initial setup without WiFI. OK full reset wipe and restore. Nope nothing doing.
It shows MAC unavailable in the initial setup. adb shell over via recovery shows no wlan0 then I tried TWRP and also OrangeFox because I saw a similar fix with it. I try ip link show but ip isn't there tried to su but it's not going. I think I have eveything mounted right but I'm more Arch than Android :\
And in 5 seconds someone is going to link a thread on here I couldn't find in the search with a easy 3 step procedure. But just in case that doesn't happen feel free to ask for any logs.
I'm a dumb. Be sure you do the Pre-install instructions as these are what fixed my issues.
Hi, is your phone ATT version? Thanks.
Didn't know where to post this exactly, to be honest. This will be a long post
I was flashing AOSP roms in the phone. Tried to go back to One UI for the VoLTE thing
In one of the AOSP roms I couldn't install it in Lineage Recovery (older version of the rom thing). I saw i one post that doing an ADB Sideload in TWRP could solve the flashing problem. Did that. No issues
Wanted to test another AOSP rom but didn't boot (bootloop), so then I tried to go back to One UI. Don't remember if I did a format data in that moment.
After installing the rom and reboot to system, the phone doesn't even show the splash screen.
But tried to go to download mode and it went there, so the phone is still alive
Tried also going to recovery and it boots there (just to recovery and download mode)
I tried everything I could:
Flashed another custom ROM without success
Flashed other AOSP roms again
Changed the recovery (Lineage, TWRP and Stock tested)
Flashed the stock firmware through Odin several times
Tried to do a re-partition in Odin
Did several factory resets
Nothing seems to work. The weird thing is that, with any rom that I try to install, it tells that is installed, but when I go to the file manager in TWRP, it doesn't install anything. The free space before the installation is the same as after it. I don't know what else I can do. I just have the hope because the phone starts in BL and recovery
Anyone have any idea of what can I do to solve this? Or if there is a way to install the OS outside Odin or recovery (or ADB)
Tried with fastboot (Lineage Recovery) with several commands, and I think I found the issue. The system partition got corrupted. Need to know how to repair it (tried already with the repair option in TWRP)
Any help with this?
https://forum.xda-developers.com/t/...sh-stock-firmware-in-samsung-devices.4452839/
Read it carefully ( retrieve the original PIT file part)
Let me test it and will give feedback
lngl said:
https://forum.xda-developers.com/t/...sh-stock-firmware-in-samsung-devices.4452839/
Read it carefully ( retrieve the original PIT file part)
Click to expand...
Click to collapse
Didn't work out. Same issue
It's so stressful because it boots to the other things, but not to the system
Good afternoon faithful and unfaithful
Unfaithful Redspikejr
The barbarian from Pakonan has no idea about this but in your case he would do the following since I have had your problems and it was resolved positively.
I'm going to try to help you, I don't know English and I use a translator, I hope it's good to understand each other. Luck
First option
1 I want you to put through odin in AP twrp-3.6.0_9-2-d2s_official_jan22.tar unchecking auto reboot
2 in twrp delete data and say YES restart in twrp again and try to install PixelExperience_d2s-12.1-20220522-1749-OFFICIAL. I understand you will have it on the SD, if not, put the ROM on a USB key and try to install it in TWRP.
If you manage to install it, then install magisk apk and restart the system.
3 once started install magisk apk and ready.
Second option
1 I want you to put through odin in AP twrp-3.6.0_9-2-d2s_official_jan22.tar unchecking auto reboot
2 in twrp delete data and say YES reboot in twrp again and install the Recovery lineage.img and reboot in Recovery lineage and Factory reset & reset system partitions
3 Install the PixelExperience_d2s-12.1-20220522-1749-OFFICIAL. I understand you will have it on the SD, if not, put the ROM on a USB key and install from there. turn off the phone and
4 in download mode odin AP twrp-3.6.0_9-2-d2s_official_jan22.tar unchecking auto reboot reboot into TWRP
5 Install Magisk apk and reboot system.
once started install magisk apk and ready.
remember to have the cable plugged in to enter TWRP and download while you are following the steps. Good luck, you will say.
Salu2 of your most faithful infidel Pako
To update the situation
The battery of the phone in inflated like a balloon. I don't know for sure if that was caused by something physical, but will update when have some news
i still have the same problem and still hunger for a solution because i just bought it .. Been running quite a few firmwares now. and bootloaders and kernels and recoverys so far... but whats funny is in pixel recovery it said i had a "d2x" model which is SM-N976 model with 5G... But every elsewhere it says d2s which is note10+. Odin also says SM-N975F model... But anyways... I really really hope someone finds a solution. Because im stuck as hell...
I also made a thread my self
Partly bricked... SM-N975F
Hey guys.. Ive been a visitor in XDA forums for quite a while... And i been running root and custom FW with more or less every samsung from S2 and up... But i just got my self a note10+ (atleast thats what ive been told) and i wanted to root it...
forum.xda-developers.com
And i think its VBMETA problem. BUT i dont have any experience on that term...
Crossing fingers still...
I might have found a solution
Holy Hell, Im am so glad im not the only one that this is happened to. I will be more happy when we find a solution. I have put myself (device) in some questionable states but this has been a first and strange one for me . Its like being so close to booting into system then nothing.
AmercianPM said:
Holy Hell, Im am so glad im not the only one that this is happened to. I will be more happy when we find a solution. I have put myself (device) in some questionable states but this has been a first and strange one for me . Its like being so close to booting into system then nothing.
Click to expand...
Click to collapse
Android Verified Boot 2.0
I found this link this morning. Im sure this is the culprit.
I experienced today something like you. It did not let me flash even stock firmware. But I succeeded to get out. I flased via ODIN BL slot from Dr.Ketan and in AP slot TWRP and nothing else. And I managed to enter the TWRP recovery and from there I restored previous backup.
I will try to do a multipost due to more threads and problems which are the same...
But this is the solution...
In my folder on the picture you will see 2 files i marked with green color...
Use the file and burn it according to your current setup. Odin or custom recovery.
And the problem will be solved. Used 14 days and countless of hours to get out of this boot loop!
So im finally happy to see the boot up screen without pressing into download mode or recovery mode...
The folder on the picture is to be found on this forum... Just cant remember from which thread exackly
GL
Titanity said:
View attachment 5656047
I will try to do a multipost due to more threads and problems which are the same...
But this is the solution...
In my folder on the picture you will see 2 files i marked with green color...
Use the file and burn it according to your current setup. Odin or custom recovery.
And the problem will be solved. Used 14 days and countless of hours to get out of this boot loop!
So im finally happy to see the boot up screen without pressing into download mode or recovery mode...
The folder on the picture is to be found on this forum... Just cant remember from which thread exackly
GL
Click to expand...
Click to collapse
Bless you. My poor phone was down since 6-20. I was just kicking myself in the ass the other day saying if I got my phone to boot again i would never flash **** it on it ever again... @Titanity thank you so much for making me look like a liar. Now lets see what else we can do lol.
So you got it to work? And whats up next?
Titanity said:
So you got it to work? And whats up next?
Click to expand...
Click to collapse
Yes it did. I have gotten myself in some pretty bleak spots in the past and have been able to resolve all my issues on my own research, troubleshooting, trial and error etc. but I had never had a device that was actually able to power on, flash twrp, stockfirmware pass in odin, tried all type of pit file patches, adb and fastboot commands and still not be able to get into OS completely stumped me and I had exhausted so much time on it that i came to the conclusion that one of the talented members of XDA would for sure come up with a solution and I was right.
Sorry for the blabber, Ive been just a watcher of this site for many years and have never had to engage so my apologies for my forum etiquette.
I main focus now is to find a good rom to run with nethunter. I was running Dr. ketan Rom with nethunter while installing every LSposed Module that sounded cool and was beyond impressed by how stable my device still performed (one of my largest TWRP backups was 49Gb btw.) So yea, look for something with a strong kernal, light rom to see what I like. I have yet to try the new roms out due to unfamiliar processes of installing outside of Odin. Its been a while since I had some free time tinker in this space again.
Yea im just a watcher my self... it took me a few days until i decided to make this solution. Because i do think it was a important solution i found. But yes im just a watcher my self...
Now im stuck again though because i have a faulty usb-c, so its claming theres water inthe entrance which there isnt. And i been looking all over the forums for a solution like 3 times now. And people are just trying to trick the fault or acturally have a solution... But thats only IF they have water inside and the stupid alarm goes off...
Instead i need a solution to disable it now that its rooted. So need to know exackly what to look for and theres no help to get here. So kinda stuck... Irritating because i just wanna use it for dex... And not dex wiesless because its lagging on the mouse and what not... So my adapter need the recharge entrance and ... doh! Long journey so far... And its far from ended...
But im very happy it worked out for you... Keep in touch if you need another silly question. Then i might have silly questions for you aswell Good day my friend
@Titanity Bless your heart, I need your help . I broke my friends phone which is a note 10 plus, and all that you guys mentioned about trying everything I did as well.. I read your solution but I dont know where to find the files you marked and how to go about them exactly... the phone is currently on stock recovery and is stuck there.
Okay do you have a option to use a mic and the software discord? i do belive its easier for both of us if we can do this with direct communication. If you dont want to use / have a mic. Then its also fine. Discord got a chat aswell so dont be shy I have my own discord which is:
Join the thetitanity @ twitch.tv Discord Server!
Check out the thetitanity @ twitch.tv community on Discord - hang outwith 17 other members and enjoy free voice and text chat.
discord.gg
Ill pop op now and then, but im not a streamer anymore on twitch. So dont be mistaken by the server info...
Look forward to see you on there. And ill make sure to have the files ready for you
Until then haha
EDIT: I just uploaded a package filled with "i help you in case of emergency" files. Make sure to download it before entering discord. Get it at...
https://easyupload.io/xwlk0w - and the PW is: titanity (30 days avalible)
Also have info ready like: is the model a 975F or? what firmware is on it at the moment. Is the bootloader unlocked. But also things like do you ever used TWRP before and know how to use it etc?
Its a package filled with files of my choice, but made by people from the forum. So no credit goes to me but them...
Have in mind that all the time i been on the forum i always just read the forum and downloaded when needed, so its the first time im trying to help others... But im optimistic!
Titanity said:
Okay do you have a option to use a mic and the software discord? i do belive its easier for both of us if we can do this with direct communication. If you dont want to use / have a mic. Then its also fine. Discord got a chat aswell so dont be shy I have my own discord which is:
Join the thetitanity @ twitch.tv Discord Server!
Check out the thetitanity @ twitch.tv community on Discord - hang outwith 17 other members and enjoy free voice and text chat.
discord.gg
Ill pop op now and then, but im not a streamer anymore on twitch. So dont be mistaken by the server info...
Look forward to see you on there. And ill make sure to have the files ready for you
Until then haha
EDIT: I just uploaded a package filled with "i help you in case of emergency" files. Make sure to download it before entering discord. Get it at...
https://easyupload.io/xwlk0w - and the PW is: titanity (30 days avalible)
Also have info ready like: is the model a 975F or? what firmware is on it at the moment. Is the bootloader unlocked. But also things like do you ever used TWRP before and know how to use it etc?
Its a package filled with files of my choice, but made by people from the forum. So no credit goes to me but them...
Have in mind that all the time i been on the forum i always just read the forum and downloaded when needed, so its the first time im trying to help others... But im optimistic!
Click to expand...
Click to collapse
@Titanity bro that's so generous of you, alright.. downloading and will join discord then , Thanks dude