Related
I accepted the latest over the air update and I need to know if that messed up my chances of obtaining root. I tried photon torpedo and could not get it to work. My device says it is unlocked but I can not boot into recovery. I have flashed several recoveries using sdk-tools but I cannot erase any recoveries. I receive an error. I have tried several things and am at a loss to as what is the most recent way if there is one. Looking for someone with more experience then I to guide me. I previously rooted my EVO 4g and EVO 3d and was away from internet for about 9 months so I mistook the old Motorola Photon for the Photon Q. Didn't realize till way later that I was trying some rooting techniques intended for the old photon on my photon q. Anyways I feel a bit lost. Any help would be greatly appreciated. I can provide any information requested. Will be monitoring this thread all day today and will provide quick responses. Cheers!
Uhm... You tried the rooting steps for the Photon?
I really hope you didn't brick your device - that is a SURE fire way to do it tho.
Anyhoo, why haven't you just tried the official unlock from Moto?
arrrghhh said:
Uhm... You tried the rooting steps for the Photon?
I really hope you didn't brick your device - that is a SURE fire way to do it tho.
Anyhoo, why haven't you just tried the official unlock from Moto?
Click to expand...
Click to collapse
I did try that first. And successfully as far as I know because my bootloader says unlocked. I then went to install supersu and It won't install su binary. Tried to force install su binary and that did not work either. Any ideas? I joined the military so I was busy for 9 months straight. Honestly I'm usually more up to date than that. I think it's an understandable mistake and I understand the risks behind rooting. I bricked my first phone 7 years ago and brought it back using putty.
sent17inel said:
I did try that first. And successfully as far as I know because my bootloader says unlocked. I then went to install supersu and It won't install su binary. Tried to force install su binary and that did not work either. Any ideas? I joined the military so I was busy for 9 months straight. Honestly I'm usually more up to date than that. I think it's an understandable mistake and I understand the risks behind rooting. I bricked my first phone 7 years ago and brought it back using putty.
Click to expand...
Click to collapse
You didn't truly brick the device if you were able to bring it back using putty...
Regardless, you should always be careful with anything you do. Why are you trying to install the SuperSU binary right after unlocking? You need to flash a custom recovery first.
Or do you already have a custom recovery? I'm kinda lost here, you seemed to indicate you were unable to get a custom recovery flashed, but you're trying to force SuperSU without a custom recovery...?
arrrghhh said:
You didn't truly brick the device if you were able to bring it back using putty...
Regardless, you should always be careful with anything you do. Why are you trying to install the SuperSU binary right after unlocking? You need to flash a custom recovery first.
Or do you already have a custom recovery? I'm kinda lost here, you seemed to indicate you were unable to get a custom recovery flashed, but you're trying to force SuperSU without a custom recovery...?
Click to expand...
Click to collapse
Soft bricked . . . I tried to flash a custom recovery. I Tried 2. CW and another one that I can't remember at the moment. They both said they flashed successfully but I was unable to boot into any of them. I got the android with an exclamation mark. I tried to erase them and it gave me an error. Some kind of permission error. I did this all a few days ago. Decided to take a break. Honestly "you should always be careful with anything you do" . . did that really need to be said?
sent17inel said:
Honestly "you should always be careful with anything you do" . . did that really need to be said?
Click to expand...
Click to collapse
Hey, I'm not trying to force SuperSU to apply without a custom recovery here... one step at a time is all I'm trying to say.
Let's get on with it...
sent17inel said:
Soft bricked . . . I tried to flash a custom recovery. I Tried 2. CW and another one that I can't remember at the moment. They both said they flashed successfully but I was unable to boot into any of them. I got the android with an exclamation mark. I tried to erase them and it gave me an error. Some kind of permission error. I did this all a few days ago. Decided to take a break.
Click to expand...
Click to collapse
So you haven't been able to flash a custom recovery. When you flash, it says successful? Perhaps try again. Follow the directions carefully.
arrrghhh said:
Hey, I'm not trying to force SuperSU to apply without a custom recovery here... one step at a time is all I'm trying to say.
Let's get on with it...
So you haven't been able to flash a custom recovery. When you flash, it says successful? Perhaps try again. Follow the directions carefully.
Click to expand...
Click to collapse
I did try again about 5 minutes ago. It says that it won't unlock because it's already unlocked.
I got into the stock recovery. adb reboot recovery and then it will display a green android laying down with a red exclamation point. From there I hit both volume keys and it brings up the stock recovery menu. I should be able to go from here. I think the Update I did changed some things that caused the CW recovery to not flash right or to be rewritten before I can boot into it. I should be good now. Thank you for your help.
sent17inel said:
I got into the stock recovery. adb reboot recovery and then it will display a green android laying down with a red exclamation point. From there I hit both volume keys and it brings up the stock recovery menu. I should be able to go from here. I think the Update I did changed some things that caused the CW recovery to not flash right or to be rewritten before I can boot into it. I should be good now. Thank you for your help.
Click to expand...
Click to collapse
So you managed to flash custom recovery? I didn't mean to say you should try to unlock again - I meant you should try flashing recovery again (CWM, TWRP).
arrrghhh said:
So you managed to flash custom recovery? I didn't mean to say you should try to unlock again - I meant you should try flashing recovery again (CWM, TWRP).
Click to expand...
Click to collapse
With the over the air update it installs a shell script that forces the install of the stock recovery. When you reboot into the stock recovery you are presented with an image that looks like it has failed (android laying down with stomach open and a red exclamation point over it.) it will not do anything from here and eventually time out and reboot itself. If when it is at this image you press both volume keys you will be presented with a Recovery menu. I can take it from here. Thank you.
sent17inel said:
With the over the air update it installs a shell script that forces the install of the stock recovery. When you reboot into the stock recovery you are presented with an image that looks like it has failed (android laying down with stomach open and a red exclamation point over it.) it will not do anything from here and eventually time out and reboot itself. If when it is at this image you press both volume keys you will be presented with a Recovery menu. I can take it from here. Thank you.
Click to expand...
Click to collapse
Ok... Good luck.
Thread moved. Please post in the correct forum sections in future. All questions belong here in Q&A.
Thanks
AvRS
unlocking nd rooting visuals
can someone who owns Photon Q 4G LTE do a visual on rooting nd unlocking the bootloader cause was thinking bout getting this phone & dont wanna brick the phone i have read the guide's nd done tons of reseaching but found no visual's on how to do it can someone help pls?
thanks in advance
1300 said:
can someone who owns Photon Q 4G LTE do a visual on rooting nd unlocking the bootloader cause was thinking bout getting this phone & dont wanna brick the phone i have read the guide's nd done tons of reseaching but found no visual's on how to do it can someone help pls?
thanks in advance
Click to expand...
Click to collapse
Well, I was going to ask you where you are stuck in the process, but it sounds like you haven't even purchased the device yet...
I wouldn't worry about unlocking and rooting until the device is in your hands. We can help out a lot easier when you actually have the thing, hahaha.
To answer your question, I don't think there's any visuals because it's not a very visual thing. fastboot is anything but visually-appealing, and the process is rather dry. Just follow the steps carefully and you'll be fine. It's very straightforward.
Plus you must decide if you prefer to keep the bootloader LOCKED or UNLOCKED and still have root access. Research the differences in the two.
The only thing simple is the belief in simplicity.
Similar problem
Hey, I have similar problem here
I tried to root my phone using howtos on internet, but when I flash cwm img (first try from howtos, second try from CWM page), it take only a second (in every howto is it should take few minutes). But it returns that cwm was flashed sucessfully. Still.... its weird.
Then - when I want to reboot to CWM, I can see only that dead poor green thing. I tried to upload the superuser zip from here, but it returns "signature verification failed".
I still belive, there IS CWM recovery, because img was flashed sucessfully (or am I wrong?) so i tried to reboot to CWM via adb.
And another problem has appeared. ADB doesn`t recognise my phone. I installed the newest drivers from moto pages (USB drivers bit 4.7.1 and DeviceManager 2.3.4) have USB debugging mod ON, restarted my computer (win7 64bit), tried stand on my head, kill black ****.... it still returns "device not found".
Any ideas how to get to the next step? Functional adb would be great...
How long took you to flash cwm image?
Thx
D.Eternity said:
Hey, I have similar problem here
I tried to root my phone using howtos on internet, but when I flash cwm img (first try from howtos, second try from CWM page), it take only a second (in every howto is it should take few minutes). But it returns that cwm was flashed sucessfully. Still.... its weird.
Then - when I want to reboot to CWM, I can see only that dead poor green thing. I tried to upload the superuser zip from here, but it returns "signature verification failed".
I still belive, there IS CWM recovery, because img was flashed sucessfully (or am I wrong?) so i tried to reboot to CWM via adb.
And another problem has appeared. ADB doesn`t recognise my phone. I installed the newest drivers from moto pages (USB drivers bit 4.7.1 and DeviceManager 2.3.4) have USB debugging mod ON, restarted my computer (win7 64bit), tried stand on my head, kill black ****.... it still returns "device not found".
Any ideas how to get to the next step? Functional adb would be great...
How long took you to flash cwm image?
Thx
Click to expand...
Click to collapse
Let's take a step back here.
If you DON'T have ADB, you're NOT going to be able to flash CWM.
Make sure you establish an ADB connection BEFORE trying to flash again.
Good luck.
arrrghhh said:
Let's take a step back here.
If you DON'T have ADB, you're NOT going to be able to flash CWM.
Make sure you establish an ADB connection BEFORE trying to flash again.
Good luck.
Click to expand...
Click to collapse
Ok, but when I ask for fastboot devices, it returns my device (and I can work with fastboot commands). When I type adb device, it returns empty list. How is it possible?
D.Eternity said:
Ok, but when I ask for fastboot devices, it returns my device (and I can work with fastboot commands). When I type adb device, it returns empty list. How is it possible?
Click to expand...
Click to collapse
fastboot and adb are kind of separate things...
You can't access adb when the phone is in fastboot mode, and you can't access fastboot when the phone is in recovery or booted into a ROM. However, in recovery or when booted adb should work. If it's still failing make sure you're using the factory USB cable. Also, try a different port or computer.
Good luck.
arrrghhh said:
fastboot and adb are kind of separate things...
You can't access adb when the phone is in fastboot mode, and you can't access fastboot when the phone is in recovery or booted into a ROM. However, in recovery or when booted adb should work. If it's still failing make sure you're using the factory USB cable. Also, try a different port or computer.
Good luck.
Click to expand...
Click to collapse
I know fastboot and adb are separate things, this is why I assumed cwm recovery image was flashed succesfully (despite it took only a few seconds). Now I`m trying to get into CWM, but when my phone is plugged (standard mode), adb reboot recovery returns Device not found. I haven`t the original cable here, but in the office (where I have motorola cable) it was the same. Truth is both my computers are Win7 64bit. Is it possible adb has problem with 64bit system?
Thank you for helping me
So, today I trade my HTC One for a RAZR XT925, $350, and a water proof 32GB Sandisk ultra sd card on Kijiji. I thought it was kinda weird to get all of this stuff, but it seemed fine at the time. Afterwards however, I found out that every time you turn off or reboot the phone, it tried to go into recovery mode or something with the android guy and a bar at the bottom in a loop and always factory reset the phone, so no matter what, every time you turned it off, it'd reset it. After hours and hours of work, I have the bootloader unlocked, rooted, CWM installed, and Cynogenmod also installed. It no longer factory resets it (I think, but i sent a text to a random number and when I rebooted it was still there), however, everytime i power off and power on, it goes into recovery mode. This is very annoying and will make it very hard to sell again, but if I can fix this last thing, I'll have a solid phone until the waterproof S4 comes out as well as having made like $100.
So basically, I need to know what to do to make it boot into the rom by default and not the recovery. Also, I searched it up and someone else had a problem where they kept booting into AP fastboot mode I think, I tried that line, it said successful, but it didnt work. For me, it's booting into the recovery by default.
Does it boot into stock recovery?
Sent from my Galaxy Nexus using xda premium
recovery
jmcdonald58 said:
Does it boot into stock recovery?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I root it, unlocked the boot loader, flashed cwm recovery, and installed CyanogenMod. Now it boots into cwm recovery by default and if I click reboot system now, it just boots back into cwm. Only way to get to the system is to go to the boot menu by pressing all three buttons and selecting boot normally.
Stock recovery is gone. Cwm asked to replace it so that the phone doesn't reinstall it on reboot. Cwm doesn't, but when the phone booted it stock recovery, it used to get wiped.
roguezz said:
I root it, unlocked the boot loader, flashed cwm recovery, and installed CyanogenMod. Now it boots into cwm recovery by default and if I click reboot system now, it just boots back into cwm. Only way to get to the system is to go to the boot menu by pressing all three buttons and selecting boot normally.
Stock recovery is gone. Cwm asked to replace it so that the phone doesn't reinstall it on reboot. Cwm doesn't, but when the phone booted it stock recovery, it used to get wiped.
Click to expand...
Click to collapse
Strange If it was me I would try a toolkit and redo the whole process something went wrong somewhere wish I could help Good Luck
recovery
jmcdonald58 said:
Strange If it was me I would try a toolkit and redo the whole process something went wrong somewhere wish I could help Good Luck
Click to expand...
Click to collapse
No the problem was in stock. When I got it it wasn't rooted or anything, rooting helped fix the problem partially by not making it wipe every time I boot it. Now the only problem is that whenever I boot it up after a shut down or restart, it boots into recovery mode instead of the ROM.
roguezz said:
No the problem was in stock. When I got it it wasn't rooted or anything, rooting helped fix the problem partially by not making it wipe every time I boot it. Now the only problem is that whenever I boot it up after a shut down or restart, it boots into recovery mode instead of the ROM.
Click to expand...
Click to collapse
did you ever find a solution for this? I just bought a used phone and am facing the same problem - I can't even boot into recovery, it will just start bootlooping again. Only thing that seems to be working is fastbood mode. (or regular reboot, but then everything is wiped every time)
coldtech said:
did you ever find a solution for this? I just bought a used phone and am facing the same problem - I can't even boot into recovery, it will just start bootlooping again. Only thing that seems to be working is fastbood mode. (or regular reboot, but then everything is wiped every time)
Click to expand...
Click to collapse
Fastboot the stock ROM. That should return the phone to it's bone stock condition.
Sent from my DROID RAZR HD using Tapatalk 4
mentose457 said:
Fastboot the stock ROM. That should return the phone to it's bone stock condition.
Sent from my DROID RAZR HD using Tapatalk 4
Click to expand...
Click to collapse
trying right now. RSDLite is giving me an "unknown fastboot command getvar" error...still trying to figure out why.
coldtech said:
trying right now. RSDLite is giving me an "unknown fastboot command getvar" error...still trying to figure out why.
Click to expand...
Click to collapse
I wouldnt mess with RSDLite. Google gave us fastboot for a reason.
mentose457 said:
I wouldnt mess with RSDLite. Google gave us fastboot for a reason.
Click to expand...
Click to collapse
is there an alternative to flash the stock ROM on a locked device?
coldtech said:
is there an alternative to flash the stock ROM on a locked device?
Click to expand...
Click to collapse
Use this utility: http://forum.xda-developers.com/showthread.php?t=2241788
Use the 'Lite' version as it includes the stock rom.
mentose457 said:
Use this utility: http://forum.xda-developers.com/showthread.php?t=2241788
Use the 'Lite' version as it includes the stock rom.
Click to expand...
Click to collapse
Thanks for the hint, will give it a try. RSDLite just completed flashing, but the odd behaviour of the phone is still the same. Guess I might just have a broken phone... :/
mentose457 said:
Use this utility: http://forum.xda-developers.com/showthread.php?t=2241788
Use the 'Lite' version as it includes the stock rom.
Click to expand...
Click to collapse
After a few hours, I (somehow) ended up being able to enter recovery. On the downside though, now it always goes automatically into fastboot, because everything seems to be screwed up. I even got CWM installed though (unlocked the device because I didn't know what else to do).
Now every time it goes into fastboot, the reason given is: "sticky bit fastboot"
Any ideas left?
Oh btw, I have a german phone, in case that matters somehow. I can't flash in any fastboot way anymore, now I always get some message about a downgraded version. Of course details can be supplied if needed.
edit: was now able to flash CM, no idea what I did so that it didn't give me errors anymore. It still goes into fastboot by default on every reboot though, I always need to select "reboot device" manually every time.
coldtech said:
After a few hours, I (somehow) ended up being able to enter recovery. On the downside though, now it always goes automatically into fastboot, because everything seems to be screwed up. I even got CWM installed though (unlocked the device because I didn't know what else to do).
Now every time it goes into fastboot, the reason given is: "sticky bit fastboot"
Any ideas left?
Oh btw, I have a german phone, in case that matters somehow. I can't flash in any fastboot way anymore, now I always get some message about a downgraded version. Of course details can be supplied if needed.
edit: was now able to flash CM, no idea what I did so that it didn't give me errors anymore. It still goes into fastboot by default on every reboot though, I always need to select "reboot device" manually every time.
Click to expand...
Click to collapse
Sounds like you are able to use the phone. That’s good.
The error is saying it can’t downgrade the trust zone (tz) right? That is normal for a phone with an unlocked bootloader. You can simply ignore that.
The sticky bit fastboot problem looks like it can be fixed by issuing this command while in fastboot mode: fastboot oem fb_mode_clear
mentose457 said:
Sounds like you are able to use the phone. That’s good.
The error is saying it can’t downgrade the trust zone (tz) right? That is normal for a phone with an unlocked bootloader. You can simply ignore that.
The sticky bit fastboot problem looks like it can be fixed by issuing this command while in fastboot mode: fastboot oem fb_mode_clear
Click to expand...
Click to collapse
the fb_mode_clear was the culprit, thanks a lot!
and the error says: "downgraded security version. update gpt_main version failed. preflash validation failed for GPT" - which is still keeping me from flashing stuff via fastboot.
since I can't fastboot flash at the moment: do you happen to know where I can get the german modem image so that I can flash it using CWM? I think through all the flashing and trying I have a corrupt or wrong modem file (probably the US version). I can not log into the carrier network right now. it asks me for my SIM PIN and unlocks the SIM, but that's it. so I can't make phone calls or anything right now.
I pulled a boneheaded move and ended up formatting my phone from within the TWRP menu. Now the stock operating system is gone.
I wanted to put on one of the Gummy Nightly builds, but I'm new to TWRP and selected the wrong options while wiping.
So now I have the Gummy ROM on my PC, the phone is connected to my PC and in TWRP (in the advanced adb sideload feature), but adb will not recognize my phone.
When I check device manager, SAMSUNG_Android_SCH-I535 is there, but with a yellow "cauton" symbol. When I look at properties, it tells me that "The drivers for this device are not installed (Code 28).
I went out to the Samsung page and got the exe to unpack drivers on my machine... I've tried "update driver" and pointing to the root of the directory containing the Samsung drivers, but my PC claims none of them are applicable.
So what I'm looking for here is:
(1) How do I get this ROM on my phone so that I can install the zip and have a working OS again?
(2) Assuming that using the ADB Sideload feature of TWRP is my best option, how do I get the device drivers for my galaxy s3 installed to my windows 8 PC and get adb to detect it?
Thanks in advance.
Ok, so it seems to have gotten worse.
I cannot get my windows installation to recognize the phone without it being able to boot an android OS, it seems.
I had it in TWRP 2.6.0.0, but as I was trying to reboot to see if I could get into download mode (my thought being to change out TWRP for Clockwork; I seem to remember Clockwork Recovery having a "mount as USB" option which TWRP seems to lack), it tried to root the file system.
After that, the screen went black and nothing happened... the phone was unresponsive. I would remove the battery and replace it to have it vibrate once and then not respond to any key presses.
I removed the battery, SD card, and SIM card, replacing only the battery and got it to turn on and show a Samsung Galaxy SIII logo... but it's just sitting there... I'm assuming it's frozen because there's no OS to boot on the internal storage.
Please help me recover my phone!
Ok, so I've found I can still get into download mode, but not into recovery.
Recovery seems to lead to a black screen with nothing on it.
Trying to boot normally leads to the statis Samsung Galaxy SIII logo.
Can I fix my phone from the download menu?
Please help me.
Install kies and at the end of the install make sure you check install unified drivers. Then flash root66 through Odin. After that you should be good to install ROMs again.
ThePagel said:
Install kies and at the end of the install make sure you check install unified drivers. Then flash root66 through Odin. After that you should be good to install ROMs again.
Click to expand...
Click to collapse
Thanks for the reply!
Sorry, I'm a little out of date on the flashing and stuff -- I was just over in the thread where the poster thought he half softbricked his phone and was asking about 4.1.2 vs. 4.3
I see this at the top of my screen sitting here in download mode:
ODIN MODE
PRODUCT NAME: SCH-I535
CUSTOM BINARY DOWNLOAD: YES (6 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
It seems my bootloader got relocked somehow -- is this why my phone just goes to black screen when I attempt to boot into recovery -- even if I have TWRP or CWR installed? Odin claims I just pushed philz custom CWR to my PDA section, but it still won't go into recovery.
What are my options here?
You are pre 4.3 I'll help you more in the morning if no one else does first.
ThePagel said:
You are pre 4.3 I'll help you more in the morning if no one else does first.
Click to expand...
Click to collapse
Ok, thanks -- I appreciate that someone's willing to help! Googling stuff is just getting me more and more confused.
I'll stay tuned for help and turn off my phone so I don't screw things up further in the meantime.
My desired result here, I think is to have my bootloader remain unlocked (as I was under the impression it was, since I was running TWRP with rooted stock ROM), with CWR as the custom recovery software and Gummy as my current ROM.
Side note: I've noticed I don't even get a battery indicator on the main screen now when I press the home button -- is this because of whatever's causing my recovery to not work (and the potential lack of an OS)?
Thanks in advance.
corrosivefrost said:
Ok, thanks -- I appreciate that someone's willing to help! Googling stuff is just getting me more and more confused.
I'll stay tuned for help and turn off my phone so I don't screw things up further in the meantime.
My desired result here, I think is to have my bootloader remain unlocked (as I was under the impression it was, since I was running TWRP with rooted stock ROM), with CWR as the custom recovery software and Gummy as my current ROM.
Side note: I've noticed I don't even get a battery indicator on the main screen now when I press the home button -- is this because of whatever's causing my recovery to not work (and the potential lack of an OS)?
Thanks in advance.
Click to expand...
Click to collapse
Once you in download mode, can your Odin see your phone?
buhohitr said:
Once you in download mode, can your Odin see your phone?
Click to expand...
Click to collapse
I believe it can. After TWRP stopped working, I tried to replace it with CWR and the digital flash count went up (Odin showed no errors on the flash) -- recovery still won't work though, holding vol+/home/power simply gives me a black screen after I see the SAMSUNG logo with the recovery boot text in the upper left.
corrosivefrost said:
I believe it can. After TWRP stopped working, I tried to replace it with CWR and the digital flash count went up (Odin showed no errors on the flash) -- recovery still won't work though, holding vol+/home/power simply gives me a black screen after I see the SAMSUNG logo with the recovery boot text in the upper left.
Click to expand...
Click to collapse
What stock version do you have on your phone right now?
buhohitr said:
What stock version do you have on your phone right now?
Click to expand...
Click to collapse
None? :silly:
I think before this fiasco, it was running whatever version was previous to the new VZW update.
It was the fact that the new update was trying to install and failing repeatedly (because my bootloader was unlocked, I think?) that prompted me to look into finally switching to a ROM. However, my unfamiliarity with TWRP led to me formatting my phone (everything, it seems, including the SD card)... so I'm not really sure what' "on the phone right now". :\
I'm really not sure what kind of state anything is in at this point -- other than Odin seemingly working and being able to get into download mode.
Again, short version of what happened:
(1) Accidentally did a full wipe (factory reset?) in TWRP -- this wiped the ROM I was going to install with TWRP off the phone.
(2) While trying to ADB sideload from TWRP and telling TWRP to reboot, TWRP tried to install supersu.
(3) After (2), I was unable to get back into recovery mode. I got into Odin and tried to flash philz customer clockwork recovery and it seemed successful. Reboot and attempt to enter recovery still fails. Samsung logo with recovery mode text appears, but then the screen goes black.
(4) Normal boot leaves the screen stuck on the Samsung Galaxy SIII logo indefinitely.
corrosivefrost said:
None? :silly:
I think before this fiasco, it was running whatever version was previous to the new VZW update.
It was the fact that the new update was trying to install and failing repeatedly (because my bootloader was unlocked, I think?) that prompted me to look into finally switching to a ROM. However, my unfamiliarity with TWRP led to me formatting my phone (everything, it seems, including the SD card)... so I'm not really sure what' "on the phone right now". :\
Click to expand...
Click to collapse
OK, download this image and flash with Odin(you should be using Odin version 3.07) http://goo.im/devs/invisiblek/i535/stock.vzw_root66.tar This should bring your phone back from the dead.
Edit: after you have your phone up and running, download goo manager and install cwm recovery since your phone is pre rooted already.
buhohitr said:
OK, download this image and flash with Odin(you should be using Odin version 3.07) http://goo.im/devs/invisiblek/i535/stock.vzw_root66.tar This should bring your phone back from the dead.
Edit: after you have your phone up and running, download goo manager and install cwm recovery since your phone is pre rooted already.
Click to expand...
Click to collapse
Ok, that looks like some version of the stock vzw ROM with root already installed?
This is what ThePagel seemed to recommend as well before I ended up with more questions about what was going on before I did it.
What part of Odin do I flash to? PDA again, just like a custom recovery?
corrosivefrost said:
Ok, that looks like some version of the stock vzw ROM with root already installed?
This is what ThePagel seemed to recommend as well before I ended up with more questions about what was going on before I did it.
What part of Odin do I flash to? PDA again, just like a custom recovery?
Click to expand...
Click to collapse
Yes, it's pre rooted stock image and yes flash with PDA.
buhohitr said:
Yes, it's pre rooted stock image and yes flash with PDA.
Click to expand...
Click to collapse
Standard auto-reboot and f_reset_time options? nothing else necessary?
corrosivefrost said:
Standard auto-reboot and f_reset_time options? nothing else necessary?
Click to expand...
Click to collapse
Correct. When you click on PDA and select the image, give it time to showup in Odin cause the size is big.
buhohitr said:
Correct. When you click on PDA and select the image, give it time to showup in Odin cause the size is big.
Click to expand...
Click to collapse
Alright, I'll give it a shot and report back.
Thank you!
corrosivefrost said:
Alright, I'll give it a shot and report back.
Thank you!
Click to expand...
Click to collapse
If that doesn't work you'll need to flash the bootchain first. I don't have a link but I could find it if you need to use it.
ThePagel said:
If that doesn't work you'll need to flash the bootchain first. I don't have a link but I could find it if you need to use it.
Click to expand...
Click to collapse
Yes if the bootloader is still locked he needs boot chain can be found here http://forum.xda-developers.com/showthread.php?t=2046439
ThePagel said:
If that doesn't work you'll need to flash the bootchain first. I don't have a link but I could find it if you need to use it.
Click to expand...
Click to collapse
It did work! Hooray!
buhohitr said:
Yes if the bootloader is still locked he needs boot chain can be found here http://forum.xda-developers.com/showthread.php?t=2046439
Click to expand...
Click to collapse
Didn't need to go that far -- but now that I'm back up and running, signed into google play, and downloaded goo manager, can you point me in the right direction for getting it to install cwm recovery?
Thanks guys!
Hi, I'm new to XDA. Sorry if I did something wrong already. But I have a problem, I tried installing a new boot animation to my moto e 1st gen (bootloader was unlocked, it was rooted too). Now whenever I turn the phone on, The WARNING BOOTLOADER UNLOCKED image shows up, but there is no boot animation. I cannot access anything, I can only go into recovery mode and CWM. I have tried factory reset using Recovery Mode (No success, just does WARNING boot loop again ) I have also tried factory reseting through CWM, till no success. I am giving up, I just recently bought this phone. NAY help would be appreciated. Thanks in advance!
rakibshahid said:
Hi, I'm new to XDA. Sorry if I did something wrong already. But I have a problem, I tried installing a new boot animation to my moto e 1st gen (bootloader was unlocked, it was rooted too). Now whenever I turn the phone on, The WARNING BOOTLOADER UNLOCKED image shows up, but there is no boot animation. I cannot access anything, I can only go into recovery mode and CWM. I have tried factory reset using Recovery Mode (No success, just does WARNING boot loop again ) I have also tried factory reseting through CWM, till no success. I am giving up, I just recently bought this phone. NAY help would be appreciated. Thanks in advance!
Click to expand...
Click to collapse
Hello,
Can you tell us what firmware was your phone running? Also what recovery do you have on your phone?
If stock, you may try flashing stock firmware via fastboot.
-Vatsal
Vatsal said:
Hello,
Can you tell us what firmware was your phone running? Also what recovery do you have on your phone?
If stock, you may try flashing stock firmware via fastboot.
-Vatsal
Click to expand...
Click to collapse
Thanks for responding so quickly! But I fixed the problem a few minutes after posting this . But there is a new problem, I downgraded from Android 5.0.2 to Android 4.4.2. After doing this the phone worked perfectly. Then a few minutes later it installed a system update for 4.4.4 and now the phone is hard bricked. I can't access recovery mode, CWM, or even turn the phone on now. Before charging the phone, if I held the power button for a long time, the LED lit up and turned back off. Now there is no response from the phone at all no matter what I do.
Also, I had ClockWorkMod and stock recovery on my phone (Is stock recovery the one that shows up when you hold power+volume down? If so I had both CWM and stock) But now I can't access either recovery modes. If it at least went into stock recovery, I'd flash stock firmware, root it, install CWM, and flash a Lollipop zip. (I like Lollipop, I don't know why there are so many people that hate Lollipop )
Any help would be much appreciated. All i need now is a way to flash files without going into recovery mode on phone.
From what I remember it had TWRP on it, I had it rooted on stock image for a while. Got absolutely fed up with their software and tried to install a stock android rom on it. Got through a few that wouldn't load properly so went to go back to a stock rom and it's stuck in a bootloop now. I've never been able to get into recovery no matter what button combo. It goes to the yellow text page then reboots. Not matter what combo of buttons i push.
Not really sure what to look for or what to do beyond this point as most help i've found has been guided to get into recovery. The most I've been able to get is this basically a downward facing parentheses with a small circle that appears and runs through it.
Can you get into fastboot? - Turn it off, connect USB and hold power and vol -
If yes, its easy to fix. Or you can try going to eRecovery and Format all data and download latest software.
Just tried. That would be a yes.
bump.
Did you fix it or you still need help? If yes, what version of android were you using? Do you have an sd card you can use to install stock firmware?
The point is, we need to get you running on oreo, after that is everything ez. There is probably no way of getting oreo other way than using hisuite, but I dont know. For hisuite. To make hisuite show oreo update, you need to get latest nougat running on your phone. It should be ez with twrp. You can use firmware finder on windows or other phone to download proper full ota update and flash trough twrp. If anything, feel free to ask me here.
Still stuck at the fastboot option. I don't really remember what version it was. Whatever it was exactly 1 year ago is all I can remember. I don't think it was oreo though?
I can't use TWRP though, as I said, I can't get into any recovery stock or TWRP, only fastboot.
delete
Spykez0129 said:
Still stuck at the fastboot option. I don't really remember what version it was. Whatever it was exactly 1 year ago is all I can remember. I don't think it was oreo though?
I can't use TWRP though, as I said, I can't get into any recovery stock or TWRP, only fastboot.
Click to expand...
Click to collapse
Did you tried Dload? It should work. Download latest nougat for your device from firmware finder and flash it with Dload.
EDIT: If fastboot works, just download latest twrp for nougat and flash it. After that just downlaod stock nougat and flash trough twrp.
PremiumBlaze said:
Are you able to flash anything in fastboot like the stock recovery?
Does fastboot say that the phone is unlocked?
Does fastboot say that FRP is unlocked?
Click to expand...
Click to collapse
Says both are unlocked. I flashed the latest recovery (for nougat) to it and both said ok.
Then I did fastboot reboot recovery command and it says OKAY on the sending, but under "booting" it says FAILED. Command not allowed?
Can't manually boot into twrp either, phone stays stuck on your device is booting now.
delete