Related
Okay so I am trying to install the jdroid rom, btw first time ever doing this so bare with me, anyways I can't boot my phone stays at HTC quietly brilliant screen with some writing underneath it red. I can get into the bootloader menu, where I am rooted and says my bootloader is unlocked. I can also get into clockwork mod however I messed up when transferring the rom onto my phone. I unzipped it and put it there instead of leaving it in the zip file. I can't mount to my laptop through clockwork mod, is there any other way? Again I can't boot my phone. Thanks
EDIT: Now whenever my phone boots, it boots into the clockworkmod and keeps rebooting I can't do anything, cant mount my phone at all
Bizarre48 said:
Okay so I am trying to install the jdroid rom, btw first time ever doing this so bare with me, anyways I can't boot my phone stays at HTC quietly brilliant screen with some writing underneath it red. I can get into the bootloader menu, where I am rooted and says my bootloader is unlocked. I can also get into clockwork mod however I messed up when transferring the rom onto my phone. I unzipped it and put it there instead of leaving it in the zip file. I can't mount to my laptop through clockwork mod, is there any other way? Again I can't boot my phone. Thanks
Click to expand...
Click to collapse
Yes ... instal this recowery (Link to the latest unofficial test recovery with USB issues fixed and automount by RichardTrip) and you can push your zip on SD
Thanks for the reply
I used this command: fastboot flash recovery <Name Of the downloaded file>.img
But I'm still stuck at the boot screen
Bizarre48 said:
Thanks for the reply
I used this command: fastboot flash recovery <Name Of the downloaded file>.img
But I'm still stuck at the boot screen
Click to expand...
Click to collapse
You need to enter the fastboot mode ... hold "volume-down + powerbutton" for 10 secs and then again push the powerbutton to enter the fastboot mode.
Edit: and after that use the comand fastboot flash recovery nameofrecovery.img
Just saw the edit now will try thanks alot man appreciate it!
Bizarre48 said:
I did that, then when I went to recovery when it boots its at the htc quietly brilliant screen.
Click to expand...
Click to collapse
OK, did you instal the ROM + boot.img?
Edit: im going to sleep ... read THIS, if that doesnt help, then THIS
Okay I still can't do it nothing works! I flash the recoveries and I still get stuck at the htc boot screen. so frustrating
Bizarre48 said:
Okay I still can't do it nothing works! I flash the recoveries and I still get stuck at the htc boot screen. so frustrating
Click to expand...
Click to collapse
What you need to do when flashing:
a) CWM recovery
fastboot flash recovery xxxrecovery.img
fastboot reboot-bootloader
fastboot erase cache
b) Flashing a ROM
extract the boot.img from the ROM.zip
fastboot flash boot boot.img
fastboot erase cache
enter recovery
install the ROM.zip
reboot
READ THIS THREAD
http://forum.xda-developers.com/showthread.php?t=1609190
basically summarises what above posters are saying in step by step detail
Yea I'm just going to use the at&t ruu and restart to process all over again. hopefully this works
Bizarre48 said:
Yea I'm just going to use the at&t ruu and restart to process all over again. hopefully this works
Click to expand...
Click to collapse
Next time also read the instructions.
M.
as long as you can get the correct RUU and flash the correct stock recovery, RUU will defo work, then you can start again from scratch. I've done this myself
edit: AT&T????? Are you even in the correct forum using the correct files/methods??? HTC One XL is different forum, different files!!!!!!!!!!!!!!
Alright I got out of it using the st&t ruu, though I live in Canada and on Rogers. Data doesnt work but that is not surprise. Gotta wait for a root access and/or bootloader unlock for 1.85. will be patient.
Hello guys. I've been looking arround for a solution before posting my situation, but I didin't find any help, so I hope you can help me over.
The fact is that my phone is stuck in the bootloader mode. No matter what I do, anytime I turn it on, it goes directly to the bootloader mode and gives me a message that says "fastboot mode-no boot or recovery img" in red. Beside that, my bootloader is locked, and if I try to unlock it, it goes to the unlock screen, it ask me if I want to unlock it, but even if I say "YES", it doesn't unlock. I can't get into recovery mode, so it is impossible to restore any previous backup i've made.
I can get into download mode, but as soon as the odin starts to flash the ROM, the program crashes.
I tried to erase the boot image and the recovery image, but it just says "unknown partition".
Now, why all this did happen?, well I was trying to install the stock firmware that I downloaded from sammobile, and it never installed, the program crashed and my phone got... bricked????
If I could only unlock the bootloader it would be easier, i think.
Any help, please????
not sure if it will work on locked boot loader.... also don't use any tool, plain adb/fast boot
Errors you are getting doesn't say boot loader, but boot and recovery so try it.
Start phone in boot loader mode
Fastboot erase boot
Fastboot flash boot boot.img
Fastboot erase recovery
Fastboot flash recovery recovery.img
You can get both files from Google images.
Thanks for responding. I tried to erase the boot and recovery partition but...
This is what i get if i try to erase the boot partition
C:\Users\Casa\Desktop\Android\ADB for NEXUS S>fastboot erase boot
erasing 'boot'...
FAILED (remote: Unknown Partition)
finished. total time: 0.000s
Same thing if I try to erase the recovery image.
And if i try to flash the boot without deleting it, this is what i get:
C:\Users\Casa\Desktop\Android\ADB for NEXUS S>fastboot flash boot boot.img
sending 'boot' (4148 KB)...
OKAY [ 0.406s]
writing 'boot'...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 0.406s
This is really weird, i can't unlock the bootloader using "fastboot oem unlock". As I said before, it takes me to the unlocking screen, asks me if i'm sure, but even if I agree, the boot loeader is still locked. I really don't understand too much thisfar, but I think there's a problem with the partitions.
Any sugestion? I really need some help please...
Well if you're sure fastboot isn't working...
Have you tried ODIN? I think officially signed Odin.tar files can be flashed with a locked bootloader.
As much as Odin freaks me out (too damn finicky)...it can have it's uses.
Well i have already tried Odin, but the flashing process fails, as a fact it doesn't even flash the kernel.
Man, this is really weird. I can't unlock the bootloader, can't erase the boot nor the recovery image because partitions seems to be broken, damaged, lost, or I dunno; I can't flash a rom using Odin...
What can I do? I flashed an md5 file that I downloaded from sammobile (I9250XXKK1 ROM), and tried to flash it, and then my nightmare begun.
I really need some help, guys... I have posted the same problem in three different pages, and I have only gotten two answers, yours.
whats the error that odin gives you?
Have you tried using the Nexus Tool Kit?
Sent from my Galaxy Nexus using xda app-developers app
vikdal said:
Have you tried using the Nexus Tool Kit?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
that will not help him. all the toolkit does is use fastboot.
Zep, thanks for responding. I think that fastboot will not work for me , as you said some lines above, unless I manage to unlock the bootloader. Right now I'm at work (I really hate to work while my phone is bricked at home), so I can't tell you exactly the error I get while using Odin, but if you don't mind, i'll back home after work and i'll teel you the error I'm getting...
ok long shot try this
Get the cwm 6 img in fast boot folder
Fastboot boot cwm.img
Format data cache system
Flash some stable stock like rom or cm9 rc2. See what happens
atifsh said:
ok long shot try this
Get the cwm 6 img in fast boot folder
Fastboot boot cwm.img
Format data cache system
Flash some stable stock like rom or cm9 rc2. See what happens
Click to expand...
Click to collapse
he cant use fastboot.... can people really not read?
Zepius said:
he cant use fastboot.... can people really not read?
Click to expand...
Click to collapse
Huh, you should start reading buddy, he can use it just fine, he can't flash any thing is the issue.
atifsh said:
Huh, you should start reading buddy, he can use it just fine, he can't flash any thing is the issue.
Click to expand...
Click to collapse
really?
apolousm said:
Hello guys. I've been looking arround for a solution before posting my situation, but I didin't find any help, so I hope you can help me over.
The fact is that my phone is stuck in the bootloader mode. No matter what I do, anytime I turn it on, it goes directly to the bootloader mode and gives me a message that says "fastboot mode-no boot or recovery img" in red. Beside that, my bootloader is locked, and if I try to unlock it, it goes to the unlock screen, it ask me if I want to unlock it, but even if I say "YES", it doesn't unlock. I can't get into recovery mode, so it is impossible to restore any previous backup i've made.
Click to expand...
Click to collapse
sure looks like he cant use fastboot to me to flash anything.
stop it man, go see what he writes in response to my first reply.
Zepius said:
really?
sure looks like he cant use fastboot to me to flash anything.
Click to expand...
Click to collapse
Exactly! He can't write, Fastboot works just fine, it even send file ok, but failed to write.
atifsh said:
stop it man, go see what he writes in response to my first reply.
Click to expand...
Click to collapse
its clear you do not understand fastboot.
he cannot flash images with a locked bootloader using fasboot. period.
even in the referenced post you just gave me, it says:
C:\Users\Casa\Desktop\Android\ADB for NEXUS S>fastboot flash boot boot.img
sending 'boot' (4148 KB)...
OKAY [ 0.406s]
writing 'boot'...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 0.406s
Click to expand...
Click to collapse
he mentioned in the first post that he cannot unlock the bootloader for whatever reason.
Zepius said:
its clear you do not understand fastboot.
he cannot flash images with a locked bootloader using fasboot. period.
even in the referenced post you just gave me, it says:
he mentioned in the first post that he cannot unlock the bootloader for whatever reason.
Click to expand...
Click to collapse
stop replying to my posts and if you can help him, you are just making this thread useless.
Hi guys... I think I should explain this ... first of all thanks for trying to help
The fact is that I can't use fastboot (I think). Let me explain: If I try to unlock the bootloader it takes me to the unlock screen, and if I choose yes, the bootloader doesn't unlock.
So, if we consider the fact that I need to unlock the bootloader to use the fastboot, I think there's no chance to use the fastboot command.
I really, really, reaaaaaaally apretiate your help guys, your knowledge will be allways wellcome.
I understand that booth have your point of view, and try to help.
This is the first tmioe I see a prolem like this, I have reading arround and there are no similiar posts, I mean, that the bootloeader can't be unlocked... I found this ------> http://forum.xda-developers.com/showthread.php?t=1067815&page=2 and as saycnahd said "...I feel like I need A to do B, and B to do A....".
Thanls in advice you guys...
the error message that you get from ODIN will be very helpful. we dont need it to fully write a rom, just a couple things so that you can use fastboot to flash anything you need.
Ok, Zep... I get it :good: as soon as I can, I'll post the error... right now i'm seated at work, front of my computer, using my mama's phone right now I just remember that the Odin showed me a Fail message on a big red square on the upper left corner, where it is supposed to appear the progres dialog. I know it sounds pretty basic and useless for now.
Hi everyone, I'm new here and I have a GNex on my hands.
While I received it to fix; I could not get it past a bootloop from the nexus 4.0.4 Boot.
Problem is I cannot seem to get past the boot animation screen nor upgrade it.
Tried flashing another bootloader via fastboot, and the bootloader does not change, stays in same version.
HW Version : 9
Bootloader version : PRIMEKK15
Baseband version : I9250XXKK6
I proceed doing a fastboot erase bootloader and trying another bootloader, rebooting into another bootloader but no luck
Tried also ODIN flash but no luck; stays into the same
Booting into recovery mode goes into stock recovery and tries to flash a file from /cache
By trying to flash CWM via fastboot flash recovery <cwm image> flashes image but no luck on booting into CWM.
Anbody can lend a hand please?
Thanks!
jhonnyx said:
Hi everyone, I'm new here and I have a GNex on my hands.
While I received it to fix; I could not get it past a bootloop from the nexus 4.0.4 Boot.
Problem is I cannot seem to get past the boot animation screen nor upgrade it.
Tried flashing another bootloader via fastboot, and the bootloader does not change, stays in same version.
HW Version : 9
Bootloader version : PRIMEKK15
Baseband version : I9250XXKK6
I proceed doing a fastboot erase bootloader and trying another bootloader, rebooting into another bootloader but no luck
Tried also ODIN flash but no luck; stays into the same
Booting into recovery mode goes into stock recovery and tries to flash a file from /cache
By trying to flash CWM via fastboot flash recovery <cwm image> flashes image but no luck on booting into CWM.
Anbody can lend a hand please?
Thanks!
Click to expand...
Click to collapse
You can flash a custom recovery like cwm or twrp. Then you can acces the custom recovery and adb push your ROM and gapps. Then you do the wipes and flash the ROM and gapps. If you dont understand anything you just have to tell me
Sent from my Galaxy Nexus using XDA Premium HD app
Thanks mrgnex. I've tried flashing TWRP, but the only thing it does is boot into stock recovery and tries to flash a file from /cache/, which file is: 5a81769b6d01.signed-yakju-IMM76I-from-ICL53F.5a81769b.zip; pretty weird. Issue is the same as this thread: http://forum.xda-developers.com/showthread.php?t=1909331&page=4
use: fastboot boot recovery.img
and "recovery.img" which recovery do you suggest? twrp or a CWM in particular?
doesnt matter. whichever.
jhonnyx said:
and "recovery.img" which recovery do you suggest? twrp or a CWM in particular?
Click to expand...
Click to collapse
I suggest the latest TWRP.
http://www.teamw.in/project/twrp2
Edit: Have you read this?
TheMysteriousOne said:
I suggest the latest TWRP.
http://www.teamw.in/project/twrp2
Edit: Have you read this?
Click to expand...
Click to collapse
While now I'm trying to install latest TWRP (already did and no luck) I'm downloading the pack from the "Have you read this?".
The things that I'm seeing right now that seem to be wrong are:
1 - everytime I reboot the phone, the "fastboot oem unlock" seems to be gone and phone re-locks again (weird!)
2 - every change I make to the filesystem, seems to be non-persistent I/E: push something via adb push and on reboot it's gone! :/
Any help would be greatly appreciated.
jhonnyx said:
While now I'm trying to install latest TWRP (already did and no luck) I'm downloading the pack from the "Have you read this?".
The things that I'm seeing right now that seem to be wrong are:
1 - everytime I reboot the phone, the "fastboot oem unlock" seems to be gone and phone re-locks again (weird!)
2 - every change I make to the filesystem, seems to be non-persistent I/E: push something via adb push and on reboot it's gone! :/
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Can you elaborate on why exactly you were not able to install TWRP?
TheMysteriousOne said:
Can you elaborate on why exactly you were not able to install TWRP?
Click to expand...
Click to collapse
Surely:
1 - Unlock via fastboot oem unlock
2 - fastboot erase recovery (exits with ok)
3 - fastboot flash recovery twrp_versiondoesnotmatter.img (exits with ok)
4 - reboot w/power+vlup+voldown and select reboot recovery
5 - stock recovery appears
an alternate method that i've tried:
1 - Unlock via fastboot oem unlock
2 - fastboot boot twrp_versiondoesnotmatter.img (exits with ok)
3 - TWRP boots and flashes a zipfile from /cache/ then reboots automatically
That's what happens. A mistery, huh?
Also I've tried OMAP Flash, and; the same issue happens over and over again
Have you tried doing a factory reset using the stock recovery?
TheMysteriousOne said:
Have you tried doing a factory reset using the stock recovery?
Click to expand...
Click to collapse
AFAIK, Yes
What happens once I start the stock recovery; as I've already stated; starts flashing a zip file located into /cache/ (5a81769b6d01.signed-yakju-IMM76I-from-ICL53F.5a81769b.zip); then bleh, starts the bootloop again.
I've tried the power+volup then selected wipe cache and wipe system and it's the same.
Did you try flash google's stock images (all of them) ?
Also try flashing TWRP in the boot (kennel) partition by :-
Code:
fastboot flash boot <path to twrp>.img
This will force the phone into Recovery (But you will have recovery bootloop , can be solved by flashing a kernel) .
when you boot into recovery install a Kernel and ROM . also you will lose the recovery after that .
You can flash the TWRP from the TWRP itself (to put it in the right partition) by (in the build in terminal) :-
Code:
dd if=/<path to twrp in SD>.img of=/dev/block/mmcblk0p8
Good Luck .
Sent from my Galaxy Nexus using xda app-developers app
$Parker said:
Did you try flash google's stock images (all of them) ?
Also try flashing TWRP in the boot (kennel) partition by :-
Code:
fastboot flash boot <path to twrp>.img
This will force the phone into Recovery (But you will have recovery bootloop , can be solved by flashing a kernel) .
when you boot into recovery install a Kernel and ROM . also you will lose the recovery after that .
You can flash the TWRP from the TWRP itself (to put it in the right partition) by (in the build in terminal) :-
Code:
dd if=/<path to twrp in SD>.img of=/dev/block/mmcblk0p8
Good Luck .
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
fastboot flash boot <path to twrp>.img does not boot the recovery . I mean; still boots the normal Kernel.
Actually I'm trying what TheMysteriousOne told me by downloading the stock Gnex zip (250Mb) to flash via Odin.
Ohh, bad luck strikes again:
<ID:0/011> system.img
<ID:0/011> Complete(Write) operation failed.
cannot write system.img :/
Any ideas?
Unlock your bootloader with omapflash. Although even if it does unlock, Your emmc/board probably has died.
a manta wrote this.
beekay201 said:
Unlock your bootloader with omapflash. Although even if it does unlock, Your emmc/board probably has died.
a manta wrote this.
Click to expand...
Click to collapse
can you please me guide how to do the omapflash?
I've downloaded a file called OMAPFlash_tuna.zip.
- Set battery of the device aside
- Plug device into USB, let it detect the device and flash the SBF I think.
That'd be all?
beekay201 said:
Unlock your bootloader with omapflash. Although even if it does unlock, Your emmc/board probably has died.
a manta wrote this.
Click to expand...
Click to collapse
Pardon me, if EMMC/Board is dead; why does it boot or get into bootloop? There is something that reflashes itself; it even overrides odin or heimdall...
Have you tried going back to completely stock using the method outlined here? http://forum.xda-developers.com/showthread.php?t=1626895
jhonnyx said:
can you please me guide how to do the omapflash?
I've downloaded a file called OMAPFlash_tuna.zip.
- Set battery of the device aside
- Plug device into USB, let it detect the device and flash the SBF I think.
That'd be all?
Click to expand...
Click to collapse
Read this thread
http://forum.xda-developers.com/showthread.php?t=2016628
a manta wrote this.
I unlocked the Nexus 5X, installed TWRP recovery and then locked the bootloader again. Locking the bootloader stops TWRP from working and stops the phone from booting into Android. And since the phone is locked, it's impossible to install anything else via the bootloader or unlock it since Android doesn't boot. I think the phone is now permanently bricked and locked.
Don't have my phone yet, but can you boot into the bootloader? That's usually all you need to unlock the bootloader via fastboot. Did you try the skipsoft toolkit?
Shouldn't you just be able to power volume down boot into the bootloader. Then fastboot oem unlock and then go from there?
Sent from my Nexus 5X using Tapatalk
The_Automator said:
Shouldn't you just be able to power volume down boot into the bootloader. Then fastboot oem unlock and then go from there?
Click to expand...
Click to collapse
Nope. You have to enable unlocking from within Android before the device can be unlocked from the bootloader. And since Android won't boot up after the device is re-locked... "fastboot oem unlock" fails with "FAILED (remote: oem unlock is not allowed)".
Twrp is in the recovery partition, which is not the same partition the boot loader resides in.
Since the only way to lock the boot loader is via fastboot, and since you successfully did this, we know your boot loader is working. Get back into the boot loader and unlock your device. You can enter the boot loader via hardware key combination. Also, you can enter the boot loader even if the phone has no is and no recovery since it is independent of those.
_jordan_ said:
Twrp is in the recovery partition, which is not the same partition the boot loader resides in.
Since the only way to lock the boot loader is via fastboot, and since you successfully did this, we know your boot loader is working. Get back into the boot loader and unlock your device. You can enter the boot loader via hardware key combination. Also, you can enter the boot loader even if the phone has no is and no recovery since it is independent of those.
Click to expand...
Click to collapse
I can get into the bootloader no problem. In the bootloader, the DEVICE STATE is locked. When I do "fastboot oem unlock" it fails with:
FAILED (remote: oem unlock is not allowed)
This is because you must first enable unlocking in the Settings menu in Android before the fastboot command works. Android doesn't boot anymore since I re-locked the device, so there is no way to unlock the device...hence it is permanently bricked.
Interesting didn't know that the developer option for oem unlocking unchecked itself when you locked the bootloader. That seems pretty dangerous
Sent from my Nexus 5X using Tapatalk
Can you enter safe mode? I thought there's a safe mode function built into Android
Sent from my Nexus 5
Can't you just flash a stock recovery?
@simms22 they need your help here Same issues as w/ Nexus 6.
nyjumpman said:
Can't you just flash a stock recovery?
Click to expand...
Click to collapse
Nope. You can't flash stock images unless the device is unlocked. If I run "flash-all.sh" it says "FAILED (remote: device is locked. Cannot flash images)".
This phone is totally bricked.
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
Do these work?
I'm pulling out stuff from an interesting N9 thread
Which linked to this post
PhoenixTank said:
Do these work?
I'm pulling out stuff from an interesting N9 thread
Which linked to this post
Click to expand...
Click to collapse
Nope. "fastboot format userdata" returns:
FAILED (remote: device is locked. Cannot erase)
I'm not sure why your phone isn't booting into Android, since it's stock, but you could try a factory reset inside TWRP. If that doesn't work, did you make a back-up you can flash or sideload in TWRP? If not, you may have to wait until someone either uploads a flashable OTA, or a custom ROM you can flash in TWRP.
Edit: If none of these methods work, you could try pushing the stock images via TWRP and then a factory reset/wipe. I'm not sure if you can do this with a locked bootloader, though. Also, if the re-locking wiped your device, you'll have lost root, which will render this option useless.
ol2 said:
Nope. "fastboot format userdata" returns:
FAILED (remote: device is locked. Cannot erase)
Click to expand...
Click to collapse
When you are in TWRP (broken, right? but will it just hang on the logo?), can you get adb to work?
Can you get adb shell to work?
If yes,
This might provide some help.
Bear in mind, those dd commands probably aren't correct for this device. I don't have an n5x yet to check...
PhoenixTank said:
When you are in TWRP (broken, right? but will it just hang on the logo?), can you get adb to work?
Can you get adb shell to work?
If yes,
This might provide some help.
Bear in mind, those dd commands probably aren't correct for this device. I don't have an n5x yet to check...
Click to expand...
Click to collapse
Awesome idea. TWRP is broken but there's a slight delay before it reboots itself. I'm trying to get the timing right to issue some adb commands before the reboot.
I made this same stupid mistake on my Nexus 6 a while back. I locked the bootloader for some reason and then ended up in the same position. Using the following commands while in the bootloader solved it for me. It took me hours to figure it out. In fact, I think Simms was the one who recommended it.
fastboot format userdata
fastboot format cache
If they are not working for you, then I wish you the best of luck. I feel your pain man.
The_Automator said:
Interesting didn't know that the developer option for oem unlocking unchecked itself when you locked the bootloader. That seems pretty dangerous
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I agree. I will have to keep it in mind and the geniuses that write guides hopefully will mention it.
Edit: Crud, that sounded sarcastic. It wasn't.
How about fastboot boot twrp-bullhead-blah.img
This will boot into twrp but not flash it. Adb will work if you can get in.
Also, try just flashing the os image file with fastboot update image-bullhead-marshmallow-delta-tango.zip (unzipb from the factory image)
The flash all command will try to flash the bootloader which is forbotten.
Make sure you are using the latest fastboot too. There are some new commands- flashboot flashing unlock blah to unlock the non-bootloader bits. I'm not sure if it will work for you, but at this point it can't hurt.
I don't think that you are locked out just yet.
Have you tried flashing factory images in fastboot?
My phone started acting really laggy today and began restarting by this evening. The restarts became more and more frequent and now I can't do anything with it. The phone is unlocked and was rooted with xposed. I can get into the bootloader and fastboot works fine. I cannot, however, get into recovery. The phone displays the unlocked warning, then the Google screen with the unlocked symbol on the bottom, and then it repeats.
Through fastboot, I flashed the newest update without wiping my data - didn't work. Then I extracted the zip file and flashed everything (radio, bootloader, recovery, system, etc..) and no change. I repeated the process with an older version just to see if there was a difference.. nope. Everything installs just fine but I get the same bootloop and inability to get into recovery. I also flashing TWRP, but no change.
Am I screwed? I voided my warranty when I unlocked the bootloader, right?
redg8gt said:
My phone started acting really laggy today and began restarting by this evening. The restarts became more and more frequent and now I can't do anything with it. The phone is unlocked and was rooted with xposed. I can get into the bootloader and fastboot works fine. I cannot, however, get into recovery. The phone displays the unlocked warning, then the Google screen with the unlocked symbol on the bottom, and then it repeats.
Through fastboot, I flashed the newest update without wiping my data - didn't work. Then I extracted the zip file and flashed everything (radio, bootloader, recovery, system, etc..) and no change. I repeated the process with an older version just to see if there was a difference.. nope. Everything installs just fine but I get the same bootloop and inability to get into recovery. I also flashing TWRP, but no change.
Am I screwed? I voided my warranty when I unlocked the bootloader, right?
Click to expand...
Click to collapse
Curious, what happens if you flash recovery.img into the boot partition?
It's a nexus device so you should be ok with warranty and an unlocked bootloader.
Sent from my Nexus 9 using XDA Free mobile app
redg8gt said:
My phone started acting really laggy today and began restarting by this evening. The restarts became more and more frequent and now I can't do anything with it. The phone is unlocked and was rooted with xposed. I can get into the bootloader and fastboot works fine. I cannot, however, get into recovery. The phone displays the unlocked warning, then the Google screen with the unlocked symbol on the bottom, and then it repeats.
Through fastboot, I flashed the newest update without wiping my data - didn't work. Then I extracted the zip file and flashed everything (radio, bootloader, recovery, system, etc..) and no change. I repeated the process with an older version just to see if there was a difference.. nope. Everything installs just fine but I get the same bootloop and inability to get into recovery. I also flashing TWRP, but no change.
Am I screwed? I voided my warranty when I unlocked the bootloader, right?
Click to expand...
Click to collapse
try clean flashing a stock image in fastboot. wipe everything.
k.s.deviate said:
try clean flashing a stock image in fastboot. wipe everything.
Click to expand...
Click to collapse
I manually flashed everything that the flash-all.bat file does, twice. I'm going to try to get it replaced with the warranty.
I can't help but think it is a hardware problem given that everything seems to work perfectly flashing it with factory images and then nothing happens when I try to boot it up.
sfhub said:
Curious, what happens if you flash recovery.img into the boot partition?
Click to expand...
Click to collapse
... is this different than flashing using fastboot? I flashed the stock recovery several times and redownloaded and tried again. TWRP didn't work either.
redg8gt said:
... is this different than flashing using fastboot? I flashed the stock recovery several times and redownloaded and tried again. TWRP didn't work either.
Click to expand...
Click to collapse
What I was suggesting is
fastboot flash boot recovery.img
previously you would have been trying
fastboot flash boot boot.img
fastboot flash recovery recovery.img
I was suggesting flashing your boot partition using the recovery.img on the assumption that the recovery partition emmc might be damaged along with parts of the user partition.
If the boot partition area of the emmc is still good, flashing the recovery.img in there will allow recovery to startup.
Recovery and boot are basically 95% the same image. The partitions sizes are the same. So basically from a flashing standpoint, they are interchangeable.
The difference is the boot partition is automatically selected by the boot loader, while the recovery partition needs special button presses to start.
If you flash the boot partition with the recovery.img, then recovery should just start up automatically without special button presses.
sfhub said:
What I was suggesting is
fastboot flash boot recovery.img
previously you would have been trying
fastboot flash boot boot.img
fastboot flash recovery recovery.img
I was suggesting flashing your boot partition using the recovery.img on the assumption that the recovery partition emmc might be damaged along with parts of the user partition.
If the boot partition area of the emmc is still good, flashing the recovery.img in there will allow recovery to startup.
Recovery and boot are basically 95% the same image. The partitions sizes are the same. So basically from a flashing standpoint, they are interchangeable.
The difference is the boot partition is automatically selected by the boot loader, while the recovery partition needs special button presses to start.
If you flash the boot partition with the recovery.img, then recovery should just start up automatically without special button presses.
Click to expand...
Click to collapse
I think you mean fastboot boot recovery.img. Not fastboot flash boot recovery.img. That'll hopefully boot you into recovery without actually flashing it.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I think you mean fastboot boot recovery.img. Not fastboot flash boot recovery.img. That'll hopefully boot you into recovery without actually flashing it.
Click to expand...
Click to collapse
Nope, I actually meant what I wrote. I wanted to test the theory that the emmc in the recovery partition is damaged and the easiest way to do that is to flash the recovery onto the boot partition, which might not be damaged.
The partitions are the same size so you won't damage the phone, you'll just cause the phone to boot the kernel which autostarts recovery instead of the kernel that tries to boot android.
fastboot boot recovery.img will just load recovery straight into memory across the USB cable. It won't allow diagnosis of whether the emmc in that section is damaged.
Ok, but if the EMMC is bad in any partition the device is still hosed.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Ok, but if the EMMC is bad in any partition the device is still hosed.
Click to expand...
Click to collapse
Actually that isn't necessarily true. While Emmc can have catastrophic failure, Emmc often has partial failure.
We discovered this when google added SecureTRIM to the kernel on the Samsung Epic Touch. The emmc was getting corrupted by this change and we found that we could lock out certain sections of the emmc by adjusting partition tables and have a functioning phone.
I figure this phone is going back for RMA anyway, so might as well get some useful failure analysis out of it.
redg8gt said:
My phone started acting really laggy today and began restarting by this evening. The restarts became more and more frequent and now I can't do anything with it. The phone is unlocked and was rooted with xposed. I can get into the bootloader and fastboot works fine. I cannot, however, get into recovery. The phone displays the unlocked warning, then the Google screen with the unlocked symbol on the bottom, and then it repeats.
Through fastboot, I flashed the newest update without wiping my data - didn't work. Then I extracted the zip file and flashed everything (radio, bootloader, recovery, system, etc..) and no change. I repeated the process with an older version just to see if there was a difference.. nope. Everything installs just fine but I get the same bootloop and inability to get into recovery. I also flashing TWRP, but no change.
Am I screwed? I voided my warranty when I unlocked the bootloader, right?
Click to expand...
Click to collapse
Try to do a factor oem lock and then unlock to completely wipe the phone , then try to adb sideload stock 6.0.1 ?
okay here's what you need to do:
1) Try the LG UP tool. There's a thread somewhere in 5x forums. 90% chances are that it will fix everything as it repartitions back to stock.
2) If the above does not work, then do this: Download the platform tools, shift right click, open command prompt, switch off the phone, connect it to pc and power on. Once you are past the google logo, type adb devices, it should show up there on the pc, if it doesn't then try the command again. once the device shows up on the command prompt, type adb logcat, once you have around 3-4 minutes of boot up logs on the cmd, copy everything and post it here, one of us will take a look and tell you what exactly is the problem.
Here is the link, http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740. Member bitdomo has been a savior on many nexus devices.
Sent from my Nexus 9 using XDA Free mobile app
The phone is indeed heading back to Google for a (refurb) replacement. I had tried to directly boot into recovery using both the stock recovery and twrp and had the same result. For the sake of science, I will try the LG tool later and see if I can get it working.
sfhub said:
What I was suggesting is
fastboot flash boot recovery.img
previously you would have been trying
fastboot flash boot boot.img
fastboot flash recovery recovery.img
I was suggesting flashing your boot partition using the recovery.img on the assumption that the recovery partition emmc might be damaged along with parts of the user partition.
If the boot partition area of the emmc is still good, flashing the recovery.img in there will allow recovery to startup.
Recovery and boot are basically 95% the same image. The partitions sizes are the same. So basically from a flashing standpoint, they are interchangeable.
The difference is the boot partition is automatically selected by the boot loader, while the recovery partition needs special button presses to start.
If you flash the boot partition with the recovery.img, then recovery should just start up automatically without special button presses.
Click to expand...
Click to collapse
I just tried this. Still bootloops.
Siddheshpatil said:
okay here's what you need to do:
1) Try the LG UP tool. There's a thread somewhere in 5x forums. 90% chances are that it will fix everything as it repartitions back to stock.
2) If the above does not work, then do this: Download the platform tools, shift right click, open command prompt, switch off the phone, connect it to pc and power on. Once you are past the google logo, type adb devices, it should show up there on the pc, if it doesn't then try the command again. once the device shows up on the command prompt, type adb logcat, once you have around 3-4 minutes of boot up logs on the cmd, copy everything and post it here, one of us will take a look and tell you what exactly is the problem.
Click to expand...
Click to collapse
1) I think I'm going to keep it broken so there is no issue whenever I send it in. I wish I would have waited to call Google. I'm curious now whether that would have worked.
2) There is no past the Google logo.. it resets before it gets past it.
redg8gt said:
I just tried this. Still bootloops.
Click to expand...
Click to collapse
Could you try 2 other things
1) try the fastboot boot recovery.img suggested earlier to confirm your recovery image can boot across USB cable
2) if not, please post a SHA1 hash for your recovery.img and which Android version you got the image from
This will just confirm that the recovery image that you are using is bootable in absence of the EMMC and if not, confirm whether the recovery.img is corrupted or not.
I experienced something similar when I moved from MM to N without wiping data. The data partition got encrypted even though I flashed that fedpatcher. Just couldn't get into twrp beyond its splash screen. The issue here might be unrelated, but I'd suggest a format userdata.
I got this problem a month ago , tried wiping everything and flash stock using fastboot command , then i got 9008 mode .
No recovery no downloads mode no fastboot . (Sometimes can go to fastboot try flash using nrt / manually , nothing happend)