hey guys , i have decided to flash a rom for my tab 10.1 p5100 for the 1st time ever with original ics rom 4.0.4 to a stock jb based rom called "ROM 4.1.2 (P51XX MOD FEXUS Tab2 V2.0.3)" so decided to flash JB Bootloader 1st from cm10.2 page at first then flashing the new rom after formatting , i installed the p5100 version and it didnt load then i looked at the tab setting from the mod installation and it stated me as p5110 and flashing its rom worked fine but with no GSM stuff , then i formatted it again and trying to restore my ics recovery and it said md5 mismatch , any known solutions for this ? , plz help
md5 missmatch problem is due to the old cwm plz flash latest cwm and than try
if is problem not fix
than open your backup folder and than edit nandriod.md5 file in notepad ++ or notepad in the file delete all the words and save it empty and then try to restore cwm skip that file and start restoring system
Related
Problem Solved
i already deleted my rom, im using twrp 2.6.3.5 for P3100 , and im using a p3113, big mistake on my end, how can i get a p3113 recovery to flash on this ? surely there must be something i have to write in the updater-script to get it to flash right ?
Update: booted into a p3100 rom , im gonna try to find a way to flash a recovery...
Update: downloaded rom manager, and selected p3113 from the model option list...
Update: Flashing CWM from a p3100 rom worked perfect
Can happen Download P3110 Recovery and flash it from your (wrong) P3100 Recovery Nothing bad
You only need to reboot your recovery after that
(Sometimes i am flashing a P3100 on my P3110 to be able to flash a P3100 Rom without Problems for testing or test my new compiled recoverys )
I recently rooted my galaxy tab 2 P3110 with Odin and CWM recovery 6011 and i seemed to have wiped the stock android os as i cannot boot into it anymote - the Tablet automically boots into CWM all the time
Then when i try to install Slimrom or CM installer to flash and install a new OS but i getting an error 7 - unverified file so i cannot put any Os back on the device
Can anyone help?
Sounds like you flashed the wrong recovery, possible that you installed the p3100 recovery.
Try reflashing the recovery.
miksol said:
I recently rooted my galaxy tab 2 P3110 with Odin and CWM recovery 6011 and i seemed to have wiped the stock android os as i cannot boot into it anymote - the Tablet automically boots into CWM all the time
Then when i try to install Slimrom or CM installer to flash and install a new OS but i getting an error 7 - unverified file so i cannot put any Os back on the device
Can anyone help?
Click to expand...
Click to collapse
Flashing KK ROMs on outdated recovery will get you a status 7 error. Grab the latest (I'd go with TWRP as CWM support will be ending soon) version from here...http://forum.xda-developers.com/showthread.php?t=2548257 update to the latest one you like (CWM is 6.0.5.0) Load up a ROM and give it a go. I put all my ROMs on an external card to be safe. Maybe do that and then just install from such.
p,s. CM installer never works, I dont think our tabs are compatible with it. At least I've never got it to work.But, you dont need it anyways.
I really need some help with my Note 10.1 Wi-Fi (N8010). I'll try to give as much detail here as I can in the hope that some of you experts will be able to help me out!
I was previously running this rom http://forum.xda-developers.com/showthread.php?t=2119547 based on N8000XXCML2 (Android 4.1.2) and I saw that Kitkat was available for my device so I thought I check it out. Now this is where the problems started...
I saw this page http://forum.xda-developers.com/showthread.php?t=2792979 and downloaded and installed the rom from sammobile (N8010XXUDNE4, stock 4.4.2), then rooted with the link on that page.
When I booted I tried to install superSU from the play store and when I ran it, i tried to install the binaries as usual choosing "normal" mode and it told me that KNOX was detected and would I like to disable it? NB: This was the first I'd ever heard of KNOX. Choosing yes didn't work so I tried reflashing the rom again and rooting again with the CF auto root and tada... it worked.
So now I was successfully running rooted, stock 4.4.2 on my N8010.
After a few days however, my keyboard disappeared! When ever I tried to go to a text input field the keyboard just wouldn't appear. I tried installing another keyboard and nothing. So I came back to xda and found Gnabo Rom V6 (http://forum.xda-developers.com/showthread.php?t=2762418).
I followed the instructions and was up and running again. Then after reinstalling all my apps from the play store I tried to install the Xposed framework and when I tried to reboot it was just stuck on the Samsung logo. I tried rebooting again and just leaving it but after about 8 hours it was still stuck on the logo.
Since that, I've managed to flash a stock 4.0.4 firmware with an N8010 PIT file and the device can boot but as soon as I try to flash another rom it just hangs on boot.
If i put the device into download mode (with the bootable 4.0.4 firmware) i see the following.
ODON MODE (red text)
PRODUCT NAME: GT-N8010
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
RP SWREV: A2 (grey text)
I've tried restoring Nandroid backups of my orignal rom and the Gnabo V6 rom but nothing works.
Now if I try to flash N8010XXUCMG1 (stock 4.1.2) from Sammobile Odin fails and on the download mode screen on my device an extra line in red appears saying "SW REV. Invalid magic string". If I reboot into download mode again that line is gone.
Does the RP SWREV line mean I have KNOX on my device?
I just want to get back to my original state (custom 4.1.2) as the 4.0.4 stock rom doesn't seem to see my external SD card (64gb Sandisk) so any suggestions would be much appreciated!
I think it's because you have a kit Kat boot loader and it won't let you downgrade to jelly bean. You could flash kit Kat through Odin and see if it works. And if your sd isn't formatted as fat32 try changing that. But I highly suggest that you wait till someone else confirms everything.
chrismin13 said:
I think it's because you have a kit Kat boot loader and it won't let you downgrade to jelly bean. You could flash kit Kat through Odin and see if it works. And if your sd isn't formatted as fat32 try changing that. But I highly suggest that you wait till someone else confirms everything.
Click to expand...
Click to collapse
I've already tried re-flashing KitKat (N8010XXUDNE4, stock 4.4.2) but its just the same as flashing any other rom; shows the samsung logo and plays the little jingle but then just stays there with the logo fading in and out.
If anyone's interested I've managed to fix it myself in the end. Turns out it was a corrupt efs partition and the Nandroid restore was ignoring the efs.tar.gz file. I never thought the efs partition was important for my tab because its wifi only.
Hi, I have the same problem. Can you describe how fixed it?
polzavotel said:
Hi, I have the same problem. Can you describe how fixed it?
Click to expand...
Click to collapse
Hi,
I tried so many things and I'm no expert so i can't be sure exactly what fixed it but here's what I think did the trick...
I first managed to get into the terminal from recovery mode using Aroma Filemanager http://forum.xda-developers.com/showthread.php?t=1646108
Then I found these 2 commands to run (sorry I don't remember which thread they were from)
mke2fs / dev/block/mmcblk0p3
mount-w-t ext4 / dev/block/mmcblk0p3 / efs
Then after that I was able to restore my old EFS backup. It was in .tar.gz format from an old Nandroid backup and not .img so I had to mandually copy the files over then change the permisions. This thread was useful for that http://forum.xda-developers.com/showthread.php?t=1089039
And this thread for how to remove the "Factory Mode"
http://forum.xda-developers.com/showthread.php?t=1089039
Hope that helps you!
Hi guys Im having the problem stated in the title even though i deleted all the asserts lines in the updater script. I recently just flash a stock rom 4.4.2 http://www.droidviews.com/install-android-4-4-2-kitkat-firmware-galaxy-note-10-1-gt-n8020/. Originally its was running 4.1.2 singapore country. After flashing 4.4.2, i find... its really bad and wanted to flash back to my original stock rom. But the problem is got status 7 error when i flash ANY rom.
My Device : GT-N8020 Singapore
Just tried the kies method but failed. It asked for a recovery code
Cant get it boot too, stuck at Samsung device model logo [ Probably is due to an accident i made by touching "Clean to install a New ROM' wipe option]
Edit : I do not find any 'getprop' in all the assert lines which i deleted
Solved
I downloaded http://www.sammobile.com/firmwares/download/32196/N8020XXUDNE4_N8020SEBDNF1_SEB.zip/ and suceed flash it via odin. I shall bare with 4.4.2 for a moment and sleep
I had some issues with ROMs, so managed to revert back to stock. Now using TWRP, but only after trying with CWM, all ROMS get error 7, "can't install this package on top of incompatible data", and CWM said something about it being the wrong firmware for a "note4" or something.
I don't know what to do, can you flash roms through ODIN? Please note this is an N8010
Thanks for your help
NOTE 4 suggests you are flashing a wrong file for another model .
TWRP CWM and Philz Recovery and High On Android recovery work on N8010 tested all within the last month .
can you flash roms through ODIN? >> Custom roms no only stock tar files .
I've tried the CM 11, the CM 12 and Android revolution ROM, all supposedly work with the N8010. Revolution Rom was the first, installed but made a boot loop after I applied the N8010 compatibility flash. After that the file structure seemed to double - there was a new folder with all the other android directory inside it. I deleted the doubleup, but now I don't know what to do, it's back on stock.
JJEgan said:
NOTE 4 suggests you are flashing a wrong file for another model .
TWRP CWM and Philz Recovery and High On Android recovery work on N8010 tested all within the last month .
can you flash roms through ODIN? >> Custom roms no only stock tar files .
Click to expand...
Click to collapse