Hi, I found out that there are official cyan roms now and I wanted to test them. For root, I installed kingroot app. Then I used the app flashify for flashing newest TWRP (from this forum) on my device, and it also says it is done, but after reboot, i get a pink screen with some kind of ram dump text. I can restart into normal android from g2 mini, but I want to use marshmallow.
Euathlus1985 said:
Hi, I found out that there are official cyan roms now and I wanted to test them. For root, I installed kingroot app. Then I used the app flashify for flashing newest TWRP (from this forum) on my device, and it also says it is done, but after reboot, i get a pink screen with some kind of ram dump text. I can restart into normal android from g2 mini, but I want to use marshmallow.
Click to expand...
Click to collapse
Can u post the image plzz? Someone might help u. ( I can too)???
tra_dax
Well I uploaded a picture to gdrive, but I cant post this link here Ok, it works with CODE tag.
Code:
https://drive.google.com/00b54106-bfd9-49ed-9f1e-550ea1df1ec9
It seems like I need to unlock the bootloader too, I downloaded this file and Terminal Emulator and typed in everything, but it says "permission denied"
Euathlus1985 said:
Well I uploaded a picture to gdrive, but I cant post this link here Ok, it works with CODE tag.
Code:
https://drive.google.com/00b54106-bfd9-49ed-9f1e-550ea1df1ec9
It seems like I need to unlock the bootloader too, I downloaded this file and Terminal Emulator and typed in everything, but it says "permission denied"
Click to expand...
Click to collapse
Well u need to install busy box first, and install the terminal emulator.
Download the 2.8.7.0 twrp IMG from here
http://forum.xda-developers.com/attachment.php?attachmentid=3385522&d=1435697303
Place the file in the root of the SD card and open the terminal emulator and run this command.
su
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Wait till whole process is over and then type
su
reboot recovery
That's all.
tra_dax
Hi, my G2 Mini's name is D620r, can I use this image anyway?
And what the heck is this busy box?
Euathlus1985 said:
Hi, my G2 Mini's name is D620r, can I use this image anyway?
And what the heck is this busy box?
Click to expand...
Click to collapse
U need to install busy box in order to run Linux commands. The IMG file will work on g2 mini's all variants. But if u want u can search and satisfy urself.
tra_dax
And wher do I have to type this whole stuff you wrote in busybox or this terminalemulator?
Euathlus1985 said:
And wher do I have to type this whole stuff you wrote in busybox or this terminalemulator?
Click to expand...
Click to collapse
In the terminal emulator.
tra_dax
Still not working, I installed the app busybox and also what the app wanted to install, I typed everything in terminal emulator like this
Code:
https://drive.google.com/file/d/0Bxuuoq6jYFMsUWxxUHRVZTItZkk/view?usp=sharing
After this I only typed reboot recovery, the smartphone restarts and ends in this pink screen, but before that is a black screen with a text "Error: Secure boot" or something like this.
Euathlus1985 said:
Still not working, I installed the app busybox and also what the app wanted to install, I typed everything in terminal emulator like this
Code:
https://drive.google.com/open?id=0Bxuuoq6jYFMsUWxxUHRVZTItZkk
After this I only typed reboot recovery, the smartphone restarts and ends in this pink screen, but before that is a black screen with a text "Error: Secure boot" or something like this.
Click to expand...
Click to collapse
I think so that's the bootloader, did u unlock it?
tra_dax
I thought this was to unlock the bootloader!?
EDIT: Here the picture
Code:
https://drive.google.com/file/d/0Bxuuoq6jYFMsUWxxUHRVZTItZkk/view?usp=sharing
Euathlus1985 said:
I thought this was to unlock the bootloader!?
EDIT: Here the picture
Code:
https://drive.google.com/file/d/0Bxuuoq6jYFMsUWxxUHRVZTItZkk/view?usp=sharing
Click to expand...
Click to collapse
Ok, to unlock the bootloader download the aboot.img from here:
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
And rename it as aboot4.img
And then open the terminal emulator and type this code:
su
dd if=/sdcard/aboot4.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
There's a video on YouTube about the whole process, I would suggest u to watch it before u perform it.
After bootloader is unlocked, use the first code that I gave u to flash the recovery accordingly.
If u find any difficult then quote me.
Best of luck??
tra_dax
Euathlus1985 said:
Hi, I found out that there are official cyan roms now and I wanted to test them. For root, I installed kingroot app. Then I used the app flashify for flashing newest TWRP (from this forum) on my device, and it also says it is done, but after reboot, i get a pink screen with some kind of ram dump text. I can restart into normal android from g2 mini, but I want to use marshmallow.
Click to expand...
Click to collapse
the same thing happened with me and in my case I had to take the technical assistance ... then I found out you have to go back to KITKAT STOCK rom because it accepts bootloader unlock by this method !! excuse my bad english
Related
Hey all,
i just found in amon_ra netherlands blog, that he released 1.8.0
Version 1.8.0
http://www.androidworld.nl/41059/amon-ra-maakt-nieuwe-aw-recovery-voor-nexus-one/
Reported Errors: NoNe
i alsou found 1.8.0.1 on alternate coding.
Version 1.8.0.1:
http://alternate-coding.com/recovery-RA-nexus-v1.8.0.1-aw.img
Reportet Errors: USB-MS Toggle possibly not working (has to be done twice)
Flash Instructions:
#download the file
#copy to android-sdk\tools (or the folder where your fastboot.exe is)
#connect your device in fastboot mode
#open cmd and navigate to android-sdk\tools
#check if device is present with
Code:
fastboot devices
#flash recovery with
Code:
fastboot flash recovery <filename>
Works fine here and does everything it is supposed to be.
As i dont speek netherlands, i dont know anything about the
release notes/changes....just wanted to let u all know
Changelog for 1.8.0:
#Completely ignore verification
#Added menu loop scrolling
Changelog for 1.8.1:
#supports SLCD AND AMOLED
Changelog:
Completely ignore verification
Added menu loop scrolling
Get Google Chrome man, auto translate
Changelog AW-recovery V1.8.0:
- Completely ignore verification (both unsigned and signed can you flash zips)
- Added course menu (to roll from bottom to top)
thanks will try it out!
Translation:
http://translate.google.com/transla...very-voor-nexus-one/&sl=nl&tl=en&hl=&ie=UTF-8
I just downloaded it and flashed it to recovery. All looks good and I like the new blue. Different. Went into recovery and did a Nandroid backup, seems to be working ok.
Thanks
xxxid dutch just me or is the download button soooo well hidden a normal person cannot see it
Ok found it IN THE TEXT in case I am not the only one who is confused here is the link
http://dl.dropbox.com/u/4548341/awrecovery.img
Thyrus said:
xxxid dutch just me or is the download button soooo well hidden a normal person cannot see it
Ok found it IN THE TEXT in case I am not the only one who is confused here is the link
http://dl.dropbox.com/u/4548341/awrecovery.img
Click to expand...
Click to collapse
Humurous because the article says: "This means that we rejoice with the latest version not yet available on XDA-Developers."
Haha...it's released now!
Flashed on Nexus One...
All works just FINE.
Thank you for the news.
techlogik said:
Humurous because the article says: "This means that we rejoice with the latest version not yet available on XDA-Developers."
Haha...it's released now!
Click to expand...
Click to collapse
thanks to tigger it is
sweeeeeeet....
this has been posted in Amon_Ra's thread for a couple days
http://forum.xda-developers.com/showpost.php?p=7912159&postcount=1124
Thyrus said:
thanks to tigger it is
Click to expand...
Click to collapse
Couldnt stand to let XDA wait ^^
Also i found this on alternate coding:
http://alternate-coding.com/recovery-RA-nexus-v1.8.0.1-aw.img
but didnt try yet! ^^
Downloaded and flashed... Works great! Thanks!
madj42 said:
Downloaded and flashed... Works great! Thanks!
Click to expand...
Click to collapse
dija flash 1.8.0.1 ?
RinTinTigger said:
Couldnt stand to let XDA wait ^^
Also i found this on alternate coding:
http://alternate-coding.com/recovery-RA-nexus-v1.8.0.1-aw.img
but didnt try yet! ^^
Click to expand...
Click to collapse
Wait a second, that first link is for v1.8.0
This is for 1.8.0.1???
Can someone verify the latest and validity and that their recovery actually shows 1.8.0.1 with the above link?
I already was a guinea pig for the 1.8.0 and verified..someone else's turn...haha
techlogik said:
Wait a second, that first link is for v1.8.0
This is for 1.8.0.1???
Click to expand...
Click to collapse
aye, i just recently found it in a german forums linkingf to alternative coding
RinTinTigger said:
aye, i just recently found it in a german forums linkingf to alternative coding
Click to expand...
Click to collapse
Ok, fine, let me nand backup and flash this one...here it goes...will report back momentarily.
EDIT:
Ok, I just flashed that second link, it shows the same version in RA recovery as the first link download I flashed.
Build : RA-nexus-v1.8.0
When he released 1.7.0.1, it shows that in the RA utility.
Just use the first link, it is an accurate description of the actual version form what I can tell. There doesn't appear to be a 1.8.0.1.
Just flashed v1.8.0...very nice and much easier to read! Love the blue vs. the red
i can't get my computer to recognize my device, so if i want to do it by terminal emulator i have to do this?.....
copy "awrecovery.img" to the root of my sd card
then go in to terminal emulator and type "su", and then type "recovery flash_image/SDcard/awrecovery.img"
and then type "reboot recovery" and then that should do it? or am i doing something wrong? i just want to be sure before i mess anything up......lol
su
flash_image recovery /sdcard/awrecovery.img
reboot recovery
i flashed few days back
SubyWill said:
i can't get my computer to recognize my device, so if i want to do it by terminal emulator i have to do this?.....
copy "awrecovery.img" to the root of my sd card
then go in to terminal emulator and type "su", and then type "recovery flash_image/SDcard/awrecovery.img"
and then type "reboot recovery" and then that should do it? or am i doing something wrong? i just want to be sure before i mess anything up......lol
Click to expand...
Click to collapse
Howdy all!
Did you install TWRP and then take the OTA, now you can't get your phone to boot normally, but you do see TWRP?
Here's the easy fix:
If you have ADB access, plug in your phone and run this:
Code:
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Then you should be able to successfully reboot your phone via the TWRP menu option, or via a simple reboot command in adb.
If you DONT have ADB access (because of an early build of TWRP), you can simply use TWRP's awesome "terminal command" option to run the following:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
You'll have to type that whole thing out, and be VERY careful with spaces and punctuation. One wrong letter and you could nuke your phone.
After that finishes, you can reboot and continue on your happy way!
Let me know if this helps anyone!
As usual, I'm on #lg-g2 in Freenode as IOMonster, if I'm around I'll be happy to help wherever I can.
Thank you! I'll update my guides now you made some folks very happy today.
Sent from my VS980 4G using Tapatalk 4
THANK YOU THANK YOU THANK YOU this worked perfectly using the method without adb. YES YES YES
jbreaz said:
THANK YOU THANK YOU THANK YOU this worked perfectly using the method without adb. YES YES YES
Click to expand...
Click to collapse
Phew, you were one of the guys I was worried about who were unlucky enough to be stuck in boot loop WITHOUT adb. Glad he got you working again!
WACOMalt said:
Phew, you were one of the guys I was worried about who were unlucky enough to be stuck in boot loop WITHOUT adb. Glad he got you working again!
Click to expand...
Click to collapse
I am too LOL Thanks for all your help
I had nothing to do with it, all thanks go to thecubed/IOMonster
Sent from my VS980 4G using Tapatalk 4
jbreaz said:
THANK YOU THANK YOU THANK YOU this worked perfectly using the method without adb. YES YES YES
Click to expand...
Click to collapse
Cool! :victory:
Glad to see you have yours working. I left mine at home today and brought the S4 instead so I'll fix my G2 tonight. Thanks for the help everyone!
jspradling7 said:
Cool! :victory:
Glad to see you have yours working. I left mine at home today and brought the S4 instead so I'll fix my G2 tonight. Thanks for the help everyone!
Click to expand...
Click to collapse
Yeah that's what I did yesterday as well used my s4 glad I didn't sell it yet
thecubed said:
Howdy all!
Did you install TWRP and then take the OTA, now you can't get your phone to boot normally, but you do see TWRP?
Here's the easy fix:
If you have ADB access, plug in your phone and run this:
Code:
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Then you should be able to successfully reboot your phone via the TWRP menu option, or via a simple reboot command in adb.
If you DONT have ADB access (because of an early build of TWRP), you can simply use TWRP's awesome "terminal command" option to run the following:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
You'll have to type that whole thing out, and be VERY careful with spaces and punctuation. One wrong letter and you could nuke your phone.
After that finishes, you can reboot and continue on your happy way!
Let me know if this helps anyone!
As usual, I'm on #lg-g2 in Freenode as IOMonster, if I'm around I'll be happy to help wherever I can.
Click to expand...
Click to collapse
I could swear I said just nuke the FOTA partition sometime yesterday as usual awesome job.
thecubed said:
Howdy all!
Did you install TWRP and then take the OTA, now you can't get your phone to boot normally, but you do see TWRP?
Here's the easy fix:
If you have ADB access, plug in your phone and run this:
Code:
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Then you should be able to successfully reboot your phone via the TWRP menu option, or via a simple reboot command in adb.
If you DONT have ADB access (because of an early build of TWRP), you can simply use TWRP's awesome "terminal command" option to run the following:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
You'll have to type that whole thing out, and be VERY careful with spaces and punctuation. One wrong letter and you could nuke your phone.
After that finishes, you can reboot and continue on your happy way!
Let me know if this helps anyone!
As usual, I'm on #lg-g2 in Freenode as IOMonster, if I'm around I'll be happy to help wherever I can.
Click to expand...
Click to collapse
Thank you!! Where do I send the beer money?
when i hit terminal command it goes to the folder browser is that supposed to happen? how do i bring up the terminal from here? my sideload isnt working like it did once earlier thats why im asking
Edit: My adb sideload def isnt working now if someone can clue me in on how to get to the terminal command in recovery im still seeing the folder browser after I touch the terminal button in recovery
---------- Post added at 09:45 AM ---------- Previous post was at 09:16 AM ----------
Walter21026 said:
when i hit terminal command it goes to the folder browser is that supposed to happen? how do i bring up the terminal from here? my sideload isnt working like it did once earlier thats why im asking
Edit: My adb sideload def isnt working now if someone can clue me in on how to get to the terminal command in recovery im still seeing the folder browser after I touch the terminal button in recovery
Click to expand...
Click to collapse
Nevermind I found it, not used terminal before in recovery, phone back up and running
jbreaz said:
THANK YOU THANK YOU THANK YOU this worked perfectly using the method without adb. YES YES YES
Click to expand...
Click to collapse
I was upset yesterday worrying about you guys. I am happy to see you happy. Thanks much OP for the fix.
I am rooted and installed TWRP recovery but reverted back to the stock recovery before accepting the VZW OTA update. I'm now stuck in a boot loop and I can't get ADB to recognize my device when plugged in via USB. When I plug in my phone it shows the following:
Fastboot mode started
udc_start()
-reset-
-portcharge-
-reset-
-portcharge-
fastboot: processing comands
Any idea why this is happening and how I can get my phone to boot normally?
Walter21026 said:
when i hit terminal command it goes to the folder browser is that supposed to happen? how do i bring up the terminal from here? my sideload isnt working like it did once earlier thats why im asking
Edit: My adb sideload def isnt working now if someone can clue me in on how to get to the terminal command in recovery im still seeing the folder browser after I touch the terminal button in recovery
---------- Post added at 09:45 AM ---------- Previous post was at 09:16 AM ----------
Nevermind I found it, not used terminal before in recovery, phone back up and running
Click to expand...
Click to collapse
I too get the file folder. How do i get the terminal command in TWRP?
synplex said:
I too get the file folder. How do i get the terminal command in TWRP?
Click to expand...
Click to collapse
When you see the file folder just ignore that and hit "select "on the bottom right and that will bring it up. Just type the command from there
Thanks it worked!:laugh: Should I flash stock now update via OTA then reroot and reflash TWRP??
synplex said:
Thanks it worked!:laugh: Should I flash stock now update via OTA then reroot and reflash TWRP??
Click to expand...
Click to collapse
I didn't. From what I've read its just best to flash the new TWRP and not worry about the new OTA. Besides there is nothing relevant about the OTA enough to worry about going through all the trouble of installing the OTA. Also the devs have pulled all the new update files and they will use those in their Roms
Walter21026 said:
I didn't. From what I've read its just best to flash the new TWRP and not worry about the new OTA. Besides there is nothing relevant about the OTA enough to worry about going through all the trouble of installing the OTA. Also the devs have pulled all the new update files and they will use those in their Roms
Click to expand...
Click to collapse
Yea, let's just wait for a ROM worth flashing and "F OTA"
How can we get the OTA if we have TWRP installed?
Can we falsh stock recovery and then accept the Update?
If so can someone please post the Stock Recovery IMG?
My phone is at the LG screen and the notification light is blinking but thats it. How can I adb anything or get into twrp?
I have a rooted mytouch 4g slide phone that seems to work fine but when I try to use certain apps that require root (for example "extended power menu") it doesn't work. here is a quick video to help explain my dilemma i bit further: http://www.youtube.com/watch?v=dYb8KiYHzC8
I can provide more information if needed and any help on this matter would be appreciated!
so does anybody have a Ideas on how to fix this?? or maybe at least any suggestions?? anything would help out right now...
pantherz said:
so does anybody have a Ideas on how to fix this?? or maybe at least any suggestions?? anything would help out right now...
Click to expand...
Click to collapse
Is busybox installed on it?
Sent from my LG-LS980 using xda app-developers app
Critical Detox said:
Is busybox installed on it?
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
no I have "superuser" installed. is "busybox" something that is recommended for rooted devices?1?
Im guessing this might be to difficult of a question for anyone to answer?? :_(
quick heads up on the subject, the phone was rooted by employees i payed behind closed doors. so I am unsure of the process involved in making the root. when the phone was given back to me i was told that the root was S-off. if there is another way to find out which one, please let me know.
Download the Terminal Emulator from Play and type the command "su".
If it gives you error, your phone is technically not rooted.
You can ask around in your phone's forum for information about rooting it yourself.
Erovia said:
Download the Terminal Emulator from Play and type the command "su".
If it gives you error, your phone is technically not rooted.
You can ask around in your phone's forum for information about rooting it yourself.
Click to expand...
Click to collapse
well I downloaded and installed Android Terminal Emulator from the play store. and then I typed "su" on the main screen. My phone asked to allow user permission as usual and then nothing happened. I typed in "su" twice to see if it was a fluke but nothing happened again. I didn't receive an error so I'm guessing my phone is rooted with s-off?!?
When you open the terminal, the prompt starts with "$" but after you type "su" it should start without "#".
Also, check if busybox is installed by typing "busyboy" into the terminal. If you got error, install it from play.
Erovia said:
When you open the terminal, the prompt starts with "$" but after you type "su" it should start without "#".
Also, check if busybox is installed by typing "busyboy" into the terminal. If you got error, install it from play.
Click to expand...
Click to collapse
ok so when you start the terminal it starts with "$" and after I typed in "su" and it started with "#" I can see that you said without "#" so im guessing thats a typo. I also dont have busybox installed because I already have superuser. I busybox considered to be more reliable than superuser???
Busybox is a lightweight package of linux applications. A lot of root app uses them.
Erovia said:
Busybox is a lightweight package of linux applications. A lot of root app uses them.
Click to expand...
Click to collapse
ok so I was able to enter the recovery mode by restarting my phone using the "press power and volume down button." The information displayed said this:
doubleshot pvt ship S-on RL
hboot-1.45.0013
microp-0353
eMMC-boot
Nov 21 2011
after seeing that it says "S-On" I'm guessing that this would be the issue on why the phone isn't responding to some of the apps that require root. even though the other phone was rooted the same way with the same information being displayed. any ideas on what my options are from this point?
I say you go to your phone's dedicated forum, here and in the Development section you can find guides about rooting your phone. Follow them and if you stuck, you can ask around there.
I definitely appreciate all the help you have offered. I will check the links you provided and see if there is a simple way to flash the rom again. thanks a bunch!!
Hi guys,
I'm new here and this is my first thread, so I hope I've chosen the correct section for my issue.
I have a sony ericsson xperia x10 mini pro and wanted to gain root access. I managed it so far and made some manipulations within the /system/ directory and due to some mental black-out I made a 'chmod 700 /system/' which now causes my device to fail on each boot. Also just connecting my phone with a computer gives the output of the white sony ericsson label followed by a rebooting, without showing the battary loading screen.
Using adb I have only a few seconds of access to the device and I wanted to change the rights of /system/ to some reasonable values. Unfortunately running 'adb shell' gives:
- exec '/system/bin/sh' failed: Permission denied (13) -
so I downloaded adb plus some other stuff following this description android.serverbox.ch/?p=1217. I replaced each and every occurance of /system/bin/sh to /bin/sh in order to call a different shell which I might have read access but still the same error as above occurs, also stating /system/bin/sh instead of /bin/sh.
Does somebody of you have an idea on how I can gain access and change the permissions or how I can completely reset the phone?
Thanks and cheers
I'm not familiar with Sony devices but most OEMS have some way of flashing stock firmware/software to the device such as with fastboot or a flash tool. If Sony has such method and has a package specific to your device this would probably be the best way.
Otherwise I assume you were rooted or you wouldn't have been able to change permissions to /system so can you boot to a custom recovery and then just flash a new ROM or fix permissions there
Sent from my Nexus 4 using XDA Premium 4 mobile app
blablubb32 said:
Hi guys,
I'm new here and this is my first thread, so I hope I've chosen the correct section for my issue.
I have a sony ericsson xperia x10 mini pro and wanted to gain root access. I managed it so far and made some manipulations within the /system/ directory and due to some mental black-out I made a 'chmod 700 /system/' which now causes my device to fail on each boot. Also just connecting my phone with a computer gives the output of the white sony ericsson label followed by a rebooting, without showing the battary loading screen.
Using adb I have only a few seconds of access to the device and I wanted to change the rights of /system/ to some reasonable values. Unfortunately running 'adb shell' gives:
- exec '/system/bin/sh' failed: Permission denied (13) -
so I downloaded adb plus some other stuff following this description android.serverbox.ch/?p=1217. I replaced each and every occurance of /system/bin/sh to /bin/sh in order to call a different shell which I might have read access but still the same error as above occurs, also stating /system/bin/sh instead of /bin/sh.
Does somebody of you have an idea on how I can gain access and change the permissions or how I can completely reset the phone?
Thanks and cheers
Click to expand...
Click to collapse
Go to the recovery then do a fix permissions in recovery. Or flash a new rom. Or use flash tools to install stock images again.
Sent from my Moto G
MasterAwesome said:
Go to the recovery then do a fix permissions in recovery. Or flash a new rom. Or use flash tools to install stock images again.
Click to expand...
Click to collapse
Thanks, but can you please give me a bit more details in what you mean by go to recovery?
Cheers,
blablubb32 said:
Thanks, but can you please give me a bit more details in what you mean by go to recovery?
Cheers,
Click to expand...
Click to collapse
Install a CWM recovery? Search about it
Sent from my Moto G
MasterAwesome said:
Install a CWM recovery? Search about it
Click to expand...
Click to collapse
I tried to, but my mobile can not be found by fastboot. Even if I make adb reboot bootloader.
blablubb32 said:
I tried to, but my mobile can not be found by fastboot. Even if I make adb reboot bootloader.
Click to expand...
Click to collapse
Thats nearly impossible.. Install your drivers.
Despite all this you can use flash tools to flash stock back again.
If you're using Linux type lsusb in the terminal and see if you see your device
Regards
MasterAwesome
Sent from my Moto G
blablubb32 said:
I tried to, but my mobile can not be found by fastboot. Even if I make adb reboot bootloader.
Click to expand...
Click to collapse
I would recommend checking out this guide, specially step 8-15 of this guide which will instruct you how to properly setup fastboot and the required drivers on your Sony device. Also I would recommend taking a look at this guide on how to boot your device into fastboot mode through the button combination. Let me know if you still have questions.
I tried to flash my mobile, using flash tool (from here: chip.de/downloads/Xperia-Flash-Tool_65533558.html) and now my mobile does not do anything anymore. So I guess this thread can be closed, except anyone has an idea what I can do now.
My son (1.5 years) somehow made a factory reset of my Xperia Z2, Android 6.01, D6503, 23.5.A.0.575.
All photos gone. No, they where not on the SD. No, not in any cloud service.
If I could get a dd of the partition, I might be able to use some linux-tools like scalpel off the phone for deep examination
Found this, but su is required: www dot nburles.co .uk
/android/recovering-data-from-an-android-device-using-dd
(Sorry for url-format First post, not allowed to paste outside links...)
I read hundreds of pages of rooting (but still don't get it) and i have no clue what it does to the internal memory, and I don't wan't to touch it too much as there might be some recoverable data left.
What is the minimum I really need to do?
I.e. I just need "su"!
I already have (on Windows) adb installed and unlocked bootloader using fastboot (with a code from Sony)
regards Martin/
martinwahlstrom said:
My son (1.5 years) somehow made a factory reset of my Xperia Z2, Android 6.01, D6503, 23.5.A.0.575.
All photos gone. No, they where not on the SD. No, not in any cloud service.
If I could get a dd of the partition, I might be able to use some linux-tools like scalpel off the phone for deep examination
Found this, but su is required: www dot nburles.co .uk
/android/recovering-data-from-an-android-device-using-dd
(Sorry for url-format First post, not allowed to paste outside links...)
I read hundreds of pages of rooting (but still don't get it) and i have no clue what it does to the internal memory, and I don't wan't to touch it too much as there might be some recoverable data left.
What is the minimum I really need to do?
I.e. I just need "su"!
I already have (on Windows) adb installed and unlocked bootloader using fastboot (with a code from Sony)
regards Martin/
Click to expand...
Click to collapse
You only have to flash a custom kernel
Ok, which one do you recommend? (Please don't tell I need to create one myself!)
And then just flash it with flashtool?
martinwahlstrom said:
Ok, which one do you recommend? (Please don't tell I need to create one myself!)
And then just flash it with flashtool?
Click to expand...
Click to collapse
Flash abricot kernel 8.1 via flashtool using fastboot mode or via adb
dylanel98 said:
Flash abricot kernel 8.1 via flashtool using fastboot mode or via adb
Click to expand...
Click to collapse
Ok, finally managed to flash the kernel.
Still no root access though... Now what?
(Thx so far anyway!)
martinwahlstrom said:
Ok, finally managed to flash the kernel.
Still no root access though... Now what?
(Thx so far anyway!)
Click to expand...
Click to collapse
Reboot the phone in recovery mode and flash superSU zip and your phone should be rooted
dylanel98 said:
Reboot the phone in recovery mode and flash superSU zip and your phone should be rooted
Click to expand...
Click to collapse
Done - but does not work!
SuperSU app tells me no su is found.
Using adb, su exists but have no apparent effect.
Permission denied when trying a simple "ls -l" of various dir's.
martinwahlstrom said:
Done - but does not work!
SuperSU app tells me no su is found.
Using adb, su exists but have no apparent effect.
Permission denied when trying a simple "ls -l" of various dir's.
Click to expand...
Click to collapse
Btw, installed Update-SuperSU-v2.02.zip from SD using TWRP.
Great... Now in bootloop... Help!
Edit: Recovered from looping.
Still no root after several tries.