[SOLVED] Help - CWM not sticking? - Sony Xperia T, TL, TX, V

So i was in the process of trying to root my phone* and install CWM > XperimenT, and ran into a couple of serious problems.
1) my IMEI is screwed up, it may be recoverable if I can get root (which is possible with this firmware) EDIT: my IMEI looks fine actually, I just need to get the APN for ATT.
2) While trying to install CWM, it shows success, but I can't get into CWM. I've tried tapping the hell out of the up and down volume keys but have had no success.
*Phone LT30at, I excluded the baseband per instructions to keep the LT radio.

So after searching around on the forums here I got my internet working. I'd still like some help with number 2, as it would suck to be stuck on firmware .303.
Thanks in advance.

scythekain said:
So i was in the process of trying to root my phone* and install CWM > XperimenT, and ran into a couple of serious problems.
1) my IMEI is screwed up, it may be recoverable if I can get root (which is possible with this firmware) EDIT: my IMEI looks fine actually, I just need to get the APN for ATT.
2) While trying to install CWM, it shows success, but I can't get into CWM. I've tried tapping the hell out of the up and down volume keys but have had no success.
*Phone LT30at, I excluded the baseband per instructions to keep the LT radio.
Click to expand...
Click to collapse
scythekain said:
So after searching around on the forums here I got my internet working. I'd still like some help with number 2, as it would suck to be stuck on firmware .303.
Thanks in advance.
Click to expand...
Click to collapse
From what this says, you do not have root yet. Try rooting your phone first and then getting into CMW

gregbradley said:
From what this says, you do not have root yet. Try rooting your phone first and then getting into CMW
Click to expand...
Click to collapse
Thanks for the reply,
I did get root, and I think I've found the problem. Just not sure how to fix it.
http://forum.xda-developers.com/showpost.php?p=38062382&postcount=57
1) the blue LED is not working, because the script is pointing to the wrong location. I can turn it on with the correct location from my device (in the above link)
2) it looks like the script (chargemon) is looking for key event7. I'm thinking this is not the volume up key on my device. I browsed the file system from adb shell and chargemon and recovery.tar are in the correct locations. the remote script also asked my device for super user access. (shell)
and that's where I'm at right now. I'm sure there's an adb command to simulate an event so I can tell what keypress event7 is, I just haven't found that command yet.

OK, you can try volume down as well.
Which CMW are you tring to install? from which thread is it?

gregbradley said:
OK, you can try volume down as well.
Which CMW are you tring to install? from which thread is it?
Click to expand...
Click to collapse
I tried both the V3 and the older one which uses event0. The event0 one if it installed correctly also didn't respond to the vol up and vol down key commands.
The V3 one, I got to boot to recovery by banging on all of the hardware keys.

Related

[Q] wrong sbf? need proper one for (RTGB)

