Related
Okay so I recently got my Galaxy Note II from VZ and traveled to Singapore and got a Singtel SIM, then I need to goto Thailand and acquire another SIM. I need to input APN settings on this phone from the Singapore carrier: Singtel but the VZ bastards hide this APN field on this phone...sooooo.. I need to root my phone.
From the masta xda-dev the instructions to load the latest note2_JellyBeans_B8.zip onto this Samsung Galaxy Note II phone is:
YOU MUST BE UNLOCKED (yup this phone is unlocked ..I can make calls np but no data... wah)
Step 1-
Wipe Data Factory Reset!
Step 2-
Wipe davlick cache
Step 3-
install zip and pick your options
Step 4-
Reboot and enjoy!
Step 1: HOW do I factory reset this phone and
Step 2: How do I davlick (whatever that means) my cache?
I am a brand new n00b so sarcasm is ok for the moment but any genuine help is greatly appreciated. Thanks.
Found part of it
Yup sorry... Google is still my best friend so I found the part of how to factory reset this phone:
"Turn the Power off. Gently press and hold down Volume Up + Home + Power buttons simultaneously. Release all keys once the Logo appears. You will then prompted in a Android System Recovery options. Now, scroll down using Volume keys, and choose "Select Wipe Data/Factory Reset" Enter your selection using the "Power" button Select Yes — "Delete All User Data". Then, select "Reboot System Now".
Wait until the device will then completely reboots. You can repeat this process if you need to restore back your Samsung Galaxy Note 2 to its original default settings. "
Now the davlick cache bit... *scratches head* and heads on to startpage dot com for a search.
By unlocked they mean boot loader. Are you in the new ota LL4? If so file this
http://forum.xda-developers.com/showthread.php?p=37195287
Sent from the dark on a Note 2
kintwofan said:
By unlocked they mean boot loader. Are you in the new ota LL4? If so file this
http://forum.xda-developers.com/showthread.php?p=37195287
Sent from the dark on a Note 2
Click to expand...
Click to collapse
I believe you are absolutely right. I need CASUAL to begin the process of unlocking the phone but per the above linkie that is considered jailbreaking not unlocking (big difference). Anyway not sure if I have ota LL4 but my specs are the following:
Model: SCH-1605
Android Version: 4.1.1
Baseband Version: 1605VRALL4
Kernel Version: 3.0.31-414933
[email protected] #1
Build Number: JR something...
Hardware version: 1605.06
Does that info help?
hugeyeti said:
I believe you are absolutely right. I need CASUAL to begin the process of unlocking the phone but per the above linkie that is considered jailbreaking not unlocking (big difference). Anyway not sure if I have ota LL4 but my specs are the following:
Model: SCH-1605
Android Version: 4.1.1
Baseband Version: 1605VRALL4
Kernel Version: 3.0.31-414933
[email protected] #1
Build Number: JR something...
Hardware version: 1605.06
Does that info help?
Click to expand...
Click to collapse
That's the right link to unlock. I believe he caked it jail break to avoid confusion since unlocking sims is now illegal. That method will work for your set up
Sent from the dark on a Note 2
---------- Post added at 06:59 PM ---------- Previous post was at 06:57 PM ----------
If you notice in parentheses he put boot loader unlock next to jail break.
Sent from the dark on a Note 2
kintwofan said:
That's the right link to unlock. I believe he caked it jail break to avoid confusion since unlocking sims is now illegal. That method will work for your set up
Sent from the dark on a Note 2
---------- Post added at 06:59 PM ---------- Previous post was at 06:57 PM ----------
If you notice in parentheses he put boot loader unlock next to jail break.
Sent from the dark on a Note 2
Click to expand...
Click to collapse
Thanks for the input. Now.. do you know of a suitable app that will backup what I have currently on this phone (SD Card notwithstanding), and after a factory reset have it all restored? All my music and movies are on the SD card but main apps that I bought from the app store are in the actual phone and not the SD card.
hugeyeti said:
Thanks for the input. Now.. do you know of a suitable app that will backup what I have currently on this phone (SD Card notwithstanding), and after a factory reset have it all restored? All my music and movies are on the SD card but main apps that I bought from the app store are in the actual phone and not the SD card.
Click to expand...
Click to collapse
I use titanium backup pro. It takes me les then 10 minutes to be back up and running after resets
Sent from the dark on a Note 2
kintwofan said:
I use titanium backup pro. It takes me les then 10 minutes to be back up and running after resets
Sent from the dark on a Note 2
Click to expand...
Click to collapse
Assuming everything went well, I read Samsung inserted new code to blacklist folks that root their phones. Further if you update your firmware then VZ will pretty much make your phone useless and you have to factory reset it. Are there any precautionary measure I should be aware of AFTER the jailbreak that will keep my phone free of these nuisances? Thanks for all your help btw.
If you're staying stock rooted then freeze the app sdm1.0 just to avoid an update but besides that you're good
Sent from the dark on a Note 2
kintwofan said:
If you're staying stock rooted then freeze the app sdm1.0 just to avoid an update but besides that you're good
Sent from the dark on a Note 2
Click to expand...
Click to collapse
Titanium Backup Pro needs a rooted phone so I am unable to backup anything stock. Not a big deal since I can re-download the common apps I bought from the app store (which are mostly games for my nephew). I am assuming that I should be able to freeze this SDM app on Titanium Backup Pro once I install it.
I am a bit confused when you say stock rooted. Do you mean I no longer should update the jellybean OS to latest releases? or installation of third party apps? or modifying the kernel?
hugeyeti said:
Titanium Backup Pro needs a rooted phone so I am unable to backup anything stock. Not a big deal since I can re-download the common apps I bought from the app store (which are mostly games for my nephew). I am assuming that I should be able to freeze this SDM app on Titanium Backup Pro once I install it.
I am a bit confused when you say stock rooted. Do you mean I no longer should update the jellybean OS to latest releases? or installation of third party apps? or modifying the kernel?
Click to expand...
Click to collapse
You know you can root, backup, then factory reset. What I meant by stock rooted is that if you're not going to flash any ROM and just leave your phone rooted only then freeze sdm. If you're flashing a ROM then there's no need to worry about it.
Also, just a tip when you're rooted and unlocked boot loader never accept an OTA
Sent from the dark on a Note 2
kintwofan said:
You know you can root, backup, then factory reset. What I meant by stock rooted is that if you're not going to flash any ROM and just leave your phone rooted only then freeze sdm. If you're flashing a ROM then there's no need to worry about it.
Also, just a tip when you're rooted and unlocked boot loader never accept an OTA
Sent from the dark on a Note 2
Click to expand...
Click to collapse
Thanks. My phone is now unlocked by CASUAL and I froze sdm 1.0 as you suggested. Is sdm1.0 the app that accepts OTA's? If not, where exactly should I disable ANY OTA coming in? I want to make sure that this phone is left "as is" as long as it's rooted. Also, assuming I want to install the latest jellybeans ROM, and I don't have to worry about sdm like you mentioned, is there a particular app I should be concerned about and freeze it to avoid OTA?
Further, what's your take on being stock root vs. loading say... the latest jellybean OS http://forum.xda-developers.com/showthread.php?t=2032447
What is your preference and why?
hugeyeti said:
Thanks. My phone is now unlocked by CASUAL and I froze sdm 1.0 as you suggested. Is sdm1.0 the app that accepts OTA's? If not, where exactly should I disable ANY OTA coming in? I want to make sure that this phone is left "as is" as long as it's rooted. Also, assuming I want to install the latest jellybeans ROM, and I don't have to worry about sdm like you mentioned, is there a particular app I should be concerned about and freeze it to avoid OTA?
Further, what's your take on being stock root vs. loading say... the latest jellybean OS http://forum.xda-developers.com/showthread.php?t=2032447
What is your preference and why?
Click to expand...
Click to collapse
You are safe from any ota. You can't even manualy take it now unless you unfreeze sdm.
Now if you flash beans or any other custom ROM you don't have to worry about otas at all. They're already blocked.
As for stock rooted vs beans that's really up to you. Performance and battery are really about the same. You get extra features with a custom ROM is the main advantage. I am running beans now because I don't like the stock look. I'll probably switch back to Eclipse with the next update because it's even darker and that's what I like.
Sent from the dark on a Note 2
Hi, i'm on 4.1.2 and rooted using link2sd and foldermount so I can store apps on the external sd card. If I upgrade to 4.2.2 do I need to unroot first and then root again after flashing the new firmware?
Also i'm assuming i'm going to lose all my game saves etc as I will lose my link2sd and foldermount setups?
My phone is unlocked from the 3 network but still has the 3 network logo on boot up and so I thought if i'm going to have to start afresh I might as well get the stock unbranded S3 rom and get rid of the 3 network branding. I used Galaxsim unlock to unlock the network so i'm assuming I won't lose my network unlock by doing any of the above?
Thanks in advance for any help given.
Sp0oner said:
Hi, i'm on 4.1.2 and rooted using link2sd and foldermount so I can store apps on the external sd card. If I upgrade to 4.2.2 do I need to unroot first and then root again after flashing the new firmware?
Also i'm assuming i'm going to lose all my game saves etc as I will lose my link2sd and foldermount setups?
My phone is unlocked from the 3 network but still has the 3 network logo on boot up and so I thought if i'm going to have to start afresh I might as well get the stock unbranded S3 rom and get rid of the 3 network branding. I used Galaxsim unlock to unlock the network so i'm assuming I won't lose my network unlock by doing any of the above?
Thanks in advance for any help given.
Click to expand...
Click to collapse
Just flash any rooted 4.2.2 ROM via custom recovery. You should take a titanium backup and a nandroid backup first. If it flashes without a wipe, you've lost nothing. If you do have to wipe, you can restore using Titanium. The Nandroid is a full system restore incase nothing works.
rootSU said:
Just flash any rooted 4.2.2 ROM via custom recovery. You should take a titanium backup and a nandroid backup first. If it flashes without a wipe, you've lost nothing. If you do have to wipe, you can restore using Titanium. The Nandroid is a full system restore incase nothing works.
Click to expand...
Click to collapse
Thanks. As you can tell i'm not up to speed on android rooting as i'm an ex iphone devotee that was good with jailbreaking but i'm new to android rooting really.
If I take an already rooted rom that surely still overwrites my current data as a rom replaces what is already there doesn't it? Can titanium and nandroid backup to pc via usb cable as my 32gb sd card won't have enough room to backup onto as it's heavily used for foldermount and link2sd.
If I wanted a pre rooted 4.2.2 stock rom for the I9300 is that something I can find on this forum to safely download and try? And if for any reasom i'm not happy with it the nandroid backup will restore the phone back to my original rom and setup as if I hadn't changed roms?
Rom and data are different. Please read the link in my signature "read before reading". It should contain everything you need to know (i'm not just saying this because I wrote it, but its really essential).
Sent from my GT-I9300 using Tapatalk 4 Beta
rootSU said:
Rom and data are different. Please read the link in my signature "read before reading". It should contain everything you need to know (i'm not just saying this because I wrote it, but its really essential).
Sent from my GT-I9300 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thank you, again. I have read all that this morning and I am in no rush to change anything as one thing i've learnt from jailbreaking when I first got into it was rushing = ending up in a big mess and panicking you've bricked your device.
I rooted my S3 earlier this year and so I expect I still have all the files and the url of the guide I followed so I can check exactly what it was I did. My flash counter won't reset to zero which really bugged me and again another lesson learnt from doing something without fully checking the consequences.
I'm an IT engineer but all windows based so when it comes to android/linux what I think would be logical pretty much seems to go out the window!
Its always good to hold off and understand before moving forward. Read the thread through a few times.
I'm also a wintel IT engineer but I wanted to get into android development so I've been using Linux at home as my daily driver for 2 years.
If there's ever anything in that thread you want me to put into windows analogies or similes,,just ask in that thread. It will help me expand the thread also
Sent from my GT-I9300 using Tapatalk 4 Beta
rootSU said:
Its always good to hold off and understand before moving forward. Read the thread through a few times.
I'm also a wintel IT engineer but I wanted to get into android development so I've been using Linux at home as my daily driver for 2 years.
If there's ever anything in that thread you want me to put into windows analogies or similes,,just ask in that thread. It will help me expand the thread also
Sent from my GT-I9300 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thanks again. I've been having a play about today and firstly got a titanium backup done for everything and then copied to my laptop. Then got the online version of nandroid backup so no reboot required to take the backup and did a full one of those and copied to my laptop too.
I've checked what root process I followed and it was one posted on the s3 forums using GalaxyS3root which uses a file via odin called CF-Root-SGS3-v6.1.tar. I won't post the link in case it breaks any rules etc. After reading your other post as advised I get the impression i'm not going to be able to reset my flash counter to zero. I have tried triangle away but it doesn't succeed.
As Android 4.3 is out/due out i'm now thinking pointless moving to 4.2.2 and I should wait and got straight to 4.3. Now what I wanted to ask was the following...
If I took titanium backup and then undid all my link2sd and foldermount links and then unrooted would I be able to flash the stock 4.3 rom when available, root it then reset up link2sd and foldermount and restore the titanium backup and have all my apps back to how they were?
I want to get an unmodified samsung rom that is unbranded so I can get rid of my 3 network branding I currently have on boot up. I also want to know if it is possible in anyway to reset the flash counter so I could in theory if unrooted get ota updates.
First question...
If you wipe and manually set up link2sd - when you then restore via titanium everything should be as it was.
You can reset the counter before unrooting. Theres a return-to-stock guide stuck in the "sticky roll-up thread" that covers it. The counter goes up to 1 on boot so the trick is to prevent the boot...
Sent from my GT-I9300 using Tapatalk 4 Beta
rootSU said:
First question...
If you wipe and manually set up link2sd - when you then restore via titanium everything should be as it was.
You can reset the counter before unrooting. Theres a return-to-stock guide stuck in the "sticky roll-up thread" that covers it. The counter goes up to 1 on boot so the trick is to prevent the boot...
Sent from my GT-I9300 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thanks, so the counter can't be cleared permanently for warranty purposes as a reboot will just put it back to 1. So as I have a custom recovery on the phone that went on with the root will that cause issues if I tried to update via official updates?
It can be prevented with an ics bootloader.
Imho its best to stay away from official updates when rooted
Sent from my GT-I9300 using Tapatalk 4 Beta
rootSU said:
It can be prevented with an ics bootloader.
Imho its best to stay away from official updates when rooted
Sent from my GT-I9300 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thanks. An ics bootloader however will just further invalidate the warranty and also prevent stock updates? What I had been getting at with wanting to do stock updates was to unroot first. However now i've got the custom recovery there that in itself makes stock updates an unwise move even with rooting removed?
So with my current setup what is the best method to go to 4.2.2 without using a custom rom?
They check warranty by looking at the information provided in the bootloader. Your warranty is either void or not void. There is no such thing as further invalidation. Its 0 or 1. There is no 2.
There is no "best way" without using a "custom rom". If you want to flash a stock rom, do it. Theres only one way.
By the way, 4.2.2 hasn't been officially released, so you wont be getting stock updates. You'll have to manually keep flashing release via odin until you get one that is official. Then if your csc is wrong, you have to change it (which requires factory reset) and then you will still only get updates over USB if you're rooted.
Don't get me wrong, but that sounds ridiculous to me. I just don't understand any rooted user wanting to do that
Sent from my GT-I9300 using Tapatalk 4 Beta
rootSU said:
They check warranty by looking at the information provided in the bootloader. Your warranty is either void or not void. There is no such thing as further invalidation. Its 0 or 1. There is no 2.
There is no "best way" without using a "custom rom". If you want to flash a stock rom, do it. Theres only one way.
Sent from my GT-I9300 using Tapatalk 4 Beta
---------- Post added at 10:52 PM ---------- Previous post was at 10:51 PM ----------
By the way, 4.2.2 hasn't been officially released
Sent from my GT-I9300 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thanks for the quick reply. I've just read through the link on your thread for returning to stock and unless i've misread it you can actually return to stock even if you have installed a custom recovery/used the auto cf root method of rooting? That's step 16?
Sorry on the invalidating warranty thing, what I meant was that if you use the ics bootloader you fix the triangleaway issue but you are then left with the ics bootloader so your warranty is still invalid.
My mistake on 4.2.2, what's the latest official version as if I plug into kies it tells me there is an update available which i'd wrongly assumed was 4.2.2?
4.1.2 is the latest.
They don't check bootloader version for warranty. They only check download mode.
You can return to stock so long as phone fully boots and usb works. If phone only partially boots, you can't return to stock or reset counter. This is why IMHO its better to have an ics bootloader where counter is always in the reset state
Sent from my GT-I9300 using Tapatalk 4 Beta
rootSU said:
You can return to stock so long as phone fully boots and usb works. If phone only partially boots, you can't return to stock or reset counter. This is why IMHO its better to have an ics bootloader where counter is always in the reset state
Sent from my GT-I9300 using Tapatalk 4 Beta
Click to expand...
Click to collapse
OK this has totally lost me now, I need to do some more reading! Also i'm on 4.1.2 yet if I plug into Kies ittells me there is an update available.
Sp0oner said:
OK this has totally lost me now, I need to do some more reading! Also i'm on 4.1.2 yet if I plug into Kies ittells me there is an update available.
Click to expand...
Click to collapse
An update won't necessarily update the android version. It will update the Samsung build version. Samsung have probably close to 100 updates on 4.1.2 (globally).
Android is just the base OS. It has Samsung GUI on top of that (and frameworks to support Samsung proprietary features). So Samsung take the android code for 4.1.2 and add all their stuff to it. But they will improve on that over a number of builds. Fixing bugs, addressing performance issues etc.
However, Samsung tend to release new features in line with android base updates too. so if Samsung are working on 4.1.2 and decide, "hey this feature would be cool", they would usually wait for the next android version to release it.
Hope that makes sense
Did that address your confusion?
Or is your confusion about returning to stock?
You return to stock by flashing a full ROM (which includes a bootloader, Android ROM, Recovery, baseband etc) over USB connection to a computer. The phone is put into download mode and flashed. if your USB is faulty, this wont work (obviously).
Before returning to stock, you need to ensure your download mode doesnt show how many times you flashed custom things. You can reset it then flash stock and warranty is fine. However, to reset it, android needs to boot, so if android doesnt boot and counter says more than "0", you've lost warranty, With ICS bootloader, you reset it once and it always says "0", so you are protected if phone doesnt boot.
rootSU said:
An update won't necessarily update the android version. It will update the Samsung build version. Samsung have probably close to 100 updates on 4.1.2 (globally).
Android is just the base OS. It has Samsung GUI on top of that (and frameworks to support Samsung proprietary features). So Samsung take the android code for 4.1.2 and add all their stuff to it. But they will improve on that over a number of builds. Fixing bugs, addressing performance issues etc.
However, Samsung tend to release new features in line with android base updates too. so if Samsung are working on 4.1.2 and decide, "hey this feature would be cool", they would usually wait for the next android version to release it.
Hope that makes sense
Did that address your confusion?
Or is your confusion about returning to stock?
You return to stock by flashing a full ROM (which includes a bootloader, Android ROM, Recovery, baseband etc) over USB connection to a computer. The phone is put into download mode and flashed. if your USB is faulty, this wont work (obviously).
Before returning to stock, you need to ensure your download mode doesnt show how many times you flashed custom things. You can reset it then flash stock and warranty is fine. However, to reset it, android needs to boot, so if android doesnt boot and counter says more than "0", you've lost warranty, With ICS bootloader, you reset it once and it always says "0", so you are protected if phone doesnt boot.
Click to expand...
Click to collapse
Thanks for both explanations :good: It was the ics bootloader I was really confused about. I'm in two minds as to change anything, the techy part of me says play with it and learn and understand more about what you've explained but the other side says i've got everything setup perfectly at the moment now I have link2sd and foldermount working and not to risk ruining that setup. I think the only thing i'd notice from 4.2.2 is the access camera from the lock screen feature.
Sp0oner said:
Thanks for both explanations :good: It was the ics bootloader I was really confused about. I'm in two minds as to change anything, the techy part of me says play with it and learn and understand more about what you've explained but the other side says i've got everything setup perfectly at the moment now I have link2sd and foldermount working and not to risk ruining that setup. I think the only thing i'd notice from 4.2.2 is the access camera from the lock screen feature.
Click to expand...
Click to collapse
If you want to continue to use stock.....
1) Backup all your app data with titanium backup (as a precaution)
2) Copy all internal /sdcard data to PC
3) Flash whatever "official" ROM you want via Odin
4) If it doesn't boot, perform factory reset#
5) re root using either cf auto root or framaroot (both do not give custom recovery)
6) Install Titanium backup and restore data.
Its worth noting a factory reset from custom recovery only wipes data and settings. A reset from stock recovery wipes internal /sdcard storage too.
rootSU said:
If you want to continue to use stock.....
1) Backup all your app data with titanium backup (as a precaution)
2) Copy all internal /sdcard data to PC
3) Flash whatever "official" ROM you want via Odin
4) If it doesn't boot, perform factory reset#
5) re root using either cf auto root or framaroot (both do not give custom recovery)
6) Install Titanium backup and restore data.
Its worth noting a factory reset from custom recovery only wipes data and settings. A reset from stock recovery wipes internal /sdcard storage too.
Click to expand...
Click to collapse
Thanks again :good: I have CWM installed and when I open CWM Manager I get a message "this version of CWM Manager should be used with CF-CWM v1.1 or newer. It appears you are running a different recovery. Various features have been disabled."
If I boot into recovery at the top it says "CWM-based recovery v5.5.04 :: CF-v1.3"
What effect does any of that have on the above steps?
Sp0oner said:
Thanks again :good: I have CWM installed and when I open CWM Manager I get a message "this version of CWM Manager should be used with CF-CWM v1.1 or newer. It appears you are running a different recovery. Various features have been disabled."
If I boot into recovery at the top it says "CWM-based recovery v5.5.04 :: CF-v1.3"
What effect does any of that have on the above steps?
Click to expand...
Click to collapse
CWM manager is an app to manage CWM. Its pretty pointless. I dont think it works on JB ROMs though.
CWM 5 is old and should be replaced by users who want to continue using a custom recovery.
The flashing stock from Odin process will overwrite any bootloader, recovery, ROM and Baseband. Nothing you have can prevent that.
I recently rooted my T-mobile 4G Samsung Galaxy S with SuperOneClick, but I think I have decided that root is way too advanced for me. I have not installed any ROMs since rooting, is it still possible for me to reinstall Android back to the stock version safely, or has my device been permanently modified??
For those unaware of SuperOneClick, installing it did not require me to lose any data on the phone to root, which was pretty nice. I like being rooted, my inner geek lusted for it, but I have a feeling it's just not for me. Perhaps if I learned a little more about ROMs, I may go that route. Either way, I want to reinstall Android and start over.
Please respond.
Double44 said:
I recently rooted my T-mobile 4G Samsung Galaxy S with SuperOneClick, but I think I have decided that root is way too advanced for me. I have not installed any ROMs since rooting, is it still possible for me to reinstall Android back to the stock version safely, or has my device been permanently modified??
For those unaware of SuperOneClick, installing it did not require me to lose any data on the phone to root, which was pretty nice. I like being rooted, my inner geek lusted for it, but I have a feeling it's just not for me. Perhaps if I learned a little more about ROMs, I may go that route. Either way, I want to reinstall Android and start over.
Please respond.
Click to expand...
Click to collapse
You can go back to stock rom find your stock rom and flash it with odin search in google
Sent from my GT-S6102 using xda app-developers app
Double44 said:
I recently rooted my T-mobile 4G Samsung Galaxy S with SuperOneClick, but I think I have decided that root is way too advanced for me. I have not installed any ROMs since rooting, is it still possible for me to reinstall Android back to the stock version safely, or has my device been permanently modified??
For those unaware of SuperOneClick, installing it did not require me to lose any data on the phone to root, which was pretty nice. I like being rooted, my inner geek lusted for it, but I have a feeling it's just not for me. Perhaps if I learned a little more about ROMs, I may go that route. Either way, I want to reinstall Android and start over.
Please respond.
Click to expand...
Click to collapse
An easier way to do it is to install SuperSU from the market and do full unroot in settings
Thanks guys, I will definitely look into those options. If I went in the root direction, could I possibly reformat the entire phone including the SD card? I have nothing on there worth keeping and want a clean slate to start from, the phone is currently running at super slow speeds.
Double44 said:
Thanks guys, I will definitely look into those options. If I went in the root direction, could I possibly reformat the entire phone including the SD card? I have nothing on there worth keeping and want a clean slate to start from, the phone is currently running at super slow speeds.
Click to expand...
Click to collapse
yes try twrp or cwm with that format system dalvik cache, cache data or anything you want
then flash your stock rom using odin
you will get a new phone as if you bought it today
Using the XDA wiki I found here, I think I've decided I am going to attempt to install a custom ROM.
I'm already rooted w/SuperOneClick, and am still on stock Gingerbread 2.3.6. This would be classified as BLM, correct?
If I am following this wiki correctly, I am at the step of installing a kernel to obtain ClockworkMod Recovery. I did some looking around between the two choices listed, Basic With A Twist and Blast-Off!. The XDA wiki suggests that All custom kernels for this device have CWM Recovery preinstalled, but I cannot seem to verify this. I'd hate to fool around with either of the two if I cannot obtain ClockworkMod Recovery.
Double44 said:
Using the XDA wiki I found here, I think I've decided I am going to attempt to install a custom ROM.
I'm already rooted w/SuperOneClick, and am still on stock Gingerbread 2.3.6. This would be classified as BLM, correct?
If I am following this wiki correctly, I am at the step of installing a kernel to obtain ClockworkMod Recovery. I did some looking around between the two choices listed, Basic With A Twist and Blast-Off!. The XDA wiki suggests that All custom kernels for this device have CWM Recovery preinstalled, but I cannot seem to verify this. I'd hate to fool around with either of the two if I cannot obtain ClockworkMod Recovery.
Click to expand...
Click to collapse
check the thread of the kernel there should a list of features provided
if the kernel is integrated with cwm then t should be listed in the features so you can be sure about cwm
sangalaxy said:
check the thread of the kernel there should a list of features provided
if the kernel is integrated with cwm then t should be listed in the features so you can be sure about cwm
Click to expand...
Click to collapse
I looked all over the BlastOff! and Basic With A Twist pages, but could not find any information on them regarding CWM.
Double44 said:
I looked all over the BlastOff! and Basic With A Twist pages, but could not find any information on them regarding CWM.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1470716 check this thread for something and I guess there is kernel with cwm
I have a ZTE Avail 2 which I recently managed to root with Cydia Impactor. Afterwards I managed to screw it up by removing too many stock apps with Titanium. I did it carefully, one by one, and for a few days everything seemed to work fine. But then apps started force-closing, '<name of app here> has stopped working', etc. Factory reset doesnt help, it just restores me to the same screwed up state I'm in now. I already know why, it's because I removed some of the stock apps, which I now realize it needs. I'm currently stuck on the AT&T logo when powering on, it never gets any further. But even while it was messed up it was still halfway-operable, and now this. This device's subforum on Android Forums is all but non-existent, and XDA doesnt seem to have anything for it.
What I need is a 100% stock ROM (pre-rooted if possible) that I can flash, along with instructions on how to flash it. I have some experience flashing ASUS devices and Samsung devices, mainly the Transformer pad, and the Note 2, but have also rooted miscellaneous other devices in the past without alot of issues. But I have no experience with ZTE. I've already checked the manaufacturer's website for some kind of recovery software I can use to restore it, there doesnt seem to be anything.
Thanks for any help!
Stephen Wayne Hamilton said:
I have a ZTE Avail 2 which I recently managed to root with Cydia Impactor. Afterwards I managed to screw it up by removing too many stock apps with Titanium. I did it carefully, one by one, and for a few days everything seemed to work fine. But then apps started force-closing, '<name of app here> has stopped working', etc. Factory reset doesnt help, it just restores me to the same screwed up state I'm in now. I already know why, it's because I removed some of the stock apps, which I now realize it needs. I'm currently stuck on the AT&T logo when powering on, it never gets any further. But even while it was messed up it was still halfway-operable, and now this. This device's subforum on Android Forums is all but non-existent, and XDA doesnt seem to have anything for it.
What I need is a 100% stock ROM (pre-rooted if possible) that I can flash, along with instructions on how to flash it. I have some experience flashing ASUS devices and Samsung devices, mainly the Transformer pad, and the Note 2, but have also rooted miscellaneous other devices in the past without alot of issues. But I have no experience with ZTE. I've already checked the manaufacturer's website for some kind of recovery software I can use to restore it, there doesnt seem to be anything.
Thanks for any help!
Click to expand...
Click to collapse
Just out of curiosity you ever figure out a solution? I have the AIO branded version of it.
drago10029 said:
Just out of curiosity you ever figure out a solution? I have the AIO branded version of it.
Click to expand...
Click to collapse
If needed, I could back up my /system folder and send it to you.
Simba.7 said:
If needed, I could back up my /system folder and send it to you.
Click to expand...
Click to collapse
it's alright man. someone on android forums has already made a custom ROM. so the ball is rolling on out weak old device :laugh:
build.prop?
Simba.7 said:
If needed, I could back up my /system folder and send it to you.
Click to expand...
Click to collapse
did you ever get around to doing this? there is supposedly a stock image on androidforums but when I opened the Zip, all it had was the stock apps, no build.prop, which I think I blew away with xblast (xposed plugin). now I hang on the boot screen image. there is a stock Rom for the z993 our there, which I suppose I could use, because they are supposed to be the same phone, just different carriers... but then I need to get the at&t apn's and it is just a PITA. so if you could post /system backup or just a stock build.prop, that would be great!
(I'd post links to these rooms but I guess I'm too new of a member... I can provide them if needed.)
I'm way late on this, but just thought I'd post to say that I no longer have the device, and I was never able to fix it.In any case, I hope the rest of you guys get it fixed. It seemed to be a halfway decent phone, although a bit sluggish at times. But beyond that, with all the bloat removed, I'd say it ran pretty well for the duration of time that I had it (less than a month). I currently have a GNote 3 (T-Mobile) and a GNote Pro 12.2" now and it's just awesome, I'm really loving them.
Sorry, accidental double-post (can't figure out how to delete this post, the "Edit/Delete" button doesnt appear to have any option to entirely delete a post).
Just like "AnonVendetta83" messed up using Titanium.
Now desperately looking for Stock ROM or any working custom ROM to bring phone back to life.:crying:
alirezayami said:
Just like "AnonVendetta83" messed up using Titanium.
Now desperately looking for Stock ROM or any working custom ROM to bring phone back to life.:crying:
Click to expand...
Click to collapse
There is a working custom Rom for the z993 (identical hardware, different customized software for AIO, another cell provider). All you will need to do is change/update the data provider stuff so you can still use 3g and mms's. Plenty of info on this online on what needs to be changed.
You can get this Rom over at androidforums.com
http://androidforums.com/prelude-all-things-root/792279-zte-prelude-z993-stock-unrooted-rom-aio.html
There is also a cwm recovery there that works on this phone, and a partial /system backup by someone else for the z992... it is just apps and what not.
If they aren't available anymore, let me know and ill see if I still have them saved somewhere for you.
Sent from my KFTHWI using Tapatalk
AlexZap said:
There is a working custom Rom for the z993 (identical hardware, different customized software for AIO, another cell provider). All you will need to do is change/update the data provider stuff so you can still use 3g and mms's. Plenty of info on this online on what needs to be changed.
You can get this Rom over at androidforums.com
http://androidforums.com/prelude-all-things-root/792279-zte-prelude-z993-stock-unrooted-rom-aio.html
There is also a cwm recovery there that works on this phone, and a partial /system backup by someone else for the z992... it is just apps and what not.
If they aren't available anymore, let me know and ill see if I still have them saved somewhere for you.
Sent from my KFTHWI using Tapatalk
Click to expand...
Click to collapse
Thank you so very much Alex
I was wondering if I can just simply place the rom zip on the root of your sdcard and continue without doing "Install CWM - ZTE Prelude (Z993) Root&Recovery" step???
Honestly I have absolutely no idea how to do CWM steps as they come so complicated to me.
alirezayami said:
Thank you so very much Alex
I was wondering if I can just simply place the rom zip on the root of your sdcard and continue without doing "Install CWM - ZTE Prelude (Z993) Root&Recovery" step???
Honestly I have absolutely no idea how to do CWM steps as they come so complicated to me.
Click to expand...
Click to collapse
You need to install the custom recovery... It is the only way to install the zip file. If you just have the zip and go into the stock recovery I don't think you can select which zip to install
Sent from my N9002 using XDA Premium 4 mobile app
AlexZap said:
There is a working custom Rom for the z993 (identical hardware, different customized software for AIO, another cell provider). All you will need to do is change/update the data provider stuff so you can still use 3g and mms's. Plenty of info on this online on what needs to be changed.
You can get this Rom over at androidforums.com
http://androidforums.com/prelude-all-things-root/792279-zte-prelude-z993-stock-unrooted-rom-aio.html
There is also a cwm recovery there that works on this phone, and a partial /system backup by someone else for the z992... it is just apps and what not.
If they aren't available anymore, let me know and ill see if I still have them saved somewhere for you.
Sent from my KFTHWI using Tapatalk
Click to expand...
Click to collapse
AlexZap said:
You need to install the custom recovery... It is the only way to install the zip file. If you just have the zip and go into the stock recovery I don't think you can select which zip to install
Sent from my N9002 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thnx Alex
I would highly appreciate if anyone tell me what ADB Driver I should use for ZTE Z992. I almost understood all the procedure in the links but now the problem is despite I tried different ADB Drivers, but still ADB reboot-bootloader boots phone again in Normal bootloader.
Also Fastboot devices command does not see the phone, while ADB Devices command see it.
Seems bootloader is locked. Right? What should I do?
This is the method I used when I rooted my avail2 :
http://androidforums.com/zte-avail-2-zte-prelude/821217-how-root-zte-avail-2-z992-guide.html
The author (and I) just used the included drivers from zte that come with the phone. From what I remember, fastboot worked fine. Just hold the volume down button then turn the phone on. It will seem to lock on the start screen, but this is the bootloader. Then connect your cable and try your fastboot commands.
If you are already rooted, you can just download the package here
http://androidforums.com/prelude-all-things-root/797487-cwm-recovery-installer-zte-prelude.html
And skip the middle section, using the impactor to root (13 and 14).
Depending on what's wrong with your phone, you could also try just using the stock recovery and doing a system reset there. It will wipe any bad custom settings, but if the rom is still viable it might get you up and running again. It got me out of a bootloop without re-romming the whole thing. And with titanium backup or system app mover you can reinstall anything you need in the system partition.
*edit - Damn kindle auto correct
Sent from my KFTHWI using Tapatalk
A bit to much fiddling resulted in disaster
Hello XDA forum users,
I'm about ready to toss this phone in the trash. I have an AT&T Avail 2 with model number z992, which is apparently manufactured by a company called ZTE. First I think it would be helpful to explain what I've done to the phone and perhaps others out there can tell me if I've destroyed the phone or if it can be fixed.
A friend of mine sold me the phone for 10 bucks, its in great condition which is why its such a shame that it seems perma-bricked. I have no need for the phone aspect of the device, I simply wanted to "convert" it to a handheld media/application player, like an ipod or tablet for example. The phone comes with several bundled software applications that I find completely useless and wanted them removed, EX. AT&T Navigator and other AT&T software, plus a bunch of google applications.
The first thing I did when I decided to try and customize it was to use Kango's root tool which worked and rooted the phone. I was all excited that it worked and continued by installing the Super User application which allowed me to gain full control over the device. (I should have stopped there.) After the successful phone root I then installed a 3rd party app called NoBloat and used its uninstall options to remove a lot of stuff. I couldn't tell you exactly what all was removed but looking back, it must have been more important than I realized at the time. I know I took out all the AT&T software, then all the Google stuff to, which destroyed the play store. I didn't take out anything that seemed like a system file but apparently the Google stuff is the system files. The phone still worked in this state but it was erratic and things like Contacts would crash even if it was not running. So I considered that a failed attempt and commenced to do a factory reset using the recovery menu (Vol Up + Menu Key + Power button) but the factory reset didn't work, well not like it was supposed to. I had used the restore option before and it made the phone work like it was brand new. Now when the phone is powered on it will boot to the initial setup and ask me to choose a language, then it will get as far as the wireless connection screen (sometime not even that far) and the phone reports that "Unfortunately, Setup Wizard has stopped." and then I tap OK and the setup wizard restarts at the language screen. This is the state it is in now and I do not know how to fix it, I'm beginning to think there currently is no method to fix this.
Things I've tried so far include installing minimal ADB-Fastboot to try and sideload various ROM images, the ones I found here and other places. The phone is not recognized by Windows 7 though and the ADB does not work like it did on a motorola phone I did this to before. I've also purchased an inexpensive 8GB microSD chip with an adapter so I could put the ROM info on that and tried the "Update from external storage option" and that seems like it would work but none of the ROM's I've used will install. I guess because there is some kind of security feature built into the phones hardware which checks the data files for specific tags/sizes and therefore won't accept any of the ROMS I've tried.
There is no means to access the old file system anymore like most guides show, I do not have any CWM's installed nor any backup data whatsoever. It's been reset and now it seems the data it used to restore itself is, while not completely missing, damaged and will not reload anymore. All the guides I've read or watched usually show the user in the operating system or using software on a PC to type out commands. None of that works on this phone though, the phone as I just described it is basically bricked. Is there anything that can fix this, or is the phone a paper weight now? A functional ROM image from AT&T seems unlikely as they have absolutely no relevant information about this on the commercial website and the help and support seems like it's setup for old people who don't understand technology at all. If anyone out there has experience with issues like this then by all means let me know. If more information is necessary then I will be glad to provide it if available.
Alright I did manage to figure out how to make the computer see the phone as an ADB device and the minimal ADB interface shows the device now when I type ADB devices at the command prompt. Though this ADB thing seems irrelevant considering I can do the same thing by using the SD card adapter. So I don't know if this was useful or not. The ADB prompt shows a device number of P752A15.
Before I was unable to make the device show up at all in the ADB list. The problem now is how to make the phone accept a ROM, at this point I don't even care if the ROM is the default factory ROM or some random ROM made by a devoted user. The issue I encounter each time is that the built in recovery option to restore from an SD card will not accept the ROM's I've tried so far, and my research on this seems to indicate that I need a custom recovery option. This is apparently called the ClockWorkMod but as to how I install that without a functional operating system on the device is a mystery still. I've tried using a file called recovery.zip and but it does not show up when I view the contents of the SD card when the card is in the phone.
I feel like an idiot because I've done this to other phones for my family and friends, you know jailbreaking an iPhone, and rooted a Galaxy S3 once but this phone seems like its not going to be as easy as those others. I guess AT&T made sure that if you alter it, it breaks the phone. I'll check back later and see if anyone has dropped a line or two here in response to my inquiry.
Thank you and have good day.
Britton Burton said:
Alright I did manage to figure out how to make the computer see the phone as an ADB device and the minimal ADB interface shows the device now when I type ADB devices at the command prompt. Though this ADB thing seems irrelevant considering I can do the same thing by using the SD card adapter. So I don't know if this was useful or not. The ADB prompt shows a device number of P752A15.
Before I was unable to make the device show up at all in the ADB list. The problem now is how to make the phone accept a ROM, at this point I don't even care if the ROM is the default factory ROM or some random ROM made by a devoted user. The issue I encounter each time is that the built in recovery option to restore from an SD card will not accept the ROM's I've tried so far, and my research on this seems to indicate that I need a custom recovery option. This is apparently called the ClockWorkMod but as to how I install that without a functional operating system on the device is a mystery still. I've tried using a file called recovery.zip and but it does not show up when I view the contents of the SD card when the card is in the phone.
I feel like an idiot because I've done this to other phones for my family and friends, you know jailbreaking an iPhone, and rooted a Galaxy S3 once but this phone seems like its not going to be as easy as those others. I guess AT&T made sure that if you alter it, it breaks the phone. I'll check back later and see if anyone has dropped a line or two here in response to my inquiry.
Thank you and have good day.
Click to expand...
Click to collapse
Ok, been a while since I've used this phone, but hopefully this will help. I assume you have the kaw202_recoveryflasher.zip file. Once you extract it, look for the .img file. Try running these adb commands
adb.exe push cwm-z993.img /cache
adb.exe shell "su -c 'dd if=/cache/cwm-z993.img of=/dev/block/mmcblk0p17'
This should flash cwm if your phone is rooted and adb shell is working.
Sent from my KFTHWI using XDA Premium 4 mobile app
AlexZap said:
Ok, been a while since I've used this phone, but hopefully this will help. I assume you have the kaw202_recoveryflasher.zip file. Once you extract it, look for the .img file. Try running these adb commandsp
Click to expand...
Click to collapse
I have not come across that particular file yet, I did try to google it and the only results it had were two and one of those was this post. Would you mind telling me where I might find a copy of the kaw202_recoverflasher.zip?
I managed to find the zip you were talking about and have downloaded it, for anyone else looking for it. I am unable to post links but I would have linked to the files you mentioned. For others looking for the same zip file search for "CWM Recovery Installer ZTE PRELUDE". That's the title of the thread I found the file on that Alex mentioned above. The instructions on the page don't seem like they apply to the situation I'm stuck in but I'll give it a whirl anyway and see if the files work.
If this forum is like the others I've read through so far then there is no real answer to the issue. The phone seems kind of new and not many of the power users on these forums use rinky dink phones like this one. You guys all have the 600 dollar models I guess. What bugs me about this this phone and the state I managed to put it in, is that the damn thing was programmed the first time when it was made. So it seems to me like there should be a way to reprogram the phone the same way the factory did it. Think about it, when they make the phones they don't have any information on the phone at all. It's completely empty, so there must be a way to load the software for the phone even if the phone has no data at all in the main storage. If the files in the recovery flasher.zip file work then I'll post back the results but if it's like the other files I've messed around with (which didn't do anything) then I'm throwing it in the trash can.
Anyway thanks for your response and for pointing me in a different direction Alex
---------- Post added at 09:15 PM ---------- Previous post was at 08:39 PM ----------
HELL YEAH!!! It worked thank you Alex,
I would have never figured this out without your help! The phone now has a version of CWM on it and the recovery menu is different. I just tried to install a ROM and it said successful. After the phone rebooted went back to the setup screen from ZTE but it still did the same thing. However this is progress and I should be able to "wander in the dark" and figure out a way to use the CWM to install a completely new rom. Any recommendations on a ROM to use for the z992?
Good news, I was able to fix it using the information Alex guided me to find. Since there doesn't appear to be a stock AT&T version of the ROM I ended up using the Azazel ROM. Which at first failed even though it was installed, this I determined was due to the old ROM image still being partially active on the system partition. So I formatted the system partition to and tried again. This time it worked and the phone seems fully functional again, and best of all the annoying bloatware is not present and the apps are not crashing. I consider this issue resolved. Thank you again Alex I will be sure to leave a thanks on your post.
Britton Burton said:
Good news, I was able to fix it using the information Alex guided me to find. Since there doesn't appear to be a stock AT&T version of the ROM I ended up using the Azazel ROM. Which at first failed even though it was installed, this I determined was due to the old ROM image still being partially active on the system partition. So I formatted the system partition to and tried again. This time it worked and the phone seems fully functional again, and best of all the annoying bloatware is not present and the apps are not crashing. I consider this issue resolved. Thank you again Alex I will be sure to leave a thanks on your post.
Click to expand...
Click to collapse
ze
Glad I could help, but none of the work was done by me, the guys over at android central did all the heavy lifting, I just pointed you in the right direction. I have a stock system e m image around here somewhere if you need it, tho installation will be a bit more complicated. If azazels rom ever gives you issues, ill dig it up and try and help you install it.
Sent from my KFTHWI using XDA Premium 4 mobile app
Some people say that trying to root this device will brick their phones and will need to do a hard reset. How will I go about rooting this device successfully. I have searched around for a few hours and my questions have not been put to ease. My S5 came in the mail today refurbished as a replacement for my malfunctioning Nexus 5 (they didn't have another in stock so they just sent me an S5). I knew that I was going to get, a slow and inefficient software paired with great hardware so I would love to install CM 13 on it. How would I go about doing this successfully without bricking my device? I am also a complete novice when it comes to tampering with custom roms and recoveries in smartphones.
CrippledChoclate said:
Some people say that trying to root this device will brick their phones and will need to do a hard reset. How will I go about rooting this device successfully. I have searched around for a few hours and my questions have not been put to ease. My S5 came in the mail today refurbished as a replacement for my malfunctioning Nexus 5 (they didn't have another in stock so they just sent me an S5). I knew that I was going to get, a slow and inefficient software paired with great hardware so I would love to install CM 13 on it. How would I go about doing this successfully without bricking my device? I am also a complete novice when it comes to tampering with custom roms and recoveries in smartphones.
Click to expand...
Click to collapse
There is a great thread right in the the other subforum for our phone:
http://forum.xda-developers.com/tmo...l/root-how-to-root-sm-g900t-firmware-t3358190
However, you only need to root stock ROMs. If you flash a non-stock ROM, they will be already rooted. This includes CM ROMs.
To flash, you either need ODIN (runs on a PC) or Flashfire (runs on the phone).
There are several ROMS here that work on the phone:
http://forum.xda-developers.com/tmobile-galaxy-s5/development
If you are on T-Mobile, and you want to keep WiFi Calling, then you need to stay with a ROM that is based on a TouchWiz stock ROM. I currently run Vision:
http://forum.xda-developers.com/showthread.php?t=2797336
You can also run ROMs developed for the international version of the phone, but you lose WiFi Calling.
Another thing, to make sure is that you have a SM-G900T or SM-G900T3. I recently got a T3 when I had my S5 replaced. The same ROMs will run on both, however the bootloader and modem are different. So, you can't flash T firmware on a T3. But, they can run the same ROMs.
Most ROMs will have instructions in their first post as to how to flash.
Rob
i dont remember T3 existing, interesting
the idea should be: copy the CM zip file onto the stock phone -> boot into download mode -> use odin (or heimdall) to flash TWRP without reboot -> remove battery after the flashing is complete while it's still plugged in -> insert battery & boot into recovery -> install CM zip & make sure cache type things are wiped -> boot normally
your thread title asks about rooting, so technically installing CM is a very different thing, yes it gives root but it also means different interface, loss of several samsung & camera features
kn00tcn said:
i dont remember T3 existing, interesting
the idea should be: copy the CM zip file onto the stock phone -> boot into download mode -> use odin (or heimdall) to flash TWRP without reboot -> remove battery after the flashing is complete while it's still plugged in -> insert battery & boot into recovery -> install CM zip & make sure cache type things are wiped -> boot normally
your thread title asks about rooting, so technically installing CM is a very different thing, yes it gives root but it also means different interface, loss of several samsung & camera features
Click to expand...
Click to collapse
Sorry for the late answer, but I already managed to root the phone and install CM 13 three days ago. It was also easier than the instructions you showed. Thanks anyway!
kn00tcn said:
i dont remember T3 existing, interesting
the idea should be: copy the CM zip file onto the stock phone -> boot into download mode -> use odin (or heimdall) to flash TWRP without reboot -> remove battery after the flashing is complete while it's still plugged in -> insert battery & boot into recovery -> install CM zip & make sure cache type things are wiped -> boot normally
your thread title asks about rooting, so technically installing CM is a very different thing, yes it gives root but it also means different interface, loss of several samsung & camera features
Click to expand...
Click to collapse
I haven't found what the differences are, but the newest MM firmware has 3 different versions: T, T1 and T3.
Rob
rlichtefeld said:
I haven't found what the differences are, but the newest MM firmware has 3 different versions: T, T1 and T3.
Rob
Click to expand...
Click to collapse
The T, T1, and T3 are actually 3 slightly different model phones, all designed to run on either T-Mobile or one of the carriers that runs on its networks such as MetroPCS. Check Settings > About device > Model number. Match what you see there with the firmware you use. Most people with the T-Mobile Galaxy S5 have the SM-G900T but I have seen a few posters here with either SM-G900T1 or SM-G900T3.
For the sake of specificity I'm pretty sure the SM-G900T1 is the MetroPCS model, I could be mistaken
thisisapoorusernamechoice said:
The T, T1, and T3 are actually 3 slightly different model phones, all designed to run on either T-Mobile or one of the carriers that runs on its networks such as MetroPCS. Check Settings > About device > Model number. Match what you see there with the firmware you use. Most people with the T-Mobile Galaxy S5 have the SM-G900T but I have seen a few posters here with either SM-G900T1 or SM-G900T3.
For the sake of specificity I'm pretty sure the SM-G900T1 is the MetroPCS model, I could be mistaken
Click to expand...
Click to collapse
I believe the T was the original T-Mobile version. But, I received a T3 version from T-Mobile a month ago for a replacement for a broken T that I had. I only realized I had a T3 when I went to flash the day I received it and couldn't figure out why what had worked with my original phone, didn't with the new one. Then, I finally realized there was a difference in the model number.
Rob