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
I have the SCH-I535 and I took the OTA and I'm running 4.3 with a locked bootloader. I've downloaded safestrap and have successfully got a recovery and even flashed the Alliance Rom and used it for over a month. I decided to switch over and try the M.O.A.R rom and everything seemed to go smoothly. I flashed the appropriate modem that the download instructions told me to use and then flashed the rom, all after doing a clean wipe first of course. But after I rebooted I now have the dreaded System software not authorized message. Has anybody figured out how to fix this without going back to stock unrooted?
Which modem did you flash? Because there's a two fold problem that you're likely facing:
a) you flashed the Sprint modem that is mentioned in the MOAR OP, cuz the rom is a port from Sprint. If you did this, you may have semi-hard bricked your S3.
b) you flashed the Verizon modem, which you aren't supposed to do with a locked bootloader.
Being on the 4.3 OTA, literally the only things you should be concerned with flashing are TouchWiz roms and also kernel modules which enable WiFi.
You're going to need Odin flash VRUCML1 if you cannot access the rom or Safestrap.
Sent from my SCH-I535 using Tapatalk 4
Hi,
I need reflash the firmware on my phone, but I can not flash the new firmware. I get a bug The bundle does not match the connected device. Any installation of custom rom will end with bootloop. The problem occurred after deodex stock rom. How can I get my phone back on? Thank you very much.
Problem solved
Hey, how did you solve the problem? I am facing same. I have a z5 E6603 I am sure it is 03, I flashed a lot of roms and today tried to flash original firmware via flashtool. It gave same error. I realized that it recognized my device as E6653. I thought that was a problem with build.prop, manually edited and tried to flash again, did not work. I wiped system partition and retried, did not work. I end up with carbon rom. How can I flash the ftf for 6603? Help me please. BTW I am using linux (to be more specific arch linux) and installed flashtool via AUR. Can this be a problem? Thanks
First I formatted a partition and then I installed AOSP ROM, for example Resurrection Remix. Than I ran mobile without setting an account, etc. Then I flashed the stock firmware.
kevin.kvik said:
First I formatted a partition and then I installed AOSP ROM, for example Resurrection Remix. Than I ran mobile without setting an account, etc. Then I flashed the stock firmware.
Click to expand...
Click to collapse
Thank you, I will download an AOSP ROM and try again tonight. I hope I can flash stock .54 again.