[Q] [4.4.2] Nexus 5 stuck on boot - Nexus 5 Q&A, Help & Troubleshooting

I'm not sure what info is relevant here so I'll just include everything I can think of.
I was on 4.4 until about 12 hours ago, when I got the update notification for 4.4.2. I am completely stock and have no provider at the moment while I wait for my contract w/verizon to expire. The phone was working fine for the past 11 hours.
My phone was at about 60% and working fine when I tried to install the facebook app. Upon opening the app, the phone went black/unresponsive. I plugged it in and tried to hard reset it-- the google logo would show up but nothing else for 5~10 minutes when I would try to restart the phone. If I pressed the power button down for ~10 seconds, the screen would blink off, but then immediately turn on again to the google logo screen without me pressing the button to turn it back on.
After about 20 minutes of this, I went into bootloader and tried a factory reset. It finished really fast and I clicked the option for reboot. The phone didn't reboot, though, and was frozen.
I hard rebooted and was able to get past the google screen and the 4 colored dots showed for about 10 seconds, and then froze. I hard reset again, and tried wiping the cache. This is the message I am seeing now:
Erasing...
E: Error in /cache/recovery/log
(Read only file system)
E: Can't open /cache/recovery/last_log
E: Can't open /cache/recovery/last_install
-- Wiping Cache...
E: Failed to mount /cache (Invalid argument)
Formatting /cache...​
And it's been like that for half an hour. I don't know if it's actually doing something, the blue completion bar isn't updating and looks frozen.
If you have any advise on how I can restore my phone to working condition, I'd be really grateful. Thanks!