first post, yes, i'm new to this... (forum, not flashing, not entirely anyway, i did fiddle with Sony Ericssons and stuff, kindergarden compared to androids)... but not an idiot, to the point:
firmware config. version seems to be RTGB, great britain, right? wrong, a RTUK is not it. I am sort of lost, i bought the phone with 2.1-update1, the 2.2.1 update has not yet been rolled out in my backwards country, so i did an official update over the internet with motorola app etc etc. I have no idea what was the 2.1 fw config. ver., but it strikes me as weird that i have a RTGB one now, the packaging/box/manuals all were German or something that looks like German. And now, i got myself RTUK sbf file, and RDS lite fails to do anything. I require assistance, and an explanation if possible as to why this didnt work? if i chose the wrong sbf, why does it show me having RTGB? and finally which sbf to take and from where (two german one's are available on this forum), but i've seen only one RTGB and it was only 2.1. For comparison, the friend bought the same phone on the same day, but she got one with a qwertz keyboard, mine is normal qwerty, fw config. ver. shows VFDE, did not update hers, it's still 2.1-update1. I can only assume that VF is german for RT and that her phone did not come from an unknows source. The phone company selling these obviously imports them, possibly even from random countries or EU countries at least...
however something did happen, my battery in the notification seems to be not present, there's just a question mark inside what appears to be an empty battery... apps that show battery levels work fine... although, scratch this last one, a reboot fixed it, even though i have not seen it before.
also, help me rack up some posts ^^ ask for info or whatever, i'd like to give a shot at improving my android...
Check the link below. You will get both service and non-service versions of 2.2.1 sbf's.
http://and-developers.com/sbf:milestone221
VF would be vodafone ( service version) while RT would be retail version.
Sent from my Milestone using Tapatalk
Thanks, gonna try asap, will come crying if it explodes in my face...
SuicideTree said:
Thanks, gonna try asap, will come crying if it explodes in my face...
Click to expand...
Click to collapse
It wont. I have done it many times and my face is still intact, as you can see from my avatar.
Sent from my Milestone using Tapatalk
now add a laptop that sometimes, actually recently starts bsoding not when you're gaming but when you're picking your nose... and now a serious question, how screwed am i if the laptop crashes WHILE doing something with RDS Lite or something similar ;]]
SuicideTree said:
now add a laptop that sometimes, actually recently starts bsoding not when you're gaming but when you're picking your nose... and now a serious question, how screwed am i if the laptop crashes WHILE doing something with RDS Lite or something similar ;]]
Click to expand...
Click to collapse
which version of rsdlite and what OS? rsdlite should not cause your OS to crash.
oh no, it's not rsd lite related, it's just laptop hardware being faulty, that's my assumption anyway, this laptop is going to the warranty next monday, it bsods randomly and i mean really randomly... atm i have win7ult x64 and rsd is 4.9... however this is unrelated, i had a linux here and on it was screwing me over from day one.
SuicideTree said:
oh no, it's not rsd lite related, it's just laptop hardware being faulty, that's my assumption anyway, this laptop is going to the warranty next monday, it bsods randomly and i mean really randomly... atm i have win7ult x64 and rsd is 4.9... however this is unrelated, i had a linux here and on it was screwing me over from day one.
Click to expand...
Click to collapse
Try it and see if it works.
Just finished. Seems to be good. Gonna Continue with the guide then ^^ Many thanks.
instead starting a new topic IDIOT QUESTION but... can someone give me a detailed dumbed down version of this instruction bellow:
If you applied an OTA update before, there is a script run at every system boot that checks and re-flashes the recovery when its checksum doesn't match. In such case, you have to avoid booting to android after the vulnerable recovery flash. Boot directly to recovery when RSD Lite restarts the phone (hold camera button) and from there remove the /system/etc/install-recovery.sh file.
rm -f /system/etc/install-recovery.sh
i am getting this
E:Cant open /cache/recovery/command
just upon entering AOR (power+x)
trying to apply the update regardless i get this
- install from sdcard
finding update package
opening update package
verifying update package
E:EOCD marker occurs after start of EOCD
E:signature verification failed
Instalation aborted
what is the meaning of this?
possible solutions:
"It seems that the key to successful recovery flash in some cases is to not let the phone to boot to android or recovery until the RSD Lite will signal PASS. When the RSD Lite is restarting the phone during flash, hold the D-Pad Up, so the phone enters the bootloader again immediately."
does this work? DIDNT WORK, so i still need help
i'm still combing through many threads mentioning this... either please tell me this works or point me in the right direction -_- thanks
Once you flash the official sbf, you need to flash the vulnerable recovery to enable you to run openrecovery which is used to flash custom roms and much more.
There is a script which checks your recovery image everytime it boots and replaces it with the original if it finds any changes. So you need to remove that script.
Procedure would be as follows.
1. Download and extract androidiani openrecovery to the root if your sdcard. You should have a update.zip file and openrecovery folder.
2. Flash official sbf.
3. Flash vulnerable recovery sbf. When the phone restarts and before it displays Moto logo, press and hold the 'x' key on your keyboard. You should see a triangle with exclamation mark. Press volume up + camera button and choose apply update menu option.
AOR should load up. Choose console option and type the following commands.
rm - rf /system/etc/install-recovery.sh
reboot
That's all.
Sent from my Milestone using Tapatalk
okay, so it seems i did all the steps EXCEPT flashing the original sbf... wait, the first link you provided was to a an official sbf - correct? then where do i get the vulnerability? or vulnerable_recovery_only_RAMDLD90_78.sbf is it? so, i have original flashed, when trying the vulnerability now it says failed, 0x7100, phone connected. what does that mean?
SuicideTree said:
okay, so it seems i did all the steps EXCEPT flashing the original sbf... wait, the first link you provided was to a an official sbf - correct? then where do i get the vulnerability? or vulnerable_recovery_only_RAMDLD90_78.sbf is it? so, i have original flashed, when trying the vulnerability now it says failed, 0x7100, phone connected. what does that mean?
Click to expand...
Click to collapse
The RAMDLD90_78 is the Vulnerable Recovery.
RSD Lite is a buggy program sometimes. What you need to do is put the sbf you want to flash on the ROOT of your C:/ drive and try it again.
I suppose there's no harm in trying that, i already had to rename it to something shorter, cause it wouldnt even give me the Start button.... brb
skadude66 said:
The RAMDLD90_78 is the Vulnerable Recovery.
RSD Lite is a buggy program sometimes. What you need to do is put the sbf you want to flash on the ROOT of your C:/ drive and try it again.
Click to expand...
Click to collapse
Buddy, please help him out with the rsdlite problem. I presume you had the same problem and someone helped you out, especially with the Windows 7 x64 error.
@SuicideTree : What is your ultimate goal? You want to have a Official ROM on your phone or you want to flash custom roms.
sileshn said:
Buddy, please help him out with the rsdlite problem. I presume you had the same problem and someone helped you out, especially with the Windows 7 x64 error.
@SuicideTree : What is your ultimate goal? You want to have a Official ROM on your phone or you want to flash custom roms.
Click to expand...
Click to collapse
You helped me out with that sileshn!
Yeah, I'll keep this thread up and I'll see what issues he's got.
sileshn said:
Buddy, please help him out with the rsdlite problem. I presume you had the same problem and someone helped you out, especially with the Windows 7 x64 error.
@SuicideTree : What is your ultimate goal? You want to have a Official ROM on your phone or you want to flash custom roms.
Click to expand...
Click to collapse
oh well, i was going for cyanogenmod, but for starters i'd like root to have some more control over my phone
EDIT: it also appears that once again it wont give me the START button, cant press it, moved files around, renamed and stuff... weird
EDIT2: by the way, is it normal for the vulnerability file not to show any file properties in RSD Lite?
SuicideTree said:
oh well, i was going for cyanogenmod, but for starters i'd like root to have some more control over my phone
EDIT: it also appears that once again it wont give me the START button, cant press it, moves files around, renamed and stuff... weird
Click to expand...
Click to collapse
Once you get VR, rooting and flashing a custom ROM is a piece of cake, so it shouldn't be that bad once you get there.
SuicideTree said:
oh well, i was going for cyanogenmod, but for starters i'd like root to have some more control over my phone
Click to expand...
Click to collapse
If you want to flash CM, just install GOT 2.2.1 from here and forget about VR. GOT has VR injected into it. Use the Retail UK sbf.
Once you have CM, you have root.
@skadude : Didn't know it was me.
is cm7 much better over cm6? cause i was looking into that ^^ however if the end goal can be achieved easier with got cm6 i should give that a try, but, what if i wanna play around with this stuff later or something? i'd like to understand what's happening at the moment... anyway, if i go with got solution what are the steps? flash uk sbf, then got or... then cm?
also, got or is better than aor? except apparently having vulnerability alreay in it... anything else?
thanks for all the help, sorry for being not too enlightened, i'll get there ;]]]

[Q] LG Thrill GB w/ClockworkMod Recovery

