I woke up today to a bootloop. After pulling out the battery, I cant turn it on, it was stuck at the google logo. I thought it was some rom issue or something. When I had the time, in the afternoon, I just boot to recovery, and wiped data+sd card. Turns out sd card was not wiped.
Just now, I found a way to boot it. (AFTER WIPING DATA) I used the gnex toolkit and boot with insecure image, and guess wat? My old rom boots. Everything was the way it was, and then it crashed and stuck on the google logo again.(I made sure i wiped things two to three times, data and sd) I did a few experiments:
1) Flash using ODIN
2) Flash CWM using toolkit--it changed back to twrp after reboot
3) Changing the icon on my homescreen after boot--- everything was the same again after booting
4) Flash stock image using toolkit
5) Wipe data using manual adb
6) Try to lock my bootloader
Everything I tried changing, change back to the original state after reboot. What is the problem?
Device: Galaxy Nexus
ROM: Purity 7 sept release
Kernel: Fancy r42
Logs in twrp are showing updating partition, not FAIL. So I really don't think there is a need to show the recovery log.
HELP ME!
are you flashing your recovery or just booting the recovery?
fastboot oem unlock
fastboot flash recovery recovery.img
use ClockWorkMod. I've heard nothing but problems with TWRP.
player911 said:
are you flashing your recovery or just booting the recovery?
fastboot oem unlock
fastboot flash recovery recovery.img
use ClockWorkMod. I've heard nothing but problems with TWRP.
Click to expand...
Click to collapse
umm, i can boot recovery. i cannot flash cwm. i tried, but when i reboot, it went back to twrp.
what is oem unlock for? coz its smth i havent tried.
jacktay94 said:
umm, i can boot recovery. i cannot flash cwm. i tried, but when i reboot, it went back to twrp.
what is oem unlock for? coz its smth i havent tried.
Click to expand...
Click to collapse
Oem unlock will unlock your bootloader and wipe the internal storage in the process. I saw you didn't use fastboot. You could try that. Flash the Factory image via fastboot. If that fails try omap flash.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
Oem unlock will unlock your bootloader and wipe the internal storage in the process. I saw you didn't use fastboot. You could try that. Flash the Factory image via fastboot. If that fails try omap flash.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Yup,I tried it already thru toolkit. Not working either.
Dude the toolkit blows, flash back to stock manually via adb command prompt. There are tutorials around here on how to do it. It's guaranteed to work if you don't screw it up.
Honestly flashing back to stock via adb should be something everyone should learn if you plan on flashing roms.
SoHaunted said:
Dude the toolkit blows, flash back to stock manually via adb command prompt. There are tutorials around here on how to do it. It's guaranteed to work if you don't screw it up.
Honestly flashing back to stock via adb should be something everyone should learn if you plan on flashing roms.
Click to expand...
Click to collapse
i did adb bro, its the last thing i tried, i learnt and try.
Sent to Samsung centre, they told me its my flash IC thats blown. sobs
Related
So I was attempting to try a new rom - Android Revolution HD 3.0.0 -. I downloaded the rom, and super wipe script and booted into CWM recovery.
Ran the Super Wipe script and now it just hangs on reboot. I can still get into fastboot but I can't get into Android or Recovery. Whenever I try to boot into Recovery I get Andy with the spinning sphere. The blue loading bar hangs about 1/5 of the way across. Eventually the phone reboots and repeats.
I've tried gnex toolkit v5.6. I tried flashing a new recovery via the toolkit and I tried option 7(1-click for all). Both say they successfully installed the recovery but I still can't boot.
Any ideas?
and this is why you dont use toolkits because you dont have a full understanding of what you're doing and relying on a program.
fastboot flash google stock images OR fastboot flash clockwork recovery in bootloader mode and then proceed to go into recovery mode and wipe factory(data)/cache/dalvik and flash a rom
i advise doing the second that i suggested. if all else fails, flash google images as a last resort
zephiK said:
and this is why you dont use toolkits because you dont have a full understanding of what you're doing and relying on a program.
fastboot flash google stock images OR fastboot flash clockwork recovery in bootloader mode and then proceed to go into recovery mode and wipe factory(data)/cache/dalvik and flash a rom
i advise doing the second that i suggested. if all else fails, flash google images as a last resort
Click to expand...
Click to collapse
Thanks for the quick reply. I just assumed the toolkit would be a quicker way of doing the commands manually. That being said even fastboot flash recovery recovery-clockwork-5.5.0.2-maguro.img nets me the exact same results, so it looks like I'm off to google stock images
AverageCanadian said:
Thanks for the quick reply. I just assumed the toolkit would be a quicker way of doing the commands manually. That being said even fastboot flash recovery recovery-clockwork-5.5.0.2-maguro.img nets me the exact same results, so it looks like I'm off to google stock images
Click to expand...
Click to collapse
It is quicker in a sense. But with every short cut that you take, you're losing knowledge. Sure, you're rooting and doing all that fancy stuff. But you're not realizing what you're doing so when you have a problem.. you're unable to diagnosis it because you aren't aware of what that toolkit just did.
Okay. Then just flash google stock images.. after it boots into Android, just fastboot flash recovery again and then wipe and then flash your ROM.
back on stock rom for now . Will have to flash custom recovery later but for now I have a working phone again which is nice.
AverageCanadian said:
back on stock rom for now . Will have to flash custom recovery later but for now I have a working phone again which is nice.
Click to expand...
Click to collapse
Glad to hear it was happy to see that you didn't panic and claim your phone being 'bricked.' Definitely weird how the superwipe script caused that problem on your phone. Personally not a fan of "superwipe" that's just me. Manually wiping factory(data)/cache/dalvik is good enough for me.
Same happened to me trying to install HD 3.0. I also had to go back to flashing Google stock after getting the boot loop you described. Would it have anything to do with that script trying to format partitions to ext3??
Sent from my Galaxy Nexus using XDA
My nexus is from everyway shape or form bricked. I tried all forms of fixing it:
-Tried flashing stock image from fastboot
-tried flashing stock through odin
-tried flashing through recovery
-tried locking and unlocking the bootloader
What I noticed: I can flash different kernels and mods. But as soon as I try to flash a ROM that I already had saved on the SD it cancels the install and shows "(bad)". I also cannot mount /system to format it.
Also, when I try to flash anything thru odin or fastboot, everything works according to ODIN and I get the blue "PASS" sign, but when it reboots nothing sticks. I was able to use the Toolkit v7.8 to boot into TWRP recorvery, and it still doesnt work. NOTE: I can only boot into it with the Toolkit, I cant actually flash the recovery permanently.
I guess the system files became Read-Only.
I have no ROM currently loaded so I can only boot into Download mode/Fastboot and CWM recovery.
Things to try
acesofbelkan said:
My nexus is from everyway shape or form bricked. I tried all forms of fixing it:
-Tried flashing stock image from fastboot
-tried flashing stock through odin
-tried flashing through recovery
-tried locking and unlocking the bootloader
What I noticed: I can flash different kernels and mods. But as soon as I try to flash a ROM that I already had saved on the SD it cancels the install and shows "(bad)". I also cannot mount /system to format it.
Also, when I try to flash anything thru odin or fastboot, everything works according to ODIN and I get the blue "PASS" sign, but when it reboots nothing sticks. I was able to use the Toolkit v7.8 to boot into TWRP recorvery, and it still doesnt work. NOTE: I can only boot into it with the Toolkit, I cant actually flash the recovery permanently.
I guess the system files became Read-Only.
I have no ROM currently loaded so I can only boot into Download mode/Fastboot and CWM recovery.
Click to expand...
Click to collapse
It looks like you've tried just about everything and you are very capable of getting it done. My only suggestion is that when I thought I was bricked, I kept wiping all the data I could find. From CWM I started with a wipe data/factory reset and that had the best results for me. After that, wipe dalvik, wipe battery stats, and I tried loading a new ROM from sdcard. I wouldn't try to install a new kernel or any other mod until you successfully boot into your new(or old) ROM.
Like I said, you probably already knew all of this but I wanted to make sure all the bases were covered. If it doesn't help you, I hope it at least helps someone else. Good luck, and please post your progress!
try using fastboot to erase the system and other partition.
fastboot erase system
fastboot erase userdata
faseboot erase boot
fastboot erase recovery
Then flash stock from fastboot
Ok, I try the fast boot method today after work. I have a feeling it wont work until I can mount the system folder which is the sole problem if Im not mistaken. I wiped absolutely everything I could in CWM to no avail. So fastboot looks like the only choice
acesofbelkan said:
Ok, I try the fast boot method today after work. I have a feeling it wont work until I can mount the system folder which is the sole problem if Im not mistaken. I wiped absolutely everything I could in CWM to no avail. So fastboot looks like the only choice
Click to expand...
Click to collapse
Fastboot does not require mounting of anything -- it writes to the entire partition.
efrant said:
Fastboot does not require mounting of anything -- it writes to the entire partition.
Click to expand...
Click to collapse
I don't have the best knowledge when it comes to this. But if this is true then perhaps I lost root? When I was flashing a Rom my phone shut off and that's when these problems started. Would losing root be the cause of this?
acesofbelkan said:
I don't have the best knowledge when it comes to this. But if this is true then perhaps I lost root? When I was flashing a Rom my phone shut off and that's when these problems started. Would losing root be the cause of this?
Click to expand...
Click to collapse
No. Root has nothing to do with fastboot. Root has nothing to do with your device. Root has to do with the Android build that you are running.
When you are booted into the bootloader (i.e., fastboot mode), there is no Android OS running, so how can there be root?
The fastboot executable on your PC interacts directly with the bootloader, and it will wipe an entire partition, or write an image to a partition.
first off you need to download wugfresh's Gnex toolkit:
http://forum.xda-developers.com/show....php?t=1766475
second you need to install all the drivers if you haven't already.
then you need to choose your model type
after you will need to click on back to stock what it does is it resets everything, assuming your phone cant boot up choose not booting
once that is done you can choose the factory image which can be downloaded from Googles factory images or you can use the options provided
after that you follow all the steps provided in the tool kit. the tool kit is mostly automatic so it wont take allot of time.
once that is done you are back in stock and have lost everything but don't fret because you can root it again using the same tool kit.
quick point your phone still has an unlocked boot loader so don't worry about that.
once youve completed the above steps you should be back to your good old galaxy nexus home screen
NoorGnex said:
[snip]
first off you need to download wugfresh's Gnex toolkit
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1469909
efrant said:
http://forum.xda-developers.com/showthread.php?t=1469909
Click to expand...
Click to collapse
I've personally never had problems with tool kits and have found them very helpful, because of my busy schedule I don't have the time to do it myself even with my amateur coding skills, and have found only people who dont understand what there getting themselves into get bricked, thats not to say you cant brick your phone if your smart but if your smart you would have done a nandroid before flashing anything.
thanks again for that enlightening post
NoorGnex said:
first off you need to download wugfresh's Gnex toolkit:
http://forum.xda-developers.com/show....php?t=1766475
Click to expand...
Click to collapse
Link is bringing up a 404 error. Did the toolkit move locations?
JackG058 said:
Link is bringing up a 404 error. Did the toolkit move locations?
Click to expand...
Click to collapse
sorry
http://forum.xda-developers.com/showthread.php?t=1766475
NoorGnex said:
sorry
http://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
Thanks. I'm prepping for doing a ROM tomorrow night so trying to do my due diligence now.
JackG058 said:
Thanks. I'm prepping for doing a ROM tomorrow night so trying to do my due diligence now.
Click to expand...
Click to collapse
This is what you should be reading for due diligence...
efrant said:
This is what you should be reading for due diligence...
Click to expand...
Click to collapse
I will add this to my reading list, and send you my kind thanks.
edit: And bookmarking, of course.
I tried WugFresh's toolkit, everything was flashed(at least thats what the program said). But when the phone reboots, nothing, just logo screen
acesofbelkan said:
I tried WugFresh's toolkit, everything was flashed(at least thats what the program said). But when the phone reboots, nothing, just logo screen
Click to expand...
Click to collapse
That's what I was trying to get across earlier...
Use this: http://forum.xda-developers.com/showthread.php?t=1626895 That way, you can see where you are having issues.
And in case you missed it earlier: http://forum.xda-developers.com/showpost.php?p=30015315&postcount=9
NoorGnex said:
first off you need to download wugfresh's Gnex toolkit:
http://forum.xda-developers.com/show....php?t=1766475
second you need to install all the drivers if you haven't already.
then you need to choose your model type
after you will need to click on back to stock what it does is it resets everything, assuming your phone cant boot up choose not booting
once that is done you can choose the factory image which can be downloaded from Googles factory images or you can use the options provided
after that you follow all the steps provided in the tool kit. the tool kit is mostly automatic so it wont take allot of time.
once that is done you are back in stock and have lost everything but don't fret because you can root it again using the same tool kit.
quick point your phone still has an unlocked boot loader so don't worry about that.
once youve completed the above steps you should be back to your good old galaxy nexus home screen
Click to expand...
Click to collapse
Only after you learn what is going on in the background.
I think i'm going to stop trying to help people using toolkits if it seem that they did not even bordered to read up on fastboot and adb..
efrant said:
http://forum.xda-developers.com/showthread.php?t=1469909
Click to expand...
Click to collapse
+1
acesofbelkan said:
I tried WugFresh's toolkit, everything was flashed(at least thats what the program said). But when the phone reboots, nothing, just logo screen
Click to expand...
Click to collapse
This quote pretty much defines why people hate toolkits.
I was attempting to unlock/root and long story short, now I have TWRP installed, and I can get to FASTBOOT but if i try to boot normally I get the Nexus logo, and no further. When I unlocked, I installed TWRP then loaded it. After leaving TWRP it said 'Seems you are not rooted, want to root"? or something to that effect. I clicked YES and now I'm stuck. Since I had just unlocked it, it *should* have reset my entire device(which was all stock anyway) so I am not sure what went wrong. I have been trying everything I know but I'm now out of ideas. Would appreciate any help. I see now that the version of SuperSu that it would have pushed would have been wrong, would that be preventing the tablet from booting?
If you can mount in fastboot you're not bricked. You tried to check md5 and push the recovery image again? And also try to throw new ROM on it.
Sent from my HTC One using xda app-developers app
ronni.rasmussen said:
If you can mount in fastboot you're not bricked. You tried to check md5 and push the recovery image again? And also try to throw new ROM on it.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
It wont boot so I don't know how to put anything on it, it's empty and doesn't show up in windows. Also I don't know what you meant exactly by push the recovery image again. Twrp is working fine. Sorry I am hardly a pro at this stuff.
Landara said:
It wont boot so I don't know how to put anything on it, it's empty and doesn't show up in windows. Also I don't know what you meant exactly by push the recovery image again. Twrp is working fine. Sorry I am hardly a pro at this stuff.
Click to expand...
Click to collapse
Try to get to fastboot and connect PC and check if it connects. You will need the USB drivers installed
Sent from my HTC One using xda app-developers app
ronni.rasmussen said:
Try to get to fastboot and connect PC and check if it connects. You will need the USB drivers installed
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Oh I can do that no problem, been using ADB. But now it just won't boot normally. But I can use the terminal and everything.
Landara said:
Oh I can do that no problem, been using ADB. But now it just won't boot normally. But I can use the terminal and everything.
Click to expand...
Click to collapse
Then it should be possible to flash and push recovery and ROM to device even get a stock image back.
Which recovery image did you install?
And did you flash any ROM or kernel?
Sent from my HTC One using xda app-developers app
Landara said:
Oh I can do that no problem, been using ADB. But now it just won't boot normally. But I can use the terminal and everything.
Click to expand...
Click to collapse
I would suggest you just restore your N7 back to stock. No need for root yet, seriously! But this should help get you going in the right direction.
Power it off completely. Hold Power + Volume down until it boots into the bootloader. Run the following commands:
fastboot devices (to confirm you are connected)
fastboot flash recovery recovery.img
If you haven't unlocked your N7 yet, run fastboot oem unlock first.
ronni.rasmussen said:
Then it should be possible to flash and push recovery and ROM to device even get a stock image back.
Which recovery image did you install?
And did you flash any ROM or kernel?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I put TWRP on there, immediately after unlocking. So it should have been completely stock since as far as I know it wipes it when you unlock. After putting TWRP on there, i told it to reboot normally(from within TWRP) and it detected that I was not rooted and asked me if I wanted to install SuperSu. I said yes and now it will not boot to the operating system. It boots fine to Bootloader and Recovery. And I am certain it's connected to my PC because I can even tell it ADB REBOOT BOOTLOADER/RECOVERY and that works. But I don't see how I can load a ROM onto it if I can't access it via windows. I don't know how to get a ROM onto the SD card. Surely there could be a way but I don't know it.
Landara said:
I put TWRP on there, immediately after unlocking. So it should have been completely stock since as far as I know it wipes it when you unlock. After putting TWRP on there, i told it to reboot normally(from within TWRP) and it detected that I was not rooted and asked me if I wanted to install SuperSu. I said yes and now it will not boot to the operating system. It boots fine to Bootloader and Recovery. And I am certain it's connected to my PC because I can even tell it ADB REBOOT BOOTLOADER/RECOVERY and that works. But I don't see how I can load a ROM onto it if I can't access it via windows. I don't know how to get a ROM onto the SD card. Surely there could be a way but I don't know it.
Click to expand...
Click to collapse
Start over by downloading recovery, Superuser and a clean stock rom image.
But before that you could try to reset all data in recovery (factory reset) and cache if you haven't tried.
http://forum.xda-developers.com/showthread.php?t=2380913
Thanks to this thread I have booted! Still have to root it but now that I know that you have to flash the NEW SuperSu not the one TWRP flashed for me, I shouldn't have a problem Thanks so much for your help everyone!
Landara said:
http://forum.xda-developers.com/showthread.php?t=2380913
Thanks to this thread I have booted! Still have to root it but now that I know that you have to flash the NEW SuperSu not the one TWRP flashed for me, I shouldn't have a problem Thanks so much for your help everyone!
Click to expand...
Click to collapse
Super
Howdy Everyone,
So just tried rooting my new m8 and now I'm stuck endlessly booting into TWRP. I thought I did everything correctly: Unlocked the bootloader, installed the USB drivers, installed the ADB fastboot drivers and then flashed twrp 2.7.0.3. I get to the the htc logo screen/warning and, bam, back to twrp everytime.
Does anyone know how to fix this??? The last time i was rooting and installing custom mods was back in samsung galaxy s2 days, so my knowledge is a little dated. Please help!!
Try flashing the recovery again. Download it from the link provided here and confirm the md5 checksum for the zip file.
http://forum.xda-developers.com/showthread.php?t=2694564
Sent from my HTC One_M8 using XDA Premium 4 mobile app
PirateP3t3 said:
Howdy Everyone,
So just tried rooting my new m8 and now I'm stuck endlessly booting into TWRP. I thought I did everything correctly: Unlocked the bootloader, installed the USB drivers, installed the ADB fastboot drivers and then flashed twrp 2.7.0.3. I get to the the htc logo screen/warning and, bam, back to twrp everytime.
Does anyone know how to fix this??? The last time i was rooting and installing custom mods was back in samsung galaxy s2 days, so my knowledge is a little dated. Please help!!
Click to expand...
Click to collapse
some reason doing twrp from terminal on hte m8 gets us stuck (it did for me at least.)
just reflash the insecure boot image.. fastboot flash boot blah.img
that should get you back up
PirateP3t3 said:
Howdy Everyone,
So just tried rooting my new m8 and now I'm stuck endlessly booting into TWRP. I thought I did everything correctly: Unlocked the bootloader, installed the USB drivers, installed the ADB fastboot drivers and then flashed twrp 2.7.0.3. I get to the the htc logo screen/warning and, bam, back to twrp everytime.
Does anyone know how to fix this??? The last time i was rooting and installing custom mods was back in samsung galaxy s2 days, so my knowledge is a little dated. Please help!!
Click to expand...
Click to collapse
I encountered this issue as well. I'm almost certain that when you were flashing recovery, you used this command "fastboot flash boot recovery.img".
The right command should be "fastboot flash recovery recovery.img".
To rectify the issue look for a tread that has the boot.img for your specific M8 model and flash boot back using " fastboot flash boot boot.img".
This should fix the issue you are having
darll said:
I encountered this issue as well. I'm almost certain that when you were flashing recovery, you used this command "fastboot flash boot recovery.img".
The right command should be "fastboot flash recovery recovery.img".
To rectify the issue look for a tread that has the boot.img for your specific M8 model and flash boot back using " fastboot flash boot boot.img".
This should fix the issue you are having
Click to expand...
Click to collapse
Forgot to come back and update this thread, but this is exactly what I did and it worked!!! Now happily rooted and running.
Thanks for the help!
PirateP3t3 said:
Forgot to come back and update this thread, but this is exactly what I did and it worked!!! Now happily rooted and running.
Thanks for the help!
Click to expand...
Click to collapse
I followed the instructions on the TWRP site:
Download the above file. Save it to the root of your /sdcard directly (internal memory only) and rename it to twrp.img
Launch terminal emulator or connect to your computer and open an adb shell, then type the following:
su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p43
Then reboot to complete installation.
But that left me in a TWRP bootloop. Can you please give me step by step instructions on how to get out of this bootloop?
Thanks!
First off, being a noob and using dd without even knowing what partiton you're writing to is extremely dangerous.
Just use fastboot.
plug phone into PC in fastboot mode.
Code:
fastboot flash recovery twrpfilename.img
fastboot erase cache
on phone go back to hboot, select, recovery
In TWRP go to wipe, then swipe for a factory reset (Advanced wipe cannot properly wipe cache and dalvik after fastboot erase cache)
then go to advanced, select cache, dalvik and system and swipe to wipe those partitions.
then go to install, select the rom on your phone and flash. follow on screen instructions.
If you don't have the rom on your phone for whatever reason,
connect your phone, while in TWRP to your PC then, using adb on your PC
Code:
adb push romfilename.zip /sdcard/
Wait until it completes with bytes sent.
Then flash using method listed above.
Be careful if you want to keep your phone. I stress this, if you don't know what a command you are issuing does, exactly, DO NOT DO IT until you look it up and understand what you are doing. There is great risk even when you know what you're doing. There's a LOT more when you don't.
exad said:
First off, being a noob and using dd without even knowing what partiton you're writing to is extremely dangerous.
Just use fastboot.
plug phone into PC in fastboot mode.
Code:
fastboot flash recovery twrpfilename.img
fastboot erase cache
on phone go back to hboot, select, recovery
In TWRP go to wipe, advanced, select cache, dalvik and system
then go to install, select the rom on your phone and flash. follow on screen instructions.
If you don't have the rom on your phone for whatever reason,
connect your phone, while in TWRP to your PC then, using adb on your PC
Code:
adb push romfilename.zip /sdcard/
Wait until it completes with bytes sent.
Then flash using method listed above.
Be careful if you want to keep your phone. I stress this, if you don't know what a command you are issuing does, exactly, DO NOT DO IT until you look it up and understand what you are doing. There is great risk even when you know what you're doing. There's a LOT more when you don't.
Click to expand...
Click to collapse
Thanks for the detailed instructions. I opened fastboot on my PC with phone plugged in and entered the code but the cmd prompt just says <waiting for device>
Do you have the HTC drivers installed on your PC with HTC sync uninstalled?
Does it say fastboot USB on your phone?
Sent from my HTC One_M8 using xda app-developers app
Update: I ended up just installing the Viper ROM and the system rebooted fine. It's strange that I couldn't reboot the device to get out of recovery without having to install a custom ROM.
Sent from my HTC6525LVW using Tapatalk
No it's not. You flashed recovery to the boot partition.
Sent from my HTC One_M8 using xda app-developers app
How do i fix TWRP Bootloop on my HTC explorer a310e... ?
How do i fix TWRP Bootloop on my HTC explorer a310e... ?
I hav custom cm11 Kitkat ROM installed on it...
but after I installed the rom, and again tried to reboot
into TWRP recovery, it is just stuck on the blue color
TEAMWIN screen... Please help how to fix it...!
HELP PLEASE
I pressed factory reset on my cm13 rom htc one m8 with twrp and now its just stuck flashing the teamwin logo and i cant do anything, i tried using fastboot but it cant see the device.
Maxxour said:
HELP PLEASE
I pressed factory reset on my cm13 rom htc one m8 with twrp and now its just stuck flashing the teamwin logo and i cant do anything, i tried using fastboot but it cant see the device.
Click to expand...
Click to collapse
You need cwm recovery to factory reset from cm roms.
Also you need to be in FASTBOOT mode for it to detect your device.
Boot to fastboot, erase cache, reinstall twrp.
Next time reset/wipe from recovery.
ashyx said:
You need cwm recovery to factory reset from cm roms.
Click to expand...
Click to collapse
cwm recovery or cm recovery?
32gb variant (H790).
I tried most of the solutions I've seen on this subforum so far - including doing a full flash-all.sh command as well as the flashing of individual files into my system.
So far I've been able to do so using the stock images from Google (Android N). However, I can never get Recovery to boot and my phone will not boot past "Google." (Not even the colorful animations show).
I am not sure what I can do - I unfortunately got this phone via a 3rd party and not Google's Store, so I'm not sure if they would honor an RMA request (maybe if I said it was a gift they would relent?).
I was reading this thread: http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740 and realized that this might be my last alternative, but I'm a bit concerned about going through all of this without giving it one more chance having access to at least the bootloader screen.
Does anyone have any suggestions on what I might be doing wrong? Should I attempt to flash the latest Android 6.0 image instead?
Is your boot loader locked? How did you flash the stock images?
Reboot into fastboot, run the flash all, reboot back to your bootloader when it's done and it. These commands....
Fastboot format cache
Fastboot format userdata
Then restart the phone
Corrupted bootloader partition, your phone is little piece of brick. EXT4 is the motive, HAHAHA.
I lost a ****ty device like you too.
Now i learned: (IF IS EXT4 , NO!)
Sent from my XT687 using xda premium
I am able to unlock bootloader. I flashed using both flash all as well as individual img at a time like described in this: http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
I ran format cache and userdata (which I think the full flash also does). I am unable to go past the Google screen.
I was able to reflash my rom again too, without errors, but the **** recused to boot up or boot recovery, your phone is death like the apocalyptical beast google inc!
Sent from my XT687 using xda premium
dcxgod said:
I am able to unlock bootloader. I flashed using both flash all as well as individual img at a time like described in this: http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
I ran format cache and userdata (which I think the full flash also does). I am unable to go past the Google screen.
Click to expand...
Click to collapse
Can you get TWRP installed via fastboot and boot into that?
Sent from my Nexus 5X using Tapatalk
Use the lg tot file method to recover. It has worked for some.
Sent from my Nexus 5X using Tapatalk
Try to flash TWRP with fasboot and see if you can boot it. There's an actual problem with the last versions of TWRP (TWRP 3.0.2-1 and 3.0.2-2), where if you backup then restore an EFS partition you end up with a phone where it doesn't get past the Google Screen (or crashes in the first frame of the bootanimation), lk panic apparently due to EFS corruption.
If this is your case (derped restoring EFS like that) and you can flash and boot on TWRP, try to flash TWRP 3.0.2-0 and restore and old backup of EFS.
maybe same problem
I have the same problem.
Before i flash manually my phone into android 7(factory image) it was rooted and unlock bootloader. I locked the bootloader again and until here everything works fine. I flashed the stock recovery mode by TWRP. after that the phone won't boot android and stock recovery mode. everything was lost except the bootloader.
I tried lots of tricks but don't answer(sideload ota update, format cache and userdata). I tried to flash stock recovery or custom recovery but i couldn't because in the process the phone restart and restart again and again. Even doesn't work temporarily boot, custom and stock recovery mode and phone has no reaction.
I only have access to the bootloader.
Would you have any suggestion?
*ps: When phone is boot up just shows a white google logo and after that shows a green bot with red alert and a message(no command) . In this point phone restart suddenly and the same process is repeated.