So it's the problem that so many other people seemed to have before, I've just bought my new Nexus 6. And can't update it. It's brand new. I just get the message ''Error'' I reboot it and it works again. And it says it has the latest update, It don't. I now nothing about sideloading stuff. I'm swedish don't have a clue what to download or anything, Tried deleting cache memory, Factory reset and it still don't work. It's a god damn Nexus phone! Shouldn't it work out of the box especially with updates? Please help.
its a nexus, you can always manually flash a factory image
But how would i do that? If i might ask :3
jonisen said:
But how would i do that? If i might ask :3
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
---------- Post added at 09:38 PM ---------- Previous post was at 09:36 PM ----------
its actually much easier than it sounds, you'll realize that after.
simms22 said:
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
---------- Post added at 09:38 PM ---------- Previous post was at 09:36 PM ----------
its actually much easier than it sounds, you'll realize that after.
Click to expand...
Click to collapse
Thank you! I'm just wondering, What factory Image should i download? from https://developers.google.com/android/nexus/images#bullhead I'm in Sweden with 4G network if that helps
jonisen said:
Thank you! I'm just wondering, What factory Image should i download? from https://developers.google.com/android/nexus/images#bullhead I'm in Sweden with 4G network if that helps
Click to expand...
Click to collapse
the very latest one, MMB29V
Now i have a problem, The update was a failure and now i can't go into my phone it's a loading screen and never goes away
jonisen said:
Now i have a problem, The update was a failure and now i can't go into my phone it's a loading screen and never goes away
Click to expand...
Click to collapse
How did it fail?
An error message / screenshot would help.
Did you use the flash-all script or flash each file manually?
Details, please... As already stated by murtaza02.
I just wanted to chip in and say that I hope you used the factory image for Nexus 6 (Shamu), since your link is to Nexus 5X (Bullhead). Bad things can happen if you use the wrong images...
And, if you want, I could help you out in swedish, if that would be any help. Just PM me...
So i got the phone replaced, It went fine. They didn't seem to care about it. New phone same problem. Can't update. C'MON GOOGLE. It's a software bugg? What am i supposed to do? I've already destroyed one lol
IIRC this was a relatively common problem around the time of 5.1.
Either the OTA update itself is corrupt or there's something on the phone that messes with the verification prior to updating. Before the screen with a dead android and "Error!", are you getting error messages along the lines of:
system partition has unexpected contents
E: Error in chace/update.zip
status 7
install aborted
You could try factory resetting and clearing cache in recovery. It might work, it might not...
1 - Turn off your phone
2 - Hold and press power button and volume down at the same time until you get to the bootloader screen (an android on its back with a bunch of information about your system).
3 - Use the volume buttons to select "Recovery mode" and press power.
4 - You'll get another android lying on it's back. Press both power button and volume up to enter the recovery.
5 - Use the volume buttons to highlight "wipe data/factory reset" and press power to confirm. Do the same with "wipe cache partition".
If you can get a working update after this, great. But, if the problem persists, you have two options. Get the phone replaced again or use a factory image to update to the latest android (currently 6.0.1 MMB29V). If you want to try flashing a factory image again, i'd suggest you first tell us EXACTLY (every singel detail) what you did last time, since it didn't seem to go too well...
Related
This should return your phone to a completely stock state in case you want to grab an OTA update or return the phone.
Instructions:
1) Download update-thrill-stock-rom-rooted.zip and place it on your SD card.
2) Power off your phone.
3) With the phone powered off, hold the volume down button, the 3D button, and the power button until you see the LG logo and then release. This should boot you into CWM.
4) Select "wipe data/factory reset".
5) Select "install zip from sdcard" and navigate to and select update-thrill-stock-rom.zip.
6) When it finishes flashing, select "reboot system now".
7) Download recovery.backup and place it on you internal SD card.
8) Run these adb commands:
Code:
adb shell
Code:
su
Code:
dd if=/sdcard/recovery.backup of=/dev/block/mmcblk0p6 bs=4096
Code:
rm /sdcard/recovery.backup
Code:
reboot
9) Finally, unroot using SuperOneClick and you should be completely stock.
----Downloads----
update-thrill-stock-rom-rooted.zip
recovery.backup
---------- Post added at 11:38 PM ---------- Previous post was at 11:33 PM ----------
I haven't tried this yet, so let me know if it works
Thank you gtg. if i were not stuck at my store doing inventory I would try it!
Sent from my SAMSUNG-SGH-I997 using XDA App
My device wont boot the rom just stays on LG anyone else having this issue?
Thanks
sent from my evo 4g
N!ghtgold said:
My device wont boot the rom just stays on LG anyone else having this issue?
Click to expand...
Click to collapse
Ok. Let me do it a different way then. Will post a new zip soon that will definitely work.
---------- Post added at 11:12 AM ---------- Previous post was at 10:20 AM ----------
N!ghtgold said:
My device wont boot the rom just stays on LG anyone else having this issue?
Click to expand...
Click to collapse
Once I get this new version up you can boot into CWM and push it to your phone using the following adb command. Then proceed from step 4.
Code:
adb push update-thrill-stock-rom-rooted.zip /sdcard
edit: Crap, couldn't get it uploaded in time. Have to run to an appointment. Will upload a little later.
gtg465x said:
Ok. Let me do it a different way then. Will post a new zip soon that will definitely work.
---------- Post added at 11:12 AM ---------- Previous post was at 10:20 AM ----------
Once I get this new version up you can boot into CWM and push it to your phone using the following adb command. Then proceed from step 4.
Code:
adb push update-thrill-stock-rom-rooted.zip /sdcard
edit: Crap, couldn't get it uploaded in time. Have to run to an appointment. Will upload a little later.
Click to expand...
Click to collapse
Just in time for everyone to return them!!! LOL
he Galaxy S II will be available starting October 2 for $199.99 w/2-yr contract! Min. $15/month data plan req'd. social.att.com/VDq
check their twitter and facebook
I still think it is silly to buy the phone...he is testing the Celox now (1.5 Snapdragon proc with LTE)
00mred00 said:
Just in time for everyone to return them!!! LOL
he Galaxy S II will be available starting October 2 for $199.99 w/2-yr contract! Min. $15/month data plan req'd. social.att.com/VDq
check their twitter and facebook
I still think it is silly to buy the phone...he is testing the Celox now (1.5 Snapdragon proc with LTE)
Click to expand...
Click to collapse
There will always be a better phone on the horizon though. Gotta jump at some point.
gtg465x said:
There will always be a better phone on the horizon though. Gotta jump at some point.
Click to expand...
Click to collapse
True...but I hate buyers remorse
I am going to hold out for LTE and the bigger screen
This Samsung friend of mine has one now, and he was spot on with the release date he gave me 2 months ago...so I'd say the Celox could be in hand within 2 months for sure. Hoping to play with the Test model he has soon (and get a release date)
Still may keep the thrill though. With your ROM this thing is pretty nifty...plus we have other upgrades available on our lines so....
but to stay on topic...I leave early today and will try out whatever you get going later today
K it's up.
gtg465x said:
K it's up.
Click to expand...
Click to collapse
Thanks GTG your the man Back to stock brotha
Thanks a lot I like this phone but I am not sure if I got lemon or what , Playing pandora radio it squeals all the time no matter what rom I use, the music on music player skips all the time too. I sometimes have to push icons 3 or 4 times to get them to register my touch. and the home row icons I cannot even use them half the time because they don't even do anything when I touch them. I think there might be a problem with the screen. But that is not all that is wrong. I have the phone freeze for 5 to 10 seconds at a time a whole lot and have to reboot. Just to many problems for me, so I really need to go back to stock to get a new phone. I will prob just get a galaxy SII instead. I sure did like recording in 3d my 6 year old playing sports and such was cool , then watching it on our 73 inch 3d tv she loved it.
I'm confused now. what is best thing to do flash back stock rom or keep the custom rom.
ueshada said:
I'm confused now. what is best thing to do flash back stock rom or keep the custom rom.
Click to expand...
Click to collapse
Unless you have a reason to such as wanting to return the phone or when there is an update coming, I would keep the custom ROM.
Unless you have a reason to such as wanting to return the phone or when there is an update coming, I would keep the custom ROM.
Click to expand...
Click to collapse
I have stupid question can't I get the update just flashing the stock rom. Do I need to unroot and remove cwm
ueshada said:
I have stupid question can't I get the update just flashing the stock rom. Do I need to unroot and remove cwm
Click to expand...
Click to collapse
Yeah, I would think you definitely need to flash stock recovery before updating. You might as well unroot while you're at it because that screws up updates on some phones too.
Ok Back to stock everything work perfect ............ waiting for updates
Unless you have heard of the update coming within the next day or two, I am going to keep Thriller on mine until I hear otherwise. No reason to flash back until the update is released.
thank you for this! worked wonderfully
Trouble pushing recovery.backup
Thanks for the information!
For some reason when I try the thing after the su command it gives me that I cannot open the file for write. I have debugging mode turned on.
Can someone help?
EDIT: Nevermind, needed to update to the latest superuser
I'm new to this forum and quite a newbie. I have not rooted my phone or unlocked my bootloader. I have just always been happy with the OTA updates. I tried doing the newest update to Android 4.3. When the phone tried to reboot after installing the update, the phone got stuck on the HTC quietly brilliant screen. It wouldn't leave that screen at all, even after leaving it overnight.
I am able to boot into the bootloader. I tried to load a ROM using fastboot, but it didn't work. I am S-ON and don't really want to change anything on my phone in that sense. Is there any way that I can install the stock ROM for 4.3 to get my phone working again? If so, where can I find the files for that?
Thanks
Did you try a factory reset?
Flash~a~holic!
Yes I did try a factory reset. It did not work. It still got stuck on the same screen.
If your phone is stock then take it to a sprint store with a service center, tell them exactly what you posted here and I'm sure they can flash it for you and get it working again. If the OTA broke it.... they should fix it.
I actually went to a Sprint store and they sent for a replacement phone, so I will at least get it resolved sometime. They told me it would take a week though, so I was hoping there was something I could do that would fix it and get me a working phone quicker. Thanks for your suggestions though!
When you took it too sprint what did they say i have the same problem does anyone know how to fix this
---------- Post added at 09:16 PM ---------- Previous post was at 09:14 PM ----------
i reverted to stock updated to 4.3 then re rooted and applied the viperboy system re writeable viper mod and then restarted it and now its stuck here
krayziecali said:
When you took it too sprint what did they say i have the same problem does anyone know how to fix this
---------- Post added at 09:16 PM ---------- Previous post was at 09:14 PM ----------
i reverted to stock updated to 4.3 then re rooted and applied the viperboy system re writeable viper mod and then restarted it and now its stuck here
Click to expand...
Click to collapse
As far as I know there is no reason to to use system write btw it's for the older versions not 4.3
bigdaddy619 said:
As far as I know there is no reason to to use system write btw it's for the older versions not 4.3
Click to expand...
Click to collapse
Damn it so how do i get out of the HTC quietly brilliant screen im i gonna have to take it to sprint its rooted and it shows "This build is for Developer message"
krayziecali said:
Damn it so how do i get out of the HTC quietly brilliant screen im i gonna have to take it to sprint its rooted and it shows "This build is for Developer message"
Click to expand...
Click to collapse
Hold the power button until the light stop blinking then when it start to reboot hold the vol down button and it will bring you to bootloader once the boot to twrp and sideload a rom
bigdaddy619 said:
Hold the power button until the light stop blinking then when it start to reboot hold the vol down button and it will bring you to bootloader once the boot to twrp and sideload a rom
Click to expand...
Click to collapse
my back and home keys just keep blinking and it never reboots
got it into boot loader will try a rom
Keep holding power til they stop blinking
I tried flashing the marshmallow update that was just released (a very, very idiotic move) I flashed it the first time and all seemed well; everything flashed with no errors, and it rebooted. Well, upon reboot, I get the dreaded Factory Reset Status 2. Okay, no big deal, I just realized that I forgot to select "BOARD DL". I got to try to flash again, this time selected BOARD. Now, I get a dodownloaderror at 18s. Every time. I have tried everything, battery pulls, reflashing, I even tried reflashing ZV6 (this is probably what dug my grave). Nothing. I can still boot to recovery and DL mode, but nothing is working. I didn't put a stock img on my internal storage, so sideloading from recovery isn't an option either.
I am such an idiot. Now I have a paperweight, and it is going to cost me several hundred, if not a thousand, dollars to end my contract on the brick and then go out and buy a new phone.
Does anyone have an methods that I haven't tried?
Did I mention that I am a huge idiot?
ironbesterer said:
I tried flashing the marshmallow update that was just released (a very, very idiotic move) I flashed it the first time and all seemed well; everything flashed with no errors, and it rebooted. Well, upon reboot, I get the dreaded Factory Reset Status 2. Okay, no big deal, I just realized that I forgot to select "BOARD DL". I got to try to flash again, this time selected BOARD. Now, I get a dodownloaderror at 18s. Every time. I have tried everything, battery pulls, reflashing, I even tried reflashing ZV6 (this is probably what dug my grave). Nothing. I can still boot to recovery and DL mode, but nothing is working. I didn't put a stock img on my internal storage, so sideloading from recovery isn't an option either.
I am such an idiot. Now I have a paperweight, and it is going to cost me several hundred, if not a thousand, dollars to end my contract on the brick and then go out and buy a new phone.
Does anyone have an methods that I haven't tried?
Did I mention that I am a huge idiot?
Click to expand...
Click to collapse
Same here..
Why are you both flashing MM? Is there an official image to flash?
EmSeeMAC said:
Why are you both flashing MM? Is there an official image to flash?
Click to expand...
Click to collapse
That's why I'm an idiot. It's not an official .TOT.
ironbesterer said:
That's why I'm an idiot. It's not an official .TOT.
Click to expand...
Click to collapse
I fixed mines using LG UP
http://forum.xda-developers.com/sprint-g4/development/howto-downgrade-to-zv6-upgrade-to-t3265976
This should help you fix the dreaded 2
If you can boot into download mode, flash the ROM for your phone on sammobile
Just say you installed an update and it bricked your phone if it's still under warranty. I dunno how many times I botched my G Flex 2 and LG replaced it (ATT model).
Why is it gonna cost you $1000.00. At worst you just buy another phone.
But the cheapest is to add TEP and bring it in. You might want to brick it hard enough that they cannot see that it was every rooted though
He fixed it
ironbesterer said:
I tried flashing the marshmallow update that was just released (a very, very idiotic move) I flashed it the first time and all seemed well; everything flashed with no errors, and it rebooted. Well, upon reboot, I get the dreaded Factory Reset Status 2. Okay, no big deal, I just realized that I forgot to select "BOARD DL". I got to try to flash again, this time selected BOARD. Now, I get a dodownloaderror at 18s. Every time. I have tried everything, battery pulls, reflashing, I even tried reflashing ZV6 (this is probably what dug my grave). Nothing. I can still boot to recovery and DL mode, but nothing is working. I didn't put a stock img on my internal storage, so sideloading from recovery isn't an option either.
I am such an idiot. Now I have a paperweight, and it is going to cost me several hundred, if not a thousand, dollars to end my contract on the brick and then go out and buy a new phone.
Does anyone have an methods that I haven't tried?
Did I mention that I am a huge idiot?
Click to expand...
Click to collapse
Okay, if you can get to download mode, then use the 'send_command' batch file to adb push a stock image to /dev/media/0/ then dd it.
---------- Post added at 05:55 PM ---------- Previous post was at 05:52 PM ----------
mswlogo said:
Why is it gonna cost you $1000.00. At worst you just buy another phone.
But the cheapest is to add TEP and bring it in. You might want to brick it hard enough that they cannot see that it was every rooted though
Click to expand...
Click to collapse
Hahaha this.
With a bootloader that's totally locked down you can just say that you accepted an OTA and your battery died while it was flashing and now your phone is screwed.
agentfusion said:
Okay, if you can get to download mode, then use the 'send_command' batch file to adb push a stock image to /dev/media/0/ then dd it.
---------- Post added at 05:55 PM ---------- Previous post was at 05:52 PM ----------
Hahaha this.
With a bootloader that's totally locked down you can just say that you accepted an OTA and your battery died while it was flashing and now your phone is screwed.
Click to expand...
Click to collapse
It would be close to a thousand to pay off my current device (around $300 owed on it) and then go out and buy a new one. But, with autoprime and awesomeslayerg's help, I got my phone back to normal.
I'm glad I seen this before I tried that
It seems that I may have flashed one to many times or something else is playing up. Anywho, I came to check my phone this morning and everything was working fine. Checked the battery status and I thought it was time for a top-up . I decide to do it via USB via my computer and that's when things started to go south. I came back to check my phone and...nothing. I done a hard restart and at first everything seemed fine only to get a continuous boot-loop. I tried to enter TWRP and it hangs on the "teamwin" logo. Then I decided to flash stock via Odin and I still get the same boot-loop. I can still access downloader but that's it.
For reference the version of TWRP I was running was 2.8.6.1 (flashed back to 2.8 Nova version) and the ROM I was running was the latest version of Ressurection Remix by Maclaw.
So, I'm open to any suggestions. Any help would be much appreciated and paid forward.
Thanks for hearing me out.
So going by the lack of feedback I'm basically screwed?
Oh for ****s sake come on! I've had this up for 3 days on this site full of so called enthusiasts and "professionals" and not one response? I'm sorely disappointed.
So there is honestly no one that can help me with this?
Pathetic...
Come on there must be someone that can help me with this, otherwise I'll have to risk buying a broken one for parts.
Haven't done any custom stuff in a while but the boot loop sounds familiar, have you wiped the dalvik cache in the advanced menu also have you tried a factory reset?
---------- Post added at 12:35 PM ---------- Previous post was at 12:30 PM ----------
Use the Volume keys in order to navigate through the recovery menu.
Select “advanced” and choose “wipe dalvik cache”.
Return to main menu.
Then select “wipe data factory reset”.
Return and this time choose “wipe cache partition”.
Return and select “reboot system now”.
Your handset should start in Android OS now.
Grumpy Cat said:
It seems that I may have flashed one to many times or something else is playing up. Anywho, I came to check my phone this morning and everything was working fine. Checked the battery status and I thought it was time for a top-up . I decide to do it via USB via my computer and that's when things started to go south. I came back to check my phone and...nothing. I done a hard restart and at first everything seemed fine only to get a continuous boot-loop. I tried to enter TWRP and it hangs on the "teamwin" logo. Then I decided to flash stock via Odin and I still get the same boot-loop. I can still access downloader but that's it.
For reference the version of TWRP I was running was 2.8.6.1 (flashed back to 2.8 Nova version) and the ROM I was running was the latest version of Ressurection Remix by Maclaw.
So, I'm open to any suggestions. Any help would be much appreciated and paid forward.
Thanks for hearing me out.
Click to expand...
Click to collapse
TheMadTurnip said:
Haven't done any custom stuff in a while but the boot loop sounds familiar, have you wiped the dalvik cache in the advanced menu also have you tried a factory reset?
---------- Post added at 12:35 PM ---------- Previous post was at 12:30 PM ----------
Use the Volume keys in order to navigate through the recovery menu.
Select “advanced” and choose “wipe dalvik cache”.
Return to main menu.
Then select “wipe data factory reset”.
Return and this time choose “wipe cache partition”.
Return and select “reboot system now”.
Your handset should start in Android OS now.
Click to expand...
Click to collapse
Thanks for the feedback but as I have already stated I can't access any recovery only Odin, and desktop Odin won't allow me to re-partition only write. Still, whether it be stock or a custom ROM it is the same result: bootloop and recovery freezes on splash screen.
So any other takers? Yes? No?
Why even have a "help & troubleshooting" section if, well, I don't know, no one helps!!!
Dude you're puerile attitude is baffling, I understand you desperately want help, but do you really think you'll get it if you keep throwing toys out of your pram?
The problem you've described suggests that you're phone is 'fixable' however, it may take a few different methods to restore it. Ok, so you cannot access recovery mode, therefore you're unable to clear your phone like TheMadTurnip suggested, and you're also unable to access any backup you might have made. The downloader works so I can only recommend you try to investigate what's going wrong when you flash via Odin, does the flash show as pass or fail? Have you tried flashing using a different cable or computer, heck have you even tried using another version of Odin? Is Kies installed on your computer, if so then remove it. Have you flashed using a PIT file as well as the stock firmware? Elaborate on your situation so tailored advice can be given to you.
Kind Regards,
Pinda
Pinda007 said:
Dude you're puerile attitude is baffling, I understand you desperately want help, but do you really think you'll get it if you keep throwing toys out of your pram?
Click to expand...
Click to collapse
In light of how active this section still is I think a week is more than enough time to expect a response, I was even quite polite in my OP. Even a simple "no I can't help but maybe try this" would have sufficed. But I'll take it under advisement...
Pinda007 said:
does the flash show as pass or fail?
Click to expand...
Click to collapse
It shows a pass, won't allow me to re-partition though.
Pinda007 said:
Have you tried flashing using a different cable or computer, heck have you even tried using another version of Odin?
Click to expand...
Click to collapse
I have tried flashing using the original cable the phone came with; so I have tried 2. I even tried other USB ports. And yes I have tried another version of Odin.
Flashing doesn't seem to be a problem at the moment, just everything else.
Pinda007 said:
Is Kies installed on your computer, if so then remove it.
Click to expand...
Click to collapse
It is installed along with the Samsung USB driver. Having it installed hasn't caused a problem. I'll uninstall it if you think that will help.
Pinda007 said:
Have you flashed using a PIT file as well as the stock firmware? Elaborate on your situation so tailored advice can be given to you.
Click to expand...
Click to collapse
A pit file? And yes, as I have already mentioned I have installed the stock firmware.
Grumpy Cat said:
In light of how active this section still is I think a week is more than enough time to expect a response, I was even quite polite in my OP. Even a simple "no I can't help but maybe try this" would have sufficed. But I'll take it under advisement...
It shows a pass, won't allow me to re-partition though.
I have tried flashing using the original cable the phone came with; so I have tried 2. I even tried other USB ports. And yes I have tried another version of Odin.
Flashing doesn't seem to be a problem at the moment, just everything else.
It is installed along with the Samsung USB driver. Having it installed hasn't caused a problem. I'll uninstall it if you think that will help.
A pit file? And yes, as I have already mentioned I have installed the stock firmware.
Click to expand...
Click to collapse
As it stands it's about ruling things out to pinpoint what's going wrong, I'm no expert, merely a trial and error kind of guy. Anyway, yes, I would suggest uninstalling Kies and try the flash again, although if Odin is flashing successfully then this might not be the issue, but it's worth a shot. When I resolved my bootloop, using a PIT file was one of the things I did, so perhaps that's something you might want to look into. Also, make sure your firmware downloads are clean, basically make sure they download smoothly and aren't disturbed by a network disconnection etc. Could you post links to where you downloaded your stock firmware?
Pinda007 said:
As it stands it's about ruling things out to pinpoint what's going wrong, I'm no expert, merely a trial and error kind of guy. Anyway, yes, I would suggest uninstalling Kies and try the flash again, although if Odin is flashing successfully then this might not be the issue, but it's worth a shot. When I resolved my bootloop using a PIT file was one of the things I did, so perhaps that's something you might want to look into. Also, make sure your firmware downloads are clean, basically make sure they download smoothly and aren't disturbed by a network disconnection etc. Could you post links to where you downloaded your stock firmware?
Click to expand...
Click to collapse
I got my firmware from sammobile.com, right down to my network provider. I've flashed it before and never had any problems. I'm just trying to figure out why my phone self-bricked. I was on latest "Resurrection Remix" when it happened.
Where can I find this "PIT" file and how do I use it? I notice an option in Odin so I can probably figure that part out. At the moment my knowledge is limited to rooting, flashing custom recoveries and ROMs. Sorry.
Grumpy Cat said:
I got my firmware from sammobile.com, right down to my network provider. I've flashed it before and never had any problems. I'm just trying to figure out why my phone self-bricked. I was on latest "Resurrection Remix" when it happened.
Where can I find this "PIT" file and how do I use it? I notice an option in Odin so I can probably figure that part out. At the moment my knowledge is limited to rooting, flashing custom recoveries and ROMs. Sorry.
Click to expand...
Click to collapse
Ahh ok, yes my knowledge is also limited in that respect. I guess it's all about learning and helping each other out, which is where I guess it can be frustrating when there's a lack of 'available' support in these forums. Nevertheless, I must stop droning on, I used a PIT file for my S variant after noticing numerous users mentioning the significance of it when using Odin to flash. Here's an interesting thread to find out more (http://forum.xda-developers.com/showthread.php?t=999097). It's a sort of map if you like, which inadvertently tells the software where everything has to go on the handset, that's my noob interpretation of it anyway. I found the relevant PIT file for my variant on a XDA thread, so it might be worth scurrying through archived threads to see if you can find one for your phone, make sure there's legit feedback for it though. You just flash it with the firmware like you normally would.
Remember, I'm no expert, I'm just going by how I fixed my phone over the weekend. I apologise my attempts to help are meager, I'm still relatively new to all this, just like you.
Pinda007 said:
Ahh ok, yes my knowledge is also limited in that respect. I guess it's all about learning and helping each other out, which is where I guess it can be frustrating when there's a lack of 'available' support in these forums. Nevertheless, I must stop droning on, I used a PIT file for my S variant after noticing numerous users mentioning the significance of it when using Odin to flash. Here's an interesting thread to find out more (http://forum.xda-developers.com/showthread.php?t=999097). It's a sort of map if you like, which inadvertently tells the software where everything has to go on the handset, that's my noob interpretation of it anyway. I found the relevant PIT file for my variant on a XDA thread, so it might be worth scurrying through archived threads to see if you can find one for your phone, make sure there's legit feedback for it though. You just flash it with the firmware like you normally would.
Remember, I'm no expert, I'm just going by how I fixed my phone over the weekend. I apologise my attempts to help are meager, I'm still relatively new to all this, just like you.
Click to expand...
Click to collapse
I tried installing stock firmware with the PIT file I found here and still get the same result. I might be screwed.
Grumpy Cat said:
I tried installing stock firmware with the PIT file I found here and still get the same result. I might be screwed.
Click to expand...
Click to collapse
I think that's the exact file that worked for me
I don't know what else to suggest at the moment, the fact that you cannot get into recovery makes it that much harder.
I'll come back to you if something comes to mind.
EDIT- Have you tried re flashing a custom recovery to overwrite your current one? If you can somehow get into recovery you could trying clearing your phone of cache and installing a ROM zip-folder. Also, have you got another battery you can try in your handset? I cannot help you with the Odin method no because you've pretty much exhausted all the possible solutions that I know of, perhaps screenshot the Odin log and post it on here for more info.
My s3 mini also got same problem.any solution found
My wife received an update notification today on her Note 9 (SM-N960F). I was quite excited as I'm still waiting for the update to pop up on mine.
Anyways, after the update finished the phone rebooted and after the unlock part there is a little unlocking animation which goes on until the phone restarts again, after failing to boot the second time this error message shows up (see picture).
Anyone knows how to fix this without wiping all data/factory reset? I went to the recovery and wiped the cache partition, but didn't help... I can only use adb in sideload mode, but I'm not an expert so don't know if that helps or not... I also tried booting in Safe Mode, but it was just loading and then restarting again.
Take it to the service center and let them help you. They might be able to do without factory reset. Fingers crossed
raul6 said:
Take it to the service center and let them help you. They might be able to do without factory reset. Fingers crossed
Click to expand...
Click to collapse
I just had a conversation with them on the chat and they suggested the same thing. Luckily there is one 5 minutes away so I will go in tomorrow.
In case this happened to anyone else, please let me know if they were able to fix it without losing all data.
UPDATE -------------------
I think, I've found the issue! She had Substratum theme installed and I think that's causing the bootloop. I tried sideloading SubstratumRescue.zip but it says Signature verification failed.
Any suggestions?
atti12 said:
I just had a conversation with them on the chat and they suggested the same thing. Luckily there is one 5 minutes away so I will go in tomorrow.
In case this happened to anyone else, please let me know if they were able to fix it without losing all data.
UPDATE -------------------
I think, I've found the issue! She had Substratum theme installed and I think that's causing the bootloop. I tried sideloading SubstratumRescue.zip but it says Signature verification failed.
Any suggestions?
Click to expand...
Click to collapse
I've been in a post substratum/update hell before. Unfortunately, the only way I fixed it was to factory reset. Sorry I couldn't help
marky310 said:
I've been in a post substratum/update hell before. Unfortunately, the only way I fixed it was to factory reset. Sorry I couldn't help
Click to expand...
Click to collapse
Ugh, that's going to be a pain! Any way to back up the phone before I reset it?
Sad will be if they tell you that they need to wipe it...
I still haven't got the update! What can I do?
melchiar said:
I still haven't got the update! What can I do?
Click to expand...
Click to collapse
Grab a coffee! Kick back and relax then wait for Samsung to release the update for you!! LOL I’m joking!! if you search xda dude you can update it manually!!
---------- Post added at 01:02 PM ---------- Previous post was at 12:57 PM ----------
atti12 said:
My wife received an update notification today on her Note 9 (SM-N960F). I was quite excited as I'm still waiting for the update to pop up on mine.
Anyways, after the update finished the phone rebooted and after the unlock part there is a little unlocking animation which goes on until the phone restarts again, after failing to boot the second time this error message shows up (see picture).
Anyone knows how to fix this without wiping all data/factory reset? I went to the recovery and wiped the cache partition, but didn't help... I can only use adb in sideload mode, but I'm not an expert so don't know if that helps or not... I also tried booting in Safe Mode, but it was just loading and then restarting again.
Click to expand...
Click to collapse
Have you looked into ABD Commands? As you should be able to back up your Note-9 that way! Google search and XDA search are you best friends! That’s if you not familiar with CMD and ABD Commands!
N1NJATH3ORY said:
Grab a coffee! Kick back and relax then wait for Samsung to release the update for you!! LOL I’m joking!! if you search xda dude you can update it manually!!
[/B]
Click to expand...
Click to collapse
I don't want to lose OTA..
melchiar said:
I don't want to lose OTA..
Click to expand...
Click to collapse
You shouldn't, just make sure the firmware you are flashing is the one that your csc supports...
Just note, Samsung seem to be releasing generic roms that have multiple csc support... Just check yours is supported...
N1NJATH3ORY said:
Grab a coffee! Kick back and relax then wait for Samsung to release the update for you!! LOL I’m joking!! if you search xda dude you can update it manually!!
---------- Post added at 01:02 PM ---------- Previous post was at 12:57 PM ----------
Have you looked into ABD Commands? As you should be able to back up your Note-9 that way! Google search and XDA search are you best friends! That’s if you not familiar with CMD and ABD Commands!
Click to expand...
Click to collapse
USB Debugging wasn't enabled, so I could only use ADB in sideload mode which was pretty useless. I'm pretty sure substratum messed up the phone so it would have been an easy fix with fully working ADB...
Anyways the engineers were useless so I had to reset the phone and it's working again.
Thanks guys!