So your on a stock ROM? Seems like you were in a boot loop and then you did something that erased your internal card. (That's what it sounds like anyways) Its not a big issue tho, you can fix it. You have no root what so ever right? If yes. Then just flash a stock ROM through the BOOTLOADER. There is a tutorial for that on the website.
BTW did your Recovery look like this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Fulbring said:
So your on a stock ROM? Seems like you were in a boot loop and then you did something that erased your internal card. (That's what it sounds like anyways) Its not a big issue tho, you can fix it. You have no root what so ever right? If yes. Then just flash a stock ROM through the BOOTLOADER. There is a tutorial for that on the website.
BTW did your Recovery look like this?
Click to expand...
Click to collapse
Yes, it looks exactly like that. I will try to flash a stock rom like you said in the morning. Thanks for the reply!

colia said:
Yes, it looks exactly like that. I will try to flash a stock rom like you said in the morning. Thanks for the reply!
Click to expand...
Click to collapse
Cool. So that option that says "Apply update through ADB" side load the stock ROM through that using ADB again and you should be fine!

Fulbring said:
Cool. So that option that says "Apply update through ADB" side load the stock ROM through that using ADB again and you should be fine!
Click to expand...
Click to collapse
Okay, I'm having some problems. I tried to side load image-hammerhead-krt16m.zip with the command in command prompt:
[adb sideload image-hammerhead-krt16m.zip]
It sent successfully, but I have a lot of error messages on my phone:
http: i.imgur.com/xqZ0K5k.jpg
The important one seems to be
"Failed to set up expected mounts for install; aborting
Installation aborted"
And when I restart and try to boot, it gets to the animated dots and doesn't progress from there. When I go back into recovery, it still says [KOT49H] so I don't think sideloading worked.

Are you sideloading Android 4.4.2? If yes, then your doing it wrong. You have to load 4.4 on it, you should erase everything first and then do a clean load. I think there are some files that are corrupt preventing from the current sideload from working.
Sent from my Nexus 5 using XDA Premium 4 mobile app

Fulbring said:
Are you sideloading Android 4.4.2? If yes, then your doing it wrong. You have to load 4.4 on it, you should erase everything first and then do a clean load. I think there are some files that are corrupt preventing from the current sideload from working.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No, I'm loading [image-hammerhead-krt16m.zip] which is supposed to be 4.4 that I got from developers.google.com/android/nexus/images#hammerhead

colia said:
No, I'm loading [image-hammerhead-krt16m.zip] which is supposed to be 4.4 that I got from developers.google.com/android/nexus/images#hammerhead
Click to expand...
Click to collapse
Can you boot into fastboot?
If so, follow this guide (make sure drivers are installed)
http://forum.xda-developers.com/showthread.php?t=2513701
It looks to me like in the beginning your cache.img was corrupted, so you could get away with just flashing the cache.img from the above files, but now I would just do the entire thing.

i have this problem
colia said:
Yes, it looks exactly like that. I will try to flash a stock rom like you said in the morning. Thanks for the reply!
Click to expand...
Click to collapse
i am with this problem.... please can u tell me the steps to solve this problem or where i can found the steps to solve this...
thank for ur time

Related

[A510] New discovery for my bricked A510

Hi all,
my A510 was half-bricked since I run the wipe option of CWM (version 5.8.4) last month. It can not boot to system, just hang at 'Iconia tab' logo if I power it on.
I tried to flash the stock recovery back, and flash the update.zip from SD. Every time it just stuck in 1/4 of the progress bar. (even change the zip or SD card)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then I chose to install the new CWM for A700 ( version 6.0.1.1 ) and success to enter it. All the options can be run without any stuck, except for the wrong picture. I didn't know what to do, so i did all the wipe and format options.
Then it's getting more terrible, it stuck in Acer logo (first screen) after boot, nothing went further.
Last night I tried the SD flash again. I flashed all the roms from this thread, (I tried all the roms and failed to flash any last time)
To my surprise, one of the rom (1.060.00_EMEA_CUS1) can be flashed!
At first it stuck at 1/4 of progress bar as usual, then after a while it went to the 9/10 very quickly!
It reboot a few secs later and I saw 'updating EBT' at the upper left. Then it reboot again.
At the second-time reboot, I didn't see the 'bootloader unlock mode' shown in first sreen anymore, so it seems I made it?:cyclops:
Then I knew I am wrong, it also hang at 'Iconia tab' logo at last. :crying: oh, come on!
I didn't give up and continued to flash other roms. But i was too tired to sleep.:angel:
When i opened my eyes, i saw my tab entered the system finally!
No, wait! What is it?
title: 'XXXX unsuccessful'(my bad, i can't remember the first word)​content: 4 lines of words, about to tell u the tab need to be reset.
So I hit the 'reset tablet' button at lower right corner, then it reboot to recovery immediately. I saw the whole progress bar became very active and went backwards, and i waited it for half an hour, but nothing changed.
'coz that was midnight, i plugged the charger and went to sleep.
When I get up, it just hang there. damn it.
Anybody know what to do next?
p.s. My tab is EMEA-DE version.
Thanks and Regards,
Jokerzlh
Sorry, but I can't help you...
I just wanted to say this was a very entertaining story. You cracked me up. Good luck with your 510. Keep us updated.
ExtremeRyno said:
Sorry, but I can't help you...
I just wanted to say this was a very entertaining story. You cracked me up. Good luck with your 510. Keep us updated.
Click to expand...
Click to collapse
Thanks, it's an entertaining story indeed, but not a happy ending at last.:crying:
If I save my tab oneday then i'll share the method immediately.
jokerzlh said:
Thanks, it's an entertaining story indeed, but not a happy ending at last.:crying:
If I save my tab oneday then i'll share the method immediately.
Click to expand...
Click to collapse
Try this can't hurt anything else.Screwed mine up tried hard reset seems it wasn't doing anything for like 15 minutes then felt it vibrate then booted up back to factory. http://forum.xda-developers.com/showthread.php?t=1747802.
jessejames44 said:
Try this can't hurt anything else.Screwed mine up tried hard reset seems it wasn't doing anything for like 15 minutes then felt it vibrate then booted up back to factory. http://forum.xda-developers.com/showthread.php?t=1747802.
Click to expand...
Click to collapse
Never try the factory reset when the tab was unlocked, rooted and CWM installed.
help please
I have the exact same problem . I can flash update.zip for WW.GEN1 version successfully but it stops at "Iconia Tab" logo . does any one knows how can i fix this ?
yoooohooo
jokerzlh said:
Thanks, it's an entertaining story indeed, but not a happy ending at last.:crying:
If I save my tab oneday then i'll share the method immediately.
Click to expand...
Click to collapse
hi jokerzlh . i unbricked me tablet . :victory: do this step by step :
1. flash the working rom for yours "EMEA_CUS1".
2. Switch off
3. Press Vol-up 'one dot' + Power
4. If display goes on: Release power but hold vol-up
5. Toggle Lock switch (On>Off>On>Off)
Screen will display:
Erasing Userdata..
Erasing Cache..
then it will pass Iconia Tab Screen and will enter OS...
Waiting for your feedback...

Well I screwed up

Okay, so SOMEHOW I downloaded the crespo factory images and flashed the bootloader and then the radio. The system update wouldn't flash and this is when I realized my horrible mistake. So I downloaded the correct factory images. But now, I have no USB access on the thing. Can't fastboot. Can't adb. Phone boots and charges over usb. I can reboot into the bootloader, but my computer doesn't recognize the phone is even attached. I can reboot into recovery (I still have CWM on there) but what can I do from there? Am I TOTALLY ****ed? Please please please help!.....
I think what I need is a CWM flashable bootloader zip file. Or a complete OTA ROM Update zip file that flashes ROM, radio, and bootloader. Since I have CWM I think either of these will work for me, but I can 't find anything like this for the Nexus S 4G. Can anyone help?
have you checked if your computer recognizes your phone on odin mode? if it does you can prob try this
http://forum.xda-developers.com/showthread.php?t=1575502
JOEOZUNA4U said:
have you checked if your computer recognizes your phone on odin mode? if it does you can prob try this
http://forum.xda-developers.com/showthread.php?t=1575502
Click to expand...
Click to collapse
Unfortunately it doesn't. My computer doesn't recognize this phone at all anymore, not in fastboot or download mode, or even just booted into Android. If someone could PLEASE show me where a CWM flashable file that will flash the bootloader is, or make me one, I'd pay some good $$$ for it. Please help?
You flashed the bootloader & radio with ODIN?
supercluver said:
Unfortunately it doesn't. My computer doesn't recognize this phone at all anymore, not in fastboot or download mode, or even just booted into Android. If someone could PLEASE show me where a CWM flashable file that will flash the bootloader is, or make me one, I'd pay some good $$$ for it. Please help?
Click to expand...
Click to collapse
Give me a sec I will try to make a flashable CWM with just the bootloader. No need for donations
polobunny said:
You flashed the bootloader & radio with ODIN?
Click to expand...
Click to collapse
I flashed the CRESPO bootloader and radio via fastboot. Then when I tried to flash the ROM update via fastboot it gave me an error. This is when I noticed I was using the CRESPO files instead of the CRESPO 4G files.... Now, after rebooting, my computer WILL NOT recognize the phone at all via usb, in any way, fastboot, ODIN, nothing. But otherwise the phone seems fine. It charges over USB. It boots and I can get into recovery (and I still have CWM) so if I could download a file over wifi (which I can, already tried) and then flash said file via CWM that would flash the new bootloader, I'd be good to go.
rasengan82 said:
Give me a sec I will try to make a flashable CWM with just the bootloader. No need for donations
Click to expand...
Click to collapse
Dude THANK YOU.
I don't think that's possible though, to make a CWM flashable bootloader. :|
Here ya go man. Hope this helps.
https://www.dropbox.com/s/0yemj2aybmdda4f/crespo4g_bootloader_rasengan82.zip
polobunny said:
I don't think that's possible though, to make a CWM flashable bootloader. :|
Click to expand...
Click to collapse
I'm pretty sure it is, as a complete OTA zip will flash the radio, bootload, and ROM, at least I think it will....
rasengan82 said:
Here ya go man. Hope this helps.
https://www.dropbox.com/s/0yemj2aybmdda4f/crespo4g_bootloader_rasengan82.zip
Click to expand...
Click to collapse
Here. Just in case you missed from previous page.
rasengan82 said:
Here. Just in case you missed from previous page.
Click to expand...
Click to collapse
THANK YOU! Worked perfectly. Flashed, rebooted to bootloader, and computer recognized the device again. You are a life saver! You sure no donations are necessary???
supercluver said:
THANK YOU! Worked perfectly. Flashed, rebooted to bootloader, and computer recognized the device again. You are a life saver! You sure no donations are necessary???
Click to expand...
Click to collapse
Nah it's alright man. Glad it worked!
NVM RAS is da man!
Can you put the phone into download mode?
1. Unplug USB and pull the battery. then replace the battery.
2. with the volume up and vol down buttons held down. Press and release the power button for about a sec.
If you get the same as the picture below follow the procedure found here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i flashed a CM nightly build.. which is out nof the norm for me kuz i usually stick with #euroskank and i lost all USB capabilities too. everything else works perfectly, charges fine and all..
i flashed the above zip and it gives me temp access via USB but if my phone goes to sleep or if i reboot im back to square 1 and have to re flash... dunno wtf i did but damn this sucks
kalico17 said:
i flashed a CM nightly build.. which is out nof the norm for me kuz i usually stick with #euroskank and i lost all USB capabilities too. everything else works perfectly, charges fine and all..
i flashed the above zip and it gives me temp access via USB but if my phone goes to sleep or if i reboot im back to square 1 and have to re flash... dunno wtf i did but damn this sucks
Click to expand...
Click to collapse
Did you ever get this resolved? I did something VERY similar when I first started modding on this phone, and experienced VERY similar issues. I have an AWESOME fix, even though it leaves the download screen looking like the oem unlock screen if you put oem lock back on (otherwise it looks normal, and who the heck would do that is beyond me - I only found it when I originally took it back to COMPLETE stock), but it functions fine, and this will take you back to gb, but it seems like the 'fixall' for this phone, and you can always reroot, reflash cwm via fastboot, etc, after using it.
Let me know.
Peace..
~WickiD~
DONT POST IN THE DEVELOPMENT THREAD UNLESS YOU'RE RELEASING A ROM KERNEL OR RECOVERYY!!!
this needs to be moved to Q&A or General...
BIGGEST PET PEEVE!!!!!!!!!

[Q] PLz Help Google logo Stuck

My nexus s m200 ( Korean) phone is stuck with google logo . i was talking on a call when phone hung. I tried to restart it but none of the buttons (Power, Up and Down) worked. so i pulled of my battery reinserted and there it was the horrible google logo sign. I tried every thing i tried to recover by going into recovery but recovery failed then i format wipe user data/ sd card but it didn't resolve my issue i even wiped the cache files as well.....
The Bootloader is locked i have tried everything but it just doesn't unlock... i cannot root from sd card because i have no access on it. i gave it to couple of repairmen but they also failed to understand the issue..........??
I cannot root from any software because the bootloader is locked... i even tried in command by typing "fastboot oem unlock" it does give caution the screen but it when i accept it.. it simply says unlock failed..........??????
i even use Nexus Root Toolkit v.1.6.1 . after unlocking when it reboots the cell phone it again hang up on the google logo. and again i have to pull out the battery inorder to go to bootloader menu... and then it is again locked.. kit has also failed to unlock and resolve my issue...
PLz Helpppppp
What SHould I do...........?? Plz can anyone poit me in the right direction.
Plz help its my first time that i hav bought anything this expensive out of my own hard earned moneu :crying:
Faizan.Waheed said:
My nexus s m200 ( Korean) phone is stuck with google logo . i was talking on a call when phone hung. I tried to restart it but none of the buttons (Power, Up and Down) worked. so i pulled of my battery reinserted and there it was the horrible google logo sign. I tried every thing i tried to recover by going into recovery but recovery failed then i format wipe user data/ sd card but it didn't resolve my issue i even wiped the cache files as well.....
The Bootloader is locked i have tried everything but it just doesn't unlock... i cannot root from sd card because i have no access on it. i gave it to couple of repairmen but they also failed to understand the issue..........??
I cannot root from any software because the bootloader is locked... i even tried in command by typing "fastboot oem unlock" it does give caution the screen but it when i accept it.. it simply says unlock failed..........??????
i even use Nexus Root Toolkit v.1.6.1 . after unlocking when it reboots the cell phone it again hang up on the google logo. and again i have to pull out the battery inorder to go to bootloader menu... and then it is again locked.. kit has also failed to unlock and resolve my issue...
PLz Helpppppp
What SHould I do...........?? Plz can anyone poit me in the right direction.
Plz help its my first time that i hav bought anything this expensive out of my own hard earned moneu :crying:
Click to expand...
Click to collapse
First off, CALM DOWN. The fact that you can see the google logo means your phone isn't dead.
Second, do not pull off the battery when you're stuck. Use Nexus root toolkit if you want to do a reboot. Go to Advanced Utilities, Click "Launch", then click Reboot, Reboot Bootloader, or Reboot Recovery.
Make sure you installed the correct drivers for your specific phone model (m200).
Try using the toolkit and set-up your phone correctly. Use PdaNet drivers. Then try to unlock the bootloader again.
Plz Help
ej8989 said:
First off, CALM DOWN. The fact that you can see the google logo means your phone isn't dead.
Second, do not pull off the battery when you're stuck. Use Nexus root toolkit if you want to do a reboot. Go to Advanced Utilities, Click "Launch", then click Reboot, Reboot Bootloader, or Reboot Recovery.
Make sure you installed the correct drivers for your specific phone model (m200).
Try using the toolkit and set-up your phone correctly. Use PdaNet drivers. Then try to unlock the bootloader again.
Click to expand...
Click to collapse
Yes i did install the PdaNet Drivers and then unlocked it that but still it is somehow locked... The thing is that when i simply turn on phone it stucks with the google logo on it. Then any command that i may type is just ineffective.. Command windows says "Device searching" but if i start the phone in bootloader menu then computer recognizes the device.....?? i just cant figure out what to do.......I have been trying to sort this issue since last monday but all in vein...
So any solution that might entertain this problem
Go to bootloader, flash a custom recovery, then flash a new rom.
ej8989 said:
Go to bootloader, flash a custom recovery, then flash a new rom.
Click to expand...
Click to collapse
Thank you so very much for your concerned and valuable advices.... i Really appreciate it but
PLz can u direct me through some instructions that how to flash a custom recovery and then flash a new room...? What soft wares i will be needing and wht will the procedure........??
amydacus3 said:
Central and elegant location.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Didn't get you bro.....??

Bricked again ?

Hi all,
I just got my TF300T back from Asus after i bricked it.
New software has been installed be Asus and ofc. it was on stock Android 4.2.1
I used Motochopper Rooting Toolkit to root the device and i installed TWRP 2.6.3.0
All went fine up untill here, i copied CM 11 to the tablet and booted up in recovery.
The install of CM 11 failed for some reason so i tried formatting the whole internal storrage.
On top of that i thought it might have been the recovery so i flashed CWM 6.0.2.3 to see if that worked.
I didnt realise i just had deleted the CM 11 .zip file so its not on the tablet anymore.
When i boot up the tablet i can get into recovery (CWM) but i cant get a valid rom in the internal memory.
When i put CM11 or any other rom on a micro SD card the tab/cwm doesnt see the external card.
Also i tried the mounting options and all fail.
I have used a 64Gb card and a 16Gb card, both arnt recognized.
Is there a way to get the .zip rom to my tablet and flash it in CWM?
I think fastboot is broken as well because when i fastboot devices the tab isnt recognize.
At first i could get into fastboot screen but after the tab said cold booting linux its broken as well.
So now i cant boot into the RCK / android / wipe data icon screen anymore since i also wiped data through the wipe data icon.
Only thing that happens now the tablet boots in Asus screen and directly goes into CWM.
Any idea's ?
Cheers
Good news, i got ADB working.
What should i do?
Rgds !
Cheered to soon, seems like all the ADB commands do not work, see ataached image.
ADB devices show a device and when i unplug it it doesnt show a device.
Funny the device name is 12345789ABCDE.....
Any ideas someone ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nobody knows an answer ?
martyzzz said:
Nobody knows an answer ?
Click to expand...
Click to collapse
Did you do NvFlash? that could restore it. Usually Wiping data from that screen ends up in a hard brick.
cmendonc2 said:
Did you do NvFlash? that could restore it. Usually Wiping data from that screen ends up in a hard brick.
Click to expand...
Click to collapse
Unfortunately i didnt do NV flash, it all happened so fast
Im giving up, to bad, the tablet had just been fixed grrr
Any1 wanna take the tablet off my hands ?
Rgds
martyzzz said:
Unfortunately i didnt do NV flash, it all happened so fast
Im giving up, to bad, the tablet had just been fixed grrr
Any1 wanna take the tablet off my hands ?
Rgds
Click to expand...
Click to collapse
It's almost frustrating to see a tablet wrecked that way. I'm not faulting you, just that all of it was totally avoidable with 10 minutes spent skimming the basics. CWM has no version that works with 4.2 bootloader, except the one embedded in the NVflash image which, of course, you ignored. Now if you get to CWM, and type "adb reboot-bootloader", what happens? If it takes you to fastboot, flash the correct version of TWRP 2.6.x.x-4.2). Failing that, search for Buster99's method. Good luck.
graphdarnell said:
It's almost frustrating to see a tablet wrecked that way. I'm not faulting you, just that all of it was totally avoidable with 10 minutes spent skimming the basics. CWM has no version that works with 4.2 bootloader, except the one embedded in the NVflash image which, of course, you ignored. Now if you get to CWM, and type "adb reboot-bootloader", what happens? If it takes you to fastboot, flash the correct version of TWRP 2.6.x.x-4.2). Failing that, search for Buster99's method. Good luck.
Click to expand...
Click to collapse
Thanks for your reply, i will give it 1 more go before i trash the TF300.
BTW i did use TWRP 2.6.X.X-4.2 i just wasnt able to flash a working rom with it, tried several but no dice...
Ill get back when i have tried.
Again thanks
martyzzz said:
Hi all,
I just got my TF300T back from Asus after i bricked it.
New software has been installed be Asus and ofc. it was on stock Android 4.2.1
I used Motochopper Rooting Toolkit to root the device and i installed TWRP 2.6.3.0
All went fine up untill here, i copied CM 11 to the tablet and booted up in recovery.
The install of CM 11 failed for some reason so i tried formatting the whole internal storrage.
On top of that i thought it might have been the recovery so i flashed CWM 6.0.2.3 to see if that worked.
I didnt realise i just had deleted the CM 11 .zip file so its not on the tablet anymore.
When i boot up the tablet i can get into recovery (CWM) but i cant get a valid rom in the internal memory.
When i put CM11 or any other rom on a micro SD card the tab/cwm doesnt see the external card.
Also i tried the mounting options and all fail.
I have used a 64Gb card and a 16Gb card, both arnt recognized.
Is there a way to get the .zip rom to my tablet and flash it in CWM?
I think fastboot is broken as well because when i fastboot devices the tab isnt recognize.
At first i could get into fastboot screen but after the tab said cold booting linux its broken as well.
So now i cant boot into the RCK / android / wipe data icon screen anymore since i also wiped data through the wipe data icon.
Only thing that happens now the tablet boots in Asus screen and directly goes into CWM.
Any idea's ?
Cheers
Click to expand...
Click to collapse
Have you tried this, saved my bricked tab. Thought I was going to have to geta new motherboard at first...
How to unbrick TF300T

I may have bricked my new oneplus6

I got the phone yesterday, I rooted and today I tried to disable fused location, but when I did it and reboot, it shows me a screen, not bootloop, only a screen with asian characters which I don't understand except 'rf' in the middle.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So what I can do? I treated like a hard brick? I tried downloading the package-restrictions.xml file and change from disable to enable but that didn't work.
I was thinking than maybe installing the system from 0 could help but I suppose the zips from here don't work since it doesn't rewrite the data partition, and most probably the fail is there no?
EDIT: More information, seems the error is about an RF test https://forum.xda-developers.com/oneplus-x/help/stuck-rf-test-boot-t3610400
If you have an unlocked bootloader use this to restore to stock. This has saved my phone once.
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
set92 said:
I got the phone yesterday, I rooted and today I tried to disable fused location, but when I did it and reboot, it shows me a screen, not bootloop, only a screen with asian characters which I don't understand except 'rf' in the middle.
So what I can do? I treated like a hard brick? I tried downloading the package-restrictions.xml file and change from disable to enable but that didn't work.
I was thinking than maybe installing the system from 0 could help but I suppose the zips from here don't work since it doesn't rewrite the data partition, and most probably the fail is there no?
EDIT: More information, seems the error is about an RF test https://forum.xda-developers.com/oneplus-x/help/stuck-rf-test-boot-t3610400
Click to expand...
Click to collapse
If post above does not work use the msmtool
I tried the method of miket674, first with "flash-all-partitions-fastboot" and then with "flash-all-partitions" without luck.
I'm trying with your method now, but the part of USB_BULK is not working, or nothing appears or a Oneplus without drivers recognized appear in device manager.
EDIT: I followed the guide, but it showed me an error of sahara communication failed, so I unplug, I tried to power on, but now it don't listen to the power on button.....
EDIT2: Seems now it can wake up or do anything at all, so the guide for fixing hard brick, let the phone worse than hard brick xD I contacted with oneplus support and they told me they need to perform an Inspection but maybe they fix the phone like it were in warranty.
EDIT3: After pressing power on + vol down like 10s or more it boot up to the error from before.
EDIT4: At the end I finished to do all the steps of MsmDownloadTool V4.0 but nothing, he finished, auto booted and the same chinese words with rf in the middle.
EDIT5: Weirdest thing happened, I went to sleep, and 3h later I tried to turn it on and the error was not there, and it welcome me with a clean OOS.... so not sure what fixed it, if the first method or the second, but seems fixed...
EDIT6: Aaaand the error came back when I rebooted because the step of "Adding finishing touches" never ended.
in TWRP
/data/system/users/0/ rename package restriction to .old
this resets your apps that have been disabled to enable incase you break something disabling apps in TIBU
---------- Post added at 02:49 PM ---------- Previous post was at 02:48 PM ----------
why dont you format /data in recovery?
After EDIT6 I tried to format /data from recovery but didn't work, also i think the first method already wipe all the partitions. And I can't access TWRP because now the recovery is the standard one
EDIT: Seems that if I wait more than 10 minutes with the phone turn off and then I boot it, then it goes to a clean OOS, although is the second time getting stuck in "Adding finishing touches", and this time instead of reboot it, I'm going to let it until it wants to end.
EDIT2: 30 minutes later the phone finished with the "Adding finishing touches", so now I'm updating to OOS 5.1.9 and I'll try to reboot it, but I think it will happen as before and it will show me the error, it may possible be happening this because of the 2 partitions? Maybe when I wait 10 minutes to start it boot the other partition which don't have the error.
YOU NEED TO DOWNLOAD MSM TOOL FOR ONEPLUS 6 GO TO QUALCOMM MOD BY PRESSING VOL DOWN + POWER BUTTON DOWNLOAD QUALCOMM TOOL ON
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
set92 said:
I tried the method of miket674, first with "flash-all-partitions-fastboot" and then with "flash-all-partitions" without luck.
I'm trying with your method now, but the part of USB_BULK is not working, or nothing appears or a Oneplus without drivers recognized appear in device manager.
EDIT: I followed the guide, but it showed me an error of sahara communication failed, so I unplug, I tried to power on, but now it don't listen to the power on button.....
EDIT2: Seems now it can wake up or do anything at all, so the guide for fixing hard brick, let the phone worse than hard brick xD I contacted with oneplus support and they told me they need to perform an Inspection but maybe they fix the phone like it were in warranty.
EDIT3: After pressing power on + vol down like 10s or more it boot up to the error from before.
EDIT4: At the end I finished to do all the steps of MsmDownloadTool V4.0 but nothing, he finished, auto booted and the same chinese words with rf in the middle.
EDIT5: Weirdest thing happened, I went to sleep, and 3h later I tried to turn it on and the error was not there, and it welcome me with a clean OOS.... so not sure what fixed it, if the first method or the second, but seems fixed...
EDIT6: Aaaand the error came back when I rebooted because the step of "Adding finishing touches" never ended.
Click to expand...
Click to collapse
It is more than likely a hardware issues then if it came back for no reason at all, I would send to oneplus
Just try to lock the bootloader back which will make your device normal as it came from box then you can unlock it again

Categories

Resources