Related
Hello all
I suspect that either my Nexus has a hardware fault (internal memory) or I bricked it somehow.
For the past few weeks the phone has been getting stuck on the google boot screen quite a lot - It takes several attempts
to start up each time so I've been trying to keep the battery from running down.
The other day while I was attempting to switch roms I put the stock img on my SD card but when I went to flash it CWM
couldnt mount my (internal) SD Card. Senior forum member Caliban2 suggested that it could be my recovery so I installed CWM 6.0.0.7 non-touch using fastboot and, like magic, the phone started up -though I suspect this may have been luck.
I rebooted the phone out of curiosity and it got stuck on the google boot screen - no amount of battery pulling and restarting could coax
it back to life, so I went into CWM again to discover that it could not mount the SD Card, I was getting the 'cannot mount' and 'E:Unable to open ums lunfile(no such file or directory)' error messages. My windows 7 PC could see the phone but said that their was non memory inserted. Out of curiosity I installed CWM 5.0.2.0 but that produced the same results.
So now my phone appears dead, is the internal memory or something related to it is broken? I have seen things on here about using an unbricking tool in Debian Linux or flashing stock using odin but I confess that I have not tried these solutions and don't fully understand them (yet).I wussed out and dropped the phone into a local repair workshop, I imagine they will be trying these same steps themselves and they say it will take them a few days to get back to me.
My problem is that I need a phone for work and I gave my backup phone (HTC Hero) to my dad recently. Should I just take the plunge
and go out today and buy a new phone? Or is there a reasonable chance that these guys can fix my nexus s, or that I might be able to?
I'm a relative 'noob' at this so I thank you all for your advice in advance, it's much appreciated.
Derek
Do a search for flashing fastboot images. Download the 4.0.4 fastboot image from google and flash it as directed through fastboot. This may sort out your problems.
Afterward, if necessary, format the /sdcard too. I would do this afterward so that maybe you can get a backup of all the stuff on it before it's gone forever.
Thanks, will do. It's in the shop at the moment, I suspect this is probably what they're doing now.
Perhaps subconsciously I'm just looking for someone to tell me it's irreparable so I can rush out
and pick up a Galaxy Nexus.
Harbb said:
Do a search for flashing fastboot images. Download the 4.0.4 fastboot image from google and flash it as directed through fastboot. This may sort out your problems.
Afterward, if necessary, format the /sdcard too. I would do this afterward so that maybe you can get a backup of all the stuff on it before it's gone forever.
Click to expand...
Click to collapse
Hey Harbb
Just wanted to give you an update on this, got it back from the shop who said they would need to send it to Samsung for a hardware repair, didn't expect it to work but fastbooted the stock bootloader, radio and image to the device and it's now working!
I've already moved onto a Galaxy Nexus on contract but at least now I can make a bit of money back off my old phone.
Thanks again for the advice
Derek
Harbb said:
Do a search for flashing fastboot images. Download the 4.0.4 fastboot image from google and flash it as directed through fastboot. This may sort out your problems.
Afterward, if necessary, format the /sdcard too. I would do this afterward so that maybe you can get a backup of all the stuff on it before it's gone forever.
Click to expand...
Click to collapse
So I feel like I am pretty experienced when it comes to the whole ROM/Root scene, I've had the OneXL, Galaxy S3, and Nexus 4.. but I've always had a difficult time with the One XL and ROMs... I always seem to run into major problems.. Right now I can only access the fastboot area of the phone, it will not go into recovery (i have even tried reflashing recovery but no luck) and no matter what, it bootloops constantly. I had ViperXL running fine on the device but I tried to install ElementalX kernel for the first time and now the phone is Kaput.. Any ideas??? Could this be a semi-brick?
did you specifically try to go into fastboot and fastboot flash recovery recovery.img
?
because this phone is pretty much either "it's reading qsb mode in device manager bricked" or "i don't know what i'm doing and cannot figure out what to do next NOT BRICKED" (i'm not rippin on you; if you pull up my history, it even happened to me once and i had to make a baww thread for someone to help me figure it out. turns out, don't click factory reset in bootloader.) there is one other way, but it involves acceptin the OTA with your CID having been changed
wdkingery said:
did you specifically try to go into fastboot and fastboot flash recovery recovery.img
?
because this phone is pretty much either "it's reading qsb mode in device manager bricked" or "i don't know what i'm doing and cannot figure out what to do next NOT BRICKED" (i'm not rippin on you; if you pull up my history, it even happened to me once and i had to make a baww thread for someone to help me figure it out. turns out, don't click factory reset in bootloader.) there is one other way, but it involves acceptin the OTA with your CID having been changed
Click to expand...
Click to collapse
Actually, I was just about to post that I fixed it!! I relocked the bootloader, then unlocked again(i thought maybe it would wipe all my data for me, and it did!!) So I then reflashed the recovery and got into it, reformatted the USB mount in windows with FAT32 and then placed a new ROM onto the device. And it booted right on up!
By the way, this ind of thing happened to me too before... but I never had to do the bootloader thing.. Thanks for the input though!
Hello everyone, I hope I'm writing in the right section.
I'll go straight to the issue: after finally deciding to install a custom rom on my device (HUAWEI GX8), i decided to opt for this one: https://forum.xda-developers.com/moto-g4-plus/development/rom-aospextended-rom-v3-0-t3537792
The first problem i had to face was the "ERROR:7" (so the rom seemed to be made for a different phone than mine) that occured while installing the rom in the twrp, but being that the rom was specifically made for my phone I followed this guide: https://www.youtube.com/watch?v=wed03948gcg and fixed the issue, resulting in a perfect installation... or so I thought.
After rebooting, the phone didn't start the os but was stuck in the twrp (I tried rebooting multiple times and in different ways of course).
Being that I had made a backup before installing the new rom, I decided to restore that backup from the twrp... but still the phone is stuck in the twrp and I don't know what to do :crying:
I hope somebody can help me because I'm starting to panicking.
Cheers in advance.
PS: I'm a complete newb so this was the first time I installed a custom rom, I tried searching for this problem online but couldn't find a solution that fitted me. I hope I won't ask too many stupid questions.
SlimeAndroid said:
Hello everyone, I hope I'm writing in the right section.
I'll go straight to the issue: after finally deciding to install a custom rom on my device (HUAWEI GX8), i decided to opt for this one: https://forum.xda-developers.com/moto-g4-plus/development/rom-aospextended-rom-v3-0-t3537792
The first problem i had to face was the "ERROR:7" (so the rom seemed to be made for a different phone than mine) that occured while installing the rom in the twrp, but being that the rom was specifically made for my phone I followed this guide: https://www.youtube.com/watch?v=wed03948gcg and fixed the issue, resulting in a perfect installation... or so I thought.
After rebooting, the phone didn't start the os but was stuck in the twrp (I tried rebooting multiple times and in different ways of course).
Being that I had made a backup before installing the new rom, I decided to restore that backup from the twrp... but still the phone is stuck in the twrp and I don't know what to do :crying:
I hope somebody can help me because I'm starting to panicking.
Cheers in advance.
PS: I'm a complete newb so this was the first time I installed a custom rom, I tried searching for this problem online but couldn't find a solution that fitted me. I hope I won't ask too many stupid questions.
Click to expand...
Click to collapse
The ROM that you flashed was NOT made specifically for your device, you have HUAWEI GX8, the ROM was made for Moto G4 Plus. You would have know this if you had looked at the forum it was posted in. It was posted in in the Moto G4 forum, not in a Huawei forum.
The "fix" that you used didn't help.it successfully flash, it only help you "force" the ROM to flash. You bypassed a safety measure that was designed to keep you from flashing the wrong thing, now you're dealing with the results of forcing it to flash on a device it wasn't meant for.
Learn to pay attention to what you are reading.
You need to flash your stock firmware to fix this.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
The ROM that you flashed was NOT made specifically for your device, you have HUAWEI GX8, the ROM was made for Moto G4 Plus. You would have know this if you had looked at the forum it was posted in. It was posted in in the Moto G4 forum, not in a Huawei forum.
Learn to pay attention to what you are reading.
You need to flash your stock firmware to fix this.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
I'm sorry I may have linked the wrong page, either way on the website of the rom I downloaded the right thing, I'm sure about it because I checked it multiple times (the error I made in writing the post may be cause by me panicking, sorry :crying: ).
While waiting for answers I installed a different twrp and it WORKS! I'm so happy I could cry. Thank you nonetheless for your help (Still dunno what the problem was though xD)
@SlimeAndroid as you installed ROM of different phone, it might not get installed as ROM zip contains script for Mobile verification.
I assume you had wiped /system and after installation of wrong ROM you rebooted your phone without reading if TWRP said you don't have any OS installed or what. (That means you have ran without any OS, that may be reason why you stuck with TWRP.)
But after Restoring Backup of Working ROM, it should boot your device, but it doesn't.
We (on G4 plus) have faced issue: when phone start, it always goes to TWRP/recovery instead of booting to system.
Are you facing similar ?
Solution for this problem was to clear bootloader data, by using fastboot commands (i assume you know how to do, otherwise ask for better explanation )
Run this two commands from Comand Prompt
-> fastboot oem fb_mode_set
-> fastboot oem fb_mode_clear
This worked for us. You can try, if doesn't work then flash Stock ROM.
____Mdd said:
@SlimeAndroid as you installed ROM of different phone, it might not get installed as ROM zip contains script for Mobile verification.
I assume you had wiped /system and after installation of wrong ROM you rebooted your phone without reading if TWRP said you don't have any OS installed or what. (That means you have ran without any OS, that may be reason why you stuck with TWRP.)
But after Restoring Backup of Working ROM, it should boot your device, but it doesn't.
We (on G4 plus) have faced issue: when phone start, it always goes to TWRP/recovery instead of booting to system.
Are you facing similar ?
Solution for this problem was to clear bootloader data, by using fastboot commands (i assume you know how to do, otherwise ask for better explanation )
Run this two commands from Comand Prompt
-> fastboot oem fb_mode_set
-> fastboot oem fb_mode_clear
This worked for us. You can try, if doesn't work then flash Stock ROM.
Click to expand...
Click to collapse
If you read the post above yours, you'll see they solved the issue.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
You always have to make sure the download is for your model of phone(settings -about) and always make sure the download has properly downloaded and I use md5 checksum as this verifies the download is not courupt.
Sent from my iPhone using Tapatalk
read this 3 times from start to finish before you start asking questions....itll help with most of your questions...also...
When your unlocking your bootloader using the "fastboot flashing unlock" command....after the system has booted.... boot back into fastboot and also run the "fastboot flashing unlock_critical” this makes this device nearly unbrickable.... please do it you won't regret it.
Next twrp is in boot.img with a/b devices..so if you flash twrp and want to root you have to reflash the stock boot.img of your rom before you flash magisk....if you don't you'll have a bootloop that gets you nowheres
http://mata.readthedocs.io/en/latest/
Also, welcome to the forums! Hopefully posts this don't scare away people and potential new devs since it's dead enough around here already.
Feel free to message me if you have questions, I won't jump down your throat.
Thank you for this.
Switched over from a Nexus 6P (that is still working great, to be honest). can't wait to start flashing
Thanks for the link to the document. Didn't realize there are two partitions.
I'm sure this question has been answered before but I'll ask here again for the newbies.
If I root the device with Magisk but stay with the stock ROM, does the OTA updates work? If the updates do work, do I have to root each time after the update?
TIA.
csrow said:
Thanks for the link to the document. Didn't realize there are two partitions.
I'm sure this question has been answered before but I'll ask here again for the newbies.
If I root the device with Magisk but stay with the stock ROM, does the OTA updates work? If the updates do work, do I have to root each time after the update?
TIA.
Click to expand...
Click to collapse
They don't work if rooted, however I, and many others, have issues with the OTAs in general anyhow.
It's super quick to just fastboot flash the firmware files yourself anyhow (modify a boot.img beforehand with magisk), and then flash the modified boot.img at the end.
I got in on the Amazon deal...should be here next week. Will be coming from a Nexus6.
Quick question for a Prime Deal newbie. Do you have to unlock the bootloader if you are just side loading the OTA file? I know you have to in order to fastboot any images but I thought the ota file would be fine. No biggie if not just curious.
After another search it looks like you do not have unlock the bootloader just to flash the ota.
Really helpful and it definitely going to keep the rest of the section tidy!
Picked one up also. Coming from/still have a Pixel 2 xl and previously a first gen pixel, so I'm familiar with a/b slots. Not having a perm twrp suuuuuucks. I got my ph1 on Sept security patch and it's updated twice now to the Jun patch will that cause issues with any root or roming?
Also coming from the Nexus 6. Looking forward to this phone.
thank you for the heads up.
Sent from my SD4930UR using XDA Free mobile app (Yep Firephone)
crixley said:
Also, welcome to the forums! Hopefully posts this don't scare away people and potential new devs since it's dead enough around here already.
Feel free to message me if you have questions, I won't jump down your throat.
Click to expand...
Click to collapse
Thanks for the welcome everyone!!
Coming from a Nexus 6 running PureNexus. Phone is still rocking, but my goodness you should see how busted my screen is.
I'm excited to get the Essential set up and flash some ROM and camera goodies!
Tech_Savvy said:
read this 3 times from start to finish before you start asking questions....itll help with most of your questions...also...
When your unlocking your bootloader using the "fastboot flashing unlock" command....after the system has booted.... boot back into fastboot and also run the "fastboot flashing unlock_critical” this makes this device nearly unbrickable.... please do it you won't regret it.
Next twrp is in boot.img with a/b devices..so if you flash twrp and want to root you have to reflash the stock boot.img of your rom before you flash magisk....if you don't you'll have a bootloop that gets you nowheres
http://mata.readthedocs.io/en/latest/
Click to expand...
Click to collapse
Thanks for the heads up, wonder if it will help the people who don't know which hole to put the sim card removal tool into.
[emoji23] I watched my brother keeps poking the microphone hole for like the 5th time until he figured it out. It is kind of a bad design imho tho.
Sent from my PH-1 using Tapatalk
This seems a welcome thread. I haven't tweaked Android for about 2½ years. From 2010 on I always had custom recovery and root and ROMs, but my last device (htc10) I didn't root, life got too busy.
Just got essential from Amazon, and trying to figure out what this AB slot stuff is is confusing the hell out of me. Also, this phone seems laggier than any device I've had, and I also just noticed a lot if the text is outlined with black, like on the LG get. Gotta get rid of that.
Sorry if this is the wrong place for those comments.
If anyone could give an explanation to what the AB slot is, to someone who is already pretty familiar with using custom recoveries, and understanding the partions (to a degree), I'd super appreciate it.
Again, I've been away from xda and customizing Android for about 3 years.
Anyone else feeling like this device isn't quite what they hoped? I always saw it at sprint stores and couldn't put it down. Now it's in my hand, doesn't seem so great. Think my htc10 is better, but maybe I'm missing how to make it great.
I hope this is in the right place.
scottspa74 said:
Anyone else feeling like this device isn't quite what they hoped? .
Click to expand...
Click to collapse
you can't beat it for $250, but I think I'm getting the OnePlus 6T or OnePlus 7 when it comes out.
installing TWRP and customs roms is such a chore on this device. I had AOSiP installed...but for some reason which I couldn't explain, it didn't feel like AOSiP on my Nexus 6P or OnePlus5 (that I just gave to my mom). Substratum worked...Magisk worked. But something didn't feel right. If I'm going to have to be on a stock ROM, I'd rather be on OxygenOS with its additional customizations.
only one of my 9 USB-C to USB-A cables seem to work for file transfer AND fastboot AND charging. It also happens to be the shortest cable I have.
See this weirdness where text is surrounded by black outline? That happened on LG g stock rom. It was fixed. Is a custom rom only way to fix this on ph1. ? Much thanks.
scottspa74 said:
See this weirdness where text is surrounded by black outline? That happened on LG g stock rom. It was fixed. Is a custom rom only way to fix this on ph1. ? Much thanks.
Click to expand...
Click to collapse
I think your phone high contrast text mode is on. Uncheck that under accessibility
scottspa74 said:
This seems a welcome thread. I haven't tweaked Android for about 2½ years. From 2010 on I always had custom recovery and root and ROMs, but my last device (htc10) I didn't root, life got too busy.
Just got essential from Amazon, and trying to figure out what this AB slot stuff is is confusing the hell out of me. Also, this phone seems laggier than any device I've had, and I also just noticed a lot if the text is outlined with black, like on the LG get. Gotta get rid of that.
Sorry if this is the wrong place for those comments.
If anyone could give an explanation to what the AB slot is, to someone who is already pretty familiar with using custom recoveries, and understanding the partions (to a degree), I'd super appreciate it.
Again, I've been away from xda and customizing Android for about 3 years.
Anyone else feeling like this device isn't quite what they hoped? I always saw it at sprint stores and couldn't put it down. Now it's in my hand, doesn't seem so great. Think my htc10 is better, but maybe I'm missing how to make it great.
I hope this is in the right place.
Click to expand...
Click to collapse
I am with ya on that...I started with Samsung devices, So using Odin for flashing was my cup of Tea. The Nexus6 was my first device using Fastboot, but I ended up using Wug's toolkit most of the time.
From what I gather the A/B slot partitions are the same thing. You basically have a kernel and ramdisk on both partitions. The ramdisk is now your recovery. You just have to make sure when you flash anything, it's to the active partition. The point of A/B slots is so Android can install upgrades seamlessly while still running by installing them to the inactive partition. Click the link in the OP, it explains things pretty well.
I have been pretty happy with the PH-1 so far. I really like the form factor and the notch hasn't bothered my at all. Coming from Note 3/4 and the 6P which was super easy to flash by the extra steps on the Essential don't seem to bad. Sucks that you need a computer most times to flash but not the end of the world.
I haven't flashed a custom ROM yet but I did bump to the P preview for a day or two and then back to stock with EX and Magisk. No issues there but I'm comfortable with ADB and fastboot. No issues with various cables as well whatever I used on my 6P seem fine for this phone as far as charging, adb and file transfers go.
Overall pretty happy.
Okay so I really messed up guys I actually deleted my root partition and while I was trying to find someway to fix it everything just kinda kept disappearing now all that is left is the boot loader mode what I'm looking for is a while custom build for it kernel partition is code everything I also don't really have access to a pc or anything very often if anyone want to take on this huge task I want to help and learn everything I can From this it would be really cool if I could turn it into a pixel seeing as there is nothing left of it I had the latest custom twrp as recovery and havoc 5 with all the GappS but the havoc never properly downloaded so my phone was convinced it was a google pixel 6 some days and a 5 on others has any else messed up this bad ?
Gaber139 said:
Okay so I really messed up guys I actually deleted my root partition and while I was trying to find someway to fix it everything just kinda kept disappearing now all that is left is the boot loader mode what I'm looking for is a while custom build for it kernel partition is code everything I also don't really have access to a pc or anything very often if anyone want to take on this huge task I want to help and learn everything I can From this it would be really cool if I could turn it into a pixel seeing as there is nothing left of it I had the latest custom twrp as recovery and havoc 5 with all the GappS but the havoc never properly downloaded so my phone was convinced it was a google pixel 6 some days and a 5 on others has any else messed up this bad ?
Click to expand...
Click to collapse
What do you mean you deleted your "root partition"? You need to be more specific about exactly what you did, as well as exactly what you want to do. Your entire post is very confusing, and you'll have better luck with more detail and clarity.
Do you still have fastboot mode working? If yes then it is no issue to restore the partions and firmware. I can help you on that if you cant figure it out. But you must have access to at least one other device, android (no root access), linux, mac, whatever. What is your problem? Even if you cant enter fastboot you can probably do a blankflash using a firehose file, if it exists that is.