I recently rooted my Galaxy Note 2 (GT-N7100) - following 'High on Android' web site instructions.
Everything went well and I installed Clockwork Mod Recovery (CMR) and I backed up then current ROM successful.
Recently, I got a new update to Gmail so, I decided to backup the ROM again. I ran CMR and I was prompted to name the backup file and I was prompted the phone would reboot and complete the backup.. The result was the phone went into a loop constantly displaying the boot logo.
I overcame the problem by re-rooting the phone using ODIN - the download mode was accessible on the phone.
However I spoke to soon: the phone became increasingly unstable and, it eventual Froze. I tried to do a factory wipe & re-root the phone - That left me in exactly the same position - at the boot logo, dead. I have written an email CMR & High on Android but, they have not replied.
I quickly realised I would have re-flash the phone completely and I sourced the correct files from 'SamsFirmware'.
That's the first question: the file I download was compressed and when it was decompressed it gave me two files;
N7100XXALJ3_N7100OXXALJ4_N7100XXALJ2_HOME.tar.md5 & SS_DL.dll
Q1. Can I run this tar.md5 using ODIN (PDA) function?
Q2. I have read that a file like this need to be further spilt? If so, How?
Q3. If spilt the file into component parts, how will I identify / set up the files to ODIN ?
Mild panic is breaking out here - it's the last time I will ever flash a perfectly working phone again. Any advice or practical instructions you can provide to recovery the situation will be warmly welcomed!
Solved - http://www.lockermike.com/how-tos/a.../unbrick-a-galaxy-note-2-with-stock-firmware/
Thanks for sharing your solution, it's always good to know should anything go wrong. I'm about to flash new custom rom in an attempt to unlock the phone too
Related
Hi all,
I'm new to trying to root the E4GT and I've gotten in a bit of a jam. I don't think I'm completely borked because I can still easily get the phone into download mode or Clockwork recovery, but I'm stuck on what to do next and I want to proceed carefully so I don't accidentally turn this into a hard brick.
Because I'm on Linux, not Windows, after reading up on rooting the E4GT I installed heimdall. It's not the most intuitive program in the world but I eventually worked out rooting it using "heimdall flash --kernel ~/path/to/zImage" where the "zImage" in question belonged to Zedomax v3 as linked from epic4gtouchroot.com. That seemed to work brilliantly as I was able to boot into what appeared to be a reset phone, now with a generic Android boot animation rather than the default Sprint advert, and I had the Superuser app.
From there, I decided to try Strongsteve's Odex blue and I booted into Clockwork. Without even thinking about it I wiped the factory data and cache partition, and then started looking into what I needed to do, only to learn that my external SD was going to be inaccessible from here so I had the .zip file in the wrong place. I proceeded to reboot my phone to set things right but I was shocked when the phone simply appeared to turn off after the (new, rooted) boot animation played. The phone then becomes unresponsive until the battery is pulled, at which point it becomes responsive again.
Because it boots the Samsung logo (with the yellow warning triangle) and part of the boot animation, I have plenty of time to get it into download mode or Clockwork, but I don't know what my next move is. I guess (based on a bad experience with trying to root a Kindle Fire) that this is still recoverable, though. Should I just flash a stock/stock rooted ROM? Reflashing the Zedomax kernel doesn't seem to work like it did before. Has anyone encountered this? Does anyone have a link to a recovery method that should be reliable in this situation? Thanks in advance and please remember LINUX -- i.e., no Odin.
[[ PS - I pretty much described the whole process above, but in case anyone was wondering, let me explicitly state I do not have a working nandroid backup. I only got Clockwork after rooting successfully, and I didn't think wipe data/cache was potentially a brick! :\ ]]
UPDATE: Solved! I was able to successfully flash the zImage from the stock rooted kernel here. Phone is working (and rooted) once again!
I have Cyanogenmod 10.1 (stable) installed; the other day it crashed while I was on Instagram, rebooted itself, and wouldn't go past the spinning circle screen. Tried rebooting it, now it won't go past the screen before that, with the blue Cyanogenmod man and the Samsung logo.
I have TWRP 2.5.0.0 installed with it, which I don't know how is possible being that the file systems are incompatible, so unless I used Odin to install CM10.1, I don't know how I did it without installing Clockworkmod Recovery over TWRP.
I've been trying to fix it for a couple days now (I'm kicking myself for not getting around to posting here sooner). When I go into TWRP it asks me for a password (which I've never set, I assume it's asking me because that's all it knows to do when the file system is incompatible), which I click cancel at every time, and when I try to do just about anything (including installing new ROMs or recoveries from within TWRP) it gets errors when trying to mount any partitions on the device, so I can't change anything on the phone at all.
I've tried re-installing TWRP AND Clockworkmod Recovery with Odin, and they succeed, but when the phone tries to reboot, the screen just turns off and nothing happens, and I have to take the battery out to do anything else.
So right now I'm totally screwed unless I can fix this thing. I'd like to not have to drop 200 on a Nexus 4 after only a year or having this phone I bought brand new, especially with the Nexus 5 already coming out later this year...can somebody help me???
EDIT: I should clarify that I can access recovery and download mode
If you can get into download mode you can flash a stock image to your phone and restart from scratch. Download the proper stock image from here http://forum.xda-developers.com/showthread.php?t=1968625 and flash it in odin.
FoxTrotz said:
If you can get into download mode you can flash a stock image to your phone and restart from scratch. Download the proper stock image from here http://forum.xda-developers.com/showthread.php?t=1968625 and flash it in odin.
Click to expand...
Click to collapse
I should've clarified that I've tried this with a bunch of roms, and it just shows SBA2 in the status box forever. I left it for a full hour before and it never changed.
According to this page http://www.alliance-rom.com/community/wiki/bricked-android/ reformating your external sd card may help. It also links to something I personally have never heard of but apparently this: http://forum.xda-developers.com/showthread.php?p=15330252 can help unbrick any samsung phone that's flashable with odin.
I have been using the i747z ROMs for quite some time and after trying a bunch of other ROMs I always reverted back to theirs. So when their 3.0 version came out with Android 4.3 I installed it, using ClockWorkMod recovery. Right after it installed, CWM displayed a message about the boot loader and to fix it. So I went ahead and did that (Don't really remember what the message was) What I know is that I lost root. Also the phone could not connect to the mobile network, only on Wifi. So this morning, I factory reset the phone again, and attempted to root the phone with Odin with CF-Auto-Root-d2att-d2uc-samsungsghi747 (which I had used when I first rooted the phone). Now the phone doesn't boot past the 2nd samsung logo, it starts out with the Samsung logo with the blue circle around it, then the AT&T Rethink Possible and then the plain white Samsung logo. Also, the LED has a slow blue flicker.
I can get the phone into download mode and I have used Odin to attempt to load the stock firmware and the stock bootloader. But after restarting the phone I can't get past the same screen described above.
I am pretty sure this is not related to the i747z v3.0 ROM but rather something a miss with the order in which things need to start in Android. I have done some reading on that but I am not sure what I need to do to correct this soft brick situation. ( I have googled "soft brick" as well)
Any thoughts would be greatly appreciated!
mozphoto said:
I have been using the i747z ROMs for quite some time and after trying a bunch of other ROMs I always reverted back to theirs. So when their 3.0 version came out with Android 4.3 I installed it, using ClockWorkMod recovery. Right after it installed, CWM displayed a message about the boot loader and to fix it. So I went ahead and did that (Don't really remember what the message was) What I know is that I lost root. Also the phone could not connect to the mobile network, only on Wifi. So this morning, I factory reset the phone again, and attempted to root the phone with Odin with CF-Auto-Root-d2att-d2uc-samsungsghi747 (which I had used when I first rooted the phone). Now the phone doesn't boot past the 2nd samsung logo, it starts out with the Samsung logo with the blue circle around it, then the AT&T Rethink Possible and then the plain white Samsung logo. Also, the LED has a slow blue flicker.
I can get the phone into download mode and I have used Odin to attempt to load the stock firmware and the stock bootloader. But after restarting the phone I can't get past the same screen described above.
I am pretty sure this is not related to the i747z v3.0 ROM but rather something a miss with the order in which things need to start in Android. I have done some reading on that but I am not sure what I need to do to correct this soft brick situation. ( I have googled "soft brick" as well)
Any thoughts would be greatly appreciated!
Click to expand...
Click to collapse
After flashing through odin did you format data?If not try it.
Go into recovery and wipe data.
**SOLVED**
Thanks xXFl4sh, I had tried that.
Solved!
Alright where do I start? How about RTFM Some how I had missed the part about flashing a bootloader and a modem after the ROM. Not recalling having to do that before, I skipped right over it. Once the recovery CWM 6.0.3.1 was finally loaded, getting the flashing the ROM, the bootloader and the modem was easy as usual.
The key was having to use Odin to install a recovery in .tar or .tar.md5 format since I could not access a Recovery Mode on the GS3, as well as a rooted stock image (I used root66_ATT_I747UCDLK3.tar.md5 which is a rooted Android 4.1.1 for AT&T) For the recovery, I couldnt' find a .tar or .tar.md5 for ClockWorkMod (did find a utility to convert it, but didn't want to introduce another variable into the mix) so I used one from Team Win Recovery (v2.6.3.0) and with that I loaded the CWM recovery. Once all of that was in place, I proceed to factory reset, clear data, cache, system and then flash the new ROM, bootloader and modem.
In all of this I learned quite a bit about the whole process and how to narrow down possible resolutions. I still see the "Rom may flash stock recovery on boot" message after flashing either a ROM, bootloader or modem, but just backing out without answering Yes or No seems to work. Also (and this may be related, I don't see the option to restart in recovery from shutdown menu). Don't really know what that's all about for now, and honestly don't want to mess around (at least for a while)
I know the steps are general, but I hope this can help some else if they get their devices in a soft brick situation. As for the i747z v3 ROM with 4.3, I really like it, everything works (Wifi,Blutooth,tethering) and the battery seems good as well.
Thanks!
[Q] T-mobile galaxy s2 t-989 stuck on Samsung logo when boot.how unbrick & keep data
Hi,
my t989 suddenly went into so called bootloop actually the phone stuck on Samsung logo after it passed t mobile & android screen. Currently the phone is running stock JB.
Some history about the phone, the phone is a little bit weird when it was running ICS so I decide to update to JB and it seems the problem is fixed but creates some other minor problem. (such as google search widget keeps on complaining no network.) About 32weeks ago When the phone battery is low, I swapped a fully charged backup battery, then soft brick just happened.
What I wanted to do is to preserve the phone data or extract it out before do a clean wipe or use Odin to recover.
By searching and reading all the forums that I have tried few things. At least I know that
Phone can boot to
Recovery
Download mode
Also I can use ADB to reboot the phone
adb recovery
adb reboot
but when I try to extract the data by using ADB pull didn't seem working well? (wrong directory, I assume)
Is there a way to do Nand backup at this state? (by forcing cwm and make the phone to have custom recovery)
If I use Odin to flash the stock room. What will happen? Data got wiped?
when I was searching around and I got impression that if I flash the kernel might fix the problem? But what kernel I should be using? ( I know I need the kernel that's designed for this OS but needs links or pointers)
Thanks for any help, I am out of country right now, desperately need to extract info out of the phone (the stupid phone die before I board the plane)
OH, one more thing... I thought the Odin is the newest one the better but after reading different forums and discussion that my impression is each Odin is design to fit different version of Android OS?? is that right ? need some more pointers
Thanks again
I might have posted this on the wrong thread sorry:
Hello everyone,
Welcome to a series of unfortunate noob events;
All I wanted was to set my default storage to SD, since my Samsung Note 8 GT-N5120 only had 16 gb of internal memory.
I am aware that with my device, I can move apps to SD, but only a part of it gets moved, a huge chunk still stays in the internal memory (i.e 60 mb of an app goes to sd and 100mb of an app stays in memory).
So I searched online and all signs lead to rooting, in order to tweak my device to its fullest ;therefore, making the feature I want available at my disposal. And so I did, I followed tutorials correctly, from usb debugging mode to using odin. SuperSU was there and I downloaded Root Checker just to verify.
My device was working perfectly, but during bootup instead of a screen that shows the android with a pirate patch, it shows a static white screen before going into the samsung logo screen. I've searched through the forums and found out that other GT-N5120 owners had the same problem as well. It was no big deal and I didn't mind.
After that I searched online on things to do after rooting my device. It says install a CWM for better recovery options than what the stock recovery offers, so I did I used this tutorial: droidviews.com/root-and-install-cwm-on-samsung-galaxy-note-8-0-gt-n5100-gt-n5110-gt-n5120-all-models/
Everything was fine and I thought I was getting the hang of this thing, so I moved on to the next step and downloaded ROM Manager, to use a Custom ROM, I used this tutorial: androidtipsz.com/how-to-install-a-custom-rom-on-your-android-phone-using-rom-manager
This part got hazy,
ROM Manager asked me what version of CWM I am using and the options were: 2.0 or 5.x+, I picked the latter
and I was all set,I just needed a Custom ROM to use I picked Paranoid Android. Went to their site downloaded the .zip file that corresponds to my device and used ROM Manager to flash Paranoid Android, but it got to a screen that says my .zip file is for GT-N5120 your device is GT-N5110, which was weird because anywhere I checked on the device (including ROM manager, except when it gets to the said screen) says my device is GT-N5120.
This where the unorthodox noob of myself comes in:
Without hesitation I downloaded the Paranoid Android .zip for GT-N5110 and flashed it with ROM Manager. It worked, the tab still boots and Paranoid Android is running, but the tab got laggy and Google Store stopped running and Email stopped running and because of that, no games would work. SuperSU and ROM Manger didn't open too, I forgot the message tho. Keep in mind I did all this WITHOUT BACKING UP MY FILES igotrektnub
I looked everywhere for a solution to revert without deleting all my files, Ive decided to download the Stock Rom for GT-N5120, the only problem was there were GT-N5120 Stock Roms from different regions, I think that my tablet was from the Sweden Region so I went ahead and downloaded that.
Question#1
Should the Stock Rom I use be region specific? If so how would I check which region my device came from?
So I went to Odin Mode again and flashed this MD5 file:N5120XXDNE4_N5120AUTDNF1_N5120XXDNE4_HOME.tar
it was ok but it got stuck on system.img for a good 2 hours or so? So I did the unthinkable, turn off the device...
After that every time I turn on my device it just boots to the white static screen and never gets past it, I can still go to download mode and recovery mode, but thats about it. I think my recovery mode went back to stock. I tried flashing the root files CF_Auto but it didnt do anything, the same for the CWM, I went into recovery mode factory reset and data wipe and cache wipe, but it still wont get pass the static white screen.
Please help, Ive read somewhere that as long as it still boots download mode, it can still be fixed.
Sincerely,
Nubdatgotrektbyhimself
Please help, I think I made an unusual mistake, all I want is to be able to use the tab again
Could I flash something to make this work again?
Ok so I got it fixed
1. I downloaded a stock rom 4.4.2 from sammobile, its region is unknown and the .md5 file has this name: N5120XWDNE3_N5120OJVDNE3_N5120XXDNE4_HOME.tar
2. Went into download mode flashed it with odin and got stuck at cache.img (passes the cruel system.img)
3. Turned off my device and went into download mode again, flashed this file: CF-Auto-Root-konalte-konaltexx-gtn5120.tar
And now its working again.
*Note: while extracting the .rar file from sammobile make sure you extract .md5 and .dll into the same folder before proceeding with odin.
the noob managed to revert
gtn5120getrektnub said:
Ok so I got it fixed
1. I downloaded a stock rom 4.4.2 from sammobile, its region is unknown and the .md5 file has this name: N5120XWDNE3_N5120OJVDNE3_N5120XXDNE4_HOME.tar
2. Went into download mode flashed it with odin and got stuck at cache.img (passes the cruel system.img)
3. Turned off my device and went into download mode again, flashed this file: CF-Auto-Root-konalte-konaltexx-gtn5120.tar
And now its working again.
*Note: while extracting the .rar file from sammobile make sure you extract .md5 and .dll into the same folder before proceeding with odin.
the noob managed to revert
Click to expand...
Click to collapse
Hey man, glad you got it sorted out. Just saw this now, otherwise I would have tried to help you sooner. Anyways, yes as long as you can get to download mode then you can always Odin flash the proper official firmware for your specific device from sammobile.com. That gets you back to normal every time. Now that you're up and running, you can root, install CWM recovery, then boot to recovery and make a backup. Now wipe cache and dalvik (note: if you want to "clean" flash instead of "dirty" flash, then also wipe system and data), and then flash a compatible custom rom (that you've previously downloaded to your device) through recovery. Reboot once it's done installing.
If something goes wrong then you can simply reboot to recovery and restore your backup. Always make a fresh backup before flashing a new rom, mod, etc, because restoring a backup is easier than having to Odin official firmware and start over from scratch.
Cheers