Related
I installed virtousity, it hangs 2 times, the 2nd time it wont boot anymore, stuck on white htc screen.
so i tried to reboot on recovery clockworkmod recovery v5.0.2.0 but it only shows the hat and arrow and "clockworkmod recovery v5.0.2.0" and nothing after that.
so i tried to install clockworkmod recovery via fastboot and it just hangs on "writing recovery..."
i dont know what else to try, anybody can help me?
i tried this method of installing via PG88IMG on bootloader, and its stuck in "updating..."
does it look like eMMC problem?
ruu says it cant detect my phone? and i notice that when i connect my phone it cant find/install "android phone" usb driver.
so i run adb command and this what came out, is this good news or bad news?
cat /proc/kmsg | grep mmc0
<3>[ 7.698364] mmc0: No card detect facilities available
<6>[ 7.698913] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 7.699127] mmc0: Platform slot type: MMC
<6>[ 7.699279] mmc0: 4 bit data mode disabled
<6>[ 7.699401] mmc0: 8 bit data mode enabled
<6>[ 7.699615] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 7.699737] mmc0: Slot eject status = 0
<6>[ 7.699890] mmc0: Power save feature enable = 1
<6>[ 7.700012] mmc0: DM non-cached buffer at ffa0f000, dma_addr 0x0baf0000
<6>[ 7.700134] mmc0: DM cmd busaddr 0x0baf0000, cmdptr busaddr 0x0baf0300
<6>[ 7.853759] mmc0: new high speed MMC card at address 0001
<6>[ 7.854980] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
Click to expand...
Click to collapse
Did you wipe data and cache before you flashed virtuous unity?
Sent from my HTC Desire S using XDA App
matthewsucks said:
Did you wipe data and cache before you flashed virtuous unity?
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
no, so thats the problem? what should i do know? the adb command seems saying that its not an eMMC problem.
Now, go into recovery and factory reset. Then, redownload rom manager and flash your rom from your sd card. To go into recovery mode, remove your battery and put it in, then hold the lock button and volume down button.
Sent from my HTC Desire S using XDA App
i cant factory reset, it just hangs when factory reset is selected.
Did you backup your stock rom? If you didn't, your phone's bricked. You gotta send it for repair.
Sent from my HTC Desire S using XDA App
matthewsucks said:
Did you backup your stock rom? If you didn't, your phone's bricked. You gotta send it for repair.
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
i backed up it, via clockwork mod recovery. but i cant install it cause clockwork mod recovery hangs and cant start.
Hang? How does. It hang?
Sent from my HTC Desire S using XDA App
matthewsucks said:
Hang? How does. It hang?
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
the factory reset hangs when i select it.
the clockworkmod recovery hangs when i go to recovery mode, its just says "clockworkmod recovery v5.0.2.0 recovery" with a hat and an orange circle arrow then nothing, i left it for a long time, still nothing
now all i can do is adb shell commands.
Now, don't enter recovery. Go to your bootloader and hit factory reset.
Sent from my HTC Desire S using XDA App
Not actually sure if this works on the Desire S (never had to use it) but have you tried:
adb reboot fastboot
fastboot erase cache
fastboot reboot
Whilst the HTC logo is displaying:
adb reboot recovery
Presuming it now enters recovery properly, you might want to do a full factory reset and another cache wipe from the main recovery menu.
I wish you luck!
LaKraven said:
Not actually sure if this works on the Desire S (never had to use it) but have you tried:
adb reboot fastboot
fastboot erase cache
fastboot reboot
Whilst the HTC logo is displaying:
adb reboot recovery
Presuming it now enters recovery properly, you might want to do a full factory reset and another cache wipe from the main recovery menu.
I wish you luck!
Click to expand...
Click to collapse
adb reboot fastboot - reboots the phone to htc logo and hangs, so what i did was go into hboot, select fastboot and connect usb, then fastboot turns to fastboot usb. after that i run fastboot erase cache which hangs the phone.
it seems this is not a burned eMMC problem, its just that the files are messed up/ maybe if theres a "scandisk" or repair partition i can use. but i dont know linux commands that well.
also tried this command inside adb shell:
mount data
mount: can't read '/etc/fstab': No such file or directory
so it seems im missing some files
matthewsucks said:
Now, don't enter recovery. Go to your bootloader and hit factory reset.
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
factory reset hangs
cd /dev/block
/dev/block # ll
ll
/sbin/sh: ll: not found
/dev/block # ls -l
ls -l
brw------- 1 root root 7, 0 Sep 11 05:40 loop0
brw------- 1 root root 7, 1 Sep 11 05:40 loop1
brw------- 1 root root 7, 2 Sep 11 05:40 loop2
brw------- 1 root root 7, 3 Sep 11 05:40 loop3
brw------- 1 root root 7, 4 Sep 11 05:40 loop4
brw------- 1 root root 7, 5 Sep 11 05:40 loop5
brw------- 1 root root 7, 6 Sep 11 05:40 loop6
brw------- 1 root root 7, 7 Sep 11 05:40 loop7
brw------- 1 root root 179, 0 Sep 11 05:40 mmcblk0
brw------- 1 root root 179, 1 Sep 11 05:40 mmcblk0p1
brw------- 1 root root 179, 10 Sep 11 05:40 mmcblk0p10
brw------- 1 root root 179, 11 Sep 11 05:40 mmcblk0p11
brw------- 1 root root 179, 12 Sep 11 05:40 mmcblk0p12
brw------- 1 root root 179, 13 Sep 11 05:40 mmcblk0p13
brw------- 1 root root 179, 14 Sep 11 05:40 mmcblk0p14
brw------- 1 root root 179, 15 Sep 11 05:40 mmcblk0p15
brw------- 1 root root 179, 16 Sep 11 05:40 mmcblk0p16
brw------- 1 root root 179, 17 Sep 11 05:40 mmcblk0p17
brw------- 1 root root 179, 18 Sep 11 05:40 mmcblk0p18
brw------- 1 root root 179, 19 Sep 11 05:40 mmcblk0p19
brw------- 1 root root 179, 2 Sep 11 05:40 mmcblk0p2
brw------- 1 root root 179, 20 Sep 11 05:40 mmcblk0p20
brw------- 1 root root 179, 21 Sep 11 05:40 mmcblk0p21
brw------- 1 root root 179, 22 Sep 11 05:40 mmcblk0p22
brw------- 1 root root 179, 23 Sep 11 05:40 mmcblk0p23
brw------- 1 root root 179, 24 Sep 11 05:40 mmcblk0p24
brw------- 1 root root 179, 25 Sep 11 05:40 mmcblk0p25
brw------- 1 root root 179, 26 Sep 11 05:40 mmcblk0p26
brw------- 1 root root 179, 27 Sep 11 05:40 mmcblk0p27
brw------- 1 root root 179, 28 Sep 11 05:40 mmcblk0p28
brw------- 1 root root 179, 3 Sep 11 05:40 mmcblk0p3
brw------- 1 root root 179, 4 Sep 11 05:40 mmcblk0p4
brw------- 1 root root 179, 5 Sep 11 05:40 mmcblk0p5
brw------- 1 root root 179, 6 Sep 11 05:40 mmcblk0p6
brw------- 1 root root 179, 7 Sep 11 05:40 mmcblk0p7
brw------- 1 root root 179, 8 Sep 11 05:40 mmcblk0p8
brw------- 1 root root 179, 9 Sep 11 05:40 mmcblk0p9
brw------- 1 root root 179, 64 Sep 11 05:40 mmcblk1
brw------- 1 root root 179, 65 Sep 11 05:40 mmcblk1p1
drwxr-xr-x 4 root root 80 Sep 11 05:40 platform
/dev/block # fsck/?
fsck/?
/sbin/sh: fsck/?: not found
/dev/block # mount -a
mount -a
mount: mounting /recovery on emmc failed: No such file or directory
mount: mounting /boot on emmc failed: No such file or directory
mount: mounting /cache on ext4 failed: No such file or directory
mount: mounting /data on ext4 failed: No such file or directory
mount: mounting /sdcard on vfat failed: No such file or directory
mount: mounting /system on ext4 failed: No such file or directory
/dev/block #
Click to expand...
Click to collapse
anybody know why cant i mount?
Hopefully this thread might help you out.
http://forum.xda-developers.com/showthread.php?t=1150917
zeekiz said:
Hopefully this thread might help you out.
http://forum.xda-developers.com/showthread.php?t=1150917
Click to expand...
Click to collapse
it seems im getting the same error from this thread when mounting /data and /cache. so its burned emmc?
since its s-off i have no more warranty, how available is this emmc from cellphone repair shops?
btw, i didnt pulled out the battery when the phone started not to boot, i used the vol+ vol- and power button. only used the pull out battery when the vol+ vol- power wont work.
this problem started when i use rom manager to "automatically" install virtuosity, and didnt clean my cache and data. also might be market related cause i was downloading and installing a lot of market apps when the phone hanged.
BratPAQ said:
it seems im getting the same error from this thread when mounting /data and /cache. so its burned emmc?
since its s-off i have no more warranty, how available is this emmc from cellphone repair shops?
btw, i didnt pulled out the battery when the phone started not to boot, i used the vol+ vol- and power button. only used the pull out battery when the vol+ vol- power wont work.
this problem started when i use rom manager to "automatically" install virtuosity, and didnt clean my cache and data. also might be market related cause i was downloading and installing a lot of market apps when the phone hanged.
Click to expand...
Click to collapse
Sorry to hear of this, it does sound very like yet another fired eMMC chip and it sounds like you did two of the possible things that I've read can cause eMMC fried chip. one) Remove battery and two) multiple market download.
Not that it's important anymore, but, wiping CACHE and DALVIK CACHE should always be done on a new ROM install, wiping DATA is just sometimes recommend. But not doing so should not lead to a bricked device. It sounds very like the battery pull has done it again - which to my reckoning is a hardware/software design flaw and SHOULD be covered under warranty!
Surely its worth returning just trying to return the device under warranty just to see if they don't notice that you've S-OFF you may be lucky!
If you cannot get past the HTC logo, and the eMMC's are indeed fried... there's no real way for HTC to know you've S-OFF'd your phone.
As Ben stated above, given that it's the removal of the battery (which is a user-intended activity and is SUPPOSED to be safe), this should certainly be accepted under warranty (or whatever your country's version is of "Statutory Rights") anyway.
Send it in for replacement/repair! The worst that'll happen is HTC refuse to do anything with it, send it back to you (as legally required to do so) and you're out of pocket on some postage!
Since the phone is FUBAR anyway, you've got nothing more than postage cost to lose!
LaKraven said:
If you cannot get past the HTC logo, and the eMMC's are indeed fried... there's no real way for HTC to know you've S-OFF'd your phone.
As Ben stated above, given that it's the removal of the battery (which is a user-intended activity and is SUPPOSED to be safe), this should certainly be accepted under warranty (or whatever your country's version is of "Statutory Rights") anyway.
Send it in for replacement/repair! The worst that'll happen is HTC refuse to do anything with it, send it back to you (as legally required to do so) and you're out of pocket on some postage!
Since the phone is FUBAR anyway, you've got nothing more than postage cost to lose!
Click to expand...
Click to collapse
Mine had the same symptoms, and I sent it to technical service. But, HTC's technicians can enter in recovery mode and realize that the terminal is s-off, has happened with my terminal. If so, warranty is void.
I've installed Fresh ROM on my Evo Shift 4G. It worked for about a week, then the GPS stopped working (a known bug with this device and Gingerbread). I restarted the device as normal, and when it came back up all my downloaded apps and the Market were gone, and the device was in that strange indeterminate state where I'm both synced to a Gmail account and not at the same time (the Setup app appears in the Apps folder). Signing in doesn't help.
I rebooted into Clockwork Recovery (3.2.0.1), wiped data/factory reset, wiped the cache, wiped dalvik, and installed Fresh ROM again.
Once that was complete and booted, I signed in, attempted to install an app and the phone reset. There's no file manager installed nor terminal app so I can't delete things by bash. I connected over USB and tried to adb shell in, but that caused the phone to reset.
I'm stuck. Clearly something has not been properly wiped prior to installing Fresh ROM.
What do I need to do to get out of this loop?
SoopahMan said:
I've installed Fresh ROM on my Evo Shift 4G. It worked for about a week, then the GPS stopped working (a known bug with this device and Gingerbread). I restarted the device as normal, and when it came back up all my downloaded apps and the Market were gone, and the device was in that strange indeterminate state where I'm both synced to a Gmail account and not at the same time (the Setup app appears in the Apps folder). Signing in doesn't help.
I rebooted into Clockwork Recovery (3.2.0.1), wiped data/factory reset, wiped the cache, wiped dalvik, and installed Fresh ROM again.
Once that was complete and booted, I signed in, attempted to install an app and the phone reset. There's no file manager installed nor terminal app so I can't delete things by bash. I connected over USB and tried to adb shell in, but that caused the phone to reset.
I'm stuck. Clearly something has not been properly wiped prior to installing Fresh ROM.
What do I need to do to get out of this loop?
Click to expand...
Click to collapse
Sounds like you either had a bad Flash, a bad Download, or both. So redownload the Rom you choose, then Clear and Flash your device according to THESE INSTRUCTIONS .
Thanks for the response. I downloaded the ROM again and ran a check - identical to the file I downloaded previously. So, if the ROM is the culprit, then the latest version of Fresh ROM for Evo Shift does not work (4.1.1).
I followed the instructions linked, wiping the cache and dalvik-cache twice (why?), and wiping system etc prior to installing the ROM.
I'm running into the exact same issues as before - I can't install anything from the Market, and the phone resets if I connect it to a computer over USB. When it resets, it resets multiple times and when it comes back up the 4G no longer works.
If I rerun the above instructions, the 4G works again, but I'm stuck back in this loop - can't use the Market or connect it over USB or it will reset, so forth.
Could Fresh ROM 4.1.1 for Evo Shift be bad? I still suspect the real problem is something is not sufficiently wiped or setup prior to install.
In case it might help, here's an ls -al after installing Fresh Rom 4.1.1 on my phone (an HTC Evo Shift 4G after following the above install instructions).
/
drwxr-xr-x 2 root root 0 Jan 17 07:39 boot
drwxr-xr-x 4 root root 1024 Jan 17 07:41 cache
drwxrwx--x 2 root root 0 Jan 1 1970 data
drwxr-xr-x 2 root root 0 Jan 17 07:39 datadata
-rw-r--r-- 1 root root 3462 Jan 1 1970 default.prop
drwxr-xr-x 12 root root 3060 Jan 17 07:39 dev
drwxr-xr-x 2 root root 0 Jan 17 07:39 emmc
drwxr-xr-x 2 root root 0 Jan 17 07:39 etc
-rwxr-x--- 1 root root 94372 Jan 1 1970 init
-rwxr-x--- 1 root root 899 Jan 1 1970 init.rc
dr-xr-xr-x 79 root root 0 Jan 1 1970 proc
drwxr-xr-x 4 root root 0 Jan 1 1970 res
drwx------ 2 root root 0 May 15 2011 root
drwxr-x--- 2 root root 0 Jan 1 1970 sbin
drwxr-xr-x 2 root root 0 Jan 17 07:39 sd-ext
drwxrwxrwx 78 root root 32768 Jan 1 1970 sdcard
drwxr-xr-x 18 root root 0 Jan 17 07:39 sys
drwxr-xr-x 3 root root 0 Jan 1 1970 system
drwxr-xr-x 2 root root 0 Jan 17 07:45 tmp
-rw-r--r-- 1 root root 0 Jan 1 1970 ueventd.goldfish.rc
-rw-r--r-- 1 root root 4027 Jan 1 1970 ueventd.rc
-rw-r--r-- 1 root root 987 Jan 1 1970 ueventd.speedy.rc
/data
(empty)
/system
drwxr-xr-x 2 root root 0 Jan 1 1970 bin
/system/bin
(empty)
/sys
drwxr-xr-x 2 root root 0 Jan 17 07:53 android_camera
drwxr-xr-x 2 root root 0 Jan 17 07:53 android_camera_awb_cal
drwxr-xr-x 2 root root 0 Jan 17 07:53 android_touch
drwxr-xr-x 2 root root 0 Jan 17 07:53 block
drwxr-xr-x 2 root root 0 Jan 17 07:39 board_properties
drwxr-xr-x 9 root root 0 Jan 17 07:53 bus
drwxr-xr-x 2 root root 0 Jan 17 07:53 camera_led_status
drwxr-xr-x 47 root root 0 Jan 17 07:53 class
drwxr-xr-x 4 root root 0 Jan 17 07:53 dev
drwxr-xr-x 10 root root 0 Jan 17 07:39 devices
drwxr-xr-x 2 root root 0 Jan 17 07:53 firmware
drwxr-xr-x 3 root root 0 Jan 17 07:53 fs
drwxr-xr-x 6 root root 0 Jan 17 07:53 kernel
drwxr-xr-x 62 root root 0 Jan 17 07:53 module
drwxr-xr-x 2 root root 0 Jan 17 07:53 power
drwxr-xr-x 2 root root 0 Jan 17 07:53 systemlog
I can post more or other diagnostics if others have something to recommend. Really stuck here.
Is it odd that /sd-ext is at root and not located on the SD card, and a directory not a symlink?
Now that you have 10 posts you should try posting your questions in the thread for flipz's rom.So the dev can help and maybe anyone else that is running this rom. Also have you tried the a2sd remove command adb shell or from terminal emulator? See if that helps.
Sent from my PG06100 using Tapatalk
A bit more to isolate the problem:
If the phone resets (due to attempting an install from the Market or plug in from USB), 4G fails - but if I restart the phone at that point, when it reboots 4G works again. So 4G appears to be fine, it's the resets that are at the core of the issue.
I shutdown, removed the SD card, booted, and attempted to install an app and got the same reset, so it's not the SD card - it's definitely a problem somewhere on internal storage.
What else do I need to clear to clear this up?
Fresh ROM's pages say to look in /data/app and /system/app for a place where an app already exists that would cause a conflict.
Here's /data after booting the ROM and setting up a Gmail account:
lrwxrwxrwx 1 root root 14 Jan 17 07:54 app -> /system/sd/app
lrwxrwxrwx 1 root root 22 Jan 17 07:54 app-private -> /system/sd/app-private
drwx------ 5 system system 1024 Jan 6 1980 backup
drwxrwx--x 2 system system 14336 Jan 17 16:25 dalvik-cache
drwxrwx--x 161 system system 9216 Jan 17 07:57 data
drwxr-x--- 2 root log 1024 Jan 17 07:54 dontpanic
lrwxrwxrwx 1 root root 11 Jan 17 07:54 drm -> /data/local
-rw-r--r-- 1 root root 6134 Jan 6 1980 dta2sd.lg1
-rw-r--r-- 1 root root 6266 Jan 6 1980 dta2sd.lg2
-rw-r--r-- 1 root root 6266 Jan 6 1980 dta2sd.log
drwxrwxrwx 2 root root 1024 Jan 17 07:54 htcfs
drwxr-xr-x 4 root root 1024 Jan 17 07:42 jit
drwxrwx--x 4 shell shell 1024 Jan 17 07:54 local
drwxrwx--- 2 root root 12288 Jan 17 07:41 lost+found
drwxrwx--t 10 system misc 1024 Jan 17 07:55 misc
drwx------ 2 root root 1024 Jan 6 1980 property
drwx------ 3 system system 1024 Jan 17 07:55 secure
drwxrwxr-x 9 system system 1024 Jan 17 17:48 system
drwxrwx--- 3 system system 1024 Jan 17 17:14 wimax
I'd like to know if app and app-private are as expected (they appear to be the result of the ROM install, since they were completely wiped prior to installing it). The app symlink is a strange one. It points to /system/sd/app, which I can't cd to. /system/sd I can cd to, and this is all it contains:
-rw-r--r-- 1 root root 17 Aug 1 2008 placeholder
A file named placeholder. What?
I'm starting to suspect apps2sd. None of the relevant partitioning steps are in those install instructions, and they appear to be specific to the apps2sd of CyanogenMod. Google's appears to support a DOS partition, while CyanogenMod's appears to only support an ext3 partition, which I do not have.
At the same time, removing the SD card didn't change things, so color me confused.
As suggested by FdxRider you should definately post up in the Rom thread. That way you can get help resolving the issue from others running the same Rom.
It was apps2sd.
To resolve this problem, I had to:
Reboot into ClockwordModRecovery
Connect the phone to a computer over USB
In Clockwork, choose Mount Storage and choose the last option, Mount USB.
Dump anything I wanted to keep off of the SD card (most importantly, the FreshRom zip file).
Then, back in Clockwork, Advanced>Partition SD
Choose a size (they recommend 1024M)
This wipes out everything on the SD card, creates a Linux partition for apps2sd to use, marks the rest as a Windows partition.
Wait till it's done, then, still from ClockworkModRecovery:
Wipe cache, dalvik cache, system, data
Factory reset
Now Mount USB again so you can copy the FreshRom zip back onto the Windows partition (the only part that will come up on a Windows machine).
Eject on the Windows machine to ensure the copy completes, Unmount in Clockwork.
Install the ROM again
Let it boot, restart
Setup my Google Account/Gmail user
And one final thing:
As it turns out ES File Explorer is pre-installed on this ROM. That means installing it from the Market will make the phone go crazy regardless of proper setup. But I am now able to install other apps just fine from the Market (at last).
reset loop NO clockwork until factory reset
I installed Fresh 4.1.1 on my shift 4g
I went to install ROM Manager got it downloaded and it reset the phone at install.
I even tried going to the website and installing it that way. Same results.
I can't get clockwork to work, when i hold the volume down and then press power nothing happens until i release the power button then it goes directly to the Fresh install.
PLEASE HELP!!!!
---------- Post added at 05:30 AM ---------- Previous post was at 05:09 AM ----------
I got the problem solved. I used the RRU and it walked me through a recovery, part of it was yanking the battery. DUH!
Hello,
I'm trying to port Ubuntu Touch for Photon Q. I'm posting in this section, because the error I get is generic. My phone fails to boot. The display flickers several times and last_kmsg contains the following message multiple times (the number is consistent with the number of flickers):
Code:
[ 13.802716,0] mdp4_calc_req_mdp_clk: src_h is zero!
[ 13.807477,0] mdp4_overlay_borderfill_stage_down: no base layer at mixer=1
Can someone please tell me what might be causing this error?
Thank you!
Some more information from the log:
Code:
E/Adreno200-GSL( 1138): <ioctl_kgsl_driver_entry:402>: open(/dev/kgsl-3d0) failed: errno 2. No such file or directory
But the device is there:
Code:
ls -l /dev/kgsl*
crw-rw-rw- 1 root root 241, 1 Nov 26 01:08 /dev/kgsl-2d0
crw-rw-rw- 1 root root 241, 2 Nov 26 01:08 /dev/kgsl-2d1
crw-rw-rw- 1 root root 241, 0 Nov 26 01:08 /dev/kgsl-3d0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/* Disclaimer
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed. Please do some research
* if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you blame me in any way for what happens to your device, I will laugh at you.
* BOOM! goes the dynamite
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 7 (nougat), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
What's working :
*Boots
*Touch
*RIL [Calls, Mobile Data, Dual SIM]
*Wifi
*Wifi Tethering
*Bluetooth
*Camera
*Camcorder
*Audio
*Sensors
*Flash
*GPS
*Notification LED
*OTG
*VoLTE (comming soon)
*FM Radio
Instructions :
Download the latest build and GApps
* Reboot to recovery
* Wipe data/factory reset
* Flash the latest build and GApps
* Reboot
* If you want to root LineageOS, take a look at this thread:
Requriment TWRP: https://mega.nz/#!qwdXjRYB!0Ka5rwLU8ev-5bRYA9M0sFx_3xnCFIGaZXNt03JjNrA
Download Link:
Mega.nz
XDA:DevDB Information
[F2FS / EXT4] LineageOs 14.1 For General Mobile 5+, ROM for the General Mobile GM 5 Plus
Contributors
kaankulahli, wzedlare
Source Code: https://github.com/OneDeveloperOrganization/
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Stable
Current Stable Version: 1.0
Created 2016-09-25
Last Updated 2017-07-04
@ kaankulahli achievements
oyş As Byraklari As
Has been sources released or will be? Where I could access them?
berkantkz said:
Has been sources released or will be? Where I could access them?
Click to expand...
Click to collapse
not yet, maybe next days.
kaankulahli said:
not yet, maybe next days.
Click to expand...
Click to collapse
Can I see the sources? I might help you
send a private message.
Right now, All of the hardware problems are fixed.
Fixed minor bugs . (Microphone)
Download link is broken.
links renewed.
kaankulahli said:
links renewed.
Click to expand...
Click to collapse
sorry download link still broken
Oops, new links added .
in recovery "twrp-3.0.2-1-shamrock" i did a full wipe/factory reset,
and flashed cm_shamrock-ota-38062b8f0f.zip (14.0-20161004-unofficial-shamrock) + open_gapps-arm-7.0-mini-20161005.zip,
then did a wipe dalvik+cache, and boot system.
now i got these 2 errors:
- android system -there's an internal error with your device, contact your manufacturer for details. then i just entered through
- SIM card missing. a sim card has not been detected in our phone
system is running nicely with Wifi, but "no sim card detected".
in settings i noticed that there's a Unknown Baseband version.
i did a TWRP-restore of my previous twrp-backup: cm-13.0-20160912-UNOFFICIAL-shamrock-by-turkdevs ,
now everything works normal again.
how to solve the above errors?
7dwergen said:
i did a full wipe/factory reset, and flashed cm_shamrock-ota-38062b8f0f.zip + open_gapps-arm-7.0-mini-20161005.zip, wipe dalvik+cache, did boot system.
then i got these 2 errors:
- android system -there's an internal error with your device, contact your manufacturer for details. then i just entered through
- SIM card missing. a sim card has not been detected in our phone
system is running nicely with Wifi, but no sim card detected. in settings i noticed that there's a Unknown Baseband version.
i did a restore of the previous cm-13.0-20160912-UNOFFICIAL-shamrock-by-turkdevs.zip , this rom works normal.
how to solve the above errors?
Click to expand...
Click to collapse
Please install 7.0 stock and transfer to cm from stock rom.
7dwergen said:
in recovery "twrp-3.0.2-1-shamrock" i did a full wipe/factory reset,
and flashed cm_shamrock-ota-38062b8f0f.zip (14.0-20161004-unofficial-shamrock) + open_gapps-arm-7.0-mini-20161005.zip,
then did a wipe dalvik+cache, and boot system.
now i got these 2 errors:
- android system -there's an internal error with your device, contact your manufacturer for details. then i just entered through
- SIM card missing. a sim card has not been detected in our phone
system is running nicely with Wifi, but "no sim card detected".
in settings i noticed that there's a Unknown Baseband version.
i did a TWRP-restore of my previous twrp-backup: cm-13.0-20160912-UNOFFICIAL-shamrock-by-turkdevs ,
now everything works normal again.
how to solve the above errors?
Click to expand...
Click to collapse
Can you paste a screenshot from the partitions that you've backed up?
berkantkz said:
Can you paste a screenshot from the partitions that you've backed up?
Click to expand...
Click to collapse
there it is;
/external_sd/TWRP/BACKUPS/d9e7aab0 # ls -la 2016-10-05--17-10-15_cm_shamrock-use
rdebug_6.0.1_MOB31E_2e9510ad/
drwxrwxrwx 2 media_rw media_rw 4096 Oct 5 2016 .
drwxrwxrwx 5 media_rw media_rw 4096 Oct 5 2016 ..
-rw-rw-r-- 1 media_rw media_rw 67108864 Oct 5 2016 boot.emmc.win
-rw-rw-r-- 1 media_rw media_rw 48 Oct 5 2016 boot.emmc.win.md5
-rw-rw-r-- 1 media_rw media_rw 786587720 Oct 5 2016 data.ext4.win000
-rw-rw-r-- 1 media_rw media_rw 51 Oct 5 2016 data.ext4.win000.md5
-rw-rw-r-- 1 media_rw media_rw 185203104 Oct 5 2016 data.ext4.win001
-rw-rw-r-- 1 media_rw media_rw 51 Oct 5 2016 data.ext4.win001.md5
-rw-rw-r-- 1 media_rw media_rw 65 Oct 5 2016 data.info
-rw-rw-r-- 1 media_rw media_rw 88080384 Oct 5 2016 modem.emmc.win
-rw-rw-r-- 1 media_rw media_rw 49 Oct 5 2016 modem.emmc.win.md5
-rw-rw-r-- 1 media_rw media_rw 3182671 Oct 5 2016 oem.ext4.win
-rw-rw-r-- 1 media_rw media_rw 47 Oct 5 2016 oem.ext4.win.md5
-rw-rw-r-- 1 media_rw media_rw 59 Oct 5 2016 oem.info
-rw-rw-r-- 1 media_rw media_rw 1867443 Oct 5 2016 recovery.log
-rw-rw-r-- 1 media_rw media_rw 11534336 Oct 5 2016 splash.emmc.win
-rw-rw-r-- 1 media_rw media_rw 50 Oct 5 2016 splash.emmc.win.md5
-rw-rw-r-- 1 media_rw media_rw 649600246 Oct 5 2016 system.ext4.win
-rw-rw-r-- 1 media_rw media_rw 50 Oct 5 2016 system.ext4.win.md5
-rw-rw-r-- 1 media_rw media_rw 65 Oct 5 2016 system.info
/external_sd/TWRP/BACKUPS/d9e7aab0 #
kaankulahli said:
Please install 7.0 stock and transfer to cm from stock rom.
Click to expand...
Click to collapse
did you mean this 7.0 stock rom ?
https://www.androidfilehost.com/?w=files&flid=96107
GM_5_PLUS_DUAL_ANDROID_7.0_NOUGAT_OTA_BY_TURKDEVS.zip
7dwergen said:
there it is;
/external_sd/TWRP/BACKUPS/d9e7aab0 # ls -la 2016-10-05--17-10-15_cm_shamrock-use
rdebug_6.0.1_MOB31E_2e9510ad/
drwxrwxrwx 2 media_rw media_rw 4096 Oct 5 2016 .
drwxrwxrwx 5 media_rw media_rw 4096 Oct 5 2016 ..
-rw-rw-r-- 1 media_rw media_rw 67108864 Oct 5 2016 boot.emmc.win
-rw-rw-r-- 1 media_rw media_rw 48 Oct 5 2016 boot.emmc.win.md5
-rw-rw-r-- 1 media_rw media_rw 786587720 Oct 5 2016 data.ext4.win000
-rw-rw-r-- 1 media_rw media_rw 51 Oct 5 2016 data.ext4.win000.md5
-rw-rw-r-- 1 media_rw media_rw 185203104 Oct 5 2016 data.ext4.win001
-rw-rw-r-- 1 media_rw media_rw 51 Oct 5 2016 data.ext4.win001.md5
-rw-rw-r-- 1 media_rw media_rw 65 Oct 5 2016 data.info
-rw-rw-r-- 1 media_rw media_rw 88080384 Oct 5 2016 modem.emmc.win
-rw-rw-r-- 1 media_rw media_rw 49 Oct 5 2016 modem.emmc.win.md5
-rw-rw-r-- 1 media_rw media_rw 3182671 Oct 5 2016 oem.ext4.win
-rw-rw-r-- 1 media_rw media_rw 47 Oct 5 2016 oem.ext4.win.md5
-rw-rw-r-- 1 media_rw media_rw 59 Oct 5 2016 oem.info
-rw-rw-r-- 1 media_rw media_rw 1867443 Oct 5 2016 recovery.log
-rw-rw-r-- 1 media_rw media_rw 11534336 Oct 5 2016 splash.emmc.win
-rw-rw-r-- 1 media_rw media_rw 50 Oct 5 2016 splash.emmc.win.md5
-rw-rw-r-- 1 media_rw media_rw 649600246 Oct 5 2016 system.ext4.win
-rw-rw-r-- 1 media_rw media_rw 50 Oct 5 2016 system.ext4.win.md5
-rw-rw-r-- 1 media_rw media_rw 65 Oct 5 2016 system.info
/external_sd/TWRP/BACKUPS/d9e7aab0 #
Click to expand...
Click to collapse
That's good you've backed up modem. To have sim working CM-14, wipe everything, then install CM-14 (and gapps as optional), restore the modem partition. Reboot your device. Mustafa work. And if it Works, I suggest you to back your modem partition somewhere like ön your local or Google Drive or Mega or Mediafire...
Modem includes your IMEI number. ?f you lost it, that back-up will help you. This saves your life.
Good luck. You can pm me anytime. I'm glad to help.
berkantkz said:
That's good you've backed up modem. To have sim working CM-14, wipe everything, then install CM-14 (and gapps as optional), restore the modem partition. Reboot your device. Mustafa work. And if it Works, I suggest you to back your modem partition somewhere like ön your local or Google Drive or Mega or Mediafire...
Modem includes your IMEI number. ?f you lost it, that back-up will help you. This saves your life.
Good luck. You can pm me anytime. I'm glad to help.
Click to expand...
Click to collapse
thanks a lot for your suggestion so fast, berkantkz !
but unfortunately it did not solve my problem, still the same error situation.
'think i'am doing something stupid (or not?)
so i restored the last twrp-backup with cm13, system is up and running smoothly as before..
strange, it is exactly the same error situation i got some weeks ago, after flashing: cm-13.0-20160802-UNOFFICIAL-shamrock_by-TURKDEVS.zip
afterwards i could flash: cm-13.0-20160912-UNOFFICIAL-shamrock-by-turkdevs.zip , this rom solved that problem....
Hi there,
I am trying to flash the 8.1.0 (OPM1.171019.012, Jan 2018) for pixel but it failed with the following message:
Code:
wiping userdata...
/usr/local/bin/mke2fs failed with status 1
mke2fs failed: 1
I searched Google and found the problem occurred in Pixel 2 and the workaround is to flash dtbo.img but I couldn't find it in the factory images for Pixel ( I have downloaded images for 8.1 and 8.0 ).
Could someone offered me some help? Thanks.
hellobbn said:
Hi there,
I am trying to flash the 8.1.0 (OPM1.171019.012, Jan 2018) for pixel but it failed with the following message:
Code:
wiping userdata...
/usr/local/bin/mke2fs failed with status 1
mke2fs failed: 1
I searched Google and found the problem occurred in Pixel 2 and the workaround is to flash dtbo.img but I couldn't find it in the factory images for Pixel ( I have downloaded images for 8.1 and 8.0 ).
Could someone offered me some help? Thanks.
Click to expand...
Click to collapse
I have met exactly the same problem, are you using a mac or linux ? I am using mac and my solution is as follows:
1) download the latest platform tools, and place all ota/factory files under the same folder
2) edit flash_all.sh, change all fastboot to ./fastboot
The following is the directory structure:
[email protected]:~/Downloads/pixel/sailfish-opm1.171019.012 $-> ls -l
total 3680832
[email protected] 1 tesla staff 6096039 Jan 9 19:51 Magisk-v15.2.zip
[email protected] 1 tesla staff 2470501 Jan 9 20:02 MagiskManager-v5.5.3.apk
[email protected] 1 tesla staff 315051 Dec 14 06:00 NOTICE.txt
[email protected] 1 tesla staff 2581412 Dec 14 05:58 adb
[email protected] 4 tesla staff 128 Dec 14 05:59 api
-rw-r--r-- 1 tesla staff 29607142 Jan 1 2009 boot.img
-rw-r--r-- 1 tesla staff 33021952 Dec 19 08:33 bootloader-sailfish-8996-012001-1711091153.img
[email protected] 1 tesla staff 60512 Dec 14 05:58 dmtracedump
[email protected] 1 tesla staff 810388 Dec 14 05:58 e2fsdroid
[email protected] 1 tesla staff 306332 Dec 14 05:58 etc1tool
[email protected] 1 tesla staff 1380616 Dec 14 05:58 fastboot
-rw-r--r-- 1 tesla staff 997 Dec 19 08:33 flash-all.bat
-rwxr-xr-x 1 tesla staff 977 Jan 10 23:02 flash-all.sh
-rwxr-xr-x 1 tesla staff 898 Dec 19 08:33 flash-base.sh
[email protected] 1 tesla staff 17544 Dec 14 05:58 hprof-conv
-rw-r--r-- 1 tesla staff 1411963519 Dec 19 08:33 image-sailfish-opm1.171019.012.zip
[email protected] 3 tesla staff 96 Dec 14 05:58 lib
[email protected] 1 tesla staff 161884 Dec 14 05:58 make_f2fs
[email protected] 1 tesla staff 771876 Dec 14 05:58 mke2fs
[email protected] 1 tesla staff 1184 Dec 14 05:58 mke2fs.conf
[email protected] 2 tesla staff 64 Jan 10 21:47 platform-tools
-rw-r--r-- 1 tesla staff 58695680 Dec 19 08:33 radio-sailfish-8996-130091-1710201747.img
[email protected] 1 tesla staff 720088 Dec 14 05:58 sload_f2fs
[email protected] 1 tesla staff 38 Dec 14 05:58 source.properties
[email protected] 1 tesla staff 1274436 Dec 14 05:58 sqlite3
[email protected] 6 tesla staff 192 Dec 14 05:58 systrace
[email protected] 1 tesla staff 31690752 Jan 9 20:04 twrp-3.2.1-0-sailfish.img
-rwxrwxrwx 1 tesla staff 9164052 Dec 6 08:15 twrp-pixel-installer-sailfish-3.2.0-0.zip
[email protected] 1 tesla staff 11711021 Jan 9 19:58 twrp-pixel-installer-sailfish-3.2.1-0.zip
-rw-r--r-- 1 tesla staff 263172256 Jan 1 2009 vendor.img
churchmice said:
I have met exactly the same problem, are you using a mac or linux ? I am using mac and my solution is as follows:
1) download the latest platform tools, and place all ota/factory files under the same folder
2) edit flash_all.sh, change all fastboot to ./fastboot
The following is the directory structure:
[email protected]:~/Downloads/pixel/sailfish-opm1.171019.012 $-> ls -l
total 3680832
[email protected] 1 tesla staff 6096039 Jan 9 19:51 Magisk-v15.2.zip
[email protected] 1 tesla staff 2470501 Jan 9 20:02 MagiskManager-v5.5.3.apk
[email protected] 1 tesla staff 315051 Dec 14 06:00 NOTICE.txt
[email protected] 1 tesla staff 2581412 Dec 14 05:58 adb
[email protected] 4 tesla staff 128 Dec 14 05:59 api
-rw-r--r-- 1 tesla staff 29607142 Jan 1 2009 boot.img
-rw-r--r-- 1 tesla staff 33021952 Dec 19 08:33 bootloader-sailfish-8996-012001-1711091153.img
[email protected] 1 tesla staff 60512 Dec 14 05:58 dmtracedump
[email protected] 1 tesla staff 810388 Dec 14 05:58 e2fsdroid
[email protected] 1 tesla staff 306332 Dec 14 05:58 etc1tool
[email protected] 1 tesla staff 1380616 Dec 14 05:58 fastboot
-rw-r--r-- 1 tesla staff 997 Dec 19 08:33 flash-all.bat
-rwxr-xr-x 1 tesla staff 977 Jan 10 23:02 flash-all.sh
-rwxr-xr-x 1 tesla staff 898 Dec 19 08:33 flash-base.sh
[email protected] 1 tesla staff 17544 Dec 14 05:58 hprof-conv
-rw-r--r-- 1 tesla staff 1411963519 Dec 19 08:33 image-sailfish-opm1.171019.012.zip
[email protected] 3 tesla staff 96 Dec 14 05:58 lib
[email protected] 1 tesla staff 161884 Dec 14 05:58 make_f2fs
[email protected] 1 tesla staff 771876 Dec 14 05:58 mke2fs
[email protected] 1 tesla staff 1184 Dec 14 05:58 mke2fs.conf
[email protected] 2 tesla staff 64 Jan 10 21:47 platform-tools
-rw-r--r-- 1 tesla staff 58695680 Dec 19 08:33 radio-sailfish-8996-130091-1710201747.img
[email protected] 1 tesla staff 720088 Dec 14 05:58 sload_f2fs
[email protected] 1 tesla staff 38 Dec 14 05:58 source.properties
[email protected] 1 tesla staff 1274436 Dec 14 05:58 sqlite3
[email protected] 6 tesla staff 192 Dec 14 05:58 systrace
[email protected] 1 tesla staff 31690752 Jan 9 20:04 twrp-3.2.1-0-sailfish.img
-rwxrwxrwx 1 tesla staff 9164052 Dec 6 08:15 twrp-pixel-installer-sailfish-3.2.0-0.zip
[email protected] 1 tesla staff 11711021 Jan 9 19:58 twrp-pixel-installer-sailfish-3.2.1-0.zip
-rw-r--r-- 1 tesla staff 263172256 Jan 1 2009 vendor.img
Click to expand...
Click to collapse
Thank you for your help, it seems the
Code:
brew cask install android-platform-tools
in macOS doesn't link all the necessary files and I finally solved it using the following command:
Code:
ln -s /usr/local/Caskroom/android-platform-tools/27.0.1/platform-tools/mke2fs /usr/local/bin/mke2fs
hellobbn said:
Thank you for your help, it seems the
Code:
brew cask install android-platform-tools
in macOS doesn't link all the necessary files and I finally solved it using the following command:
Code:
ln -s /usr/local/Caskroom/android-platform-tools/27.0.1/platform-tools/mke2fs /usr/local/bin/mke2fs
Click to expand...
Click to collapse
Thanks this was a god sent :good:
Hey guys, I'm running into the same error. Any help would be great.
I tried editing flash_all.sh, and changed all fastboot to ./fastboot and then I got an error trying to perform my flash_all command.
What's this brew cask stuff? lol. If anyone can explain this a little further so I can flash P, that would be great.
Edit* actually, looks like once I removed the -w from the script (and stopped a full wipe) everything flashed just fine. Odd.
hellobbn said:
Thank you for your help, it seems the
Code:
brew cask install android-platform-tools
in macOS doesn't link all the necessary files and I finally solved it using the following command:
Code:
ln -s /usr/local/Caskroom/android-platform-tools/27.0.1/platform-tools/mke2fs /usr/local/bin/mke2fs
Click to expand...
Click to collapse
Hey I just got this error when updating my Pixel 2 to Pie and I wanted to try this solution but I have a question. Was there already a mke2fs entry in /usr/local/bin when you linked them? Or was it only in your platform-tools directory? My platform-tools directory lies at ~/android/platform-tools and contains the mke2fs binaries but there is no entry at /usr/local/bin and I'm not sure if your linking solution would work in that scenario or not (not a UNIX wiz over here). I hope to hear back from you soon, thank you.
Shamestick
Edit: I decided not to wait for a reply and just try the symbolic link and running the commands, it worked haha. Thanks agian
I'm running linux and I have the same issue trying to flash my Nexus 6P. I figured out already about the symlink before reading this thread, however, I now get this:
/tmp/TemporaryFile-g1yMBU: Unimplemented ext2 library function while setting up superblock
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
Click to expand...
Click to collapse
Any suggestions? I will keep tinkering until someone replies with a possible solution.
hexxamillion said:
I'm running linux and I have the same issue trying to flash my Nexus 6P. I figured out already about the symlink before reading this thread, however, I now get this:
Any suggestions? I will keep tinkering until someone replies with a possible solution.
Click to expand...
Click to collapse
Well.. tinkering did me some good. I figured downloading the platform-tools would be the solution. I just had issues trying to find it. If you just go to the android sdk site you really only see the studio download wich does not help for this. I stumbled on another post that had this link which helped. https://developer.android.com/studio/releases/platform-tools
The ubuntu repo that has the android-platform-tools is minimal and missing tons. I just copied everything from the platform-tools I downloaded into the path /usr/lib/android-sdk/platform-tools. It even included mke2fs. I ran the flash-all.sh again and everything was magic.
fastboot erase userdata
fastboot update image-*
ozz1386 said:
fastboot erase userdata
fastboot update image-*
Click to expand...
Click to collapse
Two line of cmd, nothing more nothing less. that fixed my issue.
thanks you are a hero :laugh:
I've got this issue when updating ADT-3 to most recent Android 11 Developer Preview.
This problem comes when system-wide mke2fs is used.
I have most recent SDK Platform Tools installed standalone:
Code:
$ whereis mke2fs
mke2fs: /usr/sbin/mke2fs /etc/mke2fs.conf /home/astar/dev/android/sdk/platform-tools/mke2fs.conf /home/astar/dev/android/sdk/platform-tools/mke2fs /usr/share/man/man8/mke2fs.8.gz
System-wide:
Code:
$ mke2fs -V
mke2fs 1.45.3 (14-Jul-2019)
Using EXT2FS Library version 1.45.3
Standalone:
Code:
$ /home/astar/dev/android/sdk/platform-tools/mke2fs -V
mke2fs 1.45.4 (23-Sep-2019)
Using EXT2FS Library version v1.45.4-867-g4bc58792
So, to solve this issue proper mke2fs should be in the PATH.
It's possible to workaround using symlink as mentioned above, but more elegant solution without messing with system is to temporary update PATH variable (Use proper path to platform tools instead of "/home/astar/dev/android/sdk/platform-tools/"):
Code:
$ export PATH=/home/astar/dev/android/sdk/platform-tools/:$PATH
$ /home/astar/dev/android/sdk/platform-tools/mke2fs -V
mke2fs 1.45.4 (23-Sep-2019)
Using EXT2FS Library version v1.45.4-867-g4bc58792
$ ./flash-all.sh
hexxamillion said:
Well.. tinkering did me some good. I figured downloading the platform-tools would be the solution. I just had issues trying to find it. If you just go to the android sdk site you really only see the studio download wich does not help for this. I stumbled on another post that had this link which helped. https://developer.android.com/studio/releases/platform-tools
The ubuntu repo that has the android-platform-tools is minimal and missing tons. I just copied everything from the platform-tools I downloaded into the path /usr/lib/android-sdk/platform-tools. It even included mke2fs. I ran the flash-all.sh again and everything was magic.
Click to expand...
Click to collapse
Just in case someone has this problem I was getting this error when trying to fastboot format userdata in a Xiaomi A2 and this did it !