Sorry, I'm new to this so sorry if this seems dumb.
So i bought the phone from rogers and immediately updated to froyo 2.2 official release by rogers/samsung.
I read about all the hype online about rooting and custom roms so i decided to give it a shot.
I used the superoneclick method to root my phone and it was successful.
I then used "rom manager - clockworkmod" and created a restore file before i did any flashing to my phone.
after creating a backup, i went on and flashed to the cognition 3.04.
Now my question is. Am i ever able to get my phone back to its original rom, kernel, and modem? the reason i want to know is because i might need to get my phone replaced due to some technical issues with the phone.
Also, does the backup of my phone after rooting play a part in any of this? if so, how?
Im sorry if there is already a post like this one. Its just that i couldn't find the answer through all the hundreds of pages of threads and replies, so I thought it would be easier to post a here with my specific question. Thanks.
regards,
danny
dsu said:
Sorry, I'm new to this so sorry if this seems dumb.
So i bought the phone from rogers and immediately updated to froyo 2.2 official release by rogers/samsung.
I read about all the hype online about rooting and custom roms so i decided to give it a shot.
I used the superoneclick method to root my phone and it was successful.
I then used "rom manager - clockworkmod" and created a restore file before i did any flashing to my phone.
after creating a backup, i went on and flashed to the cognition 3.04.
Now my question is. Am i ever able to get my phone back to its original rom, kernel, and modem? the reason i want to know is because i might need to get my phone replaced due to some technical issues with the phone.
Also, does the backup of my phone after rooting play a part in any of this? if so, how?
Im sorry if there is already a post like this one. Its just that i couldn't find the answer through all the hundreds of pages of threads and replies, so I thought it would be easier to post a here with my specific question. Thanks.
regards,
danny
Click to expand...
Click to collapse
Follow this link: http://forum.xda-developers.com/showthread.php?t=731989
It guides you through the process of going back to a stock ROM. Btw, I've used it and it works.
Good Luck!!
Christo_69 said:
Follow this link: http://forum.xda-developers.com/showthread.php?t=731989
It guides you through the process of going back to a stock ROM. Btw, I've used it and it works.
Good Luck!!
Click to expand...
Click to collapse
Dont use that link because it is for att firmaware. I havent seen any prepackaged odin one click for rogers.
This is my captivate. There are many like it buy this one is mine.
Christo_69 said:
Follow this link: http://forum.xda-developers.com/showthread.php?t=731989
It guides you through the process of going back to a stock ROM. Btw, I've used it and it works.
Good Luck!!
Click to expand...
Click to collapse
Thanks for that. Do you think Odin is the only way to do it or do you think i can use clockworkmod
flashman2002 said:
Dont use that link because it is for att firmaware. I havent seen any prepackaged odin one click for rogers.
This is my captivate. There are many like it buy this one is mine.
Click to expand...
Click to collapse
Do I not use that link in general, or just not to use the firmware given at the bottom? the steps are correct though, no?
also from my searching.
i can put my phone back to my backup point (just after rooting) through clockworkmod. Woud this change my rom back to stock from? how about kernel and modem and all that? would that all get reversed back to my backup point? meaning it will basically be a stock phone. But I think also read somewhere that my kernel and modem does not get changed back to rogers original one. is there a way to do it?
I then found this link: http://forum.xda-developers.com/showthread.php?t=846501
that says i need the original rogers rom for the captivate by the links there no longer work for download. Also on that thread, it was mentioned that the AT&T logo will still come up on startup, which would not be a good idea if i had to send my phone in for warrenty.
I then looked at : http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SGH-I896
Here it tells me to flash to a i9000 before i reflash to a rogers firmware in order to remove the at&t logo. it also provides me with a link for the " Official Rogers Stock ROM ", but according to somebody on the first link i posted here, it isnt the "official rom"
Any ideas?
This is where I got the stock 2.2 file from http://forum.xda-developers.com/showthread.php?t=905042.
Edit: I have flashed a bunch of times and have never got stuck with the AT&T startup after flashing back to stock with the odin file.
Akalon said:
This is where I got the stock 2.2 file from http://forum.xda-developers.com/showthread.php?t=905042.
Edit: I have flashed a bunch of times and have never got stuck with the AT&T startup after flashing back to stock with the odin file.
Click to expand...
Click to collapse
Thanks. Do you know if my kernel is going to go back to stock too or is it going to remain the same as the custom rom one?
dsu said:
Thanks. Do you know if my kernel is going to go back to stock too or is it going to remain the same as the custom rom one?
Click to expand...
Click to collapse
If you use the odin file the kernal and modem will revert back to stock.
Akalon said:
If you use the odin file the kernal and modem will revert back to stock.
Click to expand...
Click to collapse
Thanks. So im assuming now that the only time my kernel and modem wont go back to stock is when i flash with CWM. correct?
I haven't tried using the CWM file in that link so I'm not sure if it contains the kernel and modem. As far as custom roms go most if not all come packaged with the kernel and modem of choice.
So.. When I do a "master clear" from http://forum.xda-developers.com/showthread.php?t=731989...
Would everything be wiped? I read somewhere that when you do a "wipe" from your settings it only clears user settings or something. What would a "wipe"
from the recovery menu do?
I flashed to a different rom today thinking it will help my battery issue. When i am flashing from one rom to the next, i do a restore back to my backup before i flash to a new rom. Is this the correct method? or am i supposed to wipe beforehand? The reason i ask is because this is my 2nd rom and my battery issue still seems to be there. I tried other methods of fixing hte battery but nothign seems to work. When i looked into root explorer, i see that there are a lot more files now everywhere, than when i first started. would some of them be from my previous rom? if so how do i remove them?
I was trying to install the CM 10 jelly bean rom into my p6210, but it was failed, and somethings were already changed after that time, such as my usb cant transfer data to my device (which is already known), the device wont save any changes such as password, brightness....etc, and the lock screen doesn work. So, I thought it could be fixed by the android recovery 3e, I did recover it few times,and nothing changed. But now, it doesnt even start up, could anyone help me plzzzz? I just want it back to the factory from.
If you installed ClockworkMod Recovery 6.0.1.0 and made a backup before flashing CM10 (as advised on the CM10 thread), you can just restore the backup. But it sounds as if you didn't.
You might try starting with these instructions for installing stock ICS using Odin and temporary CWM. Or this thread could be helpful. Beyond that I don't know enough to give any specifics. But you can search these forums for "heimdall" and "pit" to find several other threads about installing stock firmware on crippled devices. Good luck.
Sun_Cat said:
If you installed ClockworkMod Recovery 6.0.1.0 and made a backup before flashing CM10 (as advised on the CM10 thread), you can just restore the backup. But it sounds as if you didn't.
You might try starting with these instructions for installing stock ICS using Odin and temporary CWM. Or this thread could be helpful. Beyond that I don't know enough to give any specifics. But you can search these forums for "heimdall" and "pit" to find several other threads about installing stock firmware on crippled devices. Good luck.
Click to expand...
Click to collapse
Thanks a lot!!!! I bring it back, well... it wasnt actually "me", should give the credit to the threader who write that thread, but thanks anyway!!
Hi all,
I literally just read through about 15-20 different threads using the search term "bootloop" but almost everyone was on OTA JB, and that doesn't describe my current situation, so here goes:
Got a replacement tablet last week. Used stock for a while, then decided to unlock/root it like I've done in the past (Had a TF300T previously and wrote myself a detailed guide so I consider myself intimately familiar with the process).
Just to clarify, I AM STILL ON ANDROID ICS. I DID NOT TAKE THE JB UPDATE NOR FLASH ANY JB ROM OR RECOVERY.
I unlocked, used NVFlash to make some files, and flashed over the 5.5.0.4 CWM recovery, just dandy. I then make a nandroid backup of my current tablet status (unlocked, not rooted, stock ICS) and copied that over to my desktop. I copied over a nandroid backup from my old tablet (ICS blackbean #5 I think, rooted, unlocked) and attempted to restore that recovery via CWM. The recovery restored fine, but I was stuck in a perpetual "bootloop" i guess, with the BAKED team logo showing nonstop until my tablet died.
Came back home with this tablet (had gone to my brothers house right after restoring so didn't have any of my tools) and tried to fix what I thought was an easy fix (I've done it before, just can't remember how). I wiped everything, did a factory wipe/reset through CWM, formatted my partitions, cleared my caches, just about everything I could think of. Nothing has worked. I've tried flashing the stock ROM but I get an error similar to "remote <invalid size>" about 1/3rd of the way through sending it, so I'm not sure. If I can just get stock anything installed at this point I will be ecstatic.
I do want to iterate that I feel strong that my device is NOT hardbricked. I have FULL ACCESS to CWM, ADB, Fastboot, and APX. I know it's just something small and stupid that I am forgetting.
Can anyone please help me get my tablet back up and running? My laptops' screen died and is currently out of commission so I -need- something to take notes on in class in the meantime, and have no other access to another laptop.
Relevant details:
TF300T 32GB - came with STOCK ICS and did NOT TAKE THE OTA JB UPDATE
Previous setup before my "brick" : Stock ICS, Unlocked, NOT ROOTED. I attempted to restore a nandroid backup from my previous tablet (also a TF300T 32GB with STOCK ICS)
Steps I tried to do: Format partitions, caches, wipe data/factory reset, tried to flash stock firmware, tried to flash CM 9.1 and CM10, no luck.
Current setup: I have full access to ADB, Fastboot, APX, have backup NVFlash files (which I don't know how to use to restore my tablet), and it currently has a CWM 6.0.1.4 TOUCH recovery on it (which is bloody awesome).
Tablet is currently completely dead (red battery logo) and charging atm.
Any expedient help will be truly appreciated and greeted with many thanks!!
-Opethfan89
You really should have taken the jb update.. that is were I would star. Try to update to the latest bootloader.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
elesbb said:
You really should have taken the jb update.. that is were I would star. Try to update to the latest bootloader.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
I didn't want to take JB because it re-locks the bootloader and doesn't have adobe flash, which I think is an injustice.
I am wiling to take the JB update if I can find a guide on how to restore ICS bootloader using my NVFlash files.
I'm on the IRC channel until at least 7PM EST in the US (while I'm at work) if anyone can provide me some real-time advice.
opethfan89 said:
I didn't want to take JB because it re-locks the bootloader and doesn't have adobe flash, which I think is an injustice.
I am wiling to take the JB update if I can find a guide on how to restore ICS bootloader using my NVFlash files.
I'm on the IRC channel until at least 7PM EST in the US (while I'm at work) if anyone can provide me some real-time advice.
Click to expand...
Click to collapse
Check post #11 in this thread. It is from rayman the op and dev for nvflash. I think it covers your request.
Good Luck!
tobdaryl: Thanks for the response. I've actually read through that post because that seems to be the only guide on how to restore via NVFlash.
NVFlash aside, does anyone know what is causing the issue that I'm having right now? My tablet is useless and I'd rather not try to go to best buy and exchange it since my local store doesn't have any in stock and the store i got it from was almost 2 hours away :X
I will try to flash over some sort of stock firmware and hope that works. maybe i just need to re-download it, i don't know. if that doesn't work i will flash over the JB firmware after i get some more instruction on how to restore wtih nvflash.
opethfan89 said:
tobdaryl: Thanks for the response. I've actually read through that post because that seems to be the only guide on how to restore via NVFlash.
NVFlash aside, does anyone know what is causing the issue that I'm having right now? My tablet is useless and I'd rather not try to go to best buy and exchange it since my local store doesn't have any in stock and the store i got it from was almost 2 hours away :X
I will try to flash over some sort of stock firmware and hope that works. maybe i just need to re-download it, i don't know. if that doesn't work i will flash over the JB firmware after i get some more instruction on how to restore wtih nvflash.
Click to expand...
Click to collapse
I think you restored a JB rom(baked) to a unit that still had an ICS bootloader.
recovery - your recovery (JB or ICS) must be changed to match the bootloader of the rom
I suggest twrp on this unit - many problems with cwm
Perhaps my understanding is incorrect but the Baked rom I was using was made for ICS, and I've never had any issues on it previously. I have no objections to using TWRP but I am also not familiar with it so until I get back up and running, I'd like to stick with CWM.
I am waiting for a response back from Rayman in regards to a guide on how to restore via NVFlash so that I can comfortably go to the JB bootloader/rom and still change back if I deem it necessary.
You're correct (assuming it *was* BB5): BB5 was based on ICS bootloader.
Have you tried one of the "return to stock" posts: http://forum.xda-developers.com/showthread.php?t=1757077. Be sure to do a full wipe before.
If you need a stock ASUS ICS ROM, here's a US one. (don't use on WW SKU)
Good luck.
---------- Post added at 12:31 PM ---------- Previous post was at 12:27 PM ----------
opethfan89 said:
I am waiting for a response back from Rayman in regards to a guide on how to restore via NVFlash so that I can comfortably go to the JB bootloader/rom and still change back if I deem it necessary.
Click to expand...
Click to collapse
One quick note: NVFlash is good to have, don't get me wrong. But it's really more for if you lose the bootloader altogether. The ASUS JB bootloader has plenty of great ROMs compatible with it at this time so you shouldn't worry about having to go back.
---------- Post added at 12:36 PM ---------- Previous post was at 12:31 PM ----------
opethfan89 said:
I didn't want to take JB because it re-locks the bootloader and doesn't have adobe flash, which I think is an injustice.
Click to expand...
Click to collapse
That is incorrect.
There is no way to 're-lock' the bootloader. Upgrading to an ASUS JB rom will upgrade your bootloader and replace your recovery, but the bootloader remains unlocked.
JB itself is where *support* for Flash ended; this has nothing to do with the bootloader. BB5, a JB ROM, does not *support* flash. This doesn't mean it won't work, just that it's not longer made available through the Play store. You can always side-load it.
opethfan89 said:
Perhaps my understanding is incorrect but the Baked rom I was using was made for ICS, and I've never had any issues on it previously. I have no objections to using TWRP but I am also not familiar with it so until I get back up and running, I'd like to stick with CWM.
I am waiting for a response back from Rayman in regards to a guide on how to restore via NVFlash so that I can comfortably go to the JB bootloader/rom and still change back if I deem it necessary.
Click to expand...
Click to collapse
Good luck in whatever path you take!
Search on xda is still down. Manual search I have only found one cwm 6.0.1.4. I hope you have found another that was for ICS. You may wish to read the op for that thread if it is the source of your cwm 6.0.1.4.
tobdaryl: In that same thread, if you go to post #71 on page 8 you will see the OP (the actual dev) responded to my request for an ICS CWM Touch recovery in that post (link here). So I am assuming it is a working ICS CWM recovery, but even before I flashed it I was still using the old 5.5.0.4 CWM recovery. I was forced to flash 6.0.1.4 in order to have support for external SD to try and flash something that works.
Bsaman: Yes, I've tried return to stock. When I send the file, it gives me an error on the command prompt similar to "remote <invalid size>", as I've stated in my original post. I can't figure out why I'm getting that error and I've been able to flash stuff before without any issues. This is the first time I've actually messed up and had a nonfunctional tablet for an extended amount of time. Also, thank you for clarifying my inconsistencies regarding JB and adobe flash. If I can side-load it and still have support, then I have no problems going to JB.
My connection here at work (a frickin T1 at a data center!!!) is only 170kb/s download, so I am going to use the firmwares that I've had downloaded for a while. I will flash the latest firmware and hope that it works.
opethfan89 said:
tobdaryl: In that same thread, if you go to post #71 on page 8 you will see the OP (the actual dev) responded to my request for an ICS CWM Touch recovery in that post (link here). So I am assuming it is a working ICS CWM recovery, but even before I flashed it I was still using the old 5.5.0.4 CWM recovery. I was forced to flash 6.0.1.4 in order to have support for external SD to try and flash something that works.
Bsaman: Yes, I've tried return to stock. When I send the file, it gives me an error on the command prompt similar to "remote <invalid size>", as I've stated in my original post. I can't figure out why I'm getting that error and I've been able to flash stuff before without any issues. This is the first time I've actually messed up and had a nonfunctional tablet for an extended amount of time. Also, thank you for clarifying my inconsistencies regarding JB and adobe flash. If I can side-load it and still have support, then I have no problems going to JB.
My connection here at work (a frickin T1 at a data center!!!) is only 170kb/s download, so I am going to use the firmwares that I've had downloaded for a while. I will flash the latest firmware and hope that it works.
Click to expand...
Click to collapse
That's great your recovery is ICS, I'll bookmark for later use. It is good info to pass along.
Minor update: Attempted to flash the US firmware US_epad-user-10.4.2.13. When I flashed it, I got the following errors:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I get the following error on my tablet: Failed to process command flash: system error (0xa).
I am currently reading a post here and will try to follow the steps and post a follow-up post. I really hope I can get this working!!!!
*EDIT* The steps in that thread did NOT work. Exact same error. What kills me is he described my problem VERBATIM. So I'm downloading the JB update 10.4.2.20 right now and will try to flash that, hopefully it works!!!
opethfan89 said:
Minor update: Attempted to flash the US firmware US_epad-user-10.4.2.13. When I flashed it, I got the following errors:
Click to expand...
Click to collapse
Sounds like the file is failing the checksum verification. Since you've tried multiple files, I doubt the problem is with the originating file itself. I wonder if you might have a bad USB port or cable. No easy way to try another cable unless you know someone with a TF tablet, but you can try a different USB port.
bsaman said:
Sounds like the file is failing the checksum verification. Since you've tried multiple files, I doubt the problem is with the originating file itself. I wonder if you might have a bad USB port or cable. No easy way to try another cable unless you know someone with a TF tablet, but you can try a different USB port.
Click to expand...
Click to collapse
I actually have a spare USB cable that I redeemed through my replacement plan and have tried sending files via both cables, no go. My co-worker has a TF200 but that's obviously a whole 'nother beast.
I do want to report that I followed the steps in the thread I linked in my last post and after I flashed the boot.blob I no longer see the Android icon in the fastboot/wipe data menu. So I'm even further away from a working tablet than I was before.
Is there -any- other solution or am I going to have to redeem my plan (and lose $80) again and get a NEW tablet? I -really- need this thing to work for school and for my job as well, so I am open to damn near any possibilities.
If anyone can post a guide regarding how to restore my files via NVFlash, I think that might be my best step. At least I'll know which bootloader I'm on, and then can flash the appropriate files from there.
I'm getting desperate guys, help a brotha out! I do -not- want to have to buy another replacement plan and redeem this one just because I bricked it from my own stupidity....
opethfan89 said:
I actually have a spare USB cable that I redeemed through my replacement plan and have tried sending files via both cables, no go. My co-worker has a TF200 but that's obviously a whole 'nother beast.
I do want to report that I followed the steps in the thread I linked in my last post and after I flashed the boot.blob I no longer see the Android icon in the fastboot/wipe data menu. So I'm even further away from a working tablet than I was before.
Is there -any- other solution or am I going to have to redeem my plan (and lose $80) again and get a NEW tablet? I -really- need this thing to work for school and for my job as well, so I am open to damn near any possibilities.
If anyone can post a guide regarding how to restore my files via NVFlash, I think that might be my best step. At least I'll know which bootloader I'm on, and then can flash the appropriate files from there.
I'm getting desperate guys, help a brotha out! I do -not- want to have to buy another replacement plan and redeem this one just because I bricked it from my own stupidity....
Click to expand...
Click to collapse
I gave you a link earlier from rayman himself how to recover from your situation.
If you want jb try the first jb 10.4.2.9 - why this one? Rumor is this is when the partitions were resized; they are different between jb and ics. size error?
---------- Post added at 10:42 PM ---------- Previous post was at 10:05 PM ----------
opethfan89 said:
tobdaryl: In that same thread, if you go to post #71 on page 8 you will see the OP (the actual dev) responded to my request for an ICS CWM Touch recovery in that post (link here). So I am assuming it is a working ICS CWM recovery, but even before I flashed it I was still using the old 5.5.0.4 CWM recovery. I was forced to flash 6.0.1.4 in order to have support for external SD to try and flash something that works.
Bsaman: Yes, I've tried return to stock. When I send the file, it gives me an error on the command prompt similar to "remote <invalid size>", as I've stated in my original post. I can't figure out why I'm getting that error and I've been able to flash stuff before without any issues. This is the first time I've actually messed up and had a nonfunctional tablet for an extended amount of time. Also, thank you for clarifying my inconsistencies regarding JB and adobe flash. If I can side-load it and still have support, then I have no problems going to JB.
My connection here at work (a frickin T1 at a data center!!!) is only 170kb/s download, so I am going to use the firmwares that I've had downloaded for a while. I will flash the latest firmware and hope that it works.
Click to expand...
Click to collapse
There is no post 71 in the thread where rayman tells what to use and how to restore ics. I am not speaking of ics recovery file or partition but how to recover ics with nvflash.
Check post #11 in this thread. If you need blobtools look at post #14.
Could you tell us where work is? I'd like to get service there and slow my life. LOL!
tobdaryl said:
I gave you a link earlier from rayman himself how to recover from your situation.
If you want jb try the first jb 10.4.2.9 - why this one? Rumor is this is when the partitions were resized; they are different between jb and ics. size error?
---------- Post added at 10:42 PM ---------- Previous post was at 10:05 PM ----------
There is no post 71 in the thread where rayman tells what to use and how to restore ics. I am not speaking of ics recovery file or partition but how to recover ics with nvflash.
Check post #11 in this thread. If you need blobtools look at post #14.
Could you tell us where work is? I'd like to get service there and slow my life. LOL!
Click to expand...
Click to collapse
Work for me is at a data center in Virginia. We're not operational so they have us on a ridiculously slow connection :X
Just wanted to give an update: I'm working to try and follow those guides to get stuff restored. It's difficult when there are 6 links to 5 different pages, but i'm working through it.
I failed to mention this before, or perhaps I didn't notice it, but when I go to select recovery mode on tablet with volume down + power key, it instantly goes to the fastboot/wipe data screen. From there, if I wipe data (which only takes like 1 second) it'll reboot into recovery but I have no other way of rebooting into recovery atm. What does this mean? How am I able to fix this?
I was trying to flash back to the my old recovery which is the 5.5.0.4 (ICS) version of ClockworkMod thinking that might help stuff, but this time when I went to choose wipe data and get into the recovery, it said "Key driver not found.. Booting OS" and then went straight into fastboot mode. I really hope I didn't just break things even more and lose fastboot access....
Is anyone else able to post and perhaps provide some insight? A dev maybe? I'm getting desperate at this point for a damn working tablet
**EDIT** Crap, I think I may have just lost access to my recovery from doing that. I can't boot into recovery anymore atm, regardless of which one I flash. Same "key driver not found" error as above.
Maybe you can upload in youtube a movie of your troubelshoot
Envoyé depuis mon ASUS Transformer Pad TF300T avec Tapatalk
I freakin fixed it!!!!!!!!!!!
I FIXED MY TABLET!!!!!!!!
I was able to successfully use NVFlash in order to un-brick my tablet!!! I am going to eat lunch and then write a guide on EXACTLY what I did, because the steps are NOT well-documented to the point that anyone is able to follow them.
Please stay tuned for a detailed, thorough, and step-by-step guide on how to restore your ICS bootloader and unbrick yourself on a TF300T!!!!!
Any luck in creating the noob guide for unbricking your TF300T? I am stuck and deploying soon. I would like to get it up and running before I leave. Thanks!
Sean
Bricked TF300T
Hi There !
Can you please post the step by step guide .
Thanks !
opethfan89 said:
I FIXED MY TABLET!!!!!!!!
I was able to successfully use NVFlash in order to un-brick my tablet!!! I am going to eat lunch and then write a guide on EXACTLY what I did, because the steps are NOT well-documented to the point that anyone is able to follow them.
Please stay tuned for a detailed, thorough, and step-by-step guide on how to restore your ICS bootloader and unbrick yourself on a TF300T!!!!!
Click to expand...
Click to collapse