Develop Bugs

A few questions before first root attempt

Ok, going to follow the SimpleRoot OTA 1.47 how-to, but I have a few questions first.
How do I back up things like my Contacts?
What the latest "radio" and how do I check and get the newest?
How do I wipe caches? Or will the SimpleRoot guide tell me?
Any ROM recommendations? I was thinking of just trying Fresh.
Do I need to do any adb setup prior to starting?
I have been reading through the guides, but there is SO much info here, it takes too long to get through it all. Plus, I'm not even sure of all the questions I need to ask!
Thanks in advance for any and all help!

1. Use Titanium Backup. It will back up whatever you want, I backed up EVERYTHING (apps + system data) and it brought back all my settings, texts, even my scenes. I had to use Unrevoked on my 1.32.651.6 stock build to install TB, followed TheBiles "Idiot-Proof" guide for that part.
2. The radio is the baseband. I actually never flashed mine, and I haven't had issues, but I don't use 4g so I wouldn't know how that works. There are links to a few radios here, but otherwise check the thread or webpage for the custom ROM you want to flash and it might link to the recommended radio.
3. Wiping caches is done through recovery (Amon RA, Clockwork, or using ROM Manager from within a rooted ROM). You do it right before you flash the custom ROM. SimpleRoot will just root the phone, then you'll want to install ROM Manager and use that flash your preferred recovery (that's a whole separate debate).
4. I've been reading up a lot in the last day or two, and Fresh seems to be very popular. I'm using it right now, no problems so far! I've used DC, I had a couple of issues, CM6 is cool but still changing all the time. Go with Fresh at least to get your feet wet. Follow the guide that flipz provides in his Fresh thread.
5. I didn't use SimpleRoot, I rooted manually using ADB. If you're comfortable with using a terminal/command line (or at least typing and following directions) ADB might be a good idea. But if SR gives you a full-root, you don't need ADB at all. It's basically just a telnet connection to your phone.
Hey, whatdya know? I answered them all! There may be better answers, but I think this is all correct. PM me if you need more help, or I'll subscribe to this thread for a few days. I'm new but I'm learning fast and I LOVE this stuff!
Also, here's a good portal for you: http://forum.xda-developers.com/showthread.php?t=709267

Titanium backup works great for most things but you have to be rooted to use it. Your contacts should be backed up directly to your google account if you have done it correctly. When you add a contact to your phone it will ask if you want to add it to google or as a "phone" contact. Make sure you save it as a google contact. Or you can go to your google account on your computer and sync all your contacts. I used SimpleRoot to get my phone started and then I went through this thread:
http://forum.xda-developers.com/showthread.php?t=715915
That is where I started with everything.....fully unlocked and stock rooted with the newest radio. I also used Amon recovery from SimpleRoot instead of Clockwork. SR will clear all your cache, factory data, etc. Im running Damage Control ROM right now and love it. But it's fun to get your phone rooted and then just start using root apps and go from there. Oh, and the best thing for me about using SR and then going through the next thread I posted is that you dont have to use ADB. ADB is pretty simple but the SR + thread process took me about 25min.

Yeah, on that note, it's super-easy to just make a Nandroid or Clockwork backup of your flash, then flash something else to try it out. If you want to go back, just restore the backup and you're right where you were before.
And, of course, backing up contacts on Google is easier.

Running through the SimpleRoot and it got to Starting Part 2... and it's just hanging out doing nothing, been that way for a few minutes now. I didn't copy the PC36IMG file to the SD card, was I supposed to?
Will it bork anything if I disconnect, switch back to Disk Drive as the connection type and drop the file on the SD card? Do I need to do that? Am I retarded?

Not sure as I went through toast's manual method, but it shouldn't do any damage to start over. If Android is still running, I think the system will still be intact.

Well, I think I figured it out, sort of. I never got prompted to reboot into the bootloader until I disconnected the phone. Once I did that, it told me what to do. But, when I installed the update, the bootloader gave me this message: Main version is older, update fail!
Do I need to use the PC36IMG file for 1.47 now? SimpleRoot did push the PC36IMG file to the phone, btw.

