Related
Hey ive been trying to root my evo all day it is on version 2.1-update1. I was able to root my brothers perfectly fine using the downloads and tutorial from the idiot-proof guide to rooting by thebiles. But on mine I get stuck right at the beginning, when i try to flash the PC36IMG my bootloader says main version older. I feel like ive tried everything if anyone can help I'd reallly appreciate it thanks.
Try simple root, and keep trying. I got that same error even with simple root on my buddies 3 times before it worked. Don't know why. Maybe try copying the pc36img to the sd card instead of letting simple root push it...gl!
I agree with the simple root approach. Not trying to highjack your post but I have a question back at you if I may. You say you have one root EVO and one not root? If so the the root has PRI 1.34 and the nonroot 1.40? Could you perhaps do a data speed comparison on these and post the results? I am real curious...
sorry man i saw your post like 2 minutes too late the simpleroot worked right before i refreshed this page thanks for the help though guys appreciate it
one more quick question while PC36IMG was flashing the 2nd "tp" file said bypassed next to it rather than OK like all the others and the first tp had a blank next to it...is this a problem i should look into before unlocking the nand and all that other good stuff?
No problem glad you got it working. This was kinda like going to the casino...getting up to go to the bathroom...coming back to see someone hit the jackpot on your machine....hahaha!!!
That is normal....mine did that.
thanks man appreciate it...one more question for anyone that can help, im using the idiot proof guide and im on step 56 but when i try to enter the adb shell i get an error from command prompt saying "error: more than one device and emulator" i entered the shell perfectly fine like 2 steps before that and used it to flash the new pc36img rom but now i get this error to enter shell again how do i fix this error?
Okay I came here thinking this might finally be it... but nope I tried all the solutions mentioned here but to no avail. I am frustrated and still getting the main version is older. Does anyone know what is causing this error. Please I'm using usb debugging I wiped and backed my SD and have ota that came out in June. I installed Microsoft net frame and htc drivers. I updated simple root and the update log said this was to fix the error but still getting the same error. Any suggestions
I have the same issue, pretty much have tried everything with no luck, kind bummed at the moment, hope someone can help
Thanks
I got to work FINALLY!!!!!
So finally i got the main version error older NO MORE. So i decided to share what i did in hopes that it will work for all of you frustrated out there.
1) Download simple root from xda forum, dont download it anywhere else. The first time i tried i downloaded it at another android forum and even though it may seem the same, this version for some reason was not pushing the files as it suppose to. So again download from forum. Search for it on XDA.
2) Be patient and prepare yourself.
3) Make sure you on the 147 ota version. Not froyo. or before any version before ota because you can use old simple root.
4) After you download it extract it to a folder. Choose whatever location suits you i like desktop so i can delete file after i use it and keep zip. Be sure to update the program. Open it and let it search for downlaod or go to root folder and search for the updater.
5) Before running the program check the obvious. Is usb debugging enable, Do i have microsoft netframe, Are my phone drivers correct. Is the usb cable correctly connected to my computer and phone. Did i choose charge only when connected to the computer.
6) Now on your phone, and this step did it for me, go to Settings>SDandPhoneStorage>FactoryDataReset. Brace yourself this will wipe data it will not change your version. But if you want do a backup the folder of your contacts and whatever you have in your SD card, this is the time to do so. Mount as disk drive, and remember to change back to CHARGE ONLY. I skipped this because rooting was more important than my girlfriends phone number.
7) Now youre noobiness is ready connect phone double check Step 5. In case you missed something.
8) Run the simple root downloaded from XDA forum. Wait for it to push files is wont take long but me patient. Think of it passing 180mb to sd card so it takes some time.
9) Phone will reboot in a screen with skating androids Push power button and WAIT. It will find file and you shouldnt be getting "main version older" reboot error you where getting if you paid close attention to detail. Now update push volume up.
10) Why so impatient wait for it to update files. Once its down just push volume up for reboot. First time it reboots after root or when u flash a rom it usually takes longer, enough to get u nervous but dont be WAIT.
11) Easy sailing now but youre not done yet. Hit recovery once your phone reboot. Choose the method you want i chose Clockwork it works just fine for flashing roms.
12) Congrats your fully root and can flash that cool rom youve been reading about. Suggestions: DamageControl or Cyanogen but go ahead and try whichever you like.
13) YOURE DONE WOOF
If for some reason, it happened to me with AvaFroyo, when you flash your rom it goes on a loop and keeps rebooting dont panic that is what the recovery is for just put your microSD on a card reader delete the rom that is giving you problem and place another one and Reflash. Read how to flash rom you have to wipe on Recovery menu everytime you flash a different rom.
I hope this helps...Its in plain english not Dev English so...
Thanks for taking an interest in my problem and trying to help.
Here's what I've figured out. I tried doing Toast's root method for linux and the directions weren't idiot proof because I screwed them up. I've explained how far I've gotten in other threads. If that's relevant just ask and I'll explain exactly what I did.
Anyway my phone does the basics. It allows me to make phone calls, text, and look at the internet on the phone so this isn't an emergency but it I am worse off than I was before I tried to root because I can no longer use easytether.
I had no problem with easytether prior to the root attempt, and it still works when I hook it up with my wifes untampered evo. with my phone but with my wife's evo, I've never messed with that one, I have no trouble connecting with easy tether.
Some of the things I've noticed about the device since the attmept...
-I can't update to 2.2 via the OTA or any other method, my device says no updates are available.
-Simple root wasn't so simple, the phone never shut off and rebooted into boot screen like the red screen said it would in step 1.
How do I reset the device to the way it was the day it was purchased. I've got everything I need backed up. I'm ready to reset just tell me how.
Thanks.
Please?
I know it bothers people here when they think someone didn't research anything first but I really did. The problem was I'm on linux so most of the stuff I researched didn't seem to apply, not to mention I'm quite illiterate in the terminal... but working on it. I'd really like to get this phone back to stock so I can try again.
Can anyone help?
what ROM are you running? base on eclair 2.1 or froyo 2.2..
try this http://shipped-roms.com/index.php?category=android&model=Supersonic
They are the Stock Unmodified ROMs for your EVO 4G the first 3 are Eclair (2.1) and the last 2 are Froyo (2.2)
Just know that if you use any of this you will LOSE Root..
Hope it helps..
I recomend you try 1.47.651.1 first ...
Good Luck
hortstu said:
Thanks for taking an interest in my problem and trying to help.
Here's what I've figured out. I tried doing Toast's root method for linux and the directions weren't idiot proof because I screwed them up. I've explained how far I've gotten in other threads. If that's relevant just ask and I'll explain exactly what I did.
Anyway my phone does the basics. It allows me to make phone calls, text, and look at the internet on the phone so this isn't an emergency but it I am worse off than I was before I tried to root because I can no longer use easytether.
I had no problem with easytether prior to the root attempt, and it still works when I hook it up with my wifes untampered evo. with my phone but with my wife's evo, I've never messed with that one, I have no trouble connecting with easy tether.
Some of the things I've noticed about the device since the attmept...
-I can't update to 2.2 via the OTA or any other method, my device says no updates are available.
-Simple root wasn't so simple, the phone never shut off and rebooted into boot screen like the red screen said it would in step 1.
How do I reset the device to the way it was the day it was purchased. I've got everything I need backed up. I'm ready to reset just tell me how.
Thanks.
Click to expand...
Click to collapse
I bet a friend told you about root without giving you all the details, right? Haha. Ok, back to business. Rooting will make it impossible to receive ota updates. This is not a problem, because devs post rooted ota updates that you can flash manually. As far as I know, root is 100% permanent, but you don't know the goods. First of all, search wireless tether root in market it should have a green wifi icon. Second, try some custom roms and themes. I bet you will cry when you see yourself asking to go back to stock....
jadehawk said:
what ROM are you running? base on eclair 2.1 or froyo 2.2..
try this http://shipped-roms.com/index.php?category=android&model=Supersonic
They are the Stock Unmodified ROMs for your EVO 4G the first 3 are Eclair (2.1) and the last 2 are Froyo (2.2)
Just know that if you use any of this you will LOSE Root..
Hope it helps..
I recomend you try 1.47.651.1 first ...
Good Luck
Click to expand...
Click to collapse
I never got to the point where I could flash a ROM or got root. S was never off.
just in case it makes a difference.
firmware= 2.1-update1
baseband version= 1.39.00.04.26
kernel version= 2.6.29-a2443432
build#= 1.32.651.1 CL171253 test-keys
software#= 1.32.651.1
I think the rest is up to date.
I bet a friend told you about root without giving you all the details, right? Haha.
Click to expand...
Click to collapse
Actually I'm a bit of a forum junkie and as soon as I got this phone I found the android forums and have spent a ton of time there trying to maximize the utility of this device. I've done the opposite.
Ok, back to business. Rooting will make it impossible to receive ota updates. This is not a problem, because devs post rooted ota updates that you can flash manually. As far as I know, root is 100% permanent, but you don't know the goods. First of all, search wireless tether root in market it should have a green wifi icon. Second, try some custom roms and themes. I bet you will cry when you see yourself asking to go back to stock....
Click to expand...
Click to collapse
I only want to go back to stock so I can get rooted! I can't root because I can't get 2.2 so I can't use unrevoked 3.21. I can't use simple because of some problem I had with the toast linux method that seems to be screwing up everything since. I appreciate the input I hope I've explained myself better.
hortstu said:
Please?
I know it bothers people here when they think someone didn't research anything first but I really did. The problem was I'm on linux so most of the stuff I researched didn't seem to apply, not to mention I'm quite illiterate in the terminal... but working on it. I'd really like to get this phone back to stock so I can try again.
Can anyone help?
Click to expand...
Click to collapse
Use this to go back to stock: http://forum.xda-developers.com/showthread.php?t=780141
grouse130 said:
Use this to go back to stock: http://forum.xda-developers.com/showthread.php?t=780141
Click to expand...
Click to collapse
The problem is I don't think I'm rooted.I flashed pc36img.zip and never made it any further. Am I rooted. Do I need to undo this or can I do a hard reset?
grouse130 said:
Use this to go back to stock: http://forum.xda-developers.com/showthread.php?t=780141
Click to expand...
Click to collapse
OK so here's why I think I'm not rooted, when I follow step one of the detailed directions,
Power off the phone and reboot into the recovery by holding VOL DOWN + POWER until it boots to the white screen. Then select RECOVERY.
Click to expand...
Click to collapse
I get a screen with an evo, a red triangle, and a red exclamation point.
Where do I go from here?
Any direction will be immensely appreciated.
To find out if you're rooted, simply try to run an app that requires root access. Try downloading Titanium back up, and as soon as you install it, hit the "Problem?" button on the lower right and install busybox. One of the first lines on the main screen of the app says:
Root access => OK (Busybox 1.16.0 from app)
If it does not say "root access => OK" and you cannot use the app, then you don't have root.
hortstu said:
OK so here's why I think I'm not rooted, when I follow step one of the detailed directions,
I get a screen with an evo, a red triangle, and a red exclamation point.
Where do I go from here?
Any direction will be immensely appreciated.
Click to expand...
Click to collapse
From this screen, if you hold volume up and press the power key, it will take you to the hboot menu.
Have you flashed a recovery img?
Sent from my PC36100 using XDA App
rugedraw said:
From this screen, if you hold volume up and press the power key, it will take you to the hboot menu.
Click to expand...
Click to collapse
OK so I'm at the "hboot" screen.
Code:
Android system recovery <2e>
Use volume...
click power key...
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
Then in yellow, below the device picture, triangle, and exclamation I have
Code:
E: Can't open /cache/recovery/command
Not sure where you're steering me rugedraw but thanks for the help...
hortstu said:
OK so I'm at the "hboot" screen.
Code:
Android system recovery <2e>
Use volume...
click power key...
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
Then in yellow, below the device picture, triangle, and exclamation I have
Code:
E: Can't open /cache/recovery/command
Not sure where you're steering me rugedraw but thanks for the help...
Click to expand...
Click to collapse
To check if you are rooted. Download "Terminal Emulator" on the market. If it starts up and when it is done booting, you get a # prompt, you are rooted. If you get a $ prompt. You are not rooted.
You also do not have a custom recovery installed on your phone (the recovery screen you have is the stock one). Try finishing up the process by doing Toast part II -- http://forum.xda-developers.com/showthread.php?t=701835&highlight=Part-2
To find out if you're rooted, simply try to run an app that requires root access. Try downloading Titanium back up, and as soon as you install it, hit the "Problem?" button on the lower right and install busybox. One of the first lines on the main screen of the app says:
Root access => OK (Busybox 1.16.0 from app)
If it does not say "root access => OK" and you cannot use the app, then you don't have root.
Click to expand...
Click to collapse
Finally went back and checked on the titanium backup download. When I first opened it I got the message that it didn't have root access. So I clicked on "problems?" and installed busy box. Now it says,
Root access v=> OK (BusyBox 1.16.0 from app
Click to expand...
Click to collapse
Plus some other stuff... so I guess I have root but not S-off.
hecklbrg said:
To check if you are rooted. Download "Terminal Emulator" on the market. If it starts up and when it is done booting, you get a # prompt, you are rooted. If you get a $ prompt. You are not rooted.
Click to expand...
Click to collapse
Should I still do this or is the info from titanium backup enough?
You also do not have a custom recovery installed on your phone (the recovery screen you have is the stock one). Try finishing up the process by doing Toast part II -- http://forum.xda-developers.com/showthread.php?t=701835&highlight=Part-2
Click to expand...
Click to collapse
Yes I tried doing that but like I said I'm on a linux computer and had some trouble with the steps. What I'd really like to do is just go back to stock and try rooting with unrevoked 3.21.
My concern is that selecting factory reset from the hboot screen won't take me back there. If it did I could probably get the 2.2 update over the air, I suppose now I have to worry about getting this other update that everyone is talking about at the same time. Can I get 2.2 and avoid the update that came out last night? How.
Will a factory reset get me back to stock? I've already got everything backed up that matters.
Thanks for all the help.
OK...I think this should work for you:
go here and download the file on the page:
WRONG FILE>>>WILL FIND THE CORRECT ONE.
rename it update.zip and put it on the root of your SD card.
Boot into HBOOT then into recovery and go to apply update.zip -- choose the file you put on there.
let it run and you should have the stock non-rooted version of the 1st software release from sprint. from there you can update it as far as you want to root it the method of your choice.
hecklbrg said:
OK...I think this should work for you:
go here and download the file on the page:
WRONG FILE>>>WILL FIND THE CORRECT ONE.
rename it update.zip and put it on the root of your SD card.
Boot into HBOOT then into recovery and go to apply update.zip -- choose the file you put on there.
let it run and you should have the stock non-rooted version of the 1st software release from sprint. from there you can update it as far as you want to root it the method of your choice.
Click to expand...
Click to collapse
Thanks hecklbrg,
I assume since I'm half rooted a factory reset won't get me there?
I'll wait for the link to that file...
if you put this on your card and run it from HBOOT...you will get a rooted version of the latest sprint OTA with a custom recovery and the latest radios.
http://forum.xda-developers.com/showthread.php?t=791019
I'm still looking for a non-rooted version to run...but I would think this would work for you to get you the latest OTA in a rooted form.
Second thing is that I don't think you really screwed up your root process. You have only done part of the process and haven't installed a custom recovery. If this works for you, it will give you a custom recovery and you will have a fully rooted phone.
Hecklberg is right. I don't think you even need to rename it update.zip. If its a
pc36img.zip your hboot will automatically scan for it, find it and run it when you put it on your SD card and open hboot.
Also consider, I rooted my phone without any computer, all done from my Evo, using fastRX8 thread in here about how to root for newbies. It involves putting the files on your SD card, then installing terminal emulator from the market and typing a few commands to install flash_image, then custom recovery. You are root, just don't have flash image, custom recovery, and superuser yet. Basically toast part 2, it can be done with no computer, but same files.
Read real quick Whitslack thread on rooting, and fastrx8 thread, even just the 1st post, and it will make sense to you where you're at and what's left to do. You'll see how close you are.
Once root, and superuser installed, you won't need easy tether, Android wired tether is what I use (doesn't require installing any software on the host pc)
(Actually, if you use the threads I mentioned method, don't use the recovery amonra1.7.0.2, there's a newer one to download, its at 1.8 now, just Chang the recovery file name you type in terminal app accordingly-don't worry, it won't go thru if you do it wrong, but won't 'break' anything)
Hope any of this helps, but yeah, hecklberg is right too, just different methods. One requires no computer.
And yeah, with the devs around here, you don't need any Sprint OTAs, most of the time, they seem to have em available before Sprint releases them. These guys are good.
scottspa74 and hecklbrg,
Thanks for the help. I havent had time to look at this or act on it over the last 24 hours but I will try to get to it tonight and let you know how it works. Sounds like you've gotten me out of the woods.
Thanks again.
I think it is $ if you are rooted and# if you aren't because I know I'm rooted and it shows money signs, unless terminal emulator is messed up,i have nvr used it.
hecklbrg said:
To check if you are rooted. Download "Terminal Emulator" on the market. If it starts up and when it is done booting, you get a # prompt, you are rooted. If you get a $ prompt. You are not rooted.
You also do not have a custom recovery installed on your phone (the recovery screen you have is the stock one). Try finishing up the process by doing Toast part II -- http://forum.xda-developers.com/showthread.php?t=701835&highlight=Part-2
Click to expand...
Click to collapse
Sent from my netarchy_toast, froyo beast of a machine evo!
evohack99 said:
I think it is $ if you are rooted and# if you aren't because I know I'm rooted and it shows money signs, unless terminal emulator is messed up,i have nvr used it.
Sent from my netarchy_toast, froyo beast of a machine evo!
Click to expand...
Click to collapse
Nope you are incorrect my friend.. try typing " su " on the terminal emulator see if you get the "#" ... # ==> Root and $ ===> User(I Think) But I know for sure "#" is root access
Hello.
So my N7100 doesn't connect to mobile network. No voice calls, text messages or mobile internet. Wifi works just fine, although signal seems to be a little weaker (maybe just my imagination).
What I did and how it happened:
I got sick of Samsung being assholes and not pushing out software updates, so I decided to flash some custom ROM. I choose CM, because they had that "one click installation", so I didn't have to do a lot of work. After a week of using CM I decided that it sucks and wanted back my original android with all gimmicks from Samsung, mostly because battery life with CM was terrible, not even one day. And that's when everything went downhill. I downloaded and installed firmware for Baltic region, because I live here and I bought my phone here. From that moment my phone stopped being phone and evolved into wifi only tablet. After being very pissed and trying to flash couple different roms I gave up. Found my phones original box user manual and other papers. It turns out that my phone is made for Hungary region. So shop where I bought it must have imported wrong models (most likely cheaper for bigger profit). Flashing original for Hungary made firmware doesn't resolve this issue.
Guys, I really need help. I just want to return to stock - original firmware and reset flashing counter. Please help, and if possible in layman's terms...
EddsLV said:
Hello.
So my N7100 doesn't connect to mobile network. No voice calls, text messages or mobile internet. Wifi works just fine, although signal seems to be a little weaker (maybe just my imagination).
What I did and how it happened:
I got sick of Samsung being assholes and not pushing out software updates, so I decided to flash some custom ROM. I choose CM, because they had that "one click installation", so I didn't have to do a lot of work. After a week of using CM I decided that it sucks and wanted back my original android with all gimmicks from Samsung, mostly because battery life with CM was terrible, not even one day. And that's when everything went downhill. I downloaded and installed firmware for Baltic region, because I live here and I bought my phone here. From that moment my phone stopped being phone and evolved into wifi only tablet. After being very pissed and trying to flash couple different roms I gave up. Found my phones original box user manual and other papers. It turns out that my phone is made for Hungary region. So shop where I bought it must have imported wrong models (most likely cheaper for bigger profit). Flashing original for Hungary made firmware doesn't resolve this issue.
Guys, I really need help. I just want to return to stock - original firmware and reset flashing counter. Please help, and if possible in layman's terms...
Click to expand...
Click to collapse
Press *#06# and see if your EMEI is fine... If it says something like 000000000049 it seems to be bugged and you can try this solution:
I flashed the firmware N7100XXDMF2_N7100OLBDMD2_XME using ODIN PC and follow the below using root explorer:
- copy /efs/ to the sdcard
- delete /efs/
- reboot (after reboot I got the yellow recovery mode window floating over, no lock screen, and pressing power button turns the phone off directly)
- /efs/ will be autocreated again. copy the efs folder from the sd card to / (root explorer will tell you that the folder already exists and it will merge them)
- reboot
PS: I did not have an /efs/ backup before applying the above.
Click to expand...
Click to collapse
I saw from another post. Im going to try this too since Im having the same problem as you.
Find your ROM here: http://www.sammobile.com/firmwares/1/?model=GT-N7100&pcode=CHE#firmware I selected Chile Entel, but you can choose your country and company, it is the original ROM and it should fix our problem, Im downloading the ROM by now.
To use Odin, just put your phone in download mode (vol up/down + home + power) and then plug in to your PC, open Odin and at "PDA" select your ROM, then put start and just wait a few minutes and it should be working again...
After this, you should make a back up of your EFS file using a root explorer and then flash with any ROM you want (Im trying Ditto 3, it seems to be a cool jelly bean) and after this flash, you should put your new EFS file... Just the problem that Im facing is how to put this backup since the EFS is a folder being readed all the time, so there should be a program to do this, but I cant figure this out yet.
My phone doesn't have any IMEI any more. "null/null" is value given by my phone after requesting IMEI. I already flashed original ROM, problem is still here.
About /efs/ I could backup it with "File Manager"app from google play, but I can't delete it, because it is in read only.
EddsLV said:
My phone doesn't have any IMEI any more. "null/null" is value given by my phone after requesting IMEI. I already flashed original ROM, problem is still here.
About /efs/ I could backup it with "File Manager"app from google play, but I can't delete it, because it is in read only.
Click to expand...
Click to collapse
Somehow you will have to access to edit it and you will be able to solve that problem... Otherwise go to technical service.
kito2 said:
Somehow you will have to access to edit it and you will be able to solve that problem... Otherwise go to technical service.
Click to expand...
Click to collapse
In order to delete /efs/ you have to be rooted, when you flash factory rom you loose root privileges.
EddsLV said:
In order to delete /efs/ you have to be rooted, when you flash factory rom you loose root privileges.
Click to expand...
Click to collapse
After flash factory rom is easy to make root again hehe.. Anyways keep reading and maybe you will find another solution, you can't be the only one who had that problem... Good luck my friend.
Try this link http://forum.xda-developers.com/showthread.php?t=1896696
kito2 said:
After flash factory rom is easy to make root again hehe.. Anyways keep reading and maybe you will find another solution, you can't be the only one who had that problem... Good luck my friend.
Click to expand...
Click to collapse
Thanks. So I rooted my phone and did all than you wrote above - copied, deleted, replaced. It didn't helped and now I have that yeleow recovery window all the time :/
First of all let me say THANKS to all of the dedicated folks on this website that I have found to be most useful while looking for help.
My problem may have been discussed previously, but after doing much browsing I must not be using the right keywords to find a resolution.
I am having issues with a SGH-i747 running stock 4.3 that I just purchased, so I have no clue what may have been done to it in the past.
So as the title says - The green android while booting into recovery mode just falls over with red triangle, and underneath it flashes - No command - Error - No command.
Also if I do try to flash anything - I get several RED errors in a row basically saying - E: No data folder found and a few other things before it quickly reboots and I can't see what the other errors are.
Would appreciate any ideas you folks may have - Thanks.
TWRP had an Odin flashable .tar. If you need recovery you should be able to just use that or terminal command to install.
Odin Fails Too
BCSC said:
TWRP had an Odin flashable .tar. If you need recovery you should be able to just use that or terminal command to install.
Click to expand...
Click to collapse
This is how I discovered the android falling over issue.
While attempting to install clockworkmod.tar through Odin which will PASS
But then when entering recovery mode I get the stock recovery with green android falling over & data errors.
I have performed this same procedure on my other phone which is identical make and model but starting off with stock 4.1.2 without any issues.
I have also tried flashing philz_touch_6.0.7.9-d2att.tar.md5, but that creates a whole new set for errors & fails.
Deeeno said:
This is how I discovered the android falling over issue.
While attempting to install clockworkmod.tar through Odin which will PASS
But then when entering recovery mode I get the stock recovery with green android falling over & data errors.
I have performed this same procedure on my other phone which is identical make and model but starting off with stock 4.1.2 without any issues.
I have also tried flashing philz_touch_6.0.7.9-d2att.tar.md5, but that creates a whole new set for errors & fails.
Click to expand...
Click to collapse
Push it in Terminal Emulator app. Instructions here. http://forum.xda-developers.com/showthread.php?t=2170635&highlight=recovery+terminal. This forces it top the memory block, so should work. I'm asuming the phone boots and you are rooted.
BCSC said:
Push it in Terminal Emulator app. Instructions here. http://forum.xda-developers.com/showthread.php?t=2170635&highlight=recovery+terminal. This forces it top the memory block, so should work. I'm asuming the phone boots and you are rooted.
Click to expand...
Click to collapse
Boots up just fine & Unlocked, but is not rooted yet - This is why I tried getting clockworkmod.TAR & CWM_SuperUser_v3.0.7 (1).zip flashed.
But my main concern is getting the android falling over issue fixed at the moment, and I think the rest will resolve itself once that's accomplished.
I realize I am no rocket scientist with android phones (Galaxy S3), or I wouldn't be looking through these help forums, and asking for advice.
But it seems to me it's like fixing your car - You need to figure out the root cause of the issue rather than putting band aid patches on it.
Seems like the operating system has other issues to deal with other than obtaining root access at the moment, or it wouldn't keep giving me errors stating that it can't access the DATA files.
Maybe my way of thinking is way off base? Thanks for all your input anyways & I will click the THANKS button if it lets me.
Deeeno said:
Boots up just fine & Unlocked, but is not rooted yet - This is why I tried getting clockworkmod.TAR & CWM_SuperUser_v3.0.7 (1).zip flashed.
But my main concern is getting the android falling over issue fixed at the moment, and I think the rest will resolve itself once that's accomplished.
I realize I am no rocket scientist with android phones (Galaxy S3), or I wouldn't be looking through these help forums, and asking for advice.
But it seems to me it's like fixing your car - You need to figure out the root cause of the issue rather than putting band aid patches on it.
Seems like the operating system has other issues to deal with other than obtaining root access at the moment, or it wouldn't keep giving me errors stating that it can't access the DATA files.
Maybe my way of thinking is way off base? Thanks for all your input anyways & I will click the THANKS button if it lets me.
Click to expand...
Click to collapse
I understand exactly what you mean, but root access can be a key to you here. Your recovery is broken or at least something in a system file is harming what recovery is trying to do. Problem is these are not accessible without root. Root is not the band aid, it's the scalpel Try fixing that car without wrenches. The problem with recovery is that it is protected. You could flash a new stock one as part of an official firmware, but if you are stock 4.3 you are going to run into bootloader issues (nevermind the fact that Samsung hasn't released one. This leaves your other fix as replacing your recovery and requires access to the root system files.
++On another note, I just found this and don't want to delete everything I just typed. See this thread here and see if it pertains to you. http://forum.xda-developers.com/showthread.php?t=2520115
Either you or someone else have already installed a custom recovery. Without root access recovery will fail, the android will fall and you will see red. Use this to root and fix your phone...http://forum.xda-developers.com/showthread.php?t=1963790
Good point on having no wrenches to fix the car --- I will head your advise, and move forward with getting it rooted.
BCSC said:
the android will fall and you will see red. Use this to root and fix your phone...http://forum.xda-developers.com/showthread.php?t=1963790
Click to expand...
Click to collapse
You nailed it on the head - I'll be sure to also hit the Thanks tab for chainfire also since he deserves credit also.
CF Auto Root did the trick and the poor little green android no longer falls over.
Moderators can mark this thread as resolved & Thanks again for all your help.
I have been searching the forum and google and have been unable to reach a solution yet.
I am not a noob, but i am not an expert either so use small words ha.
I have a Samsung Galaxy Tab 3 10.1 5210 with the most recent OTA update.
Last night I attempted to root my device using this:
androidxda (DOT) com/root-samsung-galaxy-tab-3-10-1-gt-p5210
It claimed successful and my device started to reboot and hung up at the Samsung GALAXY TAB 3 screen. I am unable to get to recovery mode on the device. Only able to go to download mode. I have tried several options but have been unable to find a way to flash it successfully. The flashes i have tried downloading were all in .zip and that obviously isn't able to be used in Odin. I have researched how to convert the files into a .tar but I don't have linux. Can someone please help me because I need my tablet. I know it can be saved but I can't seem to locate the answers. I am also getting concerned that it is unable to charge the battery being in the condition it is in now so I am trying to conserve the battery on the tablet until it is absolutely needed. Thanks.
cameron72 said:
I have been searching the forum and google and have been unable to reach a solution yet.
I am not a noob, but i am not an expert either so use small words ha.
I have a Samsung Galaxy Tab 3 10.1 5210 with the most recent OTA update.
Last night I attempted to root my device using this:
androidxda (DOT) com/root-samsung-galaxy-tab-3-10-1-gt-p5210
It claimed successful and my device started to reboot and hung up at the Samsung GALAXY TAB 3 screen. I am unable to get to recovery mode on the device. Only able to go to download mode. I have tried several options but have been unable to find a way to flash it successfully. The flashes i have tried downloading were all in .zip and that obviously isn't able to be used in Odin. I have researched how to convert the files into a .tar but I don't have linux. Can someone please help me because I need my tablet. I know it can be saved but I can't seem to locate the answers. I am also getting concerned that it is unable to charge the battery being in the condition it is in now so I am trying to conserve the battery on the tablet until it is absolutely needed. Thanks.
Click to expand...
Click to collapse
First of all - Welcome to xda
Your tab is soft bricked, something has gone wrong with your system files... Honestly it seems like you know enough to get it done, but are struggling a bit with the file formats. You are correct in saying that Odin won't use zip files, but you shouldn't have to convert anything to tar or download linux! If you extract the zip files, you should find a .tar or .tar.md5 file (inside the zip file) that Odin can use, put it in the PDA mode box, etc etc... If your downloads don't have the correct files inside them, try THIS thread.
Let me know if you get it sorted :good:
bob23bk said:
First of all - Welcome to xda
Your tab is soft bricked, something has gone wrong with your system files... Honestly it seems like you know enough to get it done, but are struggling a bit with the file formats. You are correct in saying that Odin won't use zip files, but you shouldn't have to convert anything to tar or download linux! If you extract the zip files, you should find a .tar or .tar.md5 file (inside the zip file) that Odin can use, put it in the PDA mode box, etc etc... If your downloads don't have the correct files inside them, try THIS thread.
Let me know if you get it sorted :good:
Click to expand...
Click to collapse
I had already tried the method and file in the forum you linked me to. It failed almost instantly. That's when I turned everything off and tossed it all to the back seat of my work truck before it got thrown at the windshield. I keep seeing people saying they have trwp or whatever. I don't even know what that is haven't researched that. Is it something i need as well?
I've never successfully rooted a Samsung device. I used to do this stuff a lot back with the droid x with Linux and everything was pretty simple. Does Samsung change their bootloader with each update like Motorola did then? I was wondering that when trying to install a firmware of a previous version that maybe that was the problem.
All I wanted root for was to just tweak some things and be happy. It has turned into a nightmare.
C,
hi,
the consistent/common thread of this problem is/seems to be taking the ota and trying unverified/gimmicky
root methods.
there are recoveries for the gt-p52xx in the tab 10.1 forum
the majority of samsung devices root as follows;
if a custom recovery exist, flash it.
then download recent or latest version of chainfire's supersu update zip, reboot to recovery
backup your rom first, then flash supersu, if everything goes well, once you have set up your stock rom with root in place
make a new backup.
samsung ota's are death incarnate, reject them.
goto the tab 10 forum and get busy ! you said it yourself, you're not a noob, you know the drill. :good:
m
moonbutt74 said:
C,
hi,
the consistent/common thread of this problem is/seems to be taking the ota and trying unverified/gimmicky
root methods.
there are recoveries for the gt-p52xx in the tab 10.1 forum
the majority of samsung devices root as follows;
if a custom recovery exist, flash it.
then download recent or latest version of chainfire's supersu update zip, reboot to recovery
backup your rom first, then flash supersu, if everything goes well, once you have set up your stock rom with root in place
make a new backup.
samsung ota's are death incarnate, reject them.
goto the tab 10 forum and get busy ! you said it yourself, you're not a noob, you know the drill. :good:
m
Click to expand...
Click to collapse
I have tried the recoveries in the forum and it failed seconds after starting.
I don't do this stuff regularly as I don't hardly have the time. I haven't done anything of this nature in years so I'm well out of the loop on things..
cameron72 said:
I have tried the recoveries in the forum and it failed seconds after starting.
I don't do this stuff regularly as I don't hardly have the time. I haven't done anything of this nature in years so I'm well out of the loop on things..
Click to expand...
Click to collapse
okay, hmm, when you say it fails, do you mean odin fails to flash and if so what is the reason/ouput ?
or do you mean that you are now in a recovery bootloop ?
note- though i go the full route of packing recovery.img's for odin flashing, the md5 checksum always seems to
come up as invalid, the working "remedy" is to remove the .md5 extension from the "odin-flashable-recovery".tar.md5 file
by renaming the file to "odin-flashable-recovery".tar
odin will no longer attempt the checksum verification but the recovery file will flash.
make sure you have samsung-usb-drivers for windows installed. on the main page of my devhost archive [link is in my signature]
you will find the tools you need. the possible problem is that the ota you installed may have overwritten your bootloader, for that i don't
have a reliable fix, so if anything make sure you also have the stock recovery ready to go as well as supersu update zip
already downloaded onto your device for rooting.
after you flash the custom recovery [with auto-restart in odin disabled] run the flash and wait for the res-ok message, give it another second or two then disconnect the tab and force reboot to recovery, home,vol-up and power, once in recovery make a full backup, then flash supersu zip and reboot, if you do go into recovery loop, force reboot to odin mode, home,vol-down and power, follow the on screen instruction, now reconnect your tab to pc and use odin to flash back stock recovery.
m
Okay guys I appreciate the help. I finally got it. I tried the method on Zachisimo's post on unbricking and finally got it installed.
After it installed, it left me with a bootloop and I was actually able to go into recovery mode this time and do a factory data reset and wipe cache then everything went well. I am a happy dude now.
Going to attempt rooting it again and does anyone have any suggestions on what ROM to install? I have never used any custom ROM's before so that is a new area for me. Feeling more confident knowing how to save it from the dead. :good::good::good:
cameron72 said:
Okay guys I appreciate the help. I finally got it. I tried the method on Zachisimo's post on unbricking and finally got it installed.
After it installed, it left me with a bootloop and I was actually able to go into recovery mode this time and do a factory data reset and wipe cache then everything went well. I am a happy dude now.
Going to attempt rooting it again and does anyone have any suggestions on what ROM to install? I have never used any custom ROM's before so that is a new area for me. Feeling more confident knowing how to save it from the dead. :good::good::good:
Click to expand...
Click to collapse
Hi,
Alright !'m glad you got it working, as to roms , all available roms currently are stock modifications , I use cag-rom, there's also pimp-droid
both kitkat.
m
moonbutt74 said:
Hi,
Alright !'m glad you got it working, as to roms , all available roms currently are stock modifications , I use cag-rom, there's also pimp-droid
both kitkat.
m
Click to expand...
Click to collapse
If you use it then thats what i shall try. First i gotta find a root, then I have seen many people recommend philz recovery, and then the rom?
question why does Restl3ss say wait 10minutes after installing a rom before doing anything?
cameron72 said:
If you use it then thats what i shall try. First i gotta find a root, then I have seen many people recommend philz recovery, and then the rom?
question why does Restl3ss say wait 10minutes after installing a rom before doing anything?
Click to expand...
Click to collapse
for root look up supersu update zip
ask Restl3ss :silly:
m
cameron72 said:
Okay guys I appreciate the help. I finally got it. I tried the method on Zachisimo's post on unbricking and finally got it installed.
After it installed, it left me with a bootloop and I was actually able to go into recovery mode this time and do a factory data reset and wipe cache then everything went well. I am a happy dude now.
Going to attempt rooting it again and does anyone have any suggestions on what ROM to install? I have never used any custom ROM's before so that is a new area for me. Feeling more confident knowing how to save it from the dead. :good::good::good:
Click to expand...
Click to collapse
Glad it worked out, recovering from brick does set you free from the stress induced by the disclaimers imo :silly: