hi,
i flashed my tab to try the 4.1.2 us version and it changed my device name to n8013, i have a uk n8010, now i flashed it back to stock 4.0.4 using odin and the stock uk rom from samfirmware, however my device is still at 8013 and gives me binary counts too, and also i cant get no ota updates
i used triangle away and i am left with one count,
all i can guess is that i still have the n8013 stock recovery
i need n8010 uk stock recovery
could any one help me out with this please
ashvirk said:
hi,
i flashed my tab to try the 4.1.2 us version and it changed my device name to n8013, i have a uk n8010, now i flashed it back to stock 4.0.4 using odin and the stock uk rom from samfirmware, however my device is still at 8013 and gives me binary counts too, and also i cant get no ota updates
i used triangle away and i am left with one count,
all i can guess is that i still have the n8013 stock recovery
i need n8010 uk stock recovery
could any one help me out with this please
Click to expand...
Click to collapse
See your identical post .
Hi. As i said before i have flashed the official stock n8010 rom after triangle away and its still showing custom binary. There is a way to flash stock recovery using odin. And stock recovery is different for different models
Sent from my Nexus 4 using XDA Premium HD app
ashvirk said:
Hi. As i said before i have flashed the official stock n8010 rom after triangle away and its still showing custom binary. There is a way to flash stock recovery using odin. And stock recovery is different for different models
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
RUN TA rom counter zero .
Flash stock rom via Odin.
Factory reset .
Check three rom status indications are ok .
Stock recovery is identical and part of the stock firmware 8010 is 8013 .
jje
Hi. Done as u said. Still when i switch to odin mode my tab name is n8013. With counter set to 1 and the firmware is shown a custom even thou its an official one.
This problem only occurred after i installed a n8013 4.1.2 official rom. Before that flashing with odin never changed any thing. Could u please confirm if u have a n8010 that when in recovery mode. Which version recovery is on the top. Mine is 3e. I really confused with this. I tried what u adviced 3 times tried it with 2 different official roms. One from sammobile and one from samsung ota itself. The tab updates is on 4.0.4 official rom via ota.but if i check updates on 4.1.1 after the official update it says that my tab has been modified and i cant update.
Sent from my Nexus 4 using XDA Premium HD app
3e is stock recovery .
tab name
???
this is Note forum are you using Tab firmware ???
jje
Hi. Thanks for a quick reply. I got a n8010. But its device name on idin mode is n8013 since i flashed n8013 rom please read by posts before this one. I have elaborated on whole situation. I couldn't manage to get the device name back to 8010 and binary counter to zero. That's what i need help with. All the roms i used were official. However this problem only happened after i used n8013 official 4.1.2
Sent from my Nexus 4 using XDA Premium HD app
I flashed my stock unrooted n8010 with the n8000 leak files using odin, I did not used the modem. All good and everything working.
Now I want to get back to stock n8010 jb. When in download mode the device apears like n8000 and odin is not able to flash the stock n8010 firmware.
I installed twrp and rooted, modified buildprop to apear like n8010 and tried to flash a custom rom for n8010, no luck, I get a message that the rom is for n8010 and to try a rom for my device.
How can I trick twrp or odin to make them flash n8010 fw/rom ?
I don't have a nandroid backup,
Edit : I managed to flash 4.0.4 with odin (N8010XXALGC_N8010OXXALG4_COA). After the flash it was stuck at samsung logo, I rebooted in recovery (power+volume up, release only power at samsung...) and wiped cache, wiped data and reset. Now the device booted with android 4.0.4 and I'm downloading a 568.29 MB update. I'll see what happends next...
The goal is to get back to stock jb, official (with triangle away I gues)
Edit: I updated to JB, but when in download mode the device is still N8000, so the problem is still not solved.
Sent from my GT-N8010 using Tapatalk
KoRoZIV said:
I flashed my stock unrooted n8010 with the n8000 leak files using odin, I did not used the modem. All good and everything working.
Now I want to get back to stock n8010 jb. When in download mode the device apears like n8000 and odin is not able to flash the stock n8010 firmware.
I installed twrp and rooted, modified buildprop to apear like n8010 and tried to flash a custom rom for n8010, no luck, I get a message that the rom is for n8010 and to try a rom for my device.
How can I trick twrp or odin to make them flash n8010 fw/rom ?
I don't have a nandroid backup,
Edit : I managed to flash 4.0.4 with odin (N8010XXALGC_N8010OXXALG4_COA). After the flash it was stuck at samsung logo, I rebooted in recovery (power+volume up, release only power at samsung...) and wiped cache, wiped data and reset. Now the device booted with android 4.0.4 and I'm downloading a 568.29 MB update. I'll see what happends next...
The goal is to get back to stock jb, official (with triangle away I gues)
Edit: I updated to JB, but when in download mode the device is still N8000, so the problem is still not solved.
Sent from my GT-N8010 using Tapatalk
Click to expand...
Click to collapse
What version of Odin are you using ?Did you try to remove micro SD and full erase you tablets internal memory card? And why not 4.1.2 you install and not 4.0.4?
Because 4.1.2 gives me error, tried 3 versions of Odin: 3.04, 3.09, and 1.85. Tried 4.1.2 from 3 different sources to avoid a bad download. I can only flash 4.0.4, android shows me n8010 but in download mode is still n8000. I have no idea why, I just can't get rid of the n8000 in download mode.
Maybe I need to flash separate files, just like I did with 4.4.2, bootloader. Ap , csc but I don't know where to get those files for 4.1.2, I only have .tar.md5 files.
I attached a ss with odin eror when trying to flash stock 4.1.2
Sent from my GT-N8010 using Tapatalk
KoRoZIV said:
Because 4.1.2 gives me error, tried 3 versions of Odin: 3.04, 3.09, and 1.85. Tried 4.1.2 from 3 different sources to avoid a bad download. I can only flash 4.0.4, android shows me n8010 but in download mode is still n8000. I have no idea why, I just can't get rid of the n8000 in download mode.
Maybe I need to flash separate files, just like I did with 4.4.2, bootloader. Ap , csc but I don't know where to get those files for 4.1.2, I only have .tar.md5 files.
I attached a ss with odin eror when trying to flash stock 4.1.2
Sent from my GT-N8010 using Tapatalk
Click to expand...
Click to collapse
Did you have success installing the bootloader of the leak kitkat rom? Cause mine failed always, the AP file is the 1 working on me only. I have downloaded this TAR_MD5_PACKAGER here( http://forum.xda-developers.com/showpost.php?p=42393470&postcount=2 ) that I'm using to repack the stock and using 7zip to extract the content of the .tar.md5 files, maybe you can try repacking it seperately using this 2 program. And try to install it using Odin( I'm using Odin 1.85). By the way you can still install custom 4.1.2 rom's right, specifically for 8010 ? Lastly why do you wanna go back to stock 4.1.2 do you have problem with the leak rom?
P.S. Did you format your internal memory as I suggested? Cause once I install back to 4.1.2 have error before and have to install twice the rom( that is according to my experience which some think its not relate to installing error).maybe you can try to format all from the system to the internal memory via CWM recovery /mount section.Then try to install again and remove the SD card too.
I had no problems with the kit Kat files, flashed at the same time bl, csc and ap (no modem). I used odin 3.09. I managed to get back to 4.1.2 by flashing stock 4.0.4 then using OTA (im surprised it worked) . Someone else flashed directly 4.1.2 with mobile odin and worked, but with odin from pc you get an error.
The problem is that in download mode appears like n8000; hopefully, when official kk for n8010 is out we'll be able to fix that.
Sent from my GT-N8010 using Tapatalk
KoRoZIV said:
I had no problems with the kit Kat files, flashed at the same time bl, csc and ap (no modem). I used odin 3.09. I managed to get back to 4.1.2 by flashing stock 4.0.4 then using OTA (im surprised it worked) . Someone else flashed directly 4.1.2 with mobile odin and worked, but with odin from pc you get an error.
The problem is that in download mode appears like n8000; hopefully, when official kk for n8010 is out we'll be able to fix that.
Sent from my GT-N8010 using Tapatalk
Click to expand...
Click to collapse
Glad you manage to resolve some of your problem.Plese ignore my post above your's then.
The problem is not solved lol. I just gave up for the moment. It's a miracle that I didn't bricked the damn thing today
I'll stay with a 4.1.2 stock n8010 fw that is using an n8000 4.4.2 bootloader. Sexy
Sent from my GT-N8010 using Tapatalk
Well from everything I've read it seems the problem is that when we flashed the kitkat leak, flashing the bootloader is what allowed us to flash n8000 over our n8010. This could be why when we flash back using odin we get the error cause the bootloader isn't being flashed too so it's trying to flash n8010 onto what it reads as n8000. It seems that there are only a few solutions. 1we need to find a n8010 bootloader file which so far seems to be impossible to find. 2you can flash an original n8010 cmw or twrp back up it will return you to 4.1.2 n8010 but the bootloader will still be n8000. If this option isn't available to you then you can try 3 download a custom rom I have the darkmans customers stock as a backup and it still works going back to simple stock n 8010 but again the bootloader stays as n8000...
Basically until we can get an n8010 bootloader we are stuck with it...
I even rooted the 4.4.2 leak and tried to flash a custom 4.4.2 made for n8010 and did not let me (based on the same leak i think, so the same bootloader) and failed, twrp sees the device as n8000 and did not allowed me to use n8010 rom.
KoRoZIV said:
I even rooted the 4.4.2 leak and tried to flash a custom 4.4.2 made for n8010 and did not let me (based on the same leak i think, so the same bootloader) and failed, twrp sees the device as n8000 and did not allowed me to use n8010 rom.
Click to expand...
Click to collapse
I think I read somewhere that twrp can have issues with flashing 4.4.2 roms it needs to be the most up to date version of twrp... I tried cm 11 before and had to change to Cwm. But I went back to twrp and now it works
I used twrp 2.7, I think it's the latest.
Edit:
I reached a binary counter of 118
I used triangle away and reset it, however I'm still stuck with the n8000 4.4.2 bootloader.
N8000 bootloader
Same issue here, stuck on N8000 bootloader on my GT-N8010. After endless research I still can't find any solution but now the thing is, the official 4.4.2 KK is availble for the GT-8010, you guys think this is the solution, because I have read that though updating to the official Rom (via Odin Mobile) because Odin desktop fails, the device would still be stuck on the annoying N8000 bootloader?
Yes, even if you flash the n8010 4.4.2 with mobile Odin you will still have the damn n8000 bootloader.
Sent from my Nexus 5 using Tapatalk
KoRoZIV said:
Yes, even if you flash the n8010 4.4.2 with mobile Odin you will still have the damn n8000 bootloader.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Any way of downgrading the Bootloader, I've heard of a nandroid backup but I didn't do that before updating, is it possible to find one on the web?
You need a nandroid from a similar device, is possible but not sure if it will solve the problem.
Sent from my Nexus 5 using Tapatalk
KoRoZIV said:
You need a nandroid from a similar device, is possible but not sure if it will solve the problem.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I thought the official Rom would fix this but visibly no. So we don't have a choice of being stuck with the damn N8000 bootloader?
At the moment there is no solution that I know of.
Sent from my Nexus 5 using Tapatalk
N8010 on N8000 bootloader
Hi guys, isn't there a solution about this yet? I have the exact same problem with the N8000 bootloader, my device is a N8010 16GB from mexico and flashed the leaked N8000 kk stock rom. I will still look for a solution. TKS to all of you.
Mean time solution
Hi Guys, I found a way to flash te new N8010XXUDNE4 on the stuck n8000 bootlader, the bootloader problem remains, but it is possible to flash the n8010 stock rom via mobile odin, I did it and it's fully working, But I flashed a N8010XXUDNE4 customized without sboot.bin so it can be flashed via PC odin too, I'm still not allowed to post links here cause I'm new in forums so if you want the link to that rom let me know how to provide it to you.
Possible solution?
Have a look at my thread, does that look a viable approach?
http://forum.xda-developers.com/galaxy-note-10-1/help/recovering-n8010-leaked-locked-n8000-t2802516
ambmar78 said:
Hi Guys, I found a way to flash te new N8010XXUDNE4 on the stuck n8000 bootlader, the bootloader problem remains, but it is possible to flash the n8010 stock rom via mobile odin, I did it and it's fully working, But I flashed a N8010XXUDNE4 customized without sboot.bin so it can be flashed via PC odin too, I'm still not allowed to post links here cause I'm new in forums so if you want the link to that rom let me know how to provide it to you.
Click to expand...
Click to collapse
hello all,im new here.searched but didn't find a similar post.
my galaxy tab 2 10.1 is currently running 4.1.2 JB. it says your device is out of date. but, i can't update it because its rooted and cwm recovery is installed. whenever i click on check for updates it says your device has been modified,updates are not available. i tried through kies too,it also says that updates aren't supported.what should i do?
Yeah, you can't download official OTA updates with a custom recovery. If you want updates from Samsung you need to relock the bootloader and go back to stock recovery.