[Q] cwm 6.1 for tipo is out, can I use it with my german tipo? - Sony Xperia Miro, Tipo (Dual), J, E

cwm 6.1 for tipo is out. See >>HERE<<
Well, I am unshure to use it.
Will it brick my phone?
My Sony Xperia Tipo is german from Telekom.
- bootloader is locked
- firmware is 11.0.A.0.16
- rooted
Does a locked bootloader block installing CWM or cause trouble in any way?
Are there german users out there who have succesfully installed the mentioned CWM already?

killerhippy said:
cwm 6.1 for tipo is out. See >>HERE<<
Well, I am unshure to use it.
Will it brick my phone?
My Sony Xperia Tipo is german from Telekom.
- bootloader is locked
- firmware is 11.0.A.0.16
- rooted
Does a locked bootloader block installing CWM or cause trouble in any way?
Are there german users out there who have succesfully installed the mentioned CWM already?
Click to expand...
Click to collapse
If you're rooted already, you're good to go.I suggest flashing 4.22 though, it is really noticeably better in performance.You can root that with UnlockRoot, and install CWM/TWRP afterwards, whichever you'd like.

Steam. said:
If you're rooted already, you're good to go.I suggest flashing 4.22 though, it is really noticeably better in performance.You can root that with UnlockRoot, and install CWM/TWRP afterwards, whichever you'd like.
Click to expand...
Click to collapse
Good news. Thank you for your encouraging answer.
As I have so far noticed documentation on this forum, in the case of error doing recover attempts are made with windows software.
I am running linux, if windows is nescessary, does recover software work at a virtual machine running Windows XP with USB piped through? Or is there even linux software to manage that?
And, can you advise a good location I can read and follow instructions in the case of CWM installation problems?
Please excuse my nooby questions, my fone is the very first and only one I could afford and I have no experience so far.
I'd like to prepare as much as I can to avoid having a bricked device asking questions at a lost situation.

Cwm is fine for you take care while flashing a rom though it can cause a mess but dont worry I have been messed up before I got my tipo back running in 17 minuts
I got sollution very quickly and stepwise you are not a noob but I am so just sharing my xperience????
Sent from my ST21i using xda app-developers app

killerhippy said:
Good news. Thank you for your encouraging answer.
As I have so far noticed documentation on this forum, in the case of error doing recover attempts are made with windows software.
I am running linux, if windows is nescessary, does recover software work at a virtual machine running Windows XP with USB piped through? Or is there even linux software to manage that?
And, can you advise a good location I can read and follow instructions in the case of CWM installation problems?
Please excuse my nooby questions, my fone is the very first and only one I could afford and I have no experience so far.
I'd like to prepare as much as I can to avoid having a bricked device asking questions at a lost situation.
Click to expand...
Click to collapse
It's hardly brickable by root procedures, the only thing you could've run into was not getting the files copied to system, but since you're rooted you don't have any probs.Just DL the zip from the CWM thread, extract the files in some folder, connect phone with usb debugging on, and double click the start.bat
it will tell you when it's done, you can press any key to continue.at this point, disconnect the phone from the USB cable, power off, then start it up and tap volume down at the Sony logo.

Steam. said:
It's hardly brickable by root procedures, the only thing you could've run into was not getting the files copied to system, but since you're rooted you don't have any probs.Just DL the zip from the CWM thread, extract the files in some folder, connect phone with usb debugging on, and double click the start.bat
it will tell you when it's done, you can press any key to continue.at this point, disconnect the phone from the USB cable, power off, then start it up and tap volume down at the Sony logo.
Click to expand...
Click to collapse
Success!!!
Thank you so much, tusharkulkarni008 and Steam.
There were no errors at all, though I had to fetch an adb executable first which I checked working with "adb shell".
I successfull opened cwm and did my very first full system and data backup!
Splendid, now I am able to do more exciting things with my fone!
So, I learned, installing CWM is nothing but copying files to system partition. It does not depend on an unlocked bootloader, it just needs a rooted fone.

unlocked BL is only required for flashing a custom kernel, which is required for most custom roms around here, they are all based on FXP release,CM10.

Related

[Q] Tipo Dual Questions (relock, copy fw from another phone)

Hello everyone,
I have learned a lot from these forums and am thankful for everyone's hard work here. I have a Tipo Dual that was originally with firmware 11.0.A.6.5 (ST21a2, not i2). I installed GIMLO, which is generally good, but I have some issues with it (LED doesn't light for E-mail or charge, play store and games crashing, little things like that). The phone is rooted and boot loader is unlocked (all with tools from here!). I did not make a backup of my original system before I flashed (I thought I had, but it is not there, not sure how I failed at that).
I have two questions: I have tried a lot of times to relock my boot loader so I could use SUS or PC Companion to reload the firmware. It won't relock with any of the methods I have found here. Is there a reason for that? I have reloaded a stock firmware, and even then I could not relock boot loader. Anything I should look for to allow this?
I would like to put the a2 firmware back on but the firmware I find here is always the i2 version; I understand the difference is little tweaks in how the phone deals with the GSM network, and as phone connectivity is important to me, I'd like the original a2 version again. My wife has the identical phone (with ST21a2 & 11.0.A.6.5 -- or maybe 11.0.A.8), and she has not done anything to hers. Can I root, make a nandroid backup of her phone, and somehow import/flash that to my phone? I have my contacts backed up, so I'm not worried about that, and I have all my apps, so a clean install would be fine with me. If I can do this, how do I get the backup off of her phone and onto mine? Am I right in assuming that if I manage to do this, it will replace the kernel, too (I currently have the gimlo kernel)?
Do the experts here have any advice for a noob on these two questions?
Thanks, and thanks again for all your hard work here!
Fred
RealFred2 said:
Hello everyone,
I have learned a lot from these forums and am thankful for everyone's hard work here. I have a Tipo Dual that was originally with firmware 11.0.A.6.5 (ST21a2, not i2). I installed GIMLO, which is generally good, but I have some issues with it (LED doesn't light for E-mail or charge, play store and games crashing, little things like that). The phone is rooted and boot loader is unlocked (all with tools from here!). I did not make a backup of my original system before I flashed (I thought I had, but it is not there, not sure how I failed at that).
I have two questions: I have tried a lot of times to relock my boot loader so I could use SUS or PC Companion to reload the firmware. It won't relock with any of the methods I have found here. Is there a reason for that? I have reloaded a stock firmware, and even then I could not relock boot loader. Anything I should look for to allow this?
I would like to put the a2 firmware back on but the firmware I find here is always the i2 version; I understand the difference is little tweaks in how the phone deals with the GSM network, and as phone connectivity is important to me, I'd like the original a2 version again. My wife has the identical phone (with ST21a2 & 11.0.A.6.5 -- or maybe 11.0.A.8), and she has not done anything to hers. Can I root, make a nandroid backup of her phone, and somehow import/flash that to my phone? I have my contacts backed up, so I'm not worried about that, and I have all my apps, so a clean install would be fine with me. If I can do this, how do I get the backup off of her phone and onto mine? Am I right in assuming that if I manage to do this, it will replace the kernel, too (I currently have the gimlo kernel)?
Do the experts here have any advice for a noob on these two questions?
Thanks, and thanks again for all your hard work here!
Fred
Click to expand...
Click to collapse
Yes the nandroid backup would be fine but you will need to reflash the stock kernel with flashtool i don't no if theres any difference between the kernels of i/a. plus even if you relock your bootloader you still might brick your device flashing with Seus & pcc.
gavster26 said:
Yes the nandroid backup would be fine but you will need to reflash the stock kernel with flashtool i don't no if theres any difference between the kernels of i/a. plus even if you relock your bootloader you still might brick your device flashing with Seus & pcc.
Click to expand...
Click to collapse
Thanks for responding to my question, I appreciate your help.
Do you think it's better then to just do something like flash this if I want to go back to stock:
http://forum.xda-developers.com/showthread.php?t=2270976&highlight=+tipo+dual+
and just forget trying to make it retail again? As long as Sony doesn't change and bring out an OTA/PCC update to JB, I guess there's no reason to worry about anything else in being bootloader locked, right? Especially if I can brick the thing by trying.
This is all very new to me (if I'd realized the limitations of the Tipo Dual and cm10, I would have bought the Tipo single!), but I hope to be able to play more with Android and with roms because of this excellent forum.
Thanks again,
Fred (no, not really)
RealFred2 said:
Thanks for responding to my question, I appreciate your help.
Do you think it's better then to just do something like flash this if I want to go back to stock:
http://forum.xda-developers.com/showthread.php?t=2270976&highlight=+tipo+dual+
and just forget trying to make it retail again? As long as Sony doesn't change and bring out an OTA/PCC update to JB, I guess there's no reason to worry about anything else in being bootloader locked, right? Especially if I can brick the thing by trying.
This is all very new to me (if I'd realized the limitations of the Tipo Dual and cm10, I would have bought the Tipo single!), but I hope to be able to play more with Android and with roms because of this excellent forum.
Thanks again,
Fred (no, not really)
Click to expand...
Click to collapse
If thats the firmware you want then by all means flash that bro. The nandroid backup from your wifes phone will be just the same. the backup will be on her sdcard in the file /clockworkmod/backups/ just copy it and paste it to your sdcard. restore it then flash the kernel.
There's an ftf file available im the forum to relock the bootloader.
Flash it in fastboot mode.
I myself have flashed it to relock the bootloader on my st21i2.
After that use pc companion to get your firmware.
I have relocked and then used pc companion without any problems using this method.
Should work for you too.
All the best.
Sent from my ST23i
c4cyro said:
There's an ftf file available im the forum to relock the bootloader.
Flash it in fastboot mode.
I myself have flashed it to relock the bootloader on my st21i2.
After that use pc companion to get your firmware.
I have relocked and then used pc companion without any problems using this method.
Should work for you too.
All the best.
Sent from my ST23i
Click to expand...
Click to collapse
Thanks, c4cyro; I managed to relock with flashtool (it had not worked when I had tried before, but suddenly it did); even so, I can't load from pc companion. Did you also unroot your phone? I've seen elsewhere that that can have something to do with it. I'd like to do this just because so far I haven't been able to (and I hate not being able to do stuff, even when I'm a noob).
Thanks again,
Fred
no i did not unroot. if sony pcc does not recognise your phone, you should try doing that on another system maybe.
to unroot you can use "unlockroot" program.
also, did you check this? http://forum.xda-developers.com/showthread.php?t=2001567
c4cyro said:
no i did not unroot. if sony pcc does not recognise your phone, you should try doing that on another system maybe.
to unroot you can use "unlockroot" program.
also, did you check this? http://forum.xda-developers.com/showthread.php?t=2001567
Click to expand...
Click to collapse
I wonder if it's because it's a Tipo Dual, and the firmware that Gimlo is based on for the Dual is the latest (11.0.A.6.8); even when it's locked and unrooted, pc companion just says it doesn't have any software for my phone. Really strange (and annoying). I might try loading an older firmware, locking everything up, and trying again. Or maybe I'll just reinstall Gimlo and see if I can get it to work the way I want it to!
Thanks again for your help, c4cyro,
Fred
RealFred2 said:
I wonder if it's because it's a Tipo Dual, and the firmware that Gimlo is based on for the Dual is the latest (11.0.A.6.8); even when it's locked and unrooted, pc companion just says it doesn't have any software for my phone. Really strange (and annoying). I might try loading an older firmware, locking everything up, and trying again. Or maybe I'll just reinstall Gimlo and see if I can get it to work the way I want it to!
Thanks again for your help, c4cyro,
Fred
Click to expand...
Click to collapse
maybe. does it recognise that it's a tipo or it just says that there's no software available?
c4cyro said:
maybe. does it recognise that it's a tipo or it just says that there's no software available?
Click to expand...
Click to collapse
It picks it up as Tipo Dual (listed as St21i2 instead of St21a2 bc the Gimlo .3 firmware -- which is the right one for the dual -- is the "i" version).
I've just found this firmware, which seems to be stock, so I'm going to try this:
1) try out this firmware (http://forum.xda-developers.com/showthread.php?t=2044944; 11.0.A.6.5 stock) and see what it is and how it works;
2) then install the base stock for the Tipo Dual for Gimlo (which for the dual is );
3) then install the Gimlo firmware and ROM, and see if I can get it to work the way I want (going mostly stock except for the loader, which I really like the one I'm using on Gimlo);
Will report back on how things turn out and what I end up sticking with!
Thanks again for your help, it's good to feel like I'm not hopping about on one foot on my own.
Fred
All the best!!

Instructions to install ADB drivers? [Resolved!]

Hello, I bought my shield a while back, rooted in KitKat just to get my backup data from apps from my previous device transferred and then happily ungraded to Lollipop with the intention to stay unrooted since it means unlocking the bootloader which may void my warranty. Recently I came upon an app named Helium which I knew nothing about and which seems to be able to backup app data even without root, but to use the no-root version you need to have ADB drivers installed. I found a bunch of sets of ADB drivers, like for example this http://developer.download.nvidia.com/mobile/shield/SHIELDTablet_WHQL_USB_driver.zip but nowhere real instructions explaining how to install them in a Windows 7 PC. I've searched all over the place with no luck so help would be greatly appreciated. I installed drivers for my older device about 3 years ago so I've done it before but I can't remember a thing about it, even if it was a similar method that I had followed.
Thanks in advance, hope someone replies. Help a fellow keep his data backed up please!
Hey there, man.
First of all, neither rooting or unlocking bootloader will void your wartranty, unless the installation you made after that, break the whole tablet in pieces. For example, if you happened to install Windows 8 and it burns.
As for ADB, just read this thread: http://forum.xda-developers.com/showthread.php?t=2317790
Good luck.
YuriPan said:
Hello, I bought my shield a while back, rooted in KitKat just to get my backup data from apps from my previous device transferred and then happily ungraded to Lollipop with the intention to stay unrooted since it means unlocking the bootloader which may void my warranty. Recently I came upon an app named Helium which I knew nothing about and which seems to be able to backup app data even without root, but to use the no-root version you need to have ADB drivers installed. I found a bunch of sets of ADB drivers, like for example this http://developer.download.nvidia.com/mobile/shield/SHIELDTablet_WHQL_USB_driver.zip but nowhere real instructions explaining how to install them in a Windows 7 PC. I've searched all over the place with no luck so help would be greatly appreciated. I installed drivers for my older device about 3 years ago so I've done it before but I can't remember a thing about it, even if it was a similar method that I had followed.
Thanks in advance, hope someone replies. Help a fellow keep his data backed up please!
Click to expand...
Click to collapse
When I'm faced with a .zip file, the first thing I do is to unzip it and look at the contents. If there's an installer in there, I just double-click on it ... Sorry if this sounds very basic, but it might not occur to everyone =)
If there's not an installer, you'll probably have to install those drivers through Device Manager. Good luck =)
CM17X said:
Hey there, man.
First of all, neither rooting or unlocking bootloader will void your wartranty, unless the installation you made after that, break the whole tablet in pieces. For example, if you happened to install Windows 8 and it burns.
As for ADB, just read this thread: http://forum.xda-developers.com/showthread.php?t=2317790
Good luck.
Click to expand...
Click to collapse
Oh I see. Then I might actually root it but since I have to unlock the bootloader and it will wipe my device I definitely need to make this no-root backup work first >.<
I opened the link. The instructions are just to install the exe? I did but my pc still thinks I have no drivers installed... *sigh* Any ideas?
Ok, I figured it out, I installed via Device Manager after all, I was using a bad set of drivers, apparently some file was missing from them so the DM didn't recognize it as drivers... ugh, such confusion for such a silly little thing! Thank you for your help!
amartolos said:
When I'm faced with a .zip file, the first thing I do is to unzip it and look at the contents. If there's an installer in there, I just double-click on it ... Sorry if this sounds very basic, but it might not occur to everyone =)
If there's not an installer, you'll probably have to install those drivers through Device Manager. Good luck =)
Click to expand...
Click to collapse
I tried unziping it. Dunno what I'm supposed to do next. There's no exe's in there, there are 2 files that are considered "Security Catalog", 2 are "Setup Information" and there's 2 folders and each contains 3 files that are "Application exension"
I'd like to try installing them through Device Manager but... how do I do that?
Ok, ignore whatever I wrote before, I figured it out. Looks like I was using a bad package of adb drivers. The funny thing is, the link I posted above is the one that worked but the one I was trying to install was a different one! I suppose I got confused after finding more than one set of instructions! >.<

