Hi, I have an old N8010 16GB which was bought from John Lewis in the UK (an official retailer). The tablet has worked great, however recently it screwed up and got stuck in a bootloop.
So I decided to see if I can try to recover it and that's why I am here. I tried Odin and started putting what I thought is the correct firmware on it, however all the firmwares I try all PASS and seem to install correctly but the device still has a infinte bootloop (it crashes and reboots after the Samsung logo shows). I noticed the PIT file says -8G on one of the firmware files - I guess this means it is for the 8GB version which is clearly not going to work on my 16GB version?
Please can someone guide me on what firmware to download and what to try as I have been trying for 5 hours now and cannot find any way to get it out of this boot loop, I have no problems at all installing firmware as it passes every time with Odin. I am using Odin3 v3.10.7
I'm not sure but I think I need this firmware: N8010XXUCMG1
Killer_Klient said:
Hi, I have an old N8010 16GB which was bought from John Lewis in the UK (an official retailer). The tablet has worked great, however recently it screwed up and got stuck in a bootloop.
So I decided to see if I can try to recover it and that's why I am here. I tried Odin and started putting what I thought is the correct firmware on it, however all the firmwares I try all PASS and seem to install correctly but the device still has a infinte bootloop (it crashes and reboots after the Samsung logo shows). I noticed the PIT file says -8G on one of the firmware files - I guess this means it is for the 8GB version which is clearly not going to work on my 16GB version?
Please can someone guide me on what firmware to download and what to try as I have been trying for 5 hours now and cannot find any way to get it out of this boot loop, I have no problems at all installing firmware as it passes every time with Odin. I am using Odin3 v3.10.7
I'm not sure but I think I need this firmware: N8010XXUCMG1
Click to expand...
Click to collapse
Hey, I had the same problem recently and I fixed it using the stock firmware (can't post the link due to forum rules) and using a patched Odin 3.14.1 3B.
Hope it helps
Lets hope the OP has fixed the problem in the last 10 months .Unknown as he never came back .
Disguise link to post it or bit.ly
Flash this in odin https://forum.xda-developers.com/galaxy-note-10-1/orig-development/recovery-twrp-3-2-3-t3895276
Than flash Android 7.1 https://forum.xda-developers.com/galaxy-note-10-1/development/rom-slimroms-slim7-t4128693
Reboot
Done it is back in use
Related
Hey guys, so I have a note 3 n9005,which i had rooted previously. This morning, I tried to flash the new touchwiz kitkat firmware via Odin and failed. Now the phone wouldn't boot up, but I an able to make it into the download mode. I have tried flashing several firmwares but neither of them works, I also had cm11 installed, so odpnt know f the bootloader has been updated or not...
So of anybody could please help me with this, that would be greatly appreciated
i have excatly the same problem tried to update s9005 via odin hong kong version to german 4.4.2 and now wont boot, odin fails only 20 seconds in read so many threads would also like to see some solutions to op.
CaptaiinCaveman said:
Hey guys, so I have a note 3 n9005,which i had rooted previously. This morning, I tried to flash the new touchwiz kitkat firmware via Odin and failed. Now the phone wouldn't boot up, but I an able to make it into the download mode. I have tried flashing several firmwares but neither of them works, I also had cm11 installed, so odpnt know f the bootloader has been updated or not...
So of anybody could please help me with this, that would be greatly appreciated
Click to expand...
Click to collapse
You also need to add some of the stuff it is written in download mode and the log in Odin when in fails. If you went to 4.4.2 on N9005 you can not return to 4.3 (which you should have read by now, there are only 200 posts in 50 threads about it). What kind of N9005 was yours (16/32/64GB), what region/CSC?
xclub_101 said:
You also need to add some of the stuff it is written in download mode and the log in Odin when in fails. If you went to 4.4.2 on N9005 you can not return to 4.3 (which you should have read by now, there are only 200 posts in 50 threads about it). What kind of N9005 was yours (16/32/64GB), what region/CSC?
Click to expand...
Click to collapse
I flashed the DBT FW again with this pit file created by HSDPilot http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77.
It worked and lash was complete now however i am stuck in SAMSUNG logo after restart.
ANy help?
solution
newapostlenew said:
I flashed the DBT FW again with this pit file created by HSDPilot http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77.
It worked and lash was complete now however i am stuck in SAMSUNG logo after restart.
ANy help?
Click to expand...
Click to collapse
hi i followed your instructions afte having the same problem.
once it was flashed and at the samsung logo
i took battery out, replaced it and started phone in recovery mode. go to wipe factory reset
then reboot
mine worked and is ok .
CaptaiinCaveman said:
Hey guys, so I have a note 3 n9005,which i had rooted previously. This morning, I tried to flash the new touchwiz kitkat firmware via Odin and failed. Now the phone wouldn't boot up, but I an able to make it into the download mode. I have tried flashing several firmwares but neither of them works, I also had cm11 installed, so odpnt know f the bootloader has been updated or not...
So of anybody could please help me with this, that would be greatly appreciated
Click to expand...
Click to collapse
darkman13 said:
i have excatly the same problem tried to update s9005 via odin hong kong version to german 4.4.2 and now wont boot, odin fails only 20 seconds in read so many threads would also like to see some solutions to op.
Click to expand...
Click to collapse
Do either of you have a 16 GB version?
Hi All,
My problem :
I wanted to install the official kitkat rom but I made a big mystake : I took N900 files instead of N9005...
After that I successfully installed the right bootloader and CWM.
I installed some cuustom roms but the setupwizard crash at the last step
I tried to flash the complete official 4.4.2 rom but odin failed with message on the phone : "ODIN : invalid ext4 image"
Anybody has any idea to help me ?
hi guys i manage to fix it, well mine anyway worked by flashing the pit i found on xda and selecting repartion on odin 3.7 along with german 4.4.2 to my n9005 from Hong Kong, re booted and done a factory reset via volume button also wiped cache and re started and it came back alive on the selected german rom 4.4.2. hope it hels others. ps my note 3 was from hong kong n9005 32gb
xclub_101 said:
You also need to add some of the stuff it is written in download mode and the log in Odin when in fails. If you went to 4.4.2 on N9005 you can not return to 4.3 (which you should have read by now, there are only 200 posts in 50 threads about it). What kind of N9005 was yours (16/32/64GB), what region/CSC?
Click to expand...
Click to collapse
hey, i wasnt trying to downgrade, i was going from cm11 to official 4.4.2. i've got a 32gb model from france i believe (the box has french written all over it so do the manuals)
newapostlenew said:
I flashed the DBT FW again with this pit file created by HSDPilot http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77.
It worked and lash was complete now however i am stuck in SAMSUNG logo after restart.
ANy help?
Click to expand...
Click to collapse
dude, you are god thank you so much for that, working perfect now
xclub_101 said:
You also need to add some of the stuff it is written in download mode and the log in Odin when in fails. If you went to 4.4.2 on N9005 you can not return to 4.3 (which you should have read by now, there are only 200 posts in 50 threads about it). What kind of N9005 was yours (16/32/64GB), what region/CSC?
Click to expand...
Click to collapse
After installing DBT NB4 FW ( or with Polish NB3 FW) my LTE speeds become almost 0.
I tried multiple installs.
Any guidance?
Quick tip: Uninstall KIES.
Kies is like a big brother.
Use ODIN 1.85 and tick update phone bootloader. That's how I fixed mine. The other versions of Odin wouldn't let me update bootloader.
Of course, before you do this Flash/wipe data in recovery mode.
But uninstalling KIES solved my issue.
Sent from my SM-N9005 using Tapatalk
I know this isnt the right place for this thread, but i lost my other login credentials and had to start fresh, so Im posting here....
Device: SM-T230NU
Problem: I used a website outside of XDA to root my device. I followed the instructions precisely too, I than unplugged the device hoping that replugging and restarting odin would fix the problem i have/had as displayed by the picture. I than tried rebooting the device, and got this error message: Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again. Well I downloaded Kies 3, and much to my surpise I got an error message about the samsung galaxy tab 4 7.0 not being supported by Kies 3. I am now downloading Kies 2.6, so I can atleast get this device booting normally.
If you knew this was not the place to post, why did you post a question here? A play by play of your device root is not of much interest to anyone! I hope you got it fixed up anyway!
It's been fixed. I found an alternate DL site that had Odin in the package..I used ODIN to run cf_auto_root which created that firmware upgrade issue...I had to Odin firmware from the links I found on these forums...it's rooted now though
Hello. I'm a new user of SM G900F (SG). Running on lollipop with latest firmware
Bought it on Dec 26th, the device doesn't have any problem. I was happy back then, jumping form Galaxy Mini 2 to S5 is a big difference experience.
Running on official latest firmware, i only updated the phone once., around 1st - 2nd week of January.
The problem is, on Jan 14th, the G900F fail to boot (bootloop) after i set a new lockscreen from my gallery. It failed to boot, after several attemps, and wipe cache + wipe data, it booted. Haven't backed up my data yet, but i'm happy my phone is working.
On 15th, the same things happened. I set a new lockscreen. It's stil fine. But when a web-browsing on Chrome, the screen is automaically turn off (when not in use in a periout of time), but i immediatey press home button to wake the screen up. the screen didn't turn on, i press the power button. Then the bootloop happened. And this time, i can't go to recovery mode.
I've tried to re-flashing the phone using odin with official firmware, the SG one. But it didn't work. It showed Reset! with blue box on it. But still, m phone is bootlooping. My phone is still bricked. Can't go to the recovery mode either.
P.S: The phone is 2nd handed device from Singapore. I'm an Indonesian, bought the SG version bcs the Indonesia ver (G900H) is still 3G. While the SG one is 4G already. I'm using Indonesian provider (Telkomsel) and works fine on 3G or 4G so i assume the phone is unlocked. I've test the phone imei and it showed that it's the real S5, not the replica one. Antutu test showed 48,xxx score and proved that my device is the real S5 (judge by the name of device written on antutu).
I don't use micro SD. 32 gb is enough for me.
Sorry for long post and bad english. Really desperate to bring life to my phone back. Thanks before.
UPDATE: sometimes when i plugged on the device on my PC with kies on it, it booted to the homescreen. I dont know what exactly i do that caused the device booted, i only remember after stopping the bootloop (installed boot.tar, using this *the 1st method* that caused my knox 0x0, geez i didn't know that), then i flash my phone using the latest firmware (that i believe it's the correct one), then i re-plugged it on my PC with kies open, it booted! But the samsung animation logo played waaaay to long than usual. But it worked. Tried to reboot the phone to check if it's worked completely, unfortunately the device still doing bootloop. Then i tried method 2 from this, failed on odin. Turn on the device, still being jerk by doing bootloop. I gave up. Waiting for solution.
What model number does it say in download mode?
*Detection* said:
What model number does it say in download mode?
Click to expand...
Click to collapse
G900F. I downloaded the G900F SG firmware, too. Since it came from SG.
To rule out firmware (ROM) being the problem, flash this PIT file along with the stock ROM (Same time) in ODIN
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Add the PIT file to the PIT section, and the ROM to the normal PDA or AP section, and flash them together
If it still bootloops after a while after doing that, it's likely a hardware issue
*Detection* said:
To rule out firmware (ROM) being the problem, flash this PIT file along with the stock ROM (Same time) in ODIN
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Add the PIT file to the PIT section, and the ROM to the normal PDA or AP section, and flash them together
If it still bootloops after a while after doing that, it's likely a hardware issue
Click to expand...
Click to collapse
what is PIT file? Read the PIT explanation here, i'm afraid it'd made my device being paperweight. So what's actually PIT file do for my bricked G900F?
Thanks.
firareza said:
what is PIT file? Read the PIT explanation here, i'm afraid it'd made my device being paperweight. So what's actually PIT file do for my bricked G900F?
Thanks.
Click to expand...
Click to collapse
It repartitions the phone, 100% wiping any old firmware, then the new stock ROM will be 100% clean and you will know if it is a hardware or software problem
How can something make your bricked phone a paperweight? It already is a paperweight
If you're gonna second guess everything you're told, enjoy your buggy phone
Hi Guys,
So my friends Note 4 wouldn't boot and i tried everything to fix this flashing every recovery firmware i could find using Odin but i couldn;t get the phone to boot.
I decided to replace the motherboard but i could only find one from China, I have fitted the motherboard and the phone boots fins but its stuck on Android 4.4.4 and I cant install new firmware via the phone and the phone wont connect to Samsung Kies.
Is it worth trying to flash firmware via Odin or will I be stuck in a bootloop again?
I waited a long time for the motherboard and dont want to be back at square 1 again.
The model is N910F if you believe its worth trying and I wont be stuck in a booth loop please can you post a link to the latest firmware below.
Thanks in advance
This is the one that finally worked for me. I went to the SamMobile site to get it. I installed it with Odin.
N910FXXS1DQ15_N910FOXA1DQF1
Tried Flashing TWRP and I did what I was told, as soon as ODIN rebooted the tablet, I pressed Power+Home+VolUP, and I ended up getting a black screen with lines through it. Whenever I try to turn the Tablet off, the screen flashes. I was told to fix this by flashing stock firmware via odin. Wanted to make sure I'm downloaded the correct firmware. This is the link I'm downloading from -
https://samfrew.com/download/Galaxy__Tab__A⑥__/d0qj/XAR/T580UEU4CSC1/T580XAR4CSC1/
Also - was wondering why this happened ? I used what I believed to be the latest TWRP
Silicon Knight said:
Tried Flashing TWRP and I did what I was told, as soon as ODIN rebooted the tablet, I pressed Power+Home+VolUP, and I ended up getting a black screen with lines through it. Whenever I try to turn the Tablet off, the screen flashes. I was told to fix this by flashing stock firmware via odin. Wanted to make sure I'm downloaded the correct firmware. This is the link I'm downloading from -
https://samfrew.com/download/Galaxy__Tab__A⑥__/d0qj/XAR/T580UEU4CSC1/T580XAR4CSC1/
Also - was wondering why this happened ? I used what I believed to be the latest TWRP
Click to expand...
Click to collapse
I have no idea about the correct firmware, but I believe you used a "bad" TWRP. When I first got my tab in November I searched through all TWRP threads and kept finding mentions of those lines. I then flashed the OMNI6 version and never had an issue.
The last one is HERE - maybe try that one?
Good luck either way :fingers-crossed: