Related
I just got a brand new SGS2 GT-i9210 from sweden. After unsimlocking it, it perfectly works on our experimental 4G (2.6Ghz) network in France.
I tried to root it, but the zergrush doomlord rootkit v4 does not work properly, it ends with the "Hellions with BLUE flames" error.
I used this rootkit with different SGS2 4G/LTE smartphone and never had problem, it always worked.
I was just wondering if someone could help me to root this GT-i9210...
Thanks in advance for your replies
I'd love to get into this as soon as I've got rid of the Tele2 simlock on my i9210. Any tips on reliable unlock code providers for this phone?
As this post comes up high on the google results for rooting the GT-i9210, here's the link to the ACTUAL page on how to root it.
Edit: Probably better to link to the OCAU thread http://forums.overclockers.com.au/showthread.php?p=14233218#post14233218
http://forum.xda-developers.com/showthread.php?t=1340526
This, 100%, works. More discussion on this phone here:
http://forums.whirlpool.net.au/forum-replies.cfm?t=1891584
xrobau said:
As this post comes up high on the google results for rooting the GT-i9210, here's the link to the ACTUAL page on how to root it.
http://forum.xda-developers.com/showthread.php?t=1340526
This, 100%, works. More discussion on this phone here:
http://forums.whirlpool.net.au/forum-replies.cfm?t=1891584
Click to expand...
Click to collapse
I don't dare to belive you.
The root method you refer to in your link is for models sold on the US market, in Europe this model is branded GT-I9210 (EU) and is similar, but not identical to the models in US or Canada.
I have followed a Swedish thread where people has used this method, but many of them has bricked their phones....
The whole process works fine through all steps until rebooting.
The back key and the menu key stops working.
I wish somebody could fix a reliable root method for GT-I9210.
I'm the guy who wrote that post on Whirlpool. I have a pair of GT-I9210Ts, both of which are now rooted using CWM and superuser.zip.
Note that this doesn't actually CHANGE anything on the phone. So it's not going to brick it. All it does is install CWM, and then uses CWM to install superuser.zip. I can't possibly see how it's possible to brick the phone doing this.
F5:ad said:
I have followed a Swedish thread where people has used this method, but many of them has bricked their phones....
The whole process works fine through all steps until rebooting.
The back key and the menu key stops working.
Click to expand...
Click to collapse
Yep, I did this today. The phone's back and menu buttons aren't working. I tried installing softkeys from the Market but still no go. Is there a solution to this problem?
That's.. very very strange. Someone else reported it, but I have no idea why this happened. You're not touching ANYTHING to do with the buttons. All you're doing is updating the recovery.img and then installing a package. I've rooted three phones now, and haven't had that problem.
Can you read http://forums.overclockers.com.au/showthread.php?p=14233218#post14233218 and tell me if you did anything different?
briteway said:
Yep, I did this today. The phone's back and menu buttons aren't working. I tried installing softkeys from the Market but still no go. Is there a solution to this problem?
Click to expand...
Click to collapse
I've put a bunch of recovery information on that ocau post (linked above). Have a run through that. If you're NOT using a Telstra phone, I'm unsure where you're going to find the correct roms though 8-\
xrobau said:
I've put a bunch of recovery information on that ocau post (linked above). Have a run through that. If you're NOT using a Telstra phone, I'm unsure where you're going to find the correct roms though 8-\
Click to expand...
Click to collapse
The method you have posted is one I have already tried, 2hrs after getting my phone from Telstra. Back button and Menu buttons blank out and no longer work.
No one should use this method until it is specifically tried and tested for the phone.
EDIT: Just to assist you a bit further with the method.
- A full factory reset was completed, not working.
- Telstra firmware downloaded, installed, factory reset, not working.
- Dialled *#*#2663#*#* - Selected Touch Key F/W to upgrade, not working.
----- Phone F/W was marked as 0x4, Part F/W was 0x0.
I believe this was the issue, the fact that there was a number mismatch.
Those with the GT-I9210 visit this link for Original EU Rom.
www"dot"sammobile"dot"com
As I mentioned on OCAU, I didn't have much of a problem.
"xrobau" Did you have any moment when the buttons did not work?
Hi,
Any updates on this phone rooting procedure?
This generic firmware will work in Portuguese operators? Any European tested it?
Thanks
Sent from my GT-I9210 using XDA
It's in Portuguese. Translate with Google. A friend of mine did root gt-i9210. I've used this method to root mine.
http://stuffandroid.blogspot.pt/2012/04/como-fazer-root-no-samsung-galaxy-s-ii.html
Sent from my GT-I9210 using XDA
In my case the keys stopped working after flashing first time a kernel with cwm recovery. The phone also didn't boot anymore. The kernel itself was backuped with the very same cwm.
Before I flashed the kernels with odin and also with "dd" command. No problems with the keys.
Based on these things I got the feeling that there could be something wrong with cwm.
I could not fix it so far.
I'm not sure whether my post would be valid any longer on a thread more than a year old.
Anyway, if someone needs a pre-rooted version of the latest stock Jelly Bean 4.1.2 XXUAMF1 COV (GT-I9210), they can do so from this thread, post #4:
http://forum.xda-developers.com/showthread.php?p=34712551
Flashed it via Odin & using it without any issues on my S II LTE GT-I9210T.
Jp
:good:
i would like to preface this by acknowledging that this was a serious mess up on my part. i tried to root my sprint nexus s 4g the other night. I used a guide on nexusshacks dot com due to its simplicity and detailed instruction.i did all necessary steps but the first time i tried to boot into clockwork recovery i got a dead android and a red triangle error message. my phone restarted a few minutes later and i was able to fix that problem (or so i thought) and boot into recovery. i applied the correct zips and such that came in the download and i went off to sleep. the next day i tried accessing super user and realized it didn't work. i went back to that guide and noticed that its was for ginger bread and there was a new guide linked at the top for ICS . this is were i need assistance. is it enough to just do a hard factory reset and start over or is there more to it than that. also, will such a guide work on jelly bean or should i find another guide. i only use that site for the fact it has a well done step by step tutorial and all needed files compiled into one download. i am aware this site is much better for such things, but i'm, new here so i felt a tad intimidated. anyway, any help is appreciated, i already looked for similar problems but no one else made the dumbass mistake.
(i cant post links because this is my first post, so i apologies for the inconvenience)
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
How to root the SGH-T769 Galaxy S Blaze 4G from T-Mobile
if you are running Android 4.0.4 Ice Cream Sandwich
**As always, I am NOT responsible for any bricked or broken devices. These steps worked for me, but are NOT guaranteed to work for you. USE AT YOUR OWN RISK**
STEPS
You must first downgrade your phone to Gingerbread
Back up all the data on your Blaze and perform a factory reset. If you do not do this, you will have issues with the setup wizard force closing (voice of experience)
Download Odin here and extract the file. Open Odin.
Go to SamMobile's Firmware Page
Register with SamMobile (it's free) and make sure you are logged in to continue
Enter your device (Blaze 4G is T-769)
In the chart at the bottom, click July 2012 Version 2.3.6
Follow the directions on the page to download the Gingerbread firmware
Extract these files
Download the PIT
In Odin, hit PIT and use the PIT file you just downloaded
Hit PDA and put in the .tar you downloaded from SamMobile
MAKE SURE YOU ONLY HAVE AUTO REBOOT CHECKED AND NOTHING ELSE
Put your device into download mode (instructions here)
Odin should say "Added!"
Hit START to begin flashing
The phone will reboot on its own when flashing is complete
Check the firmware version in the "About Phone" section in Settings to make sure you are now in Gingerbread 2.3.6
You have now downgraded your device.
Now you need to flash the rooted kernel. Follow the instructions here.
You should now be rooted!
Good luck! I wish you all the best!
msohsonice said:
I just had to replace my rooted Blaze through insurance because phones and water don't mix.
I'm trying to root the new one I just got, but I am running into a lot of issues and would really appreciate some help.
The old phone was running Gingerbread and I was easily able to root it with Odin. It took only a few minutes.
The new one, however, is not so nice. Here is a list of what I've tried:
Tried rooting with Odin
Realized I was flashing the Gingerbread version and soft bricked the phone where it wouldn't go past the boot screen (bar fully loaded and then would do nothing else)
Reverted to stock ICS
Searched for 3 days and nights to find an ICS version to flash
Supposedly found a few, but each time they soft bricked the phone and I had to re-flash the ICS stock
Downgraded to Gingerbread so I could flash the version in Odin that I knew worked
The downgraded version was buggy and the phone wouldn't go past the first step of the setup wizard
Repeated steps 5-7 all night long before giving up and asking for help
I've tried all k0nane's tutorials, read through a ton of XDA threads, tried Blz3r, and tried downgrading using firmware on SamMobile.
Fingers crossed someone will help me :fingers-crossed:
THANKS IN ADVANCE TO YOU WONDERFUL PEOPLE ON XDA
Click to expand...
Click to collapse
try following this thread:
http://forum.xda-developers.com/showthread.php?t=1917570
which will bring you back to stock 2.3.6 and then re-root following K0nane's thread precisely.
If you can get a root kernel and CWM, you'll be golden.
Nice write-up
It's curious though, as I never had an issue just ODINing the cwm recovery from here and being good to go - regardless of being on GB or ICS. That being said - more than one way to skin a cat and all that
dwitherell said:
Nice write-up
It's curious though, as I never had an issue just ODINing the cwm recovery from here and being good to go - regardless of being on GB or ICS. That being said - more than one way to skin a cat and all that
Click to expand...
Click to collapse
I used those exact instructions and had nothing but issues. I swear I have grey hairs now from the stress of almost bricking my brand new device
msohsonice said:
I used those exact instructions and had nothing but issues. I swear I have grey hairs now from the stress of almost bricking my brand new device
Click to expand...
Click to collapse
LOL well that's no good! Well, like I said - a number of ways to reach that ultimate goal. My comment was more based on the fact that I am genuinely curious as to the variability in outcome seen with things like this (it happens across devices even). Really the important thing is attaining that goal - so kudos to you for the nice write-up on another method of getting there Now you just need to grab some tweezers and remove the evidence of a struggle lol
Nice! I've always just ODIN'd back to GB, I've always been curious on how to root ICS
Hi I want to unlock my t mobill samsung sgh t 769
could you Help me ?
hello i am rooted with twrp recovery installed. I was able to unroot and download the latest 5.0.2-01001 ota but im not able to install the update it would just take me to twrp recovery and stop there.?? i found the update zip and tried to flash it in twrp but it says it cant mount and failed to flash any help would be appreciated.
OTA updates will require a stock recovery. I'm in the process of getting an Idol 3 but I used to have an Idol 2 and, to return to a completely stock ROM, I had to use the Alcatel Mobile upgrade too which identified my phone, downloaded the correct firmware, and restored the phone. Prior to restoring back to stock, I had cwm and root.
Thanks for the reply I tried the software update but its not working keep saying I have the latest even when I did a full wipe. Using the latest 4.9.2 version...is there a way to make a twrp flashable ota zip from the downloaded update file in the ota cache..
lude86 said:
hello i am rooted with twrp recovery installed. I was able to unroot and download the latest 5.0.2-01001 ota but im not able to install the update it would just take me to twrp recovery and stop there.?? i found the update zip and tried to flash it in twrp but it says it cant mount and failed to flash any help would be appreciated.
Click to expand...
Click to collapse
You cannot be rooted and install a stock update...it's mentioned in several places throughout the forum. Quickest solution is to use the mobile q to restore the whole phone to factory (and in the process it will put the latest version on it). Otherwise you have to fully unroot AND if you have modified any files such as build.prop or other system files it still won't work. You CAN install with TWRP however in the process of the install it will overwrite it with stock recovery. If I had to guess I'd say you did not do the supersu FULL unroot.
famewolf said:
You cannot be rooted and install a stock update...it's mentioned in several places throughout the forum. Quickest solution is to use the mobile q to restore the whole phone to factory (and in the process it will put the latest version on it). Otherwise you have to fully unroot AND if you have modified any files such as build.prop or other system files it still won't work. You CAN install with TWRP however in the process of the install it will overwrite it with stock recovery. If I had to guess I'd say you did not do the supersu FULL unroot.
Click to expand...
Click to collapse
mobile Q is horse manure now. I ran into the same problem, whereby it says you're up to date (which it's not), even if you're running 5.0.2.7SMA-UEA1 ! I only know that one because I inadvertently flashed 5.0.2.7SMA-UEA1 today when I meant to flash 5.0.2.7SRA-UEA2.
Speaking of 5.0.2-01001, 5.0.2.7SRA-UEA2 is on longer the latest yeah... anyway we can update the firmware page? http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
I just tried to OTA update to 5.0.2-01001, but OTA of course does not work if TWRP is acting recovery; it just reboots to TWRP and then if you reboot system, nothing happens. Although seemingly never mentioned, we must remove TWRP (even read only TWRP) before updating OTA?
tekka-maki said:
mobile Q is horse manure now. I ran into the same problem, whereby it says you're up to date (which it's not), even if you're running 5.0.2.7SMA-UEA1 ! I only know that one because I inadvertently flashed 5.0.2.7SMA-UEA1 today when I meant to flash 5.0.2.7SRA-UEA2.
Speaking of 5.0.2-01001, 5.0.2.7SRA-UEA2 is on longer the latest yeah... anyway we can update the firmware page? http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
I just tried to OTA update to 5.0.2-01001, but OTA of course does not work if TWRP is acting recovery; it just reboots to TWRP and then if you reboot system, nothing happens. Although seemingly never mentioned, we must remove TWRP (even read only TWRP) before updating OTA?
Click to expand...
Click to collapse
The thread is closed. There is also no reason you NEED the most recent posted as you can flash any of them and then do an update. Mobile Q is the recommended method to re-do your phone if you can't manage to make a backup before messing with it. It has apparently worked just fine for people in this forum for every model type mentioned so the burden of proof is on your part if you can't get it to work.
famewolf said:
The thread is closed. There is also no reason you NEED the most recent posted as you can flash any of them and then do an update. Mobile Q is the recommended method to re-do your phone if you can't manage to make a backup before messing with it. It has apparently worked just fine for people in this forum for every model type mentioned so the burden of proof is on your part if you can't get it to work.
Click to expand...
Click to collapse
Why would the thread be 'closed'. OP's problem is unresolved.
'Worked' is the operative term for. Perhaps you haven't used to Mobile Q tool lately? As OP (and I) said (today), running OTA from 6045 now just reboots to TWRP, no install. Alternately, when attempting to update 6045 from Mobile Q, it just throws a funny English 'update no needed' kinduva message (pic). Incidentally, have you been to their website to find an update to this tool? Holy crap, in that respect, Mobile Q must be a virtual breakthrough for these boys! :laugh:
You're so helpful here famewolf. I've both appreciated and have been comforted by seeing your knowledge all over this subforum, since day 1. Please provide help. You tell me where this 'people' person is, and I'll wank on his boner for you. Then we have a definition of 'working fine' in stead of 'worked fine'. ? :angel:
tekka-maki said:
Why would the thread be 'closed'. OP's problem is unresolved.
'Worked' is the operative term for. Perhaps you haven't used to Mobile Q tool lately? As OP (and I) said (today), running OTA from 6045 now just reboots to TWRP, no install. Alternately, when attempting to update 6045 from Mobile Q, it just throws a funny English 'update no needed' kinduva message (pic). Incidentally, have you been to their website to find an update to this tool? Holy crap, in that respect, Mobile Q must be a virtual breakthrough for these boys! :laugh:
You're so helpful here famewolf. I've both appreciated and have been comforted by seeing your knowledge all over this subforum, since day 1. Please provide help. You tell me where this 'people' person is, and I'll wank on his boner for you. Then we have a definition of 'working fine' in stead of 'worked fine'. ? :angel:
Click to expand...
Click to collapse
The thread that is closed is the one YOU mentioned.... not the op. http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
I dont use mobile Q as I use Linux and they don't have a linux version. I use 3rd party roms such as AICP with the ARDE non OC rom. TWRP puts a log in /tmp...did you look at what the error message says? OTA updates will NOT apply if you have updated system files such as build.prop. Thats all I can tell you because I can't try what you are using.
famewolf said:
The thread that is closed is the one YOU mentioned.... not the op. http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
I dont use mobile Q as I use Linux and they don't have a linux version. I use 3rd party roms such as AICP with the ARDE non OC rom. TWRP puts a log in /tmp...did you look at what the error message says? OTA updates will NOT apply if you have updated system files such as build.prop. Thats all I can tell you because I can't try what you are using.
Click to expand...
Click to collapse
I haven't updated the build.prop, I doubt the OP has either.
'There is no greater software version available to upgrade your phone,actual version of your phone is the latest'
Hehe! Only thing that would make this funnier is if they misspelled 'version'. At least I can derive some amusement from that message and their ****ty, convoluted website.
Shame you can't help on that front, but maybe you can at least guide me on what should be normal flow of this procedure.
When one does OTA update unrooted (but with custom recovery), at the point that the phone reboots, it should not (in theory) boot into TWRP right? I would think just continue with update, and maybe that's why I would need to remove TWRP in favor of stock recovery.
It would be easier to attack it from that angle as opposed to their crappy win32 program. which they probably didn't pay the GoDaddy bill on.:laugh:
I don't even know why I'm bothering as it's just a backup phone now. I just find it ridiculous that I can get their last measly update either from Q or from device (ostensibly so long as custom recovery remains). Holy bejebus, updating Shamu is so painless (6.0.1)
---------- Post added at 08:41 PM ---------- Previous post was at 08:22 PM ----------
likely they have not updated their server side to to UEN0 from UEA2 for their craptacular tool which would explain that problem.
Curious, did you lose Band 12 with UEN0. I haven't heard anything positive from this most recent update that is giving me a headache to get to. Perhaps it's for naught. They don't even have a changelog do they. Meh... I'm going to forget about it until something notable comes along or maybe even just sell this thing while I might still get over a hundred.
tekka-maki said:
I haven't updated the build.prop, I doubt the OP has either.
'There is no greater software version available to upgrade your phone,actual version of your phone is the latest'
Hehe! Only thing that would make this funnier is if they misspelled 'version'. At least I can derive some amusement from that message and their ****ty, convoluted website.
Shame you can't help on that front, but maybe you can at least guide me on what should be normal flow of this procedure.
When one does OTA update unrooted (but with custom recovery), at the point that the phone reboots, it should not (in theory) boot into TWRP right? I would think just continue with update, and maybe that's why I would need to remove TWRP in favor of stock recovery.
It would be easier to attack it from that angle as opposed to their crappy win32 program. which they probably didn't pay the GoDaddy bill on.:laugh:
I don't even know why I'm bothering as it's just a backup phone now. I just find it ridiculous that I can get their last measly update either from Q or from device (ostensibly so long as custom recovery remains). Holy bejebus, updating Shamu is so painless (6.0.1)
---------- Post added at 08:41 PM ---------- Previous post was at 08:22 PM ----------
likely they have not updated their server side to to UEN0 from UEA2 for their craptacular tool which would explain that problem.
Curious, did you lose Band 12 with UEN0. I haven't heard anything positive from this most recent update that is giving me a headache to get to. Perhaps it's for naught. They don't even have a changelog do they. Meh... I'm going to forget about it until something notable comes along or maybe even just sell this thing while I might still get over a hundred.
Click to expand...
Click to collapse
As I mentioned here: http://forum.xda-developers.com/showpost.php?p=64967202&postcount=4 you CAN install an OTA update with twrp...it will install it just fine however at the completion of the update you will no longer HAVE twrp installed because it will have been overwritten with stock recovery. (it does that at the END) This will be apparent the NEXT time you try to load recovery. Where do you imagine the update is processed? It's processed by the recovery app...it can't be done inside the rom because files would be in use. The last version I ever ran was UER0..was not even aware UEN0 was out. As I indicated, I switched to a rom based on cyanogenmod with some features I wanted...if I was going to switch NOW I'd choose blisspop and it's the one I intend to install the next time I have to do a reinstall. I don't see why you fight on 5.02 when 5.1.1 is available in various flavors and with the ARDE NON OC Kernel is rock steady. If you made full backups of your device (ie dd images of ALL partitions using the Backupall bat file or shell script running around the forum restoring to a previous radio is as simple as reflashing the partition using fastboot commands.
The radio is stored in the "modem" partition fyi.
famewolf said:
As I mentioned here: http://forum.xda-developers.com/showpost.php?p=64967202&postcount=4 you CAN install an OTA update with twrp...it will install it just fine however at the completion of the update you will no longer HAVE twrp installed because it will have been overwritten with stock recovery. (it does that at the END) This will be apparent the NEXT time you try to load recovery. Where do you imagine the update is processed? It's processed by the recovery app...it can't be done inside the rom because files would be in use. The last version I ever ran was UER0..was not even aware UEN0 was out. As I indicated, I switched to a rom based on cyanogenmod with some features I wanted...if I was going to switch NOW I'd choose blisspop and it's the one I intend to install the next time I have to do a reinstall. I don't see why you fight on 5.02 when 5.1.1 is available in various flavors and with the ARDE NON OC Kernel is rock steady. If you made full backups of your device (ie dd images of ALL partitions using the Backupall bat file or shell script running around the forum restoring to a previous radio is as simple as reflashing the partition using fastboot commands.
The radio is stored in the "modem" partition fyi.
Click to expand...
Click to collapse
So where is the latest update to flash with twrp (good dry run for me should a decent upgrade come out that isn't UEN0)? I just went with UER0 posted on yer thread thr with all the megaupload firmwares & flash restored system & boot (after full wipe); as an aside, it took, & I still have TWRP in tact. I'm well aware of your fastboot method & orig backup of ALL partitions. Seemed like a waste of space at the time, still kinda does.
Regarding your rhetorical question, I was referencing Alcatel's w32 Q tool. It seemingly wasn't updated to be keyed in on the latest update either. No wait, it said the same 'no greater version' crap even when I restored the original 6045i US system/boot fw from twrp, lmao
tekka-maki said:
So where is the latest update to flash with twrp (good dry run for me should a decent upgrade come out that isn't UEN0)? I just went with UER0 posted on yer thread thr with all the megaupload firmwares & flash restored system & boot (after full wipe); as an aside, it took, & I still have TWRP in tact. I'm well aware of your fastboot method & orig backup of ALL partitions. Seemed like a waste of space at the time, still kinda does.
Regarding your rhetorical question, I was referencing Alcatel's w32 Q tool. It seemingly wasn't updated to be keyed in on the latest update either. No wait, it said the same 'no greater version' crap even when I restored the original 6045i US system/boot fw from twrp, lmao
Click to expand...
Click to collapse
Why are you assuming I should know where the latest and greatest update for stock should be? Updates are customized based on the rom version you are running at the time you submit a request. I've already stated I'm using a 3rd party rom and using an OS that doesn't allow me to run their software. You consider my recommendations a waste of time so I'll quit making them and continue using my perfectly working device on 5.1.1.
famewolf said:
Why are you assuming I should know where the latest and greatest update for stock should be? Updates are customized based on the rom version you are running at the time you submit a request. I've already stated I'm using a 3rd party rom and using an OS that doesn't allow me to run their software. You consider my recommendations a waste of time so I'll quit making them and continue using my perfectly working device on 5.1.1.
Click to expand...
Click to collapse
Omfg buddy, you said, '... you CAN install an OTA update with twrp' ; all I did was point out that I flashed previous updates (presumably the same way you're talking about), TWRP remained in tact afterward, & asked you to follow through with that point with, you know, the actual update in question here that defies many of your assertions. One of your recommendations is broken (Q), the other is hindsight (full backup) & last (update via TWRP) seemingly not feasible (unless someone were to submit updated /system) . Anyway it's all a moot point now since we're just measuring our junk.
I'm tickled you're running 5.1.1, as you've said repeatedly... I tried it briefly on Shamu & was happy to leave the LP quagmire all together & get to 6.0.1. Sufficed to say, there isn't anything perfect about this device or 5.1.1, which is why I'll leave as is & sell it. :good:
Thanks anyway.