(Obvious Noob warning---) A friend helped me root my Thrill, install ClockworkMod Recovery, and then install CM7 on my Thrill. But I would like to try the LG GB release. Is it necessary to backtrack all the way back to stock to do this (i.e. reinstall the stock ROM, reinstall the stock recovery, unroot, etc.)?
My friend tried using the LG upgrade tool on his LG phone without going back to stock and ended up bricking it. He says that usually within a few days of release, a CMR compatible zip file (usually already rooted) appears here on XDA (I haven't seen it), which makes things easier (but obviously he didn't wait for it himself).
Will a zip be possible for the Thrill GB? (The file seems quite large (420MB), so I'm guessing there is a lot of media included.) Or should I just bite the bullet and backtrack?
Rick
Rick Tillery said:
(Obvious Noob warning---) A friend helped me root my Thrill, install ClockworkMod Recovery, and then install CM7 on my Thrill. But I would like to try the LG GB release. Is it necessary to backtrack all the way back to stock to do this (i.e. reinstall the stock ROM, reinstall the stock recovery, unroot, etc.)?
My friend tried using the LG upgrade tool on his LG phone without going back to stock and ended up bricking it. He says that usually within a few days of release, a CMR compatible zip file (usually already rooted) appears here on XDA (I haven't seen it), which makes things easier (but obviously he didn't wait for it himself).
Will a zip be possible for the Thrill GB? (The file seems quite large (420MB), so I'm guessing there is a lot of media included.) Or should I just bite the bullet and backtrack?
Rick
Click to expand...
Click to collapse
I'm assuming that the official update method was used.
Just use this method after downloading the update. No bricking.
SEE THREAD
The Dark Lestat said:
I'm assuming that the official update method was used.
Just use this method after downloading the update. No bricking.
SEE THREAD
Click to expand...
Click to collapse
Thank you for your help!
Rick
Trojan?
Sorry, but as a noob, I can't post in that other thread.
It seems that the shttp3.exe in the LG Flash Package triggers Symantec's trojan detection. Some searching seems to indicate (assuming I'm reading all the cryptic virus sites correctly) that there is something to this, although it seems that different scanners find different trojans/viruses (can't post the link, but Google for "shttp3.exe" and "trojan"). I also found that the web site for this utility is blocked at work, because it's a "malicious site."
Has anyone seen this? Has anyone been able to verify/refute this?
Rick
There is no virus, Lestat would never do that
Sent from my LG-P925 using XDA
Just my .02 .....Get rid of Symantec !! They are known for scaring people into a virus frenzy.. Yes, it is possible that it is seeing it as a potential virus because shttp is a workaround from the usual porting of windows ip services. ...
Correct me if i'm wrong somebody please !!
Get yourself Comodo and save your money...
Regards,
Dwayne
PS: somebody on here has written a script that just uses shttp temporarily while
your doing the flash procedure, and then reverts your host files back automatically after your done. You should try it.
dwaynedman said:
Just my .02 .....Get rid of Symantec !!
Click to expand...
Click to collapse
Symantec isn't really a choice on work PC.
Get yourself Comodo and save your money...
Click to expand...
Click to collapse
I'm sorry I can't give the link yet, but if you'll Google you'll see Comodo classifies shttp3.exe as "ApplicUnwnt.Win32.ServerWeb.SmallHTTP.~A" or "UnclassifiedMalware" (I guess depending on the version). A number of scanners find issues with shttp3.exe. I'm not saying it is infected, only that it is doing something suspicious.
Rick
Rick Tillery said:
Sorry, but as a noob, I can't post in that other thread.
It seems that the shttp3.exe in the LG Flash Package triggers Symantec's trojan detection. Some searching seems to indicate (assuming I'm reading all the cryptic virus sites correctly) that there is something to this, although it seems that different scanners find different trojans/viruses (can't post the link, but Google for "shttp3.exe" and "trojan"). I also found that the web site for this utility is blocked at work, because it's a "malicious site."
Has anyone seen this? Has anyone been able to verify/refute this?
Rick
Click to expand...
Click to collapse
shttp3.exe is in no way a virus. I've scanned with AVG and MalwareBytes Anti-Malware and they check out good.
Back to square one
OK, I seem to be stuck.
With paranoia in tow, I decided to take the long way back to stock. Unfortunately, when I tried to restore the backup of my stock image I made to SD card after installing CMR, the md5 checksum failed. I'm not sure what I can do about this.
So ok, I tried following the above link. The first step is to ensure the su binary is up-to-date. But when I tried this, I get a failure downloading the manifest. This is true for WiFi and HSPA+. I Googled and found a suggestion to delete the su binary. But that didn't help (I'm not sure how it would have helped anyway).
So back to the original question. Can I use the LG upgrade process to upgrade without going backwards (as you can see above, I can't) without bricking the phone? Can I start at step 3 in the link above and succeed?
Rick
The Dark Lestat said:
shttp3.exe is in no way a virus. I've scanned with AVG and MalwareBytes Anti-Malware and they check out good.
Click to expand...
Click to collapse
Thank you, sir. I hope it didn't seem accusing.
Rick
Rick Tillery said:
Thank you, sir. I hope it didn't seem accusing.
Rick
Click to expand...
Click to collapse
It's cool, my friend.
Sent from my Samsung Galaxy S II w/ CM9
Rick Tillery said:
OK, I seem to be stuck.
With paranoia in tow, I decided to take the long way back to stock. Unfortunately, when I tried to restore the backup of my stock image I made to SD card after installing CMR, the md5 checksum failed. I'm not sure what I can do about this.
So ok, I tried following the above link. The first step is to ensure the su binary is up-to-date. But when I tried this, I get a failure downloading the manifest. This is true for WiFi and HSPA+. I Googled and found a suggestion to delete the su binary. But that didn't help (I'm not sure how it would have helped anyway).
So back to the original question. Can I use the LG upgrade process to upgrade without going backwards (as you can see above, I can't) without bricking the phone? Can I start at step 3 in the link above and succeed?
Rick
Click to expand...
Click to collapse
Is it safe to ignore the su version update?
Short of this, can I override the MD5 checksum? I realize that image could be corrupt, but if I'm just going to replace it with the GB release, does that matter?
Rick
You should just put your phone in recovery mode and update through the tool
with your IMEI #. It will give you the latest update !
If you need some help on that I think Lestat or somebody has a write-up
on doing this.
Good luck,
Dwayne
dwaynedman said:
You should just put your phone in recovery mode and update through the tool
with your IMEI #. It will give you the latest update !
If you need some help on that I think Lestat or somebody has a write-up
on doing this.
Good luck,
Dwayne
Click to expand...
Click to collapse
Can you be a bit more specific?
1. By "recovery mode," do you mean into ClockworkMod Recovery, or I should revert to stock (I made a copy of it after I rooted the stock ROM, but before I installed CMR)?
2. By "the tool," do you mean the official LGMobile Software Update, or the LG Flash Package referenced in the link above?
3. By "latest update," do you mean the file directly from LG, or the copy (v20p) linked from the link above?
4. If the latter in both previous questions, which set of steps do I need to follow from the above link? Can I do only 3 (LG Flash Tool), or do I need to follow 1 (Recovery Manager), 2 (Returning to Stock), and 3?
My friend had a different LG phone, with ClockworkMod Recover and CM7 installed. He reverted the CM7 to stock, but did not replace CMR with the stock recovery. Then he used the official LG upgrade method and bricked his phone. I'm trying to avoid this.
Are you saying I don't have to worry about this on the LG Thrill 4G? Can I go straight from the current CMR+CM7 configuration to the LG GB release using the official LG process?
If you mean I should use a different process, can you point me to it? As I mentioned, I run into dead-ends using the method linked above. And I'm not even sure whether I should be doing steps 1, 2 and 3, or if I should just use step 3.
Any and all help is appreciated, but I guess I don't understand the shorthand you're using here, so if you could be a bit more specific, I wouldn't feel so lost.
Rick
Rick Tillery said:
Can you be a bit more specific?
1. By "recovery mode," do you mean into ClockworkMod Recovery, or I should revert to stock (I made a copy of it after I rooted the stock ROM, but before I installed CMR)?
2. By "the tool," do you mean the official LGMobile Software Update, or the LG Flash Package referenced in the link above?
3. By "latest update," do you mean the file directly from LG, or the copy (v20p) linked from the link above?
4. If the latter in both previous questions, which set of steps do I need to follow from the above link? Can I do only 3 (LG Flash Tool), or do I need to follow 1 (Recovery Manager), 2 (Returning to Stock), and 3?
My friend had a different LG phone, with ClockworkMod Recover and CM7 installed. He reverted the CM7 to stock, but did not replace CMR with the stock recovery. Then he used the official LG upgrade method and bricked his phone. I'm trying to avoid this.
Are you saying I don't have to worry about this on the LG Thrill 4G? Can I go straight from the current CMR+CM7 configuration to the LG GB release using the official LG process?
If you mean I should use a different process, can you point me to it? As I mentioned, I run into dead-ends using the method linked above. And I'm not even sure whether I should be doing steps 1, 2 and 3, or if I should just use step 3.
Any and all help is appreciated, but I guess I don't understand the shorthand you're using here, so if you could be a bit more specific, I wouldn't feel so lost.
Rick
Click to expand...
Click to collapse
Remove your battery and keep the phone unplugged
Launch the mobile updater tool
Hold the volume+ button plug the phone in and keep holding the volume+ till the computer downloads the drivers your phone is now in download mode
Once the phone is picked up go to customer support on the LG updater tool and click on recovery phone put your imie number in click check (make sure its the right model) an let the updater tool do its job. Once its done flashing launch into recovery volume- plus power plus 3D button do a complete wipe and factory reset and reboot your phone ... you'll lose cwm and root and be back to full stock
Sent from my LG-P925 using XDA
Bricked?
No joy. Following the steps, the upgrade stopped at 6%. Trying a number of times, it eventually forced me to exit the program (no more restarts). Rerunning the updater (and downloading the 420 MB image yet again on a VERY slow connection) I tried again and again, with different combinations of battery and plug order with power and volume buttons, but nothing worked. Checking elsewhere I found some issues had been reported with Windows Vista/7, so I tried on an XP machine. Now the "Start Updating" bar is red (it was always gray with W7). But now when I try to restore (or even update for that matter), it asks for my S/N (it never did that before) and then says it is "no longer able to upgrade." Reading around, it seems this is an indication of the device being bricked.
Rick
It sounds like you are very close to getting it working Rick.
My update did the same thing, looped over and over until it
finally kicked me out. Just plugging and unplugging the phone etc....
And when my update stuck at 6% the last time, i took my battery out and then in real quick and that seemed to work.
Does the phone still vibrate when you plug the usb cable into it while holding volume..? If it does then I highly doubt that your phone is bricked, just in a semi flashed state....No worries
Should Rick be trying to run LG Updater as administrator ? I didn't, but it might not hurt.
Regards & Luck,
Dwayne
http://forum.xda-developers.com/showthread.php?p=22417769
Have you tried this yet cause if you can get the LG logo to come up then you can reflash the phone and get it working send a pm to the dark lestat he may be able to team viewer you and help you out
Sent from my ****ty supported LG Thrill
dwaynedman said:
It sounds like you are very close to getting it working Rick.
Click to expand...
Click to collapse
I wouldn't have believed you early this morning, but now maybe...
My update did the same thing, looped over and over until it
finally kicked me out. Just plugging and unplugging the phone etc....
And when my update stuck at 6% the last time, i took my battery out and then in real quick and that seemed to work.
Click to expand...
Click to collapse
I tried a bunch of different combinations...none seemed to make the app happy. I finally punted Windows 7 and moved to an XP machine, only to get the "no longer able to update" message. At that point I assumed I was screwed (effectively bricked).
Does the phone still vibrate when you plug the usb cable into it while holding volume..? If it does then I highly doubt that your phone is bricked, just in a semi flashed state....No worries
Click to expand...
Click to collapse
It never really vibrated, but I was able to get back into CMR. Unfortunately NONE of my backups work at all. They all have MD5 checksum failures. I tried a trick I found online and got past that step, only to have it say a failure restoring /system. So much for CMR.
JReeher said:
http://forum.xda-developers.com/showthread.php?p=22417769
Have you tried this yet cause if you can get the LG logo to come up then you can reflash the phone and get it working send a pm to the dark lestat he may be able to team viewer you and help you out
Click to expand...
Click to collapse
Which step? As I mentioned above, I can't even get the first step of the first section (updating the su binary). And if I start at the 3rd section, Symantec prohibits me from using shttp3.exe (I tried to unquarantine it, but it gives a permission error, even as Administrator, when I try to run it), so I'll have to use a different machine.
I was able to reinstall the CM7 3/15 release, so that's something. I was going to restore the stock recovery backup I made, but even that doesn't seem to work. I'm having issue with backups :-(
Rick
i have never been able to restore a backup. i dont know why... but i have tried several times in several different instances.
---------- Post added at 11:56 AM ---------- Previous post was at 11:50 AM ----------
rick tillery, if you want to get your phone back to alive and well i'd suggest doing this:
http://forum.xda-developers.com/showthread.php?t=1558723&page=3
4th post i think

[q] 10.3.1.e.0.191

There any way to root my device? pretty new to this whole rooting thing. Tried using the Doomlord easy root kit. it pretty much laughed at me, and
said "C6606 <10.3.1.E.0.191> is not supported you need to manage to get remap_PFN_range address.
I've been at this for a while now, bout 2 hours of reading up on these things. Have a lame mans understanding of the basics. A very Lame mans. I've done nothing as of yet besides that root attempt. Makes me a bit nervous don't want to screw the phone.
Thanks in advance
Sorry if it's been asked excessively, but I could not seem to find it elsewhere.
Tragediya said:
There any way to root my device? pretty new to this whole rooting thing. Tried using the Doomlord easy root kit. it pretty much laughed at me, and
said "C6606 <10.3.1.E.0.191> is not supported you need to manage to get remap_PFN_range address.
I've been at this for a while now, bout 2 hours of reading up on these things. Have a lame mans understanding of the basics. A very Lame mans. I've done nothing as of yet besides that root attempt. Makes me a bit nervous don't want to screw the phone.
Thanks in advance
Sorry if it's been asked excessively, but I could not seem to find it elsewhere.
Click to expand...
Click to collapse
I have an idea that you should be able to use the ftf method (replace the kernel, root, and restore the stock kernel)...
Sent from my Xperia ZL using Tapatalk
Tragediya said:
There any way to root my device? pretty new to this whole rooting thing. Tried using the Doomlord easy root kit. it pretty much laughed at me, and
said "C6606 <10.3.1.E.0.191> is not supported you need to manage to get remap_PFN_range address.
I've been at this for a while now, bout 2 hours of reading up on these things. Have a lame mans understanding of the basics. A very Lame mans. I've done nothing as of yet besides that root attempt. Makes me a bit nervous don't want to screw the phone.
Thanks in advance
Sorry if it's been asked excessively, but I could not seem to find it elsewhere.
Click to expand...
Click to collapse
Can you try this rootkit (uses master key exploit)?
It works on 10.3.1.A.2.67, but no one checked if it works on .191
http://forum.xda-developers.com/showthread.php?t=2547714
RyokoN said:
Can you try this rootkit (uses master key exploit)?
It works on 10.3.1.A.2.67, but no one checked if it works on .191
http://forum.xda-developers.com/showthread.php?t=2547714
Click to expand...
Click to collapse
I tried it, didn't work.
vfxraven19 said:
I tried it, didn't work.
Click to expand...
Click to collapse
Hmmm...
So you should be able to use flashtool to flash the .423 kernel
Boot your phone with the .423 kernel installed and turn on dev mode and enabled usb debugging, and unknown sources under security and run the root... you're exploiting a flaw/bug in the .423 kernel to root your phone...
That will install su and then you can flash the .191 kernel (or even the .67 kernel) to get back to the latest kernel and have a rooted rom...
ok... so the root tool check's the firmware version... and when it finds the "191" firmware signature, it refuses to run... even if you're running a kernel combination that will work...
scifan said:
Hmmm...
So you should be able to use flashtool to flash the .423 kernel
Boot your phone with the .423 kernel installed and turn on dev mode and enabled usb debugging, and unknown sources under security and run the root... you're exploiting a flaw/bug in the .423 kernel to root your phone...
That will install su and then you can flash the .191 kernel (or even the .67 kernel) to get back to the latest kernel and have a rooted rom...
ok... so the root tool check's the firmware version... and when it finds the "191" firmware signature, it refuses to run... even if you're running a kernel combination that will work...
Click to expand...
Click to collapse
Like I wrote here,
there is no config to look for version.
Maybe Sony fixed bug 9950697 on .191.
The only clean way to root .191 is flashing old kernel and making prerooted.zip...
RyokoN said:
Like I wrote here,
there is no config to look for version.
Maybe Sony fixed bug 9950697 on .191.
The only clean way to root .191 is flashing old kernel and making prerooted.zip...
Click to expand...
Click to collapse
I could very well be wrong... I was putzing around with the .191 version to try and see if I could get wifi calling working for myself on my ZL... I flashed the 191 firmware with the 67 kernel... seemed to work somewhat... except there were some quirks... I'm flashing 67 again at this point so I can re-root and restore my nandroid.... *sigh*...
On the other hand I'd guess if you can live without wifi calling, you should be able to flash .67 on a t-mobile Z and then root using DoomLoRD's method....
(oh, and for what it's worth, the quirks I saw on my ZL included that the screen wouldn't turn off completely... and that the gyro seemed to not work quite right... but wifi calling worked great...
I think the version being detected is based on the build.prop... and you could very well be right that even with the old kernel loaded it wouldn't be vulnerable...
rooted with download.cnet.com/Kingo-Android-Root/3000-2094_4-75996768.html
i originally tried another method but it didnt work out in the end so afterwards i used the above method to root. but if it doesnt work then maybe what i did was important so the steps below is what i did for the method that didnt work. (if it works with just using kingo then WOOT otherwise. the below should help cause i have the same exact phone)
you should have your phone in developer mode and have usb debugging on
i used a flash tool from d-h.st/Kb8
switched my kernel to d-h.st/1Vz
rooted with download.cnet.com/Kingo-Android-Root/3000-2094_4-75996768.html
you do this by opening flash tool. letting it install. then selecting you device and flashmode drivers.
then connect your phone to computer via usb
then click the lighting bolt in the top right in the menu bar.
a window will pop up. press the flashmode radio button then ok
another window will pop up.
on the right side of the window it will ask if you wanna wipe types of info like cache, data, applogs. if you want you can click those if not leave them blank.
then at the top you will see a browse button to browse files (i think its a ... button)
use it to find the kernel
after you do that click the flash button and follow the instructions.
the instructions are "1 unplug the phone. 2 turn off phone. 3 enter flash mode by pressing and holding the down volume button (while off). 4 connect device (still off)"
once you plug the phone back in the flash tool will exit the window you were in and be doing its process in the terminal like window in the original window.
after you do that. unplug the device and reboot it. then exit flashtool (important) and then
use the kingo android root.
it should do some installing then ask you to connect device
then just follow those instructions in which i dont have up so i cant tell you hope i helped

Can't root GT-S5570

I'm a newb, so don't jump at me if the solution is simple.
I tried rooting my Mini(GT-S5570)using different threads around here, and none worked. I have tried booting into recovery mode and installed 5 different root packages, none worked. Superoneclick is unavailable(none of the download links worked, also tried googling for it, nothing). I'd like a tutorial that can work, since i'll add some infos below why it might not work.
I am running an android version made for vodafone germany, with 4 system apps that are vodafone only and can't be deleted
maybe the version number can help :
PDA: S5570BUKT2
Phone: S5570XWKT8
CSC: S5570VCRKT2
Edit: I want to go with the "flash cwm with odin" then flash rom, but Odin doesn't pick up the phone in download mode, only in upload mode(when I boot with volume up+home+power button). I installed Kies for drivers, so I don't see how I could've gone wrong
Same issue with my friend anyone can resolved this kind of problem?
What recovery do you have? What error you get when you're trying to install the packages?
tomi456 said:
What recovery do you have? What error you get when you're trying to install the packages?
Click to expand...
Click to collapse
I can't use any custom recovery since I don't have it rooted(it's the default one I think), and I am not getting any error whilist installing packages, the superuser icon is there, just it still says my phone doesn't have root permissions
If you have a 2.3.6 Android, then the attached files will root (pop) and unroot your phone to your will.
"Copy the pop_2.3.6.zip file to the root of your SD Card. Make sure you do not extract the contents of the zip file. Just copy the zip file to your SD Card.
Boot your phone into recovery. To do this, turn off your phone and press the OK button and Power button. You can release the buttons when you see the Samsung Logo to enter the recovery mode.
From the recovery menu, select “Apply update from SD Card” and choose the zip file you downloaded in step 1.
Flash the zip and then choose “Reboot system now” option.
After your phone reboots, check if you have the superuser Application installed"
Standard disclaimer applies I'm not responsible for anything anybody does using my advice (given to the best of my knowledge).
smolny2 said:
If you have a 2.3.6 Android, then the attached files will root (pop) and unroot your phone to your will.
"Copy the pop_2.3.6.zip file to the root of your SD Card. Make sure you do not extract the contents of the zip file. Just copy the zip file to your SD Card.
Boot your phone into recovery. To do this, turn off your phone and press the OK button and Power button. You can release the buttons when you see the Samsung Logo to enter the recovery mode.
From the recovery menu, select “Apply update from SD Card” and choose the zip file you downloaded in step 1.
Flash the zip and then choose “Reboot system now” option.
After your phone reboots, check if you have the superuser Application installed"
Standard disclaimer applies I'm not responsible for anything anybody does using my advice (given to the best of my knowledge).
Click to expand...
Click to collapse
Oh well. Tried it, the superuser icon is there, but multiple root checker apps say it's still not rooted. Any other ideas?
Extra(edit): I have wiped any data, restoring my phone before doing the steps you listed above
S1ckMike said:
Oh well. Tried it, the superuser icon is there, but multiple root checker apps say it's still not rooted. Any other ideas?
Extra(edit): I have wiped any data, restoring my phone before doing the steps you listed above
Click to expand...
Click to collapse
Open superuser app and let it update binaries. This needs internet access, but it SHOULD be fine after that.
Tapatalk-kal küldve az én GT-S5570-el
ast00 said:
Open superuser app and let it update binaries. This needs internet access, but it SHOULD be fine after that.
Tapatalk-kal küldve az én GT-S5570-el
Click to expand...
Click to collapse
I updated it from market, it still doesn't work... But you said to update binaries, is there anything different than what I did?
Oh btw when I enter the superuser app it says below the "elite not installed-get elite" Su binary not found" I think that could be one of the reasons :s
S1ckMike said:
I updated it from market, it still doesn't work... But you said to update binaries, is there anything different than what I did?
Oh btw when I enter the superuser app it says below the "elite not installed-get elite" Su binary not found" I think that could be one of the reasons :s
Click to expand...
Click to collapse
"After flashing the zip, make sure you connect to internet and then it'll ask you to update superuser app. Do so and then from within superuser app, update su binaries. Then, it should work without any issues"
Some more info:
http://androidsu.com/superuser/
https://play.google.com/store/apps/details?id=com.noshufou.android.su
I remember it was a bit tricky, still it seems your phone IS rooted (if you installed pop_2.3.6.zip from recovery). Updating supersu from market means the binary portion is not up-to-date, that's why IMO you have to update binaries. So click on the supersu icon, and find the "update binaries" option (needs internet connection).
If it fails, have a look at
https://play.google.com/store/apps/details?id=com.noshufou.android.su.fixer
Don't remember if I needed it or not with the pop_2.3.6.zip.
BTW, if your Mini is out of warranty period, why don't you put something bloatware-free on it? (with Odin)
I can highly recommend TassNewExperience v.10.1 final2,
or newer CM 7.2 clean of 18.05.2014.
Both shall (most probably) fix your problem with rooting, both are fast, stable, battery-friendly.
smolny2 said:
BTW, if your Mini is out of warranty period, why don't you put something bloatware-free on it? (with Odin)
I can highly recommend TassNewExperience v.10.1 final2,
or newer CM 7.2 clean of 18.05.2014.
Both shall (most probably) fix your problem with rooting, both are fast, stable, battery-friendly.
Click to expand...
Click to collapse
I want to go with odin, since I can't update the binary from updated app, and with original app verison an error(check for new version failed) prevents me from updating. Anyone can redirect me to a thread on how to flash with odin on my phone?
S1ckMike said:
I want to go with odin, since I can't update the binary from updated app, and with original app verison an error(check for new version failed) prevents me from updating. Anyone can redirect me to a thread on how to flash with odin on my phone?
Click to expand...
Click to collapse
Is your phone sim-locked for Vodafone network? If yes, go to Vodafone to remove sim-lock prior to anything.
Here is a decent ROM to start with (I've been using it for half a year):
http://forum.xda-developers.com/showthread.php?t=1648213
and there are working links in the second post, that I followed myself, explaining howto.
Here is a more detailed guide for flashing CWM recovery:
http://forum.xda-developers.com/showthread.php?t=1342190
IMHO you should put unbranded, stock Gingerbread ROM in your Mini before trying to flash CWM recovery.
Remember to make a backup of your data, my recommendation:
https://play.google.com/store/apps/details?id=com.idea.backup.smscontacts
and perhaps a "dump" backup of the partition holding IMEI of your MIni (you have to look for details - keywords efs and/or stl5).
smolny2 said:
Is your phone sim-locked for Vodafone network? If yes, go to Vodafone to remove sim-lock prior to anything.
Here is a decent ROM to start with (I've been using it for half a year):
http://forum.xda-developers.com/showthread.php?t=1648213
and there are working links in the second post, that I followed myself, explaining howto.
Here is a more detailed guide for flashing CWM recovery:
http://forum.xda-developers.com/showthread.php?t=1342190
IMHO you should put unbranded, stock Gingerbread ROM in your Mini before trying to flash CWM recovery.
Remember to make a backup of your data, my recommendation:
https://play.google.com/store/apps/details?id=com.idea.backup.smscontacts
and perhaps a "dump" backup of the partition holding IMEI of your MIni (you have to look for details - keywords efs and/or stl5).
Click to expand...
Click to collapse
I don't think it's simlocked, since I don't have a vodafone sim and it's working perfectly, and I'll try using your stuff
Edit: i've installed kies, and when I follow the guide, it doesn't get picked up by ODIN, and the pc says it malfunctioned(the usb device) Is this related to me having windows 8?
Edit 2: I would really like some real-time assistance through skype or whatnot, since i feel like i'm always doing something wrong...and when i'm following a guide, there's always a link that's broken, or a file that's outdated, not working etc
S1ckMike said:
I don't think it's simlocked, since I don't have a vodafone sim and it's working perfectly, and I'll try using your stuff
Edit: i've installed kies, and when I follow the guide, it doesn't get picked up by ODIN, and the pc says it malfunctioned(the usb device) Is this related to me having windows 8?
Click to expand...
Click to collapse
I used Odin in WinXP, have no experience with Win8 - only heard most of the older stuff didn't work in Win8. So you might be pioneering Odin in Win8
But there is another way of rooting Android devices, introduced last year, with a universal chinese soft. As the soft is new, could work in Win8 (it only roots the devices). Don't remember the name of it, there was a lot of info on the Net in the second half of last year. It worked for some no-name tablets of my friends.
smolny2 said:
I used Odin in WinXP, have no experience with Win8 - only heard most of the older stuff didn't work in Win8. So you might be pioneering Odin in Win8
But there is another way of rooting Android devices, introduced last year, with a universal chinese soft. As the soft is new, could work in Win8 (it only roots the devices). Don't remember the name of it, there was a lot of info on the Net in the second half of last year. It worked for some no-name tablets of my friends.
Click to expand...
Click to collapse
That didn't quite help me ... I guess I'll use another pc, but I'll have to wait for the school year to finish...If you find any other method that might work, make sure to post it here
S1ckMike said:
That didn't quite help me ... I guess I'll use another pc, but I'll have to wait for the school year to finish...If you find any other method that might work, make sure to post it here
Click to expand...
Click to collapse
Well, I'm not a pro in mobiles software - but having the info given in my last post, it's just a minute googling to find:
http://www.3ptechies.com/mobile/android/vroot-rooting-method-for-android.html
http://www.mgyun.com/en/GetVRoot
The orig. soft is in chinese, but used it without problems "the monkey way".
That gives you root - and nothing more (but should be enough to play with Android till the end of school
No help with Odin in Win8, sorry.
smolny2 said:
Well, I'm not a pro in mobiles software - but having the info given in my last post, it's just a minute googling to find:
http://www.3ptechies.com/mobile/android/vroot-rooting-method-for-android.html
http://www.mgyun.com/en/GetVRoot
The orig. soft is in chinese, but used it without problems "the monkey way".
That gives you root - and nothing more (but should be enough to play with Android till the end of school
No help with Odin in Win8, sorry.
Click to expand...
Click to collapse
Tried Vroot, says "root failed".
-_-......................................OH COME ON how can my phone be unbreakable like that? srsly it's starting to really piss me off
S1ckMike said:
Tried Vroot, says "root failed".
-_-......................................OH COME ON how can my phone be unbreakable like that? srsly it's starting to really piss me off
Click to expand...
Click to collapse
Weird. Perhaps (as above) it is in fact rooted. Try to unroot with unroot zip, and give a chance vroot again?
Unless there are some more residuals of previous attempts of rooting, and they interfere? Back to factory settings after unroot.
Or check which superuser u have on your Mini, and put binaries as zip from recovery? as in the first comment here:
http://androidsu.com/superuser/
And last but not least, it shouldn't be too difficult to put some old WinXP on an old disk/partition just to use Odin. And taking into account your first post "I tried rooting my Mini(GT-S5570)using different threads around here, and none worked", perhaps your Mini is so messed up that Odin is your only option?
Anyway, it's a mystery, and would really appreciate if you keep us informed of the progress.
smolny2 said:
Weird. Perhaps (as above) it is in fact rooted. Try to unroot with unroot zip, and give a chance vroot again?
Unless there are some more residuals of previous attempts of rooting, and they interfere? Back to factory settings after unroot.
Or check which superuser u have on your Mini, and put binaries as zip from recovery? as in the first comment here:
http://androidsu.com/superuser/
And last but not least, it shouldn't be too difficult to put some old WinXP on an old disk/partition just to use Odin. And taking into account your first post "I tried rooting my Mini(GT-S5570)using different threads around here, and none worked", perhaps your Mini is so messed up that Odin is your only option?
Anyway, it's a mystery, and would really appreciate if you keep us informed of the progress.
Click to expand...
Click to collapse
I installed kies for drivers and the phone still doesn't get picked up by odin... I would've gone with odin a long time ago if it worked...I'll try on another pc... Wish me luck
SRS One Click Root for Android
Galaxy_Rohit said:
SRS One Click Root for Android
Click to expand...
Click to collapse
Thanks bud but it gets stuck at "10:08:57 - Getting OffSets.. : 0x8003 0x8005 (False)"

Won't boot into recovery

Hello. I have unlocked bootloader successfully (it says "unlocked" at screen and also "tampered"). I have all the fastboot/adb software on my windows pc and can communicate with the phone. I flash recovery via fastboot and it is successful...includes a "recovery" option under bootloader options but it just flashes a disclaimer screen and quickly goes back to bootloader screen. Without custom recovery I cannot root this phone which is my goal. I have tried to reflash other recovery images, including cmw and twrp - I believe cmw is on it now but it won't open.
Hoping someone can assist me with this.
Thank you
belowHeights00 said:
Hello. I have unlocked bootloader successfully (it says "unlocked" at screen and also "tampered"). I have all the fastboot/adb software on my windows pc and can communicate with the phone. I flash recovery via fastboot and it is successful...includes a "recovery" option under bootloader options but it just flashes a disclaimer screen and quickly goes back to bootloader screen. Without custom recovery I cannot root this phone which is my goal. I have tried to reflash other recovery images, including cmw and twrp - I believe cmw is on it now but it won't open.
Hoping someone can assist me with this.
Thank you
Click to expand...
Click to collapse
Reflash whichever recovery you plan to use then remove the battery and put it back in then hold the volume down button and then press and hold the power button at the same time and the phone should then boot to recovery. Make a backup after so you have something to fall back on just in case.
MrMike2182 said:
Reflash whichever recovery you plan to use then remove the battery and put it back in then hold the volume down button and then press and hold the power button at the same time and the phone should then boot to recovery. Make a backup after so you have something to fall back on just in case.
Click to expand...
Click to collapse
Thanks for the reply! I just now gave that a shot but it had no effect.
belowHeights00 said:
Thanks for the reply! I just now gave that a shot but it had no effect.
Click to expand...
Click to collapse
Are you actually holding both buttons down at the same time until the screen turns on? Don't let them go hold them both down until your screen lights up. Then select recovery but if it doesn't work then try below.
Try flashing this version of twrp https://twrp.me/devices/htcdesire510usa32bit.html ... If you're not in the USA I need to know.
Flashing twrp didn't change anything unfortunately. I recently tried re-locking my bootloader and attempted to flash stock images back to the phone but when I press "yes" to the question about voiding the warranty before unlocking the bootloader again...the disclaimer just flashes and the phone won't let it.
Also, I cannot seem to restore it to stock through the menu...nor the bootloader screen.
So now I have "tampered" and "Relocked" banners on top of bootloader screen.
One the upside, the phone itself works fine (I currently only use it for wifi).
Only thing I can think of is I originally flashed a corrupt recovery img (or incompatible version).
Hoping you or someone else has any ideas as to how to get this thing working again. I'd be happy with reverting completly back to stock and starting the process over..
belowHeights00 said:
Flashing twrp didn't change anything unfortunately. I recently tried re-locking my bootloader and attempted to flash stock images back to the phone but when I press "yes" to the question about voiding the warranty before unlocking the bootloader again...the disclaimer just flashes and the phone won't let it.
Also, I cannot seem to restore it to stock through the menu...nor the bootloader screen.
So now I have "tampered" and "Relocked" banners on top of bootloader screen.
One the upside, the phone itself works fine (I currently only use it for wifi).
Only thing I can think of is I originally flashed a corrupt recovery img (or incompatible version).
Hoping you or someone else has any ideas as to how to get this thing working again. I'd be happy with reverting completly back to stock and starting the process over..
Click to expand...
Click to collapse
What service provider are you using?
Don't toss the unlock code you got from HTC you're gonna need the very first one you got keep it forever.
I'm using Boost but I think I figured it out. It ended up being a corrupt download of cmw. I actually used an ruu to get back stock and now the whole process went smoothly. Just looking for a rom that fits...got any recommendations in that area?
belowHeights00 said:
I'm using Boost but I think I figured it out. It ended up being a corrupt download of cmw. I actually used an ruu to get back stock and now the whole process went smoothly. Just looking for a rom that fits...got any recommendations in that area?
Click to expand...
Click to collapse
Not really since everyone has their own tastes but I'd advise you to create a backup in your recovery so you can use it in case something goes wrong. Currently me and a friend are working on CM13/12..
MrMike2182 said:
Not really since everyone has their own tastes but I'd advise you to create a backup in your recovery so you can use it in case something goes wrong. Currently me and a friend are working on CM13/12..
Click to expand...
Click to collapse
Funny enough I never made a backup before and constantly have to re-locate stock images due to soft bricking. I now am making backups so as not to go through that again.
I have a question perhaps you could answer -- if I install a rom that doesn't include any additional tweaks such as extended personaliation options in settings (transitions, etc, etc.)..is there a mod I can flash to achieve that?
belowHeights00 said:
Funny enough I never made a backup before and constantly have to re-locate stock images due to soft bricking. I now am making backups so as not to go through that again.
I have a question perhaps you could answer -- if I install a rom that doesn't include any additional tweaks such as extended personaliation options in settings (transitions, etc, etc.)..is there a mod I can flash to achieve that?
Click to expand...
Click to collapse
For extended personalizing other than developer options, I'd use Xposed.
MrMike2182 said:
Not really since everyone has their own tastes but I'd advise you to create a backup in your recovery so you can use it in case something goes wrong. Currently me and a friend are working on CM13/12..
Click to expand...
Click to collapse
How have you started working on that, i gthink i should join too. Are you working on the USA model or UK? (X86 or X64)
Zubagy said:
How have you started working on that, i gthink i should join too. Are you working on the USA model or UK? (X86 or X64)
Click to expand...
Click to collapse
The USA model because myself and rb don't have the EU phone to even test anything on it.. We still have a lot of booting problems right now. I'd say if you wanted to help I'd have to ask what you know about building roms from source? Have you done it before?
P.S: There's already a CM-12.1 available for the EU model although it does have some issues.. You should read about it if you want to try it..
MrMike2182 said:
The USA model because myself and rb don't have the EU phone to even test anything on it.. We still have a lot of booting problems right now. I'd say if you wanted to help I'd have to ask what you know about building roms from source? Have you done it before?
P.S: There's already a CM-12.1 available for the EU model although it does have some issues.. You should read about it if you want to try it..
Click to expand...
Click to collapse
Not really, But perhaps it time to learn
Zubagy said:
Not really, But perhaps it time to learn
Click to expand...
Click to collapse
It's pretty cool and fun once you get the hang of making things and seeing them function right, and the other thing is... You'll need a pretty decent computer to compile/build with and it'll need to have at least 4GB ram (more is better) and about 50 to 100 GB hard drive space for building your rom plus the CM source code needs to be on your system too...
MrMike2182 said:
It's pretty cool and fun once you get the hang of making things and seeing them function right, and the other thing is... You'll need a pretty decent computer to compile/build with and it'll need to have at least 4GB ram (more is better) and about 50 to 100 GB hard drive space for building your rom plus the CM source code needs to be on your system too...
Click to expand...
Click to collapse
I guess then am good to go, are those the only requirements....... i dont have any source code though
Zubagy said:
I guess then am good to go, are those the only requirements....... i dont have any source code though
Click to expand...
Click to collapse
Well how fast is your internet? By the way.. I'm using a Linux operating system... What are you using? It cannot be done on Windows unless you use a VM.
Hey, I also faced this problem but I find the solution and successfully flash twrp
Hey, I also faced this problem but I find the solution and successfully flash tarp recovery.
belowHeights00 said:
Hello. I have unlocked bootloader successfully (it says "unlocked" at screen and also "tampered"). I have all the fastboot/adb software on my windows pc and can communicate with the phone. I flash recovery via fastboot and it is successful...includes a "recovery" option under bootloader options but it just flashes a disclaimer screen and quickly goes back to bootloader screen. Without custom recovery I cannot root this phone which is my goal. I have tried to reflash other recovery images, including cmw and twrp - I believe cmw is on it now but it won't open.
Hoping someone can assist me with this.
Thank you
Click to expand...
Click to collapse
MrMike2182 said:
Well how fast is your internet? By the way.. I'm using a Linux operating system... What are you using? It cannot be done on Windows unless you use a VM.
Click to expand...
Click to collapse
Sorry for the delay, yes.... i am using vm ware... my net is not that fast... but it can get things done.

Categories

Resources