Related
I've been asking for help after screwing up my Tab while trying to restore my Roto Backup with Odin, and the thread has been completely quiet.
I just wanted to ask an easier question, and see if that might tell me everything I need to know: Has anyone other than rotohammer ever actually successfully restored their Roto Backup? Second question, has anyone, including rotohammer, ever restored their Roto Backup with Odin?
The reason you screwed with your roto backup is the base in which you flashed the backup over and how you flashed the backup.
Here are the Reasons for Rotobackup failures:
1- Flashing a FROYO backup over a GINGERBREAD system (Both systems have DIFFERENT BOOTLOADERS) this causes lines and corrupted system image etc.
2. Not Flashing the correct PIT file or flashing one at all over a custom ROM you are using e.g Flashing your ROTO without PIT over overcome ROM formatted in EXT4 can result in a non boot as the kernel doesn't support EXT4.
3. Flashing bootloaders (boot.bin and SBL.bin) from the Roto backup. My advice: DO NOT DO THAT IF YOU DON'T WANT TO END WITH A HARD brick. For some reasons bootloaders from rotobackup arent really Safe.
My advice is to flash a Standard stock firmware (Froyo if you backup is froyo and GB if your backup is GB) then flash your Roto backup over it WITHOUT pit and WITHOUT bootloaders.
DarkPal said:
The reason you screwed with your roto backup is the base in which you flashed the backup over and how you flashed the backup.
Here are the Reasons for Rotobackup failures:
1- Flashing a FROYO backup over a GINGERBREAD system (Both systems have DIFFERENT BOOTLOADERS) this causes lines and corrupted system image etc.
2. Not Flashing the correct PIT file or flashing one at all over a custom ROM you are using e.g Flashing your ROTO without PIT over overcome ROM formatted in EXT4 can result in a non boot as the kernel doesn't support EXT4.
3. Flashing bootloaders (boot.bin and SBL.bin) from the Roto backup. My advice: DO NOT DO THAT IF YOU DON'T WANT TO END WITH A HARD brick. For some reasons bootloaders from rotobackup arent really Safe.
My advice is to flash a Standard stock firmware (Froyo if you backup is froyo and GB if your backup is GB) then flash your Roto backup over it WITHOUT pit and WITHOUT bootloaders.
Click to expand...
Click to collapse
Thanks for the help. So you've managed to get your Roto Backup to work before?
So if I can't flash a bootloader from Roto backup, how do you recommend I flash back to the Froyo bootloader?
Also, any recommendations on a Froyo standard stock firmware image I can flash safely on an AT&T tab?
Well any stock package (froyo or GB) will have its bootloaders included so don't worry about them. As for a recommendation for a stock package yes actually I have 2 for froyo. JK5 and JJ4 packages should be good to go if you want to downgrade your tab to froyo (if you for some reason wanted to do that).
DarkPal said:
The reason you screwed with your roto backup is the base in which you flashed the backup over and how you flashed the backup.
Here are the Reasons for Rotobackup failures:
1- Flashing a FROYO backup over a GINGERBREAD system (Both systems have DIFFERENT BOOTLOADERS) this causes lines and corrupted system image etc.
2. Not Flashing the correct PIT file or flashing one at all over a custom ROM you are using e.g Flashing your ROTO without PIT over overcome ROM formatted in EXT4 can result in a non boot as the kernel doesn't support EXT4.
3. Flashing bootloaders (boot.bin and SBL.bin) from the Roto backup. My advice: DO NOT DO THAT IF YOU DON'T WANT TO END WITH A HARD brick. For some reasons bootloaders from rotobackup arent really Safe.
My advice is to flash a Standard stock firmware (Froyo if you backup is froyo and GB if your backup is GB) then flash your Roto backup over it WITHOUT pit and WITHOUT bootloaders.
Click to expand...
Click to collapse
and
I'll explain
=-=-=-=-=-=
I got 2 Tab's same STOCK ROM's...
on one of them installed overcome...
then i took roto backup the other and restored with odin on the overcome..
wait wait... i restored a stock GB from samfirm first and then used my Froyo backup...
kinda the same like you explained not to do... and guess what?!
tab died needed jtag... after jtag they gave me back the tab with stock froyo from samfirm...
now i'll explain
=-=-=-=-=-=-==
i restored again my backup with odin and original rom is now installed perfectly.. i did had an error when it reached boot.bin though..
but i restarted the tab and it's up and running...
too bad i didn't saw your message before...
i just have a question..
so lets say i'm now in overcome.. want to install 2.2
you say that i'll should use lets say stock rom from samfirm
with odin... with p1 pit file
check repartition, areboot, freset and start...
when done restore using my backup created using RB
with odin... areboot, freset and start (pda with the tar file and no pit)
but in the 'tar' file not to include boot.bin and SBL.bin files? just those files?
sorry for bad english...
I would think that Roto Backup is only good for restoring within the same base rom. For example, if the backup is done under rom DXJDE, i would flash stock DXJPE rom with pit file and all, then follow by the backup without the pit file.
Secondly, if you want to revert to stock status, i think Roto Backup is only suitable for Froyo base. This is because in order to create a backup, your tab have to be rooted and with busy box. Froyo can easily go back to unroot status by using SuperOneClick.
Not so for Gingerbread. The only way to get unroot status is to flash stock.
Once you restore from your backup, your tab is rooted.
nevermind it's working...
cymagnus said:
I would think that Roto Backup is only good for restoring within the same base rom. For example, if the backup is done under rom DXJDE, i would flash stock DXJPE rom with pit file and all, then follow by the backup without the pit file.
Secondly, if you want to revert to stock status, i think Roto Backup is only suitable for Froyo base. This is because in order to create a backup, your tab have to be rooted and with busy box. Froyo can easily go back to unroot status by using SuperOneClick.
Not so for Gingerbread. The only way to get unroot status is to flash stock.
Once you restore from your backup, your tab is rooted.
Click to expand...
Click to collapse
So there's probably no way to go back to AT&T stock then once you flash a custom ROM right? Because there is no AT&T base ROM for the ROM that was originally flashed on my Tab floating around to use as a base for my Roto Backup.
manekineko said:
So there's probably no way to go back to AT&T stock then once you flash a custom ROM right? Because there is no AT&T base ROM for the ROM that was originally flashed on my Tab floating around to use as a base for my Roto Backup.
Click to expand...
Click to collapse
i had the same problem u have... u must find someone with same rom u had and rotobackup it then flash stock rom from samfirn and then restore ur backup. dont forget to remove the boot and sbl files do not flash them. i did so and it hard bricked my tab needed jtag.
hope i helped...
avishai0528 said:
i had the same problem u have... u must find someone with same rom u had and rotobackup it then flash stock rom from samfirn and then restore ur backup. dont forget to remove the boot and sbl files do not flash them. i did so and it hard bricked my tab needed jtag.
hope i helped...
Click to expand...
Click to collapse
I have a Roto Backup, made from my own tab right after I got it, just no stock AT&T ROM to use as a base.
manekineko said:
So there's probably no way to go back to AT&T stock then once you flash a custom ROM right? Because there is no AT&T base ROM for the ROM that was originally flashed on my Tab floating around to use as a base for my Roto Backup.
Click to expand...
Click to collapse
That is correct. The backup made does not contain all the files.
DarkPal said:
Well any stock package (froyo or GB) will have its bootloaders included so don't worry about them. As for a recommendation for a stock package yes actually I have 2 for froyo. JK5 and JJ4 packages should be good to go if you want to downgrade your tab to froyo (if you for some reason wanted to do that).
Click to expand...
Click to collapse
I've done some research based on your recommendations. JK5 is actually no good I think, since it isn't a full ROM, and can't be used to re-partition.
JJ4, however, worked a charm. I downloaded it from samfirmware.com, and it came with all files necessary in the rar. Re-flashed pit, pda, modem and csc. Everything booted up as expected in Russian.
Then I used my Rotobackup, and re-flashed my pit and pda.
For the most part, everything is working, and restored, but for whatever reason, the boot animation is missing, and after the Galaxy Tab screen, it just turns black, and then after a while if I turn the screen off and on, I find it's already booted up (but booted with screen off). Any thoughts on why this occurs or how I can fix it?
My situation is that I'm increasingly beginning to suspect that my data connection is fritzy because of a hardware defect. I was on Overcome, and the data would just not be working when I turned on the Tab. The symptoms are one of the following: (1) data shows as connected and you can see the Tab sending but not receiving on the status bar, or (2) data shows as disconnected and then will show as connected for a moment and then show as disconnected again, or (3) data shows as disconnected, period. To fix any of these, I would have to either cycle the data or sometimes re-select the APN and reboot and then it would work. I then flashed to and used JPE for a few days, and observed today that my data showed as connected but would only send and not receive until I cycled the packet data setting.
Flashing back to stock, which I've now (mostly) done, is pretty much a last resort. I want to confirm whether this problem still exists on stock firmware, and if it does, I want to be in a condition to send in my Tab for repairs.
Just an update, I found this thread, which sounded a lot like my problem:
http://forum.xda-developers.com/showthread.php?t=899196
However, flashing jj4_bootloaders hasn't helped my missing logo problem. There is sound now, but still a black screen on bootup.
and none from samfirm are working? couldnt be.
Have you try booting up in recovery (power on, volume up combination) and do factory reset, clear cache?
cymagnus said:
Have you try booting up in recovery (power on, volume up combination) and do factory reset, clear cache?
Click to expand...
Click to collapse
As with the people that had the white line problem, with the corrupted graphics on the bootloader, I can't see recovery, just a black screen.
hi guys,
i have a serious problem now.
today I tryed to install Cyonegen ROM but during the install something went wrong and the phone started in a loop trying to boot again and again.
if i now want to insall the cyonegen.zip i get the Error message 7 (think becuse the efs folder is gone)
i have a backup of the previous EFS folder but i dont know how to restore it.
all the Tutorials i've found so far indicate that you have a working OS where you can put on the USB Debug for the ADB.
i also tryed to run samsungs kies but of course it's not recognized and kies is just telling me that the device is not supported.
any suggestions?
thanks in advance
Arne
You ever heard of Odin v1.83? Get a ROM with 3 files ([…]Code.tar, […]phone.tar, […]csc.tar) + pit file then check repartition and click start. After that your imei should be restored and you're ready to flash a custom Kernel and CyanogenMod.
Sent from my GT-I9000 using XDA App
moin blockbusta,
jo thanks
totally forget about odin.
set up an old rom from my ssd and now its working again. even the cyonegen rom is working now without any problems.
thanks m8
grüße aus - greetings from:
AKL / NZ
Arne
Hello all,
I was wondering can i change between a nandroid backup of an ICS install (say darknight) and a gingerbread nandroid backup.(say stock w/ rooted kernal)?
or do both nandroid backups need to be the same base?(ICS or GB)
Same base as nandroid required to restore.
Sent from my GT-I9000 using xda premium
U can. But u should flash to stock first. After that u can use restore frm backup.
Sent from my GT-I9000 using XDA
ICS Roms run a different file system to Gingerbread Roms. As mentioned in the previous post if you wish to restore your backup you would need to first flash a stock rom then restore your backup over this.
The process is to use Odin with the 3 files (phone, pda, csc) and the 512 pit file. You will also need to have repartition checked.
You may also need to flash stock a second time using the 3 files. The 2nd time don't use the pit file and make sure repartition is unchecked.
hi everybody
i have a big problem . for more than of one month i am working on my phone but i couldn't solve the problem,. my galaxy note was stuck on galaxy note logo . my previous Rom was 4.0.4 and i downloaded new 4.0.4 Rom but i couldn't flash it with Odin . it stuck on factory, i downloaded gingerbread stock Rom but was the same , after looking for solution on xda i found that has emmc bug . i couldn't access to recovery after flash gingerbread rom but i flash all of pit files that was on the emmc bug thread but none of them worked.but now i have bigger problem now is a tiangle between a pc and a mobile. how can i solve the problem? please help .
( i add this that i live in iran and we dont have a formal representative in Iran.):crying::crying:
king-heart said:
hi everybody
i have a big problem . for more than of one month i am working on my phone but i couldn't solve the problem,. my galaxy note was stuck on galaxy note logo . my previous Rom was 4.0.4 and i downloaded new 4.0.4 Rom but i couldn't flash it with Odin . it stuck on factory, i downloaded gingerbread stock Rom but was the same , after looking for solution on xda i found that has emmc bug . i couldn't access to recovery after flash gingerbread rom but i flash all of pit files that was on the emmc bug thread but none of them worked.but now i have bigger problem now is a tiangle between a pc and a mobile. how can i solve the problem? please help .
( i add this that i live in iran and we dont have a formal representative in Iran.):crying::crying:
Click to expand...
Click to collapse
Should try this http://forum.xda-developers.com/showthread.php?t=1667886
You'll have to identify the bad partition and then manualy rebuild the partition table with ADB.
You'll lose up to 3gb of space and stock roms will probably not work anymore without fc's. Cm based roms usually work best after emmc brick revival.
Sent from my GT-N7000 using xda premium
i tried all but doesnt work
SpyderTracks said:
You'll lose up to 3gb of space and stock roms will probably not work anymore without fc's. Cm based roms usually work best after emmc brick revival.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
yes i know that but the problem is this i use all of this method but i cant revival my phone cuz i cant access to recovery and when i turn on my phone i infront with a message that show a triangle between a pc and a phone and says use kiess. i use pit method without accesing to recovery cuz of this i flash all of pit files one by one but doesn't get any way to revival my phone.
screenshot of my phone
lionelia said:
Should try this http://forum.xda-developers.com/showthread.php?t=1667886
You'll have to identify the bad partition and then manualy rebuild the partition table with ADB.
Click to expand...
Click to collapse
i attached screenshot of my phone . i couldnt access to recovery .
After flashing pit file did you try and flash a kernel like Phillz?
Sent from my GT-N7000 using xda premium
pit files couldnt set
SpyderTracks said:
After flashing pit file did you try and flash a kernel like Phillz?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
thanks . actually not . cuz none of pit file couldnt set on my partition and stuck in odin.can i flash this kernel without flash pit?
new problem
now i have a bigger probem .my battery is out of charge and when i plug in phone to adapter it start bootllop and i cant enter in download mode cuz of low battery
help me plz
help me for 1 month im working on my phone :silly::silly::silly::crying::crying::crying:
Remove the battery. Put back. Then plug the charger and let the phone charge for a couple of hours before you boot into download mode again?
Buy an external battery charger. They are very cheap
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
My phone was bricked.
And I use hg42 revival method.
Simply go into download mode.
Use odin pc to flash stock rom (gingerbread preferred).
And....
Choose the pit from hg42, tick repartition.
Flash.
Voila. It is up alrd with a lost of 3gb. But I didn't care since I have ext sd.
PS:
It will be good if u know how to identify the bad block first. So u can choose the correct pit file to do repartition of ur device.
And.... u better charge ur battery first, no matter how r u goin to do it. I m sure u don't want to get worst while flash with odin pc, and ur battery dead.
^_^
Sent from N7105, at the corner of this rounded earth.
king-heart said:
hi everybody
i have a big problem . for more than of one month i am working on my phone but i couldn't solve the problem,. my galaxy note was stuck on galaxy note logo . my previous Rom was 4.0.4 and i downloaded new 4.0.4 Rom but i couldn't flash it with Odin . it stuck on factory, i downloaded gingerbread stock Rom but was the same , after looking for solution on xda i found that has emmc bug . i couldn't access to recovery after flash gingerbread rom but i flash all of pit files that was on the emmc bug thread but none of them worked.but now i have bigger problem now is a tiangle between a pc and a mobile. how can i solve the problem? please help .
( i add this that i live in iran and we dont have a formal representative in Iran.):crying::crying:
Click to expand...
Click to collapse
Check md5 sum of downloaded file...
I think it's the download of the file.
than try this-http://forum.xda-developers.com/showthread.php?t=1667886
After that try to flash PhilZ kernel (look for .tar file in Philz thread and flash via ODIN-i don't preffer ODIN but since u got nothing else u have to flash via ODIN PhilZ kernel) and some custom TW JB ROM from CWM that comes with PhilZ kernel.
So everything should be working or?
nokiamodeln91 said:
Remove the battery. Put back. Then plug the charger and let the phone charge for a couple of hours before you boot into download mode again?
Click to expand...
Click to collapse
Thank u i solve battery problem by changing with my friends but other problem . I couldnt install recovery to solve with pit fils
king-heart said:
Thank u i solve battery problem by changing with my friends but other problem . I couldnt install recovery to solve with pit fils
Click to expand...
Click to collapse
You just need download mode to flash pit file. Then once complete flash Phillz kernel.
Sent from my GT-N7000 using xda premium
SpyderTracks said:
You just need download mode to flash pit file. Then once complete flash Phillz kernel.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I flash all of patched pit file but doesnt work i flash more than 100 pit file.
king-heart said:
I flash all of patched pit file but doesnt work i flash more than 100 pit file.
Click to expand...
Click to collapse
You have to do it manualy with your brain and your hands.
With ADB you can check each partitions to find the one faultly and then create new one.
you will loose space on mass storage (UMS partition) but your phone will work.
So are you still on stock recovery? After flashing PIT you need to format emmc, data, cache and system before flashing new ROM with Odin. You need custom kernel for that.
Also, did you do factory reset with CWM.zip before you bricked?
Sent from my GT-N7000 using xda app-developers app
Ah!why are people using odin when flashing from phone is so easy???!!!i did not use odin.now i have philz kernel and ultimate jb rom v5.1
And i also live in iran!
Sent from my GT-N7000 using xda premium
sepehrthegreat-iran said:
Ah!why are people using odin when flashing from phone is so easy???!!!i did not use odin.now i have philz kernel and ultimate jb rom v5.1
And i also live in iran!
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
its because he has bricked the phone and no access to recovery currently. also Odin (PC/Mobile) is the only way to get back a stock official rom
My phone keep bootlooping and rebooting sometimes it work
Idk why is this but i have screenshot of recovery on stock
tried to install gingerbread from sammobile but
no use one week it was ok but after that it went back
I tried to replace the battery but the same results
Ubuntu-i9001 said:
My phone keep bootlooping and rebooting sometimes it work
Idk why is this but i have screenshot of recovery on stock
tried to install gingerbread from sammobile but
no use one week it was ok but after that it went back
I tried to replace the battery but the same results
Click to expand...
Click to collapse
+1
Ubuntu-i9001 said:
My phone keep bootlooping and rebooting sometimes it work
Idk why is this but i have screenshot of recovery on stock
tried to install gingerbread from sammobile but
no use one week it was ok but after that it went back
I tried to replace the battery but the same results
Click to expand...
Click to collapse
Flash full gingerbread (3 files with pit file) via odin and select repartition
Sent from my GT-I9000 using xda app-developers app
5aaled said:
Flash full gingerbread (3 files with pit file) via odin and select repartition
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
Chose a know working firmware, that you use before and work.
Like 5aaled said, make a clean flash: modem, kernel, PDA with repartition.
Sometimes i have that problem after i came back from ICS and JellyBean to GB. For me it work after i install the kernel with root.
P.S. You have to always have a know working firmware based on GB in order to fix this kind of problems
.
The phone is on stock since I bought it just add that
For the first solution it didn't work but thx for trying
Sent by the guy who hate to be thanked