6039y unblock from stock recovery - Onetouch Idol 3 Q&A, Help & Troubleshooting

Hi, I screwed up my phone (soft-bricked) trying to install TWRP and now my phone is stuck on the logo, it just stays there forever...
I can boot into recovery, but I can not boot into download mode, because as soon as I plug my phone in, it goes straight to the logo screen.
Basically I need a way to restore my boot.img - I have tried using the Alcatel update software but my phone will not show the battery screen because it is always stuck on the logo screen. If there is a stock update.zip please can I have it!!!
Thanks,
MasterDoctor

Update: I am trying to create my own update.zip to flash using the stock recovery software. I can now confirm that the problem is definitely caused due to the boot partition. I stupidly flashed TWRP to the boot partition and not the recovery partition using the Flashify App. Anyway, I am downloading an update.zip for a Nexus device and I'm going to try and hack together a zip to get my phone working.
If it works, I will post it here. If I haven't posted with another update, the problem is still ongoing so feel free to post with an idea.

try to repair your device using the official alcatel upgrade app. I think you will not be able to make update. zip flashable trough stock recovery since you will not sign it properly to be flashable trough stock recovery.

look my post:
http://forum.xda-developers.com/showpost.php?p=63709274&postcount=113

wiemar said:
look my post:
http://forum.xda-developers.com/showpost.php?p=63709274&postcount=113
Click to expand...
Click to collapse
It says : Download Fail:Sahara FailValeue cannot be null.
Parameter name: key

DallasCZ said:
try to repair your device using the official alcatel upgrade app. I think you will not be able to make update. zip flashable trough stock recovery since you will not sign it properly to be flashable trough stock recovery.
Click to expand...
Click to collapse
Yeah, I came to that conclusion shortly after embarking on my task.
All in all it came to me getting a free replacement.

MBix said:
It says : Download Fail:Sahara FailValeue cannot be null.
Parameter name: key
Click to expand...
Click to collapse
What exactly says this?
Can you provide screenshots?

Related

[Q] [i9023] Blank/Black screen in recovery

