Related
I was trying to root and nand unlock my gfs phone and now Im at a point where usb and nothing is working. All i want do is go back to stock and make it like nothing happened. And no i dont have a nandroid backup. Im screwed. Please help.
i have the sd card error and usb error similar to here: http://forum.xda-developers.com/showthread.php?t=695243
but I cant get into adb because it says device not found.
when I connect USB it says error setting up new hardware in windows.
http://forum.xda-developers.com/showthread.php?t=695243
Sent from my PC36100 using XDA App
she's going to cut his..... SOMEBODY HELP HIM!!!!!
gatorran said:
she's going to cut his..... SOMEBODY HELP HIM!!!!!
Click to expand...
Click to collapse
Yes why is this so much more difficult compared to winmo?
[email protected] said:
http://forum.xda-developers.com/showthread.php?t=695243
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yes read above, I can't get into adb shell to do that. Thanks!
riotburn said:
Yes why is this so much more difficult compared to winmo?
Yes read above, I can't get into adb shell to do that. Thanks!
Click to expand...
Click to collapse
Was adb working for you before? You may need to install some drivers
yes it was. I need this fixed fast she just got it yesterday!, i rather like my testicles, kind of attached to them. I humbly accept all flaming and newbie calling.
riotburn said:
Yes why is this so much more difficult compared to winmo?
Yes read above, I can't get into adb shell to do that. Thanks!
Click to expand...
Click to collapse
so the first part of the commands using fastboot you don't do from adb shell. when you get the phone into fastboot, attach to your computer, you then open command prompt on computer and navigate directories until you are in the android sdk tools folder on your computer wherever it is (most people it is somewhere like c:/android-sdk-windows/tools/)
THEN you type
fastboot oem enableqxdm 0
fastboot reboot
Click to expand...
Click to collapse
no adb shell.
most people have installed adb in such a way that they can access it's tools from any directory. however, at least on my computer, fastboot commands will only work from within the android tools folder where fastboot is located.
hope this helps.
riotburn said:
yes it was. I need this fixed fast she just got it yesterday!, i rather like my testicles, kind of attached to them. I humbly accept all flaming and newbie calling.
Click to expand...
Click to collapse
Did you download the drivers??? they are not the same as the ones installed when you connect the phone....
yea also try pulling the battery and sometimes thats all it takes to get the use to be seen
then tell ur girl to mod the evo her self in case something like this happend my wife rooted and mods her's she love's to tinker
Lol at ruining your girlfriends phone. What tutorial were you following?
Sent from my HTC EVO via XDA App
i love how this is like, atleast the 4th thread someone has ruined there GFs evo due to inexperience, or the inability to read.
seriously, im not even trying to flame. i love reading this stuff.
its like general information for what NOT to do, for us that do read.
if you find the answer that works for you, mind mentioning said message?
i like to see threads that answer the questions at least, rather than have 10 suggestions, and no final response
Dam that sucks
Sent from my PC36100 using XDA App
how do i transfer the files for the second part of the usb is broken?
I was following the one that has pic by pic, and got to the point where pc36 wouldn't work. Saw that with the newest version this method wouldn't work. Went to the tutorial for that workaround and started following that. I think it got mixed up in there and thought i had nand unlocked it. Went to install the new radio, checked the system info and it wasnt the new one and started to get the problems.
Think it is rooted though because i get the # in adb shell.
How does one check to see if they did unlock nand, besides of the problem causing method i did?
I believe i ****ed up the custom recovery part. When I would load custom recovery it would flicker back and forth to the stock recovery, dont know if thats normal.
update: with more searching i found this http://forum.xda-developers.com/showpost.php?p=7136621&postcount=128 to use a update to fix the usb.
I did this and at least now it is charging, still not connecting to computer though it will charge through comp.
Can i flash back to the stock rom now? Will that fix it? How do i flash the stock rom?
Laughed at the thread title. Is the phone messed up, or the girlfriend? Gotta love misplaced modifiers.
If in fact you are rooted, you can use this method. It will put you back to "stock" with root and all the latest updates. If your computer wont mount your phone, you may have to get a micro sd card reader and plug it directly to your usb on your computer to download the files you need. Just make sure the phone is off or you unmount the sd in settings before you remove it. Or you can download them from your phone's browser, but you'll need a file manager to move the files to the root of your sd. If that wont work, your sd card might be corrupted.
http://forum.xda-developers.com/showthread.php?t=715915
dglowe343 said:
If in fact you are rooted, you can use this method. It will put you back to "stock" with root and all the latest updates. If your computer wont mount your phone, you may have to get a micro sd card reader and plug it directly to your usb on your computer to download the files you need. Just make sure the phone is off or you unmount the sd in settings before you remove it. Or you can download them from your phone's browser, but you'll need a file manager to move the files to the root of your sd. If that wont work, your sd card might be corrupted.
http://forum.xda-developers.com/showthread.php?t=715915
Click to expand...
Click to collapse
THANKS! I got it now. I had root but not nand so that prob f'ed it up. The link you sent me requires nand and has go do toasts method. I did that with no problems and had nand unlocked. So I installed the 2.0.... radio and freshevo with no problems. Thanks to everyone who helped, I will post in the first post what I did, at least what i can remember. I love xda, thanks so much guys.
I'm very happy to announce, that a developer raidzero from rootzwiki forum, has made us a fully working recovery for Samsung Galaxy w i8150!
You can download it from here:
DOWNLOAD
TEMPORARY LINK .... USE THIS IF FIRST ONE DOESN'T WORK
THANKS TO andynroid FOR PROVIDING LINKS!
Flashing recovery is very simple, all you need is root access on your phone, and adb on computer. You just copy downloaded recovery on internal sdcard. Then disconect phone from copmuter. Make sure that USB debugging is on. Now connect it again but don't connect phone memory (computer shouldn't see sdcard and internal memory in Windows explorer), open command prompt and got directory where adb is installed, now enter this:
Code:
adb shell
$su
#dd if=/sdcard/RZR-2.1.4-ancora-rec.img of=/dev/block/mmcblk0p13
This is all. Now turn off phone and turnd it on like this: hold Volume Up + Home + Power button, when Samsung sign appears relese power button but still hold other two, until recovery is loaded. Bamm you are in, and ready to flash something, or backup ! Expolre the recovery, it has a lot of options, you can even choose what color of menus you want .
I would like to thanks raidzero again for all his effort he made! And also big thanks to arco68,for much need informations he provided!
We can now expect, that when developing his recovery and adding new goodies, this recovery will follow others!
great news!! Thanks for your effort!
Has anyone had a chance to test the Recovery?
Will this work on the Samsung Exhibit II?
thanks mate.downloading now. just in case it needs to be recovered. after this we would see custom roms developed by our developers here..
klingel_One said:
great news!! Thanks for your effort!
Has anyone had a chance to test the Recovery?
Click to expand...
Click to collapse
I've tested it and it works
radgoos said:
Will this work on the Samsung Exhibit II?
Click to expand...
Click to collapse
I wouldn't bet that this will work on Exibith II cause every phone has different partitions.
after giving me the command you said to me reacts to: permission denied.. Whi?
lipanz said:
thanks mate.downloading now. just in case it needs to be recovered. after this we would see custom roms developed by our developers here..
Click to expand...
Click to collapse
Definitely...BTW can anyone adv us the rooting method Odin or....
can you show me a screen when you give the command adb?
when I try to restart the device in recovery restarts continuously and never give me the recovery menu
qzem said:
I'm very happy to announce, that a developer raidzero from rootzwiki forum, has made us a fully working recovery for Samsung Galaxy w i8150!
You can download it from here:
www.rzdroid.com/ftp/recovery/gingerbread/2.1.4/RZR-2.1.4-ancora-rec.img
Flashing recovery is very simple, all you need is root access on your phone, and adb on computer. You just copy downloaded recovery on internal sdcard. Then disconect phone from copmuter. Make sure that USB debugging is on. Now connect it again but don't connect phone memory (computer shouldn't see sdcard and internal memory in Windows explorer), open command prompt and got directory where adb is installed, now enter this:
Code:
adb shell
$su
#dd if=/sdcard/RZR-2.1.4-ancora-rec.img of=/dev/block/mmcblk0p13
This is all. Now turn off phone and turnd it on like this: hold Volume Up + Home + Power button, when Samsung sign appears relese power button but still hold other two, until recovery is loaded. Bamm you are in, and ready to flash something, or backup ! Expolre the recovery, it has a lot of options, you can even choose what color of menus you want .
I would like to thanks raidzero again for all his effort he made! And also big thanks to arco68,for much need informations he provided!
We can now expect, that when developing his recovery and adding new goodies, this recovery will follow others!
Click to expand...
Click to collapse
Thanks again, will try this ASAP, just a few questions:
Is /dev/block/mmcblk0p13 the Recovery partition??
Is it been overwritten by the dd if.......of??
Should the original stock recovery?? be backed-up/saved first??
Is there an MD5 or anything to check file integrity:
This could be used on the Device: Android File Verifier
Can the procedure be done using Terminal Emulator on the phone?
Do I need to have stock ROM for it to work?
snake873 said:
after giving me the command you said to me reacts to: permission denied.. Whi?
Click to expand...
Click to collapse
There are two possible reasons for this either you didn't run su command first, or you don't have rooted phone.
irishpancake said:
Thanks again, will try this ASAP, just a few questions:
Is /dev/block/mmcblk0p13 the Recovery partition??
Is it been overwritten by the dd if.......of??
Should the original stock recovery?? be backed-up/saved first??
Is there an MD5 or anything to check file integrity:
This could be used on the Device: Android File Verifier
Can the procedure be done using Terminal Emulator on the phone?
Click to expand...
Click to collapse
1. Yes /dev/block/mmcblk0p13 is recovery partition
2. It is gonna be overwritten with costum one.
3. You can back it up that you reverse dd command. Or I can upload original recovery.
4. There isn't MD5 cause noone made it , you only need MD5 file if you would like to flash this via Odin.
nakTT said:
Do I need to have stock ROM for it to work?
Click to expand...
Click to collapse
Do you know any custom rom for our phone ? But no it is not rom related.
snake873 said:
can you show me a screen when you give the command adb?
when I try to restart the device in recovery restarts continuously and never give me the recovery menu
Click to expand...
Click to collapse
What screen? From computer or phone? Your phone need to be turned on and booted in android when running dd command.
qzem said:
There are two possible reasons for this either you didn't run su command first, or you don't have rooted phone.
1. Yes /dev/block/mmcblk0p13 is recovery partition
2. It is gonna be overwritten with costum one.
3. You can back it up that you reverse dd command. Or I can upload original recovery.
4. There isn't MD5 cause noone made it , you only need MD5 file if you would like to flash this via Odin.
Do you know any custom rom for our phone ? But no it is not rom related.
What screen? From computer or phone? Your phone need to be turned on and booted in android when running dd command.
Click to expand...
Click to collapse
From computer
---------- Post added at 12:09 PM ---------- Previous post was at 11:41 AM ----------
ahahaha ok ok I did thank you very much for your patience
qzem......top marks for your persistence
qzem said:
There are two possible reasons for this either you didn't run su command first, or you don't have rooted phone.
1. Yes /dev/block/mmcblk0p13 is recovery partition
2. It is gonna be overwritten with costum one.
3. You can back it up that you reverse dd command. Or I can upload original recovery.
4. There isn't MD5 cause noone made it , you only need MD5 file if you would like to flash this via Odin.
Click to expand...
Click to collapse
Thanks, gotta learn ODIN first,
btw, thanks for the ODIN d/l........installed it, but still unsure how to proceed???
I have latest Kies installed on my laptop, any reason why you do not use it?? It appears to allow back-ups and restores, also new firmware d/l.
As I am new to Samsung, and also ODIN, but does using ODIN have advantages over Kies, and is it safer to upgrade new f/w with ODIN or Kies, do you lose root, or anything else??
BTW, on the MD5 thing, for the RZR-2.1.4-ancora-rec.img
I used MD5 Checksum Tool from http://www.novirusthanks.org/product/md5-checksum-tool/
to generate the MD5.
File: RZR-2.1.4-ancora-rec.img
Size: 5230592 bytes
Publisher: Unknown
Checksum (MD5): 3b9cc641aa898910b5bad911bd38f675
*File generated by MD5 Checksum Tool*
http://www.novirusthanks.org
Click to expand...
Click to collapse
I just think it is good security practice to check file integrity before applying on your device, as many things can happen, like data corruption, while transferring file from download on Laptop to SD card, and best to check file on device SD or Internal Storage with AFV against MD5 generated at source.........
which I did not check at source, but I am just illustrating for example!!
[BTW, lots of MD5's on rzdroid.com recovery ftp site, here, but not sure of our .img file
The above MD5 is what I got from the d/l file
Thanks again, I saw your stuff with raidzero on rootzwiki.........
top marks for your persistence, and a good result for all i8150 owners.
irishpancake said:
Thanks, gotta learn ODIN first,
btw, thanks for the ODIN d/l........installed it, but still unsure how to proceed???
I have latest Kies installed on my laptop, any reason why you do not use it?? It appears to allow back-ups and restores, also new firmware d/l.
As I am new to Samsung, and also ODIN, but does using ODIN have advantages over Kies, and is it safer to upgrade new f/w with ODIN or Kies, do you lose root, or anything else??
BTW, on the MD5 thing, for the RZR-2.1.4-ancora-rec.img
I used MD5 Checksum Tool from http://www.novirusthanks.org/product/md5-checksum-tool/
to generate the MD5.
I just think it is good security practice to check file integrity before applying on your device, as many things can happen, like data corruption, while transferring file from download on Laptop to SD card, and best to check file on device SD or Internal Storage with AFV against MD5 generated at source.........
which I did not check at source, but I am just illustrating for example!!
[BTW, lots of MD5's on rzdroid.com recovery ftp site, here, but not sure of our .img file
The above MD5 is what I got from the d/l file
Thanks again, I saw your stuff with raidzero on rootzwiki.........
top marks for your persistence, and a good result for all i8150 owners.
Click to expand...
Click to collapse
Well I really don't know that is better to use Kies or Odin. If you want official and (what is supposed to be tested) firmware, tha you better use Kies (but well even with kies your phone could get bricked, I've learned that from one user here ). If you want to flash latest firmware, which sometimes is not availible on all the countries, and you can't get it from Kies fast enaught, than I suggest odin is the choice. I prefere Odin, cause I don't like official stuff .
To use Odin is very simple. You need to turn on phone with Volume Down + Home + Power. When you are prompt (on hte phone),wether to conutioue od cancle, you connect phone and computer with USB cable, and choose contuinu, now you are in download mode. Then all you have to do, to choos proper .ops file (button OPS) in odin, an proper firmware (usually you choos that under One Package button, if you have one package in tar.md5), then you wait for chekcking md5. When is checked you just click Start, and wait for stuff to happen.
Don't forget that there is a possabiltiy that something might go wrong with flashing, but it is not that big one. I suggest, that you first made full nandorid backup with recovery, if something goes wrong, you can boot you phone in recovery and restore it totaly. And one more suggestin when flashing, do it with latop(if possible), so that you have battery and power cable plugged in laptop, if electricyty goes out, that you still have battery to run laptop.
And thanks for the support you guys are showing to me, since I'm not a developer. I try really hard, to get people that are willing to help us developing better roms for our phone !
qzem said:
There are two possible reasons for this either you
Do you know any custom rom for our phone ? But no it is not rom related.
Click to expand...
Click to collapse
Spot on. I just need to know if it is ROM related (that I need a ROM file on my PC).
Thanks for the reply.
Hey there, just a noob question:
Where are adb drivers installed? I'm working under Windows 7.
I tried to google this and ended up here /developer.android.com/sdk/index.html
and downloaded the first two files, but I'm unsure what to do now. Thanks in advance!
Hey qzem,
Am I right, that the adb driver should be installed, when i first installed Kies?
Is your Guide How-To Install the recovery also working on my mac? I think so, or am I wrong?
Perhaps you already figured by now, I'm new to Android!
There is one more thing i can't seem to figure out:
In foreseeable future, there are hopefully some nice custom roms for the Galaxy W. Do I have to install recovery everytime i flash a new Rom? Or is it like a bios, that has nothing to do with the actual Android System?
Thanks for your help in advance
fender90 said:
Hey there, just a noob question:
Where are adb drivers installed? I'm working under Windows 7.
I tried to google this and ended up here /developer.android.com/sdk/index.html
and downloaded the first two files, but I'm unsure what to do now. Thanks in advance!
Click to expand...
Click to collapse
For adb, you need to download Android SDK from here. Download zip file and extract it somwhere. Than go in folder where you have extract it and run SDK Manager, from there you will install adb rivers and everything else. When you are done (it could take a while, to download and install everything), open Command promnt and follow the instrucions I've wrote in first post.
klingel_One said:
Hey qzem,
Am I right, that the adb driver should be installed, when i first installed Kies?
Is your Guide How-To Install the recovery also working on my mac? I think so, or am I wrong?
Perhaps you already figured by now, I'm new to Android!
There is one more thing i can't seem to figure out:
In foreseeable future, there are hopefully some nice custom roms for the Galaxy W. Do I have to install recovery everytime i flash a new Rom? Or is it like a bios, that has nothing to do with the actual Android System?
Thanks for your help in advance
Click to expand...
Click to collapse
The same goes for mac users, there is also Android SDK for mac. You can install Kies before this, but you need both because kies includes drivers for this phone exactly. As far as recoverey goes, if it is not included in ROM, which you flash, I think you'll need to install it again. I hope that developers will include recovery in their roms.
Thanks so far qzem,
It seems like theres someone in your Cyanogenom-Forum-Post qzem, who is trying and willing to help making a custom rom. But he seeks for som guidance!
Perhaps someone with experience like, arco can take him under his wings!
Hi there,
i would like to thank you. Everything works like a charm.
Did the flash, tried the recovery.. and uaaaahhhh....
...i forgot to backup the original recovery!
can someone please, please upload it to somewhere??
thx.
Zetup-EXe
I was in the process of replacing framework-res.apk and missed the step of changing the permissions before replacing it. I found several threads on how to unbrick the phone by flashing a new ROM but I was hoping I can somehow fix the permissions on the framework file and be done. I installed adb and I already had the LG USB drivers installed but when I run adb devices it doesn't list anything. Windows 7 shows "LG AndroidNet Phone" and a removable disk under "Safely Remove Hardware" so I think I have the right drivers.
Is there hope that I can fix the file permissions?
BTW, I'm a newb so I may be missing something. And also scared of having to flash a ROM
I need help.
do you have CWM in the phone ? if so boot into that and run adb devices and see if it finds it their
No, I don't. Other than using DooMLoRD zergrush to root the phone a few months ago, I have not messed with anything else.
gabcon73 said:
No, I don't. Other than using DooMLoRD zergrush to root the phone a few months ago, I have not messed with anything else.
Click to expand...
Click to collapse
unless your phone will boot normaly to the home screen or you have CWM on it you will haveto flash the koren rom theirs no way to get it into recovery that i know of ... have you tryed a factory reset ?
I replied to you at another thread, so I'll repeat here.
What you need to do is re-root while it's looping. It might take you 100 tries before it succeed , but eventually it should succeed.
After that you can try fix the permissions, but if the new .apk file is not copied successfully first time it might get you in boot loop again, so I'd recommend at that point push the .apk again and then change the permissions.
I found that zergrush dated 2011-10-21 has more chances to succeed, because it has more retries before it gives up, the new version tries only few times and gives up too quickly.
I've attached the root I was using with 3 versions of zergrush.
Open CMD window and execute root.bat, let it copy all needed files to the phone. If it fails, try execute loop.bat, it will just execute zergrush indefinitely , so you can go do other stuff. You can check if root succeeded by opening another CMD window and type: adb shell
then, if it shows sign "$" type su, if it shows "#" you are good to go.
P.S.
This method only works with AT$T stock rom, if you are on LU6200 you are probably out of luck, as their root requires wifi and user interaction...
Having CWM is very handy in such situations, not only because you can restore backups, but because you'll have root access.
Thanks [email protected], I'll give it a try. And yes, I have the stock ROM.
I'm having problems downloading root.zip, I've tried two computers and different browsers, it only downloads 554 bytes.
Yeah, for some reason it was downloading 404 page...
I reuploaded it.
I let the loop.bat run overnight without success so I decided to call AT&T and have it replaced under warranty. The new phone arrived today and I've been busy reinstalling and reconfiguring. I may install CWM just so I can easily recover from a backup in case I do some other stupid thing to the phone.
Thanks guys
I politely ask any person able to help to explain to me, like I am a three year old, exactly how to update a Samsung Glide from 4.0.4 to whatever newer version is able to work on the phone, that is rooted? AGAIN... I ask this politely.
Allmystical1 said:
I politely ask any person able to help to explain to me, like I am a three year old, exactly how to update a Samsung Glide from 4.0.4 to whatever newer version is able to work on the phone, that is rooted? AGAIN... I ask this politely.
Click to expand...
Click to collapse
No problem, we are all new at this once, right?
First Step: Downloads!
TWRP:
http://dualhoki.vim.hu/bubor/dev/twrp-i927/twrp-2.8.4-for_odin.tar.md5
ROM:
Here is a matter of preference. If you want the latest *working* version, you can upgrade to 5.0, but you lose the camera. I presume you want the camera to work, so I suggest Bubor's CM11 for KitKat. There are other good roms too, like PAC and SediRom, but we will start with Bubor's CM11.
http://dualhoki.vim.hu/bubor/dev/11.0/cm-11-20160126-UNOFFICIAL-i927.zip
http://dualhoki.vim.hu/bubor/dev/11.0/cm-11-20160126-UNOFFICIAL-i927.zip.md5sum
ODIN:
http://www.mediafire.com/download/7us5q44aab1xl9d/Odin304.zip
Second Step: Prepare.
I am presuming that you are using a Windows computer. If you are using a Linux computer, I can tell you what to do also, but these instructions are for Windows. I am also presuming that you have an external SD card in your phone, if you do not, go buy one and put it in your phone.
Unzip the Odin304.zip by right clicking on it and say unzip/extract, etc. If your Windows does not have this option, you need to download a program like winzip or 7zip so you can unzip this file. If you need those programs, they can be googled and downloaded.
Third step: Further preparation.
Turn on your phone and plug it into a usb cord and plug the usb cord into your computer. If you are using Windows, it will try to find drivers for the phone. It should be automatic and just work. If it does not, then you need the drivers, which are here:
http://www.mediafire.com/download/0up21ccc9gajwjv/Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
*If you downloaded this file, just double click it like a program, it should open and install drivers for your phone. Do not do this unless your computer cannot find drivers for your phone!
Fourth step: Charge your phone.
Plug in your phone and FULLY charge it. ALL the way to 100% CHARGED. No exceptions. No shortcuts. Do it. Then UNPLUG YOUR PHONE AND TURN IT OFF.
Fifth step: Put TWRP on your phone.
a. Your phone should now be unplugged and off. Open the ODIN folder that you unzipped earlier and double click on ODIN to open the program.
b. Click on the PDA button ( you and I both know that your phone is not a PDA, this is not a typo ) and it will open a browser. Find the twrp-2.8.4-for_odin.tar.md5 file and select it. It should now fill in the blank line next to PDA with this info.
c. WHILE HOLDING THE UP VOLUME BUTTON ON YOUR PHONE, press and hold the power button. When you see "SAMSUNG" you can release the power button, but KEEP HOLDING THE UP BUTTON, untill you see a yellow triangle and warning notice. If you hold too long, that is okay as it will take you straight to the download mode with the green android that says "ODIN" at the top and "Downloading" in the middle. If you got stopped at the yellow warning/triangle, press up again to go to download mode.
d. Plug your phone into the usb, and the usb into your computer.
e. In the Odin program, press start.
You should now see a serries of verbage going by on the left, at the top a green bar may fill in, and hopefully, in the end it says "success" or "pass". Your phone should reboot all by itself. If ODIN says fail, ask for further instructions. If passed, close Odin.
Sixth step: Put your CM11 files on your phone.
Your phone should have rebooted and looks just like it did before, now powered on, and in your stock Ice Cream Sandwich firmware. As with any file transfer, plug your USB into the phone and computer. Drag the CM11 files to the phone. Anywhere will do, but if you have an external SD card in your phone, I recommend you put it there.
Seventh Step: Boot into TWRP.
a. Turn off your phone.
b. Unplug the USB.
c. HOLD THE DOWN VOLUME BUTTON and press the POWER BUTTON. When you see "Samsung" release the POWER BUTTON, but keep holding the VOLUME DOWN BUTTON. At the top of the screen, white letters should say something like "entering recovery".
d. When you see "Team Win Recovery Project" release the down volume button.
Eighth step: Make a backup!
a. Press "Backup" button on screen.
b. Check all checkboxes (system, cache, data, boot, Android Secure)
c. Press "Storage: sdcard (xxxx mb)" bar.
d. Select "External_sd" to choose to backup to your external sd card.
e. Slide the swipe bar to the right to backup. This will take a few minutes, with progress bar.
NOTE: if the screen dims, when you touch it, you will see a TWRP lock icon, swipe right to unlock it.
f. When backup is completed, it will say "reboot system", do not click that. Click the "home" icon in the lower left corner.
g. Click the "Wipe" button.
h. Swipe right to factory reset.
i. Click the "home" icon in the lower left corner.
j. Click the "install" button.
k. At the top, click on the "Storage: sdcard (xxxx mb)" bar.
l. Select "External_sd"
m. choose the cm-11-20160126-UNOFFICIAL-i927.zip
n. When that is done, click on the "reboot system" button.
The system will reboot. You should now see CM11's boot screen. The first boot takes a bit of time.
Ninth step: Thank Bubor.
a. Log into XDA.
b. Go to http://forum.xda-developers.com/captivate-glide/development/dev-cm-11-0-t2802184
c. Slap every thanks button that is for a post by Bubor untill it tells you that you cannot slap any more thanks buttons (that is only 8 thanks per day).
Tenth step: Enjoy your phone!
....I think you know how to do that.....
If you have ANY questions, please just post them here and we will see if we can answer them.
I am thanking you so very much! Also... I do apologize for such a time lapse in my reply. Life happened.
I followed the above procedure and have CM11 installed. But my problem is I can't use my SIM card anymore because it's like my phone doesn't see it at all. I checked my settings and saw that I no longer had an IMEI number. I used the restore feature and the stock ROM had an IMEI number. What should I do? I saw a few threads about using a program to rewrite the IMEI or others to copy the file containing the IMEI but I wasn't really sure what I should do or how to copy files to and from that partition from my computer. I should add that the phone is unlocked.
tr3sie7e said:
I followed the above procedure and have CM11 installed. But my problem is I can't use my SIM card anymore because it's like my phone doesn't see it at all. I checked my settings and saw that I no longer had an IMEI number. I used the restore feature and the stock ROM had an IMEI number. What should I do? I saw a few threads about using a program to rewrite the IMEI or others to copy the file containing the IMEI but I wasn't really sure what I should do or how to copy files to and from that partition from my computer. I should add that the phone is unlocked.
Click to expand...
Click to collapse
Great question, and an interesting problem!
First, I am really glad that you followed the instructions and made a backup! It is good to know that you can always go back to the way it was.
I recommend that you download another rom from the developer section here, such as Sedi-rom, omni-rom, etc., and try flashing that. If you flash one of those roms, does your IMEI stay for those roms?
Try this one: http://forum.xda-developers.com/showthread.php?t=2789727
You can do steps 7 through 10 with any of the roms in the developer thread. If this other rom works, you can use it, or download others and try them. If the SediRom does not work also, then we will need to sit down and figure this out.
I really appreciate the fact that you're here to help.
I downloaded and installed SediRom 2.1.2 and my IMEI still shows as "Unknown." However this time I should add there is a serial number, which I don't believe was present in CM11 or in the stock ROM, although I'm not sure if that's at all significant. I made an external backup of the efs file from the stock ROM, is there some way I could just reinstall CM11 and replace/overwrite the efs to give it an IMEI number? I'd really like to use CM11 if possible, I was enamored by how good it looked and how functional it was, especially since the last time I tried CM a long time ago I didn't have such a good opinion of it. Plus the bootloader is friggin sweet !
I recently got the phone unlocked off eBay, so I don't know its past history but I was able to access the network when I had the SIM card in prior to initially installing CM11 but not afterwards. I'm trying to use a T-Mobile SIM but like I said I was able to successfully access the network prior to installing CM11. But the IMEI doesn't show at all regardless if the SIM is in at all.
Is there some kind of different hardware/firmware like in a newer slightly different version of the phone that came out resulting in compatibility issues? I'm not the most experienced but I've dipped by toes in this before, so I would be willing to go the extra mile if it meant I could get CM11 to work, because honestly it looked like everything I could ever want from this phone with a good looking theme too...
Do you have a full backup of the efs partition?
If so it should be enough to restore it.
Sent from my LG-H815 using XDA Labs
xdajog said:
Do you have a full backup of the efs partition?
If so it should be enough to restore it.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Yes I believe so. I used the procedure from this thread to back it up. I tried copying the efs directly over using the built in file manager with root access, but when I try to copy the entire efs folder over I get a non-descriptive error "this operation has failed." I tried copying the nv_data.bin folder by itself to overwrite the one currently there (which copied successfully), then rebooted the phone but the IMEI still shows as "unknown." Do I need to copy the efs while the phone is in recovery mode or via PC or something because of file in-use errors or something else I don't know about?
tr3sie7e said:
Yes I believe so. I used the procedure from this thread to back it up. I tried copying the efs directly over using the built in file manager with root access, but when I try to copy the entire efs folder over I get a non-descriptive error "this operation has failed." I tried copying the nv_data.bin folder by itself to overwrite the one currently there (which copied successfully), then rebooted the phone but the IMEI still shows as "unknown." Do I need to copy the efs while the phone is in recovery mode or via PC or something because of file in-use errors or something else I don't know about?
Click to expand...
Click to collapse
Well restoring efs have to be done in recovery only! Do not try to do this while android is running!!
To be honest the absolute best way is having a dd partition dump of the whole partition. When you have followed the mentioned guide do you have used also dd like this?
dd if=/dev/block/mmcblk0p1 of=/storage/external_SD/efs.img
I don't know if copying the efs folder alone would work.. better is restoring the whole partition if possible. Do you have such kind of backup?
Sent from my LG-H815 using XDA Labs
Hi there,
Many thanks for this great post! I am going through the steps and when I press Start in Odin3 v3.04, I get this message
<OSM> twrp-2.8.4-for_odin.tar.md5 is invalid.
Please help.
Many thanks in advance!
Andrew
azwindsor said:
Hi there,
Many thanks for this great post! I am going through the steps and when I press Start in Odin3 v3.04, I get this message
<OSM> twrp-2.8.4-for_odin.tar.md5 is invalid.
Please help.
Many thanks in advance!
Andrew
Click to expand...
Click to collapse
try to rename to recovery.tar.md5
try older version, and flash the latest from recovery.
azwindsor said:
Hi there,
Many thanks for this great post! I am going through the steps and when I press Start in Odin3 v3.04, I get this message
<OSM> twrp-2.8.4-for_odin.tar.md5 is invalid.
Please help.
Many thanks in advance!
Andrew
Click to expand...
Click to collapse
Redownload. Maybe the file you had downloaded gets corrupted or is incomplete ..
.
Sent from my LG-H815 using XDA Labs
bubor said:
try to rename to recovery.tar.md5
try older version, and flash the latest from recovery.
Click to expand...
Click to collapse
Many thanks bubor! Renaming worked like a charm.
FYI, I tried re-downloading it, but that didn't seem to work yesterday.
I really appreciate all of your work, everything is working great.
Thanks for the quick responses.
All the best!
So I'm really late here but the phone got thrown to the backburner and I forgot about it. Lol but anyways, I created the EFS backups using dd like it said, but I'm not sure how to restore them? Do I unpack them and then use ADB to move them there? I'm kind of confused. Also, for some reason going through the TWRP to the stock ROM doesn't let me root it, it crashes every time I get to that screen, don't know if that's important to the operation. Hope I can finally get this stupid thing working right with the custom ROM...
tr3sie7e said:
So I'm really late here but the phone got thrown to the backburner and I forgot about it. Lol but anyways, I created the EFS backups using dd like it said, but I'm not sure how to restore them? Do I unpack them and then use ADB to move them there? I'm kind of confused. Also, for some reason going through the TWRP to the stock ROM doesn't let me root it, it crashes every time I get to that screen, don't know if that's important to the operation. Hope I can finally get this stupid thing working right with the custom ROM...
Click to expand...
Click to collapse
Check my faq here:
http://forum.xda-developers.com/showthread.php?t=2789727&p=54075993
Scroll down to restore efs.
.
Okay so I used TWRP to do a factory restore, flashed SuperUser, then flashed CM11, went into TWRP and did the terminal commands you listed in the guide for backing up the EFS... to no avail. Would it be better to copy the EFS while I'm still on the rooted stock ROM using a terminal app? I don't understand what the problem is...
tr3sie7e said:
Okay so I used TWRP to do a factory restore, flashed SuperUser, then flashed CM11, went into TWRP and did the terminal commands you listed in the guide for backing up the EFS... to no avail. Would it be better to copy the EFS while I'm still on the rooted stock ROM using a terminal app? I don't understand what the problem is...
Click to expand...
Click to collapse
Please paste the output of the results. Doing this in twrp is the correct way.
Today, my phone got bricked after I installed Magisk, am i am looking for a way of sorting it out. The phone was running Android 9 DP3 when rooted, and I was following HighOnAndroids root guide on Youtube for reference,
I unlocked my bootloader and successfully installed TWRP. After this, I installed Magisk, which went throuygh perfectly fine. However, after rebooting the phone, I am stuck on the google splash screen, with a small progress bar that stays for the duration of the time on this screen. After about 2 minutes, the phone reboots into TWRP again.
Does anyone know how I could return to stock Android or at least escape this issue?
Many thanks
James
Jameswebb97 said:
Today, my phone got bricked after I installed Magisk, am i am looking for a way of sorting it out. The phone was running Android 9 DP3 when rooted, and I was following HighOnAndroids root guide on Youtube for reference,
I unlocked my bootloader and successfully installed TWRP. After this, I installed Magisk, which went throuygh perfectly fine. However, after rebooting the phone, I am stuck on the google splash screen, with a small progress bar that stays for the duration of the time on this screen. After about 2 minutes, the phone reboots into TWRP again.
Does anyone know how I could return to stock Android or at least escape this issue?
Many thanks
James
Click to expand...
Click to collapse
Use duces script to flash June google factory image.
jlokos said:
Use duces script to flash June google factory image.
Click to expand...
Click to collapse
I followed the guide on the DeucesScript XDA page but the command window keeps saying "'fastboot' is not recognized as an internal or external command, operable program or batch file."
Jameswebb97 said:
I followed the guide on the DeucesScript XDA page but the command window keeps saying "'fastboot' is not recognized as an internal or external command, operable program or batch file."
Click to expand...
Click to collapse
You need this information (the stuff I made bold + the hyperlink):
Code:
If you are having issues with this script:
Download the latest fastboot and adb Platform Tools UPDATED Dec. 22, 2017!!! This is the most common problem!!!
Download/Update Google USB Drivers
Video: Force-Installing the Android USB Drivers Fastboot & ADB
[B]Verify you have the [URL="https://wiki.lineageos.org/adb_fastboot_guide.html"]environment variable (path)[/URL] set for adb and fastboot[/B]
Try a different USB port
Try a different cable
Format Userdata in Stock Recovery
Try to boot stock before doing mods like Locking Bootloader / Kernel / TWRP / Magisk
Jameswebb97 said:
I followed the guide on the DeucesScript XDA page but the command window keeps saying "'fastboot' is not recognized as an internal or external command, operable program or batch file."
Click to expand...
Click to collapse
umph....hate to tell you, but you have a long way to go...
so before going on this "journey", I would suggest you booting into TWRP again, and try installing (not adb sideloading, just in case you're doing that) Magisk again. Also, be sure you are using the latest (might be considered "beta") 16.4 for taimen... I'm thinking your boot.img or dtbo.img simply may have gotten glitchy and repatching (by installing Magisk again) might fix it...
Also, if you want to go a step further, you might want to consider using the official Magisk uninstaller. Since Magisk makes a copy of your stock boot and dtbo image, it may put that back so you can get it in working order to get into the system (although without root), and then figure things out and/or reinstall Magisk (through TWRP is best) while all things Magisk was removed...
Good luck and hope this helps....
Make sure you are trying to open from the correct location, and put .\fastboot
EvilDobe said:
You need this information (the stuff I made bold + the hyperlink):
Code:
If you are having issues with this script:
Download the latest fastboot and adb Platform Tools UPDATED Dec. 22, 2017!!! This is the most common problem!!!
Download/Update Google USB Drivers
Video: Force-Installing the Android USB Drivers Fastboot & ADB
[B]Verify you have the [URL="https://wiki.lineageos.org/adb_fastboot_guide.html"]environment variable (path)[/URL] set for adb and fastboot[/B]
Try a different USB port
Try a different cable
Format Userdata in Stock Recovery
Try to boot stock before doing mods like Locking Bootloader / Kernel / TWRP / Magisk
Click to expand...
Click to collapse
Ive tried all of this now, i got the script working, but now the phne says it is corrupt and i cannot get into recovery. Is this game over do you think?
simplepinoi177 said:
umph....hate to tell you, but you have a long way to go...
so before going on this "journey", I would suggest you booting into TWRP again, and try installing (not adb sideloading, just in case you're doing that) Magisk again. Also, be sure you are using the latest (might be considered "beta") 16.4 for taimen... I'm thinking your boot.img or dtbo.img simply may have gotten glitchy and repatching (by installing Magisk again) might fix it...
Also, if you want to go a step further, you might want to consider using the official Magisk uninstaller. Since Magisk makes a copy of your stock boot and dtbo image, it may put that back so you can get it in working order to get into the system (although without root), and then figure things out and/or reinstall Magisk (through TWRP is best) while all things Magisk was removed...
Good luck and hope this helps....
Click to expand...
Click to collapse
This is good advice, thanks. i have a new problem (ugh), where i got the script working through changing the paths, but now the phone says that it is corrupt and i cannot access TWRP. Game over?
Jameswebb97 said:
Ive tried all of this now, i got the script working, but now the phne says it is corrupt and i cannot get into recovery. Is this game over do you think?
Click to expand...
Click to collapse
With the unlocked bootloader it'll always say the device is corrupt. Manually put the device into the bootloader & flash the DeucesScript. You're basically starting over at this point but it is possible to get up & going again.
Jameswebb97 said:
This is good advice, thanks. i have a new problem (ugh), where i got the script working through changing the paths, but now the phone says that it is corrupt and i cannot access TWRP. Game over?
Click to expand...
Click to collapse
EvilDobe said:
With the unlocked bootloader it'll always say the device is corrupt. Manually put the device into the bootloader & flash the DeucesScript. You're basically starting over at this point but it is possible to get up & going again.
Click to expand...
Click to collapse
EvilDobe might be right...but I have a bit to offer before maybe starting all over...
I doubt you needed to edit the script and "change the paths." Most likely you merely did not have the images (you extracted from the .zip of the Full Factory image you got from the Google Developers site) inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders.
In any case, I suggest you get the TWRP image file [.img] (NOT the installer .zip necessarily), put the .img file "... inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders." (I've seen some users simply cut and paste those 2 .exe files only to the extracted folder -- this is why I state it this way) Then, power down your device. After it's off, hold down the Volume Down button and press & hold the Power button (this is the manual way to get into the Bootloader Mode). Once there, plug your phone into your computer (USB-A to USB-C would be best) and open a command prompt/powershell ("run as administrator" or with administrative priveleges) and direct it to the platform-tools folder (i.e. if I put it on my desktop, it would be "C:\Users\MyName\Desktop\platform-tools"), you can temporarily boot into TWRP via command
Code:
fastboot boot twrp-3.2.1-2-taimen.img
When in TWRP (hopefully), I suggest trying to do what I advised before -- try either Magisk installer to repatch the boot and dtbo image, or Magisk Uninstaller to attempt to replace your boot and dtbo to stock.
*NOTE: Of course, this is assuming you are running Microsoft Windows (if not, you will need to input .\ as @naiku suggested) and also the whole "device is corrupt" is due to "funky" boot image issues. If not, I/we can guide you to flashing the Full Factory back onto the phone (hopefully without losing data and settings)...
Good luck and hope this helps...
simplepinoi177 said:
EvilDobe might be right...but I have a bit to offer before maybe starting all over...
I doubt you needed to edit the script and "change the paths." Most likely you merely did not have the images (you extracted from the .zip of the Full Factory image you got from the Google Developers site) inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders.
In any case, I suggest you get the TWRP image file [.img] (NOT the installer .zip necessarily), put the .img file "... inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders." (I've seen some users simply cut and paste those 2 .exe files only to the extracted folder -- this is why I state it this way) Then, power down your device. After it's off, hold down the Volume Down button and press & hold the Power button (this is the manual way to get into the Bootloader Mode). Once there, plug your phone into your computer (USB-A to USB-C would be best) and open a command prompt/powershell ("run as administrator" or with administrative priveleges) and direct it to the platform-tools folder (i.e. if I put it on my desktop, it would be "C:\Users\MyName\Desktop\platform-tools"), you can temporarily boot into TWRP via command
Code:
fastboot boot twrp-3.2.1-2-taimen.img
When in TWRP (hopefully), I suggest trying to do what I advised before -- try either Magisk installer to repatch the boot and dtbo image, or Magisk Uninstaller to attempt to replace your boot and dtbo to stock.
*NOTE: Of course, this is assuming you are running Microsoft Windows (if not, you will need to input .\ as @naiku suggested) and also the whole "device is corrupt" is due to "funky" boot image issues. If not, I/we can guide you to flashing the Full Factory back onto the phone (hopefully without losing data and settings)...
Good luck and hope this helps...
Click to expand...
Click to collapse
Pleased to be editing this comment; managed to get it working following your step by step. Think i'm going to stay away from rooting something this expensive in the future! Thanks so much!
Jameswebb97 said:
Pleased to be editing this comment; managed to get it working following your step by step. Think i'm going to stay away from rooting something this expensive in the future! Thanks so much!
Click to expand...
Click to collapse
I wouldn't go that far with staying away. When I come across people IRL that want to start doing this stuff I always tell them to read the instructions, step through them, read the instructions again, ask questions (as you did here) BEFORE you get started, read the instructions again, and only when you're confident start messing with your device. This is a fun, and at times stressful, hobby. It's great when everything goes according to plan but it's an omg omg omg omg omg omg moment when you mess something up.
Start with baby steps. The straight upgrade to P is fairly simple provided your device is unlocked. Get that working & you'll be set. I have root on my DP3 & the only thing I've done so far is delete some apps from system that I know I don't want/need. If your main goal is to just enjoy your phone, test out Android P, and maybe go back... root isn't needed. Once everything is squared away & you're running for a day or so you can always fastboot to recovery, make a backup, and then try to add root. I hope you don't shy away & get deeper into the hobby. It truly starts to get fun when you begin to understand more of what is going on.
Jameswebb97 said:
Pleased to be editing this comment; managed to get it working following your step by step. Think i'm going to stay away from rooting something this expensive in the future! Thanks so much!
Click to expand...
Click to collapse
Hey I'm so glad you got it working! Leave me a "Thanks!" would make it up to me ... I'm always happy to help out and get things figured out...yet I don't get the satisfaction of knowing if it does end up helping a lot of the time because a good number don't come back with their experience...so thanks for that! Glad you got it going...
EvilDobe said:
I wouldn't go that far with staying away. When I come across people IRL that want to start doing this stuff I always tell them to read the instructions, step through them, read the instructions again, ask questions (as you did here) BEFORE you get started, read the instructions again, and only when you're confident start messing with your device. This is a fun, and at times stressful, hobby. It's great when everything goes according to plan but it's an omg omg omg omg omg omg moment when you mess something up.
Start with baby steps. The straight upgrade to P is fairly simple provided your device is unlocked. Get that working & you'll be set. I have root on my DP3 & the only thing I've done so far is delete some apps from system that I know I don't want/need. If your main goal is to just enjoy your phone, test out Android P, and maybe go back... root isn't needed. Once everything is squared away & you're running for a day or so you can always fastboot to recovery, make a backup, and then try to add root. I hope you don't shy away & get deeper into the hobby. It truly starts to get fun when you begin to understand more of what is going on.
Click to expand...
Click to collapse
And it's as @EvilDobe means.....
I remember back in the days of the Motorola Droids (OG Droid1, Droid 3, & Droid 4) where you could really mess things up and come out with a big ol' "brick" "paperweight" as there were many instances where you could not come back from (i.e. updating to a certain point, then attempting to downgrade when Google/Motorola/Verizon put blocks that breaks it). But this isn't the case these days. @Jameswebb97, at least with the Pixel 2's, Oreo and/or P(Android OS 9), it's actually more difficult than easy to get that too far gone. The only reason why I can help so many troubleshooting their issues is because I, myself, have wrecked my current device in some serious ways! So I can relate and have experience in helping in the same situations. I've gotten it to where it says "device is corrupt," (which isn't all that uncommon), BUT with the added desperate troubleshooting where I had to wipe/erase, changing partition types, format several partitions, even go about "resizing" the partition to match the "target extraction size" of the Full Factory flash, and even as far as learning to manually flash the various system partitions and that there are two (system_a & system_b) but, in Google's infinite wisdom(?), one flashes to system_a and the other to system_other!!! And I haven't even started on reading others' issues when going after the Slot A and Slot B complications -- I didn't even attempt to touch this in that troubleshooting story.
My point is: I think I've broken my device farther than most people and got it so close to the brink, and yet I was able to bring it back and am still using that same device today (most people would usually, at that point, go and get a RMA replacement). Honestly, as long as you have access to Bootloader Mode (which Google, in their infinite wisdom, seems to have placed it in the main board memory or separate memory rather than storage as to make it always accessible which makes it hard to "lose"), you have a really good (seemingly perfect) "safety net" in which you can always flash back to a working, stock state -- which is why it's the best policy to just make good backups before experimenting so, if anything, you get back to this state and restore all your data. I'm not trying to convince you to root or to try custom ROMs or anything -- even though there are many great reasons and capabilities of rooting -- I am simply appealingl to your sense of curiosity and reassure you so you aren't held back and you don't restrict and limit yourself if you don't want to, but are to fearful to experiment.
I hope you don't take this post as "lecturing" or anything, just some thoughts I hope you consider...
Glad it worked out in the end for you!