ElectricWraith said:
Well, I think I figured it out, sort of. I never got prompted to reboot into the bootloader until I disconnected the phone. Once I did that, it told me what to do. But, when I installed the update, the bootloader gave me this message: Main version is older, update fail!
Do I need to use the PC36IMG file for 1.47 now? SimpleRoot did push the PC36IMG file to the phone, btw.
Click to expand...
Click to collapse
i had the same issue, you need to make sure all the steps are complete before you go into step 4 and boot into bootloader...so make sure after pushing the files you finish step 2 and 4...it worked for me...my pc kept hanging on some steps so i tried it on a different pc and it went throught perfectly the first time around.

Uhh, starting to get a little worried here. I deleted the PCIMG36.zip file per the "Starting Over..." thread, and copied the su-2.1 file on to the SD card. Rebooted into bootloader, selected Recovery per the instructions, now I have a red triangle with and exclamation point and an unresponsive phone!

ElectricWraith said:
Uhh, starting to get a little worried here. I deleted the PCIMG36.zip file per the "Starting Over..." thread, and copied the su-2.1 file on to the SD card. Rebooted into bootloader, selected Recovery per the instructions, now I have a red triangle with and exclamation point and an unresponsive phone!
Click to expand...
Click to collapse
you're fine that's just telling you that you're in recovery mode follow the steps....it should tell you to run a command in you're command prompt which will get you into recovery and then you backup nand, wipe, and load image from sd card

Ah, OK. I pulled the battery and it came back to life. Didn't see anything in that thread about commands, but I will read it again.

just boot your phone holding power and volume up button and then when you see the white screen go down to recovery and press the power button...now you should be in recovery mode from there just follow instructions. you should backup nand, wipe cache and wipe data, and install rom from sd card.

That's the problem, following this thread: http://forum.xda-developers.com/showthread.php?t=715915, I don't get any instructions for the recovery portion that match what I actually get on the phone. I don't get the different menu so I don't get a chance to flash from the su-2.1 file.
Arrrgh! Here's what I did:
Replaced the PCIMG36.zip file that was in the SimpleRootOTA folder that I downloaded with the PC36IMG-1.47.651.1_eng-hboot_RA-1.7.0.1.zip file (renamed to PCIMG36.zip)
Ran SimpleRootOTA, followed all instructions
When I got to the place in Step 4 where I was supposed to be prompted to install the update at the bootloader, it didn't happen. I assume that this was due to the fact that I had already applied that update
I unplugged, looked in the root of the SD card, found that the PCIMG36.zip file had not been pushed.
I copied the file on to the SD card, rebooted into the bootloader, let it scan the PCIMG36.zip file and apply the update, then rebooted.
So, that's where it sits now. I'm out of time and can't do anything more with it, so I just re-installed MyBackup and am restoring apps and data.
Any ideas as to what I should do next?

Hopefully you are just transposing numbers in your post? According to the thread you linked, the name of file should be PC36IMG.zip....you are writing PCIMG36.zip....those are very different.
edit...and if you are getting stuck at step 4...that sounds like what you did.

youngdhillon said:
just boot your phone holding power and volume up button .
Click to expand...
Click to collapse
volume DOWN button
2. Power off your phone.
3. Hold down the Volume Down and Power buttons until the white screen appears.
4. HBOOT will scan the PC36IMG.zip file. You'll see a blue progress bar on the right side of the screen.
Click to expand...
Click to collapse

ElectricWraith said:
That's the problem, following this thread: http://forum.xda-developers.com/showthread.php?t=715915, I don't get any instructions for the recovery portion that match what I actually get on the phone. I don't get the different menu so I don't get a chance to flash from the su-2.1 file.
Arrrgh! Here's what I did:
Replaced the PCIMG36.zip file that was in the SimpleRootOTA folder that I downloaded with the PC36IMG-1.47.651.1_eng-hboot_RA-1.7.0.1.zip file (renamed to PCIMG36.zip)
Ran SimpleRootOTA, followed all instructions
When I got to the place in Step 4 where I was supposed to be prompted to install the update at the bootloader, it didn't happen. I assume that this was due to the fact that I had already applied that update
I unplugged, looked in the root of the SD card, found that the PCIMG36.zip file had not been pushed.
I copied the file on to the SD card, rebooted into the bootloader, let it scan the PCIMG36.zip file and apply the update, then rebooted.
So, that's where it sits now. I'm out of time and can't do anything more with it, so I just re-installed MyBackup and am restoring apps and data.
Any ideas as to what I should do next?
Click to expand...
Click to collapse
ok if you has updated without any errors and you're rooted...
1)turn off your phone power it back on holding the volume down button and power button at the same time
2)when you see the white screen with HBoot menu scroll down using volume down button, highlight recovery and press power button.
3)you should now see a different menu (black&green) you are now in recovery from here:
4)select backup nand it will ask you to confirm hit power button and wait till it backs up you're nand
5)go down to wipe data...highlight wipe data hit power, confirm
6)wipe cache...confirm
7)load rom from sd card (you should have the su-2.1 in you're sd card) it will let you choose, choose su-2.1 hit power, confirm and let it finish.
you're done wait for the phone to reboot into you're new rom

sablesurfer said:
volume DOWN button
Click to expand...
Click to collapse
oops sorry about that, volume down

Yes, I was just transposing digits, DERP.
I will try again later. Thanks for all the help!

Well, I just booted into the bootloader, it scanned the PC36IMG.zip file, but didn't do anything else but put me back at the bootlader menu. I selected Recovery, hit the power button, then black screen with image of phone and red triangle w/exclamation point.
No idea what's wrong or what to do now except pull the battery.

ElectricWraith said:
Well, I just booted into the bootloader, it scanned the PC36IMG.zip file, but didn't do anything else but put me back at the bootlader menu. I selected Recovery, hit the power button, then black screen with image of phone and red triangle w/exclamation point.
No idea what's wrong or what to do now except pull the battery.
Click to expand...
Click to collapse
I remember this problem and I'm trying to remember what I had to do. It seems like after it scanned the PC36IMG.zip it asked if I wanted to scan and I had to say "no" and then after that I could boot in to recovery. I remember it being some dumb little mistake that I made like 2 times in a row and then had a "d'oh" moment when I realized why I kept getting the red triangle. Man, I'm gonna try to remember this and post later. Hopefully you get it though.

Cannot boot to OS at all only Fastboot or into recovery without USB connected

I was copying my SD Card to my computer. At some point I forgot I was transferring files and disconnected the usb cable. I reconnected the cable and all seemed right. So I continued on and rebooted my phone.
After a few minutes I noticed the green notification light blinking and assumed I had a text or mail. When I hit the power button on top to wake the phone the screen never came on. I pulled the battery and tried to reboot the phone. It would just vibrate 5 times and the screen would stay blank. So i tried recovery and it would work only with the USB cord plugged in. But it wouldn't do a nandroid backup or even see the sdcard.
when in recovery I get the error E:Can't mount /dev/block/mmcblk1p1 (or /dev/block/mmcblk1)
I tried getting a adb shell but it says no device connected
I tried using fastboot flash boot boot.img and fastboot flash system system.img
they would error with FAILED (remote: signature verify fail)
anyone have any suggestions?
oh in windows device manager it say ADB bootloader only when I am in HBOOT when in fastboot it says nothing but since it did push the system image I assume it does work.
if i go into recovery though (Windows7 Enterprise 32bit) it asks for a Qualcomm CDMA driver real quick(2 seconds) then goes to Unknown Device

fader01 said:
oh in windows device manager it say ADB bootloader only when I am in HBOOT when in fastboot it says nothing but since it did push the system image I assume it does work.
if i go into recovery though (Windows7 Enterprise 32bit) it asks for a Qualcomm CDMA driver real quick(2 seconds) then goes to Unknown Device
Click to expand...
Click to collapse
Sounds like you corrupted a partition or two. Just get an RUU PB31IMG.zip, copy it your card (you may have to take it out and fix it in windows first), and let bootloader see it. There are ways to manually NANDroid your phone in ADB/Recovery, but it doesn't sound like you want to go that deep nor do I know how to tell you to do it from the command line.
Good luck!

Thanks for the reply. The phone will not mount or see the SD Card. I put the sd card in my storm and it formatted it I put it into the Incredible but it still will not mount the SD Card.
I did go to the verizon store and my hopes where they had some way to format the partitions and force the OS on it. The guy looked at the phone and said we dont have a recovery console for the Incredible so I will have a new one sent to you probably will be Tuesday.
I thought the Dallas Cowboys boot screen and fastboot screen would tell him something wasnt right but he didnt know or he didnt care. I also thought it was odd he gave me the phone back. Shouldnt he have kept it to send back in?

I have ran into the same issue. Basically my phone was bootlooping after a bad rom install(my guess). Then when I tried my nandroid recovery backup, I got to this black screen and the phone would vibrate 5 times! I have never had this issue before.
I have tried various RUU PB31IMG.zip's to flash back to a stable system and nothing works. I have noticed after flashing different RUU images(stock 2.2, stock 2.1), the phone will either vibrate 3, 4 or 5 times. I believe these could be error code messages of some kind.
Has anyone else gotten this black screen, and the 5 vibrations????? This seems like it should be called the black screen of death because it honestly makes me want pull my hair out in frustration! Any knowledge would be greatly appreciated. thanks.

google this error: E:Can't mount /dev/block/mmcblk1p1 and there should be a link to a cyanogen forums thread and a link to an xda thread. those two will contain the information necessary to repartition your internal storage so you can boot into the OS again

illalliance said:
I have ran into the same issue. Basically my phone was bootlooping after a bad rom install(my guess). Then when I tried my nandroid recovery backup, I got to this black screen and the phone would vibrate 5 times! I have never had this issue before.
I have tried various RUU PB31IMG.zip's to flash back to a stable system and nothing works. I have noticed after flashing different RUU images(stock 2.2, stock 2.1), the phone will either vibrate 3, 4 or 5 times. I believe these could be error code messages of some kind.
Has anyone else gotten this black screen, and the 5 vibrations????? This seems like it should be called the black screen of death because it honestly makes me want pull my hair out in frustration! Any knowledge would be greatly appreciated. thanks.
Click to expand...
Click to collapse
I got the 5 vibration deal when I was trying to boot into recovery.....but was pressing volume up/power, instead of vol down/power......the 5 vibrations are a Qualcomm diagnostic test.

SLOflatlander said:
google this error: E:Can't mount /dev/block/mmcblk1p1 and there should be a link to a cyanogen forums thread and a link to an xda thread. those two will contain the information necessary to repartition your internal storage so you can boot into the OS again
Click to expand...
Click to collapse
I had googled that before making this post, nothing I found had helped me. I cannot say, for sure, that I found the post you are referring to though. I did finally manage to get the system to see the sdcard and PB31IMG.zip. I took the rom.zip from the Froyo RUU and I renamed it pb31img.zip. It went through and flashed everything but still nothing. When I later tried to do the same thing with the rom.zip from the 2.1 RUU the system said that it was an older version and would not flash it. So this seems to me that the flash went OK. Its like the main OS partition isn't bootable or something the system knows the OS is there it just cannot boot to it.

You said it. The main partition is corrupt, I will try and find the link to the thread about how to restore it just give me a second.
Here is the link Talk to Ciwrl; he is a very smart person when it comes to these problems.

tdavis42 said:
You said it. The main partition is corrupt, I will try and find the link to the thread about how to restore it just give me a second.
Here is the link Talk to Ciwrl; he is a very smart person when it comes to these problems.
Click to expand...
Click to collapse
I trashed my internal partitions yesterday and used this method to fix it.....had to end up un-rooting and starting over after I got the partitions back in order....but it did fix the problem.

tdavis42 said:
You said it. The main partition is corrupt, I will try and find the link to the thread about how to restore it just give me a second.
Here is the link Talk to Ciwrl; he is a very smart person when it comes to these problems.
Click to expand...
Click to collapse
Thanks a lot. I will work on it after work tonight.

Boot Loop stuck in Animation help.

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

[Q] Repair platform.xml?

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).