Hey everyone,
Basically I was trying to flash a new ROM onto an old Nexus S of mine and when I tried to boot into recovery there was just a black screen. I pressed the power button and a single line saying "Clockwork mod Recovery" and the version number popped up. I assumed that the recovery must've been corrupted so I erased it and installed the latest version using fastboot which seemed to work fine.
Now whenever I try to boot into recovery I just get a blank screen with nothing else. I've tried using other recovery images such as twrp but the same problem happened, I just get the background wallpaper/image and nothing else.
I searched the forums and apparently people were having this issue earlier on when the i9023 was first released but now most custom recoveries are supposed to work with both i9020 and i9023.
Also the touch buttons light up and vibrate whenever I touch them when I'm in recovery mode.
Any help to this problem would be greatly appreciated as atm I have an old ROM which is buggy as hell and I need to get rid of it.
Cheers!
I had the same Issue. If you can boot into the rom, you can try to download the rommanager-app and install the recovery from there.
Hey I tried that already that and instead of booting into recovery it just went into the bootloader and said "No Recovery or Bootloader found".
Any other ideas?
Did you clicked the first point in rommanager? Install recovery, or you only hit the second button reboot into recovery?
Sent from my Full Android on Crespo using XDA App
Hey
I have the i9023 and I install rom manager. install CWM and if I reboot into recovery it works and I get in to CWM recovery.. but after reboot into os.. if I go into Rom manager and reboot to recovery it dont work? I just get the android figur and a "!".. then I just can Power + vol up and I'm in bootloader recovery..
Do I have to install CWM every time i want to use it? and can't I access CWM on boot op ?
sorry for my bad English
Normaly you have to flash the recovery only once.
Try to flash the newer clockwork-recovery with fastboot.
http://forum.xda-developers.com/showthread.php?t=988686
Alfiedk: You need to get rid of this file:
/system/etc/install-recovery.sh
As it re-installs the stock recovery every boot.
I think you can download any custom ROM for your phone, and flash it in CWM recovery, this will also solve the problem
Edit: Did you unlock the phone? Have you tried fastboot oem unlock?
Sent from my SNES
bedalus said:
Alfiedk: You need to get rid of this file:
/system/etc/install-recovery.sh
As it re-installs the stock recovery every boot.
I think you can download any custom ROM for your phone, and flash it in CWM recovery, this will also solve the problem
Edit: Did you unlock the phone? Have you tried fastboot oem unlock?
Sent from my SNES
Click to expand...
Click to collapse
I havent unlock my phone, but I can get in to bootloader is it then necessary to unlock ?
I try to delete the /install-recovery.sh
Yes you need to unlock your bootloader, if you dont want to reflash it all the time.
Sent from my Full Android on Crespo using XDA App
Xziped said:
Yes you need to unlock your bootloader, if you dont want to reflash it all the time.
Sent from my Full Android on Crespo using XDA App
Click to expand...
Click to collapse
Then it must be unlock as default.. I havent unlock it.. just delete the install install-recovery.sh and it works every time now.
now I just have to find a ROM to try..
Xziped said:
Did you clicked the first point in rommanager? Install recovery, or you only hit the second button reboot into recovery?
Sent from my Full Android on Crespo using XDA App
Click to expand...
Click to collapse
Yes I made sure I selected install clockwork mod. Like I said the problem isn't the same when I do this, instead of a blank screen, when I boot into recovery it goes straight to fastboot and tells me that I don't have a recovery image installed at all...
Simultaneity said:
Yes I made sure I selected install clockwork mod. Like I said the problem isn't the same when I do this, instead of a blank screen, when I boot into recovery it goes straight to fastboot and tells me that I don't have a recovery image installed at all...
Click to expand...
Click to collapse
what happens when you try to temporary boot into the recovery?
instead of "fastboot flash recovery recovery.img", try to "fastboot boot recovery.img"
Just look for an recovery.img that works temporary and then try to flash it permanently.
I'll try it and get back to you Xziped. If anyone else can think of any other ideas please just throw'em at me, I'm willing to try anything!
Yeah no help there either. It does the exact same thing temporarily booting into a recovery that it did when I actually had it installed on the phone :\.
I updated ROM manager to the latest and tried installing CWM with that but to no avail. It still says that there is no recovery installed when I do that.
Simultaneity said:
Yeah no help there either. It does the exact same thing temporarily booting into a recovery that it did when I actually had it installed on the phone :\.
I updated ROM manager to the latest and tried installing CWM with that but to no avail. It still says that there is no recovery installed when I do that.
Click to expand...
Click to collapse
Sorry but if not even the temporary recovery boots up, i dont know what else we can do
did you try some of the older recoverys? is your bootloader unlocked?
I haven't tried an older recovery and my bootloader is unlocked.
could it be a problem with my computer as opposed to the phone itself? As in my computer is messing up when trying to flash the recovery?
I've also noticed now that when I boot into fastboot mode the menu just locks up and doesn't respond to anything. Sometimes I have to pull the battery and other times it'll start responding after randomly pressing the power key a lot of times...
I'll try an older recovery next
Simultaneity said:
I haven't tried an older recovery and my bootloader is unlocked.
could it be a problem with my computer as opposed to the phone itself? As in my computer is messing up when trying to flash the recovery?
I've also noticed now that when I boot into fastboot mode the menu just locks up and doesn't respond to anything. Sometimes I have to pull the battery and other times it'll start responding after randomly pressing the power key a lot of times...
I'll try an older recovery next
Click to expand...
Click to collapse
Use Odin, that might solve your problems. Search for the Nexus S version of Odin in the Dev section here.
khartaras said:
Use Odin, that might solve your problems. Search for the Nexus S version of Odin in the Dev section here.
Click to expand...
Click to collapse
There's a version of Odin for the Nexus S!?!? I'll look into that straight away thanks!
Simultaneity said:
There's a version of Odin for the Nexus S!?!? I'll look into that straight away thanks!
Click to expand...
Click to collapse
Just look @ http://www.samfirmware.com/ .
There you should find all you need
Sent from my Full Android on Crespo using XDA App

[Q] Need help recovering my S3 -- TWRP ADB Sideload not working

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!

Help softbricked or hardbricked device?

Help softbricked device
well i was running more rom on the device when i droped it then i got the screen and digi replaced
and when the tech tuned it on for the first time after repair we got a udc start screen that says unknown error at the top
i can get to download mode though. but even after trying to restore the bootloader or flash a new modem i cant get to any recovery.
right now this is what it says in download mode.
odin mode
product name : SM-G900P
current binary: custom
system status : custom
knox warranty void 0x1 (4)
i can go to download mode or try and let it boot up to the samsung boot but it says recovery booting in blue and loops there on reboot.
i forget the name of the modem i was on in more rom. i think it was the one be4 ota6
but i want to update to latest version of modem and rom not sure where to start.
i cant seem to get back to stock or custom recovery at all. or even boot up to a rom now. and i honestly have no idea why? =( can someone help?
jackrabbit72380 said:
Help softbricked device
well i was running more rom on the device when i droped it then i got the screen and digi replaced
and when the tech tuned it on for the first time after repair we got a udc start screen that says unknown error at the top
i can get to download mode though. but even after trying to restore the bootloader or flash a new modem i cant get to any recovery.
right now this is what it says in download mode.
odin mode
product name : SM-G900P
current binary: custom
system status : custom
knox warranty void 0x1 (4)
i can go to download mode or try and let it boot up to the samsung boot but it says recovery booting in blue and loops there on reboot.
i forget the name of the modem i was on in more rom. i think it was the one be4 ota6
but i want to update to latest version of modem and rom not sure where to start.
i cant seem to get back to stock or custom recovery at all. or even boot up to a rom now. and i honestly have no idea why? =( can someone help?
Click to expand...
Click to collapse
Follow the instructions from this post. Since you are soft bricked at the moment, you'll need to start at step 4. If you have an extSD in your phone, you might want to pull it until after you're up and running because the "Android" folder from Kitkat needs to be deleted and rebuilt for Lollipop.
That's what I tryed first but it didn't work,
First step.... flash SM-G900P_OA6_FullRestore.
(on boot i have samsung galaxy s5 screen with blue letters at the top saying recovery booting and it loops.)
sense that didn't work i tryed... SM-G900P_NI3-Full_Restore_Unrooted (Compressed Archive)
(on boot i have samsung galaxy s5 screen with blue letters at the top saying recovery booting and it loops.)
then i tryed SM-G900P_OA6_FullRestore. again but still no luck im out of ideas
I cant get to any recovery.
please help.
jackrabbit72380 said:
That's what I tryed first but it didn't work,
First step.... flash SM-G900P_OA6_FullRestore.
(on boot i have samsung galaxy s5 screen with blue letters at the top saying recovery booting and it loops.)
sense that didn't work i tryed... SM-G900P_NI3-Full_Restore_Unrooted (Compressed Archive)
(on boot i have samsung galaxy s5 screen with blue letters at the top saying recovery booting and it loops.)
then i tryed SM-G900P_OA6_FullRestore. again but still no luck im out of ideas
I cant get to any recovery.
please help.
Click to expand...
Click to collapse
Are you using the wrong terminology? You have to use Odin and a PC to install the .tar. Also, the first boot into Lollipop can take about 20 minutes. You have to be patient. I see you posting in different threads and you seem to be digging deeper into a hole.
Are you using Odin and starting by downloading (to PC) the file in step #4? Then follow the remaining steps "exactly". Re-read those instructions and if you not already downloaded the needed files, do that first.
Ramer said:
Are you using the wrong terminology? You have to use Odin and a PC to install the .tar. Also, the first boot into Lollipop can take about 20 minutes. You have to be patient. I see you posting in different threads and you seem to be digging deeper into a hole.
Are you using Odin and starting by downloading (to PC) the file in step #4? Then follow the remaining steps "exactly". Re-read those instructions and if you not already downloaded the needed files, do that first.
Click to expand...
Click to collapse
Yes I downloaded the files to the pc.
Im using odin3.07
in pda I add the file Odin'd the [ODIN][TAR][5.0] SM-G900P OA6 (Official!) - Full Restore (ROM, Modem, Kernel),
put phone in download mode.
flash file!
ODIN SAYS PASS
next phone reboots to samsung galaxy black screen with with blue letters at the top saying
RECOVERY BOOTING......
then boot loops there.
I CANT GET TO STEP 5
I am not able to boot to the rom or recovery
jackrabbit72380 said:
Yes I downloaded the files to the pc.
Im using odin3.07
in pda I add the file Odin'd the [ODIN][TAR][5.0] SM-G900P OA6 (Official!) - Full Restore (ROM, Modem, Kernel),
put phone in download mode.
flash file!
ODIN SAYS PASS
next phone reboots to samsung galaxy black screen with with blue letters at the top saying
RECOVERY BOOTING......
then boot loops there.
I CANT GET TO STEP 5
I am not able to boot to the rom or recovery
Click to expand...
Click to collapse
Try this: Do a battery pull, then put the phone in Download mode, hook up to PC and then open Odin and then Odin custom recovery, either twrp or Philz. Uncheck auto reboot in odin and once it passes, pull the battery, unplug and boot into recovery. Also, you might update Odin, there's a link to Odin 3.10.0 in my post. Let's see if we can get that far and go from there.
ramer said:
try this: Do a battery pull, then put the phone in download mode, hook up to pc and then open odin and odin custom recovery, either twrp or philz. Uncheck auto reboot in odin and once it passes, pull the battery, unplug and boot into recovery. Also, you might update odin, there's a link to odin 3.10.0 in my post. Let's see if we can get that far and go from there.
Click to expand...
Click to collapse
ok used odin 10
tryied everything you said exactly phone reboots on samsung galaxy s5 boot logo everytime. Whether i try booting to recovery or the rom.
jackrabbit72380 said:
ok used odin 10
tryied everything you said exactly phone reboots on samsung galaxy s5 boot logo everytime. Whether i try booting to recovery or the rom.
Click to expand...
Click to collapse
Which recovery tar did you Odin? You pulled the battery after Odin said PASS, then unplugged the phone, put battery back in and immediately tried to get into recovery? If so, I'm stumped.
Ramer said:
Which recovery tar did you Odin? You pulled the battery after Odin said PASS, then unplugged the phone, put battery back in and immediately tried to get into recovery? If so, I'm stumped.
Click to expand...
Click to collapse
Yes I tryed
I pulled the battery after Odin said PASS
Yes I tryed
kt_twrp_recovery_boa6_firmware.tar
and
openrecovery-twrp-2.8.4.0-klte
and
philz_touch_6.57.8-klte
NOTHING!
when ever i try and boot the rom the phone vibrates 2 times and resets.
when ever i try to boot to recovery
i get
recovery booting....
recovery is not seandroid enforcing
set warranty bit : recovery
then phone reboots.
then it trys to boot the rom.
and vibrates 2 times and resets.
Im not new to using odin or flashing roms or recoverys i sort of know what im doing. not to sound cocky.
Im Stumped to!
jackrabbit72380 said:
Yes I tryed
kt_twrp_recovery_boa6_firmware.tar
and
openrecovery-twrp-2.8.4.0-klte
and
philz_touch_6.57.8-klte
NOTHING!
Im not new to using odin or flashing roms or recoverys i sort of know what im doing. not to sound cocky.
Im Stumped to!
Click to expand...
Click to collapse
I saw your post count, I knew you knew what you're doing, just wanted to double check everything. Sorry, I'm out of ideas. I did ask @tdunham to take a look at this thread, if he has some other ideas, but he's offline right now. Hopefully he'll check in later.
What about flashing back to an older version of android? Full tar flash.
---------- Post added at 12:38 AM ---------- Previous post was at 12:36 AM ----------
Like ne5, and nothing else, just see if you can get stock to boot, no messing around trying to flash recovery.
This is RWillco12's NE5 stock.. Have the phone in download mode and run the .exe
Thanks TD.
Ramer said:
This is RWillco12's NE5 stock.. Have the phone in download mode and run the .exe
Thanks TD.
Click to expand...
Click to collapse
I tryied ni3 already
but as far as i know you cant downgrade the bootloader.
if i could flash just the bootloader for ota6 maybe that would help.
i will try downloading ne5 now but my last rom was running a nkd modem.
im going to try and flash G900P_NKD_FullRestore.tar in odin if that dont work ill try ne5
and will report back shortly.
well nkd full restore boots up to
unknowen error!
wait..
done!
udc start.
power reset or
unknown
upload mode.
this is the way i got it back from retech after they replaced my bezel and digitlizer and screen
i never had an issue with anything software wize before that.
Have you tried flashing the phone without any sim cards inserted including the sprint card? You are flashing from a powered off state right? You know it wont work unless phone is powered off before going into download mode.
As a last resort attached is the pit file for the 16gb G900P. Unzip and put it into the pit section of odin and flash the stock firmware again. It will repartition the entire phone when it flashes the stock image.
tdunham said:
Have you tried flashing the phone without any sim cards inserted including the sprint card? You are flashing from a powered off state right? You know it wont work unless phone is powered off before going into download mode.
As a last resort attached is the pit file for the 16gb G900P. Unzip and put it into the pit section of odin and flash the stock firmware again. It will repartition the entire phone when it flashes the stock image.
Click to expand...
Click to collapse
Yes I was using the pit file and yes I know to go to download mode from power off state. and no sim card is in the phone.
flashing ne5 stock with fingers crossed.
brb
nope
is there any bootloaders only i can flash?
well tryed everything all it does is vibrate 2 times. same as be4 im dead in the water. i don't know what's wrong or what to do.
I have tryed everything i can think of.
I can boot to download mode and flash anything i want but nothing works.
no recovery. no rom.

Can't flash custom recovery on a XT925

Hi,
My wife just got a new phone and gave up her old XT925 so I thought I would try to put CM or SlimKat on it and let my daughter play around with it. But I'm having trouble putting a custom recovery on it. I've unlocked the bootloader. I've used fastboot to write the recovery image...but when I try to reboot directly into recovery so the binary update can complete, it pauses for a couple of minutes and then reboots the OS normally. If I try entering reovery after that, I end up with the dead android with a red exclamation point in him and "no command" written below.
The phone currently has 4.4.2 and System 181.46.3.XT925.RCI.en.CA. Am I out of luck with this device and stuck on 4.4.2?
Thanks!
What recovery did you try to flash ?
Use this one, it worked for me :
http://forum.xda-developers.com/showthread.php?t=2747535
Thanks. That one worked. I wonder why I had trouble with twrp.
Orionbell37 said:
What recovery did you try to flash ?
Use this one, it worked for me :
http://forum.xda-developers.com/showthread.php?t=2747535
Click to expand...
Click to collapse
pls update the link pls
Pausky said:
pls update the link pls
Click to expand...
Click to collapse
Its because you need to rename the stock recovery to .bak at the end of the file name. The stock recovery is getting in the way of you rebooting to TWRP or what ever custom recovery you are trying to use.
If you cant figure out how to do that or don't know where in system the stock recovery is just hit me up and ill give you the path to the file. After you rename the file just go back into fastboot and reflash the custom recovery and you should be able to reboot into TWRP or what ever custom recovery you want.

TWRP Boot Loop

Hi,
I tried yesterday to return my Nexus 5 to a stock image so that I could do OTA updates. I realised after that I also had to return it to stock recovery because TWRP was not letting it work.
using this tutorial, I booted into the latest TWRP image, which only caused my phone to go into a boot loop, only making it as far as the Teamwin screen. The phone will not load the bootloader to do anything with fastboot.
what are my options?
t.holley.os said:
Hi,
I tried yesterday to return my Nexus 5 to a stock image so that I could do OTA updates. I realised after that I also had to return it to stock recovery because TWRP was not letting it work.
using this tutorial, I booted into the latest TWRP image, which only caused my phone to go into a boot loop, only making it as far as the Teamwin screen. The phone will not load the bootloader to do anything with fastboot.
what are my options?
Click to expand...
Click to collapse
What do you want to do exactly? Restore stock recovery so that you can take the OTA? If you followed either one of the methods on that thread, you should already be stock, i don't get why you booted TWRP again.
Hi,
As I mentioned, following that tutorial, I just booted into the TWRP image. It wasn't that tutorial I used to flash the stock image. All that I did was get back to the stock android.
I originally did try using their method, but wasn't able to get the .sh script to run so I used another tutorial to flash the android image, but didn't have a boot or recovery that I flashed. I was able to download the update now and tried installing, but it would take me to the TWRP recovery and say that the update failed.
I was following the optional steps at the bottom, thinking that was what I needed to lock everything back up, clearly that wasn't right.
t.holley.os said:
Hi,
As I mentioned, following that tutorial, I just booted into the TWRP image. It wasn't that tutorial I used to flash the stock image. All that I did was get back to the stock android.
I originally did try using their method, but wasn't able to get the .sh script to run so I used another tutorial to flash the android image, but didn't have a boot or recovery that I flashed. I was able to download the update now and tried installing, but it would take me to the TWRP recovery and say that the update failed.
I was following the optional steps at the bottom, thinking that was what I needed to lock everything back up, clearly that wasn't right.
Click to expand...
Click to collapse
Just flash the stock recovery image with fastboot
Sent from my Nexus 9 using XDA Free mobile app
That's what I am asking...I can't load into anything on the Nexus to use fastboot, it is stuck loading into this TWRP image.
t.holley.os said:
That's what I am asking...I can't load into anything on the Nexus to use fastboot, it is stuck loading into this TWRP image.
Click to expand...
Click to collapse
Press and hold power for 30 second, the device will try to boot but just keep holding the power. Then press and hold vol down and power. It doesn't boot into the bootloader?
Sent from my Nexus 9 using XDA Free mobile app
Hi,
I tried this again today and was able to get into it. Yesterday it didn't want to boot into it for some reason. Followed the tutorial I posted from the start to re-flash everything, and so far seems to be working. Hasn't loaded into android yet, just stuck on the loading screen, hoping it's just the initial start up that sometimes takes a while.
t.holley.os said:
Hi,
I tried this again today and was able to get into it. Yesterday it didn't want to boot into it for some reason. Followed the tutorial I posted from the start to re-flash everything, and so far seems to be working. Hasn't loaded into android yet, just stuck on the loading screen, hoping it's just the initial start up that sometimes takes a while.
Click to expand...
Click to collapse
FYI the TWRP boot loops are due to MTP bug that was never fully fixed from 2860. It's better than it used to be, but still an issue occasionally, especially if connected to power while you try to get in to TWRP.

Categories

Resources