Related
Hello.
Well, sorry for bothering you... but I really don't know what to do. I am too lost so the things I wrote here may not have sense
There is a recap at the end of this post, so I won't annoy you more than necessary.
Before explaining anything, I will show you my mobile specifications.
- Model: Sony Xperia Go ST27i
- Android version: Ice Cream Sandwich 4.0.4
- Kernel: 6.1.1.B.1.54
- Root?: No
- Unblocked Bootload: No
Click to expand...
Click to collapse
My mobile phone was in the 6.1.B.0.599 kernel. Thanks to the user Bin4ry and his application Root and Restore, I could root it and gain superuser privileges, so I could uninstall annoying apps and customize my phone as I wanted with a custom launcher, etc.
Suddenly, every time I reseted the phone, it began to happen a strange thing. I will explain it detailedly.
- I turn on the phone.
- The screen brights with the SONY logo.
- The XPERIA logo appears.
- The phone vibrates shortly and the screen stops brighting.
- The XPERIA logo keeps until an undetermined moment.
- After X time (minutes, hours), Android asks me for the PIN number and starts working normally.
I was tired of this, but I didn't know what to do or why do this happen.
Today I connected the phone to the PC and Sony Companion asked me to update to 6.1.1.B.1.54. I hoped that would help with the problem. What I didn't know is that when I update the kernel, I must root the phone again.
That's because I tried to root the phone again, but the application Root and Restore couldn't do it. I mean, the application did the work, the phone reseted and the problem I had with the Xperia initialization solved, but the mobile kept unrooted.
This is the Root and Restore log:
Code:
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (18.12.2012) v17 =
======================================================================
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
x) Unroot
Make a choice: 1
Checking if i should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
Waiting for device to shop up, if nothing happens please check if Windows ADB-dr
ivers are installed correctly!
1656 KB/s (210390 bytes in 0.124s)
remote object '/system/bin/ric' does not exist
.
Found Sony Backup-Restore.apk
LT26,LT22 etc. mode enabled!
.
Pushing busybox....
3010 KB/s (1085140 bytes in 0.352s)
Pushing su binary ....
2897 KB/s (91980 bytes in 0.031s)
Pushing Superuser app
3908 KB/s (996704 bytes in 0.249s)
Making busybox runable ...
.
Pushing fake Backup
2999 KB/s (73728 bytes in 0.024s)
Extracting fakebackup on device ...
Watch now your device. Select the backup named RootMe and restore it!
Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.L
AUNCHER] cmp=com.sonyericsson.vendor.backuprestore/.ui.BackupActivity }
If all is successful i will tell you, if not this shell will run forever.
Running ......
Good, it worked! Now we are rebooting soon, please be patient!
Waiting for device to come up again....
Going to copy files to it's place
[B]mount: permission denied (are you root?)[/B]
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
After I investigated a little in this forum, I learnt that I precisely updated to an unrooteable kernel...
I kept investigating and I found out that the solution was downgrading to the kernel I was, then rooting and finally upgrading again, but to downgrade and upgrade I needed to "flash".
I'm not English, I'm noob in Android world and I'm retard, so I couldn't understand how to flash. I installed FlashTools, but I need to download the kernel and I don't know how to find the correct one for my phone. I don't know if FlashTools needs me to unblock Bootload either, but if I need it, I've already got the code from Sony, though maybe there are other unofficial methods...
Sorry for this huge Bible. I will summarize:
I upgraded from .599 to .54 and I can't root. How can I downgrade the kernel?
I'm sorry again for bothering you and for being so retard in this, but could you help me, please? I would like so much to become root again... You can laugh at me :silly: If I wrote something wrong, please, correct me because I'm not English and I could not realize.
Thank you so much :victory:
crystaldolly said:
Hello.
Well, sorry for bothering you... but I really don't know what to do. I am too lost so the things I wrote here may not have sense
There is a recap at the end of this post, so I won't annoy you more than necessary.
Before explaining anything, I will show you my mobile specifications.
My mobile phone was in the 6.1.B.0.599 kernel. Thanks to the user Bin4ry and his application Root and Restore, I could root it and gain superuser privileges, so I could uninstall annoying apps and customize my phone as I wanted with a custom launcher, etc.
Suddenly, every time I reseted the phone, it began to happen a strange thing. I will explain it detailedly.
- I turn on the phone.
- The screen brights with the SONY logo.
- The XPERIA logo appears.
- The phone vibrates shortly and the screen stops brighting.
- The XPERIA logo keeps until an undetermined moment.
- After X time (minutes, hours), Android asks me for the PIN number and starts working normally.
I was tired of this, but I didn't know what to do or why do this happen.
Today I connected the phone to the PC and Sony Companion asked me to update to 6.1.1.B.1.54. I hoped that would help with the problem. What I didn't know is that when I update the kernel, I must root the phone again.
That's because I tried to root the phone again, but the application Root and Restore couldn't do it. I mean, the application did the work, the phone reseted and the problem I had with the Xperia initialization solved, but the mobile kept unrooted.
This is the Root and Restore log:
Code:
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (18.12.2012) v17 =
======================================================================
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
x) Unroot
Make a choice: 1
Checking if i should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
Waiting for device to shop up, if nothing happens please check if Windows ADB-dr
ivers are installed correctly!
1656 KB/s (210390 bytes in 0.124s)
remote object '/system/bin/ric' does not exist
.
Found Sony Backup-Restore.apk
LT26,LT22 etc. mode enabled!
.
Pushing busybox....
3010 KB/s (1085140 bytes in 0.352s)
Pushing su binary ....
2897 KB/s (91980 bytes in 0.031s)
Pushing Superuser app
3908 KB/s (996704 bytes in 0.249s)
Making busybox runable ...
.
Pushing fake Backup
2999 KB/s (73728 bytes in 0.024s)
Extracting fakebackup on device ...
Watch now your device. Select the backup named RootMe and restore it!
Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.L
AUNCHER] cmp=com.sonyericsson.vendor.backuprestore/.ui.BackupActivity }
If all is successful i will tell you, if not this shell will run forever.
Running ......
Good, it worked! Now we are rebooting soon, please be patient!
Waiting for device to come up again....
Going to copy files to it's place
[B]mount: permission denied (are you root?)[/B]
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
After I investigated a little in this forum, I learnt that I precisely updated to an unrooteable kernel...
I kept investigating and I found out that the solution was downgrading to the kernel I was, then rooting and finally upgrading again, but to downgrade and upgrade I needed to "flash".
I'm not English, I'm noob in Android world and I'm retard, so I couldn't understand how to flash. I installed FlashTools, but I need to download the kernel and I don't know how to find the correct one for my phone. I don't know if FlashTools needs me to unblock Bootload either, but if I need it, I've already got the code from Sony, though maybe there are other unofficial methods...
Sorry for this huge Bible. I will summarize:
I upgraded from .599 to .54 and I can't root. How can I downgrade the kernel?
I'm sorry again for bothering you and for being so retard in this, but could you help me, please? I would like so much to become root again... You can laugh at me :silly: If I wrote something wrong, please, correct me because I'm not English and I could not realize.
Thank you so much :victory:
Click to expand...
Click to collapse
Download Flashtool by Bin4ary and Androxyde. Install it. Then You should find the 'rootable ftf' file of your firmware in your Xperia Go forum. Download it. and then put it in the folder where you installed Flashtool. Ex. If you installed it in C Drive, go to C> Program Files> Flashtool> Firmwares and paste the 'ftf' file. Then open Flashtool and click on 'Flash' icon. Select flashmode. Select firmware (Careful). Select Ok and follow instructions on screen. After it is done flashing, disconnect the phone and turn it on. It WILL NOT turn ON on its own. Before flashing, make sure USB debugging is on, unknown sources is checked & you are in MSC mode not in MTP mode.
Flashing this ftf will solve ALL of your problems and will unroot your device.
Once the phone turns on, go to your forum section and search on topics how to root. Once rooted, you can remove any unwanted bloat from your system. I prefer using NoBloat free from market. It's cool and safe app that backups all the apps you delete so you can replace them.
Hit thanks if ^^^it^^^ helped you.
kadukarashutosh7 said:
C Drive, go to C> Program Files> Flashtool> Firmwares and paste the 'ftf' file.
Click to expand...
Click to collapse
its not in program files, just c>flashtool>firmwares
try going here
go .54
or here
or here
for flashtool download
for use search the forums
hit thanks.
Ooooooooh, THANK-YOU-SO-MUUUUUUCH! You're awesome. I don't know how to thank you. I'm root again and I've solved all my problems! Really, thank you. :laugh:
:highfive:
crystaldolly said:
Ooooooooh, THANK-YOU-SO-MUUUUUUCH! You're awesome. I don't know how to thank you. I'm root again and I've solved all my problems! Really, thank you. :laugh:
:highfive:
Click to expand...
Click to collapse
Your welcome. And thanks for your comment. someone from xda helped me to root. So I should do my part for the community
Oh and next time you make a thread, don't include all the bio-history from ten years before, okay.
Sent from my Xperia Mini Pro
---------- Post added at 09:21 PM ---------- Previous post was at 09:17 PM ----------
Oh and change the title to solved, edit it, go advanced and insert solved in place of Q
Sent from my Xperia Mini Pro
Hi, everyone!
I got this pretty device o DX
Coolpad 7268
MSM8225Q 1.2GHz Quad-Core
GPU Adreno203
BUT! The system has tons of customizations and I cant even use the google play. So I decided to install a custom ROM on it.
But I cant find one.
I found a chinese website that explains some kind of rooting process... lots of chinese, so its a bit confusing and the softwares needed are also in chinese. For me its almost impossible to do. I heard that coolpad launched this model with an pure Android on it, for the american market. It will solve all my problems, But I can find the rom nowhere.
I think I need the recovery and the ROM for the process...
Somebody can please help me?
*update*
I tried lots and lots of rooting metods. Nothing can do it succesfully. eRoot, superOneClick... nothing can do it.
Root coolpad
I want to root my coolpad 7268 i / spice coolpad2 mi 496... Plz provide some information in this thread
Here is partition list :
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /tmp tmpfs rw,relatime,size=4096k,mode=771,gid=1000 0 0
debugfs /mnt/debugfs debugfs rw,relatime,gid=512 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.3/by-num/p17 /system ext4 ro,relatime,norecovery 0 0
/dev/block/platform/msm_sdcc.3/by-num/p18 /cache ext4 rw,nosuid,nodev,relatime,nodelalloc,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.3/by-num/p14 /persist ext4 rw,nosuid,nodev,relatime,nodelalloc,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.3/by-num/p21 /data ext4 rw,nosuid,nodev,relatime,nomblk_io_submit,nodelalloc,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/platform/msm_sdcc.3/by-num/p22 /tombstones ext4 rw,nosuid,nodev,relatime,nodelalloc,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.3/by-num/p25 /autobak ext4 rw,nosuid,nodev,relatime,nodelalloc,noauto_da_alloc,data=ordered 0 0
/dev/block/vold/179:20 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:20 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:33 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
I am unable to root this in any way - **** spice mobiles. Also, unable to take a dump of the recovery - keeps giving permission denied.
More Info
Drivers : https://drive.google.com/file/d/0ByoBGpu4hq-bT1cyWWNOeFhXYnc/edit?usp=sharing
To go into the stock recovery, keep both volume buttons pressed while powering on the phone. Else, from ADB, use "adb reboot-recovery" command. You will see the android with red excalamation. Press the Home button to get the screen like below. Long press the power button to select.
Stock Recovery :
There are four options.
First option is unknown. Second option is for installing zip from external SD card. Third option is format data partition. Fourth option is format cache.
Also, I got another option by keeping power up button pressed while inserting USB cable :
Update : On going to the ~download mode [image above], a new uninitialized disk drive of 3.61GB is there in Disk Managment and a Yulong CP7268 USB Storage Device is there in Device Manager with this Hardware ID - USBSTOR\DISK&VEN_YULONG&PROD_CP7268_STORAGE&REV_2.31\8&10C80774&0
Update 2 : Once in this pseudo download mode - I can see about ~20 odd partitions, some of them ext4, and some unknown file format. Parition 17 is the system partition and 18 is the recovery parition.
However, on Ubuntu, I am not able to modify the system partition by adding the su binary since it says owner is "user #2000". Also there is a su binary of 61.40 KB already in the xbin folder.
I
drivers of coolpad mi 496
Sent from my Spice Mi-496 using XDA Premium 4 mobile app
You will be happy to know that I have received this device too (45 minutes back)
Cost me Rs. 5450 only off Snapdeal
Custom recovery flashed and rooted. Root procedure and firmware ports coming soon
Have to work all night tonight so firmware ports will be done over the next couple of days.
Free Radical said:
You will be happy to know that I have received this device too (45 minutes back)
Custom recovery flashed. Root procedure and firmware ports coming soon
Cost me Rs. 5450 only off Snapdeal
Click to expand...
Click to collapse
I too finally hit on the same idea - flash cwm and then root - since by going into download mode I was not able to modify the files.
Thanks mate.
Edit - there is an autobak parition of about 1GB - is it possible to remove that and join with sdcard partition? since we already have shortage of sd card space.
Edit 2 : This is the lonk for the place I got drivers and other stuff - Yulong site : www.yulong.com/product/download/dow...nfoBO.downloadInfo.mobileType=7268#downListUL
I have made the newest ROM link into torrent since I was getting too little speeds as a webseed - http://burnbit.com/torrent/262996/20130629165410699_2_zip
The ROM is in CPB format - I dont know how to open it. If anyone wants to me to upload the same file to G drive - will do the same.
You are on the correct path mate.
The cwm recovery.cpb for coolpad 7268 is working for the Mi-496 proving that this is indeed a clone of the same device.
Don't flash the entire rom. Wait a while and I shall post the exact cpb files, flash tool and recovery.cpb I have used. There is also a mini-root.cpb which I will flash after taking a rom backup and report back here, Lets make a new all things root thread for the Mi-496
Free Radical said:
You are on the correct path mate.
The cwm recovery.cpb for coolpad 7268 is working for the Mi-496 proving that this is indeed a clone of the same device.
Don't flash the entire rom. Wait a while and I shall post the exact cpb files, flash tool and recovery.cpb I have used. There is also a mini-root.cpb which I will flash after taking a rom backup and report back here, Lets make a new all things root thread for the Mi-496
Click to expand...
Click to collapse
Thats fine with me. I too would like to know how to use the CPB files - the yulong software that I downloaded was showing up some weird chinese error and just fc'd on me.
This is how I took backup of the phone.
I took a 4GB or bigger USB drive (I used a 8GB drive). All the data on this drive will get deleted.
Then, install Minitool Partition Home Edition. Plug in the USB drive.
Next - switch off the phone. Keeping the volume up button pressed, plug in the microUSB cable to the phone. The phone will go into the pseudo download mode.
Now, you will get a Coolpad/Yulong 7268 disk drive in your device manager. Also, if you open disk managment, you will see a 3.61 GB partition which is "uninitiated" - I did not initialize it.
Next open Minitool Partition software - select the wizard option. Then you will see several disks Disk 1, Disk 2 and so on. The Coolpad USB disk will have lots of small partitions. Right click on Disk # (where # is the disk number) and right click - copy. A new Copy Wizard will come up and there, select the USB drive which you have inserted in USB port. Next, it will ask whether to adjust the partition size - select option 2 - keep the size same.
Now it will start copying, once finished, you have a soft copy of the phone. This may not be useful always, though.
TO make the img files, I booted into Ubuntu and then gave command
"dd if=/dev/sdc1 of=sdc1" Replace sdc with sdX where X is the USB drive mount. Then, replace 1 by 2 uptill 23. This created all imgs in home directory of Ubuntu - I moved them to a different location.
EDIT : For those who want a flip cover for temporary - buy a Karbon A6 flip cover or silicon cover - it will be a decent fit. You will need to cut out the holes for USB, headphone and speaker grille. Got one for INR 150 yesterday.
Spice Coolpad 2 MI-496 / 酷派 7268 Discussion Thread - xda-developers
coolpad -2
Oh ho! Thank god I am not alone with this device.
I also bought it from snapdeal via Rs.500 off coupon
but really a disappointed after use it for two days. Really amazing to find this thread and now will be use it with the full power.
By the way, is it have, sms bugs, I cannot receive any mail from banking alert.
Thank you guys for the awesome work. I am not really helpful at software side but will be tested as soon.
Probably due to the crap preloaded on the device. Shall post a cwm flashable rooted stock rom later. Trying to get MIUI to boot.
Not that bad a device considering HTC Desire 600 which has the same SoC sells for 26k which is almost 5 times the price you are getting this for.
Its good device @6000.... and working fine... all games are running on it...but getting hoy after playing games.. only thing i want is to root my phone .. to make it supercomputer smartphone..
Sent from my Spice Mi-496 using XDA Premium 4 mobile app
Hello @Free Radical i want drivers of spice mi 496 and want to know how to root this device
Sent from my Spice Mi-496 using XDA Premium 4 mobile app
sohanjaryal said:
Hello @Free Radical i want drivers of spice mi 496 and want to know how to root this device
Sent from my Spice Mi-496 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ADB and USB drivers - https://drive.google.com/file/d/0ByoBGpu4hq-bT1cyWWNOeFhXYnc/edit?usp=sharing
Thanks @vivek.krishnan
Sent from my Spice Mi-496 using XDA Premium 4 mobile app
Will be posting a cwm flashable stock based rom later today. Its currently uploading.
Prerooted, deodexed, zipaligned, debloated and optimized
Should be the first rom for this device and a backup if you mess up and want to go back to stock.
Already tested. Expect the download link near midnight today.
Thank you guys for the efforts.
Indeed very good device among the competitors.
Sent from my Spice Mi-496 using xda app-developers app
Thanks @Free Radical
Sent from my Spice Mi-496 using XDA Premium 4 mobile app
Testers wanted: Anyone who uses this method, let me know if you can access stock recovery after this method.
Summery
Thanks to the amazing work by our active member @bibikalka, a method was found to unbrick these devices Thread link here. The method he found was slightly tedious for some people, so I've decided to put together a Linux iso that you can boot into on your computer with everything you need to get your device running again. It uses the same methods proposed but makes things easier. This comes with all the necessary drivers, scripts to do everything you need, all the img files needed to flash, a hex editor for advanced users, and more. Before the scripts included in this OS, determining the option (A, B, or C) to take in order to unbrick the device required .part files to be evaluated manually. Now with the custom script, it can quickly evaluate what option to take.
Video Instructions
Brief Instructions
1. Download the Linux iso:
Linux ISO
2. Burn the iso to a USB drive or cd
3. Boot into the operating system
4. Type "root" at the login prompt
5. Right click on the desktop and choose file manager. Go to "aftv2-tools" folder
6. Right click on file manager and press "open in terminal"
7. From device turned off, enter command "./handshake.py", then plug in device. You may need to do this a couple times to get a connection. Try pressing volume keys & power etc to get it connected. See video if you have problems
8. After handshake is complete, run "./reader.sh"
9. After all addresses are read in, run "./determineOption.sh". You should get back a result of A, B, or C
10. Depending on the option returned (A,B,or C), run "./readerSpecialOptionA.sh", "./readerSpecialOptionB.sh", or "./readerSpecialOptionC.sh". This is an optional step but may be useful if you want to back up part files or their were no options available. Back up part files to a usb drive if you want to be safe.
11. Now the actual unbricking. Run "./unbrickOptionA.sh", "./unbrickOptionB.sh", or "./unbrickOptionA.sh" depending on your option. This can take about 40 minutes
12. hold volume up and run "./complete.sh" at the same time to get into TWRP
13. boot into your default operating system on your computer
BE VERY CAREFUL FROM NOW ON
13. We will be installing Fire OS 5.3.1. If you are not installing this ROM, make sure you know what you are doing. Download the ROM:
update-kindle-20.5.5.2_user_552153420.bin
14. Download 5.4.1_1133_stock_recovery_uboot.zip: 5.4.1_1133_stock_recovery_uboot.zip. Without this you could turn your device into a paperweight. This installs stock recovery and a uboot version that MUST be installed. This file was taken from the thread here: how-to-upgrade-to-lollipop-root-gapps
15. Rename the ROM extension from .bin to .zip
16. Transfer the two files to the Fire
17. Do a factory reset. Flash the ROM and uboot&recovery file
18. Reboot! Your device should now be working. It will take about 15 mins to boot up.
Big thanks to @bibikalka for helping work everything out and for the initial unbrick method.
Edit 10/13/21: Fixed Google Drive Link
Linux ISO Changelog
Updated 10/5/16:
*Optomized scripts
*Added "complete.sh" This reboots the device
Updated 9/27/16:
*Added script to auto-detect which unbrick option to use (determineOption.sh)
*Added scripts to write img files to correct addresses ( unbrickOptionA.sh, unbrickOptionB.sh, and unbrickOptionC.sh)
*Added scripts to read in and label part files (readerSpecialOptionA.sh, readerSpecialOptionB.sh, and readerSpecialOptionC.sh)
*Nemo open in terminal fixed
*.part files set to open with ghex by default
Updated 9/24/16:
*Nemo as default file manager
*Updated html page with instructions from forum
well, after seriously struggling with the parent thread mentioned in the OP I've managed to get to TWRP & am just waiting for my win10 machine to install it's updates before attempting to adb push the uboot & zip files for installation back to fireOS.
feels great to see the screen displaying something other than the looping amazon logo after months of frustration. I do not have the words to express my gratitude for @powerpoint45 for an excellent & well thought through tool and walkthrough. special mention also goes out to @bibikalka
gascomm said:
well, after seriously struggling with the parent thread mentioned in the OP I've managed to get to TWRP & am just waiting for my win10 machine to install it's updates before attempting to adb push the uboot & zip files for installation back to fireOS.
feels great to see the screen displaying something other than the looping amazon logo after months of frustration. I do not have the words to express my gratitude for @powerpoint45 for an excellent & well thought through tool and walkthrough. special mention also goes out to @bibikalka
Click to expand...
Click to collapse
great to hear! I hope everything works for you! After you get everything done, can you check if you can get into recovery.
after flashing both zips & rebooting I've now got my working fire (OS 5.3.1.0) back. thank you Mr PowerPoint!
i tried rebooting to recovery & it now takes me to the stock amazon recovery not TWRP..... which is unfortunate.
I did get asked if I wanted to install SuperUser which was a no-brainer YES. although I'm staying offline until I identify a functional (fast) flavour of android to flash. suggestions welcome.
gascomm said:
after flashing both zips & rebooting I've now got my working fire (OS 5.3.1.0) back. thank you Mr PowerPoint!
i be tried rebooting to recovery & it now takes me to the stock amazon recovery not TWRP..... which is unfortunate.
I did get asked if I wanted to install SuperUser which was a no-brainer YES. although I'm staying offline until I identify a functional (fast) flavour of android to flash. suggestions welcome.
Click to expand...
Click to collapse
Good to hear everything is working. Ya TWRP does not work with 5.x bootloader. Good to hear you can get into stock recovery because I had some incidents where I could not get into it. Thanks for responding. The only custom ROM ATM is CM13.
powerpoint45 said:
The only custom ROM ATM is CM13.
Click to expand...
Click to collapse
sorry to trouble you again but do you know where I can find a guide/walkthrough of how to root via adb & install twrp or cwm to allow flashing of a rom & gapps..
I can only find the kingroot method & the CM11 rom discussion. where might I find the CM13 you mentioned?
I have searched fruitlessly. I guess I just need a little guidance to avoid running straight into another brick.
cheers.
gascomm said:
sorry to trouble you again but do you know where I can find a guide/walkthrough of how to root via adb & install twrp or cwm to allow flashing of a rom & gapps..
I can only find the kingroot method & the CM11 rom discussion. where might I find the CM13 you mentioned?
I have searched fruitlessly. I guess I just need a little guidance to avoid running straight into another brick.
cheers.
Click to expand...
Click to collapse
I meant to say CM11. This guide is probably one of the best http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950/page1
This is a bit older one: http://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351/page1
In order to have TWRP, you must have a 4.x bootloader so CM11 would work with it.
Thank you
I have a question I can work downgrade from 5.3.1 to 4.5.3
I'm currently on version 5.3.1
PRInCEI7 said:
Thank you
I have a question I can work downgrade from 5.3.1 to 4.5.3
I'm currently on version 5.3.1
Click to expand...
Click to collapse
yes you should be fine doing that
Unfortunately, did not respond
I worked
MacBook-Air-2:ROOT IP$ ./handshake.py
Waiting for preloader...
Found port = /dev/cu.usbmodem1420
Handshake complete!
In the second step does not respond to the order ./reader.sh
Also tried
/.read_mmc.py 0x0000000 0x1000 0x0000000.part
Does not respond
By the way tried way on more than one device
And tried through the system Max os x and the system arch-custom-firehd67-unbrick100516.iso did not work and also the same result
MY device Amazon Fire HD 6 version 5.3.1 All functions work, but I need to work downgrade to 4.5.3
Is there a solution to my problem
[/SIZE]
@powerpoint45 thanks for the pointers. I am now the proud owned of an hd6 booting straight into cm11 & it's been well worth the wait. I am forever in your digital debt.
gascomm said:
@powerpoint45 thanks for the pointers. I am now the proud owned of an hd6 booting straight into cm11 & it's been well worth the wait. I am forever in your digital debt.
Click to expand...
Click to collapse
sweet!!!
PRInCEI7 said:
Unfortunately, did not respond
I worked
MacBook-Air-2:ROOT IP$ ./handshake.py
Waiting for preloader...
Found port = /dev/cu.usbmodem1420
Handshake complete!
In the second step does not respond to the order ./reader.sh
Also tried
/.read_mmc.py 0x0000000 0x1000 0x0000000.part
Does not respond
By the way tried way on more than one device
And tried through the system Max os x and the system arch-custom-firehd67-unbrick100516.iso did not work and also the same result
MY device Amazon Fire HD 6 version 5.3.1 All functions work, but I need to work downgrade to 4.5.3
Is there a solution to my problem
[/SIZE]
Click to expand...
Click to collapse
I am also getting the same results with my HD 7 4th gen. The handshake completes just fine, but the reader just hangs. When I'm in recovery, I get errors saying the /cache folder failed to mount. I'm thinking the memory is corrupt and there is no way to fix this.
nai1ed said:
I am also getting the same results with my HD 7 4th gen. The handshake completes just fine, but the reader just hangs. When I'm in recovery, I get errors saying the /cache folder failed to mount. I'm thinking the memory is corrupt and there is no way to fix this.
Click to expand...
Click to collapse
Unfortunately it appears that with the latest bootloader on the latest Amazon update that they have disabled these commands (such as reading and writing). Unfortunately if you can't get into recovery with (vol+ & power) then it is currently unrecoverable. Best option for an unrecoverable device would be to buy another motherboard from eBay or some place. They are pretty cheap and easy to replace. I've had to do it a couple times now.
Confused
First you say it should be OK to downgrade:
powerpoint45 said:
PRInCEI7 said:
Thank you
I have a question I can work downgrade from 5.3.1 to 4.5.3
I'm currently on version 5.3.1
Click to expand...
Click to collapse
yes you should be fine doing that
Click to expand...
Click to collapse
Although, it's unclear how, since reports indicate that sideloading older
firmware bricks the device (or, does that only apply to 5.x?).
Then, we learn that the preloader trick (from aftv2-tools) doesn't work anymore:
Code:
[[email protected] aftv2-tools]# ./handshake.py
Waiting for preloader...
Found port = /dev/ttyACM0
Handshake complete!
[[email protected] aftv2-tools]# ./reader.sh
^CTraceback (most recent call last):
File "./read_mmc.py", line 355, in <module>
if msdc_dma_status():
File "./read_mmc.py", line 146, in msdc_dma_status
return False if sdr_read32(MSDC_CFG) & MSDC_CFG_PIO else True
File "./read_mmc.py", line 82, in sdr_read32
check(dev.read(2), b'\x00\x00') # arg check
File "/usr/lib/python3.5/site-packages/serial/serialposix.py", line 450, in read
ready, _, _ = select.select([self.fd, self.pipe_abort_read_r], [], [], timeout)
KeyboardInterrupt
^CTraceback (most recent call last):
File "./read_mmc.py", line 355, in <module>
if msdc_dma_status():
File "./read_mmc.py", line 146, in msdc_dma_status
return False if sdr_read32(MSDC_CFG) & MSDC_CFG_PIO else True
File "./read_mmc.py", line 82, in sdr_read32
check(dev.read(2), b'\x00\x00') # arg check
File "/usr/lib/python3.5/site-packages/serial/serialposix.py", line 450, in read
ready, _, _ = select.select([self.fd, self.pipe_abort_read_r], [], [], timeout)
KeyboardInterrupt
^Z
[1]+ Stopped ./reader.sh
[[email protected] aftv2-tools]# kill %1
[[email protected] aftv2-tools]#
[1]+ Terminated ./reader.sh
[[email protected] aftv2-tools]#
The above is for a 4th gen HD7 with this device showing in 'lsusb':
Code:
Bus 001 Device 006: ID 0e8d:3000 MediaTek Inc.
powerpoint45 said:
Unfortunately it appears that with the latest bootloader on the latest Amazon update that they have disabled these commands (such as reading and writing). Unfortunately if you can't get into recovery with (vol+ & power) then it is currently unrecoverable. Best option for an unrecoverable device would be to buy another motherboard from eBay or some place. They are pretty cheap and easy to replace. I've had to do it a couple times now.
Click to expand...
Click to collapse
BTW, are we sure that this is *disabled* as opposed to _tweaked_?
(e.g. by changing the protocol slightly by, say, requiring an extra byte
or two "confirmation" before execution? has anyone bothered reversing
the bootloader? [Please excuse my ignorance, but would this be handled
by UBOOT, TEE1, or some other component?])
So, what's the current best option for 5.3.1?
---------- Post added at 11:23 ---------- Previous post was at 10:58 ----------
draxie said:
BTW, are we sure that this is *disabled* as opposed to _tweaked_?
(e.g. by changing the protocol slightly by, say, requiring an extra byte
or two "confirmation" before execution? has anyone bothered reversing
the bootloader?
Click to expand...
Click to collapse
OK. So, I found this post by @zeroepoch,
which makes it very clear that said exercise has been performed for the AFTV2...
No reason to believe that this would be different for the Fire HD7...
draxie said:
First you say it should be OK to downgrade:
Although, it's unclear how, since reports indicate that sideloading older
firmware bricks the device (or, does that only apply to 5.x?).
Then, we learn that the preloader trick (from aftv2-tools) doesn't work anymore:
The above is for a 4th gen HD7 with this device showing in 'lsusb':
BTW, are we sure that this is *disabled* as opposed to _tweaked_?
(e.g. by changing the protocol slightly by, say, requiring an extra byte
or two "confirmation" before execution? has anyone bothered reversing
the bootloader? [Please excuse my ignorance, but would this be handled
by UBOOT, TEE1, or some other component?])
So, what's the current best option for 5.3.1?
---------- Post added at 11:23 ---------- Previous post was at 10:58 ----------
OK. So, I found this post by @zeroepoch,
which makes it very clear that said exercise has been performed for the AFTV2...
No reason to believe that this would be different for the Fire HD7...
Click to expand...
Click to collapse
My understanding is that you only need to worry about bricking if You are downgrading to another lollypop ROM. We found out that the device has a fuse that is set in later lollypop ROMs where it will check against the current version. But this check only seems to be on lollipop ROM's. As for the aftv2 protocol, you might be right but I don't know enough about that yet to know. Currently we have no unbrick method for latest bootloader. If you can get into recovery then you could sideload but most can't get into recovery during brick.
I've followed the steps but not into twrp, only screen amazon and reset. I'm not good at English
error trying to unbrick hd6
[[email protected] aftv2-tools]# ./complete.sh
1: 0xd1
4: 0x00 0x00 0x00 0x00
4: 0x00 0x00 0x00 0x01
Traceback (most recent call last):
File "/usr/lib/python3.5/site-packages/serial/serialposix.py", line 468, in read
'device reports readiness to read but returned no data '
serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "./read32.py", line 69, in <module>
ret = read32(addr, size)
File "./read32.py", line 45, in read32
print_hex_byte(dev.read(2)) # status
File "/usr/lib/python3.5/site-packages/serial/serialposix.py", line 475, in read
raise SerialException('read failed: {}'.format(e))
serial.serialutil.SerialException: read failed: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
[[email protected] aftv2-tools]#
kingwill101 said:
[[email protected] aftv2-tools]# ./complete.sh
1: 0xd1
4: 0x00 0x00 0x00 0x00
4: 0x00 0x00 0x00 0x01
Traceback (most recent call last):
File "/usr/lib/python3.5/site-packages/serial/serialposix.py", line 468, in read
'device reports readiness to read but returned no data '
serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "./read32.py", line 69, in <module>
ret = read32(addr, size)
File "./read32.py", line 45, in read32
print_hex_byte(dev.read(2)) # status
File "/usr/lib/python3.5/site-packages/serial/serialposix.py", line 475, in read
raise SerialException('read failed: {}'.format(e))
serial.serialutil.SerialException: read failed: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
[[email protected] aftv2-tools]#
Click to expand...
Click to collapse
You are on any version.
You can access to recovery now
I've flashed cm 14.1 osprey and it is working all fine accept I've lost root and my incoming and outgoing calls are not working in one sim(data is working fine) and second problem is my root access has lost after some time. I tried with latest update of SuperSU but both sim card not shows up, with old versions supersu just don't get installed.
And yes i flashed it more than one time but the problem continues .
Phone status:
Moto g3 ,twrp latest version installed, everything working fine accept these two problems.
Plz help ,any small help will be appreciated.
Clean flash again, don't flash superSU instead use built in root method. Because CM is already rooted.
aadison said:
Clean flash again, don't flash superSU instead use built in root method. Because CM is already rooted.
Click to expand...
Click to collapse
Done clean flashing but still not incoming and outgoing not working on one sim slot.
And thanks for replying.
manmali said:
Done clean flashing but still not incoming and outgoing not working on one sim slot.
And thanks for replying.
Click to expand...
Click to collapse
Wipe system and reflash ROM an gapps, or better yet clean flash the whole thing... Not really sure what calls would have to do with root access though.
acejavelin said:
Wipe system and reflash ROM an gapps, or better yet clean flash the whole thing... Not really sure what calls would have to do with root access though.
Click to expand...
Click to collapse
I always flash rom after a deep wipe and i flashed 3 updates of cm 14.1 but same problem occured in all.
You must think may be slot is not working but to check this i flashed stock rom once, it just worked. Now what to do??
And thanks for suggestions
manmali said:
I always flash rom after a deep wipe and i flashed 3 updates of cm 14.1 but same problem occured in all.
You must think may be slot is not working but to check this i flashed stock rom once, it just worked. Now what to do??
And thanks for suggestions
Click to expand...
Click to collapse
Try a different ROM... AICP or RR or something.
acejavelin said:
Try a different ROM... AICP or RR or something.
Click to expand...
Click to collapse
I don't know about any other roms accept cm, I'll read about them if they are good, I'll try flashing em. Thanks
manmali said:
I don't know about any other roms accept cm, I'll read about them if they are good, I'll try flashing em. Thanks
Click to expand...
Click to collapse
Lol... I have nothing against CM, but there are definitely other good roms out there, CM is very basic and bland, which is not intended to be negative, but there are much more feature packed roms out there. I hope you enjoy your "journey" past CM.
acejavelin said:
Lol... I have nothing against CM, but there are definitely other good roms out there, CM is very basic and bland, which is not intended to be negative, but there are much more feature packed roms out there. I hope you enjoy your "journey" past CM.
Click to expand...
Click to collapse
Thankyou , suggest me which rom should i try first??
manmali said:
Thankyou , suggest me which rom should i try first??
Click to expand...
Click to collapse
I don't know... Rez Remix was always my favorite on G3, personally I would stick with Marshmallow for now too. Dirty Unicorns, AICP, and BrokenOS are solid options as well.
acejavelin said:
I don't know... Rez Remix was always my favorite on G3, personally I would stick with Marshmallow for now too. Dirty Unicorns, AICP, and BrokenOS are solid options as well.
Click to expand...
Click to collapse
I going for aicp, it's ui customization features seems pretty good. Thanks for your time
manmali said:
I always flash rom after a deep wipe and i flashed 3 updates of cm 14.1 but same problem occured in all.
You must think may be slot is not working but to check this i flashed stock rom once, it just worked. Now what to do??
And thanks for suggestions
Click to expand...
Click to collapse
Same for me on the oneplus-3t. Our similarity is that I also use cm-14.1.
The error message is lengthy (170 lines) and reports things like:
WARNING: linker: /su/bin/sush: unused DT entry: type 0xaa1303e0d00000c1 arg 0x97ff73519111c021
WARNING: linker: /su/bin/sush: unused DT entry: type 0xd00000c134000fa0 arg 0x9111e021aa1303e0
WARNING: linker: /su/bin/sush: unused DT entry: type 0x350010e097ff734c arg 0x910b8062d00000c3
CANNOT LINK EXECUTABLE "/su/bin/sush": empty/missing DT_HASH/DT_GNU_HASH in "/su/bin/sush" (new hash type from the future?)
Aborted
In a different root shell I was able to verify, that the binaries /su/bin/app_process and /su/bin/sush changed both, content and date.
Old (working) version
ls -lani:
23 -rwxr-xr-x 1 0 0 279K 1970-01-17 19:09 /su/bin/sush*
24 -rwxr-xr-x 1 0 0 18K 1970-01-17 19:09 /su/bin/app_process*
md5sum:
daf9ea634bfd1577e62dcf30a998586f /su/bin/sush
4aadf50b46676e6da7c38ab40c0f1ac7 /su/bin/app_process
broken version:
ls -lani
23 -rwxr-xr-x 1 0 0 279K 1970-01-17 19:09 /su/bin/sush*
24 -rwxr-xr-x 1 0 0 18K 1970-01-17 19:09 /su/bin/app_process*
md5sum:
4fddfedaeaea883514cd6d78d2412766 /su/bin/sush
71f9cf0c48095fdf41fab958407bc265 /su/bin/app_process
A reboot fixes the issue. I'll try and see if there are files with the given md5sum on the phone. I tried to find those files: no success. Just to find that sush and app_process vanished altogether. Still: rebooting fixes this.
mrcvs said:
Same for me on the oneplus-3t. Our similarity is that I also use cm-14.1.
The error message is lengthy (170 lines) and reports things like:
WARNING: linker: /su/bin/sush: unused DT entry: type 0xaa1303e0d00000c1 arg 0x97ff73519111c021
WARNING: linker: /su/bin/sush: unused DT entry: type 0xd00000c134000fa0 arg 0x9111e021aa1303e0
WARNING: linker: /su/bin/sush: unused DT entry: type 0x350010e097ff734c arg 0x910b8062d00000c3
CANNOT LINK EXECUTABLE "/su/bin/sush": empty/missing DT_HASH/DT_GNU_HASH in "/su/bin/sush" (new hash type from the future?)
Aborted
In a different root shell I was able to verify, that the binaries /su/bin/app_process and /su/bin/sush changed both, content and date.
Old (working) version
ls -lani:
23 -rwxr-xr-x 1 0 0 279K 1970-01-17 19:09 /su/bin/sush*
24 -rwxr-xr-x 1 0 0 18K 1970-01-17 19:09 /su/bin/app_process*
md5sum:
daf9ea634bfd1577e62dcf30a998586f /su/bin/sush
4aadf50b46676e6da7c38ab40c0f1ac7 /su/bin/app_process
broken version:
ls -lani
23 -rwxr-xr-x 1 0 0 279K 1970-01-17 19:09 /su/bin/sush*
24 -rwxr-xr-x 1 0 0 18K 1970-01-17 19:09 /su/bin/app_process*
md5sum:
4fddfedaeaea883514cd6d78d2412766 /su/bin/sush
71f9cf0c48095fdf41fab958407bc265 /su/bin/app_process
A reboot fixes the issue. I'll try and see if there are files with the given md5sum on the phone. I tried to find those files: no success. Just to find that sush and app_process vanished altogether. Still: rebooting fixes this.
Click to expand...
Click to collapse
Unhappy coensidence, I'm getting the same issue right now on my zte axon 7 and I'm in total panic mode after uncountable firmware flashing and trials, My Phone's nand won't stand long, even tho it's ufs 2.0
different phones, different softwares and the same error, I think supersu is getting weak in general with google's latest policy against modding. It's just...xposed is doa, cm is long gone with the theme engine that everyone loved, rooting is not as easy as it used to be and simple things are getting harder and harder. besides everything, going off-road here, Im sick of dealing with google's bad temper about this, This is the first time in my life I consider a jailbroken iphone over android, which is sad.
anyways, Im looking for a fix of this very annoying issue, btw what file system you use?
maybe f2fs is the reason for all this?
Hey guys! Some of you might know me from the LG G5 scene, but I have since moved on from there and am hoping to make some progress with the Gear S3
After doing some digging and paying zero attention in class today, I came across the kernel source files for the Exynos 7270 and the combination firmwares for the Gear 3 Classic and Frontier versions.
If you don't know what combination files are here (link removed) is a great explanation but the TL;DR is that this is the internal firmware Samsung uses to reset devices, so it gives you full read/write access to the device including root access. So basically this is a pre-rooted firmware, and I assume that it is bootloader unlocked as it appears to flash an engineer sboot (bootloader), so I believe this would be the first step towards porting Android Wear/TWRP!
The kernel source is what we will actually use to port over AW/TWRP. It does not seem to have been posted before, and took me a few hours of digging to find. My watch comes in tomorrow, and after I flash this firmware I will pull the boot.img and start making a device/vendor tree to attempt and make a kernel!
Here is the kernel source for the Exynos 7270: https://github.com/HonestlyAnnoying/tizen_kernel_exynos7270
Here is the kernel source for the Gear S3 (all versions) (will upload to GitHub in the morning): Samsung Opensource
Here is the SM-R770 (Classic) combination firmware [R770XXU2BQC2]: link
Here is the SM-R760 (Frontier) combination firmware [R760XXU2BQC2]: link
The road to porting Android Wear is going to take a lot of work, and any help developing (not testing for now!) would be EXTREMELY appreciated (looking at you guys @cipherswitch @biktor_gj !). If you would like to help with development or would like to contribute in any way, please PM me or hit me up on Skype (honestly.annoying)!
Here is a Google Drive folder with all files I have for this, it will be updated as new things are found
The one thing that might persuade me to try a sammy product! Thanks for your efforts @Honestly Annoying
Update: have flashed this, can confirm it has root access!! Pulling images now
Wow!!! Fingers crossed!!
@Honestly Annoying
Please, can you tell us what you see on Screen?
Maybe screenshot if posible...
I have flashed just for fun the older Z1 Combination I have... AOC1... and my SM-Z130H shows testmode Icons...
Later I can upload Screenshot... I have to remove something...
But in this Firmware I can enter all testmode Codes via Keys... like:
*#197328640#
And more... this is blocked in normal Firmware...
Cool. su work nice...
I can enter su in Shell and Super User is active... instead SDB Command:
sdb root on
Best Regards
Edit 1.
Screenshot from Combination Firmware AOC1 I have added in this Post:
https://forum.xda-developers.com/showpost.php?p=71744490&postcount=413
adfree said:
@Honestly Annoying
Please, can you tell us what you see on Screen?
Maybe screenshot if posible...
I have flashed just for fun the older Z1 Combination I have... AOC1... and my SM-Z130H shows testmode Icons...
Later I can upload Screenshot... I have to remove something...
But in this Firmware I can enter all testmode Codes via Keys... like:
*#197328640#
And more... this is blocked in normal Firmware...
Cool. su work nice...
I can enter su in Shell and Super User is active... instead SDB Command:
sdb root on
Best Regards
Edit 1.
Screenshot from Combination Firmware AOC1 I have added in this Post:
https://forum.xda-developers.com/showpost.php?p=71744490&postcount=413
Click to expand...
Click to collapse
I'm just going to start dumping information I find in this thread
this is the partition scheme
Code:
sh-3.2# ls -l /dev/disk/by-partlabel
total 0
lrwxrwxrwx 1 root root 15 Apr 6 09:52 boot -> ../../mmcblk0p8
lrwxrwxrwx 1 root root 15 Apr 6 09:52 cm -> ../../mmcblk0p7
lrwxrwxrwx 1 root root 15 Apr 6 09:52 cpnvcore -> ../../mmcblk0p3
lrwxrwxrwx 1 root root 15 Apr 6 09:52 csa -> ../../mmcblk0p2
lrwxrwxrwx 1 root root 16 Apr 6 09:52 csc -> ../../mmcblk0p11
lrwxrwxrwx 1 root root 16 Apr 6 09:52 module -> ../../mmcblk0p10
lrwxrwxrwx 1 root root 15 Apr 6 09:52 param -> ../../mmcblk0p6
lrwxrwxrwx 1 root root 15 Apr 6 09:52 ramdisk1 -> ../../mmcblk0p5
lrwxrwxrwx 1 root root 15 Apr 6 09:52 ramdisk2 -> ../../mmcblk0p4
lrwxrwxrwx 1 root root 15 Apr 6 09:52 recovery -> ../../mmcblk0p9
lrwxrwxrwx 1 root root 16 Apr 6 09:52 rootfs -> ../../mmcblk0p14
lrwxrwxrwx 1 root root 16 Apr 6 09:52 steady -> ../../mmcblk0p15
lrwxrwxrwx 1 root root 16 Apr 6 09:52 system-data -> ../../mmcblk0p12
lrwxrwxrwx 1 root root 15 Apr 6 09:52 tup -> ../../mmcblk0p1
lrwxrwxrwx 1 root root 16 Apr 6 09:52 user -> ../../mmcblk0p13
Code:
sh-3.2# ls -l /dev/disk/by-label
total 0
lrwxrwxrwx 1 root root 16 Apr 6 09:52 modules -> ../../mmcblk0p10
lrwxrwxrwx 1 root root 10 Apr 6 09:52 ramdisk -> ../../ram0
lrwxrwxrwx 1 root root 15 Apr 6 09:52 ramdisk-recovery -> ../../mmcblk0p4
lrwxrwxrwx 1 root root 16 Apr 6 09:52 rootfs -> ../../mmcblk0p14
lrwxrwxrwx 1 root root 16 Apr 6 09:52 tizen -> ../../mmcblk0p13
Honestly Annoying said:
Update: have flashed this, can confirm it has root access!! Pulling images now
Click to expand...
Click to collapse
Did it erase the serial number of the device?
10urshin said:
Did it erase the serial number of the device?
Click to expand...
Click to collapse
nope
Honestly Annoying said:
nope
Click to expand...
Click to collapse
How about knox trip?
10urshin said:
How about knox trip?
Click to expand...
Click to collapse
how can I check?
Honestly Annoying said:
how can I check?
Click to expand...
Click to collapse
Good question. I don't know. I thought it might show on download mode but it doesn't.
This is the boot.img and recovery.img. The Tizen does not seem to extract like an Android kernel, will have to look into this more...
Also, they are both 16.8MB in size, possibly the same image?
Check this path:
/home/developer
Here is device-profile.xml inside...
This allow Privileges of all 3 Levels:
Public
Partner
Platform
But for now only if this Combination Firmware is flashed... it ignores Serial Number/DUID... maybe by these 0 Byte Flag file(s) in CSC...
Best Regards
Edit 1.
... seems my fault...
All Certs are inside...
Code:
usr/share/cert-svc/certs/code-signing/tizen
So fingerprint should be similar like in Reference devices...
Code:
usr/share/wrt-engine
Will later check with open eyes... now better sleep...
adfree said:
Check this path:
/home/developer
Here is device-profile.xml inside...
This allow Privileges of all 3 Levels:
Public
Partner
Platform
But for now only if this Combination Firmware is flashed... it ignores Serial Number/DUID... maybe by these 0 Byte Flag file(s) in CSC...
Best Regards
Click to expand...
Click to collapse
here ya go
Thank you for device-profile.xml...
Should be same here...
https://forum.xda-developers.com/showpost.php?p=71737611&postcount=18
And maybe in all FTMA Combination files... all Gear... all Z-Mobiles...
But reason for working seems not this file...
Sorry, my fault...
But difference in these 2 folders...
Code:
usr/share/wrt-engine/fingerprint_list.xml
and in commercial devices... Certs missing...
Code:
usr/share/cert-svc/certs/code-signing/tizen
This is what I did long time ago in my rooted Zseries Firmware...
By "mistake"... :laugh:
I have nuked device-profile.xml... because I was tooo lazy to register my Email and Certs...
Best Regards
Currently trying to extract the boot.img... should be studying for the SAT but screw it
I did lose Samsung Pay, but to me that is not a big deal. Waiting for a USA firmware to be released to reflash
EDIT: JUST KIDDING. It's still there! I'm an idiot lol
This is great to see! Good luck guys, hope you get this all worked out. Android Wear on the Gear S3 would be the perfect combination! :good:
I have the S3 Frontier, but not all that knowledgeable with Android dev unfortunately.
the_scotsman said:
This is great to see! Good luck guys, hope you get this all worked out. Android Wear on the Gear S3 would be the perfect combination! :good:
I have the S3 Frontier, but not all that knowledgeable with Android dev unfortunately.
Click to expand...
Click to collapse
Honestly at this point any help would be greatly appreciated. Do you have any interest/time available to help out?