Is a sad day for me...i didn't knew about the Hardware Lock of Vibrants and i rooted and applied lag fix to my phone. After this i just updated the phone via Kies to JI6 then when phone rebooted got stucked after the second stage of booting with a blank screen. I tried many methods of get into Recovery or Download to flash again but can't because of Hardware Lock. Anyone knows if my problem have a solution?? Im very sad plz help.
Have you tried holding volume down and power until it boots?
Sent from my T-Mobile G2 using XDA App
Yah....Nothing!!
Try all methods:
http://forum.xda-developers.com/showthread.php?t=771247
I think you may need to use ADB commands to force it to reboot into download.
You may need to do method #4.
You may want to keep adb up and keep typing 'adb devices' to see if it sees the device when you try these different methods. If so - reboot into recovery from that.
You should be able to get into DL mode. Do you have ADB on your computer? If not, get it. Put it on the root of your C:\ and than make sure you get the drivers installed on your PC. Get ODIN and have it open. When that is done, connect your phone to your PC and boot it up. Open a cmd prompt (if you are in windows 7 you may need to open as admin) and navigate to C:\ (or where ever you decided to put ADB). At the command prompt type this exactly minus the parenthesis: "adb reboot download" Should shoot you right into DL mode. At that point you will need to flash a new ROM via ODIN, so make sure you read up.
Hope this works/helps.
I tried all that but cant get into recovery or download mode, my phone is not stuked on vibrant logo it just go to the second logo and then blank screen. Fabrication date is 08-10.
Hello there,
Well, my Galaxy S 2, after uninstalling a program, got an error (black screen, need to restart...) and so doesn't start anymore (freezes at "Samsung Galaxy S II" screen) or enter in recovery mode (freezes with the robot on background, without letters). I have the download mode yet.
I tried to flash a rom with odin, but it freezes at "NAND write start" process (I've waited 30 min), and I have to abort disconecting the phone.
Could anyone help me?
Thanks
You get into the download mode. That's good. The flashing fails. That's not good.
We need more info to help you. The fact that you had some error and now cannot flash some firmware does not really help us. At least me...
Here are some questions I have:
What firmware did you try to flash?
What Operating System are you using?
Do you have KIES installed?
or
Where do you got the drivers from?
Did ODIN work in the past or did you never use it before?
Sent from my GT-I9100 using XDA App
Thank you for answering.
I've never flashed any firmware before on this phone (it has the original one). I tried to flash the stock XXKI1, using just the PDA field. So, Odin still at "NAND write start" part.
As I said, I had an error after uninstalling an app (launcher error), that I've forced to remove the battery. After that, the phone didn't start anymore (freeze at "Samsung Galaxy SII" screen), and I can't enter in recovery mode.
I don't have Kies installed (got the drivers separated).
Sorry that it took me so long to answer you.
If you still have the problem, I'll try my best to guide you through the process of restoring your device.
What do you want to install on your device?
-A stock rom
-A customrom based on TouchWiz
-CyanogenMod
-MIUI
Just let me know and I'll help you asap.
A stock rom...
Okay, where do you live? Or more accurate, what language do you want to use later?
Your first step is to get the "Heimdall Suite" up and running on your PC.
Download it from their homepage. Extract it somewhere where you can easily find it later. Then you'll need to install the drivers.
Put your phone into download-mode and plug it in. If they aren't installed yet, Windows will now start the installation. When completed, open the "drivers"-folder in the Heimdall folder. Run "zDiag" as administrator.
Enable the show all devices option and select either "Samsung USB composite device" or "Gadget serial" (depending on what's available in your dropdown-list). Install the driver and ignore the warning from Windows (install it anyway).
Now that everything is set up, your first step is to get the ".pit" file for your device. I'll check whether yours is valid. Open the Heimdall frontend as administrator and go into the last tab. Click on detect device and, if your device gets detected, click on print pit. If you get errors in the output, disconnect your phone, shut it down and enter download-mode again. Retry.
Please post the output here.
Sent from my GT-I9100 using XDA App
I have bought a second-hand Galaxy Tab which will not keep changes in settings or any uploaded files or IDs after switch off and restart.
This means I cannot root it, as any uploaded files with Odin are lost on restart.
Can anyone help me please? I have tried all the usual resets to no avail.
FG
No-one interested in a tricky problem challenge???
ForeignGadger said:
I have bought a second-hand Galaxy Tab which will not keep changes in settings or any uploaded files or IDs after switch off and restart.
This means I cannot root it, as any uploaded files with Odin are lost on restart.
Can anyone help me please? I have tried all the usual resets to no avail.
FG
Click to expand...
Click to collapse
Hmm, I thought this might intrigue the experts, but to no avail.
Where the hell do I go for an answer to this problem: rooting cannot be done as flashed files will be lost on reboot.
ForeignGadger said:
Hmm, I thought this might intrigue the experts, but to no avail.
Where the hell do I go for an answer to this problem: rooting cannot be done as flashed files will be lost on reboot.
Click to expand...
Click to collapse
Hmm have you really odined and see the files replaced? Can you boot into recovery do a full wipe and odin a stock or custom rom
Sent from my GT-P7510 using Tapatalk
animatechnica said:
Hmm have you really odined and see the files replaced? Can you boot into recovery do a full wipe and odin a stock or custom rom
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
Hi. Thanks for getting back.
I have gone up and down the forums for ideas. (for over 3 days now).
The story so far:
I have tried to flash the overcome .tar file for my model using odin 1.83, but get a red box and a Fail! : error 0X140005. I followed the Overcome guide VERY carefully, got the yellow COM box, put the right file in the right box, but when I hit the start button, it fails.
I can boot into "Download". I have tried restore after wiping the cache.
With normal power up, the OS seems to work partially, in that I can do all the things I want to do, but all the settings, WiFi passwords, uploaded files etc disappear on reboot, and any uninstalled programmes re-appear. It seems that it won't permanently write to, or erase from, "long term" memory.
Before this,I have done a full cache wipe and factory restore but no difference.
Thoughts:
a) I am wondering if a previous occupant has tinkered with it and messed up the memory partitions? is it all RAM?
b) As it is stuck, it is stuck with USB debugging disabled. this will be maintained on reboot: could this interfere with Odin?
Any suggestions would be very, very gratefully accepted.
FG
ForeignGadger said:
Hi. Thanks for getting back.
I have gone up and down the forums for ideas. (for over 3 days now).
The story so far:
I have tried to flash the overcome .tar file for my model using odin 1.83, but get a red box and a Fail! : error 0X140005. I followed the Overcome guide VERY carefully, got the yellow COM box, put the right file in the right box, but when I hit the start button, it fails.
I can boot into "Download". I have tried restore after wiping the cache.
With normal power up, the OS seems to work partially, in that I can do all the things I want to do, but all the settings, WiFi passwords, uploaded files etc disappear on reboot, and any uninstalled programmes re-appear. It seems that it won't permanently write to, or erase from, "long term" memory.
Before this,I have done a full cache wipe and factory restore but no difference.
Thoughts:
a) I am wondering if a previous occupant has tinkered with it and messed up the memory partitions? is it all RAM?
b) As it is stuck, it is stuck with USB debugging disabled. this will be maintained on reboot: could this interfere with Odin?
Any suggestions would be very, very gratefully accepted.
FG
Click to expand...
Click to collapse
Dude i ask this in another forum you posted, did you use odin to install recovery or not? if you did then just boot into recovery and wipe all - then flash galaxytab or any flashable roms that way.
Sent from my GT-P7510 using Tapatalk
As I said in the second paragraph: I tried to use odin to install recovery, but got the big red square. The file did not transfer.
ForeignGadger said:
As I said in the second paragraph: I tried to use odin to install recovery, but got the big red square. The file did not transfer.
Click to expand...
Click to collapse
No your second paragraph said you flashed overcome. Not recovery
So if odin is not installing recovery can you boot into fastboot? Power off then press power n volume down then go to fastboot mode and install recovery that way. Check this thread for info. . http://www.galaxytabforums.net/forum/galaxy-tab-10-1-general-discussions/1044-my-galaxy-tab-10-1-wont-power-up.html
Then flash a cwm flashable ROM
Sent from my GT-P7510 using Tapatalk
OK, thanks for the steer and your patience. I'll get to work.
I'll report back (eventually!).
(Please remember that there is an awful lot of jargon and TLA's to learn for us newcomers, even if willing).
Regards, FG
ForeignGadger said:
OK, thanks for the steer and your patience. I'll get to work.
I'll report back (eventually!).
(Please remember that there is an awful lot of jargon and TLA's to learn for us newcomers, even if willing).
Regards, FG
Click to expand...
Click to collapse
Lol i hear you i was there too
Sent from my GT-P7510 using Tapatalk
animatechnica said:
Lol i hear you i was there too
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
hi again; well no success so far.
- I downloaded and installed SDK (software development kit: for other noobs like me)
- I downloaded and installed recovery.img, and installed the google USB drivers from the extras
- I checked that the fastboot.exe, adb.exe (android debug bridge) and recovery.img were all in the platform tools folder.
- got into "download":- odin mode
- plugged in the tab and tried to launch "adb start-server" from cmd screen
(I was in the right directory at the command line), but no cigar: nada.
- I went back and did the PDAnet routine, but still no joy, no devices shown
there were no error messages either, which made me think the usb was not communicating with the tab.
To try this out I used Kies to transfer a photo file to the tab, and viewed on the tab it after disconnecting, so tranfers do take place.
Sure enough, after rebooting, the file was gone, like all the other settings and changes made in the past.
I also tried adb when the tablet was on and I had checked usb debugging. In this case, adb recognised the device and returned the serial number.
It does not do this when in cwm mode as it will not remember to keep debugging on when I power down.
Any other ideas anyone? can I switch debugging on from the command line before I try to recover?
FG, (now getting a sore head and worrying if I have p***d my money up the wall.)
Funny, when things get really tough, the helpers disappear.
Still no solution.
Oh dear: silence again.
ForeignGadger said:
- got into "download":- odin mode
- plugged in the tab and tried to launch "adb start-server" from cmd screen
(I was in the right directory at the command line), but no cigar: nada.
- I went back and did the PDAnet routine, but still no joy, no devices shown
there were no error messages either, which made me think the usb was not communicating with the tab.
To try this out I used Kies to transfer a photo file to the tab, and viewed on the tab it after disconnecting, so tranfers do take place.
Sure enough, after rebooting, the file was gone, like all the other settings and changes made in the past.
I also tried adb when the tablet was on and I had checked usb debugging. In this case, adb recognised the device and returned the serial number.
It does not do this when in cwm mode as it will not remember to keep debugging on when I power down.
Any other ideas anyone? can I switch debugging on from the command line before I try to recover?
FG, (now getting a sore head and worrying if I have p***d my money up the wall.)
Click to expand...
Click to collapse
AFAIK you won't get a response in ADB when the tablet is in download mode but you should when the tablet is in CWM recovery mode.
If it were me I'd odin a stock factory recovery to the device and a stock factory rom for it. Then i'd boot into stock recovery and do the factory reset to see if that cleans things up. You should probably link to the source of the files you're downloading as well as provide specific model of your device so people can verify that you're flashing the right files.
I'm totally confused by your steps here
you went to odin mode and used adb? or did you go into fastboot and adb the recovery?
step by step here
a quick overview of it is to get your tab into ODIN mode and use ODIN to reload a copy of the stock image to your tab. This erases all of your previous data but you can reinstall those later. But at least it gets you back to a working tab - Note this is for the 7510 - the wifi tab
1) Download this file - MEGAUPLOAD - The leading online storage and file delivery service
2) extract the file
you should have the following
a file called GT-P7510_USB_Driver_v1_3_2360_0-Escape - this file is the USB driver for your PC, if you don't have the driver installed already, run this
a folder named Odin3 v1.85 - this contains the ODIN executable file
a folder named KME Odin - which contains 2 files - android_fastboot_emmc_full_p4_16G_32G.pit" and a "P7510XABKME_P7510UEKME_HOME.tar"
3) Power down the tab
4) press POWER and Volume Down at the same time until it powers up and you should see 2 logos - USB and triangle (note the retail wifi version might show 2 different logos, android on right and bag on left - left is recovery and right is Odin/download)
5) press volume down to move the selection to the triangle (or the icon on the right)
6) press volume up to lock in selection. You are now in ODIN/download mode
assuming all your drivers are installed to your PC, plug in the tab via the USB to your PC
run the ODIN executable
only Auto-reboot and F.reset Time should be ticked
after a minute, the ID:Com box should turn yellow -if not you may have driver issues (try this driver http://drivers.softpedia.com/progDo...SB-Driver-for-Windows-x86-Download-96692.html)
7) tick PDA and click the PDA button and navigate to the KME Odin folder and select "P7510XABKME_P7510UEKME_HOME.tar"
8) select the PIT button and navigate to the KME Odin folder and select the "android_fastboot_emmc_full_p4_16G_32G.pit"
9) Select START
it should start writing the image to your tab and once done, should reboot you back into stock
in case you want to go ahead and flash 3.2 -
use this pit file - http://forum.xda-developers.com/attachment.php?attachmentid=784889&d=1321486916
and use this for the PDA http://hotfile.com/dl/135008863/06c...EKMM_P7510XABKMM_P7510UEKMM.rar.html?expire=1
if it asks you for Password for the 3,2 file use : sampro.pl
when resorting to odin and first booting up, you might get asked for a password, the way around this is to
a) power off,
b) press power n volume down until you get 2 icons left is recovery right is download.
c) press volume down to select recovery icon then volume up to lock it, you should then see the recovery menu
d) then use volume buttons until wipe data/factory reset is highlighted press power to do it
e)after its done wiping, select reboot n you should be ready
Now the key thing here is installing the right drivers - after installing teh driver, connect the tab and see if the drivers are installed - go to your pc control panel and check if you get a triangle with an exclamation point. If there is, right click on it and select update driver, then manually choose device - navigate through and find the Android or samsung device (cant remember the name off the top of my head)
if you get stuck, report on which part you got stuck on - currently it seems like you're mixing and matching different steps so it is a little confusing
ForeignGadger said:
hi again; well no success so far.
- I downloaded and installed SDK (software development kit: for other noobs like me)
- I downloaded and installed recovery.img, and installed the google USB drivers from the extras
- I checked that the fastboot.exe, adb.exe (android debug bridge) and recovery.img were all in the platform tools folder.
- got into "download":- odin mode
- plugged in the tab and tried to launch "adb start-server" from cmd screen
(I was in the right directory at the command line), but no cigar: nada.
- I went back and did the PDAnet routine, but still no joy, no devices shown
there were no error messages either, which made me think the usb was not communicating with the tab.
To try this out I used Kies to transfer a photo file to the tab, and viewed on the tab it after disconnecting, so tranfers do take place.
Sure enough, after rebooting, the file was gone, like all the other settings and changes made in the past.
I also tried adb when the tablet was on and I had checked usb debugging. In this case, adb recognised the device and returned the serial number.
It does not do this when in cwm mode as it will not remember to keep debugging on when I power down.
Any other ideas anyone? can I switch debugging on from the command line before I try to recover?
FG, (now getting a sore head and worrying if I have p***d my money up the wall.)
Click to expand...
Click to collapse
Hi again, sorry to confuse you but I was following your suggestions in post #7 of this thread. when I got to step 5 of that post, I got no response from the device: installed PDAnet to get over the driver issue. and no joy.
When trying to install .tar or PIT files I get a big red box, even though the yellow COM box looks good.
When trying the data erase/ factory reset option in the "Download" mode, I get the error message "Can't access to /system/csc/XEU/system.
Steps 7/8/9 in your post above do not work: I have tried them a few times.
Sorry, I have run out of options, and thank you for your help.
I have a blind N10 on bootloader that is it doesnt show anything on fastboot mode but it does go there. I researched and found other people with similar problem http://rootzwiki.com/topic/37629-bootloader-fastboot-weirdness/ . However they managed to unlock the device by clicking the vol+ once and then power key as I also saw on youtube videos. IT WORKED. and then it went downhill. it got stuck on bootloop. SO i tried to go into fastboot again and it went and then pressed vol+ twice to go into recovery and there was a android with "!" red sign on middle.
and of course it won't boot. So I tried to use the Wugs toolkit, put it on back to stock with bootloop option. and it started to do its work, but got stuck at the sending bootloader (1280KB) sign for more than 10-15 mins. I pressed the power button and it failed that step saying too many links and wugs kit continued the process got stuck again and then completed and my device still goes to fastboot, but cant go into recovery anymore I think as it shows blank screen. Please mind that I am still blind on the screen and nothing comes. my only way of knowing it goes to fastboot is through cmd line. PLEASE HELP, dont wanna brick this.
Is there any way to ODIN it. I cant find online any ODIN insturctions? help help
I cant even turn it off now! Its always going to fastboot. Please help
mustafansu said:
I cant even turn it off now! Its always going to fastboot. Please help
Click to expand...
Click to collapse
I think that's a good thing, if you can get to Fastboot then I would say to forget about the toolkits and just download the latest Google MantaRay image from here https://dl.google.com/dl/android/aosp/mantaray-jwr66y-factory-3d8252dd.tgz
Make sure your Android SDK is updated, unzip the downloaded file once and copy the contents to your Fastboot folder, shift/right click inside your fastboot folder and select "open command window here" then type "fastboot devices" and make sure your device id is shown, after that just type in your cmd window "flash-all.bat" and let it do its magic. If everything goes well by the time it completes you will have a factory restored Nexus10 and then you can start the hacking all over again.
Good Luck! and remember when in doubt, just ask.
Erik
ricco333 said:
I think that's a good thing, if you can get to Fastboot then I would say to forget about the toolkits and just download the latest Google MantaRay image from here https://dl.google.com/dl/android/aosp/mantaray-jwr66y-factory-3d8252dd.tgz
Make sure your Android SDK is updated, unzip the downloaded file once and copy the contents to your Fastboot folder, shift/right click inside your fastboot folder and select "open command window here" then type "fastboot devices" and make sure your device id is shown, after that just type in your cmd window "flash-all.bat" and let it do its magic. If everything goes well by the time it completes you will have a factory restored Nexus10 and then you can start the hacking all over again.
Good Luck! and remember when in doubt, just ask.
Erik
Click to expand...
Click to collapse
Hi ricco333
thanks for the reply. I have updated the SDK and tried to run the command as you mentioned. However it is the same thing. Its getting stuck at sending bootloader. I am attaching a screenshot here. it stays there until i press ctrl+c. then it tries to continue and gets stuck again at sending boot. which is the second screenshot.
Is there any other way to restore factory image. i thought samsung devices had ODIN system. Thanks again for the reply.
Try connecting the Nexus to a different USB port, also try another USB cable, as a last resort I will go as far as using a different PC, based on your screenshots it is being recognized but my guess is that it is having a problem writing the new partitions.
Erik
Also try re downloading the stock images...
Maybe you have a corrupted file.
Have you tried using the Nexus 10 Toolkit?
http://forum.xda-developers.com/showthread.php?t=2001868
IT WORKED!!
ricco333 said:
Try connecting the Nexus to a different USB port, also try another USB cable, as a last resort I will go as far as using a different PC, based on your screenshots it is being recognized but my guess is that it is having a problem writing the new partitions.
Erik
Click to expand...
Click to collapse
Thanks so much guys.After trying 2 different cables and a new computer, a fresh installation of ADB and samsung drivers it finally worked. Thanks again. HUGE SIGH of RELIEF
I'm new to XDA so, i don't know what is needed for someone to help me root my phone, I'm tired of not having space due to preinstalled apps
@ZFSamael
Look inside here.
jwoegerbauer said:
@ZFSamael
Look inside here.
Click to expand...
Click to collapse
that's a horrible thread, besides just being vague, i tried to install the TWRP recovery as suggested from that link. It worked in installing the custom recovery, but left me stuck in recovery. After pulling the battery out umpteenth times, pressing the volume down button and/or the power button i finally got back into the OS. The Fortune 2, Andr OS 7.1.2 Nougat isn't compatible w/ TWRP. At least it didn't seem at all compatible w/ mine.
as far as the OP. using fastboot, the original ROM from LG and rebooting into fastboot mode, Magiskk works fine. the one click solutions i couldn't get to work, but why would ya want to if you can use Magisk.
need a couple of things to get started. https://github.com/Snoop05/adb-installer. I would go ahead and install the drivers from this. the WinDoze drivers failed to work as did the Google drivers w/ the full SDK. Open a cmd or powershell prompt (i have a habit of opening any of these in admin mode). When ya install the platform-tools, i would keep it simple (ie. C:\\platform-tools ... C:\\blah ... etc) something easy to get too in the confines of a DOS prompt. Need to test your driver is showing up for phone. adb devices or .\adb devices.
ya need ... i would suggest the boot.img file, so your going to need the "WindowsLGFirmwareExtract" tools and of course the LG firmware: https://lg-firmwares.com/lg-lmx210cm-firmwares/ ... it's a kdz file, don't freak, that's what the extract tool is for, but it only gets ya too a bin file for the boot.img. just rename the boot.bin file to boot.img. sometimes the same exact file works fine with fastboot, other times i have to use the raw command.
getting into fastboot was easy enough. you seem to be using the same sys i am. lm-x210cm andr OS 7.1.2 Nougat Cricket Fortune 2. Soooo, what worked for me, power down, then hold the vol down button, release, then hold and simutaneously insert your tether cord.
you should be looking at your cmd/powershell window now. if you haven't already, install the Magisck Manager and run ... there's plenty of tutorials already on this. the only thing maybe worth mentioning, is ya may have to issue flash:raw instead of just the flash for the fastboot command.
Once done, it's going to factory reset your machine, so hopefully your using Titanium Backup or Dr Fone .... something where it's easy to get most of your stuff back.
good luck.