Hello, I have problem with CWM, i have rooted Galaxy Ace 2, then i wanted to update recovery to CWM 6.0.4.5. but my Odin Failed in conection. I decided to unplug phone and then i realised that i see only statement "Firmware upgrade encountered an issue. Please select recovery mode in kies & try again" (I could go only in Download mode). After long time i found a bit older CWM, 5.x.x it worked but it doesnt support kitkat. I wanted to update it from SDcard to 6.0.4.5, it has beed installed successful but when i reboot it again to recovery it was still same old version.
I have done the same things with my galaxy mini 2 in the same way and i didnt have any problem with it (kitkat works there propely).
Could you help me to fix it? what should i do, i heard that i should install JB via Odin then root again and update CWM but im not sure about it.
Thanks Athery
Related
I recently rooted my galaxy tab 2 P3110 with Odin and CWM recovery 6011 and i seemed to have wiped the stock android os as i cannot boot into it anymote - the Tablet automically boots into CWM all the time
Then when i try to install Slimrom or CM installer to flash and install a new OS but i getting an error 7 - unverified file so i cannot put any Os back on the device
Can anyone help?
Sounds like you flashed the wrong recovery, possible that you installed the p3100 recovery.
Try reflashing the recovery.
miksol said:
I recently rooted my galaxy tab 2 P3110 with Odin and CWM recovery 6011 and i seemed to have wiped the stock android os as i cannot boot into it anymote - the Tablet automically boots into CWM all the time
Then when i try to install Slimrom or CM installer to flash and install a new OS but i getting an error 7 - unverified file so i cannot put any Os back on the device
Can anyone help?
Click to expand...
Click to collapse
Flashing KK ROMs on outdated recovery will get you a status 7 error. Grab the latest (I'd go with TWRP as CWM support will be ending soon) version from here...http://forum.xda-developers.com/showthread.php?t=2548257 update to the latest one you like (CWM is 6.0.5.0) Load up a ROM and give it a go. I put all my ROMs on an external card to be safe. Maybe do that and then just install from such.
p,s. CM installer never works, I dont think our tabs are compatible with it. At least I've never got it to work.But, you dont need it anyways.
I really need some help with my Note 10.1 Wi-Fi (N8010). I'll try to give as much detail here as I can in the hope that some of you experts will be able to help me out!
I was previously running this rom http://forum.xda-developers.com/showthread.php?t=2119547 based on N8000XXCML2 (Android 4.1.2) and I saw that Kitkat was available for my device so I thought I check it out. Now this is where the problems started...
I saw this page http://forum.xda-developers.com/showthread.php?t=2792979 and downloaded and installed the rom from sammobile (N8010XXUDNE4, stock 4.4.2), then rooted with the link on that page.
When I booted I tried to install superSU from the play store and when I ran it, i tried to install the binaries as usual choosing "normal" mode and it told me that KNOX was detected and would I like to disable it? NB: This was the first I'd ever heard of KNOX. Choosing yes didn't work so I tried reflashing the rom again and rooting again with the CF auto root and tada... it worked.
So now I was successfully running rooted, stock 4.4.2 on my N8010.
After a few days however, my keyboard disappeared! When ever I tried to go to a text input field the keyboard just wouldn't appear. I tried installing another keyboard and nothing. So I came back to xda and found Gnabo Rom V6 (http://forum.xda-developers.com/showthread.php?t=2762418).
I followed the instructions and was up and running again. Then after reinstalling all my apps from the play store I tried to install the Xposed framework and when I tried to reboot it was just stuck on the Samsung logo. I tried rebooting again and just leaving it but after about 8 hours it was still stuck on the logo.
Since that, I've managed to flash a stock 4.0.4 firmware with an N8010 PIT file and the device can boot but as soon as I try to flash another rom it just hangs on boot.
If i put the device into download mode (with the bootable 4.0.4 firmware) i see the following.
ODON MODE (red text)
PRODUCT NAME: GT-N8010
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
RP SWREV: A2 (grey text)
I've tried restoring Nandroid backups of my orignal rom and the Gnabo V6 rom but nothing works.
Now if I try to flash N8010XXUCMG1 (stock 4.1.2) from Sammobile Odin fails and on the download mode screen on my device an extra line in red appears saying "SW REV. Invalid magic string". If I reboot into download mode again that line is gone.
Does the RP SWREV line mean I have KNOX on my device?
I just want to get back to my original state (custom 4.1.2) as the 4.0.4 stock rom doesn't seem to see my external SD card (64gb Sandisk) so any suggestions would be much appreciated!
I think it's because you have a kit Kat boot loader and it won't let you downgrade to jelly bean. You could flash kit Kat through Odin and see if it works. And if your sd isn't formatted as fat32 try changing that. But I highly suggest that you wait till someone else confirms everything.
chrismin13 said:
I think it's because you have a kit Kat boot loader and it won't let you downgrade to jelly bean. You could flash kit Kat through Odin and see if it works. And if your sd isn't formatted as fat32 try changing that. But I highly suggest that you wait till someone else confirms everything.
Click to expand...
Click to collapse
I've already tried re-flashing KitKat (N8010XXUDNE4, stock 4.4.2) but its just the same as flashing any other rom; shows the samsung logo and plays the little jingle but then just stays there with the logo fading in and out.
If anyone's interested I've managed to fix it myself in the end. Turns out it was a corrupt efs partition and the Nandroid restore was ignoring the efs.tar.gz file. I never thought the efs partition was important for my tab because its wifi only.
Hi, I have the same problem. Can you describe how fixed it?
polzavotel said:
Hi, I have the same problem. Can you describe how fixed it?
Click to expand...
Click to collapse
Hi,
I tried so many things and I'm no expert so i can't be sure exactly what fixed it but here's what I think did the trick...
I first managed to get into the terminal from recovery mode using Aroma Filemanager http://forum.xda-developers.com/showthread.php?t=1646108
Then I found these 2 commands to run (sorry I don't remember which thread they were from)
mke2fs / dev/block/mmcblk0p3
mount-w-t ext4 / dev/block/mmcblk0p3 / efs
Then after that I was able to restore my old EFS backup. It was in .tar.gz format from an old Nandroid backup and not .img so I had to mandually copy the files over then change the permisions. This thread was useful for that http://forum.xda-developers.com/showthread.php?t=1089039
And this thread for how to remove the "Factory Mode"
http://forum.xda-developers.com/showthread.php?t=1089039
Hope that helps you!
hi all, I'm trying to upgrade to KK with a stock/official fw; linky via odin 3.07. I am able to flash successfully, the tablet restarts and then just sits at the Samsung "blue oval thing"
I've tried TWRP touch 2.8.0.1 to install Gnabo 6.5, following instructions of Here, using "Installation for N801x". All has gone as expected until I tried to install the bootloader section, TWRP crashes to bootloop each time.
I've tried re-downloading the bootloader as well as clean flash of KK and using CWM touch 6.0.3.6 in place of TWRP; same result.
I have a backup of 4.0.something, but i want 4.4.2. Any suggestions are welcomed, TIA.
check bootlader version
daniel302010 said:
hi all, I'm trying to upgrade to KK with a stock/official fw; linky via odin 3.07. I am able to flash successfully, the tablet restarts and then just sits at the Samsung "blue oval thing"
I've tried TWRP touch 2.8.0.1 to install Gnabo 6.5, following instructions of Here, using "Installation for N801x". All has gone as expected until I tried to install the bootloader section, TWRP crashes to bootloop each time.
I've tried re-downloading the bootloader as well as clean flash of KK and using CWM touch 6.0.3.6 in place of TWRP; same result.
I have a backup of 4.0.something, but i want 4.4.2. Any suggestions are welcomed, TIA.
Click to expand...
Click to collapse
Did you flash the Leaked n8000 firmware that Changes the Boot-Loader to the knox boot-loader. If so i think you have to flash a 4.4.2 zip with Mobile odin as it does not do a Boot loader check. There are several threads about 8010 Devices STUCK Into using the n8000 firmware only. Then you have to apply the no cell and wifi fix patches. I do not have a 8010 mine is 8013 so i do not have this issue and have not read totally up on it. It just seems this could be your Trouble.
Good Luck
Thanks Erica_Renee,
I've read about this issue in a few threads, I didn't feel it affected me as my bootloader screen
View attachment 2968202
doesn't show anything about Knox.
but, as I'm short on options; why not. So you're saying go back to 4.0.whatever, install mobile odin and flash KK N8010 rather than through odin on desktop?
problem with up rom
Hi guys,
Please help me
last time i used N8013 with revolution hd 10.1, till now i tried up new rom on xda but it's not working, its was hand up at samsung logo, and then i tried re setup CMR Download HighOnAndroid v1 ClockworkMod Recovery 6.0.1.1 and then re up rom revolution again, but it till stop at samsung logo, then i find one rom stock on samfirmware KIES_HOME_N8013UEALI3_N8013XARALI3_1081475_REV00_u ser_low_ship.tar but its has a problem ( factory mode has unabale working) and auto turn off wifi, so i dont know how to turn back my best tab before.
Thanks
I have a Samsung galaxy Tab2 p3100,
Few dayz back I tried to install a custom rom in it thru CWM, but it was unsuccessfull.
Then I installed back that stock rom that I had backup.
Then I formatted my tab few times.
Then it shows some errorr;!!.
Then I used my phone, but when I opened SuperSU,
It is showing "There is no SU binary installed,and SuperSU cannot install it,This is a problem"
So I flashed again that rooting file thru odin 3 times,
but still itz showing the same error.
So Dev's I kindly request u guyz to provide any solution to this problem.
Its really freaking me out .
Plzzz help me Guyszz....
You may need to flash a stock firmware, something may be borked in system, by updating your firmware and updating your custom recovery it will probably fix issue . After wards root update binary again and flash roms.
Pp.
any other solutions Bro
If something is borked due to a bad flash or bad or wrong download the only way to fix it is to reflash original stock firmware in order to fix it. You then start all over again.
I keep a folder on my pc with all the stuff I need incase this happens.
Pp.
Flash a custom recovery. Download latest SuperSU zip from SuperSu thread and flash in recovery
Send from OnePlus One using Tapatalk
Hey XDA Devs,
I have an old S2 on which I was trying to downgrade Android from CM12.1 to CM11.
CM12.1 had somehow installed it's own recovery console; using which I couldn't have flashed CM11, so for installing CM11 I tried to flash "CWM-KitKatCompatible-i9100" using ODIN 1.85.
The flash completed successfully but then my phone died. It doesn't even get into download mode or recovery mode anymore.
Also, while installing CWM, I flashed the PIT file "omap4_all_20110627_emmc.pit" as it was instructed on http://forum.xda-developers.com/galaxy-s2/general/how-to-root-install-cwm-recovery-flash-t1814801.
Is there any way to revive my phone?
I've already tried jig, even that doesn't work.
I need to get some data from my phone. Even if that's possible somehow?
Thanks,
- V
Hello Dear ,
If ur device get to booted to downloading mode i suggest u to flash stock rom with factory fw through odin here is 2 link for that rom
4.0.3
http://www.mediafire.com/download/etttzxwacsv3dg8/Galaxy+S2+i9100+Full+Factory+Rom+4.0.3.docx
4.1.2
https://mega.nz/#!LEF1AYqB!lMr2S90aZY_MChswC2pLdX4Zva11K6WVG9_WA8yNdNg
For how to flash it here some screenshots ,
https://www.google.com/search?q=how...ved=0ahUKEwj1696-mb_JAhWENxQKHVkTAb0Q_AUICCgE
Last chance for u if this not working for u then only one way 100% it's should work its via box like z3x box on any service center near u ok ..
Hope this will help You,
Thank You ,