[Q] in need of dire help. please read

OK so I have the z3. Cool phone I might add. I use my hotspot A lot but after upgrading to 5.0.2 foolishly. I cannot use my data connection externally. Is there a a way to downgrade to 4.4.4 or b. A way to upgrade to a later version of android where this big may be fixed. I really need the hotspot to work as its my life line. I'd like to keep it stock for now if possible too. Thanks Guys
benjy105 said:
OK so I have the z3. Cool phone I might add. I use my hotspot A lot but after upgrading to 5.0.2 foolishly. I cannot use my data connection externally. Is there a a way to downgrade to 4.4.4 or b. A way to upgrade to a later version of android where this big may be fixed. I really need the hotspot to work as its my life line. I'd like to keep it stock for now if possible too. Thanks Guys
Click to expand...
Click to collapse
(I think you meant "in dire need of help" unless you're specifically looking for low quality answers )
Downgrade using xperifirm to get the rom, and flashtool to install it, using this guide (note: you'll have to choose a different rom to the one mentioned in that guide):
http://www.xperiablog.net/2015/03/1...peria-lollipop-using-xperifirm-and-flashtool/
OK that's great. What is xperifirm in regards to.the importance of getting the room. I have downloaded 4.4.4 from.another source before I started this thread. Will I not be able to.use thaT? What I mean is is it significant to the process??
benjy105 said:
OK that's great. What is xperifirm in regards to.the importance of getting the room. I have downloaded 4.4.4 from.another source before I started this thread. Will I not be able to.use thaT? What I mean is is it significant to the process??
Click to expand...
Click to collapse
No, nothing special about xperifirm; It's just the only place i've ever got a rom from so i know it's legit. as long as flashtool likes your 4.4.4 it should be fine.
So I've coklme across a new problem. When installing the flash program I tried the windows key and r and typed in the stuff needed but I'm not getting what it says on the instructions. Therefor unable to install allbthe drivers. Running Windows 8.1.
I'm lost nnow. Could it be zipped with the drivers pre installed?
benjy105 said:
So I've coklme across a new problem. When installing the flash program I tried the windows key and r and typed in the stuff needed but I'm not getting what it says on the instructions. Therefor unable to install allbthe drivers. Running Windows 8.1.
I'm lost nnow. Could it be zipped with the drivers pre installed?
Click to expand...
Click to collapse
Probably need to put a little more detail about what you expect to happen and what's actually happening. (I used windows 7 and it installed without problem, but I think I read that windows 8 required a little more love to get the drivers installed. )
Webern said:
Probably need to put a little more detail about what you expect to happen and what's actually happening. (I used windows 7 and it installed without problem, but I think I read that windows 8 required a little more love to get the drivers installed. )
Click to expand...
Click to collapse
First off it wouldn't download and install all the drivers. So I installed the Sony companion and then when I went to flash the tft file it said unable to extract.ini or such. May just be a bad roM. I'm not at the computer now but I'll try again tomorrow
benjy105 said:
First off it wouldn't download and install all the drivers. So I installed the Sony companion and then when I went to flash the tft file it said unable to extract.ini or such. May just be a bad roM. I'm not at the computer now but I'll try again tomorrow
Click to expand...
Click to collapse
You have installed the wrong program, Install flashtool from flashtool.net and flash the FTF (not tft) using that
The sony flashtool only works on unlocked bootloader phones, but the original developed here on XDA is far better and works on locked bootloaders as well.
It was an ftf file it just blooming autocorrected. Right I'm going to try again and I'll take shots too

Noob Help - Bootloop on Sony Xperia Z3

Hello, I am new to xda, so if this is in the wrong place, I apologize. Also, I am new to this rooting stuff, so I do not now much about it.
Anyway, I have a just rooted Xperia Z3 D6653 Android Device and I was in the middle of installing TWRP (which successfully installed) and my phone got stuck in a boot loop. I have searched every where for a fix but nothing is working. I tried to factory reset and wipe the dalviq cache on recovery mode, but it says it always fails. I still try to reboot the phone into the system, but it keeps looping. Could someone please help me out? Any help would be really appreciated.
Also my bootloader is unlocked
And I am running Lollipop.
Thanks
yahboyvictorr said:
Hello, I am new to xda, so if this is in the wrong place, I apologize. Also, I am new to this rooting stuff, so I do not now much about it.
Anyway, I have a just rooted Xperia Z3 D6653 Android Device and I was in the middle of installing TWRP (which successfully installed) and my phone got stuck in a boot loop. I have searched every where for a fix but nothing is working. I tried to factory reset and wipe the dalviq cache on recovery mode, but it says it always fails. I still try to reboot the phone into the system, but it keeps looping. Could someone please help me out? Any help would be really appreciated.
Also my bootloader is unlocked
And I am running Lollipop.
Thanks
Click to expand...
Click to collapse
Fist of all: welcome to xda and thanks for actually posting in the right thread
Now, your problem: what did you do exactly?
You downgraded to 4.4.4, rooted, and then installed recovery? Which guide did you follow and what programs did you use?
Generally speaking what you should be able to do:
Turn phone off (long vol+ & power press)
Prepare flashtool by selecting your .ftf of choice (recommendable to use 4.4.4 so you can get it right then) and checking clear data and cache
Then let it prepare everything
Hold down vol- when asked tip and plug your phone in
You'll get a fresh start!
Best of luck!
Just one thing: you first unlocked your phone and then rooted it? If so that'd be a pitty, cause that'd mean you lost DRM keys and functions. Why did you exactly unlock it if I may ask?
Edit: you said you are on LP, therefore I assume you are unrooted, which would show why it didn't work
I advise you to follow this guide: http://forum.xda-developers.com/showthread.php?t=3017056
As it shows everything really well
Jkay7 said:
Fist of all: welcome to xda and thanks for actually posting in the right thread
Now, your problem: what did you do exactly?
You downgraded to 4.4.4, rooted, and then installed recovery? Which guide did you follow and what programs did you use?
Generally speaking what you should be able to do:
Turn phone off (long vol+ & power press)
Prepare flashtool by selecting your .ftf of choice (recommendable to use 4.4.4 so you can get it right then) and checking clear data and cache
Then let it prepare everything
Hold down vol- when asked tip and plug your phone in
You'll get a fresh start!
Best of luck!
Just one thing: you first unlocked your phone and then rooted it? If so that'd be a pitty, cause that'd mean you lost DRM keys and functions. Why did you exactly unlock it if I may ask?
Edit: you said you are on LP, therefore I assume you are unrooted, which would show why it didn't work
I advise you to follow this guide: http://forum.xda-developers.com/showthread.php?t=3017056
As it shows everything really well
Click to expand...
Click to collapse
Well I tried what you said, but I cannot find a link. So I just downloaded a random one (its the right version) but in flashtool it just keeps coming up with errors. I followed the steps from these 3 websites
http://howtorootmobile.com/root-sony-xperia-z3-easy-steps/#top_ankor
http://howtorootmobile.com/unlock-bootloader-sony-xperia-z2/
http://howtorootmobile.com/guide-install-twrp-recovery-sony-xperia-z3/
What I was installing TWRP and the last step was to type in fastboot reboot on the command window, that is when my Xperia Z3 got stuck in a boot loop. I dont really know what a ROM is and how to properly flash stuff, so I probably made a mistake while installing TWRP and thats why I get errors trying to wipe files using it.
Also, I did not downgrade before I rooted and unlocked bootloader and installed TWRP. I didnt even know you had to downgrade. Would that be a reason why the bootloop occured?
yahboyvictorr said:
Well I tried what you said, but I cannot find a link. So I just downloaded a random one (its the right version) but in flashtool it just keeps coming up with errors. I followed the steps from these 3 websites
http://howtorootmobile.com/root-sony-xperia-z3-easy-steps/#top_ankor
http://howtorootmobile.com/unlock-bootloader-sony-xperia-z2/
http://howtorootmobile.com/guide-install-twrp-recovery-sony-xperia-z3/
What I was installing TWRP and the last step was to type in fastboot reboot on the command window, that is when my Xperia Z3 got stuck in a boot loop. I dont really know what a ROM is and how to properly flash stuff, so I probably made a mistake while installing TWRP and thats why I get errors trying to wipe files using it.
Also, I did not downgrade before I rooted and unlocked bootloader and installed TWRP. I didnt even know you had to downgrade. Would that be a reason why the bootloop occured?
Click to expand...
Click to collapse
Yes it is definitely a reason. Follow the steps from the guide I linked you step by step, it works 100%

Already rooted Samsung J5 - general inquiry

Hello guys. I just bought a used Samsung Galaxy J5 (SM-J500FN) with android version 5.1.1. The previous owner told me that it is rooted. Nothing seems weird with the phone other than when i try to factory reset it it takes me to a "bios" kind window where i have to manually choose to delete all data (hard delete i think its called), that and when i normally turn on the phone, at the top left corner it says "set warranty bit kernel". I was just wondering how do i go about installing custom roms since its already rooted, and can i unblock the default carriers (T-mobile) block for other sim cards. When asked how he rooted it (what method was he using) he said he just used Odin. I dont know much about rooting so, whatever you can tell me as to the handling of the phone would be amazing. Any other guides to installing some custom roms and making the phone easier and faster ( i only want functionality, don't care much about the UI) would be greatly appreciated. Thanks in advance.
luan96 said:
Hello guys. I just bought a used Samsung Galaxy J5 (SM-J500FN) with android version 5.1.1. The previous owner told me that it is rooted. Nothing seems weird with the phone other than when i try to factory reset it it takes me to a "bios" kind window where i have to manually choose to delete all data (hard delete i think its called), that and when i normally turn on the phone, at the top left corner it says "set warranty bit kernel". I was just wondering how do i go about installing custom roms since its already rooted, and can i unblock the default carriers (T-mobile) block for other sim cards. When asked how he rooted it (what method was he using) he said he just used Odin. I dont know much about rooting so, whatever you can tell me as to the handling of the phone would be amazing. Any other guides to installing some custom roms and making the phone easier and faster ( i only want functionality, don't care much about the UI) would be greatly appreciated. Thanks in advance.
Click to expand...
Click to collapse
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
ShaDisNX255 said:
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
Click to expand...
Click to collapse
That's what I love about Samsung, as long as you have your ducks in a row, the files and tools are extremely easy to use, a 4 year old could do it.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
ShaDisNX255 said:
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
Click to expand...
Click to collapse
Thank you, ill be sure to check them out. Although, i would like to do the entire process from the beginning (root it again myself since i have no idea what the previous owner has done) and then try to install custom roms and other cool features rooting offers. I read that the KNOX security on samsung phones can pose some problems, any thoughts on that ?
Thank you again for your response.
ShaDisNX255 said:
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
Click to expand...
Click to collapse
Also, i use Linux so i hear the alternative to Odin is Heimdall, anyone have any experience with it, or should i just do it on a Windows PC?
luan96 said:
Also, i use Linux so i hear the alternative to Odin is Heimdall, anyone have any experience with it, or should i just do it on a Windows PC?
Click to expand...
Click to collapse
I've got no experience with Linux, sorry. SuperSU disables knox so there's nothing to worry about.
luan96 said:
Also, i use Linux so i hear the alternative to Odin is Heimdall, anyone have any experience with it, or should i just do it on a Windows PC?
Click to expand...
Click to collapse
If you're a Linux user and you have knowledge of using terminal commands then you should have no trouble setting up Hiemdall. Getting full USB functionality set up for the device in Hiemdall can be a pain if you aren't familiar with that kind of thing.
But, having a Windows PC will make a lot of things very simplified for you. A Windows/Linux dual boot system would be very handy to you if you can set that up. Then you could also use Kies/SmartSwitch if it ever comes to a point that you need it.
There are some handy rarely used instances with Linux when it comes to Samsung. They have no fastboot like other devices so only adb is usable. I think they primarily centered around Windows being the preferred OS to interact with their devices.
Droidriven said:
If you're a Linux user and you have knowledge of using terminal commands then you should have no trouble setting up Hiemdall. Getting full USB functionality set up for the device in Hiemdall can be a pain if you aren't familiar with that kind of thing.
But, having a Windows PC will make a lot of things very simplified for you. A Windows/Linux dual boot system would be very handy to you if you can set that up. Then you could also use Kies/SmartSwitch if it ever comes to a point that you need it.
There are some handy rarely used instances with Linux when it comes to Samsung. They have no fastboot like other devices so only adb is usable. I think they primarily centered around Windows being the preferred OS to interact with their devices.
Click to expand...
Click to collapse
Thank you for the info. I already have a dual boot on my pc with windows. I am an experienced Linux user and setting up Hiemdall should not pose a problem, but i opted to go for Windows since as you said makes things simpler.
Still looking for guides and tutorials on how exactly the root process goes. Doing research, so i guess its going to be a late night. If you have any links or pages you can guide me to for my Samsung J5 it would be amazing. Right now am looking around this forum and wherever the links lead me.
Thank you again.
luan96 said:
Thank you for the info. I already have a dual boot on my pc with windows. I am an experienced Linux user and setting up Hiemdall should not pose a problem, but i opted to go for Windows since as you said makes things simpler.
Still looking for guides and tutorials on how exactly the root process goes. Doing research, so i guess its going to be a late night. If you have any links or pages you can guide me to for my Samsung J5 it would be amazing. Right now am looking around this forum and wherever the links lead me.
Thank you again.
Click to expand...
Click to collapse
First, just to make sure that you are not walking blindly into some potential traps.
1) download the root checker app from Playstore, use it to verify whether the device is actually rooted.
2) power the device off, wait 5 seconds, hold volume up+home+power, when it boots past the logo, let go. It should boot to recovery, tell me what you see. Does it say TWRP with grey buttons on a black screen? Or does it have an android lying on his back and have options listed?
3) verify whether or not the bootloader is unlocked or not on your specific device model number with your specific build number/android version, if it's locked it will create problems if you try to flash custom recovery. Though you can flash CF autoroot with locked bootloader.
Then I'll help find what you need to do what you are looking to do. It may be simpler than you think.
If he in fact used Odin and the device is rooted, he did one of three things.
1) flashed custom recovery(TWRP) via Odin then flashed SuperSU.zip to root, not possible with locked bootloader.
2) flashed CF auto root via Odin, potentially leaving stock recovery if your bootloader is locked.
3) flashed a pre-rooted stock firmware via Odin, not likely though.
The first 2 being more likely than the last one, the second one being the most likely if your bootloader is locked.
Edit: @luan96, edited for more information.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
@Droidriven Thank you for the info. After a rough night of research i realized what i need to do. According to root checker, my phone is not rooted, and the recovery seems to be stock. This is very weird, since the phone is obviously not just the stock version that came from T Mobile. Im guessing its probably a badly done root or one that was removed. Anyways, this is how i am planing to proceed:
1. Turn on OEM Unlocking and USB Debugging from developer versions
2. Download CM Autoroot for my specific phone ( i do not know what is the difference between "normal" root and autoroot, but autoroot seems to be simpler and offers the same thing. Please correct me if i am wrong, i would love to know how to do a manual root as well if it has more benefits).
3. Volume down+home+power to get to the download screen
4. Launch Odin that comes with the autoroot package
5. Plug my phone into the USB and wait for Odin to add it.
6. Select the autoroot md5 file from the folder and begin the flashing process
7. Hope for the best and that my phone is still functional when it auto reboots.
After this i should check with Root Checker weather its properly installed or not. If it is, and i see the SuperSU application i continue to installing the custom recovery ( through some research i found out that TWRP is the best choice for me). Installing the custom recovery should be as easy as auto rooting the device. I should download the files from an official website, and flash them using the same process i did for AutoRoot.
After that its mod heaven. With my understanding so far, TWRP lets me install custom roms, and other things i might need.
This is what i plan on doing as soon as im done with a little more research. If anyone has any tips, corrections or general information on what to expect or do please share.
Many thanks to every contributor on this thread.
luan96 said:
@Droidriven Thank you for the info. After a rough night of research i realized what i need to do. According to root checker, my phone is not rooted, and the recovery seems to be stock. This is very weird, since the phone is obviously not just the stock version that came from T Mobile. Im guessing its probably a badly done root or one that was removed. Anyways, this is how i am planing to proceed:
2. Download CM Autoroot for my specific phone ( i do not know what is the difference between "normal" root and autoroot, but autoroot seems to be simpler and offers the same thing. Please correct me if i am wrong, i would love to know how to do a manual root as well if it has more benefits).
3. Volume down+home+power to get to the download screen
4. Launch Odin that comes with the autoroot package
5. Plug my phone into the USB and wait for Odin to add it.
6. Select the autoroot md5 file from the folder and begin the flashing process
7. Hope for the best and that my phone is still functional when it auto reboots.
After this i should check with Root Checker weather its properly installed or not. If it is, and i see the SuperSU application i continue to installing the custom recovery ( through some research i found out that TWRP is the best choice for me). Installing the custom recovery should be as easy as auto rooting the device. I should download the files from an official website, and flash them using the same process i did for AutoRoot.
After that its mod heaven. With my understanding so far, TWRP lets me install custom roms, and other things i might need.
This is what i plan on doing as soon as im done with a little more research. If anyone has any tips, corrections or general information on what to expect or do please share.
Many thanks to every contributor on this thread.
Click to expand...
Click to collapse
I would recommend using the command line to flash the twrp instead of the GUI if you want a simple process in linux
Run a terminal as a superuser (sudo)
heimdall flash –RECOVERY filename.img
Do step 1 and 3 you gave before before doing this
Or just flash the twrp image using Odin
J500FN twrp
https://dl.twrp.me/j5nltexx/
-Hope- said:
I would recommend using the command line to flash the twrp instead of the GUI if you want a simple process in linux
Run a terminal as a superuser (sudo)
heimdall flash –RECOVERY filename.img
Do step 1 and 3 you gave before before doing this
Or just flash the twrp image using Odin
J500FN twrp
https://dl.twrp.me/j5nltexx/
Click to expand...
Click to collapse
I'm going to use Odin for this. Since I'm quite new to the rooting community I dont want to mess things up on the first try. I'd rather get comfortable with some standard stuff before I proceed to try different variations. Thank you for your input. Though I would still like to know if I should use cm auto root or do a manual root. The difference is not quite clear to me yet. Again, thank you for your input, it is appreciated.
luan96 said:
@Droidriven Thank you for the info. After a rough night of research i realized what i need to do. According to root checker, my phone is not rooted, and the recovery seems to be stock. This is very weird, since the phone is obviously not just the stock version that came from T Mobile. Im guessing its probably a badly done root or one that was removed. Anyways, this is how i am planing to proceed:
1. Turn on OEM Unlocking and USB Debugging from developer versions
2. Download CM Autoroot for my specific phone ( i do not know what is the difference between "normal" root and autoroot, but autoroot seems to be simpler and offers the same thing. Please correct me if i am wrong, i would love to know how to do a manual root as well if it has more benefits).
3. Volume down+home+power to get to the download screen
4. Launch Odin that comes with the autoroot package
5. Plug my phone into the USB and wait for Odin to add it.
6. Select the autoroot md5 file from the folder and begin the flashing process
7. Hope for the best and that my phone is still functional when it auto reboots.
After this i should check with Root Checker weather its properly installed or not. If it is, and i see the SuperSU application i continue to installing the custom recovery ( through some research i found out that TWRP is the best choice for me). Installing the custom recovery should be as easy as auto rooting the device. I should download the files from an official website, and flash them using the same process i did for AutoRoot.
After that its mod heaven. With my understanding so far, TWRP lets me install custom roms, and other things i might need.
This is what i plan on doing as soon as im done with a little more research. If anyone has any tips, corrections or general information on what to expect or do please share.
Many thanks to every contributor on this thread.
Click to expand...
Click to collapse
Flashing CF autoroot will simplify rooting, again, just make sure you have the correct autoroot for your specific model number and firmware, flashing the wrong one can softbrick or hardbrick your device, this would require flashing stock firmware via Odin to repair if softbricked and more serious methods to restore if hardbricked. There isn't much difference in effect with the different rooting methods. They all get the job done about equally.
Just make sure that you verify that your bootloader is in fact unlocked BEFORE you flash TWRP. As stated earlier, if it is locked, it will certainly cause issues and you'll have to restore stock recovery and/or stock firmware.
As long as your bootloader is unlocked then your outlined plan should be good to go.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
Flashing CF autoroot will simplify rooting, afain, just make sure you have the correct autoroot for your specific model number and firmware, flashing the wrong one can softbrick or hardbrick your device, this would require flashing stock firmware via Odin to repair if softbricked and more serious methods to restore if hardbricked. There isn't much difference in effect with the different rooting methods. They all get the job done about equally.
Just make sure that you verify that your bootloader is in fact unlocked BEFORE you flash TWRP. As stated earlier, if it is locked, it will certainly cause issues and you'll have to restore stock recovery and/or stock firmware.
As long as you're bootloader is unlocked then your outlined plan should be good to go.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Well, looks like i messed up somehow. I was fiddling around the recovery mode and Odin mode. Those were the only two screens i could view besides normal booting, so i was looking for any info.
Recovery Mode https://ibb.co/hotYZ5
Odin mode 1 https://ibb.co/nFfVE5
Once on the recovery mode, i selected "reboot to bootloader" hoping to find info if its locked or not. I got redirected to this screen
Odin Mode 2 https://ibb.co/kqhtZ5
And then i did what i think is the dumbest thing this year....i removed the batery and now when i try to turn on my phone -
Blocked https://ibb.co/kkOd1k
Please tell me i did not brick my phone without even trying to root it first. My understanding is that i accidentally wiped the current OS (softbrick?) and now i have to flash a new one and then continue with what i had planned. Or is this a small problem that can be fixed easier? Or a more serious one ? Good news tho maybe, i think that the bootloader is unlocked ?
Thank you @Droidriven for your info so far, you have been extremely helpful.
*EDIT* - Pictures didnt link correctly.
luan96 said:
Well, looks like i messed up somehow. I was fiddling around the recovery mode and Odin mode. Those were the only two screens i could view besides normal booting, so i was looking for any info.
Recovery Mode https://ibb.co/hotYZ5
Odin mode 1 https://ibb.co/nFfVE5
Once on the recovery mode, i selected "reboot to bootloader" hoping to find info if its locked or not. I got redirected to this screen
Odin Mode 2 https://ibb.co/kqhtZ5
And then i did what i think is the dumbest thing this year....i removed the batery and now when i try to turn on my phone -
Blocked https://ibb.co/kkOd1k
Please tell me i did not brick my phone without even trying to root it first. My understanding is that i accidentally wiped the current OS (softbrick?) and now i have to flash a new one and then continue with what i had planned. Or is this a small problem that can be fixed easier? Or a more serious one ? Good news tho maybe, i think that the bootloader is unlocked ?
Thank you @Droidriven for your info so far, you have been extremely helpful.
*EDIT* - Pictures didnt link correctly.
Click to expand...
Click to collapse
It looks to me like they attempted to root the device but didn't do it correctly.
FRP can be a pain to deal with. Some can be bypassed easily, those that have trouble bypassing must sign in with the original owner's original Gmail and password used to activate the device.
The method of bypassing FRP varies from device to device.
Did you factory reset in recovery? If so, that's why you FRP blocked you.
If you have stock recovery then you should not have been able to wipe out the OS using stock recovery, typically, only custom recovery can do that, unless you did something accidentally that somehow corrupted/wiped your OS.
If the OS is gone, you'll have to flash your stock firmware via Odin and start over from the beginning.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
It looks to me like they attempted to root the device but didn't do it correctly.
FRP can be a pain to deal with. Some can be bypassed easily, those that have trouble bypassing must sign in with the original owner's original Gmail and password used to activate the device.
The method of bypassing FRP varies from device to device.
Did you factory reset in recovery? If so, that's why you FRP blocked you.
If you have stock recovery then you should not have been able to wipe out the OS using stock recovery, typically, only custom recovery can do that, unless you did something accidentally that somehow corrupted/wiped your OS.
If the OS is gone, you'll have to flash your stock firmware via Odin and start over from the beginning.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Thank you. At least its not just a paperweight. I'm installing new software on it with Kiesk 3 right now. Hope that works so i can do the rooting and TWRP install soon. I pressed "reboot to bootlader" to try and find out if its locked or not, but then it got me in download mode (without having to press up volume to contionue). After i turned off my phone by removing the battery, the OS was gone.
luan96 said:
Thank you. At least its not just a paperweight. I'm installing new software on it with Kiesk 3 right now. Hope that works so i can do the rooting and TWRP install soon. I pressed "reboot to bootlader" to try and find out if its locked or not, but then it got me in download mode (without having to press up volume to contionue). After i turned off my phone by removing the battery, the OS was gone.
Click to expand...
Click to collapse
Did you get this restored with Kies?
Droidriven said:
Did you get this restored with Kies?
Click to expand...
Click to collapse
Yes, i did. Worked like a charm, and even got the new 6.0.1 android on it. Also installed TWRP, and just finished installing Xposed Framework, now waiting for it to boot up ( i hear it takes some time). Seems all well so far. If any problems pop out ill be sure to post about it. Also thinking about making a new thread just to help newbies like me who really just want to remove some bloatware, and install some nice modules and not heavily mod the phone. You have been very helpful during this process. Many thanks to you ^-^ .
luan96 said:
Yes, i did. Worked like a charm, and even got the new 6.0.1 android on it. Also installed TWRP, and just finished installing Xposed Framework, now waiting for it to boot up ( i hear it takes some time). Seems all well so far. If any problems pop out ill be sure to post about it. Also thinking about making a new thread just to help newbies like me who really just want to remove some bloatware, and install some nice modules and not heavily mod the phone. You have been very helpful during this process. Many thanks to you ^-^ .
Click to expand...
Click to collapse
If you have issues with Xposed causing a bootloop, you can flash the Xposed uninstaller zip in TWRP to remove it, then troubleshoot why it bootlooped and try again.
Are you using the Touch wiz marshmallow Xposed framework?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Categories

Resources