{
"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"
}
how to install
download to http://www.4shared.com/file/XIqMjv5jba/v700_rootfsimg.html?
execute Odin
ap click
choice to v700_rootfs.img.tar
start
What does this do? Not really sure based on the information in the post.
Jijonhyuni said:
how to install
download to http://www.4shared.com/file/XIqMjv5jba/v700_rootfsimg.html?
execute Odin
ap click
choice to v700_rootfs.img.tar
start
Click to expand...
Click to collapse
I think it is a root method for Tizen, yet I myself am not quite sure what this actually benefits or achieves at this point.
Are there Tizen apps requiring root or a Tizen ROM I'm not aware of?
Thanks
root would be useful to remove the shutter sound for example...
Sent from my Nexus 7 using XDA Premium 4 mobile app
Jijonhyuni said:
how to install
download to http://www.4shared.com/file/XIqMjv5jba/v700_rootfsimg.html?
execute Odin
ap click
choice to v700_rootfs.img.tar
start
Click to expand...
Click to collapse
Think he lives in Korea. I will ask.
루팅을 하면 혜택은 있나요? Custom rom이나 다른 기능이 추가가능한지?
전 아직까지 앤드로이드사용중인데 Tizen으로 프래쉬를해야하는지 고민중입니다.
혹시 시간 나실때 알려주시겠어요?
감사합니다
Flashing now. I'll report back in a minute or two when I'm done playing around with it, maybe even get a system dump.
---------- Post added at 10:56 PM ---------- Previous post was at 10:33 PM ----------
Okay...I got it working but I can't really do much with it. It's not even letting me change directories through SDB.
Here's a list of partitions for Tizen. Anyone want to be bold and try to make a system dump out of one of these?
Will TWRP work with Tizen? Or should we wait for it to be updated?
Thats the best way to get a backup isnt it?
And will that restore partitions from a backup? I have a backup of my Android setup, wondering if I install TWRP on Tizen will I be able to restore Android? Its a thought, probably a bad one but still....
shutter sound off
TML1504 said:
root would be useful to remove the shutter sound for example...
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
install tizen-sdk
sdb root on
sdb shell mount -o remount,rw /
sdb shell mv /usr/share/sounds/mm-camcorder/ /usr/share/sounds/mm-camcorder_bak/
sdb shell mv /usr/apps/com.samsung.w-camera-app/res/sounds /usr/apps/com.samsung.w-camera-app/res/sounds_bak
헤택이라....
escenkay012 said:
think he lives in korea. I will ask.
루팅을 하면 혜택은 있나요? Custom rom이나 다른 기능이 추가가능한지?
전 아직까지 앤드로이드사용중인데 tizen으로 프래쉬를해야하는지 고민중입니다.
혹시 시간 나실때 알려주시겠어요?
감사합니다
Click to expand...
Click to collapse
저도 지금 이것저것 시도를 해보고있습니다.
일단 카메라 사운드부터요
아직 타이젠이라는 운영체제를 모르다보니 어찌할지 모르겠어요
tizen partition info
blackknightavalon said:
Here's a list of partitions for Tizen. Anyone want to be bold and try to make a system dump out of one of these?
Click to expand...
Click to collapse
tizen partition info
sh-3.2# ls -al /dev/disk/by-partlabel
drwxr-xr-x 2 root root 360 Jun 3 07:32 .
drwxr-xr-x 8 root root 160 Jun 3 07:32 ..
lrwxrwxrwx 1 root root 15 Jun 3 07:32 boot -> ../../mmcblk0p6
lrwxrwxrwx 1 root root 15 Jun 3 07:32 bota0 -> ../../mmcblk0p1
lrwxrwxrwx 1 root root 15 Jun 3 07:32 bota1 -> ../../mmcblk0p2
lrwxrwxrwx 1 root root 15 Jun 3 07:32 csa -> ../../mmcblk0p4
lrwxrwxrwx 1 root root 16 Jun 3 07:32 csc -> ../../mmcblk0p13
lrwxrwxrwx 1 root root 16 Jun 3 07:32 fota -> ../../mmcblk0p11
lrwxrwxrwx 1 root root 16 Jun 3 07:32 module -> ../../mmcblk0p10
lrwxrwxrwx 1 root root 15 Jun 3 07:32 param -> ../../mmcblk0p5
lrwxrwxrwx 1 root root 15 Jun 3 07:32 ramdisk1 -> ../../mmcblk0p8
lrwxrwxrwx 1 root root 15 Jun 3 07:32 ramdisk2 -> ../../mmcblk0p9
lrwxrwxrwx 1 root root 15 Jun 3 07:32 recovery -> ../../mmcblk0p7
lrwxrwxrwx 1 root root 15 Jun 3 07:32 reserved -> ../../mmcblk0p3
lrwxrwxrwx 1 root root 16 Jun 3 07:32 rootfs -> ../../mmcblk0p16
lrwxrwxrwx 1 root root 16 Jun 3 07:32 system -> ../../mmcblk0p12
lrwxrwxrwx 1 root root 16 Jun 3 07:32 system-data -> ../../mmcblk0p14
lrwxrwxrwx 1 root root 16 Jun 3 07:32 user -> ../../mmcblk0p15
Jijonhyuni said:
tizen partition info
sh-3.2# ls -al /dev/disk/by-partlabel
drwxr-xr-x 2 root root 360 Jun 3 07:32 .
drwxr-xr-x 8 root root 160 Jun 3 07:32 ..
lrwxrwxrwx 1 root root 15 Jun 3 07:32 boot -> ../../mmcblk0p6
lrwxrwxrwx 1 root root 15 Jun 3 07:32 bota0 -> ../../mmcblk0p1
lrwxrwxrwx 1 root root 15 Jun 3 07:32 bota1 -> ../../mmcblk0p2
lrwxrwxrwx 1 root root 15 Jun 3 07:32 csa -> ../../mmcblk0p4
lrwxrwxrwx 1 root root 16 Jun 3 07:32 csc -> ../../mmcblk0p13
lrwxrwxrwx 1 root root 16 Jun 3 07:32 fota -> ../../mmcblk0p11
lrwxrwxrwx 1 root root 16 Jun 3 07:32 module -> ../../mmcblk0p10
lrwxrwxrwx 1 root root 15 Jun 3 07:32 param -> ../../mmcblk0p5
lrwxrwxrwx 1 root root 15 Jun 3 07:32 ramdisk1 -> ../../mmcblk0p8
lrwxrwxrwx 1 root root 15 Jun 3 07:32 ramdisk2 -> ../../mmcblk0p9
lrwxrwxrwx 1 root root 15 Jun 3 07:32 recovery -> ../../mmcblk0p7
lrwxrwxrwx 1 root root 15 Jun 3 07:32 reserved -> ../../mmcblk0p3
lrwxrwxrwx 1 root root 16 Jun 3 07:32 rootfs -> ../../mmcblk0p16
lrwxrwxrwx 1 root root 16 Jun 3 07:32 system -> ../../mmcblk0p12
lrwxrwxrwx 1 root root 16 Jun 3 07:32 system-data -> ../../mmcblk0p14
lrwxrwxrwx 1 root root 16 Jun 3 07:32 user -> ../../mmcblk0p15
Click to expand...
Click to collapse
Let the custom ROM building begin!
Jijonhyuni said:
install tizen-sdk
sdb root on
sdb shell mount -o remount,rw /
sdb shell mv /usr/share/sounds/mm-camcorder/ /usr/share/sounds/mm-camcorder_bak/
sdb shell mv /usr/apps/com.samsung.w-camera-app/res/sounds /usr/apps/com.samsung.w-camera-app/res/sounds_bak
Click to expand...
Click to collapse
MY BAD.
Thanks for this Got it working and now deleted the shutter sounds.
NakedFaerie said:
MY BAD.
Thanks for this Got it working and now deleted the shutter sounds.
Click to expand...
Click to collapse
When I type sdb root on it get " Permission denied" ??
Gossieur said:
When I type sdb root on it get " Permission denied" ??
Click to expand...
Click to collapse
Have you rooted it yet?
go to the first post and get the file and root it then try again.
NakedFaerie said:
Have you rooted it yet?
go to the first post and get the file and root it then try again.
Click to expand...
Click to collapse
Donwloading now
escenkay012 said:
Think he lives in Korea. I will ask.
루팅을 하면 혜택은 있나요? Custom rom이나 다른 기능이 추가가능한지?
전 아직까지 앤드로이드사용중인데 Tizen으로 프래쉬를해야하는지 고민중입니다.
혹시 시간 나실때 알려주시겠어요?
감사합니다
Click to expand...
Click to collapse
no...right now
Flash. you get "Improved"Battery
Gossieur said:
Donwloading now
Click to expand...
Click to collapse
Strange ... Odin fails to upload the file ... (succeed 0/ failed 1)
---------- Post added at 12:34 PM ---------- Previous post was at 12:22 PM ----------
NakedFaerie said:
Have you rooted it yet?
go to the first post and get the file and root it then try again.
Click to expand...
Click to collapse
Strange ... downloaded the file but Odin fails to upload the file ... (succeed 0/ failed 1)
---------- Post added at 12:40 PM ---------- Previous post was at 12:34 PM ----------
Gossieur said:
Strange ... Odin fails to upload the file ... (succeed 0/ failed 1)
---------- Post added at 12:34 PM ---------- Previous post was at 12:22 PM ----------
Strange ... downloaded the file but Odin fails to upload the file ... (succeed 0/ failed 1)
Click to expand...
Click to collapse
STUPID ME !! Forgot to put the Gear in download mode ... :crying:
hi Jijonhyuni ,
Rooted gear, turn root mode on in Tizen sdk ,no problem .Thank you.!
My " quest/purpose " is to get/ to put custom ringtones/notifications on Gear ,
(as it has only 3 ringtones etc etc .)
Any suggestions ..how ?? or where to push ringtones to..... " Sounds/ringtones " ?
How ...cmd ?
thanks
willcor said:
hi Jijonhyuni ,
Rooted gear, turn root mode on in Tizen sdk ,no problem .Thank you.!
My " quest/purpose " is to get/ to put custom ringtones/notifications on Gear ,
(as it has only 3 ringtones etc etc .)
Any suggestions ..how ?? or where to push ringtones to ? How ?
thanks
Click to expand...
Click to collapse
I posted how on the Gear 1 Tizen thread.
They are located here /opt/share/settings/
To change them the easy way install the Tizen wearable SDK, run the root lines in SDB then goto the SDK and delete files and copy files over. (Make sure you root the device first or none of this will work)
This is my cheat sheet.
sdb root on
sdb shell mount -o remount,rw /
Ringtones located at:
/opt/share/settings/
Camera shutter at:
/usr/share/sounds/mm-camcorder/
Related
In debugging a problem with a cross-compiled binary crashing on someone elses Droid Bionic, I noticed that a bunch of dirs in / are sym-linked into /osh:
Code:
/# [B]ls -l /[/B]
...
lrwxrwxrwx root root 2011-11-06 09:38 etc -> /osh/etc
lrwxrwxrwx root root 2011-11-06 09:38 lib -> /osh/lib
lrwxrwxrwx root root 2011-11-06 09:38 sbin -> /osh/sbin
lrwxrwxrwx root root 2011-11-06 09:38 usr -> /osh/usr
...
Is it 'normal' for stock Droid Bionic Androids to sym-link this stuff in the root dir to /osh, or is it the result of some customisation (Havent seen this on other devices, and dont have hands-on a Bionic to check further ... ) ?
- jc
Hi,
I have upgraded my moboot to 3.0.5 and upgraded the Cyanogenmod to CM9. Also, i have decided to install TouchPadBuntu to test it. Followed the instructions with some modifications, and everything went fine, but when i try to boot on it via moboot, it gives the error:
Loading '/boot/uImage.TouchPadBuntu'... OK
Checking uImage... Invalid Magic
BOOT FAILED!
Also, ClockRecovery doesn't works too, it returns some numbers (hex codes) on the boot screen.
Someone can give some light?
I'm dealing with same problem, but with Arch Linux.
I think the problem is in /boot free space...
Can you list your files in /boot and your free space in there?
ls -l /boot
df -h /boot
Hi, i have attached the errors... one is TouchPadBuntu error, and the other is Cyanogenmod error that is appearing sometimes yes, sometimes no...
http://img19.imageshack.us/img19/5138/imagem0000m.jpg
http://img828.imageshack.us/img828/4153/imagem0001.jpg
Also, here is my /boot
Code:
[email protected]:/# ls -l /boot
-rw-r--r-- 1 root root 1430215 Jul 30 2011 System.map-2.6.35-palm-tenderloin
drwxr-xr-x 2 root root 4096 Oct 14 02:59 bin
-rw-r--r-- 1 root root 490764 Jul 30 2011 boot-genesis.tar.gz
-rw-r--r-- 1 root root 119371 Jul 30 2011 boot-images.tar.gz
-rw-r--r-- 1 root root 115392 Jul 30 2011 boot.bin
-rw-r--r-- 1 root root 75277 Jul 30 2011 config-2.6.35-palm-tenderloin
drwxr-xr-x 2 root root 4096 Oct 14 02:59 dev
drwxr-xr-x 3 root root 4096 Oct 14 02:59 etc
-rwxr-xr-x 1 root root 1131 Jul 30 2011 genesis-update.xml
-rwxr-xr-x 1 root root 2224 Jul 30 2011 image-update.xml
drwxr-xr-x 2 root root 4096 Oct 14 02:59 lib
drwx------ 2 root root 16384 Oct 14 02:56 lost+found
-rw-r--r-- 1 root root 11 Oct 14 03:51 moboot.default
-rw-r--r-- 1 luna luna 0 Feb 9 01:57 moboot.next
-rw-rw-rw- 1 root root 30313 Feb 8 00:58 moboot.splash.CyanogenMod.tga
-rw-r--r-- 1 luna 10000 14046 Sep 8 2001 moboot.splash.webOS.tga
-rw-r--r-- 1 root root 4 Feb 8 01:51 moboot.verbose.TouchPadBuntu
drwxr-xr-x 2 root root 4096 Oct 14 02:59 proc
drwxr-xr-x 2 root root 4096 Oct 14 02:59 realroot
drwxr-xr-x 2 root root 4096 Oct 14 02:59 sbin
drwxr-xr-x 2 root root 4096 Oct 14 02:59 sys
lrwxrwxrwx 1 root root 13 Feb 8 01:51 uImage -> uImage.moboot
-rw-r--r-- 1 root root 3333228 Jul 30 2011 uImage-2.6.35-palm-tenderloin
-rw-r--r-- 1 root root 5006686 Feb 8 00:57 uImage.ClockworkMod
-rw-r--r-- 1 root root 4136681 Feb 8 00:58 uImage.CyanogenMod
-rw-r--r-- 1 root root 1106 Feb 8 02:53 uImage.TouchPadBuntu
-rw-r--r-- 1 root root 64508 Feb 8 01:50 uImage.moboot
lrwxrwxrwx 1 root root 29 Oct 14 02:58 uImage.webOS -> uImage-2.6.35-palm-tenderloin
-rw-r--r-- 1 root root 84 Jul 30 2011 updatefs-info
drwxr-xr-x 5 root root 4096 Oct 14 02:59 usr
[email protected]:/# df -h /boot
Filesystem Size Used Available Use% Mounted on
/dev/root 31.0M 22.1M 8.9M 71% /boot
Hi folks,
I have corrected my problem downloading uImage.TouchPadUbuntu again via CURL direclty to /boot. To do this i have to use mount -O rw,remount /boot and execute the curl command here.
After this, i rebooted the touchpad and now have ubuntu on it. But using touchscreen as mouse is sucking a lot, and response of my touch on virtual keyboard too... but fine to test!
I also solved my problem, I think the problem was pretty like yours!
My solution post.
Many of XT890s with "Service required Code corrupt" are bricked and mine as well.
I've found out that there's a ancestor model - XT788 in China. And now we've all parts to reflash Medfield: ifwi (UEFI BIOS), osdnx (bootloader), osimage (kernel with fastboot). There's the last part to do, the fwdnx should be changed, but it has checksum and it should be recalculated. How to calculate dnx checksum?
Maybe you know somebody who knows!
He knows but I can't reach him.
http://www.linkedin.com/pub/tapan-shah/10/59a/39
View attachment dnx.zip
The algorithm is unknown still.
Could somebody make a dump of the first 500 Mb of the eMMC, please? (XT890)
Code:
su
busybox dd if=/dev/block/mmcblk0 of=/sdcard/dd.bin bs=500M count=1
After some time (10 minutes in the worst case), You'll find dd.bin file in /sdcard folder.
It operation will copy some specific to only your's device data. I'll not use it and will delete it after my analysis.
Sorry, my I is bricked, or I would.
So, by reading the "--help" message, "xfstk" is capable of flashing more then two files. I assume more then two files have to match/are the same/depend on each other to bootstrap Android. Why aren't more files being flashed? In my bricking experience, I tried flashing the ifwi and dnx files from the 4.0.4 that I was leaving, the 4.1.2 zip didn't have them in it so I tried others from a stock 4.1.2 rom and the original versions packaged with the xfstk. So which ones go with Mattlgroff's cwm Jelly Bean zip? What other files need to be flashed to un-corrupt the code? I don't see names that line up here.
The flashing utility works, we just need the right files to be flashed.
Code:
Z:\brick\unbrick>xfstk-dldr-solo.exe --help
XFSTK Downloader Solo 1.1.0a
Copyright (c) 2011 Intel Corporation
Command Line Options:
-h [ --help ] Print usage message
--fwdnx arg (=BLANK.bin) File path for the FW DNX module
--fwimage arg (=BLANK.bin) File path for the FW Image module
--osdnx arg (=BLANK.bin) File path for the OS DNX module
--osimage arg (=BLANK.bin) File path for the OS image
--miscdnx arg File path for miscellaneous DNX module
--gpflags arg (=0x80000000) Optional argument. 32 Bit Hex Value of the
GPFlags.
--transfer arg (=USB) Optional argument. Determines how the image will
be transferred.
--idrq arg (=0) Optional argument. Indicates whether IDRQ is
used. 1 means idrq is used, 0 means idrq is not
used.
-v [ --verbose ] Optional argument. Display debug information. 1
means show debug information, 0 means hide debug
information.
gilbertiddi0, things aren't so simple.
Motorola doesn't provide osdnx. I'm almost sure that it have never been developed for our model (XT890).
I still have no full dump of the first 500M.
Can you do that on an unrooted machine? If you can describe how to do that I will try. I am familiar with "dd" - just assumed you are needing the help of usb-debugging and busybox.
My phone doesn't have /dev/block/mmcblk0
gilbertiddi0 said:
Can you do that on an unrooted machine? If you can describe how to do that I will try. I am familiar with "dd" - just assumed you are needing the help of usb-debugging and busybox.
Click to expand...
Click to collapse
You could check if you have a read permission by:
Code:
cd /dev/block
ls -l | grep mmc
itsmeinarizona, could you execute those commands and reply, please?
Dark2150 said:
You could check if you have a read permission by:
Code:
cd /dev/block
ls -l | grep mmc
itsmeinarizona, could you execute those commands and reply, please?
Click to expand...
Click to collapse
Code:
[email protected]:/dev/block $ ls -l | grep mmc
lrwxrwxrwx root root 2013-10-03 03:51 boot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-10-03 03:51 bos -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-10-03 03:51 bosbackup -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-10-03 03:51 cache -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2013-10-03 03:51 cdrom -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2013-10-03 03:51 cid -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-10-03 03:51 devtree -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-10-03 03:51 devtreeBackup -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-10-03 03:51 logo -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-10-03 03:51 misc -> /dev/block/mmcblk0p13
brw------- root root 179, 0 2013-10-03 03:51 mmcblk0
brw------- root root 179, 1 2013-10-03 03:51 mmcblk0p1
brw------- root root 179, 10 2013-10-03 03:51 mmcblk0p10
brw------- root root 179, 11 2013-10-03 03:51 mmcblk0p11
brw------- root root 259, 0 2013-10-03 03:51 mmcblk0p12
brw------- root root 259, 1 2013-10-03 03:51 mmcblk0p13
brw------- root root 259, 2 2013-10-03 03:51 mmcblk0p14
brw------- root root 259, 3 2013-10-03 03:51 mmcblk0p15
brw------- root root 259, 4 2013-10-03 03:51 mmcblk0p16
brw------- root root 259, 5 2013-10-03 03:51 mmcblk0p17
brw------- root root 179, 2 2013-10-03 03:51 mmcblk0p2
brw------- root root 179, 3 2013-10-03 03:51 mmcblk0p3
brw------- root root 179, 4 2013-10-03 03:51 mmcblk0p4
brw------- root root 179, 5 2013-10-03 03:51 mmcblk0p5
brw------- root root 179, 6 2013-10-03 03:51 mmcblk0p6
brw-rw---- root mot_tcmd 179, 7 2013-10-03 03:51 mmcblk0p7
brw------- root root 179, 8 2013-10-03 03:51 mmcblk0p8
brw------- root root 179, 9 2013-10-03 03:51 mmcblk0p9
lrwxrwxrwx root root 2013-10-03 03:51 panic -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-10-03 03:51 pds -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2013-10-03 03:51 recovery -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-10-03 03:51 sp -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-10-03 03:51 system -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2013-10-03 03:51 ulogo -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-10-03 03:51 userdata -> /dev/block/mmcblk0p17
[email protected]:/dev/block $
[\code][COLOR="Silver"]
[SIZE=1]---------- Post added at 04:19 AM ---------- Previous post was at 04:04 AM ----------[/SIZE]
[/COLOR][QUOTE="Dark2150, post: 46131662, member: 421987"]You could check if you have a read permission by:
[CODE]
cd /dev/block
ls -l | grep mmc
itsmeinarizona, could you execute those commands and reply, please?[/QUOTE]
Code:
|[email protected]:/dev/block $ dd if=/dev/block/mmcblk0 of=/sdcard/dd.bin bs=500M count=1 <
/dev/block/mmcblk0: cannot open for read: Permission denied
1|[email protected]:/dev/block $
I went ahead and ran that command. This is a friends 890. As I hardbricked mine by opening the bootloader I am unwilling to unlock theirs
gilbertiddi0, Thank you.
As you see there is a mmcblk0. But only root has rights to read it.
Yours headset bricked with "Service required Code corrupt"? All others cases are debrickable.
Dark2150 said:
Yours headset bricked with "Service required Code corrupt"? All others cases are debrickable.
Click to expand...
Click to collapse
Yes. when I first downgraded, it worked for one boot but the second time it did not.
gilbertiddi0 said:
Yes. when I first downgraded, it worked for one boot but the second time it did not.
Click to expand...
Click to collapse
By the time of the first boot the headset was connected to PC, and by the second reboot it wasn't, right?
Dark2150 said:
By the time of the first boot the headset was connected to PC, and by the second reboot it wasn't, right?
Click to expand...
Click to collapse
Now that you mention it, yes in fact that is what happened. I never thought of it in quite those terms. The second time it got locked on the "bootloader unlocked" warning so I forced it off and turned it back on, I had always equated THAT as the important event: somehow it got stuck, in my haste I corrupted something by making it reload. Since it obviously couldn't get back to the "bootloader unlocked" screen even. I searched for quite awhile for that logo screen thinking that replacing that would allow it to cycle normally. Of course that isn't something you get with a new firmware like you're saying ...
gilbertiddi0 said:
Of course that isn't something you get with a new firmware like you're saying ...
Click to expand...
Click to collapse
The picture of unlocked bootloader it's a part of the firmware, but your phone doesn't boot a firmware.
The dump of mmcblk0 is still needed! Someone?
Dark2150 said:
The dump of mmcblk0 is still needed! Someone?
Click to expand...
Click to collapse
I have the dump. The "pm" link doesn't include a file transfer, how do I get it to you?
I got another 890. It had Jelly Bean on it - it was a pain rooting (I used Matt's method of rooting - unlocked bootloader, flashed insecured boot - reinstalled boot) but I had to do it with "su-bin-3.1-x86" instead of the su file that came with it. Ohh, and replaced the "boot" that came with the unit. I knew you needed this dump and I am still hoping to fix that other unit.
gilbertiddi0 said:
I have the dump. The "pm" link doesn't include a file transfer, how do I get it to you?
I got another 890. It had Jelly Bean on it - it was a pain rooting (I used Matt's method of rooting - unlocked bootloader, flashed insecured boot - reinstalled boot) but I had to do it with "su-bin-3.1-x86" instead of the su file that came with it. Ohh, and replaced the "boot" that came with the unit. I knew you needed this dump and I am still hoping to fix that other unit.
Click to expand...
Click to collapse
And there's a hope to fix it still. Unfortunately Motorola have made it as hard as possible.
The fix process is the same for whole Z2xxx family and it suits to other devices. We're working with XT890 and Lenovo K900 now. But if anybody has a device on Atom SoC platform (Orange SanDiego, Lenovo K800, Lava Xolo X900 e.t.c) and wants to join - welcome.
Dark2150 said:
And there's a hope to fix it still. Unfortunately Motorola have made it as hard as possible.
The fix process is the same for whole Z2xxx family and it suits to other devices. We're working with XT890 and Lenovo K900 now. But if anybody has a device on Atom SoC platform (Orange SanDiego, Lenovo K800, Lava Xolo X900 e.t.c) and wants to join - welcome.
Click to expand...
Click to collapse
HI!
Thanks guys for the help! i have a razr i and it is hard bricked, and there isn't nothing to do (the battery is over and the phone doesn't start) an option is change the motherboard with another and maybe the phone can start ? (sorry for my bad english but i am italian)
peter971215 said:
HI!
Thanks guys for the help! i have a razr i and it is hard bricked, and there isn't nothing to do (the battery is over and the phone doesn't start) an option is change the motherboard with another and maybe the phone can start ? (sorry for my bad english but i am italian)
Click to expand...
Click to collapse
If you have no "Service required code corrupt" message - it have chance to be reflashed with standard tool.
And yes - if you'll change mainboard it will solve the problem, because it's like change the whole phone.
Dark2150 said:
If you have no "Service required code corrupt" message - it have chance to be reflashed with standard tool.
And yes - if you'll change mainboard it will solve the problem, because it's like change the whole phone.
Click to expand...
Click to collapse
i had hard bricked my phone why i downgraded (not from jelly bean to ics , but i had downgraded with a fastboot ics from jelly bean and it was all ok, and when I flash with rsd a firmware ics the phone after 1 reboot gave me the "service required code corrupt" screen with the green led, i tried to revive the phone with the unbrick.zip but nothing outcome from the phone.. sometimes when i change the dnx and ifwi file the phone reboot with a dark screen but nothing..
peter971215 said:
i had hard bricked my phone why i downgraded (not from jelly bean to ics , but i had downgraded with a fastboot ics from jelly bean and it was all ok, and when I flash with rsd a firmware ics the phone after 1 reboot gave me the "service required code corrupt" screen with the green led, i tried to revive the phone with the unbrick.zip but nothing outcome from the phone.. sometimes when i change the dnx and ifwi file the phone reboot with a dark screen but nothing..
Click to expand...
Click to collapse
The same problem there. You definitely could fix it with a new mainboard.
Dark2150 said:
The same problem there. You definitely could fix it with a new mainboard.
Click to expand...
Click to collapse
Yes!! i had just take this option, but i need a razr i used (the mainboard new is 200$)
In other ROMs I've edited an XML file in /system/csc to make some changes to the keyboard -- specifically, to display alternate symbols when you press-hold a key. I flashed stock MM tonight and noticed that this folder no longer exists.
I checked the Maximum OvrDriVE MM ROM and it does have this folder with the appropriate file. So what happened to the CSC stuff in stock?
SteveRiley said:
In other ROMs I've edited an XML file in /system/csc to make some changes to the keyboard -- specifically, to display alternate symbols when you press-hold a key. I flashed stock MM tonight and noticed that this folder no longer exists.
I checked the Maximum OvrDriVE MM ROM and it does have this folder with the appropriate file. So what happened to the CSC stuff in stock?
Click to expand...
Click to collapse
which stock firmware you are using?
pvsgh said:
which stock firmware you are using?
Click to expand...
Click to collapse
The one DeeXii posted a couple weeks ago: N910TUVS2EPG2_N910TTMB2EPG2_TMB
http://forum.xda-developers.com/note-4-tmobile/development/stock-n910t-n910tuvu2epe3-6-0-1-t3407018
SteveRiley said:
The one DeeXii posted a couple weeks ago: N910TUVS2EPG2_N910TTMB2EPG2_TMB
http://forum.xda-developers.com/note-4-tmobile/development/stock-n910t-n910tuvu2epe3-6-0-1-t3407018
Click to expand...
Click to collapse
Those are the stock ODIN flashable files. Once you flash it via ODIN you will see CSC folder on your phone under /system directory.
pvsgh said:
Those are the stock ODIN flashable files. Once you flash it via ODIN you will see CSC folder on your phone under /system directory.
Click to expand...
Click to collapse
No CSC folder here.
Code:
[email protected]:/ # [B]ls -al /system[/B]
drwxr-xr-x root root 2016-08-11 23:53 app
drwxr-xr-x root shell 2008-12-31 07:00 bin
-rw-r--r-- root root 8080 2008-12-31 07:00 build.prop
drwxr-xr-x root root 2008-12-31 07:00 cameradata
drwxr-xr-x root root 2016-07-07 07:17 container
drwxr-xr-x root root 2016-08-12 01:00 etc
drwxr-xr-x root root 2008-12-31 07:00 fonts
drwxr-xr-x root root 2016-07-07 07:17 framework
-rw-r--r-- root root 10800 2008-12-31 07:00 kern_sec_info
drwxr-xr-x root root 2016-08-11 23:36 lib
drwx------ root root 1969-12-31 16:00 lost+found
drwxr-xr-x root root 2008-12-31 07:00 media
drwxr-xr-x root root 2016-07-07 07:16 preloadedmdm
drwxr-xr-x root root 2016-08-11 23:52 priv-app
-rw-r--r-- root root 4876860 2008-12-31 07:00 recovery-from-boot.bak
drwxr-xr-x root root 2008-12-31 07:00 saiv
-rw-r--r-- root root 417 2016-07-07 07:36 tima_measurement_info
drwxr-xr-x root root 2008-12-31 07:00 tts
drwxr-xr-x root root 2008-12-31 07:00 usr
drwxr-xr-x root shell 2008-12-31 07:00 vendor
drwxr-xr-x root root 2008-12-31 07:00 voicebargeindata
drwxr-xr-x root root 2008-12-31 07:00 wakeupdata
drwxr-xr-x root shell 2008-12-31 07:00 xbin
And a little bit of searching on /system and /data doesn't reveal anything much:
Code:
[email protected]:/ # [B]find /system -iname '*csc*'[/B]
/system/fonts/CarroisGothicSC-Regular.ttf
/system/lib/libcontrolcsc.so
/system/lib/libsccore_csc.so
/system/priv-app/CSC
/system/priv-app/CSC/CSC.apk
/system/priv-app/CSC/oat/arm/CSC.odex.xz
[email protected]:/ # f[B]ind /data -iname '*csc*'[/B]
/data/data/com.samsung.sec.android.application.csc
/data/data/com.google.android.gms/files/AppDataSearch/main/cur/ds.cscoring
/data/system/cscversion.txt
/data/dalvik-cache/profiles/com.samsung.sec.android.application.csc
/data/dalvik-cache/arm/[email protected]@[email protected]@classes.dex
And this zero-byte file seems odd:
Code:
[email protected]:/ # [B]ls -al /data/system/cscversion.txt[/B]
-rw------- system system 0 2016-08-12 20:03 cscversion.txt
I've flashed the build a couple times now, same results. My procedure:
1. Ensure SuperSU zip is on external SD card
2. Boot TWRP recovery (currently 3.0.2 installed)
3. Wipe every partition except external SD
4. Boot the phone into download mode
5. Odin (3.0.9) the ROM to the phone
6. Odin TWRP back to the phone
7. Boot TWRP recovery
8. Flash SuperSU zip
9. Reboot and let settle for 15 minutes
SteveRiley said:
No CSC folder here.
Code:
[email protected]:/ # [B]ls -al /system[/B]
drwxr-xr-x root root 2016-08-11 23:53 app
drwxr-xr-x root shell 2008-12-31 07:00 bin
-rw-r--r-- root root 8080 2008-12-31 07:00 build.prop
drwxr-xr-x root root 2008-12-31 07:00 cameradata
drwxr-xr-x root root 2016-07-07 07:17 container
drwxr-xr-x root root 2016-08-12 01:00 etc
drwxr-xr-x root root 2008-12-31 07:00 fonts
drwxr-xr-x root root 2016-07-07 07:17 framework
-rw-r--r-- root root 10800 2008-12-31 07:00 kern_sec_info
drwxr-xr-x root root 2016-08-11 23:36 lib
drwx------ root root 1969-12-31 16:00 lost+found
drwxr-xr-x root root 2008-12-31 07:00 media
drwxr-xr-x root root 2016-07-07 07:16 preloadedmdm
drwxr-xr-x root root 2016-08-11 23:52 priv-app
-rw-r--r-- root root 4876860 2008-12-31 07:00 recovery-from-boot.bak
drwxr-xr-x root root 2008-12-31 07:00 saiv
-rw-r--r-- root root 417 2016-07-07 07:36 tima_measurement_info
drwxr-xr-x root root 2008-12-31 07:00 tts
drwxr-xr-x root root 2008-12-31 07:00 usr
drwxr-xr-x root shell 2008-12-31 07:00 vendor
drwxr-xr-x root root 2008-12-31 07:00 voicebargeindata
drwxr-xr-x root root 2008-12-31 07:00 wakeupdata
drwxr-xr-x root shell 2008-12-31 07:00 xbin
And a little bit of searching on /system and /data doesn't reveal anything much:
Code:
[email protected]:/ # [B]find /system -iname '*csc*'[/B]
/system/fonts/CarroisGothicSC-Regular.ttf
/system/lib/libcontrolcsc.so
/system/lib/libsccore_csc.so
/system/priv-app/CSC
/system/priv-app/CSC/CSC.apk
/system/priv-app/CSC/oat/arm/CSC.odex.xz
[email protected]:/ # f[B]ind /data -iname '*csc*'[/B]
/data/data/com.samsung.sec.android.application.csc
/data/data/com.google.android.gms/files/AppDataSearch/main/cur/ds.cscoring
/data/system/cscversion.txt
/data/dalvik-cache/profiles/com.samsung.sec.android.application.csc
/data/dalvik-cache/arm/[email protected]@[email protected]@classes.dex
And this zero-byte file seems odd:
Code:
[email protected]:/ # [B]ls -al /data/system/cscversion.txt[/B]
-rw------- system system 0 2016-08-12 20:03 cscversion.txt
I've flashed the build a couple times now, same results. My procedure:
1. Ensure SuperSU zip is on external SD card
2. Boot TWRP recovery (currently 3.0.2 installed)
3. Wipe every partition except external SD
4. Boot the phone into download mode
5. Odin (3.0.9) the ROM to the phone
6. Odin TWRP back to the phone
7. Boot TWRP recovery
8. Flash SuperSU zip
9. Reboot and let settle for 15 minutes
Click to expand...
Click to collapse
Don't know if it would make any difference but you should be using Odin 3.11.1 with this latest EPG2 firmware. CSC related files reside in cache.img.ext4 , so it is possible that that particular file is not being flashed in your case.
pvsgh said:
Don't know if it would make any difference but you should be using Odin 3.11.1 with this latest EPG2 firmware. CSC related files reside in cache.img.ext4 , so it is possible that that particular file is not being flashed in your case.
Click to expand...
Click to collapse
Hm, you might very well have discovered the cause.
Examining the cache.img.ext4 file on my PC:
Code:
[email protected] ~/junk $ [B]simg2img cache.img.ext4 cache.raw[/B]
[email protected] ~/junk $ [B]sudo mount -t ext4 -o loop cache.raw /mnt[/B]
[email protected] ~/junk $ [B]ls -al /mnt[/B]
total 28
drwxr-xr-x 4 root root 4096 Dec 31 1969 .
drwxr-xr-x 1 root root 122 Dec 24 2015 ..
drwx------ 2 root root 4096 Dec 31 1969 lost+found
drwxrwx--- 2 steve 2001 4096 Jul 7 07:36 recovery
[email protected] ~/junk $ [B]ls -al /mnt/recovery/[/B]
total 82720
drwxrwx--- 2 steve 2001 4096 Jul 7 07:36 .
drwxr-xr-x 4 root root 4096 Dec 31 1969 ..
-rw-r--r-- 1 root root 78 Jul 7 07:36 command
-rw-r--r-- 1 root root 84691365 Jul 7 07:36 sec_csc.zip
[email protected] ~/junk $ [B]unzip -l /mnt/recovery/sec_csc.zip[/B]
Archive: /mnt/recovery/sec_csc.zip
signed by SignApk
Length Date Time Name
--------- ---------- ----- ----
{... many files, including several for system/csc ...}
--------- -------
104784820 113 files
I'm surprised the phone even works!
Hm, experiencing flash write failures. First time was about 15% finished. Second time seems about 95% finished.
Third flash completed. Before rebooting, I flashed TWRP. Then I booted TWRP and installed SuperSU. Booted normally and received the dreaded ddi: mmc_read failed message. Crap. Tried another flashing round, which also completed, and let it boot immediately. The Samsung recovery started (which I have never actually seen before) and ran through an installation cycle of something. After that, the phone booted and once again shows ddi:mmc_read failed. Is this thing kaput now?
----------
EDIT: I power cycled the phone and now it appears to be doing a normal first boot -- I'm staring at the T-Mobile splash and the status light is flickering blue/cyan. Wow!
SteveRiley said:
Third flash completed. Before rebooting, I flashed TWRP. Then I booted TWRP and installed SuperSU. Booted normally and received the dreaded ddi: mmc_read failed message. Crap. Tried another flashing round, which also completed, and let it boot immediately. The Samsung recovery started (which I have never actually seen before) and ran through an installation cycle of something. After that, the phone booted and once again shows ddi:mmc_read failed. Is this thing kaput now?
----------
EDIT: I power cycled the phone and now it appears to be doing a normal first boot -- I'm staring at the T-Mobile splash and the status light is flickering blue/cyan. Wow!
Click to expand...
Click to collapse
Did you use the latest version of ODIN now? Also if the phone looks stuck on T-Mobile logo for longer than 30 mins, then remove the battery from the phone and try to boot again.
pvsgh said:
Did you use the latest version of ODIN now? Also if the phone looks stuck on T-Mobile logo for longer than 30 mins, then remove the battery from the phone and try to boot again.
Click to expand...
Click to collapse
Yep, Odin 3.11.1 worked, but like I wrote before, it took three attempts. Weird.
BTW, not everyone agrees that the version of Odin was the actual problem:
http://forum.xda-developers.com/not...ow-updates-issues-t3415914/page2#post68173468
pvsgh said:
Don't know if it would make any difference but you should be using Odin 3.11.1 with this latest EPG2 firmware. CSC related files reside in cache.img.ext4 , so it is possible that that particular file is not being flashed in your case.
Click to expand...
Click to collapse
Worked like a charm. Now I have wifi calling and secondary characters on my keyboard again!
You'll also notice that Bluetooth tethering is gone. T-Mobile likes to disable that for some reason. I imagine that buried in one of the CSC files is a line you could delete to restore Bluetooth tethering.
DUMP - OnePlus 6T [OOS 9.0.5/6]
{
"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"
}
boot.img will help get TWRP issues actually do something with their device. ?!
system.img and vendor.img will help with ports , dev , ect.
these zips are not "flashable" !!! just compressed files
Download: DUMP - OnePlus 6T [OOS 9.0.5]
Download: DUMP - OnePlus 6T [OOS 9.0.6]
Download: DUMP - OnePlus 6T [OOS 9.0.7]
My dump & My G-D upload
thx for the dump. will try to boot the system on my op5 since with openbeta he got treble support
S3V3N said:
DUMP - OnePlus 6T [OOS 9.0.5]
boot.img will help get TWRP issues actually do something with their device. ?!
system.img and vendor.img will help with ports , dev , ect.
these zips are not "flashable" !!! just compressed files
Download: DUMP - OnePlus 6T [OOS 9.0.5]
My dump & My G-D upload
Click to expand...
Click to collapse
Yes, I think this is all I need to fix my device. Oneplus sent me a device that wouldn't boot. L2 Tech remoted in to my pc and said apparently the firmware hasn't been flashed to the device. After 5 minutes of troubleshooting they weren't able to get it to flash.
Eventually I was able to get it to register to my pc and this might be what fixes it for me. Downloading as I type this. Unfortunately I already ordered a replacement that shipped an hour ago and have a refund process to return this one started... At least I can play with it til the new one arrives.
Code:
drwxr-xr-x 2 root root 2060 1970-01-01 04:52 .
drwxr-xr-x 3 root root 2200 1970-01-01 04:52 ..
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 ALIGN_TO_128K_1 -> /dev/block/sdd1
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 ALIGN_TO_128K_2 -> /dev/block/sdf1
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 ImageFv -> /dev/block/sde72
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 LOGO_a -> /dev/block/sde20
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 LOGO_b -> /dev/block/sde48
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 abl_a -> /dev/block/sde8
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 abl_b -> /dev/block/sde36
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 aging -> /dev/block/sde58
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 aop_a -> /dev/block/sde1
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 aop_b -> /dev/block/sde29
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 apdp -> /dev/block/sde63
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 bluetooth_a -> /dev/block/sde5
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 bluetooth_b -> /dev/block/sde33
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 boot_a -> /dev/block/sde11
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 boot_b -> /dev/block/sde39
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 cdt -> /dev/block/sdd2
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 cmnlib64_a -> /dev/block/sde13
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 cmnlib64_b -> /dev/block/sde41
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 cmnlib_a -> /dev/block/sde12
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 cmnlib_b -> /dev/block/sde40
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 config -> /dev/block/sda12
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 ddr -> /dev/block/sdd3
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 devcfg_a -> /dev/block/sde14
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 devcfg_b -> /dev/block/sde42
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 devinfo -> /dev/block/sde61
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 dip -> /dev/block/sde62
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 dsp_a -> /dev/block/sde9
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 dsp_b -> /dev/block/sde37
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 dtbo_a -> /dev/block/sde18
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 dtbo_b -> /dev/block/sde46
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 frp -> /dev/block/sda6
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 fsc -> /dev/block/sdf5
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 fsg -> /dev/block/sdf4
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_4j1ed_a -> /dev/block/sde21
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_4j1ed_b -> /dev/block/sde49
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_4u1ea_a -> /dev/block/sde22
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_4u1ea_b -> /dev/block/sde50
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_ufs3_a -> /dev/block/sde23
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_ufs3_b -> /dev/block/sde51
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_ufs4_a -> /dev/block/sde24
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_ufs4_b -> /dev/block/sde52
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_ufs5_a -> /dev/block/sde25
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_ufs5_b -> /dev/block/sde53
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_ufs6_a -> /dev/block/sde26
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_ufs6_b -> /dev/block/sde54
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_ufs7_a -> /dev/block/sde27
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_ufs7_b -> /dev/block/sde55
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_ufs8_a -> /dev/block/sde28
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 fw_ufs8_b -> /dev/block/sde56
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 hyp_a -> /dev/block/sde3
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 hyp_b -> /dev/block/sde31
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 keymaster_a -> /dev/block/sde10
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 keymaster_b -> /dev/block/sde38
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 keystore -> /dev/block/sda5
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 limits -> /dev/block/sde67
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 logdump -> /dev/block/sde71
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 logfs -> /dev/block/sde69
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 mdtp_a -> /dev/block/sde7
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 mdtp_b -> /dev/block/sde35
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 mdtpsecapp_a -> /dev/block/sde6
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 mdtpsecapp_b -> /dev/block/sde34
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 minidump -> /dev/block/sde57
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 misc -> /dev/block/sda3
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 modem_a -> /dev/block/sde4
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 modem_b -> /dev/block/sde32
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 modemst1 -> /dev/block/sdf2
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 modemst2 -> /dev/block/sdf3
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 msadp -> /dev/block/sde64
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 odm_a -> /dev/block/sda15
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 odm_b -> /dev/block/sda16
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 oem_dycnvbk -> /dev/block/sda8
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 oem_stanvbk -> /dev/block/sda9
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 op1 -> /dev/block/sde59
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 op2 -> /dev/block/sda7
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 param -> /dev/block/sda4
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 persist -> /dev/block/sda2
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 qupfw_a -> /dev/block/sde15
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 qupfw_b -> /dev/block/sde43
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 reserve1 -> /dev/block/sda10
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 reserve2 -> /dev/block/sda11
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 sec -> /dev/block/sde60
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 splash -> /dev/block/sde66
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 spunvm -> /dev/block/sde65
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 ssd -> /dev/block/sda1
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 sti -> /dev/block/sde70
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 storsec_a -> /dev/block/sde19
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 storsec_b -> /dev/block/sde47
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 system_a -> /dev/block/sda13
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 system_b -> /dev/block/sda14
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 toolsfv -> /dev/block/sde68
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 tz_a -> /dev/block/sde2
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 tz_b -> /dev/block/sde30
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 userdata -> /dev/block/sda17
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 vbmeta_a -> /dev/block/sde17
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 vbmeta_b -> /dev/block/sde45
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 vendor_a -> /dev/block/sde16
lrwxrwxrwx 1 root root 16 1970-01-01 04:52 vendor_b -> /dev/block/sde44
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 xbl_a -> /dev/block/sdb1
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 xbl_b -> /dev/block/sdc1
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 xbl_config_a -> /dev/block/sdb2
lrwxrwxrwx 1 root root 15 1970-01-01 04:52 xbl_config_b -> /dev/block/sdc2
OnePlus6T:/ #
if someone need the partition above
i owned the oneplus 6T since yesterday. i will make my Eragon Custom Rom for it very soon
@skeleton1911
You're right
Because I am just collecting for the purchase of this phone, I unpacked the firmware and shared it. My mistake
My 6T is stuck in boot loop. It was rooted and had blue spark installed. Can I use these files to recover, how?
You take the boot.img .
Then with buttons hold power and vol+ and vol- until the phone reboots
Then you are in Fastboot Mode
Via ADB flash the boot.img
Fastboot flash boot boot.img
pramathesh said:
My 6T is stuck in boot loop. It was rooted and had blue spark installed. Can I use these files to recover, how?
Click to expand...
Click to collapse
Gesendet von meinem ONEPLUS A6013 mit Tapatalk
---------- Post added at 12:40 PM ---------- Previous post was at 12:37 PM ----------
Hold power and vol-+ and vol-
Gesendet von meinem ONEPLUS A6013 mit Tapatalk
skeleton1911 said:
You take the boot.img .
Then with buttons hold power and vol+ .
When the phone boots again release power but still hold vol+
Then you are in Fastboot Mode
Via ADB flash the boot.img
Fastboot flash boot boot.img
Gesendet von meinem ONEPLUS A6013 mit Tapatalk
Click to expand...
Click to collapse
Let me give this a try and report. My guess is that the 9.0.5 update was applied automatically thereby messing my phone. Also, if the phone was 9.0.4 the 9.0.5 image would work fine, right?
pramathesh said:
Let me give this a try and report. My guess is that the 9.0.5 update was applied automatically thereby messing my phone. Also, if the phone was 9.0.4 the 9.0.5 image would work fine, right?
Click to expand...
Click to collapse
Read above again. Hold all buttons.
Also 9.0.5 is on slot b
And 9.0.4 on a.
So if it don't work you can just set slot b
Fastboot --set-active=b
Gesendet von meinem ONEPLUS A6013 mit Tapatalk
skeleton1911 said:
Read above again. Hold all buttons.
Also 9.0.5 is on slot b
And 9.0.4 on a.
So if it don't work you can just set slot b
Fastboot --set-active=b
Gesendet von meinem ONEPLUS A6013 mit Tapatalk
Click to expand...
Click to collapse
So, if I get this right 9.0.5 can be flashed in a and b either. It a cause of concern then, right?
You can flash it in both yes. But useless . If it's on b it's fine
pramathesh said:
So, if I get this right 9.0.5 can be flashed in a and b either. It a cause of concern then, right?
Click to expand...
Click to collapse
Gesendet von meinem ONEPLUS A6013 mit Tapatalk
skeleton1911 said:
You can flash it in both yes. But useless . If it's on b it's fine
Gesendet von meinem ONEPLUS A6013 mit Tapatalk
Click to expand...
Click to collapse
Downloading the files now. Hoping it works fine, let's hope you are still online just in case something goes off!
---------- Post added at 05:39 PM ---------- Previous post was at 05:31 PM ----------
skeleton1911 said:
You can flash it in both yes. But useless . If it's on b it's fine
Gesendet von meinem ONEPLUS A6013 mit Tapatalk
Click to expand...
Click to collapse
I have a weird problem of the device not getting detected. This is the same machine I had used to root the device earlier. No device number is getting shown but the reboot command did work on the terminal
pramathesh said:
Downloading the files now. Hoping it works fine, let's hope you are still online just in case something goes off!
---------- Post added at 05:39 PM ---------- Previous post was at 05:31 PM ----------
I have a weird problem of the device not getting detected. This is the same machine I had used to root the device earlier. No device number is getting shown but the reboot command did work on the terminal
Click to expand...
Click to collapse
only use adb fastboot. sdk . dont use a program etc.
if you want i can take a look, send me a private message, we go via teamviewer ( i need id and password of teamviewer then)
skeleton1911 said:
only use adb fastboot. sdk . dont use a program etc.
if you want i can take a look, send me a private message, we go via teamviewer ( i need id and password of teamviewer then)
Click to expand...
Click to collapse
Using minimal fastboot and adb. The device number isn't shown but fasboot reboot did work on it. Bluespark is showing partition b is active. So I am guessing that is where I have to flash the boot.img. I am happy to let you take over my PC and let you handle it. Let's get over PM, shall we?
pramathesh said:
Using minimal fastboot and adb. The device number isn't shown but fasboot reboot did work on it. Bluespark is showing partition b is active. So I am guessing that is where I have to flash the boot.img. I am happy to let you take over my PC and let you handle it. Let's get over PM, shall we?
Click to expand...
Click to collapse
yes. send me
skeleton1911 said:
yes. send me
Click to expand...
Click to collapse
fastboot did work. Just tried that before sending you a PM. I cannot thank you enough for saving my life here <3
---------- Post added at 06:03 PM ---------- Previous post was at 06:00 PM ----------
Restarting the phone is causing the loop to happen again. Any way to fix that?
Wifi isn't switching on either. Stuck pretty bad here now
pramathesh said:
fastboot did work. Just tried that before sending you a PM. I cannot thank you enough for saving my life here <3
---------- Post added at 06:03 PM ---------- Previous post was at 06:00 PM ----------
Restarting the phone is causing the loop to happen again. Any way to fix that?
Wifi isn't switching on either. Stuck pretty bad here now
Click to expand...
Click to collapse
i will help you.
now send me pm and we will manage it. (teamviewer)
Is this full dump include all partition? I used other fastboot stock rom and somehow end up losing my VOLTE ON SIM slot 1 but when i switch to sim slot 2 everything work...kinda frustrating...kinda news to OP
vouch post for @skeleton1911. Cannot thank you enough for going out of your way to help me resolve the issue
_BГ@ckθut said:
Is this full dump include all partition? I used other fastboot stock rom and somehow end up losing my VOLTE ON SIM slot 1 but when i switch to sim slot 2 everything work...kinda frustrating...kinda news to OP
Click to expand...
Click to collapse
no. not all.
i think he did not own the phone and therefore he dont has all...
BTW little tip:
Never ever flash the modem_st1 and modem_st2 image files.! after that the risk is high to lose imei numbers.
pramathesh said:
vouch post for @skeleton1911. Cannot thank you enough for going out of your way to help me resolve the issue
Click to expand...
Click to collapse
your welcome!