Related
Well, I've asked a mod to lock the other root status thread. It was getting kind of out of hand. After about page 80, people stopped looking at what we had done so far, and trying to help by putting ideas out that already failed.
This is what we know:
Fastboot is locked down in everything but oem-78 mode. You can get to this mode by typing "reboot oem-78" at an adb shell. Fastboot is essentially unlocked, allowing fastboot boot and fastboot flash, only the .img images we try to boot or flash NEED TO BE SIGNED.
Goldcards no longer allow non signed firmware to be loaded, only signed firmware with a different SID.
All known flashing methods require the .img files to be signed by HTC. We do not have the privatekey, nor do we have any way to decrypt the key as it is RSA. Meaning this is a NO GO.
All previous known exploits (asroot2, g1 telnetd, DROID update.zip method) have been patched. They won't work. And there isn't a way around this.
All the partitions except /data are mounted as read only. Meaning, without root access, there is NO way to modify them. In the init.rc file, they are mounted rw, and directly after that mounted ro. We can read and write to /data as we wish, but NOTHING important is here.
The only folder anything can run as root out of is /system/bin. Every other partition is mounted with the nosuid option, meaning code CANNOT be run as root. Simple enough. We can't run anything as the user root, or the group root.
Lets try to stay a little more on topic this time. Please don't let this become another 40 pages of complete crap. And please keep this thread about root access, any other problems should be posted in the appropriate forum.
Thanks, and lets get this root done!
I'm currently comparing superboot.img in a hex editor to the vanilla boot.img for that phone so I can better understand what he did, and how. I'll see what I can turn up, maybe we can make one for the eris.
EDIT: It seems it's not going to be so easy. There's a lot of things changed. It appears he changed something at the top of the file right after the header, and then there is some sort of (SHA1?) hash right below that, but I don't know what it's calculated from. This is beyond my skills at the moment, I think.
Are any of the fields changed from the original boot.img show up in our boot.img? Chance of searching for each field in our img and replacing with possibly what he did?
is it possible that the guy who made superboot has htc signature, or somehow decrypted it???? 8-O
Yes I guess anything is possable but I think their is a better chance of monkeys flying out of my butt.
well i guess it was time to lock the other thread as some people could not play nice..... so i guess we will use this one now..... next idea anyone, and i am guessing jman will no longer be joing us, so it looks like we are on our own.
im ready to get this done what have we got so far?
About 140 pages of failed attempts.
well i know that much i have been sitting back following from the begining now im ready to get my hands dirty, though i have no clue what im doing
binny1007 said:
well i guess it was time to lock the other thread as some people could not play nice..... so i guess we will use this one now..... next idea anyone, and i am guessing jman will no longer be joing us, so it looks like we are on our own.
Click to expand...
Click to collapse
Ok, I missed something I think. Thats what I get for not refreshing every 10 seconds What happened to jman? Or is it better off that I not ask
punk.kaos said:
Ok, I missed something I think. Thats what I get for not refreshing every 10 seconds What happened to jman? Or is it better off that I not ask
Click to expand...
Click to collapse
I don't think I'll be following these threads anymore. I try to help you guys, but in the end some of you just don't appreciate the help.
I don't claim to be an expert, and I never promised anybody that I could root their phone. I simply have information to share that I think has brought you guys to a greater understanding of your phones and the Android system. Most of you are thankful, but I really don't need to be attacked personally in these threads that don't even have anything to do with my phone.
I'd like to thank the moderator for locking down the other forum, I'd also like to thank whichever moderator deleted the message that was quite insulting to me.... I only happened to see it because it came into my email. Yes, I subscribed to the thread via email to try to keep up with you guys and offer any help I could as quickly as I could.
I'm sorry guys, I wish you luck, but I just don't need to be berated in open forum like that for trying to help the Eris owners out, so I won't be keeping up with your rooting efforts.
There are a couple of you that have been very appreciative, and please feel free to PM me.
Thanks jman and I understand, if I was in your shoes I would do the same and I reported that post almost right after it was posted hoping you would not see it. But I know for me I have a greater understanding of my phone and like I have said before Thank you very much for your help. It's a shame to see you go but we understand.
Binny
doubt this will help, its all that htc tech support would throw up at me.
http://developer.htc.com/
contains hero and adp but nothing about eris.
jmanley69 said:
I don't think I'll be following these threads anymore. I try to help you guys, but in the end some of you just don't appreciate the help.
I don't claim to be an expert, and I never promised anybody that I could root their phone. I simply have information to share that I think has brought you guys to a greater understanding of your phones and the Android system. Most of you are thankful, but I really don't need to be attacked personally in these threads that don't even have anything to do with my phone.
I'd like to thank the moderator for locking down the other forum, I'd also like to thank whichever moderator deleted the message that was quite insulting to me.... I only happened to see it because it came into my email. Yes, I subscribed to the thread via email to try to keep up with you guys and offer any help I could as quickly as I could.
I'm sorry guys, I wish you luck, but I just don't need to be berated in open forum like that for trying to help the Eris owners out, so I won't be keeping up with your rooting efforts.
There are a couple of you that have been very appreciative, and please feel free to PM me.
Click to expand...
Click to collapse
Thanks for sticking through with us. You've been extremely helpful since day one, and I would like to say thanks and basically say what Binny said above.
I haven't had a lot of time to follow the thread, but, I too, am happy that it was locked. Hopefully the Eris owners can regroup in a day or so after we all chill out. Sigh. Fingers are still crossed for root.
Has anyone been able to actually BOOT any of the images extracted from the rom.zip via fastboot in oem-78 mode? If so, and you could post how, I might have access to an image with root access. I've tried repeated times to perform "fastboot boot recovery.img" but it sends it and then sticks on "booting..." I have moved forward with the RUU at this point, but the device never actually boots into the img.
Unfortunately, I cannot not upload the image due to my job.
Also, if anyone can help with goldcard downgrading, I might be able to downgrade to an old version with root access. My downgrade continues to fail due to the bootloader version being too high. I created the goldcard per the appropriate thread and it appeared to work as the Cell South thread indicated, but still no dice on the downgrade.
If your gold card is made right it should work.... are you putting the .zip on you gold card and renameing it PB00IMG.zip?
binny1007 said:
If your gold card is made right it should work.... are you putting the .zip on you gold card and renameing it PB00IMG.zip?
Click to expand...
Click to collapse
Yes, but it still fails with error 43, I believe. "Main version check"
Did you run the simlock option in the bootloader, and it passed
binny1007 said:
Did you run the simlock option in the bootloader, and it passed
Click to expand...
Click to collapse
Yes. Perhaps goldcard doesn't work on this device like it's supposed to.
Hello
I am new here and was wondering if someone could tell me what to do or what I did wrong.
I rooted my phone and put a custom rom on my phone by modaco. When I reboot the phone it will not go pass the dell logo. I followed all the instuctions at the unlockr.com. Followed all the videos.
Can someone tell me if I need to take something off or redo it. I am able to get into the fastboot mode and into the clockwork mod recovery v1.8.1.7 and see all the files and upload files to my sd card if I need to take them out and add through my card on my pc.
I am wondering if I did a step wrong. I also tried to go back to the stock rom and cannot get there because my phone won't boot.
I don't think it is bricked. I think I just made a mistake by skipping a step.
Thank you for your help.
khernden69 said:
Hello
I am new here and was wondering if someone could tell me what to do or what I did wrong.
I rooted my phone and put a custom rom on my phone by modaco. When I reboot the phone it will not go pass the dell logo. I followed all the instuctions at the unlockr.com. Followed all the videos.
Can someone tell me if I need to take something off or redo it. I am able to get into the fastboot mode and into the clockwork mod recovery v1.8.1.7 and see all the files and upload files to my sd card if I need to take them out and add through my card on my pc.
I am wondering if I did a step wrong. I also tried to go back to the stock rom and cannot get there because my phone won't boot.
I don't think it is bricked. I think I just made a mistake by skipping a step.
Thank you for your help.
Click to expand...
Click to collapse
The phone was working and I started to get some errors so I turned my phone back off and have not been able to get passed this dell logo when I turned it back on.
You could try reflashing it I suppose, if if that doesn't work and it's very new you might be able to convince Dell to exchange it as faulty
This is NOT a hardware fault!
Please have a look at this forum:
http://android.modaco.com/category/436/dell-streak-streak-modaco-com/
where you will find answers to ALL your questions.
Success.
Why isn't this a sticky, it's not irrelevant as people still keep doing things they shouldn't
http://forum.xda-developers.com/showthread.php?t=759951
Troute said:
You could try reflashing it I suppose, if if that doesn't work and it's very new you might be able to convince Dell to exchange it as faulty
Click to expand...
Click to collapse
Thank you. I just called Dell Yesterday and I am getting a new one sent. The phone wouldn't even do a factory reset. She said that they have been having problems with them.
Techneut said:
This is NOT a hardware fault!
Please have a look at this forum:
http://android.modaco.com/category/436/dell-streak-streak-modaco-com/
where you will find answers to ALL your questions.
Success.
Click to expand...
Click to collapse
Thank you for your help. Getting a new one from Dell.
Hey guys.
I've been attempting this all morning and so far I've had no luck. I have a VodafoneAU Legend which I updated to the official 2.2 yesterday. But now I want to try root.
I've been trying to follow the HBOOT 1.01 guide but there's a few problems. First, I cannot connect to the phone with adb unless it's in htc sync mode. No other mode will work. So when it's time to copy testimage.zip to the card I have to change from sync mode to disk mode, whereby adb loses it's connection. What do I do about this? Is it a driver problem (in Win7 here) or something else?
Thanks,
Dave.
Ok, the first problem were drivers.
Now I can't finish the second guide. When I try using clockwork to install the firmware.zip, the phone just boots to the red triangle. What do I have to do?
Dave.
So I pressed the up button/power combo at the red triangle and get the Android system recovery. Selecting "apply update.zip" says it can't verify. What do I do? Is this guide for my phone or do I need to follow something else?
I don't understand this guys. Anyone help? I'm thinking since this is a step to root the phone, I'm not actually rooted yet so I can't use the clockworkmod? Then what is the guide for? The guides at unlockr don't mention what firmware/hboot they work for so I'm not keen to try them yet.
Read the guide on fake flash. You need the recovery file named "update.zip" in the root of your sd to proceed..
Sent from my Legend using XDA App
whitetigerdk said:
Read the guide on fake flash. You need the recovery file named "update.zip" in the root of your sd to proceed..
Sent from my Legend using XDA App
Click to expand...
Click to collapse
But isn't that what Rom Manager does? Download the update.zip then run it? Man this is getting even harder to understand.
Edit: And this is left out of the HBOOT 1.01 guide because.....????? When I work this out I'll write a PROPPER guide, lol.
Just checked and update.zip is on the card.
So which part of the guide am I getting wrong?
Decided to reinstall phone with the official froyo release and am now ready to try this again. Is there anyone that will walk me through the process? I will write a complete guide if the "gotchas" are still there.
i feel for you ... hope you get it fixed... thats one of the reason i havent dared messing with the phone because i've seen a few post like yours where something didnt go quite as described... for whatever reason... and im sure the answer is out there but just not within the guide instructions... i guess there is no way to gather all gotchas because there are so many environment variables...
good luck
and please share your technique
Just saw gobczak's thread in the developer forum having similar troubles with Vodafone UK phone, getting the red triangle at reboot. I'll keep an eye on his thread and see how he goes with it.
Did you run the stage1 and stage2 bats while in recovery?
dezzadk said:
Did you run the stage1 and stage2 bats while in recovery?
Click to expand...
Click to collapse
No because the guide didn't say to.
The thing is it seems I'm only stuck on the part where the firmware.zip file has to be flashed. The guide says to use clockworkmod for this. But when I try installing the clockworkmod recovery it gives some file verification error. Isn't there ways to do this via the pc, either through those batch files, adb etc? Or will that fake-flash update.zip file work?
jabbado said:
No because the guide didn't say to.
Click to expand...
Click to collapse
As I just posted on the other forum, I think you need to skip that step in guide 2 and go straight onto guide 3 after you have flashed the LEGEIMG.zip, rebooted, and then removed LEGEIMG.zip from the SD card.
Guys I've got to the point of downgrading to 1.31. But when I run the first batch file it just hangs at the "Writing zip" part, with the htc logo on the screen. Is there any way to fix this?
Can someone please explain this part of the guide:
Phone will reboot and find LEGEIMG.zip on your sdcard, copy it into RAM and check it. If you get CID error at this point, then you don't have goldcard.
Click to expand...
Click to collapse
Ok, so I don't get an error. I get nothing. The phone just boots to the fastboot screen. If I press the power button it goes to the hboot screen and I can see the messages of loading LEGEIMG.zip. But the guide doesn't say to press anything.
So should I or shouldn't I press the power button? Also, if I try making the goldcard again, at which point in the guide do I start from again? The entire process or just copying LEGEIMG.zip to card then rebooting phone? I mean, will all the other things like flashing misc1-2.img still be there?
Guys I finally got this working.
The first problem was with the goldcards. For whatever reason formatting them with the win7 format tool just wouldn't work. I had to use the command-line format tool, setting the block size etc manually.
The second problem was the unnecessary steps in the guide. A few people helped me out with this (namely blackbart at the Aus Whirlpool forum), but basically in the second step you can stop after flashing the LEGEIMG.zip. The updating froyo part isn't needed - for my phone anyway.
Then when running the batch files in the third part, for whatever reason the first batch would keep hanging at 'writing zip...' and I needed to remove the battery to unfreeze the phone. flannigan, also from the Aus Whirlpool forums suggested to just go on to the second batch file. This worked!
So my Legend is now finally a true Legend
Anyway, thanks for the help everyone - couldn't have done this by myself.
Dave
Great news, I think we need a new guide focused on rooting for HBOOT 1.01 / Stock Froyo to clear up the inconsistencies in the existing one. It's a minefield for a noob (or a rite of passage!), a revised guide will certainly save a lot of time and frustration for those taking this road in the future.
Sent from my HTC Legend using XDA App
EpicSauce said:
Great news, I think we need a new guide focused on rooting for HBOOT 1.01 to clear up the inconsistencies in the existing one. It's a minefield for a noob (or a rite of passage!), a revised guide will certainly save a lot of time and frustration for those taking this road in the future.
Click to expand...
Click to collapse
I'll write one if ya's want. I wanted to include little tidbits like downloading the apps required (visionary, rom manager etc) from the market then backing them up to the card with Astro so if it goes all wrong and you have to start again, you can just install them all from the card Also on using adb to push the files (roms, img's etc) when the guides say "copy this blah blah". Much quicker than changing to disk mode and back. Sound good?
Sounds good! Happy to help and add my 20c worth along the way. The existing guide has got the meaty bits, a new guide would cull the stuff not relevant, help fill in the gaps and alert to the pitfalls we've fallen into.
jabbado said:
I'll write one if ya's want. I wanted to include little tidbits like downloading the apps required (visionary, rom manager etc) from the market then backing them up to the card with Astro so if it goes all wrong and you have to start again, you can just install them all from the card Also on using adb to push the files (roms, img's etc) when the guides say "copy this blah blah". Much quicker than changing to disk mode and back. Sound good?
Click to expand...
Click to collapse
I agree... i've done my reading since june of last year but then didnt check for another 4 months... and so many how to's pop up with various ways of doing it depeding on the situation... a lot of those howtos were consolidated howtos which sometimes make intermediate steps unenecessary (may be in some cases causes more head aches since it didnt take into considerations on newer version of hboots...etc)... an updated how to will be much appreciated...
And you're right the most important pre requirement is to have a safety net ... so starting with how to create a back up in case you screw it up is a must!
but im glad it worked out for you!
Tab boots to "welcome" screen but does not register touches, leaving me unable to move forward. Ready for the long story?
I am helping a friend who bought this tab from a third party. When he received it, the previous owner stated that they did a factory reset back to Honeycomb but he noticed that it did in fact still have ICS on it. Probably OTA'd when the previous owner did the reset. Tab worked fine for about two weeks until one day he came home and the lockscreen would not register touches. That's where I come in.
I did the "erase, wipe" (booting while switching the screen rotation back and forth.) Tab wiped and brought me to the "Welcome" screen where you select country and language and still does not register touches. I have tried blackthund3r's flash and manager tools, as well as multiple guides to recover from what I have seen referred to as "flu." The main problem I have is that I cannot get a valid UID. Using USBDeview gives me an 11 digit serial but it returns as invalid when plugged into DotNetDetector and I am unable to use SDB because the non working touchscreen has left me unable to enable USB debugging.
Any suggestions, help, advice, on things I can try? I am really stumped and would like to help my friend/conquer this problem. Thanks for anyone who has taken the time to read this/offer help.
generalagony said:
Any suggestions, help, advice, on things I can try? I am really stumped and would like to help my friend/conquer this problem. Thanks for anyone who has taken the time to read this/offer help.
Click to expand...
Click to collapse
Get ready for some Ubuntu... Here is the guide that will get you a valid sbk. My nephew just brought his tab to me after forgetting his password. So I was in the same boat as far as UID/SBK. This is gonna take a while so put some time aside.
JdgM3NT4L said:
Get ready for some Ubuntu... Here is the guide that will get you a valid sbk. My nephew just brought his tab to me after forgetting his password. So I was in the same boat as far as UID/SBK. This is gonna take a while so put some time aside.
Click to expand...
Click to collapse
As sure as I am reading yoru reply the damn thing just started working. I was able to get to USB debugging and via ADB I was able to pull the UID; which was the same as the one I got from USBDeview btw. Still an 11 digit code. The only thing I can guess is that it has a faulty touchscreen, or maybe the battery was just too low to register touches? Thanks for your reply though. Always nice to be able to rely on the folks at XDA.
That is too cool. The other way is a learning experience to be sure. Enjoy.
JdgM3NT4L said:
That is too cool. The other way is a learning experience to be sure. Enjoy.
Click to expand...
Click to collapse
I have now realized that the touchscreen does work but is very glitchy and have found that lots of people have had problems with the OTA ICS update. Any suggestions on a good custom ROM for this tab? It isn't mine so I have not been following this section. Would like something close to stock ICS but with fixes that resolve the problems associated with OTA.
generalagony said:
...I was able to get to USB debugging and via ADB I was able to pull the UID; which was the same as the one I got from USBDeview btw. Still an 11 digit code...
Click to expand...
Click to collapse
generalagony said:
I have now realized that the touchscreen does work but is very glitchy and have found that lots of people have had problems with the OTA ICS update. Any suggestions on a good custom ROM for this tab? It isn't mine so I have not been following this section. Would like something close to stock ICS but with fixes that resolve the problems associated with OTA.
Click to expand...
Click to collapse
First check in Settings>About Tablet>Build Version - this will tell you what rom you are currently running -
Then, if you can, download and install Acer Recovery Installer
This tells you what bootloader and recovery is installed.
The glitches you speak of and the 11 digit uid point to an ICS Rom and unpatched HC bootloader - updating to the new BL often fixes these weird glitches BUT if you flash a custom rom as well, you'll be running sweet!!!
If you wanna stay close to Stock then I'd recommend ezterrys one here comes pre-rooted and busy box installed - and if you want to you can install his Over clocked kernel too.... plus its well maintained and supported
there are many tools and guides around to help you...the ones in my sig for instance the cpuid one has a lot of general info in it too re bootloaders, sbk and flash tools.
If you have any q just ask, there's always someone round willing to help...good luck!!
Elite thanks in advance. No, seriously, thanks. I'm a broke single parent of 2 kids and I realized my phone is about my only guilty pleasure after giving my kids 200% of my time and money. Any help would be appreciated.
I have an LG G2 that I apparently bricked by using an app to "freeze" the latest OTA software update that was pushed to my ATT LG G2 about a month + ago if not slightly longer. I unfroze the process and the update suddenly appeared and said it would reboot the phone and or apply the update it in 30 seconds. I panicked and held the power button in to turn the phone off.
Once the phone was turned back on I was greeted with tiny white text that said "error: Boot certification verify" From here I was unable to get into down load mode, do a hard reset. I was able to see fast boot mode but wasn't sure what to do with it. I was able to see the phone in Windows 7 Pro Sp1 device manager but it was listed as QHSUSB_BULK
After initially freaking out which lasted about 20 mins, I was able to compose myself and start researching my new seemingly serious problem. After a few hours of reading a dozen or so treads / hundreds of replies it seemed I would have to load into Ubuntu and push some files to my LG G2.
I followed this guide - http://forum.xda-developers.com/showthread.php?t=2582142
I was very careful to follow this guide to the letter and everything went as expected the first, 2nd and 3rd time only the results were worse and worse and worse.
The first time I lost fast boot, the 2nd time I lost the boot certification verify error, After the 3rd attempt I get a split second LG Logo and that's it. What did I do during those 3 attempts? The first time, the 4 files and the recovery as directed. The 2nd time, the same files, plus the boot.img and a different recovery. The 3rd time, all the files and yet a different recovery. All the files were pulled from here - http://downloads.codefi.re/autoprime/LG/LG_G2/D800
The other recovery.imgs were for the correct model, just older, newer variants. I was very careful to push the right files to the right partitions.
I can still see the phone via Ubuntu. I'm scared to do anything else along the lines of what I've been doing. In fact I'm lost as to what to do next.
Can anyone here help me push more / different files via Ubuntu that would help bring my phone back to life? I'm completely dead in the water. Or perhaps an exe package / program that can fix my problem? If I sound stupid, it's because this is all new to me.
Thanks in advance, Tom
@rthefley Go back to the autoprime downloads and get the boot, aboot and laf image. Follow the ubuntu guide and flash those images only.
@art
Thank you for taking the time to stop and help me. I greatly appreciate it. I followed your instructions and pushed those 3 files in the order you gave me. Results were the same, nothing. I still get a very brief LG logo but nothing more. I can get into the hard reset but it does nothing as well.
Here are pics I took of the files and directories from my phone connected via usb through Ubuntu. There are a few wrong commands, ignore them. GF was behind me talking and I wasn't focused. I can assure you the proper cmds were given when it counted.
Well ....... I guess I cannot post links ............. so they are edited out. I wanted to show that my highest number was sbe43 so I had to use sbe
Im using the files from the D800 dir which is the ATT LG G2. Or should I tried another directory or files? I can still access the phone via Ubuntu ... THANK GOD
I am still hopeful.
rthefley said:
@art
Thank you for taking the time to stop and help me. I greatly appreciate it. I followed your instructions and pushed those 3 files in the order you gave me. Results were the same, nothing. I still get a very brief LG logo but nothing more. I can get into the hard reset but it does nothing as well.
Here are pics I took of the files and directories from my phone connected via usb through Ubuntu. There are a few wrong commands, ignore them. GF was behind me talking and I wasn't focused. I can assure you the proper cmds were given when it counted.
Well ....... I guess I cannot post links ............. so they are edited out. I wanted to show that my highest number was sbe43 so I had to use sbe
Im using the files from the D800 dir which is the ATT LG G2. Or should I tried another directory or files? I can still access the phone via Ubuntu ... THANK GOD
I am still hopeful.
Click to expand...
Click to collapse
In that case, you should try to push a recovery image, too!
Raymonf said:
In that case, you should try to push a recovery image, too!
Click to expand...
Click to collapse
I've pushed 4 or 5 different recovery images. Should I try something different than the recovery images suggested? I am willing to try anything at this point.
rthefley said:
I've pushed 4 or 5 different recovery images. Should I try something different than the recovery images suggested? I am willing to try anything at this point.
Click to expand...
Click to collapse
Did you lokify them?
Raymonf said:
Did you lokify them?
Click to expand...
Click to collapse
@Raymonf first let me thank you for taking the time to try and help me sort out my ... what I consider a serious issue. Thank you!
I've not read about lokify. So I am not sure what that is but I can absolutely tell you, I'm a great listener. I've spent 12 or 13 hours reading all over the internet, tread after tread and post after post. So I somehow missed the instructions on lokifying the files.
Tom
rthefley said:
@Raymonf first let me thank you for taking the time to try and help me sort out my ... what I consider a serious issue. Thank you!
I've not read about lokify. So I am not sure what that is but I can absolutely tell you, I'm a great listener. I've spent 12 or 13 hours reading all over the internet, tread after tread and post after post. So I somehow missed the instructions on lokifying the files.
Tom
Click to expand...
Click to collapse
Okay, are you now able to go into download mode?
1127
Art Vanderlay said:
Okay, are you now able to go into download mode?
Click to expand...
Click to collapse
No, I've never been able to get into the download mode.
The only way I can access my phone is via Ubuntu. Hard Reset doest work even though I can get to that screen and initiate the process, it doesn't complete.
One other person that's also trying to help me out asked if I've lokify those img files. No I haven't. I've not come across those instructions yet. Would that make a difference?
I also sent you a private PM with links to pics I took of my directory structure from my ATT LG G2 via usb / Ubuntu
rthefley said:
No, I've never been able to get into the download mode.
The only way I can access my phone is via Ubuntu. Hard Reset doest work even though I can get to that screen and initiate the process, it doesn't complete.
One other person that's also trying to help me out asked if I've lokify those img files. No I haven't. I've not come across those instructions yet. Would that make a difference?
I also sent you a private PM with links to pics I took of my directory structure from my ATT LG G2 via usb / Ubuntu
Click to expand...
Click to collapse
Your directories are fine. But if you successfully flashed those 3 partitions, you should Have a working download mode. Make sure you fully power off the phone, you might have to hold the button down for a while.
Art Vanderlay said:
Your directories are fine. But if you successfully flashed those 3 partitions, you should Have a working download mode. Make sure you fully power off the phone, you might have to hold the button down for a while.
Click to expand...
Click to collapse
Yes I'm pretty sure it's completely powered off. I will try again but I've held the power button in for several several seconds and saw the screen go solid black. I've flashed those 3 files just as instructed. Nothing is working sadly. Maybe I am missing some key procedure others take for granted that I just personally do not know about
Is there anything else I could try doing? I'm going in circles here.
Do your results match the one in the forum when you type gdisk -l /dev/sdb in the terminal.? Also is your fastboot still gone.?
Sent from my LG-LS980 using Tapatalk
LilDemon124 said:
Do your results match the one in the forum when you type gdisk -l /dev/sdb in the terminal.? Also is your fastboot still gone.?
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
No they are different, I actually gdisked all of the different letters but I have an sda,c,b and e, I even have have an sde1. All the numbers follow sde however up to 42 or 43. So when I gdisk -l /dev/sde that's when I see all the files.
I've tried to gdisk sdb but I get a mbr / gpt or something error saying something is corrupted so I just leave it alone.
Should I be looking at a different letter then? If so, I can't seem to get into any of them other than the one I mentioned, sde
Guys, I'm now offering a $40 paypal bounty directly to your pocket or a donation to this web site for help allowing me to get back into my phone.
I will try my best to help you. Im at work, but will be home soon so that I can do some snooping.. From what your saying you MIGHT have a corrupt storage OR you might have a corrupt file.
Sent from my LG-LS980 using Tapatalk
Im going to have to work on this a bit later. Worked all day. I'm still here and around just need to get a little sleep before I even think of trying to dive into this again. Thanks.