Ok, so this is an odd issue. I've had my N7 Grouper unlocked and have been running custom roms for a long time now, and about 6 months back I tossed on the All-F2FS version of Slimkat. Everything was running fine and has been since then, up until the last few days. Now the device just reboots randomly after it gets into the system. It runs fine in bootloader or recovery so I know it's not a loose battery connector as I've read about. I'm at a loss as to why and I gave up trying to find out.
I've since been trying to simply wipe my tablet and reset back to a clean install of the All-F2FS Slimkat as I've had or even tried a stock restore now. Nothing I do works at all. I've tried everthing from the modified All-F2FS TWRP 2.7.0.0 that I installed as a part of the move to F2F2 but although it reports that it's wiped everything fine, or flashed a new rom fine, it does nothing in truth. After a quick reboot its as if nothing happened at all. I've then tried to run things from adb/fastboot and I'm even after running all the commands in fastboot which all say they run fine (flashing, reformatting partitions, etc.) nothing at all actually happens to the N7.
Anyone else seen this or have any ideas?
Hello,
please try this command's:
Code:
fastboot erase cache
fastboot erase system
fastboot erase userdata
fastboot erase recovery
fastboot erase boot
Then flash a FactoryImage! At least root and flash again.
Trafalgar Square said:
Hello,
please try this command's:
Code:
fastboot erase cache
fastboot erase system
fastboot erase userdata
fastboot erase recovery
fastboot erase boot
Then flash a FactoryImage! At least root and flash again.
Click to expand...
Click to collapse
I've tried all of those commands multiple times. I'm an old hat at rooting, unlocking, and running custom roms on Android so I've been doing literally everything I can think of. Every command shows that it completes successfully but nothing actually happens. I've tried fastboot erase commands, fastboot format commands, fastboot flash commands, and many many more. I've run six different versions of the factory image, everything from 4.0.0 to 5.1.1. The only errors I've ever seen while working with the tablet is while attempting to erase/format partitions within the recovery there are some errors about not being able to access the cache. I'll update this with the specific errors.
Anyone? I'm at a loss here. I've run everything I can think of and the commands always complete successfully, then don't actually work at all.
I have the 128GB model and I was transferring 32GB worth of music over to my 6P and before it completed I was getting warnings that files couldn't be copied. I stopped it and then looked at the phone on my PC and it was saying it's size was 24.1 GB. It shows the same thing when I look at the storage on the phone. What happened?
If you flashed the factory image, it probably set the partition for userdata to the wrong size. One fix is to go into recovery and perform a factory reset from recovery and it will fix the size. I am not sure if there are other methods that can fix it without doing the reset. Another person may be able to offer a better alternative.
tkoreaper said:
I have the 128GB model and I was transferring 32GB worth of music over to my 6P and before it completed I was getting warnings that files couldn't be copied. I stopped it and then looked at the phone on my PC and it was saying it's size was 24.1 GB. It shows the same thing when I look at the storage on the phone. What happened?
Click to expand...
Click to collapse
Did you flash the userdata.img from the factory images at some point? Doing so always allocates the smallest of the available storage sizes, so it really shouldn't be used. You can fix it by issuing this fastboot command:
Code:
fastboot format userdata
This will wipe your userdata partition so make sure you back up anything important first.
Heisenberg said:
Did you flash the userdata.img from the factory images at some point? Doing so always allocates the smallest of the available storage sizes, so it really shouldn't be used. You can fix it by issuing this fastboot command:
Code:
fastboot format userdata
This will wipe your userdata partition so make sure you back up anything important first.
Click to expand...
Click to collapse
That explains it, thank you. I ended up just starting over so it's all good now.
Heisenberg said:
Did you flash the userdata.img from the factory images at some point? Doing so always allocates the smallest of the available storage sizes, so it really shouldn't be used. You can fix it by issuing this fastboot command:
Code:
fastboot format userdata
This will wipe your userdata partition so make sure you back up anything important first.
Click to expand...
Click to collapse
Hehe that's exactly what I just did (flahsed my own cooked up userdata.img, which cut my size in half), thanks Heisenberg
I was at work when i entered a bootloop. I was doing nothing special maybe using the camera. I was bootloader unlocked rooted on latest twrp and on the latest official dirty unicorn I think 10.4 and everything was fine.
After the bootloop started I tried entering recovery in which it only boot loops. I can only access the bootloader screen. I Can see my device in fastboot devices.
I think my next step is to flash some Google factory images in fastboot. But I was wondering if my device be encrypted with fingerprints and a pin will affect it because I've ran into a problem last year when flashing a new version of TWRP it asked for passcode when one was not set.
I'd love to be able to recover some of my data but I guess if it's Encrypted that is not a chance, so I guess I will fastboot Flash the original images.
Is there going to be any problems when I try to flash Nexus images while it is encrypted with a passcode, Any suggestions?
Yeah, standard answer here is to flash the fastboot images. It'll be wiping/overwriting system and vendor so you shouldn't have any issues with the previous fingerprints. It'd be a good idea to wipe data once you get into TWRP afterwards but I wouldn't worry about wiping/formatting userdata.
Heisenberg said:
Yeah, standard answer here is to flash the fastboot images. It'll be wiping/overwriting system and vendor so you shouldn't have any issues with the previous fingerprints. It'd be a good idea to wipe data once you get into TWRP afterwards but I wouldn't worry about wiping/formatting userdata.
Click to expand...
Click to collapse
Thanks... I was just re reading your huge thread for the 4th time this year.
Heisenberg said:
Yeah, standard answer here is to flash the fastboot images. It'll be wiping/overwriting system and vendor so you shouldn't have any issues with the previous fingerprints. It'd be a good idea to wipe data once you get into TWRP afterwards but I wouldn't worry about wiping/formatting userdata.
Click to expand...
Click to collapse
I flashed the stock images mtc19x and its bootlooping to hell. Is it time for me to call Google? To see if I can get a new one I bought it in November when it came out
dontbeweakvato said:
I flashed the stock images mtc19x and its bootlooping to hell. Is it time for me to call Google? To see if I can get a new one I bought it in November when it came out
Click to expand...
Click to collapse
It's worth trying the latest (MTC20F) images first. And if that doesn't work I'd try formatting userdata too.
Heisenberg said:
It's worth trying the latest (MTC20F) images first. And if that doesn't work I'd try formatting userdata too.
Click to expand...
Click to collapse
Hey man, you think i can relock the bootloader with only access to the bootloader screen. I can't access anything accept for bootloader.... It won't boot up or go into recovery.
I'm returning it for rma
dontbeweakvato said:
Hey man, you think i can relock the bootloader with only access to the bootloader screen. I can't access anything accept for bootloader.... It won't boot up or go into recovery.
I'm returning it for rma
Click to expand...
Click to collapse
Yeah, relocking the bootloader is easy, just put it in bootloader mode and issue this command:
Code:
fastboot flashing lock
Heisenberg said:
Yeah, relocking the bootloader is easy, just put it in bootloader mode and issue this command:
Code:
fastboot flashing lock
Click to expand...
Click to collapse
I did that exactly. It returned with the list of commands
Fastboot flashing lock
I think it can't. When I type devices it comes back with a serial number and I could even flash boot system and all that from the system image. But when I type fastboot flashing lock it acts like it can't complete that request. Hopefully Huawei or Google won't care if my bootloader is unlocked although i did Flash the factory images and unrooted it
dontbeweakvato said:
I did that exactly. It returned with the list of commands
Fastboot flashing lock
I think it can't. When I type devices it comes back with a serial number and I could even flash boot system and all that from the system image. But when I type fastboot flashing lock it acts like it can't complete that request. Hopefully Huawei or Google won't care if my bootloader is unlocked although i did Flash the factory images and unrooted it
Click to expand...
Click to collapse
That usually means your fastboot isn't up to date.
Heisenberg said:
That usually means your fastboot isn't up to date.
Click to expand...
Click to collapse
Yea that dawned on me and yea it worked. I was thinking there was an error because the board is fried.
Thanks
I followed the guide here: https://forum.xda-developers.com/mo.../rom-lineageos-14-1-moto-e4-qualcomm-t3690156
But now the sim card reader is not working.
I then installed the stock ROM using this guide: http://techposts.org/unbrick-moto-g4-plus-flash-stock-romfirmware/
But it is still not working.
I really don't think it's a hardware issue because the contacts are all there and clean. The sim card works in other phones so it's not that either.
I'm actually not sure if it worked before this, but I'm pretty sure it did. Because I flashed the moment I got the phone.
Thanks for your help!
kidbao said:
I followed the guide here: https://forum.xda-developers.com/mo.../rom-lineageos-14-1-moto-e4-qualcomm-t3690156
But now the sim card reader is not working.
I then installed the stock ROM using this guide: http://techposts.org/unbrick-moto-g4-plus-flash-stock-romfirmware/
But it is still not working.
I really don't think it's a hardware issue because the contacts are all there and clean. The sim card works in other phones so it's not that either.
I'm actually not sure if it worked before this, but I'm pretty sure it did. Because I flashed the moment I got the phone.
Thanks for your help!
Click to expand...
Click to collapse
Do you have the plus model? This is for the regular e4. Probably should have activated it first too.
Which model do you have? Qualcomm? Mediatek? What carrier? You have to flash the proper firmware.
madbat99 said:
Do you have the plus model? This is for the regular e4. Probably should have activated it first too.
Which model do you have? Qualcomm? Mediatek? What carrier? You have to flash the proper firmware.
Click to expand...
Click to collapse
Hi thanks for responding! I have the E4 XT1765. It's Qualcomm. MetroPCS. I tried the PERRY_METROPCS_C and PERRY_METROPCS_C_7.1.1 from from here: firmware. center/firmware/Motorola/Moto%20E4/Stock/
Same issue on one of my XT1765 MetroPCS E4's... it didn't happen after installing LineageOS, tho (maybe wrong thread to post this?). It happened after fiddling with several things - editing build.prop, installing unofficial apps, and disabling/re-enabling bloatware/system apps. I also lost the camera completely and lost all lockscreen notifications. I tried researching the problem, undoing all the changes, and even installing LineageOS. I've since re-installed stock several times on it and all the issues are corrected, except the SIM one - it just stays on Emergency Calls Only or sometimes No Sim, even with a known working, activated SIM card at the MetroPCS store. They suspected hardware (I don't, too coincidental on timing), but wouldn't submit it for repair as the screen is cracked a bit, so no warranty. For $50, it's a great phone, tho, so I bought another one.
It'd be nice to know if there is a fix for this. I tried all the suggestions I could find online.
Flash aokp latest build
beachfl said:
Same issue on one of my XT1765 MetroPCS E4's... it didn't happen after installing LineageOS, tho (maybe wrong thread to post this?). It happened after fiddling with several things - editing build.prop, installing unofficial apps, and disabling/re-enabling bloatware/system apps. I also lost the camera completely and lost all lockscreen notifications. I tried researching the problem, undoing all the changes, and even installing LineageOS. I've since re-installed stock several times on it and all the issues are corrected, except the SIM one - it just stays on Emergency Calls Only or sometimes No Sim, even with a known working, activated SIM card at the MetroPCS store. They suspected hardware (I don't, too coincidental on timing), but wouldn't submit it for repair as the screen is cracked a bit, so no warranty. For $50, it's a great phone, tho, so I bought another one.
It'd be nice to know if there is a fix for this. I tried all the suggestions I could find online.
Click to expand...
Click to collapse
Yeah same. I tried everything :\
nayan deka said:
Flash aokp latest build
Click to expand...
Click to collapse
aokp doesn't have a build for my device. The closest they have is the Moto E line, not E4
kidbao said:
aokp doesn't have a build for my device. The closest they have is the Moto E line, not E4
Click to expand...
Click to collapse
There's an unofficial one here in the forum
https://forum.xda-developers.com/mo...aokp-rom-oms-substratum-t3748033/post75529247
ok. Now I'm thinking why would aokp help me? I tried installing dotOS and resurrection. So I don't think another custom ROM will help.
kidbao said:
ok. Now I'm thinking why would aokp help me? I tried installing dotOS and resurrection. So I don't think another custom ROM will help.
Click to expand...
Click to collapse
I don't know. I was just pointing out that we had one, lol. Not sure it will help you.
I see you "solved" it, lol
Hey guys! So I solved it. I reinstalled the stock rom using this instead: https://forum.xda-developers.com/moto-e4/how-to/guide-flash-stock-firmware-recovery-t3738165. Make sure you change the two lines with oem_sparsechunk with just one like of oem.
kidbao said:
Hey guys! So I solved it. I reinstalled the stock rom using this instead: https://forum.xda-developers.com/moto-e4/how-to/guide-flash-stock-firmware-recovery-t3738165. Make sure you change the two lines with oem_sparsechunk with just one like of oem.
Click to expand...
Click to collapse
Not for me. As we've said, re-installing stock ROM doesn't seem to solve the problem for some people, but it's cool it did for you. Other forums are peppered with people experiencing the same SIM issue, some even apparently happening at random.
beachfl said:
Same issue on one of my XT1765 MetroPCS E4's... it didn't happen after installing LineageOS, tho (maybe wrong thread to post this?). It happened after fiddling with several things - editing build.prop, installing unofficial apps, and disabling/re-enabling bloatware/system apps. I also lost the camera completely and lost all lockscreen notifications. I tried researching the problem, undoing all the changes, and even installing LineageOS. I've since re-installed stock several times on it and all the issues are corrected, except the SIM one - it just stays on Emergency Calls Only or sometimes No Sim, even with a known working, activated SIM card at the MetroPCS store. They suspected hardware (I don't, too coincidental on timing), but wouldn't submit it for repair as the screen is cracked a bit, so no warranty. For $50, it's a great phone, tho, so I bought another one.
It'd be nice to know if there is a fix for this. I tried all the suggestions I could find online.
Click to expand...
Click to collapse
By installing unofficial apps, what do you mean?
And what system apps, specifically, did you re-enable or disable?
---------- Post added at 09:33 PM ---------- Previous post was at 09:25 PM ----------
kidbao said:
Hey guys! So I solved it. I reinstalled the stock rom using this instead: https://forum.xda-developers.com/moto-e4/how-to/guide-flash-stock-firmware-recovery-t3738165. Make sure you change the two lines with oem_sparsechunk with just one like of oem.
Click to expand...
Click to collapse
But which one do we delete? sparsechunk.0 or sparsechunk.1? And beachfl says to leave out gpt.bin...
Scholeggo said:
By installing unofficial apps, what do you mean?
And what system apps, specifically, did you re-enable or disable?
Click to expand...
Click to collapse
Unofficial apps... I just mean any apps that I didn't get from the Google Play Store. Nothing too dodgy, but I just can never rule out that those might be a factor in issues.
Specifically, I played around with disabling/uninstalling the MetroPCS apps (MyMetro, NameID, MetroZone) and a few things that had "Moto" in the name, not sure which... that's all.
Scholeggo said:
But which one do we delete? sparsechunk.0 or sparsechunk.1? And beachfl says to leave out gpt.bin..
Click to expand...
Click to collapse
You delete both those lines and replace them. Unlike the system.img file, which you do have to flash in 'sparsechunks', the oem.img file in this phone's stock ROM isn't in chunks, so flashing it is as a whole, with only one line, as follows:
> fastboot flash oem oem.img
And yah, I don't understand why, but I found flashing the partition table (gpt.bin) made my phone bootloop. Omitting it worked.
HTH.
beachfl said:
Unofficial apps... I just mean any apps that I didn't get from the Google Play Store. Nothing too dodgy, but I just can never rule out that those might be a factor in issues.
Specifically, I played around with disabling/uninstalling the MetroPCS apps (MyMetro, NameID, MetroZone) and a few things that had "Moto" in the name, not sure which... that's all.
You delete both those lines and replace them. Unlike the system.img file, which you do have to flash in 'sparsechunks', the oem.img file in this phone's stock ROM isn't in chunks, so flashing it is as a whole, with only one line, as follows:
> fastboot flash oem oem.img
And yah, I don't understand why, but I found flashing the partition table (gpt.bin) made my phone bootloop. Omitting it worked.
HTH.
Click to expand...
Click to collapse
So, basically, to get back to original ROM, flash the following:
fastboot oem fb_mode_set
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Compared to the original:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash oem oem.img_sparsechunk.0
fastboot flash oem oem.img_sparsechunk.1
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
?
Note that the e4 I'll get is from MetroPCS, and I own a Windows 10 PC, so do I have to add sudo -s before each line?
Scholeggo said:
So, basically, to get back to original ROM, flash the following:
Compared to the original:
?
Note that the e4 I'll get is from MetroPCS, and I own a Windows 10 PC, so do I have to add sudo -s before each line?
Click to expand...
Click to collapse
Yup, that list all looks exactly like what I did.
'sudo -s' .... no, you don't include that when running fastboot from Windows, it's a Linux thing. I'm not sure you have to, but I do always run adb/fastboot from a command prompt with admin priveleges when I'm using WIndows. which is kinda the same thing as 'sudo' on Linux.
Scholeggo said:
So, basically, to get back to original ROM, flash the following:
Compared to the original:
?
Note that the e4 I'll get is from MetroPCS, and I own a Windows 10 PC, so do I have to add sudo -s before each line?
Click to expand...
Click to collapse
I use the rsdlite from rootjunky and it works fine on Windows 10. Well it does on mine. I couldn't say for sure every PC. But I've flashed 2 e4's on mine with rsdlite. So much easier.
http://rootjunkysdl.com/files/Android Programs/RSDLite6.2.4.zip
Go to Android programs and scroll down to rsdlite 6.2.4
Edit: link corrected
madbat99 said:
I use the rsdlite from rootjunky and it works fine on Windows 10. Well it does on mine. I couldn't say for sure every PC. But I've flashed 2 e4's on mine with rsdlite. So much easier.
http://rootjunkysdl.com/files/Android Programs/RSDLite6.2.4.zip
Click to expand...
Click to collapse
Yep, similar experience. I hate doinking around in fastboot if another option exists. That said, one needs to be comfortable at the command line in case something goes amiss.
Davey126 said:
Yep, similar experience. I hate doinking around in fastboot if another option exists. That said, one needs to be comfortable at the command line in case something goes amiss.
Click to expand...
Click to collapse
For sure. Comfort in fastboot is a must
madbat99 said:
I use the rsdlite from rootjunky and it works fine on Windows 10. Well it does on mine. I couldn't say for sure every PC. But I've flashed 2 e4's on mine with rsdlite. So much easier.
http://rootjunkysdl.com/files/Android Programs/RSDLite6.2.4.zip
Click to expand...
Click to collapse
Like some others, RSDLite couldn't see my E4 from Windows 10