Hi folks,
I tried to modify the platform.xml file to enable some write permissions. As far as I can tell, the app I used to modify the file didn't write it back correctly, and now my device is what might be called "semi-bricked."
Almost everything force closes, WiFi and write permissions seem to be broken, and I can't seem to get my Galaxy Nexus to communicate with my PC via USB.
I tried booting into CWM and mounting some /system, but I'm not sure how to access it since fastboot/adb don't seem to recognize the device.
I've also booted into some sort of recovery (fastboot?) that looks like the attached image. But I can't get it to do anything except boot up into the normal OS when I click the power button.
Any suggestions on how I can get access back to my device so I can repair/replace the platform.xml file and restore functionality to my phone?
Thank you very much!
Deozaan said:
Hi folks,
I tried to modify the platform.xml file to enable some write permissions. As far as I can tell, the app I used to modify the file didn't write it back correctly, and now my device is what might be called "semi-bricked."
Almost everything force closes, WiFi and write permissions seem to be broken, and I can't seem to get my Galaxy Nexus to communicate with my PC via USB.
I tried booting into CWM and mounting some /system, but I'm not sure how to access it since fastboot/adb don't seem to recognize the device.
I've also booted into some sort of recovery (fastboot?) that looks like the attached image. But I can't get it to do anything except boot up into the normal OS when I click the power button.
Click to expand...
Click to collapse
No it is not bootloader. to access to the bootloader turn on your device long pressing power, volume up and volume down buttons together (don't use odin).
To access to cwm recovery from bootloader just press volume down button until you see "recovery" option, then press power button and it will boot in recovery.
which rom are you using?
solution: download the zip file of your rom and extract the file you modified, make a zip (if you can't make a flashable zip i'll post an attachment for you) and flash it in recovery
enryea123 said:
No it is not bootloader. to access to the bootloader turn on your device long pressing power, volume up and volume down buttons together (don't use odin).
To access to cwm recovery from bootloader just press volume down button until you see "recovery" option, then press power button and it will boot in recovery.
which rom are you using?
solution: download the zip file of your rom and extract the file you modified, make a zip (if you can't make a flashable zip i'll post an attachment for you) and flash it in recovery
Click to expand...
Click to collapse
Thanks for the reply.
I actually did manage to get my PC to recognize the device via USB/adb and I copied the file back to the way it should have been. But that didn't fix anything, so I ended up doing a wipe/factory reset. Everything works now but things still seem a bit. . . off. For instance, it takes a while after my phone boots up before the WiFi will actually connect. It used to be connected almost immediately. And it takes a while for the alarm icon to load/show up in the notification area at the top. And I can't find the option in the settings anymore to use USB debugging. There are lots of little things like that, where it works, but it just doesn't quite work like it used to. . .
And to answer your question, I'm using the stock ROM that came with the Galaxy Nexus (from Google Play Store).
Deozaan said:
Thanks for the reply.
I actually did manage to get my PC to recognize the device via USB/adb and I copied the file back to the way it should have been. But that didn't fix anything, so I ended up doing a wipe/factory reset. Everything works now but things still seem a bit. . . off. For instance, it takes a while after my phone boots up before the WiFi will actually connect. It used to be connected almost immediately. And it takes a while for the alarm icon to load/show up in the notification area at the top. And I can't find the option in the settings anymore to use USB debugging. There are lots of little things like that, where it works, but it just doesn't quite work like it used to. . .
And to answer your question, I'm using the stock ROM that came with the Galaxy Nexus (from Google Play Store).
Click to expand...
Click to collapse
first: to make the "developer settings" appear go settings/About phone and tap on build number 7 times (google has hidden it in 4.2).
said that, you can:
1) fix permissions in cwm recovery (under advanced menu)
2) download a zip of your rom and flash it in recovery
3) if your bootloader is unlocked (you see a padlock when you boot your phone) you can flash a factory image to return completely stock.
4) if your bootloader is locked you can follow the 3) method but you will lose all your sdcard data.
enryea123 said:
first: to make the "developer settings" appear go settings/About phone and tap on build number 7 times (google has hidden it in 4.2).
said that, you can:
1) fix permissions in cwm recovery (under advanced menu)
2) download a zip of your rom and flash it in recovery
3) if your bootloader is unlocked (you see a padlock when you boot your phone) you can flash a factory image to return completely stock.
4) if your bootloader is locked you can follow the 3) method but you will lose all your sdcard data.
Click to expand...
Click to collapse
Thanks again for the response.
I got developer settings to appear. Hooray! Fix Permissions is one of the first things I did to try to repair the platform.xml file when things were broken. I ran it again (but from ROM Manager rather than from CWM Recovery) and it didn't seem to have any effect on the weird sluggishness when first booting up.
My bootloader is unlocked. Will I have to root again if I flash one of those factory images? I'm currently backing up the contents of my "SD card" in case I have to completely wipe the entire thing.
Deozaan said:
Thanks again for the response.
I got developer settings to appear. Hooray! Fix Permissions is one of the first things I did to try to repair the platform.xml file when things were broken. I ran it again (but from ROM Manager rather than from CWM Recovery) and it didn't seem to have any effect on the weird sluggishness when first booting up.
My bootloader is unlocked. Will I have to root again if I flash one of those factory images? I'm currently backing up the contents of my "SD card" in case I have to completely wipe the entire thing.
Click to expand...
Click to collapse
well, you can firstly try to flash a zip of your rom (search on xda or google), it should fix.
the fastboot flash method is the google method so you won't need root (you just have to go into fastboot and connect your phone to your computer, doesn't matter if you have root, or a different rom/kernel/recovery).
If you don't know you to flash from fastboot try first to flash the rom zip.
having a backup of the sdcard is always a good idea :good:, i have 2 backups of mysdcard on 2 different hard drives of my computer and the pictures i take with the camera are automatically uploaded on my dropbox .
enryea123 said:
well, you can firstly try to flash a zip of your rom (search on xda or google), it should fix.
the fastboot flash method is the google method so you won't need root (you just have to go into fastboot and connect your phone to your computer, doesn't matter if you have root, or a different rom/kernel/recovery).
If you don't know you to flash from fastboot try first to flash the rom zip.
Click to expand...
Click to collapse
Weird things are happening. I was making a backup of the "SD Card" and partway through, things stopped copying over. And pretty much everything got erased from it. No big deal, since I'd already copied the important stuff first.
But CWM Recovery won't flash the zip file. It keeps telling me the update failed. I verified the hash on the zip I downloaded and it is the same as what is listed on Google's site. But it just won't flash in CWM.
Deozaan said:
Weird things are happening. I was making a backup of the "SD Card" and partway through, things stopped copying over. And pretty much everything got erased from it. No big deal, since I'd already copied the important stuff first.
But CWM Recovery won't flash the zip file. It keeps telling me the update failed. I verified the hash on the zip I downloaded and it is the same as what is listed on Google's site. But it just won't flash in CWM.
Click to expand...
Click to collapse
wait, are you in cwm recovery o just in stock recovery (they are different)? have you previously installed a cwm recovery using fastboot? which zip are you trying to flash?
edit: ok you know what is rom manager so i think that you are in cwm.
edit2: try this zip http://goo.im/devs/bigxie/maguro/bigxie_maguro_OTA_JOP40D-signed.zip
enryea123 said:
wait, are you in cwm recovery o just in stock recovery (they are different)? have you previously installed a cwm recovery using fastboot? which zip are you trying to flash?
edit: ok you know what is rom manager so i think that you are in cwm.
edit2: try this zip
Click to expand...
Click to collapse
I was in CWM Recovery. I was using the zip file that I extracted from the link you gave me for Google's stock ROMs (I can't post external links yet):
(Factory Images "takju" for Galaxy Nexus "maguro" (GSM/HSPA+) (with Google Wallet) --> Android 4.2.1 (JOP40D))
Strangely enough, after "failing" to flash the zip, I had to log into my Google account again because I had selected the option to Wipe Data and Cache, and most things seem to be working very well again. One odd thing I'm still noticing, though, is that some things don't seem to be syncing properly. For example, if I archive some of my email in the Gmail app, then log into Gmail on my PC, the mail is still unread in my inbox. My phone downloads the new mail just fine. But the changes I make on my phone (reading, archiving, deleting, etc.) don't seem to be syncing to anywhere else.
I'm downloading the zip you suggested. I'll give that a try. Thanks!
enryea123 said:
edit2: try this zip http://goo.im/devs/bigxie/maguro/bigxie_maguro_OTA_JOP40D-signed.zip
Click to expand...
Click to collapse
Try this one
Deozaan said:
I was in CWM Recovery. I was using the zip file that I extracted from here the link you gave me (I can't post external links yet):
(Factory Images "takju" for Galaxy Nexus "maguro" (GSM/HSPA+) (with Google Wallet) --> Android 4.2.1 (JOP40D))
Strangely enough, after "failing" to flash the zip, I had to log into my Google account again because I had selected the option to Wipe Data and Cache, and most things seem to be working very well again. One odd thing I'm still noticing, though, is that some things don't seem to be syncing properly. For example, if I archive some of my email in the Gmail app, then log into Gmail on my PC, the mail is still unread in my inbox. My phone downloads the new mail just fine. But the changes I make on my phone (reading, archiving, deleting, etc.) don't seem to be syncing to anywhere else.
I'm downloading the zip you suggested. I'll give that a try. Thanks!
Click to expand...
Click to collapse
That is not a flashable zip! It is a factory image, it must be flashed via fastboot using a computer.
enryea123 said:
That is not a flashable zip! It is a factory image, it must be flashed via fastboot using a computer.
Click to expand...
Click to collapse
Just to be sure I explained myself clearly, I downloaded that Google provided factory image (a .tgz file) and inside it I found a zip file named "image-takju-jop40d.zip" which is what I tried to flash.
That said, I've just recently finished downloading the one you just suggested to me and I will give that one a try soon. Thank you again for your help. I really appreciate it.
I got it working again. The ROM you gave me failed signature verification in CWM Recovery, but I told it to install anyway and it worked. Thank you.
The problem I was having with Gmail not syncing was that I used Titanium Backup to restore my data, but because all the data from my "SD card" got erased, Titanium Backup itself lots its settings, so my Device ID was different. I guess Gmail relies on the device ID for syncing.
Thank you so much for your help! I learned a lot from the experience.
Glad i helped you. well this is one of the reasons why i don't restore data with titanium (especially system data).
and by the way:
Deozaan said:
Just to be sure I explained myself clearly, I downloaded that Google provided factory image (a .tgz file) and inside it I found a zip file named "image-takju-jop40d.zip" which is what I tried to flash.
That said, I've just recently finished downloading the one you just suggested to me and I will give that one a try soon. Thank you again for your help. I really appreciate it.
Click to expand...
Click to collapse
To fully reset and install a clean rom using fastboot you have to extract the bootloader-blabla.img and radio-blabla.img files from the tar.gz archive and then extract the 4 .img files inside the zip (that is inside the tar.gz) and flash this 6 .img files connetting your phone in bootloader mode to your computer and using fastboot in terminal (in fact this procedure reinstall the recovery too).
Related
Hey everyone. I know there are already a few threads with boot loop animations, and am having difficulties finding the same situation as what I'm going through. Here is what the phone used to have before it randomly started looping:
Rooted - with Stock rom, using ClockwordMod Recovery 5.5.0.2
Used Go Launcher Theme ( if that even matters )
No additional roms installed or anything, the phone is 3 months old.
Ok here is where I'm stuck. I understand I should reflash somethings like recovery image or something, but I'm stuck with one big problem. My computer and phone don't recognize using the USB mount.
The message I get is called "Unable to open lunfile ( no such file or directory)
Here's what screens I can get to:
1. Hold vol up/down while holding power ( the little android with its belly open, and the options Start - Restart Bootloader - Recovery mode - Power Off )
2. Hold vol down - ODIN mode, with the START option only
I can access WMD recovery and factory reset, Try to install my old backup, nothing works at all in that area, no matter what I do.
Can someone advise me a step by step way of getting my computer to recognize my phone, so that I am able to do fastboot, or reflash, or anything to get my phone working again. I can't access my internal memory at all.
It's even possible that I've read too much, and my frustration is getting in the way, if so I apologize! Some guidance would be greatly appreciated!
Thanks in advance of course! I need my phone for business!
Cheers,
Install the drivers on a computer then use fastboot oem unlock. Or just factory reset it from within recovery.
Sent from my Galaxy Nexus using Tapatalk 2 Beta-4
Try my siggy.
I'm not sure about the exact error:
But the link there will get you the correct drivers.
Also, as stated...try to factory reset.
You'll lose your apps/data that way though =/
Hopefully you can get the driver installed and get your computer to recognize.
If so, follow this to back up your apps:
http://forum.xda-developers.com/showthread.php?t=1420351
Have exactly the same setup as you (rooted/stock/CWM) and had the animation bootloop - animation would just loop until a battery pull.
Only thing that solved it was a factory reset from recovery. Been working fine for the 4 weeks since. No need for any reflashing etc. Titanium recoveries have all worked fine as well. Didn't try my Nandroid backup as I thought that may still have the 'fault' built in.
I had a boot loop for every from I tried to flash...wat fixed it was before flashing u need to wipe system data and wipe the cache in the recovery...ie a clean install...then every rom I tried worked...so I think ur missing that crucial step coz it worked for me
Sent from my Galaxy Nexus using Tapatalk
Hey guys, as stated above I've done numerous factory resets, it still seems to boot. I will for sure try to get the drivers installed so my phone is recongised by the computer, but would need step-by-step assistance when doing fastboot, or whatever the next step is.
Looking for more help though! Keep em coming!
?
Any other ideas?
Thanks!
Ok guys, so here's where I'm at now. I've used Jubakuba's sticky link, located here:
http://forum.xda-developers.com/showthread.php?t=1529058
Everything is able to be recognized up to the point where it says "Put the su.zip on your phone."
Since I cannot access my phone contents, since I keep getting this "Unable to open lunfile ( no such file or directory), it does not allow me to add anything to my phone.
I re-installed CWD as stated in the list of things to do, and all that went well. But I have the same issue, I tried factory resetting all that. erase cache, and still stuck with the same issue.
What's my next step now peeps? Looking for a quick answer as I have time to do it tonight!
Edit***
Just tried this trick: but it says it does not recognize the device?? what is going on! Please help someone! Thanks!
Panic Section! (Something is Wrong)
Q: My phone won't boot!
A: The easiest option is to get into recovery and restore a nandroid using the above guide (pull battery to put phone in an off-state if needed).
However, more advanced options are available if you don't have a nandroid available (You're naughty).
Do you have another rom .zip available on your SD card? If so, simply use the above guide for installing a rom to get you booting again.
If not, you can download one on your PC. Boot into fastboot (the green Android with open chest menu).
Move the .zip to the C:\android-sdk-windows\platform-tools folder.
Open ADB.
Change the NAMEOFZIP.zip below to the correct file name...and perform the action.
Surely your computer recognizes your phone. Otherwise how were you able to unlock the bootloader and flash the recovery?
And I've never seen that error message before. It doesn't even make any sense to me. Where are you seeing it? On your phone or on your computer? And in what context? What are you trying to do when it shows up?
If your phone isn't booting I'm not sure that you can copy any files to it yet. (Maybe you can use adb in clockworkmod? I'm not sure) What I do know you can do is flash the stock ROM and start over.
Download the image from Google here:
http://code.google.com/android/nexus/images.html
Here's a instructions for the GSM version:
http://forum.xda-developers.com/showthread.php?t=1366806
For the Verizon version, I can't find the thread at the moment but you just replace the filenames and also there's 2 radios to flash so:
fastboot flash radio *filename*
fastboot reboot-bootloader
fastboot flash radio-cmda *filename*
"Unable to open lunfile ( no such file or directory) appears on the phone, in CWD mode, when trying to attempt "mount Usb" to be able to access my internal storage .
I am attempting your thoughts right now.
I will post with results
Ok I tried to do this step. This is the outcome I received on the computer after even typing the first step:
'fastboot-windows' is not recognized as aninternal or external command, operable program or batch file.
A thing to stress, I'm not sure how to do step 1: 1) Take a Nandroid Backup if you have CWM installed.
EDIT***
GREAT NEWS!
used this setup!
http://android.modaco.com/topic/348161-01-feb-r4-superboot-rooting-the-gsm-lte-galaxy-nexus/
and it worked!
Thank you everyone! Going to play with my phone and make sure it all works!
Macinshak said:
Ok here is where I'm stuck. I understand I should reflash somethings like recovery image or something, but I'm stuck with one big problem. My computer and phone don't recognize using the USB mount.
The message I get is called "Unable to open lunfile ( no such file or directory)
Click to expand...
Click to collapse
the problem is when that happen?? when ur phone is booted and u plug the usb cable to ur pc? or when u are under recovery and want mount the usb mass storage? the second one doesn't work
Post 1: How to unlock your bootloader, flash a recovery and root
Post 2: How to flash a custom ROM and kernel (boot.img)
Post 3: How to reverse everything and go back to stock
Post 4: How to ADB Sideload a ROM
Alright. This is for everyone who wants to root their phone. I've seen MULTIPLE threads of the same question "Can I root my phone and How do I do it". So I hope I never have to see it again! In this tutorial, I use use my toolkit as the way to root. Doing it manually takes forever and that is why I made my toolkit.
Requirements:
HTC One X (charged to at least 70%)
Windows XP,Vista,7 (8 is not officially supported since I don't have the drivers)
USB cable
Ability to read and follow step-by-step
Understanding that I am no way guaranteeing anything. If you screw up your phone, you probably didn't follow my steps and made a foolish mistake.
Let's begin.
Download my toolkit from here.
Link 1 and Link 2
Extract the FOLDER to your C: drive or to your desktop.
MAKE SURE YOUR DIRECTORY DOES NOT HAVE A PERIOD OR SPACE.
Open One X.exe
So now you have my program open. Great.
On your phone, go to Settings -> Developer Options and Enable USB Debugging.
From my toolkit, Click 1. Install HTC Drivers.
After the drivers install, restart your computer.
After your computer loads up, open my toolkit and connect your phone to the computer. Your phone should now be recognized.
Now, click 2. Register at HTCDev. Register with a VALID email address and LEAVE the web browser open.
Now, under the commands section of my toolkit, press Boot into Bootloader.
You should have a nice, white, shiny screen that says FASTBOOT USB.
Click 3. Get Token ID. Look at the pop up and it will tell you how to get the Token ID.
Highlight where it says < < < < Identifier Token Start > > > > all the way to < < < < < Identifier Token End > > > > > and right click and it will automatically copy it.
Now, click Submit Token ID. Your web browser should now open a new tab. Scroll down and in the empty box, paste your Token ID. Press submit. HTCDev now emailed you your unlock token.
Your phone should still be in the bootloader. Now, go to the email address you registered to HTCDev and DOWNLOAD your unlock_code.bin. Press 5. Unlock Bootloader. Locate your unlock_code.bin and it will flash it to your phone.
READ the warning. THIS WILL WIPE ALL YOUR DATA FROM THE PHONE.
When you agree to it, press the volume up button and press the power button to accept it. Your phone will now restart.
When your phone loads up, go through the set up wizard. Then, on your phone, go to Settings -> Developer Options and Enable USB Debugging.
Under the Extras section, press Perm Root. It will push SuperSU.zip to your phone.
Under commands, press Boot into Bootloader once again.
Now, it is time to flash a recovery.
TWRP (Team Win Recovery Project) is a custom recovery that will allow you to flash custom ROMs, Mods, etc.
CWM (ClockWorkMod) is a custom recovery that will allow you to flash custom ROMs, Mods, etc.
I recommend TWRP and we will use it for this tutorial,
Select TWRP and press Flash Recovery.
After it flashes, remove the USB cable and have HBOOT selected in bootloader. Press the power button and it will reload to another screen. Press the Volume Down button until you get to Recovery. Press the power button to select it.
Go to Backup and back up your boot and system partition. Always have a back up before you flash or do anything.
After that, go to Install and locate SuperSU.zip. Click it and slide the screen on the bottom to flash it. After it flashes, reboot the phone.
In your app drawer (your menu with all the apps), open SuperSU. If it says the binary needs to be updated, then update it. If it doesn't, then you are fully rooted!
Post 2: How to flash a custom ROM and kernel (boot.img)
The fun part! Now, I will teach you how to flash a ROM and boot.img
Find a ROM you like, the first thing you should do is make sure it is COMPATIBLE with your phone. If you find a ROM that is for AT&T (Evita) and you have the International model (Tegra3), don't be an idiot and flash it. I will not help you with that since you already agreed to my warning from the first post.
International models won't work on an AT&T HOX and Vice Versa.
Also, DO NOT ASK IF YOU CAN FLASH A ROM FROM ANOTHER DEVICE!
Will it work? NO! Will it ever work? NO! Can I flash it anyways? Brick your device, I don't care. I warned you.
Let's get back on task. So you found the ROM you want to try, so go ahead and download it. KEEP THE THREAD OPEN! MAKE SURE YOU READ EVERYTHING AND REREAD IT AGAIN! READ WHAT USERS SAID ABOUT IT AND ABOUT BUGS! GO AHEAD AND READ THE WHOLE ENTIRE THREAD! GAIN KNOWLEDGE!!
Connect your USB cable to your phone. View the folders on your phone. I like to make a folder called ROMs on my phone and transfer it in there.
After you transfer it, open my toolkit and press Boot into Recovery. When you are in TWRP, MAKE A BACKUP!!!
After you make a backup AKA a Nandroid, click Wipe. Wipe Cache, Dalvik, Factory Reset and System. NOTHING ELSE! If you click anything else, IT WILL WIPE YOUR SD CARD AND YOU WILL HAVE MORE ISSUES ON YOUR HEAD!
So you wiped everything. Great. Your phone is ROMless, Yay!
Now go back and press install. Go to the folder where the ROM you downloaded, is located in. Select the ROM and slide the screen to flash it. After it flashes, press the back button. Press Reboot and Reboot into bootloader. Open the ROM you downloaded from your computer. You should see boot.img. Extract it to your computer. Open my toolkit and press Flash a Kernel. Locate the boot.img and it will flash it.
After it flashes, press reboot from the phone.
Congrats! Enjoy your fully working or borked ROM! Remember, DO NOT ASK FOR ETAs, DO NOT BUG/PM A DEV ABOUT UPDATES, and BE RESPECTFUL TO THE DEVELOPERS!
Post 3: How to reverse everything and go back to stock
Now, let's talk about getting back to stock. There are 2 ways to do this.
1. Flash the stock RUU (If available) (Recommended)
2. Restore your Nandroid (backup that I told you to make earlier)
1. I'll talk about flashing the stock RUU first.
Go here and download the RUU.
http://forum.xda-developers.com/showthread.php?t=1543604
Download the correct RUU for your phone.
Now, back up all your data (pictures, contacts, etc) since this will put your phone back to complete stock.
Connect the USB cable to your phone. Press Boot into Bootloader.
It should now say FASTBOOT USB on your screen.
Press Relock bootloader. It may give you a security warning error or it may say failed. Who cares, ignore it. It's normal.
Your phone will boot up normally.
When the phone is fully loaded. Unplug and replug the USB cable back in the phone. Now,run the RUU you downloaded and follow the instructions.
Your phone will be back to stock.
2. Now, we will talk about restoring your nandroid backup.
Connect your phone to the computer. Open up the folder to view the files on your phone.
From your computer, Go to TWRP -> BACKUPS -> (Your hardware Serial Number) -> (Folder you wish to restore to) -> and copy boot.emmc.win to your computer. Rename boot..emmc.win to boot.img
Open my toolkit and press boot into recovery.
Click Wipe. Wipe Cache, Dalvik, Factory Reset and System. NOTHING ELSE! If you click anything else, IT WILL WIPE YOUR SD CARD AND YOU WILL HAVE MORE ISSUES ON YOUR HEAD!
Press back and press Restore. Choose the backup to restore to.
After it finishes, press the back button. Press Reboot and select bootloader.
Open my toolkit and press Flash a Kernel. Locate the boot.img and it will flash it.
You are now back to your stock Nandroid.
4. How to use ADB Sideload
You may have seen what ADB Sideload around the forums but have no idea what it is. Since the HOX does not have an SD card, it makes things harder when you have to flash a ROM.
Here's a scenario when we need to use ADB Sideload.
1. You accidentally wiped your internal SD and have no ROM on your phone
2. You wiped your ROM and forgot to transfer a custom ROM/have no backups(Nandroid) available.
3, You have none of the above and there is no available RUU for your phone. <----- This is a real bummer.
Here are the steps to load on a ROM
I placed TWRP in my toolkit for a reason. CWM does not support ADB Sideload (as far as I know) and TWRP does.
Boot into recovery manually. Turn your device off and hold the VOLUME DOWN + POWER button together until the BOOTLOADER pops up. Press the VOLUME DOWN button until you have selected RECOVERY. Press the POWER button to get into RECOVERY.
Connect the USB Cable to your phone and computer.
In TWRP, click "Advanced" and select ADB Sideload.
Download a ROM to your computer (if you haven't already done so). Rename it as one word. For example CM10.zip, QX.zip, ARHD.zip, etc.
In my toolkit, under the extras section, press ADB Sideload a ROM. Press "Yes" when it asks you if you are in recovery. Then select the ROM you want to install. It will then sideload it to your phone and flash it.
After it finishes, press the back button. Press Reboot and select bootloader.
Pull the boot.img from the zip file and extract it.
Open my toolkit and press Flash a Kernel. Locate the boot.img and it will flash it.
You now have a ROM on your phone!
1 more, just in case.
and yes, i know. Wrong section. posted here by accident.
thanksss
Thanks for the info you provided.
Hasoon, quick suggestion.
As much as I think your info is quality, I think you should add some screenshots.
If anyone's like me I hate reading massive paragraphs of instructions.
Remember - A picture can speak 1000 words
Thanks though.
Dear hasoon2000
Nice tutorial.. help me alot thx..
worked very fine for me, thanks a lot !! :good:
Is it working with Jelly Beam? And will i be able to get OTA updates after?
Thanx
Sent from my HTC One X using xda app-developers app
OTA
uguaanga said:
Is it working with Jelly Beam? And will i be able to get OTA updates after?
Thanx
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
You won't be able to get official OTA updates after you have flashed a custom rom.
My experience is that even rooting is tricky for official Firmware upgrades.
Even tough there are some ROM's on XDA that have OTA support!
Thanks! Works fine for me!
When you say THIS WILL WIPE ALL YOUR DATA FROM THE PHONE in post 1, does that include sdcard data, photos, music etc?
Since USB mass storage is not available, I've tried using android file transfer to backup my files before unlocking boot loader. Its not working though. Any way to do this?
Sent from my HTC One X using xda premium
nevermind
When acquainted with my HTC this thread helped me. thanks
Htc one x stuck on htc one logo
please help meee
i have an htc one x running jelly bean 4.1.1 and i rooted it ...everything worked finee ... until i installed an app from the play store called font installer after i installed it i changed the font and installed the font ... the notification bar was gone ... i was able to use the device but without the notification bar so i turned it off and on again ... and i get stuck on the htc one logo ... PLEASE ANYONEEE PLEASE HELP MEE ... did i brick the device or what?? pleasee again hellpp and thank you
Nice guide. Thanks.:victory:
After a update for better compatibility for 3rd party app, my Zenfone wont get past the ASUS screen at all.
Im also stuck at the asus load screen. I played around with the permissions of the sd card, after rebooting its stuck. Guys how to unbrick?
bratski said:
Im also stuck at the asus load screen. I played around with the permissions of the sd card, after rebooting its stuck. Guys how to unbrick?
Click to expand...
Click to collapse
you may want to flash your phone back. so this consist of
1) read up how to access to Temp CWM
2) download and transfer the full rom to your SD card
3) do a wipe all partition and go to advanced setting, wipe cache
4) install zip and choose from external SD, point to that .zip file for the full rom and apply.
5) installation may take 10min or so do not switch it off. after installation you are good as new.
I believe this should solve your problem, normal if things get bricked is due to config file error could be [syntax, corrupted, missing, setting].
Flashing should solve mostly of it unless the file that you previously accessed require root and cwm does not give permission to the file. that is a permanent bricking.
As always, newbie should not try tweaking permission required files, you end up having bricking the device as there might be no solution to recover it due to access rights. ALWAYS have a back up file so you can at least copy the file back and chmod it.
jerk48 said:
After a update for better compatibility for 3rd party app, my Zenfone wont get past the ASUS screen at all.
Click to expand...
Click to collapse
by asus screen, did you mean the ASUS Setup Wizard?
sooty84 said:
you may want to flash your phone back. so this consist of
1) read up how to access to Temp CWM
2) download and transfer the full rom to your SD card
3) do a wipe all partition and go to advanced setting, wipe cache
4) install zip and choose from external SD, point to that .zip file for the full rom and apply.
5) installation may take 10min or so do not switch it off. after installation you are good as new.
I believe this should solve your problem, normal if things get bricked is due to config file error could be [syntax, corrupted, missing, setting].
Flashing should solve mostly of it unless the file that you previously accessed require root and cwm does not give permission to the file. that is a permanent bricking.
As always, newbie should not try tweaking permission required files, you end up having bricking the device as there might be no solution to recover it due to access rights. ALWAYS have a back up file so you can at least copy the file back and chmod it.
Click to expand...
Click to collapse
my problem right now is my pc wont detect my phone. Ive already installed the drivers.
Same thing happened to me when I tried flashing the OTA update with my phone being rooted. You have get into recovery mode on the phone and then use ADB to put the original image back to the device to get it back to stock so it will reboot. It worked for me
sooty84 said:
you may want to flash your phone back. so this consist of
1) read up how to access to Temp CWM
2) download and transfer the full rom to your SD card
3) do a wipe all partition and go to advanced setting, wipe cache
4) install zip and choose from external SD, point to that .zip file for the full rom and apply.
5) installation may take 10min or so do not switch it off. after installation you are good as new.
I believe this should solve your problem, normal if things get bricked is due to config file error could be [syntax, corrupted, missing, setting].
Flashing should solve mostly of it unless the file that you previously accessed require root and cwm does not give permission to the file. that is a permanent bricking.
As always, newbie should not try tweaking permission required files, you end up having bricking the device as there might be no solution to recover it due to access rights. ALWAYS have a back up file so you can at least copy the file back and chmod it.
Click to expand...
Click to collapse
downshift00 said:
Same thing happened to me when I tried flashing the OTA update with my phone being rooted. You have get into recovery mode on the phone and then use ADB to put the original image back to the device to get it back to stock so it will reboot. It worked for me
Click to expand...
Click to collapse
where do i get the stock image?
bratski said:
where do i get the stock image?
Click to expand...
Click to collapse
here is the stock firmware.
https://www.asus.com/Phones/ZenFone_2_ZE551ML/HelpDesk_Download/
its fine if your phone does not talk to your PC now. copy the firmware to your SD card via other means. [card reader etc]
then try my method of flashing it back to original state, you stated that adb dont work, have you tried the temp CWM method yet?
the main goal is to wipe dalvik cache under advanced menu in CWM, and cache partition and all hard reset.
then you flash back your original file.
hope it works for you.
sooty84 said:
here is the stock firmware.
https://www.asus.com/Phones/ZenFone_2_ZE551ML/HelpDesk_Download/
its fine if your phone does not talk to your PC now. copy the firmware to your SD card via other means. [card reader etc]
then try my method of flashing it back to original state, you stated that adb dont work, have you tried the temp CWM method yet?
the main goal is to wipe dalvik cache under advanced menu in CWM, and cache partition and all hard reset.
then you flash back your original file.
hope it works for you.
Click to expand...
Click to collapse
ive read about the temp cmw method and i cant figure out how to go about it. it says on the instruction that you need to turn on phone before running the cai_dat_CWM. how am i going to do this as my phone will only boot to the asus logo? thanks
just figured it out. I need to boot in fastboot so the phone will get recognized. However, the latest build available on the asus website is still 2.17.40.12. I already have the 2.18.40.12 version. The 2.17 firmware can't overwrite the newer build in temp CWM recovery. Anybody knows where i can download the full rom? Z00A-WW-2.18.40.12?
bratski said:
just figured it out. I need to boot in fastboot so the phone will get recognized. However, the latest build available on the asus website is still 2.17.40.12. I already have the 2.18.40.12 version. The 2.17 firmware can't overwrite the newer build in temp CWM recovery. Anybody knows where i can download the full rom? Z00A-WW-2.18.40.12?
Click to expand...
Click to collapse
I GOT THE SAME PROBLEM.
dunno what to do anymore.
sigh...
help me please
Ninjakura said:
I GOT THE SAME PROBLEM.
dunno what to do anymore.
sigh...
help me please
Click to expand...
Click to collapse
here is the link for stock but pre-rooted img for latest 2.18.40.12 firmware,,make sure to download Z00A firmware if you have ZE551ML device.. and if I was not mistaken, you may choose to FULL UNROOT in SuperSU apps to go back to stock rom..
cangcan said:
here is the link for stock but pre-rooted img for latest 2.18.40.12 firmware,,make sure to download Z00A firmware if you have ZE551ML device.. and if I was not mistaken, you may choose to FULL UNROOT in SuperSU apps to go back to stock rom..
Click to expand...
Click to collapse
thanks. problem solved after i followed instructions from this thread, http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
bratski said:
my problem right now is my pc wont detect my phone. Ive already installed the drivers.
Click to expand...
Click to collapse
me too, any idea on how to fix it?
sooty84 said:
you may want to flash your phone back. so this consist of
1) read up how to access to Temp CWM
2) download and transfer the full rom to your SD card
3) do a wipe all partition and go to advanced setting, wipe cache
4) install zip and choose from external SD, point to that .zip file for the full rom and apply.
5) installation may take 10min or so do not switch it off. after installation you are good as new.
I believe this should solve your problem, normal if things get bricked is due to config file error could be [syntax, corrupted, missing, setting].
Flashing should solve mostly of it unless the file that you previously accessed require root and cwm does not give permission to the file. that is a permanent bricking.
As always, newbie should not try tweaking permission required files, you end up having bricking the device as there might be no solution to recover it due to access rights. ALWAYS have a back up file so you can at least copy the file back and chmod it.
Click to expand...
Click to collapse
I have same prolem as OP's got.
I've got stuck on Asus Loading screen after install OTA update on rooted device.
I'm gonna try your method.
Thanks
downshift00 said:
Same thing happened to me when I tried flashing the OTA update with my phone being rooted. You have get into recovery mode on the phone and then use ADB to put the original image back to the device to get it back to stock so it will reboot. It worked for me
Click to expand...
Click to collapse
how did u do that? can u give me step by step instruction please?
ty
Did anyone able to fix this problem (stuck at Asus logo and not able to get to recovery mode or connect to the computer)? Thanks!
SAN_MARINO said:
Did anyone able to fix this problem (stuck at Asus logo and not able to get to recovery mode or connect to the computer)? Thanks!
Click to expand...
Click to collapse
Press Power+Volume Up key, After vibration leave Power Button then choose Recovery Mode using Volume keys, if sleeping Android screen appear at Recovery with Error message, Press Volume Up and Power and leave immediately Power Key, it will show you the Recovery Menu, then Reset your device, it will solve your problem.
If I am helped you, Press Thanks button.
k576 said:
Press Power+Volume Up key, After vibration leave Power Button then choose Recovery Mode using Volume keys, if sleeping Android screen appear at Recovery with Error message, Press Volume Up and Power and leave immediately Power Key, it will show you the Recovery Menu, then Reset your device, it will solve your problem.
If I am helped you, Press Thanks button.
Click to expand...
Click to collapse
Thanks!
I already tried it like 20 or more times. The ASUS logo still shown for like 10 seconds and died and came back again (ASUS logo). When I tried to connect it with my laptop, the computer won't recognize the device.
SAN_MARINO said:
Thanks!
I already tried it like 20 or more times. The ASUS logo still shown for like 10 seconds and died and came back again (ASUS logo). When I tried to connect it with my laptop, the computer won't recognize the device.
Click to expand...
Click to collapse
I will try to tell you step by step:
1. Press Power Button + Volume Button
You enter into Recovery Fastboot Option, then Choose Recovery menu using Volume Key (3 Option mostly shown)
then press Power Button (From Recovery Mode), it restart.
2. Then after Restart it shows you (Mostly) Sleeping Android Screen with Error text, then Press First Volume Up Button, and Press Power Button (Power button for a second or two then leave it, IF YOU PRESS MORE TIME, IT WILL RESTART THE PHONE).
3. You can now see the Recovery Menu with Normally appear in other phones also - Reset, Restart, Etc Option.
Hope you will now able to reset your phone...
----------------------------------------------------------
PRESS THANKS BUTTON IF I AM HELPED YOU
----------------------------------------------------------
I wanted to update my phone from Software version/Baseband version PF4 to the latest Software and Baseband version PG1, but I wanted to KEEP EVERYTHING ELSE. All my apps, my ROM and my Kernel. I was able to do this in less than one hour by following these steps.
Necessary files first:
1) ODIN file. You want to have a folder with the Odin .exe and other files somewhere convenient, your desktop is fine.
2) Latest TAR file available. Currently, that is PF4. The file should end in .md5.
3) Latest CF-Auto-Root. The file should end in .md5.
4) Latest Recovery (TWRP) TAR file. The file should end in .tar.
All of these are available from thread here: http://forum.xda-developers.com/spr...uide-links-files-update-root-restore-t3366862
All Put the PF4, the CF-Auto-Root and the TWRP file in the folder where Odin is.
For convenience, I also recommend installing Minimal ADB. Grab that here: http://forum.xda-developers.com/showthread.php?t=2317790
Install the Minimal ADB. Run that and make sure that it sees your phone. Plug your phone in and type "ADB devices." Look at your phone and accept the security prompt if that comes up.
Once you have Minimal ADB installed the commands that you will use are "ADB Reboot Download" and "ADB Reboot Recovery." These just simplify things.
Is your phone Rooted with TWRP Recovery? Great, we can get started! If not, open ODIN. Flash CF-Auto-Root to get your phone rooted. Then flash the TWRP TAR file. And then you are ready to begin.
Make sure that you have Developer options selected and OEM unlock selected. Really. Make sure. Otherwise you will get the FRP lock.
1) From ADB, type "ADB Reboot Recovery." This should take you to TWRP. If it doesn't read up ^^^^ because you missed a step.
2) In TWRP, go to Backup. This should be the default but if not select Boot, System and Data. Make that backup, which will get stored in TWRP/Backups on your phone. Within that folder, you will see a folder with a long name with lots of numbers and letters that identifies that this backup is for your phone. I generally copy the whole Backup folder to my PC, just in case my phone gets totally wiped I can still restore it. It takes a few minutes and better safe than sorry. Backup done, you can go to the next step.
3) In ADB, type the command to put your file into Download mode. ("ADB reboot download.") Start ODIN. Click on the AP button and select the PF4 file. Let it load, it takes a while. Then click start. This will take few minutes, maybe 10, then your phone will restart back to stock. Again you are going to have to wait for a bit.
4) Let your phone finish rebooting. Once done, you can go to Settings -> System Update -> Download updates manually. You should have an update to PG1 available. Install that and again, your phone will reboot. Once that is done, check your Software version/Baseband version and they should both say PG1.
5) Again, use ADB to send your phone back to download mode and back to Odin. Select the CF-Auto-Root and Start. This should go much faster.
6) Back to Download mode and Odin one last time. Select the TWRP file and start.
7) In ADB, type "ADB reboot recovery".If you have done everything right, you should now be in TWRP.
8) I like to get rid of any bloat that may have been installed with the Stock. I go into Wipe and do both a Factory reset and then in Advanced wipe Caches, System and Data. Then go back to the TWRP main screen WITHOUT REBOOTING.
9) Click Restore and restore the backup that you did at the beginning.
Your phone is now updated to the latest Software and Baseband versions but with all your apps and data as it was before you started.
This literally took me 45 minutes today and that only because of the long rebooting times.
Have fun!
So I always have a space issue with this. I don't have enough free space on my device to hold a backup.
Do you know if there's any way to backup to an external/usb device. I have one of the micro USB to female USB adapters...and I can see the USB drive connected while in the phone, but I don't see an option to use that as a backup destination from TWRP.
Is there a way to backup off the device?
Sent from my SM-G920P using XDA-Developers mobile app
Saafir said:
Mount the USB OTG then you should be able to backup too it
Click to expand...
Click to collapse
I thought I tried that. Ill try again.
Going off the top of my head, if I remember right, it said that the external drive was non-writable.
Is there a specific partition type the USB drive had to be (fat32, ext4, etc) or is there a specific process that I need to follow to mount the drive in TWRP?
Sent from my SM-G920P using XDA-Developers mobile app
Alright. I tried again this morning. The problem is, when I go into mount the USB in TWRP, it does nothing. I can't check it off. I've tried with 2 different USB sticks and I cant get it to work. When the phone is booted to system, I can see the USB, read/write without any problems.
hotwired34 said:
Alright. I tried again this morning. The problem is, when I go into mount the USB in TWRP, it does nothing. I can't check it off. I've tried with 2 different USB sticks and I cant get it to work. When the phone is booted to system, I can see the USB, read/write without any problems.
Click to expand...
Click to collapse
I just tested and OTG seems to be working fine for me.
I went into TWRP, selected Mount, selected USB Storage. Tapped on Select Storage (same screen) and selected USB Storage. (Did you miss this last step?)
I don't know what to tell you beyond the old "It works on my computer/phone."
Are you sure that you are using the right version of TWRP? From here: https://dl.twrp.me/zerofltespr/
koop1955 said:
I just tested and OTG seems to be working fine for me.
I went into TWRP, selected Mount, selected USB Storage. Tapped on Select Storage (same screen) and selected USB Storage. (Did you miss this last step?)
I don't know what to tell you beyond the old "It works on my computer/phone."
Are you sure that you are using the right version of TWRP? From here: https://dl.twrp.me/zerofltespr/
Click to expand...
Click to collapse
I have the right version of TWRP. It might be my otg cable. It's one of the cheap ones. I think I got a 3 pack for something like $0.99.
I was able to use the cable from within the phone and do a full Titanium backup. It's not going to be 100% like your method, but at least my apps and data will be preserved (for the most part). I probably have enough space to do the backup of system and boot, then just restore the apps with data.
Thanks for your help!
Need some help on how to get the download mode back.
so i have HTC 10, Nougat. S-off and unlocked bootloader,
had some issues with my phone so i formatted the user data from TWRP, the went to flash the original stock ROM, something went wrong obviousely so now i lost the ability to get into download mode.
if i press the power and volume down the phone just gets stuck in boot screen, i can get into the bootloader and recovery (not the TWRP) by pressing power and both volume buttons, bot from recovery I seem to fail flashing the ROM again, it fails on the signature check and even via ADB i cannot boot to download mode.
Any advice on how to get this issue sorted. i want to get the twrp or reinstall the rom again.
PS placing the rom.zip on the SD card is not doing anything as the phone bypasses that step automatically
thanks in advance
Avo_GH said:
Need some help on how to get the download mode back.
so i have HTC 10, Nougat. S-off and unlocked bootloader,
had some issues with my phone so i formatted the user data from TWRP, the went to flash the original stock ROM, something went wrong obviousely so now i lost the ability to get into download mode.
if i press the power and volume down the phone just gets stuck in boot screen, i can get into the bootloader and recovery (not the TWRP) by pressing power and both volume buttons, bot from recovery I seem to fail flashing the ROM again, it fails on the signature check and even via ADB i cannot boot to download mode.
Any advice on how to get this issue sorted. i want to get the twrp or reinstall the rom again.
PS placing the rom.zip on the SD card is not doing anything as the phone bypasses that step automatically
thanks in advance
Click to expand...
Click to collapse
Go into download mode from bootloader.
yldlj said:
Go into download mode from bootloader.
Click to expand...
Click to collapse
I cannot, when i pick download mode it goes straight into a boot loop and gets stuck on the HTC logo screen nothing else happens
push vol down vol up and power
Since the computer can talk to the phone, I would try the RUU executable.
(hard to help troubleshoot not knowing what you did but flashing "original stock ROM" via TWRP is a problem)
If you're getting a signature check fail, investigate that. What file are you flashing? How are you trying to flash it? Does downloading it again and comparing the two show any differences (if there isn't a hash to verify it)?
Rolo42 said:
Since the computer can talk to the phone, I would try the RUU executable.
(hard to help troubleshoot not knowing what you did but flashing "original stock ROM" via TWRP is a problem)
If you're getting a signature check fail, investigate that. What file are you flashing? How are you trying to flash it? Does downloading it again and comparing the two show any differences (if there isn't a hash to verify it)?
Click to expand...
Click to collapse
thanks for your comment,
I will try the RUU method tonight and see if that makes any difference.
I was flashing the Original Stock ROM, but i did that from SD card not TWRP, but during the flashing the phone rebooted multiple times and then i ended up with this issue. i am pretty sure I am trying to flash the same file, but will check the Hash just to be sure.
the issue the annoys me is that i cannot access the download mode, if i could then i will flash TWRP again and restore from backup images i have.
I want to say there's a condition where you have to flash twice but I'm not certain on that but it wouldn't hurt.
The signature fail is a concern; hence getting a new file. Are you exctracting 2PS6IMG.zip from the RUU via the decrypt tool? That's what I've always done to ensure I have the correct file and intact.
Rolo42 said:
I want to say there's a condition where you have to flash twice but I'm not certain on that but it wouldn't hurt.
The signature fail is a concern; hence getting a new file. Are you exctracting 2PS6IMG.zip from the RUU via the decrypt tool? That's what I've always done to ensure I have the correct file and intact.
Click to expand...
Click to collapse
oh thanks for that tip, I used a zip file downloaded from easy-firmware.com
but tonight will try to extract from the RUU. will see how that goes.
really appreciate you taking time to respond
Avo_GH said:
oh thanks for that tip, I used a zip file downloaded from easy-firmware.com
but tonight will try to extract from the RUU. will see how that goes.
really appreciate you taking time to respond
Click to expand...
Click to collapse
Yeah, there's a lot that can go wrong there, like downloading the wrong one, the poster making a mistake, not to mention its an unknown source--especially since you're S-OFF.
Ensure you get the correct version from htc.
Rolo42 said:
Yeah, there's a lot that can go wrong there, like downloading the wrong one, the poster making a mistake, not to mention its an unknown source--especially since you're S-OFF.
Ensure you get the correct version from htc.
Click to expand...
Click to collapse
ok here is the latest development, wondering if anyone has any advise,
firstly extracting the file from the RUU and flashing it did not work. however i managed to find a little app called Windroid that allowed me to flash TWRP from the bootloader (without the need to go to download mode)
but I soon found out that the phone lost all its partitions. so i cannot wipe, format, install anything, but i can see a bunch of folders and filed via the TWRP file manager.
used ADB fdisk -lu I only see one single partition end was only able to remount /dev/block/mmcblk0p1.
any advice will be highly appreciated I am not sure how to proceed here
thanks in advance
Avo_GH said:
ok here is the latest development, wondering if anyone has any advise,
firstly extracting the file from the RUU and flashing it did not work. however i managed to find a little app called Windroid that allowed me to flash TWRP from the bootloader (without the need to go to download mode)
but I soon found out that the phone lost all its partitions. so i cannot wipe, format, install anything, but i can see a bunch of folders and filed via the TWRP file manager.
used ADB fdisk -lu I only see one single partition end was only able to remount /dev/block/mmcblk0p1.
any advice will be highly appreciated I am not sure how to proceed here
thanks in advance
Click to expand...
Click to collapse
If you're still in this trouble: -Search for your actual installed ROM (the firmware zip with a lot of other zips inside), deRUU it (search on google how to decompress a RUU) and flash via BOOTLOADER the hosd_signed.img image (this is "download" and "RUU" modes). You can boot to BOOTLOADER holding both volume buttons and power together (try more times if it wont boot).
vladmitra said:
If you're still in this trouble: -Search for your actual installed ROM (the firmware zip with a lot of other zips inside), deRUU it (search on google how to decompress a RUU) and flash via BOOTLOADER the hosd_signed.img image (this is "download" and "RUU" modes). You can boot to BOOTLOADER holding both volume buttons and power together (try more times if it wont boot).
Click to expand...
Click to collapse
thanks for the response, I want to try this method too, just wondering do you have any idea how to flash the file form bootloader, given i donot have fastboot, or more precisely fastboot would not see my device, but adb does. (but if I try to reboot to download/fastboot from adb the phone just goes to sleep)
thanks in advance
Avo_GH said:
thanks for the response, I want to try this method too, just wondering do you have any idea how to flash the file form bootloader, given i donot have fastboot, or more precisely fastboot would not see my device, but adb does. (but if I try to reboot to download/fastboot from adb the phone just goes to sleep)
thanks in advance
Click to expand...
Click to collapse
Flash in bootloader the hosd image for your actual firmware and you should be able to use fastboot/download