Related
MOD EDIT: Ronjoe requested i put the link to droidstyle's guide in here:
http://forum.xda-developers.com/showthread.php?t=1238070
Foreword:
After scouring these forums for a guide for getting CM7 on the Fascinate, I found myself a bit confused and lost. I set out to create a new guide using what I learned from the others, and this is what came out of that.
Anyways, let me start this thing...
*clears throat*
Oops! It seems you've gotten into a bit of trouble! You may have been trying to stick a square peg in a round hole, fly too close to the sun, or perhaps run with a plasma sword. In any case, you've bricked your phone, and you have resorted to seeking help on the interwebz. Well look no further! Uncle Ronjoe can solve all of your Fascinate-ing problems!
Let us begin...
0. Gather everything we need:
i. Obviously, your phone and its USB cable.
ii. Download the files for this guide and extract them to a convenient place on your computer.
Please take note of some important information about this guide:
You must use an OEM cable for the Fascinate.
Regardless of whether your phone is bricked, on another ROM, or doing this for the first time, the steps are the same. Just follow along with the instructions.
If anything goes wrong, you've just bricked the phone again. It's not a big deal: just start over from the beginning of the guide.
Once you have installed CWM, NEVER use the "three-finger salute" (Volume Up, Volume Down, and Power) to enter recovery. This will remove CWM and replace it with stock recovery. Instead, use ADB, terminal, or an app to reboot into recovery.
Real men index their lists at 0. Just sayin'.
1. Make sure you have the official Samsung drivers installed.
NOTE: If you have used Heimdall in the past, you need to uninstall that driver (read its readme) and reinstall the official Samsung ones. If not, don't worry about it.
2. Put your phone in download mode:
i. Turn off the phone and remove the battery.
ii. Press and hold the Volume Down button.
iii. While holding Volume Down, plug the USB cable into the phone.
iv. If you now see a yellow "Download Mode" screen, you're in download mode.
3. Extract the zip and open Odin.
4. If Odin recognizes the phone, a yellow bar will appear under the top left square, and it should say "Added!" in the message box on the bottom left. If Odin does not see the phone, go back to Step 0 and double check everything.
If you are starting with stock firmware for the phone and just want CM7, feel free to skip ahead to step 9.
5. Place Atlas_v2.2.pit in the PIT section.
6. Place the EH03 image in the PDA section (NOT PHONE!!!).
7. Click "Start" and go grab a Snickers. This will take a while.
8. When you see "PASS" in the box, the phone will shut down. Reinsert the battery.
If all you want is stock, you can stop here. But if you want CM7, then follow the rest of this guide.
9. Reboot the phone.
10. Put the zips for CM7 and Google Apps on your SD card.
11. Put the phone in download mode and open Odin again.
12. Put the fixed CWM4 in the PDA section. Hit "Start."
13. Boot the phone into recovery. It should do it automatically the first boot. If it doesn't and it boots completely to stock Android, use terminal or adb to reboot it in recovery. (DO NOT use the three-finger salute)
It should be CWM v 4.0.1.0.
14. Now in CWM, Flash CM7:
i. Wipe data, cache partition, and Dalvik cache (under Advanced)
ii. Still in CWM, go to "Install .zip from sdcard." Select the CM7 zip and install it (You may want to get another Snickers). The screen might go blank a few times. This is normal.
iii. Reboot the phone.
15. After the phone boots up to CM7 completely, reboot to recovery. (either perform step 13, or long-press the power button, select reboot, and choose recovery). At this point, if your touchscreen does not work, just reboot CM7 by pulling the battery. (DO NOT do a three-finger salute)
It should be CWM v 5.0.2.6.
16. Once again in CWM, wipe cache and Dalvik (but NOT DATA) and go to "Install .zip from sdcard." Choose the GApps zip and install it.
17. Reboot. The GApps installer should now run.
18. (Optional) Go back into CWM and make a backup, so you don't brick the phone again.
19. ???
20. PROFIT! I told you there would be profit, didn't I?
Comments, questions, or suggestions? Feel free to speak your mind! If your question isn't obvious or answered already, I might even respond! If it is, well, you'll figure it out soon enough.
suggestion: dont knock others contributions to the community...makes you look like a....well ill let you fill in the blank.
Well sir, although I appreciate your attempted contribution to the community, I must strongly disagree with your "reasons" for thinking "THE GUIDE" is in some odd way " inadequate ". Many in this community have used, and referred many new users seeking help and advice, to this Guide with great success. Also, as mentioned by above OP, don't knock the hard work and contributions by other Devs. It really does make you look like a......well you know.
Sent from my SCH-I500 using XDA App
Sorry, I was in the wrong frame of mind when making the guide. I didn't mean to offend. Rather, I hoped that the comment would prompt the other guidemakers to fix their mistakes.
All I can say is that droidstyles guide has been my flash bible and has never failed me. If there were any errors, why not simply PM him with suggestions? He has always seemed to appreciate and incorporate feedback.
Ronjoe said:
Sorry, I was in the wrong frame of mind when making the guide. I didn't mean to offend. Rather, I hoped that the comment would prompt the other guidemakers to fix their mistakes.
Click to expand...
Click to collapse
Let's see......You've been a member since January 2011 and in a little over a year you've only managed to contribute 7 posts to these forums. You haven't been helping people, answering questions, and providing guidance on a daily basis like the members you are disparaging and insulting first with your OP "oh look these other people are morons and have made completely confusing guides so I'm making one that is so much moar better", and second after your insulting demeanor is pointed out to you, you say you weren't in the right frame of mind then go right back to insulting by pointing out that the other guide makers need to "fix their mistakes." Pretty much confirms you are a........well you know.
--snip--
EDIT: Sometimes saying nothing is better for eveyone involved.
Ronjoe said:
--snip--
EDIT: Sometimes saying nothing is better for eveyone involved.
Click to expand...
Click to collapse
I guess I can see your side of it too. However a simple search would have landed you on droidstyles guide. But some of the comments have gone a bit too far. Its not like your an 11 year old named twinkie
Sent from my SCH-I500 using XDA App
Hello
My phone tells me that it is ready to update to Kit Kat.
Before I install Kit Kat I would like to learn how to go back to Jelly Bean if things go t1ts-up.
So, I would like to learn how to root my phone?
I would also like to learn how to backup everything including the Jelly Bean operating system, and I would like to know how to revert my phone back to Jelly Bean?
Please forgive my ignorance, but this whole process genuinely scares me. I have only ever rooted my Samsung Ace phone once and the experience left a bitter taste in my mouth.
I did manage to root my phone. I also thought that I had created a backup but when I tested the backup I discovered that my phone got wiped and I ended up with a brick. I eventually found an official Samsung ROM but it wasn't the one I wanted and it caused a few problems, especially with the Bluetooth feature.
I hope you can understand or appreciate my apprehension with even contemplating such a task on my expensive Nexus 4.
Cheers muchly
the lemming said:
Hello
My phone tells me that it is ready to update to Kit Kat.
Before I install Kit Kat I would like to learn how to go back to Jelly Bean if things go t1ts-up.
So, I would like to learn how to root my phone?
I would also like to learn how to backup everything including the Jelly Bean operating system, and I would like to know how to revert my phone back to Jelly Bean?
Please forgive my ignorance, but this whole process genuinely scares me. I have only ever rooted my Samsung Ace phone once and the experience left a bitter taste in my mouth.
I did manage to root my phone. I also thought that I had created a backup but when I tested the backup I discovered that my phone got wiped and I ended up with a brick. I eventually found an official Samsung ROM but it wasn't the one I wanted and it caused a few problems, especially with the Bluetooth feature.
I hope you can understand or appreciate my apprehension with even contemplating such a task on my expensive Nexus 4.
Cheers muchly
Click to expand...
Click to collapse
You might want to check out the Wugfresh's toolkit if you are not incline with technical stuff. The toolkit is in the Development section.
Hello
I have no idea what Wugfresh's tool-kit is.
Sorry
the lemming said:
Hello
I have no idea what Wugfresh's tool-kit is.
Sorry
Click to expand...
Click to collapse
I would suggest that you study up and follow this guide here. http://forum.xda-developers.com/showthread.php?t=2010312
I was like you when I first got the nexus. Didn't know what to do and the steps seems to be so complicated. Hell..I even took couple of days to finally succeed in installing the drivers. And for me I think it is better to learn the basics of using adb before trying out the toolkits. If you start with toolkits and you will later on rely entirely on the toolkits. This is not good as some problems, the toolkits might not be able to solve it for you.
Btw, look into original android development for wug's toolkits. It is pinned there. Should be easy to find.
Sent from my Nexus 4 using xda premium
You seem to be taking interest in Rooting and stuffs. I would suggest you to get handy with a few ADB and FASTBOOT commands and you won't need any toolkit ever in Life !!!
Its very very very easy in Nexus Devices.
Here is my attempt to make you learn :-
1. Say Bye Bye to your phone OS version.
2. Open Command Prompt or Terminal.(Assuming, you have SDK & Drivers installed)
Code:
adb devices
It shall return you the device id.
3. Reboot to BootLoader
Code:
adb reboot-bootloader
4. Check for your device's recognition in FastBoot Mode.
Code:
fastboot devices
5. I assume you have all the files(Factory Image tar.gz extracted to a folder)
just type :-
Code:
flash-all.bat
BOOM...
You are now on stock KitKat !
Now, To get a Custom Recovery (IMHO go with TWRP),
1. Download latest recovery from the official website.
2. Type when in FastBoot Mode.
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.4-mako.img
(Or whatever the name is)
3. Reboot your device.
Now, to get the ROOT ACCESS, after booting up the device,
1. Download the latest UPDATE-SuperSU zip from here.
2. Keep it somewhere in DEVICE STORAGE.
3. open TWRP RECOVERY
4. FLASH that ZIP
5. HIT THANKS !
Have Fun ...
Welcome to the Flashing Fraternity !!! LOL
miku3191 said:
You seem to be taking interest in Rooting and stuffs. I would suggest you to get handy with a few ADB and FASTBOOT commands and you won't need any toolkit ever in Life !!!
BOOM...
You are now on stock KitKat !
Click to expand...
Click to collapse
Hello
Thank you for replying but I fear that I will not be following your advice at the moment.
I initially asked how to ROOT my phone so that I can learn how to do backups and recoveries. My phone is ready for the Over The Air official upgrade.
I want to take things one step at a time rather than causing problems by blindly following code.
Sorry
the lemming said:
Hello
Thank you for replying but I fear that I will not be following your advice at the moment.
I initially asked how to ROOT my phone so that I can learn how to do backups and recoveries. My phone is ready for the Over The Air official upgrade.
I want to take things one step at a time rather than causing problems by blindly following code.
Sorry
Click to expand...
Click to collapse
If you want official OTA update of KitKat you should update it, and after that unlock bootloader and root phone. That way nothing will go wrong.
If you unlock bootloader and root your phone OTA update will cause problems like stuck in bootloop(your phone will be stuck on nexus logo and it will never boot into android)
If you want to learn about rooting I suggest you this http://forum.xda-developers.com/showthread.php?t=2367406
this is excelent tutorial how to root your nexus 4 http://forum.xda-developers.com/showthread.php?t=2018179
and if you are more comfortable to hear and see somebody do it you can check out this page it have video of full process and pictures for every step http://nexus4root.com/nexus-4-root/how-to-root-nexus-4-windowsmac-osxlinuxubuntu/
Good luck!:cyclops:
miku3191 said:
You seem to be taking interest in Rooting and stuffs. I would suggest you to get handy with a few ADB and FASTBOOT commands and you won't need any toolkit ever in Life !!!
Its very very very easy in Nexus Devices.
Good luck!:cyclops:
Click to expand...
Click to collapse
This process is an absolute nightmare.
All I want to do is back-up my Jelly Bean phone operating system and have it safe in case the OTA Kit Kat goes wrong. I thought that this was sensible and safe practice before doing any updates, especially something as serious as a system update?
I have now tried several Tutorials on how to root my phone and all I have succeeded in doing is wiping my phone clean and returning it to Factory Settings. The latest Tutorial was here
http://forum.xda-developers.com/showthread.php?t=2010312
I followed the following advice to this point
1) All of the files that are required, need to be in one (i.e., the same) directory. It does not matter what it is called, but all the files need to be in there, with NO subfolders. EVERYTHING needs to be extracted into this one directory;
2) Download the attachment from the end of this post and extract the contents to the directory created in step 1. (Latest version for Windows is here). Note: if all you want to do is unlock your bootloader, skip to step 7 in this section (C).
7) Reboot your device into bootloader mode (by turning it off, hold volume down, and press and hold power) and plug it into your computer;
8) Open a command prompt in the same directory (i.e., make sure you are in the same directory as your files are located). You can hold the shift key when you are in the folder in Windows explorer and right-click in a blank spot and it will open a command prompt.
I then get to the bit about rooting
E. Optional -- Root
If you want to get root access follow the steps below. (And no, this will not flash a custom recovery, and not, it will not make you "not stock".) Unlocked bootloader required. See steps above.
1) Download (to your computer) the latest version of CWM (from here) or TWRP (from here) for your device;
http://www.clockworkmod.com/rommanager/
http://www.clockworkmod.com/rommanager/developers/mako?name=Google Nexus 4
And when I click the link I am blinded by options. This is a nightmare.
Could somebody please cut through all this hyperbole and just explain how I get ROOT?
I have been at this for 24 hours solid.
the lemming said:
This process is an absolute nightmare.
All I want to do is back-up my Jelly Bean phone operating system and have it safe in case the OTA Kit Kat goes wrong. I thought that this was sensible and safe practice before doing any updates, especially something as serious as a system update?
I have now tried several Tutorials on how to root my phone and all I have succeeded in doing is wiping my phone clean and returning it to Factory Settings. The latest Tutorial was here
http://forum.xda-developers.com/showthread.php?t=2010312
I followed the following advice to this point
1) All of the files that are required, need to be in one (i.e., the same) directory. It does not matter what it is called, but all the files need to be in there, with NO subfolders. EVERYTHING needs to be extracted into this one directory;
2) Download the attachment from the end of this post and extract the contents to the directory created in step 1. (Latest version for Windows is here). Note: if all you want to do is unlock your bootloader, skip to step 7 in this section (C).
7) Reboot your device into bootloader mode (by turning it off, hold volume down, and press and hold power) and plug it into your computer;
8) Open a command prompt in the same directory (i.e., make sure you are in the same directory as your files are located). You can hold the shift key when you are in the folder in Windows explorer and right-click in a blank spot and it will open a command prompt.
I then get to the bit about rooting
E. Optional -- Root
If you want to get root access follow the steps below. (And no, this will not flash a custom recovery, and not, it will not make you "not stock".) Unlocked bootloader required. See steps above.
1) Download (to your computer) the latest version of CWM (from here) or TWRP (from here) for your device;
http://www.clockworkmod.com/rommanager/
http://www.clockworkmod.com/rommanager/developers/mako?name=Google Nexus 4
And when I click the link I am blinded by options. This is a nightmare.
Could somebody please cut through all this hyperbole and just explain how I get ROOT?
I have been at this for 24 hours solid.
Click to expand...
Click to collapse
The point you are missing is that your fear is clouding your ability to simply read and comprehend the proper steps to take. My friend rooting your phone with a toolkit is a simple task but you ask what is Wugs toolkit instead of taking the time to search for it an read up. YOu do not want to root your phone but to have someone do it for you. I used to do this for people back in the days where I would log into their pc and root their phones from my home.
My friend its simple your bootloader is unlocked and now all you need to do is push a recovery over to your phone. Now go to the TWRP thread and download the image file and follow the instructions given to you to flash the recovery. I fear if following these simple directions are too much for you maybe you should simply leave your phone alone before the next step is you calling Google with an issue or having to buy another phone...
Sorry but thats my honest opinion....
Edit: Boot into bootloader and check to see if its says unlocked. If so then all thats left is flashing a recovery
the lemming said:
This process is an absolute nightmare.
And when I click the link I am blinded by options. This is a nightmare.
Could somebody please cut through all this hyperbole and just explain how I get ROOT?
I have been at this for 24 hours solid.
Click to expand...
Click to collapse
Reading your posts, I understand your frustration. Here are my suggestions, 1) step away from your PC for a few minutes or an hour or get a cup of water, 2) put the phone aside, 3) read and re-read the information in Google Nexus 4 threads just to get the knowledge first and then start working on your phone. You will be doing fine. BTW, you should have a back up phone that you can use while working on your Nexus 4.
playya said:
Edit: Boot into bootloader and check to see if its says unlocked. If so then all thats left is flashing a recovery
Click to expand...
Click to collapse
Thank you for this useful bit of information.
the lemming said:
Thank you for this useful bit of information.
Click to expand...
Click to collapse
You got it man I know but sometimes the truth hurts... You have been given all the information laid out for you in the posts above. If this is still too difficult for you your only other task is to actually have somebody do it for you this is nothing more than simply reading and taking your time. I tell you this with all sincerity I would rather see you stop now than later see another thread created by you saying possibly bricked
Sent from my Nexus 4 using Tapatalk
---------- Post added at 02:51 PM ---------- Previous post was at 02:51 PM ----------
playya said:
You got it man I know but sometimes the truth hurts... You have been given all the information laid out for you in the posts above. If this is still too difficult for you your only other task is to actually have somebody do it for you this is nothing more than simply reading and taking your time. I tell you this with all sincerity I would rather see you stop now than later see another thread created by you saying possibly bricked
Take care
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Sent from my Nexus 4 using Tapatalk
the lemming said:
And when I click the link I am blinded by options. This is a nightmare.
Could somebody please cut through all this hyperbole and just explain how I get ROOT?
I have been at this for 24 hours solid.
Click to expand...
Click to collapse
I trust that you have read the entire guide from that link you post. To get you see this clearly. Rooting is very easy. You just have to:
1. Install driver, download platform-tools (if you don't wanna download the entire android sdk) and SuperSU I trust that all the links are given in that guide.
2. Make sure you device is detected in adb. Copy SuperSU.zip into your device.
3. Unlock your device.
4. Push recovery. fastboot flash recovery recovery name.img
5. Reboot into recovery and flash SuperSu.zip
6. Reboot. Done.
Really..this is all it takes to perform a simple rooting. But if you're not the one who likes to read..and try to understand the steps. I suggest you not to mess with your device. You are more likely to brick it than make it better. The truth hurts but it is for your own good. Unless you prove me wrong. Then you are awesome instead
Sent from my Nexus 4 using xda premium
So here's my story,
I bought this Zte phone off someone on craigslist a couple of weeks ago, and I've loved it every since. In fact, I have yet to turn it off, I've kept it on the entire time. Today the new update 29 came out for the US, and I tried downloading. To my dismay when the phone restarted I was greeted with a bootloader screen, and then a TWRP screen. I freaked out and panicked and emailed the guy I bought the phone from since I heard that unlocking bootloader on your phone voids the warranty. He told me he had done it in such a way OTA framework that it didn't void the warranty and also I can always relock the phone but be careful because I might brick it. I'm not a very tech savvy person and have no idea what to do to relock the phone so I can download this new update. Could someone please help me out and walk it out with me step by step so I know what to do. Thanks so much guys!
Look in the section rooms, recoveries,etc... look for one the says roms update stock DrakenFX
Since you are not tech savvy, you could just keep it unlocked and use those twrp flashable files to update B29.
http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
credit: @DrakenFX
However If you will wish to restore to locked state without twrp, I will be happy to guide you but you'll have many more steps to do.
Nik2424 said:
Since you are not tech savvy, you could just keep it unlocked and use those twrp flashable files to update B29.
http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
credit: @DrakenFX
However If you will wish to restore to locked state without twrp, I will be happy to guide you but you'll have many more steps to do.
Click to expand...
Click to collapse
I would much rather just restore to locked state without twrp so I don't have to worry about this situation again. I don't need bootloader or twrp and just wanna remove both. Would you please guide me through this?
ctran1996 said:
I would much rather just restore to locked state without twrp so I don't have to worry about this situation again. I don't need bootloader or twrp and just wanna remove both. Would you please guide me through this?
Click to expand...
Click to collapse
http://forum.xda-developers.com/axon-7/how-to/b20-factory-image-posted-t3492552 click the link in this post. It will take you to the ZTE site with the official B20 firnware. You flash this in stock recovery and you will have a fully locked Axon 7.
tabletalker7 said:
http://forum.xda-developers.com/axon-7/how-to/b20-factory-image-posted-t3492552 click the link in this post. It will take you to the ZTE site with the official B20 firnware. You flash this in stock recovery and you will have a fully locked Axon 7.
Click to expand...
Click to collapse
How do I flash to stock recovery with teamwin keeps popping up and restarting and not allowing me to flash it?
ctran1996 said:
I would much rather just restore to locked state without twrp so I don't have to worry about this situation again. I don't need bootloader or twrp and just wanna remove both. Would you please guide me through this?
Click to expand...
Click to collapse
If you're not tech savvy, you probably don't want to do this. It's not simple and for whatever reason, some people (who would consider themselves more tech savvy) have had some issues.
Your best bet is to copy all of your data from internal memory (just in case), flash a new copy of TWRP (recovery only, you don't need to do boot) using tenfar's tool (http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204), then follow the steps in DrakenFX's thread to get B29: http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
I'm happy to write you a guide for getting back to bone stock, but I'm not going to do it until next week when I have time at work and as I said earlier, some folks have had issues. For what it's worth, you likely won't hard brick the phone. So far, we've only seen soft bricks AFAIK.
rczrider said:
if you're not tech savvy, you probably don't want to do this. It's not simple and for whatever reason, some people (who would consider themselves more tech savvy) have had some issues.
Your best bet is to copy all of your data from internal memory (just in case), flash a new copy of TWRP (recovery only, you don't need to do boot) using tenfar's tool (http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204), then follow the steps in DrakenFX's thread to get B29: http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
I'm happy to write you a guide for getting back to bone stock, but I'm not going to do it until next week when I have time at work and as I said earlier, some folks have had issues. For what it's worth, you likely won't hard brick the phone. So far, we've only seen soft bricks AFAIK.
Click to expand...
Click to collapse
Are they really hard to follow?? I mean my guides?
If I could I love to redo Tenfar tool guide ,but don't think he will allow me recreate that thread in a more clean way (guide wise)
ctran1996 said:
How do I flash to stock recovery with teamwin keeps popping up and restarting and not allowing me to flash it?
Click to expand...
Click to collapse
http://www.mediafire.com/file/1jw9b24glt5fd7t/recovery.img put this on your SD card
Boot to TWRP
Push Install (top left)
Push Install Image (bottom right)
find the recovery.img and push it - TWRP will install it for you.
Then reboot into recovery.
You will now be in stock recovery and can use it to install update from SD card and install the B20 firmware from ZTE
BE WARNED - THIS WILL FACTORY RESET YOUR PHONE WHEN YOU ARE DONE!!!!!
DrakenFX said:
Are they really hard to follow?? I mean my guides?
If I could I love to redo Tenfar tool guide ,but don't think he will allow me recreate that thread in a more clean way (guide wise)
Click to expand...
Click to collapse
Hah, no, your guides are not hard to follow. They're great
I think the bigger problem is that there are a lot of threads to wade through and there are various posts within in each thread that address specific issues users have run into. If someone who claims not to be "tech savvy" doesn't understand something in your thread (not because it's unclear but because they have zero experience with this and need some hand-holding) and then happens to read something else in the thread and tries that, it can get messy.
rczrider said:
Hah, no, your guides are not hard to follow. They're great
I think the bigger problem is that there are a lot of threads to wade through and there are various posts within in each thread that address specific issues users have run into. If someone who claims not to be "tech savvy" doesn't understand something in your thread (not because it's unclear but because they have zero experience with this and need some hand-holding) and then happens to read something else in the thread and tries that, it can get messy.
Click to expand...
Click to collapse
That is my problem entirely! I AM tech savvy as I have worked as a Microsoft/VMware Systems engineer for over 20 years and when I try to make heads or tails of doing some of the things necessary to flash a ROM, or root, or unlock the bootloader.... after my eyes glaze over I just stick with Nova Prime and hope the original manufacturers get everything worked out. What's really needed is a well written manual detailing step-by-step basics on what all these various things do as well as how to do them. Then more specific guides on a per phone basis. I know, it's asking too much! LOL :silly:
ctran1996 said:
So here's my story,
I bought this Zte phone off someone on craigslist a couple of weeks ago, and I've loved it every since. In fact, I have yet to turn it off, I've kept it on the entire time. Today the new update 29 came out for the US, and I tried downloading. To my dismay when the phone restarted I was greeted with a bootloader screen, and then a TWRP screen. I freaked out and panicked and emailed the guy I bought the phone from since I heard that unlocking bootloader on your phone voids the warranty. He told me he had done it in such a way OTA framework that it didn't void the warranty and also I can always relock the phone but be careful because I might brick it. I'm not a very tech savvy person and have no idea what to do to relock the phone so I can download this new update. Could someone please help me out and walk it out with me step by step so I know what to do. Thanks so much guys!
Click to expand...
Click to collapse
OK. Step by Step to get it back to B20
1) Move anything you want to save off your internal storage to your sd card or computer.
2) Download B20 image button.
3) Save file to SD card
4) Boot into Recovery by shutting it down and then push Volume Up Button+Power Button
5) When screen comes up boot into Recovery
6) in TWRP click Install, choose Select Storage, Choose Micro SDCard, Locate your update.zip file and click it
7) Swipe to confirm flash
WARNING: This will clean out your phone and turn it to B20. @DrakenFX can tell you how to not wipe the internal storage if you want to edit the update.zip file.
Hope this helps.
Thank you this is exactly what I was looking for. However, when I tried this the other day, it reset my phone as planned, but TWRP and bootloader were still on there. Any way of getting them off?
swehes said:
OK. Step by Step to get it back to B20
1) Move anything you want to save off your internal storage to your sd card or computer.
2) Download B20 image button.
3) Save file to SD card
4) Boot into Recovery by shutting it down and then push Volume Up Button+Power Button
5) When screen comes up boot into Recovery
6) in TWRP click Install, choose Select Storage, Choose Micro SDCard, Locate your update.zip file and click it
7) Swipe to confirm flash
WARNING: This will clean out your phone and turn it to B20. @DrakenFX can tell you how to not wipe the internal storage if you want to edit the update.zip file.
Hope this helps.
Click to expand...
Click to collapse
Preamble
Hello, all.
Soooo I've never posted on this forum before. I've mainly leeched the invaluable info for my personal gain. I'm sure many a googler has come here trying to figure out how to root their phone. And I'm sure many a "swimmer" in Schitz Creek has come here via Google to figure out how to save their device from what had been perceived as an upgrade. I'm speaking, of course, of trying to root/unlock a phone and finding said phone "bricked".
Well, it’s time to give back.
Because yesterday, I was neck deep in Schitz Creek. After a series of dumb decisions and a lack of knowledge, I bricked the phone I’d bought for my wife’s birthday. I was just trying to be able to delete the Asus bloatware and install titanium backup and greenify. By the way, since when did Facebook become a system app? How is this a thing? Anyways, my wife deserves better battery life. And it’s fun to feel like Cyber MacGuyver by rooting a phone. But the situation went awry. My wife kept telling me that everything was going to be alright, but I know the limitations of my knowledge.
Brief aside: I'm decently computer/phone savvy, but I would, in no way, consider myself an advanced user. Sure, to my family, I'm a computer wizard. But that doesn't mean a whole lot. To them, opening up a command prompt in Windows is seen as an act of magic. And I haven't had my planeswalker spark yet. However, I have successfully rooted, and in most cases unlocked the bootloader, for several phones (HTC desire, Galaxy S3 [three different models over three years], Asus Zenfone 5, LG G4 [once pre-motherboard-death and once post (after a downgrade)], and now the ZE552KL). So I know how to at least fumble my way around adb, fastboot, odin, and various recoveries. As long as you’re at this level, or willing to learn, then you should be able to follow these instructions. End aside.
Mistakes not to make
Let’s get down to brass tacks. I made two big mistakes that you shouldn’t make. Both mistakes stemmed from the basic mistake of using a root method other than this one: https://forum.xda-developers.com/zenfone-3/help/guide-how-to-root-zenfone-3-ze552kl-t3471524
The problem with not using this EXACT method is that some of the files/programs which you need to use have specific versions which will ensure an easypeasy root. Honestly, if you properly follow the instructions in the above post, you will most likely not run into any problems. The only addition I can make is that instead of steps 6 and 7, you might find it easier to install SuperSU.zip through TWRP instead of pushing and sideloading.
Mistake 1: Not using the proper TWRP file and SuperSU file
For some reason, there are multiple versions of these files. Your SuperSU file should be 4.8MB. Using the wrong SuperSU will break the dm-verity. Your TWRP should NOT be the latest experimental version. It should be the one from November or earlier of 2016. Using the wrong TWRP will leave you unable to use the touchscreen. Trust me. I know from experience.
Mistake 2: KEEP TWRP READ ONLY
Disabling read only has no current benefits. It will just break the dm-verity. Your device will still be able to be written to if you keep TWRP read only. I have no idea why it’s called “read only”.
How to unbrick the phone
I’m sure some of you skipped straight to here. While I can’t blame you, please at least read the above paragraph. It will help you.
First I will describe the situation the phone was in, and then I will explain how I saved it. Before I continue, I want to give a big shout out to Niemer. Without their helpful post, I would’ve had no idea what to do. Thanks!
Situation the phone was in
--TWRP could not be used because the touchscreen wasn’t working.
--The dm-verity was messed up (i.e. “not started in enforcing mode").
Before you look at the solutions, make sure that your phone shows up in the windows device manager as an ADB device/ASUS ADB device/ADB composite device/etc. no matter which step you’re in. Google it to figure out how if you don’t already know.
The solution
Part 1 - Create and flash a system image which will restore your dm-verity
step 1. download the latest system “update” from the asus drivers website. I have a WW version of the phone, so I downloaded “WW_V13.20.10.152”. It’s a 1.76GB file, so be patient. I haven’t tested this method with other versions of the phone, but they should work in theory.
step 2. go into the updater script file (META_INF → com → google → android → updater-script). Open it with notepad ++.
step 3. delete from the beginning of the file up until the line “ui_print("Target: asus/WW_Phone/ASUS_Z012D:6.0.1/MMB29P/13.20.10.152-20161222:user/release-keys");”
The code that you are deleting checks to make sure that your phone is the proper model. But there is a good chance that it will mistakenly identify your phone as a phony. So we need to get rid of this code.
step 4. save the updater-script file
step 5. create a copy of the modified system update zip file. You should now have two 1.76GB files (or maybe slightly different if your phone is a CN, JP, or other model. Once again, I have a WW version of the phone). Name one of the files “realupdate.zip” and name the other “dmsaver.zip”. The names aren’t actually important.
step 6. enter dmsaver.zip. delete these four files: file_contexts, system.new.dat, system.patch.dat, and system.transfer.list. Exit out of the file. It should now be about 60MB.
step 7. turn on your ZE552KL and enter fastboot mode
step 8. in a cmd screen from your main folder (i.e. the one with adb, fastboot, and all the other files, including the ones you just created), type in the command “fastboot flash system dmsaver.zip”
step 9. if successful, you have just restored the dm-verity. You should now no longer get that sinister red text which has been ruining all your fun.
Part 2 - Install a proper version of TWRP
(This is only important if your version of TWRP won’t let you do anything because you can’t use your touch screen)
Download the version of TWRP that is included in the how-to-root post I linked to above. Also, you can download the oldest version (NOT the newest) from a sharing website which is linked to in a post on the ASUS website. It’s not in english though. Flash it to your phone in fastboot mode using the “fastboot flash recovery” command. Make sure you turn your phone off before turning it back on, or your recovery might not activate correctly.
Part 3 - Install a new version of your system.
Go into TWRP and install the zip file “realupdate.zip” that you created in Part 1 - step 5.
Part 4 - Root your phone
Follow the instructions in the link I posted earlier. It comes from this website, so you know it’s good. This time, though, you probably don’t need to unlock the bootloader
Part 5 - Breathe a sigh of relief
Parting words
I really hope this guide can be of assistance to you. The full procedure for fixing “my” phone wasn’t really recorded anywhere (although once again, big shout out to Niemer for their post). I went through hundreds of iterations of seemingly random fastboot, recovery, and adb actions before everything worked out. Because of this, I feel quite fortunate to have saved the phone, and I really wanted to give back. This community has been super helpful to me over the last seven years, and this is my chance to reciprocate. I sincerely hope that this post will help you.
I hope I didn’t forget anything. I have a sneaking suspicion that I did. In any event, if you have any questions, please post them, and I’ll try to be of assistance. Happy rooting!
thank you man but i start Part1 step8 "fastboot flash system dmsaver.zip" it's successful then i go into TWRP and install the zip file “realupdate.zip” dm-verity show again.
Thank again.
Raw firmware
I have the same issue. My phone was branded "tim italy". When i bought it, I flashed the WW version via asus flash tool, and I'm currently able to update till the last M version, which is the ......152.
If i try to update to Android N, my phone will not boot, giving me the corruption message and shutting down after 10 seconds. I also tried to perform the dm restore procedure; the dm error disappeared but the system is stuck on the Asus boot screen
I believe that the only solution is to flash a Nougat RAW firmware via asus Flash tool. Does Anyone have a download link for the N version ?
thank you, you helped me, now im on N
I guess the version matters then. So be careful with which firmware you download/install. If anyone has success with other versions, please share how you did it
I am stuck on Step 8. i put the 2 zips in where my adb and fastboot is located, and then proceed to type 'fastboot flash system...' and then it wont let me flash, any help?
Device Locked
When I flash the dmsaver.zip, receive the error "FAILED (remote: not allowed in locked state)". Apparently this with the bootloader locked, but I already unlocked before. Someone can help me unlock the bootloader again?
Further hyperlinks & solution ideas
Check out my solution and Ideas in those in links I posted in this thread at 4th of septembre 2017:
https://forum.xda-developers.com/ze...-zenfone-3-zoom-ze553kl-t3657239#post73661437
The hyperlinks in my post might also be useful, I hope.
Would be glad about your feedback, if it helped! :good:
how do you update the script file ..can u just post the file that u made somehow or email it or attach it to a message?
cant get it to work followed the instructions still getinf error code 7 trying to install lineage os
If you have lineage OS version not is a zip file but all the images (boot.img, system.img, ...) then you could try to flash the images through ADB...
if someone have the no verity issue, can you try a method for me please?
it consists on:
re-flash the rom kernel via fastboot
and run:
Code:
fastboot oem reset-dm-verity
Followed all the steps and twrp still has no touch function.
Tried all different twrp versions.
OS Version is a key
Hi everybody that has the same issue, I hope you read that so you can fix your problem.
So what I did was downloading old version of OS that autor mentioned "WW-13.20.10.152". It is necessary to download this version even if there are more newer versions. Then follow tutorial and you should be fine.
So again, thanks OP for posting this. You helped me a lot!
**CREDIT GOES TO messi2050 FOR THE WORKING RECOVERY AND TO paco_1 FOR HIS GUIDE TOO
ASHYX FOR THE DECRYPTION BREAKER AND Walkerblue2030 (??) FOR AT LEAST HAVING A STABLE ENOUGH ROM TO FLASH THAT'S ACTUALLY WORTH YOUR TIME. AND ALSO CREDIT TO fullofhell (??) FOR WHO EVER HE DESIDES TO ENROL FOR THE BETA FOR THE MOST BATTERY EFFICIENT ROM ON THE DEVICE**
--Make sure y'all slap a thanks to these people because without them, unfortunately, any excitement on the J700T devices wouldn't be possible.--
<<DISCLAIMER>>
I NOR ANY OF THE CREDITED PEOPLE ARE RESPONSIBLE FOR ANY DAMAGE DONE TO YOUR DEVICE AFTER FOLLOWING THIS GUIDE. YOU'RE ON XDA SO YOU SHOULD ALREADY KNOW WE LIKE TO SH*T ON OUR WARRANTIES LIKE THERE'S NO TOMORROW. IF YOUR DEVICE BECOMES A BAKED POTATOE OR BLOWS UP YOUR HOUSE FOLLOWING THIS GUIDE OR FLASHING ANY OF THE CREDITED PEOPLE'S WORK, DO KEEP IN MIND THAT YOU HAVE ACCEPTED THIS WARNING AND EVERYTHING AFTER FOLLOWING THIS GUIDE IS BECAUSE OF YOUR ACTIONS.
-------YOU HAVE BEEN WARNED-----
(as scary as I made it sound, I've done this COUNTLESS times and it has worked for me just fine, so nothing to be scared of here if you do this step by step! If you do mess up, try finding the stock firmware and flash back to stock with Odin! Though do take note that Odin has never worked for me unless it was flashing a recovery. I will be making a post on how to flash back to stock soon, so definitely keep an eye out for that!)
Okay so many people are asking how to root the J7 and I wanted to post this small simple guide on how I did it successfully. Without further delay, let's begin.
1- You get yourself them Samsung drivers
2- Get Odin. Duuh.
3- download TWRP (this is messi2050's TWRP, so go give 'em a thanks won't ya?)
4- have a micro SD ready because once you're in TWRP, internal storage won't be mountable.
Okay, so after you've got those things ready, start by enabling OEM unlock. And then USB debugging.
Then you want to move the SU ZIP to your SD card.
(Link for the one I used down below)
Then, power your phone down. Boot into download mode (volume down+home button+power button)
Have that TWRP on your computer, you'll need it on there
Then you'll want to open Odin, select the TWRP.img
(or .tar, I forgot which it is but if .img doesn't show get the .tar from messi2050's post) THROUGH THE AP SLOT
Open the back cover of your device
Plug in your device. When your Odin displays "Added!' you'll know you're ready.
Then click "start" or whatever the button is to begin the flashing process. It should flash and end with a "PASS!" on the top left box and it should be green.
Now, on your device, when you see the Samsung Galaxy J7 logo, IMMIDIATELY unplug the device and remove the battery. I don't know if there is a setting to disable auto reboot, but this is how I personally got it to work.
Then put the battery back in, hold the volume up, power and home buttons untill you boot into TWRP.
Select "install" and then you'll have to select your external storage. Then find the SU zip you should have and then flash it. If it doesn't work you might need to format your internal memory through the WIPE category, then you'll reboot into TWRP again and try again. But make sure you back up before that. And if you do end up formatting, flash SU and the encryption breaker down below.
You should be done! You should be rooted and ready to go! Ahead lies a huge mass of S8/N7 ROMs you should try (they're kinda the same but one in particular has amazing battery life, you'll need to ask " fullofhell" for it, though .-.) a somewhat S5 ROM you can try, just DONT expect any AOSP ROMS to come because from the looks of it they end up broken. And don't try to flash any of the other J7 ROMS (J7 2015-2016, etc.) Because they don't work. Trust me, I've tried.
LINKS
TWRP.IMG: http://www.mediafire.com/file/ehygrybdq7a2j8e/
TWRP. TAR. MD5 (Odin format. To flash this one, you'll need to select it from your PC in the AP slot on odin)
http://www.mediafire.com/file/4f5sz13cz5gy466/
SU ZIP:
https://www.androidfilehost.com/?fid=24591000424939898
DECRYPTION BREAKER:
https://www.androidfilehost.com/?fid=24591000424951049
Use this after you format your data, flash SU or another ROM. Flash it every time you after you flash a ROM so that you can mount internal storage so that you can flash internal zips and images or so that you can create backups and be able to restore. You know, in case you wanna play dirty and all ?)
A ROM TO BEGIN WITH:
https://forum.xda-developers.com/ga...lkerblue-v1-notexperienceromv3-t3575377/page2
(even though the people of this ROM LOVE to bash opinions, this is definitely the ROM to start with. Most stable of all the N7/S8 clones and is kinda battery efficient though id still ask @fullofhell for a beta tryout. Also keep in mind that VIDEO CALLING and WIFI CALLS along with NFC are only a FEW OF THE THINGS YOU WILL BE SACRIFICING TO FLASH ANY ROM ON THIS DEVICE!!!!! DONT ASK ME WHY, ASK ANY OF THE CREATORS OF THE ROM YOU CHOOSE)
I don't use this phone but I can still help out who ever needs it and who ever isn't willing to bash my balls out for my opinions so if you ever need help with things like this, do PM me as I love talking about Android!
I went through the process shown but when finished my phone said "verification failed. unable to restart device" so I would like to know how to fix this.
I don't have oem unlock in developer option
Is this currently(8/13/2019) still working?? Can you point me in direction to list of Compatible Custom Roms or a Stock Debloated Rom and a zip to most current SU archive file?? Would be great since it was took off store. I use to own SU Pro