Hello, this is my first post to XDA. I've read for a long time but never posted.
Ok, so I have a U.S galaxy tab 10.1 (From best buy- locked bootloader) Gt-P7510. My problem is, I have rooted my tab and installed clockwork I flashed a Oc Non-Touchwiz rom, then tried to do the ota update...it failed at 13%...Fine. But now when i try to install roms with clockwork i get "asert failed: getprop ("ro.bootloader") == "P7100BUKB7" Intallation aborted." What went wrong? and if i try to odin back to stock with the correct P7510 image will it brick? im very scared
Did you make a nandroid backup wenn you had CWM installed and the Tab was working fine? If yes, just restore the backup from the recovery.
If not, flash the original rom with Odin, it will restore the bootloaders.
Thanks so much, I was worried that if I flashed in Odin the mismatched bootloaders would cause it to brick. And I might have made the back-up but I'm not sure, so other than human error, if I have all the right files there should be no worry?
Rileyrealz said:
Thanks so much, I was worried that if I flashed in Odin the mismatched bootloaders would cause it to brick. And I might have made the back-up but I'm not sure, so other than human error, if I have all the right files there should be no worry?
Click to expand...
Click to collapse
You should always rememver to make a nandroid before flashing anything to any of your devices bro. Odin will save your tab when needed. Just make sure to put the files in the rights spots and you'll be good to go bro.
Again,thanks I did make the back-up .....BUT when I go to restore it i get Md5 mismatch! then the restore aborts...i think that failed update was more damaging than i thought
Rileyrealz said:
Again,thanks I did make the back-up .....BUT when I go to restore it i get Md5 mismatch! then the restore aborts...i think that failed update was more damaging than i thought
Click to expand...
Click to collapse
As I stated #2...flash THE ORIGINAL ROM in Odin. You will be ok then
Rileyrealz said:
Hello, this is my first post to XDA. I've read for a long time but never posted.
Ok, so I have a U.S galaxy tab 10.1 (From best buy- locked bootloader) Gt-P7510. My problem is, I have rooted my tab and installed clockwork I flashed a Oc Non-Touchwiz rom, then tried to do the ota update...it failed at 13%...Fine. But now when i try to install roms with clockwork i get "asert failed: getprop ("ro.bootloader") == "P7100BUKB7" Intallation aborted." What went wrong? and if i try to odin back to stock with the correct P7510 image will it brick? im very scared
Click to expand...
Click to collapse
I had this problem too....you're flashing a ROM not made for your device. "P7100BUKB7". your's is a p7510
Related
I have a U.S Tab 10.1 and I was wondering if anyone knows of or could upload the Retail stock zip. I got the tab a rooted it when it first came out the process said i needed to flash the "hc-3.1_ota-full_sam_tab_10.1.zip" to stop all the FC so I did. I went along using the tab and installed the 11.5 Mb (which was really for the I-O tab).
Over time everyone got their Touchwiz update and i did not. After doing some research I found out that the OTA zip that I flashed while rooting was really for the I-O tab. I know I could get back to stock and update by using Odin but I REALLY HATE ODIN (too many heartaches from bricked galaxy S) I dont even want to risk it with this tab WHATSOEVER! So if any one could help me out it would really be great . I don't care about loosing root. Thanks.
P.s the night I rooted I did make a Nandroid back up but when trying to restore I get MD5 Mismatch! so I'm also worried that the I-O update changed my Bootloader or something?
If you rename your nandroid backup folder you will get MD5 mismatch.
Here's the link to CWM backup of stock US wifi retail version :
http://db.tt/Fdx2ALuh
Sent from my GT-P7510
thank you so much, its downloading now ill report to let you know if it works. Do i put it in the back up folder created by clockwork or should i make a new one?
Rileyrealz said:
thank you so much, its downloading now ill report to let you know if it works. Do i put it in the back up folder created by clockwork or should i make a new one?
Click to expand...
Click to collapse
Put it in clockwork/backup itself.
Sent from my GT-P7510
i have the hc-3.1_ota-full_sam_tab_10.1.zip installed already and i tryed restoring to the back up that u posted here but it just said that the md5 mistmatch. plz help
it says MD5 mismatch when trying to restore
juangutierrez29 said:
i have the hc-3.1_ota-full_sam_tab_10.1.zip installed already and i tryed restoring to the back up that u posted here but it just said that the md5 mistmatch. plz help
Click to expand...
Click to collapse
After you extract the folder to /clockwork/backup make sure the folder name is "2011-09-13.15.19.39"
Hello,
I want to go back to gingerbread from resurrection v7.4 ics rom.
I made a backup before i flashed the rom, via CWM, do i just wipe everything and flash the backup? or any extra steps?
also now i cannot load files into my phone, i turned on usb debugging and can access files but when i try to copy a file into the phone it says "can not copy items" "the device either stopped working or has been disconnected"
Help please, many thanks.
To restore you dont have to wipe anything.Use CWM app or boot to recovery and restore.After that Id wipe cache pratition and dalvik cache just in case.Factory reset may be a good idea seeing as your coming back from ICS but thats your choice.After that see how mass storage is.Ive read a few threads about people having trouble getting back from ICS.Hope it all goes well.
cooza said:
To restore you dont have to wipe anything.Use CWM app or boot to recovery and restore.After that Id wipe cache pratition and dalvik cache just in case.Factory reset may be a good idea seeing as your coming back from ICS but thats your choice.After that see how mass storage is.Ive read a few threads about people having trouble getting back from ICS.Hope it all goes well.
Click to expand...
Click to collapse
Thanks Cooza,
but i think i made a stupid mistake, im getting an MD5 mismatch when i try to restore, im searching for the reason, im not sure its true but i think its because i renamed the backup folder from its original date/time to a name i gave it. does that cause MD5 mismatch?
the rest of my backups are with ICS not Gingerbread . is there another way to go back to my version ( i dont mind reformatting the whole phone if i have to)
my former gingerbread Version was
Baseband: XXKI4
Kernel: JPKJ2
android 2.3.5
Flash stock rom then CF root with the exact same CWM kernel you used to backup .
jje
flash via odin the stock rom and custom kernel if you want to have root
otherwise just flash the stock rom, id suggest the original android dev subforum
Ive read that you shouldnt change the name of a nandroid backup but I dont know if that could be the problem.You could Flash the old bootloader and try the nandroid but I dought now that it would work so the best is to flash a custom ROM as the other posters have been advising although like I said ealier Ive read alot of threads with people having this problem of coming back to Gingerbread from ICS.Thats the risk of flashing a test ROM as no ICS ROM is full complete yet.Dont worry mate,theres still hope
ab.riyami said:
Thanks Cooza,
but i think i made a stupid mistake, im getting an MD5 mismatch when i try to restore, im searching for the reason, im not sure its true but i think its because i renamed the backup folder from its original date/time to a name i gave it. does that cause MD5 mismatch?
Click to expand...
Click to collapse
Renaming it will cause a mismatch, if you can't recall the original name, don't worry. You can use Advanced Restore from recovery to restore the b/u.
Thanks guys,
Ill be honest, the only time i flashed my phone was when Cf-rooting then i downloaded the .zip files for resurrection ics and it was easy cuz done via CWM.
so ive never flashed a rom on my fone using odin, i fell intimidated i bit, dont know the difference in flashing a rom and a kernel (i know what they are but donno how to flash individually)
anyways i went to sammobile.com, downloading the stock firmware now.
by searching online i now think the zip file from sammobile will have some files and i gotta load the files provided in their proper places (dont know if .pit file will be provided with it, nor if i need to load .pit)
please tell me if what ive mentioned above is correct, sorry for the noob questions but i just dont wanna screw up.
after all of that ill then back up properly and try some gingerbread roms and kernels. but i just wanna get it back to the original first to be safe, dont know if i can just flash gingerbread roms and kernels with my ics phone.
ab.riyami said:
also now i cannot load files into my phone, i turned on usb debugging and can access files but when i try to copy a file into the phone it says "can not copy items" "the device either stopped working or has been disconnected"
Click to expand...
Click to collapse
adb push, or Droid Explorer, or QTAdb, et al, will allow you to get those files to your phone.
mudferret said:
Renaming it will cause a mismatch, if you can't recall the original name, don't worry. You can use Advanced Restore from recovery to restore the b/u.
Click to expand...
Click to collapse
Thanks mate,
Tried Advance restore option, it said "no file found"
I went back myself from ics to a stock ROM. It's really easy
What I did first was fully wipe cache, dalvik etc in cwm. Next up: put your phone in download mode (volume down, home and power)
Start odin and add the tar file or tar.md5 file with the PDA button. That should be the only file in the zip, if there are more: look at the file names, they'll say where to add them in odin.
Next up, connect your phone to your computers usb port (odin should tell you that it has added your phone) and hit the start button.
After the flashing is done your phone will reboot and it should be back to normal. Now you can flash a kernel to get root again if you like
Good luck, it will work out just fine
Sent from my GT-I9100 using XDA App
Excellent, thanks guys it worked
Flashed stock via Odin, not rooted now but will do when i flash CF-root again
waiting for sam to finally release ics!
ab.riyami said:
Excellent, thanks guys it worked
Flashed stock via Odin, not rooted now but will do when i flash CF-root again
waiting for sam to finally release ics!
Click to expand...
Click to collapse
Well done.Better to wait for the official release of ICS
hi, i recently broke my old gs2's screen but as i had an insurance i got a brand new phone. i was wondering wheter it would be possible to restore a CWM-backup of my old ROM to the new phone, which would safe me a lot of time, as opposed to restoring everything manually. I tried just putting the backup in the correct folder and tried to restore it from CWM recovery, but i've encountered an MD5-mismatch! error at the beginning of the proces.. so i was wondering of there is any way to work around this problem..
wootyv said:
hi, i recently broke my old gs2's screen but as i had an insurance and i got a brand new phone. i was wondering wheter it would be possible to restore a CWM-backup of my old ROM to the new phone, which would safe me a lot of time, as opposed to restoring everything manually. I tried just putting the backup in the correct folder and tried to restore it from CWM recovery, but i've encountered an MD5-mismatch! error at the beginning of the proces.. so i was wondering of there is any way to work around this problem..
Click to expand...
Click to collapse
make sure you are running the same kernel you used, when you created those backups on your new phone.
The restore process should work well after that.
For example, if you were running Siyah 3.2 when you created those backups then flash Siyah 3.2 on your new phone or at worst Siyah 3.x.
Swyped from my Samsung Galaxy SII
Jokesy said:
make sure you are running the same kernel you used, when you created those backups on your new phone.
The restore process should work well after that.
For example, if you were running Siyah 3.2 when you created those backups then flash Siyah 3.2 on your new phone or at worst Siyah 3.x.
Swyped from my Samsung Galaxy SII
Click to expand...
Click to collapse
i was at siyah kernel, but actually i dont really remember what version.. now i'm back at latest siyah kernel, but apparantly i wasn't on last version when i did the backup.. i'll try to install older versions of siyah and try again, thanks
actually, that doesnt really make sense to me.. the purpose of a nandroid is to restore your full rom when u messed up on something new.. so u won't be always on the same kernel, still it always worked for me.. any reason you would need to have the same kernel when it is another phone?
wootyv said:
actually, that doesnt really make sense to me.. the purpose of a nandroid is to restore your full rom when u messed up on something new.. so u won't be always on the same kernel, still it always worked for me.. any reason you would need to have the same kernel when it is another phone?
Click to expand...
Click to collapse
I suspect its to stop retards trying to restore incorrect device backup and also because of some kernels restoring/backup differently to others so its all to stop you bricking your device.
Just install correct kernel and you shouldnt have a prob. There is also a way to bypass the check afaik, but I wouldnt advise it.
ok sorry, sound quite logic indeed.. maybe i was a bit of a retard there (although i'd consider people who really restore backup from a totally different kind of phone far more retarded )
no luck on same kernel neither, tried even adding same rom but didn't work
ok, now i'm in big trouble, tried to restore my stock backup i made, error in restoring system, stuck at siyah boot logo and unable to enter recovery, what now?
was able to get into download mode, will try to flash stock rom through odin..
wootyv said:
ok, now i'm in big trouble, tried to restore my stock backup i made, error in restoring system, stuck at siyah boot logo and unable to enter recovery, what now?
Click to expand...
Click to collapse
Flash your firmware back via Odin.
Ps:
1.Something messy must have gone wrong during your restore.
2. I always makes a full set up device in my phone, then restore it on my friends' phones without issues.
Swyped from my Samsung Galaxy SII
well, i guess that since now also the stock restore has gone wrong it has something to do with my recovery.. so if i get my phone working again i'll try to start all over again..
wootyv said:
well, i guess that since now also the stock restore has gone wrong it has something to do with my recovery.. so if i get my phone working again i'll try to start all over again..
Click to expand...
Click to collapse
Are you sure you really restored the backup using the same kernel version?
Swyped from my Samsung Galaxy SII
pretty sure, is i used the zip i found in a backup of the memory of my old phone.. but got it working again, that's already a huge relief.. next try will be for tomorrow, thanks for your help anyway
oh yeah, as i have to start all over again, maybe you have an idea on how to root it without triggering custom counter? i somehow succeeded one time but since then only had problems... mainly the reason of all the error is already there..
wootyv said:
oh yeah, as i have to start all over again, maybe you have an idea on how to root it without triggering custom counter? i somehow succeeded one time but since then only had problems... mainly the reason of all the error is already there..
Click to expand...
Click to collapse
1. Root it with this method
2. Flash Siyah kernel using the Temporary recovery after successful rooting
this will not increase counter.
However, if you have in a way increased your counter, just use Triangle away App by chainfire to reset it. Root is needed for the App to function
thanks alot
unfortunatly, that's the method i used, so or something went wrong the first time, or the problem wasn't that part, leaving me in doubt where it might have taken place
and thanks for triangle away link, i knew it existed but i always thought it just removed the triangle but didn't really reset the counter.. now by clicking again on your link i read the description so now i know that there is another way then buying a jig, so maybe i'll just flash using odin, leaving the counter on 1, but having a way to reset it when i should ever need to..
Code:
su
mount -o remount rw /sdcard
cd /sdcard/clockworkmod/backup/xxxx-xx-xx.yy.yy.yy
rm nandroid.md5
md5sum *img > nandroid.md5
Also found that, and it worked, sent from my restored Galaxy sii, thanks guys, problem solved
wootyv said:
Also found that, and it worked, sent from my restored Galaxy sii, thanks guys, problem solved
Click to expand...
Click to collapse
Glad to hear that.
Can you add SOLVED to the thread title? That will be great
Swyped from my Samsung Galaxy SII
Jokesy said:
make sure you are running the same kernel you used, when you created those backups on your new phone.
The restore process should work well after that.
For example, if you were running Siyah 3.2 when you created those backups then flash Siyah 3.2 on your new phone or at worst Siyah 3.x.
Swyped from my Samsung Galaxy SII
Click to expand...
Click to collapse
Hey thanks you helped me. I just have one question. I'm into Android rooting/flashing/etc for almost two years now and I wondered, how do you know this stuff? I mean I read a lot about android but I would never have figured the kernel would be the problem.
I was trying to upgrade from 4.0.3 to 4.1.2 and I accidently flashed wrong CWM (v5) instead v6 and it got stuck at Samsung logo, reflashed 4.0.3 and now it gets stuck at the S logo (after start up sound).
Anyone know where I can get the multi-file old-style firmware so I can get this working again?
Thanks in advance!
Use Odin.... If You Already Usingtgen tell me Which file you tried to flash...
Sent from my iPhone using Tapatalk
otester said:
I was trying to upgrade from 4.0.3 to 4.1.2 and I accidently flashed wrong CWM (v5) instead v6 and it got stuck at Samsung logo, reflashed 4.0.3 and now it gets stuck at the S logo (after start up sound).
Anyone know where I can get the multi-file old-style firmware so I can get this working again?
Thanks in advance!
Click to expand...
Click to collapse
Here you got ICS ROMs & LS8.
That's for I9100, make sure you're packing the right model as well.
I managed to get it working again by VOLUP+Power+Menu and going into CWM and restoring from a backup.
But it is rather concerning that if I hadn't of had a backup I would be screwed right now, I use Odin and I was using the thread you posted above, however even after flashing those and even wiping user data, it still boot looped.
otester said:
I managed to get it working again by VOLUP+Power+Menu and going into CWM and restoring from a backup.
But it is rather concerning that if I hadn't of had a backup I would be screwed right now, I use Odin and I was using the thread you posted above, however even after flashing those and even wiping user data, it still boot looped.
Click to expand...
Click to collapse
hummm.........
If you can flash a back up you should be able to flash anything else. I mean, there's nothing wrong with your device.
Are you sure kies is all closed before flashing via Odin?
Try Mobile Odin to flash a stock ROM.
otester said:
I managed to get it working again by VOLUP+Power+Menu and going into CWM and restoring from a backup.
But it is rather concerning that if I hadn't of had a backup I would be screwed right now, I use Odin and I was using the thread you posted above, however even after flashing those and even wiping user data, it still boot looped.
Click to expand...
Click to collapse
Did you try follow the guide here: http://forum.xda-developers.com/showthread.php?t=1108499
It outlines what you did, only it suggests flashing a stock ROM through Odin instead of restoring a backup. Data stored on the internal memory will be lost during process, but it seems you have no way of retrieving it anyway! Give it a go with the stock ROM's link that gastonw linked you.
otester said:
I managed to get it working again by VOLUP+Power+Menu and going into CWM and restoring from a backup.
But it is rather concerning that if I hadn't of had a backup I would be screwed right now, I use Odin and I was using the thread you posted above, however even after flashing those and even wiping user data, it still boot looped.
Click to expand...
Click to collapse
Dude, your device was not "bricked" and it was of no concern. The problem was simply that you flashed a incompatible kernel.
To solve it all you needed to do was flash compatible kernel in download mode using ODIN and you would have then had correct cwm, root and rom would have booted no problem.
hi all,
im new to the forum but read up on here lots of times. i reluctantly have to now beg for help as im at my wits end here. i rooted my s3 phone a month ago after it kept crashing with the stock samsung fw on it. So i rooted and used odin 3 to install cm-10.0.0-d2att.zip. this was great for two month then all of a sudden, no reason the phone kept restarting and not getting past the samsung logo screen again, yes the phone has issues so i then wanted to install the stock firmwre and use triangle app to zero the counter. stupidity on my part i foolishly loaded the wrong file and loaded cm-10.1-20130504-nightly-i9100.zip . great firmware but not what i wanted.
so i installed the custom one which kept aborting loading from external sd saying something about unable to verify signature. i have also tried to load the origional custom firmware cm-10.0.0-d2att.zip but nothing will load now. and no firmware will load and again it wont get past the logo screen. My only saving grace is that i can still get into downloading mode and the boot mode with the up key.
Please please help if you can
Sincerely
Fei
Try flashing a stock Samsung rom via odin from your pc, if that doesn't work then probably a new motherboard is required.
yeah i did try that . im getting E:failed to verify whole-file signature
E:signature verification failed
im using android system recovery <3e>
i was using something ele prior to this, not sure what
fatfei said:
yeah i did try that . im getting E:failed to verify whole-file signature
E:signature verification failed
im using android system recovery
i was using something ele prior to this, not sure what
Click to expand...
Click to collapse
That's the stock recovery. I don't believe that will flash firmware, which is why you get the error, before you probably had CWM.
As said before, go to download mode and flash a stock rom from sammobile through odin, if it doesn't work. I think it may be bricked (someone more experienced may disagree though)
Sent from my GT-I9300 using xda premium
squ89r97 said:
That's the stock recovery. I don't believe that will flash firmware, which is why you get the error, before you probably had CWM.
As said before, go to download mode and flash a stock rom from sammobile through odin, if it doesn't work. I think it may be bricked (someone more experienced may disagree though)
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
thanks mate. ill try now