My Honor 7x BND-L21 is quite broken, need help

Hello, sorry for the generic title, but i'm quite the noob about android modding and stuff.
Anyway I wanted to root my phone, just to stream some music to my stereo system. How naive I was...
So I unlocked the bootloader, installed twrp with adb and SuperSU with twrp. Everything was fine and phone was rooted but my past naive me thought "well let's try a custom rom, why not". So I went forth and downloaded some stuff from getdroidtips and what I understood is that all I needed to do was to do a wipe, then install the zip file via twrp. I did that and didn't work. After that I realized I made a crucial mistake: I didn't backup my phone from twrp, so I was there with no OS, quite panicked and frustrated. So I tried some other roms, finally I got one that worked, this: https://forum.xda-developers.com/honor-7x/development/openkirin-aosp-8-0-honor-7x-t3746257
It works but it's barebones and on boot it shows a message: "There's an internal problem with your device. Contact your manifacturer for details.". So, I tried recovering from HiSuite, recovery mode etc but nothing worked, I reinstalled SuperSU in the new OS via twrp to see if that would help somehow, but no. in the end I had the even more naive thought that maybe unrooting would allow me to repair via hi suite or something, so I mindlessly selected "complete unroot" on the SuperSU app, and this was the second big mistake, the process somehow ****ed up the twrp install and it no longer works. Instead, if I try to enter twrp with power button + volume up button, it shows the regular "your phone has been unlocked" screen and then comes up for a split second a black screen with, on the bottom half of the screen the "no command" logo, under it some lines of code that I can't read. It suddenly disappears and sometimes enters in a bootloop showing this screen and powering off every time.
If I keep power button pressed bootloop ends and the phone boots "regularly" in the openkirin OS.
I tried reinstalling twrp the same way I did the first time. No error on adb but same no command behaviour
So what I got now is:
kind of bootlooping no command window
openkirin OS with internal problem message
fastboot and rescue mode
it seems to work on adb (everything is fine if I type adb devices)
not working HiSuite recovery
not working Huawei eRecovery
not working download mode (I guess? the power+volume up+volume down combination)
Maybe I should mention I also did a data wipe (?? the option on the right next to "advanced wipe" in the Wipe screen, if I remember correctly) in twrp before installing openkirin, it was suggested on a yt video about how to install openkirin. And that, at a stage I tried using MultiTool but it gives me an error: "exception during a web client request. Error#9", while at the bottom left it says "downloading AdbWinUsbApi.dll..."
Sorry for the general noobishness and the bad english that might be there.
So, any tips for bringing back the phone to normal? Or at least repair twrp??
Please help, I hate needing to throw this phone away just because I wanted to stream some music and because of a couple of stupid errors

Sorry for not answering earlier. It seems, between TWRP and stock recovery, you have messed up I think. When there is no proper recovery it become difficult to bring back the phone. You should try to put it in fastboot mode first, by powering off, pressing the volume lower button and connecting it to computer. Try installing TWRP and flash a custom rom other than openkirin from there if possible. Fastboot is the choice to go if recovery is messed up.

sdivk said:
Sorry for not answering earlier. It seems, between TWRP and stock recovery, you have messed up I think. When there is no proper recovery it become difficult to bring back the phone. You should try to put it in fastboot mode first, by powering off, pressing the volume lower button and connecting it to computer. Try installing TWRP and flash a custom rom other than openkirin from there if possible. Fastboot is the choice to go if recovery is messed up.
Click to expand...
Click to collapse
No worries, I managed to fix it anyway. Some things might be obvious but I'll share what I did nevertheless, in case some other newbie finds himself in a similar situation.
So there was seemingly no way of reinstalling twrp nor the stock recovery. But luck came my way and by almost random clicking I found out that, even if multitool closed as soon as I clicked the ok button in the error message, if I simply ignored the error, the program worked just fine (as I write this I installed another version and it gave no error message). So I played with it a bit and found out that it can flash twrp and it does not need a file from you, it already has a twrp version ready to install. I did that and it worked. It looks like the first twrp file I used didn't work anymore or was someway corrupted by the countless things I tried. So, with twrp working again I was able to backup the sloppy openkiring OS and try the unbrick tool. So I browsed the internet for a guide. Guides always mention as the first step for unbricking using the VENDOR.img file located inside a full stock rom. Problem is, 99% of the times they provide a rom without the needed file. So after some tries I found a good complete stock rom with the VENDOR.img here: drive.google.com/file/d/1tjHefytEWbpuV1f4YjX8AaSMzT6jr8TQ/view but I can't remember which forum/site I found it in.
I followed the guide which involves:
-extracting the UPDATE.APP file contained in the provided zip with huawei extractor tool into an X folder on your pc
-copying the VENDOR.img file contained in the X folder, on the root folder of the sd card
-backing up OS (if there's any) via twrp (I had something like 50 partitions, I guess that was messing things up a bit, but for safety I backed them all up)
-doing an advanced wipe from twrp selecting ALL checkboxes BESIDES the SDcard of course
-flashing the vendor.img file via twrp selecting the "Vendor" partition when prompted
-downloading the update_full_[your model]_hw_[your region].zip file, in my case update_full_BND-L21C_hw_eu.zip
-extracting the UPDATE.APP file contained in update_full_BND-L21C_hw_eu.zip with Huawei extractor tool in some other folder Y
-looking for a file named cust.img/CUST.img/version.img/other_name.img (I don't know which other names it can have, I was lucky and had a VERSION.img file in it)
-rename the cust.img/CUST.img/version.img/other_name.img to CUST.img and copy it from the Y folder to the X folder
-boot your phone into fastboot mode
-connect phone to multitool via usb and select the "unbrick" tab
-there, Multitool asks for a folder, give it the X folder. There are some checkmarks on the Multitool "unbrick" page. 4/5 of them should become checked after the folder input. In my case the first 4
-then, simply press the unbrick button
-wait and pray (it can look like it freezes while it's copying the system.img file but wait, it'll be fine)
So I did that and it worked flawlessly, the phone booted slowly but surely into EMUI 5.1 with Android 7.0 I think and everything was fine.
At that point I had a working OS and a working twrp but wanted to go back to the OS I was used to, Android 8.something so, I tried connecting the thing to HiSuite and it automatically asked if I wanted to update, not to 8.something but to 9.1. I thought "SURE I DO!" and updated flawlessly (I thought 9.1 hadn't even been released here in Italy).
When it booted I found out the new OS was working like an antivirusless xp pc: it didn't recognise the SIM, it would crash every 20 seconds, app downloads got stuck at 99%, if it felt like it, it rebooted, pc connection was not stable. Besides, the update being "official" and installed from "trusted" sources (HiSuite), it completely wiped twrp.
And that was the "OH ****, here we go again" moment: no twrp and worse-than-ever-working OS.
So because of the new EMUI version, I guess, Multitool kept recognizing the phone but stopped offering its own recovery, eRecovery, twrp files available for flashing. I was completely frustrated with all of this and decided to give up, but I made the last effort: I tried the relock function in multitool. So I provided the key, pressed relock, waited, prayed, and finally cheered. It worked like a charm. Phone runs now on EMUI 9.1 with locked bootloader without problems. Finally
So I guess in the end I payed 4 euros for a nice update, a painful and frustrating trip into android modding and a lesson : never do android modding!
no, just kidding, don't do it just if you are a newbie AND you don't want to risk to throw the phone in the grabage.
In all other cases consider it carefully
Oh, and also, God bless the MT Team and Russia altogether!! thanks

Quite an experience. All the best. ?

Lol sounds fun. I've bricked my Huawei Mate SE/Honor 7x more times than I can count. I'm just awaiting my 9.1. I want my GPU Turbo! Is it as good as it's supposed to be?