Related
UPDATE 3: I've got it back to as stock as I can get it. I think I'm going to just return it and get a new one. Thank you all for your help.
UPDATE 2: As of right now, I'd like to completely remove FFF from the device, but I can only use fastboot to do it. I have absolutely no adb access. Is there a way?
UPDATE: Here is a video showing what is happening to my KF: http://www.youtube.com/watch?v=MH6oUg1NmC0
I hate to start another thread about boot loops/bricking, but I'm not sure what's going on with my fire.
I had CM7 installed successfully since the day after Christmas. This morning I woke up and my Fire was being really sluggish, so I rebooted it (I did not select reboot into recovery).
After it powered on, I was stuck at the CM7 boot screen (with the skateboarding android). I let it sit, but no luck. I went into TWRP to try and restore the backup I made of the stock rom. It looked successful, but when I rebooted I was stuck at the Kindle Fire boot screen.
Next, I tried wiping the device and re-installing CM7, but I received an error (something along the lines of E:Error unable to find /tmp/sideload/blahblah).
So I again restored my backup of the stock rom. Now when I power on my Fire I see the yellow triangle, then the kindle fire logo, yellow triangle, kindle fire logo, and it just keeps repeating. The problem is I am unable to connect to adb because the PC only seems to recognize the adb device for a few seconds after the yellow triangle, which does not give me enough time to fix the problem.
Any ideas?
looks like you'r out of battery ! the kf is rebooting !
would take the wall charger and charge for an hour
it's not possible to charge with the computer - it lasts forever
then it should respond in a stable state
b63 said:
looks like you'r out of battery ! the kf is rebooting !
would take the wall charger and charge for an hour
it's not possible to charge with the computer - it lasts forever
then it should respond in a stable state
Click to expand...
Click to collapse
Recovery shows my battery level to be at 53%. I've got it on the charger now, but I have a feeling there is something else going on.
Also, I am unable to mount my Fire's SD to my computer in recovery. It looks like it is working, but my computer never acknowledges it.
maybe because your last installation failed
nevertheless i would try to charge and then go in twrp and retry the installation
if that's not sucessful i would try to switch the kf to fastboot and copy a new rom. stock or prerooted stock or cm7 - whatever you like
in twrp there is a point "mount" - sdcard - then you should get it from computer
b63 said:
maybe because your last installation failed
nevertheless i would try to charge and then go in twrp and retry the installation
if that's not sucessful i would try to switch the kf to fastboot and copy a new rom. stock or prerooted stock or cm7 - whatever you like
in twrp there is a point "mount" - sdcard - then you should get it from computer
Click to expand...
Click to collapse
Thanks for the reply. Is adb required to get into fastboot? The problem is that I am unable to get into adb because my computer only sees the Fire for about 1 second. When I go into device manager, I don't see it at all.
EDIT: Yeah, I see the mount in TWRP, but it does not do anything when I select it.
Hi Im a beginner but Id like to try to help :
In case you become desperate ignore twrp's battery display and try wall charger.
Anorher idea id have is to shut down throughr twrp and start up then instead of rebooting.
ADB is needed to get into fastboot, but it's quick. If you use KFU, you can probably hit the option during the couple seconds you have available. I would say your best bet, however, is booting into twrp, doing a full wipe of system, cache, davlik cache, and maybe data, and then trying the rom install again.
skourg3 said:
ADB is needed to get into fastboot, but it's quick. If you use KFU, you can probably hit the option during the couple seconds you have available. I would say your best bet, however, is booting into twrp, doing a full wipe of system, cache, davlik cache, and maybe data, and then trying the rom install again.
Click to expand...
Click to collapse
So this time it looks like the installation worked in TWRP, but after reboot now I'm stuck at the CM7 boot screen. This is at least some progress, so when I get home I'll see what I can do.
Sent via my internet connected mobile cellular telephone.
Well, the battery is definitely not the issue. I've been trying to get fastboot, but the problem is the fact that I can not get adb. Has anyone else had issues with getting adb? I've already tried to install the drivers, and that doesn't work.
EDIT: I've tried issuing "adb devices" from the command prompt repeatedly as soon as I hear the ding until it disconnects a second later, but still I have had no luck.
Also, I found this thread in which someone else appears to have had a similar issue to mine.
[Q] New kind of unfixable Super Brick?
at the moment adb is useless - you should try to get the device in fastboot mode - correctly recognised from your computer - then work with fastboot commands - if you don't get that then your next opinion is buying or making a factory cable - but we should try to avoid that ...
b63 said:
at the moment adb is useless - you should try to get the device in fastboot mode - correctly recognised from your computer - then work with fastboot commands - if you don't get that then your next opinion is buying or making a factory cable - but we should try to avoid that ...
Click to expand...
Click to collapse
I can not seem to get fastboot to work either. Does fastboot rely on adb? Or do you just run the .exe file? I tried to run it, and nothing happened.
fastboot has nothing to do with adb - calling just the exe does nothing -
you have to issue fastboot commands
ok have reread the whole thread and have some ideas:
your currently stuck at the cm7 boot screen ?
have you used the "stock rom version" to wipe data and cache partitions as described here ?
http://forum.xda-developers.com/showthread.php?t=1390773
perhaps it will help to wipe data/cache with twrp ...
b63 said:
fastboot has nothing to do with adb - calling just the exe does nothing -
you have to issue fastboot commands
ok have reread the whole thread and have some ideas:
your currently stuck at the cm7 boot screen ?
have you used the "stock rom version" to wipe data and cache partitions as described here ?
http://forum.xda-developers.com/showthread.php?t=1390773
perhaps it will help to wipe data/cache with twrp ...
Click to expand...
Click to collapse
Just wanted to let you know I updated the OP with a video showing what is happening to my KF.
Haven't tried that particular rom yet, but I have wiped data and cache and attempted to re-install CM7.
great idea with the video !!!
b63 said:
fastboot has nothing to do with adb - calling just the exe does nothing -
you have to issue fastboot commands
ok have reread the whole thread and have some ideas:
your currently stuck at the cm7 boot screen ?
have you used the "stock rom version" to wipe data and cache partitions as described here ?
http://forum.xda-developers.com/showthread.php?t=1390773
perhaps it will help to wipe data/cache with twrp ...
Click to expand...
Click to collapse
OK, so I restored my original rooted kindle rom, but I still can't get into fastboot because of the problem I showed in the video. It is doing exactly the same thing, just instead of the CM7 boot screen, it is the Kindle Fire boot screen.
Is is possible to get into fastboot without the computer? Can anyone think of a reason why I would not be able to mount my device in TWRP?
I just want to understand something about fastboot... can you upload and flash roms with it? Or can you only get TWRP / FFF with it? I ask because I already have them, and I still can't do anything (mount from inside TWRP doesn't work). Thanks!
Sent via my internet connected mobile cellular telephone.
with fastboot you can install the newest fff and if you need twrp
but with the newest fff you can issue ""fastboot oem format"
see here:
http://forum.xda-developers.com/showthread.php?t=1369405
that should solve every issue ...
b63 said:
with fastboot you can install the newest fff and if you need twrp
but with the newest fff you can issue ""fastboot oem format"
see here:
http://forum.xda-developers.com/showthread.php?t=1369405
that should solve every issue ...
Click to expand...
Click to collapse
Cool. I just ordered one of SkOrPn's cables, so once I get it I'll be sure to give an update. Thanks for all the help so far!
The cable isn't need when you have the FFF bootloader, in fact, when your computer does see the device for the short amount of time shown in the video, fastboot is active. It's a feature of FFF. Fastboot is a command line tool like adb but is used for different things. It comes in Android sdk which if you have that, you should update the tools packages in the Android manager and it will update adb and fastboot. It looks like something is not working correctly in twrp and the OS is failing to load. I'm not sure you need to oem format tho.....
At some point you had to have used fastboot to install twrp and/or FFF.... Unless you used adb dd? :what:
Anyway, I can help more but it's late where I am, need to sleep. Was going to write more but... Need sleep lol. I'll post some questions and check back tomorrow.
Have you used adb before? Do you know if platform-tools is in your environment variables PATH? In other words, can you open up cmd and type adb or do you need to "cd" to platform-tools then use adb? If you know where adb is located? If so, is a file called fastboot in there? (Maby called fastboot.exe)
foxdog66 said:
The cable isn't need when you have the FFF bootloader, in fact, when your computer does see the device for the short amount of time shown in the video, fastboot is active. It's a feature of FFF. Fastboot is a command line tool like adb but is used for different things. It comes in Android sdk which if you have that, you should update the tools packages in the Android manager and it will update adb and fastboot. It looks like something is not working correctly in twrp and the OS is failing to load. I'm not sure you need to oem format tho.....
At some point you had to have used fastboot to install twrp and/or FFF.... Unless you used adb dd? :what:
Anyway, I can help more but it's late where I am, need to sleep. Was going to write more but... Need sleep lol. I'll post some questions and check back tomorrow.
Have you used adb before? Do you know if platform-tools is in your environment variables PATH? In other words, can you open up cmd and type adb or do you need to "cd" to platform-tools then use adb? If you know where adb is located? If so, is a file called fastboot in there? (Maby called fastboot.exe)
Click to expand...
Click to collapse
Yep, I've used adb successfully, and it is set up as an environmental variable. I actually installed FFF and TWRP with the KFU. Problem is I think something else is botched; perhaps it is TWRP itself, since I am unable to mount from TWRP. I'll try again when I get home.
Sent via my internet connected mobile cellular telephone.
This is one I haven't seen in the forums -
Last night I used KFU 093 to permanently root my phone, flash firefirefire bootloader and the twrp recovery module, followed by a flash of CM7 with a twrp backup and the KF as a second backup. All did not go smoothly but i knuckled down and with the help of the forums - i got there. i was hoping to use twrp to switch between backups of CM7 and the KF OS as needed but as of this morning i'm not seeing the firefirefire bootloader screen anymore and so i can't boot into recovery using the power button.
i tried to use kfu again today to re-flash firefirefire but now am getting an "access denied - the bootloader was not flashed" message on my kindle even though the kfu says the flash was successful. rebooting the kf demonstrates firefirefire was not flashed.
Any ideas what might be causing the "access denied" message? I checked and su access is allowed... any help would be greatly appreciated! Thank you.
PS i'm running Win 7 and KF 6.2.2.
I used KFU 093 to permanently root my phone
Click to expand...
Click to collapse
i assume you mean the kf ?
never seen such failure - sounds like messed partitions
if you get it to fastboot somehow you could try to hotboot the bootloader
by "fastboot -i 0x1949 boot bootloader u-boot.bin" and
try to restore factory partitioning with "fastboot oem format"
if you have to format it maybe this thread can help you further:
http://forum.xda-developers.com/showthread.php?t=1403337
maybe you'll need a factory cable to get to fastboot:
http://forum.xda-developers.com/showthread.php?t=1392693
Minor detail - yes the kindle fire.
I had not thought about partitions - perhaps that's the issue. I haven't had the best of luck getting it into fastboot - with the utility or by command prompt. The driver issues with the KF are absurd. Any experience with Firekit? http://forum.xda-developers.com/showthread.php?t=1430038
Perhaps I will need to get a factory cable (which by the way appear to finally be in stock: http://forum.xda-developers.com/showthread.php?t=1430038).
Is there any way for me to confirm it is a partition issue before reformatting?
Thanks again!
Btw I have been ripping off sound advice from you on these forums for a few days now - since I got myself addicted to this whole mess. I owe you already!
the thing with the drivers sounds more complicated than it is - i have written a quite long post about this: http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
i have no experience with firekit but as linux needs no drivers and the firekit is prepared exactly for the kf it should work fine - it had done for many others
if you don't have adb commands available i don't know a way to check the partitions
and to have a factory cable is allways a good idea - i have one from scorpn allthough i never needed it - just good to have
My Nexus 10 was on Android 4.3 rooted and unlocked. Upgrade to 4.4 via OTA would not work.
I used WugFresh Nexus Rootkit 1.79, and was about to upgrade from Android 4.3 to 4.4, but first ran Flash Stock and unroot so I would be able to accept OTA updates. Unfortunately, the program halted when it completed the requested action, and I am left in fastboot. The tablet is stuck in fastboot mode, and no matter which option I try it always comes back to fastboot mode. Also I have tried to initiate custom recovery, via power and Volume up, but again to no avail.
USB debugging was active, and I had CWM recovery and root.
When I go to 'Restart Bootloader', (or 'Recovery Mode' or 'Start') the tablet immediately reboots back to 'Start'. Thankfully the 'Power Off' button does actually stop the tablet.
I have tried to see if I could get to Stock Recovery from fastboot, but that gives no response beyond going to the next tab.
Is anyone able to provide assistance in recovering from this dilemma?
First make sure bootloader is unlocked, if not
fastboot oem unlock
Then fastboot wipe
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now grab latest twrp or clockwork image
fastboot flash recovery nameofrecovery.img
Then boot to new recovery
For fun format all partitions available to in there
Now go to advanced, adb sideload
adb sideload romofchoice.zip
Then probably need gapps
adb sideload gapps.zip
Now reboot
This will get you up and running, if you absolutely want stock and non rooted let me know and I'll help you get there, but I will advise not to bother with toolkits as most every "help me fix xxxxxx" is from a toolkit user
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
First make sure bootloader is unlocked, if not
fastboot oem unlock
Then fastboot wipe
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now grab latest twrp or clockwork image
fastboot flash recovery nameofrecovery.img
Then boot to new recovery
For fun format all partitions available to in there
Now go to advanced, adb sideload
adb sideload romofchoice.zip
Then probably need gapps
adb sideload gapps.zip
Now reboot
This will get you up and running, if you absolutely want stock and non rooted let me know and I'll help you get there, but I will advise not to bother with toolkits as most every "help me fix xxxxxx" is from a toolkit user
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Many thanks for your response demkantor.
Although I tried to clearly describe the status of the tablet and the problem, I did not intend that I should come across as one who is familiar with the complexities of programming of either the tablet, or rooting around in the registry of a PC.
I can however follow clear instructions.
Your message appears to give a list of what to do, and presumably in the tablet from within fastboot. But I am lost after that.
By the way, the bootloader is unlocked.
Since the fastboot is currently inoperable, how do I initiate fastboot wipe, and then the following 3 commands 'erase system-w, boot & recovery'?
If you can spare the time and expand on your listing, I would certainly appreciate it.
http://forum.xda-developers.com/showthread.php?t=2277112
Sent from my Nexus 4 using XDA Premium 4 mobile app
Wow demkantor many thanks! The link you provided will take a bit of reading after I get back from the gym. A full afternoon ahead I suspect! I'll let you know how I go.
Just let me know if you get stuck
Sent from my Nexus 4 using XDA Premium 4 mobile app
Hi demkantor,
All done and dusted. Many thanks for your help, My tablet is now running on KitKat 4.4.2.
Your contributions to XDA University are very well arranged and written, and logically guide us through the maze. I for one did not know XDA University existed, and it is a shame that you as the person who pulled your contributions together have to also point us to it!
Many thanks for your efforts!
Edit - I read somewhere that the [Q] at the start of the thread should be changed to something else when the problem is resolved. It certainly is! Can the moderator correct this for me please?
Demkantor, I think I may have screwed up big time. I am unlocked and rooted, running stock 4.4. I woke up yesterday and had a notification that a system update had been downloaded. I did a temporary unroot and took the update. Which failed. I went into twrp and wiped everything. Still no go.Then, like a dummy I rebooted after it gave me a warning about not having an os installed. It wont do anything now except go into bootloader. I must have wiped twrp, because it wont boot into that or stock recovery. When I plug it up to my computer,I get this message( fastboot status-failInvalid command). I've just about every option in wugs toolkit. I keep getting adb and fastbooterrors. Have I completely hardbricked my nexus 10? I would appreciate it if you could point me in the right direction or let me know if I'm just wasting my time. I've been messing with this thing since around midnight and I'm about ready to start pullnig hair out of my head. Thanks in advance my friend.
@63t061
Thanks for the kind words, ive been busy lately (finals and all) so normally i would helped more personally but im glad you were able to get it all working on your own through research, which is the best way as im sure you have learned much and will be able to share with the next! Great job! As for editing the thread title, just edit it in your first post @moejoe88
Can you post all input output from cmd/terminal as its easier to see the issue. And try not use tool kits
Start with
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery recovery.img
Sent from my SGH-T699 using XDA Premium 4 mobile app
Thanks for replying so quickly. I've had to walk away from it for a little while and get some sleep. I'll get some rest and make a fresh start of it. Again, thanks for the quick reply.
I've tried running terminal and the computer wont even recognize the tablet. I believe the battery is drained because I can get it to the bootloader, but it shuts back off after a few minutes. I'm trying to charge for a while and I'll give it another shot. Thanks again.
This is the whole situation:
I have Pure Nexus installed on my 6P, running great for months. Suddenly yesterday it rebooted while I was using it and sticking in a bootloop. "No problem", I thought, and wanted to reboot into recovery - but nope, can't access it anymore. So I tried to reflash the recovery when I got home, but I only get errorors
When using the command adb devices the line just stays blank. The same with fastboot commands, besides "Fastboot devices"
After messing around a couple hours with the drivers and so on, I managed to somehow get the fastboot command working again. But no sign for the ADB commands, probably because I didn't turn on USB-debugging.
I am now at the point, where I have reflashed Stock Android with the Nexus Root Toolkit and managed to get back into stock android recovery, but still can't get TWRP to boot. I didn't want to delete my personal data, but I saw no other way and formatted /data in stock recovery. But the problem with the bootloop is still there.
It's not the classic bootloop, it boots as far as the Google Logo, then shuts itself down and begins again. I have now reached the point where I have to say, that the hardware might be damaged too. I'd love to somehow get access to the internal storage at least, but I can't without a working ADB.
Reinstalled TWRP with every available version, none of them worked. I am able to access stock Android recovery, but adb commands aren't working from here anyway.
Is there an option to fix the recovery mode? If I could get this working, the rest would be easy for me.
Edit: The reboot looks like in this Link. Only difference is, my device doesn't even the reach the dots.
StarShoot97 said:
This is the whole situation:
I have Pure Nexus installed on my 6P, running great for months. Suddenly yesterday it rebooted while I was using it and sticking in a bootloop. "No problem", I thought, and wanted to reboot into recovery - but nope, can't access it anymore. So I tried to reflash the recovery when I got home, but I only get errorors
When using the command adb devices the line just stays blank. The same with fastboot commands, besides "Fastboot devices"
After messing around a couple hours with the drivers and so on, I managed to somehow get the fastboot command working again. But no sign for the ADB commands, probably because I didn't turn on USB-debugging.
I am now at the point, where I have reflashed Stock Android with the Nexus Root Toolkit and managed to get back into stock android recovery, but still can't get TWRP to boot. I didn't want to delete my personal data, but I saw no other way and formatted /data in stock recovery. But the problem with the bootloop is still there.
It's not the classic bootloop, it boots as far as the Google Logo, then shuts itself down and begins again. I have now reached the point where I have to say, that the hardware might be damaged too. I'd love to somehow get access to the internal storage at least, but I can't without a working ADB.
Reinstalled TWRP with every available version, none of them worked. I am able to access stock Android recovery, but adb commands aren't working from here anyway.
Is there an option to fix the recovery mode? If I could get this working, the rest would be easy for me.
Edit: The reboot looks like in this Link. Only difference is, my device doesn't even the reach the dots.
Click to expand...
Click to collapse
If you can get fastboot commands to work, just flash the factory image per Heisenberg's guide. Toolkits are more trouble than help. Return it to fresh stock with a full wipe and start fresh.
Sent from my Nexus 6P using Tapatalk
StarShoot97 said:
Edit: The reboot looks like in this Link. Only difference is, my device doesn't even the reach the dots.
Click to expand...
Click to collapse
That vid you linked is an N5 with a stuck power button. It'll do the same thing and reboot recovery as well. It could be your issue but if it is it'll be the first stuck power button I've heard of on a 6P.
When you access fastboot does it stay on in fastboot or does it reboot from it?
theesotericone said:
That vid you linked is an N5 with a stuck power button. It'll do the same thing and reboot recovery as well. It could be your issue but if it is it'll be the first stuck power button I've heard of on a 6P.
When you access fastboot does it stay on in fastboot or does it reboot from it?
Click to expand...
Click to collapse
I said it looks like this, I did not say the button is the reason
When I access fastboot it stays there until I manually select an option
ultyrunner said:
If you can get fastboot commands to work, just flash the factory image per Heisenberg's guide. Toolkits are more trouble than help. Return it to fresh stock with a full wipe and start fresh.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
This is my last viable option, as I'd like to somehow pull my stuff from the phone. Afterwards I'd clean install it anyway.
StarShoot97 said:
This is my last viable option, as I'd like to somehow pull my stuff from the phone. Afterwards I'd clean install it anyway.
Click to expand...
Click to collapse
You contradict yourself a bit so it is difficult to help you. You got to stock recovery but you can't boot into TWRP? If you have stock recovery, of course you can't boot into TWRP. You have wiped your data but you still want to preserve your data ... Huh?
Your phone isn't working so just nuke and pave with the command line and avoid toolkits. They are sometimes part of the problem.
Sent from my Nexus 6P using Tapatalk
ultyrunner said:
You contradict yourself a bit so it is difficult to help you. You got to stock recovery but you can't boot into TWRP? If you have stock recovery, of course you can't boot into TWRP. You have wiped your data but you still want to preserve your data ... Huh?
Your phone isn't working so just nuke and pave with the command line and avoid toolkits. They are sometimes part of the problem.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
When stock recovery is installed, I am from time to time able to access it (most of the times it just ends in a bootloop)
If I flash TWRP I can't access it, no matter how often I try
I have factory reset my phone, the stuff on the internal is still there and I want to reach this, as I have my chats, SMS, university stuff and so on backed up on the internal storage
I am trying everything - all the regular adb methods, toolkits, every driver, nothing is working
Sorry if you don't understand my situation, but I am in a pinch right now
You said you have fastboot working?
Download the factory image zip file. Extract it. Extract the zip file from inside that as well. Move the img files to your platform-tools folder.
Reboot your phone to the bootloader. Hold volume down+power from a powered off state.
Plug into PC, open command line from your platform-tools folder.
Type, fastboot devices
Does it show your serial number? If so, start flashing the following images;
Bootloader-angler-angler-xx.xx.img, radio-angler-angler-xx.xx.img, vendor.img, system.img, boot.img, recovery.img
Flash with fastboot.
Code:
fastboot flash bootloader bootloader-angler-angler-xx.xx.img
Code:
fastboot flash radio radio-angler-angler-xx.xx.img
(Substitute "xx.xx" for the version number shown in the img files you unpacked)
Reboot bootloader
Code:
fastboot flash vendor vendor.img
Code:
fastboot flash system system.img
Code:
fastboot flash boot boot.img
Code:
fastboot flash recovery recovery.img
Once you do that, boot to stock recovery and cache wipe. Reboot and you're stock. If you're still not able to boot after that post back.
Edit: You said you wanted to avoid flashing factory images to keep internal storage in tact. Do it this way and you can have your cake and eat it too.
Edit2: wrong, see my latest reply
RoyJ said:
You said you have fastboot working?
Download the factory image zip file. Extract it. Extract the zip file from inside that as well. Move the img files to your platform-tools folder.
Reboot your phone to the bootloader. Hold volume down+power from a powered off state.
Plug into PC, open command line from your platform-tools folder.
Type, fastboot devices
Does it show your serial number? If so, start flashing the following images;
Bootloader-angler-angler-xx.xx.img, radio-angler-angler-xx.xx.img, vendor.img, system.img, boot.img, recovery.img
Flash with fastboot.
Code:
fastboot flash bootloader bootloader-angler-angler-xx.xx.img
Code:
fastboot flash radio radio-angler-angler-xx.xx.img
(Substitute "xx.xx" for the version number shown in the img files you unpacked)
Reboot bootloader
Code:
fastboot flash vendor vendor.img
Code:
fastboot flash system system.img
Code:
fastboot flash boot boot.img
Code:
fastboot flash recovery recovery.img
Once you do that, boot to stock recovery. Perform a factory reset again like you already mentioned you did as well as a cache wipe. Reboot and you're stock. If you're still not able to boot after that post back.
Edit: You said you wanted to avoid flashing factory images to keep internal storage in tact. Do it this way and you can have your cake and eat it too.
Click to expand...
Click to collapse
I did this already exactly like you wrote, did it again now, and I am still stuck in the reboot loop (boots up to Google Logo, then shuts itself down; repeat)
Can't reach recovery mode either
You said you had access to stock recovery before?
You already did this?
---------- Post added at 12:17 PM ---------- Previous post was at 12:16 PM ----------
If you flashed the factory images and still boot looping you may need to RMA.
Did you restore a TWRP backup?
Edit: Sorry, it's late and I have no sleep. I was wrong. I was thinking TWRP. Factory Reset from TWRP before my steps will keep internal storage I'm tact. Factory Reset from stock recovery will wipe internal storage. Everything. You mentioned you did that already from stock recovery before i made my reply. Your data is already gone as soon as you did that. If not, your emmc is likely corrupted and you need to RMA.
Fastboot twrp 3.0.0-0 then try to access it
RoyJ said:
You said you had access to stock recovery before?
You already did this?
---------- Post added at 12:17 PM ---------- Previous post was at 12:16 PM ----------
If you flashed the factory images and still boot looping you may need to RMA.
Did you restore a TWRP backup?
Edit: Sorry, it's late and I have no sleep. I was wrong. I was thinking TWRP. Factory Reset from TWRP before my steps will keep internal storage I'm tact. Factory Reset from stock recovery will wipe internal storage. Everything. You mentioned you did that already from stock recovery before i made my reply. Your data is already gone as soon as you did that. If not, your emmc is likely corrupted and you need to RMA.
Click to expand...
Click to collapse
Yes, I think so too. I flashed the phone with the full Stock image, the bootloop is still there.
Looks like my precious is dead
At least I have my most important data like phonenumbers, pictures and SMS saved to the cloud
Gonna RMA it tomorrow
Goodybe my precious, I hope you'll be fine :crying:
Got my device back today, the mainboard was damaged, so I had no chance to get my data from the phone
Hey, at least my warranty has been renewed 'till 2018
StarShoot97 said:
This is the whole situation:
I have Pure Nexus installed on my 6P, running great for months. Suddenly yesterday it rebooted while I was using it and sticking in a bootloop. "No problem", I thought, and wanted to reboot into recovery - but nope, can't access it anymore. So I tried to reflash the recovery when I got home, but I only get errorors
When using the command adb devices the line just stays blank. The same with fastboot commands, besides "Fastboot devices"
After messing around a couple hours with the drivers and so on, I managed to somehow get the fastboot command working again. But no sign for the ADB commands, probably because I didn't turn on USB-debugging.
I am now at the point, where I have reflashed Stock Android with the Nexus Root Toolkit and managed to get back into stock android recovery, but still can't get TWRP to boot. I didn't want to delete my personal data, but I saw no other way and formatted /data in stock recovery. But the problem with the bootloop is still there.
It's not the classic bootloop, it boots as far as the Google Logo, then shuts itself down and begins again. I have now reached the point where I have to say, that the hardware might be damaged too. I'd love to somehow get access to the internal storage at least, but I can't without a working ADB.
Reinstalled TWRP with every available version, none of them worked. I am able to access stock Android recovery, but adb commands aren't working from here anyway.
Is there an option to fix the recovery mode? If I could get this working, the rest would be easy for me.
Edit: The reboot looks like in this Link. Only difference is, my device doesn't even the reach the dots.
Click to expand...
Click to collapse
Try flashing TWRP 3.0.2-3 or boot into twrp through fastboot. Using
fastboot boot recovery <twrp filename>.img
I think booting to twrp using this command will work.
And here's the link to Twrp 3.0.2-3 , as its not available on Official Twrp page.
https://idlekernel.com/twrp/nexus/twrp-3.0.2-3-angler.img
I had the same problem with my 5X, nothing worked I tried every possible solution described above and more. Nothing. I figured out that there was nothing to loose and followed directions from YouTube videos (links below) and it worked. Used heat gun at max temp for about 2 mins from each side. It's been about 12 hours since then, phone works flawlessly. Here are the links:
https://www.youtube.com/watch?v=SD25mdrgAys
https://www.youtube.com/watch?v=Cqh2x-TGnCY
Be careful handling the motherboard after you heat the first side, let it cool first before you start working on the second side. The same with the second side do not pick it up until it's cool.
5X, Pure Nexus Rom 7.1.2 June 5th security update, Elemental X Kernel,
has anyone found solution to this?????
Title says it, have a seemingly dead N10 that I cannot get anything to load on. It kind of crapped the bed and I'm trying to revive it with no success. I can fastboot twrp on to it, but nothing on it to flash and with no adb access, I can't sideload anything to it. I tried fastboot installing a stock image but it just cycles for hours until the battery runs dead.
Suggestions?
vlucchetti said:
Title says it, have a seemingly dead N10 that I cannot get anything to load on. It kind of crapped the bed and I'm trying to revive it with no success. I can fastboot twrp on to it, but nothing on it to flash and with no adb access, I can't sideload anything to it. I tried fastboot installing a stock image but it just cycles for hours until the battery runs dead.
Suggestions?
Click to expand...
Click to collapse
Once you do
flashboot flash twrp.img
try
fastboot boot twrp.img
bedwere said:
Once you do
flashboot flash twrp.img
try
fastboot boot twrp.img
Click to expand...
Click to collapse
I'll give it a go, have done each of those separately, will try together.
Did you flash via fastboot each partition from the correct (sometimes you can message up firmware# thru bad ROM flas) I'd try *fastboot erase erase system* same syntax but wipe all partitions boot system recovery bootloader ect and create the new partitions and fastboot flash sys,bl,bt,rc. Worked on a personal phone all thru fastboot, and many more when I worked as a electronics repair Technician not sure to the whole process so check around gl mate
Nothing seems to work, I think she's dead. Picked up an inexpensive N10 off of swappa, so I'm good now.
I'll be damned. Could not give up on it, so I downloaded NRT, set it up and let it do its thing. 24 hours later and that n10 is running stock stuff.
Bless you NRT. Once it settles, going to root, install pure nexus and profit!
Excuse my ignorance, what is "NRT"?
JackTheMan18 said:
Excuse my ignorance, what is "NRT"?
Click to expand...
Click to collapse
Nexus Root Toolkit. It is a GUI based tool for rooting, flashing and has some tools for recovering seemingly dead devices. It can be found here.