Greetings, this is my first post on the forum.
Sadly, I tried to backup my M8s to do a factory reset it and I forgot to save some audio recordings.
I tried to root to install some kind of file recovery but it didn't work out.
I am on android 6.0.1
HBOOT 3.19.0.0000
OS-2.21.401.1
First, I unlocked the bootloader , using HTC Dev, then I tried to flash a custom recovery from voidzero(can't post the link due to being a new user)
It didn't work out saying :
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 7751680 is not a multiple of the block size 4096
Sending sparse 'recovery' 1/2 (15368 KB) error: write_sparse_skip_chunk: don't care size 7751680 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 7751680 is not a multiple of the block size 4096
OKAY [ 1.610s]
Writing sparse 'recovery' 1/2 FAILED (remote: 'image error! (BootMagic check fail)')
Finished. Total time: 1.844s
Then I tried to flash an older recovery from TWRP witch told me it was a success but when I try to enter recovery mode it says entering recovery for a split second and took me to fastboot once again. I am officially out of ideas and I didn't want to post anything before I don't "do my homework".
Thank you all in advance . I have learned a lot in the past week about my phone but not enough.
BigTree22 said:
Greetings, this is my first post on the forum.
Sadly, I tried to backup my M8s to do a factory reset it and I forgot to save some audio recordings.
I tried to root to install some kind of file recovery but it didn't work out.
I am on android 6.0.1
HBOOT 3.19.0.0000
OS-2.21.401.1
First, I unlocked the bootloader , using HTC Dev, then I tried to flash a custom recovery from voidzero(can't post the link due to being a new user)
It didn't work out saying :
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 7751680 is not a multiple of the block size 4096
Sending sparse 'recovery' 1/2 (15368 KB) error: write_sparse_skip_chunk: don't care size 7751680 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 7751680 is not a multiple of the block size 4096
OKAY [ 1.610s]
Writing sparse 'recovery' 1/2 FAILED (remote: 'image error! (BootMagic check fail)')
Finished. Total time: 1.844s
Then I tried to flash an older recovery from TWRP witch told me it was a success but when I try to enter recovery mode it says entering recovery for a split second and took me to fastboot once again. I am officially out of ideas and I didn't want to post anything before I don't "do my homework".
Thank you all in advance . I have learned a lot in the past week about my phone but not enough.
Click to expand...
Click to collapse
It is not a very good phone to root. I am popping in on this forum which I haven't used in almost a year...
I have had mine rooted for a long time. The phone is the only phunction that I use this phone for. That and the occasional porno search.
The phone resets its friggin permissions all the friggin time and displays a notification that its permissions for gallery require to be set to allow storage permission.
This can also be accompanied by a total settings wipe on occasion. That means that ALL settings get destroyed, such as network mode and location on/off.
This is usually also accompanied by disappearance of widgets, I have found.
All in all the phone has been decent as a phone-only, but really a PITA for any other use. I use my more modern larger phone for internet and other functions now.
It requires the obligatory visit to htcdev to be rooted. But I'm sure you know that.
Biggest thing is though, this phone is like pumping iron you will be a much stronger android user than the brainless masses who never heard of the apps tab in settings. Perhaps you'll even learn to clear your caches like dirty dishes after every use on social networking sites.
kruc Ire said:
It is not a very good phone to root. I am popping in on this forum which I haven't used in almost a year...
I have had mine rooted for a long time. The phone is the only phunction that I use this phone for. That and the occasional porno search.
The phone resets its friggin permissions all the friggin time and displays a notification that its permissions for gallery require to be set to allow storage permission.
This can also be accompanied by a total settings wipe on occasion. That means that ALL settings get destroyed, such as network mode and location on/off.
This is usually also accompanied by disappearance of widgets, I have found.
All in all the phone has been decent as a phone-only, but really a PITA for any other use. I use my more modern larger phone for internet and other functions now.
It requires the obligatory visit to htcdev to be rooted. But I'm sure you know that.
Biggest thing is though, this phone is like pumping iron you will be a much stronger android user than the brainless masses who never heard of the apps tab in settings. Perhaps you'll even learn to clear your caches like dirty dishes after every use on social networking sites.
Click to expand...
Click to collapse
Sorry I didn't answer earlier. I was away for a few days. The thing is, it's not that important, just wanted to have a little fun trying to root the phone, as I have never done this before.
This phone is not my primary phone so no big deal.
I unlocked the bootloader from HTC Dev but installing a TWRP said it worked and now, when I enter recovery....it just takes me back to fastboot menu, which is a bit weird and I'm stuck at this stage.
Has this happened to you before? because I searched for a bit and didn't find something like this.
BigTree22 said:
Sorry I didn't answer earlier. I was away for a few days. The thing is, it's not that important, just wanted to have a little fun trying to root the phone, as I have never done this before.
This phone is not my primary phone so no big deal.
I unlocked the bootloader from HTC Dev but installing a TWRP said it worked and now, when I enter recovery....it just takes me back to fastboot menu, which is a bit weird and I'm stuck at this stage.
Has this happened to you before? because I searched for a bit and didn't find something like this.
Click to expand...
Click to collapse
I use one of the TWRPs from this board
if you flashed one and it doesn't work, I suggest to flash the other
of course by now maybe there's a third or more recovery here. My TWRP works. My M8s is red and pretty reliable. I keep the stock system but use a few apps that use root. However like I said I only ever use the phone as a phone anymore. Or to look at Twitter.
kruc Ire said:
I use one of the TWRPs from this board
if you flashed one and it doesn't work, I suggest to flash the other
of course by now maybe there's a third or more recovery here. My TWRP works. My M8s is red and pretty reliable. I keep the stock system but use a few apps that use root. However like I said I only ever use the phone as a phone anymore. Or to look at Twitter.
Click to expand...
Click to collapse
Could you link me the exact recovery or tell me the version ? I have tried many of them,of course, from the other threads. and they didn't work.
The ones I tried are 2.8.6.0 | 2.8.7.1 | 3.2.1.0 | 3.2.3.0
You have not tried the recovery I use
it is 3.0.2.0
---------- Post added at 08:18 PM ---------- Previous post was at 08:06 PM ----------
Here is (a copy of a quote of) a/the xda post which contains a/the 3.0.2-0 twrp maybe it comes from:. You can additionally search the internet for "htc m8s" twrp 3.0.2-0
Note*
I remember now that I did have troubles with other twrps on the phone because they were a bad size. But this one (or the one I have) seems to work well:
burleanu said:
RUU for your phone is not present on ruu.lalleman.net.
Your need to find right RUU for your phone or wait for right OTA update for your phone made by H3G.
It is possible to change CID and flash whatever RUU. However, you need to be S-OFF and you loose customization of H3G ROM and warranty of course.
---------- Post added at 10:31 PM ---------- Previous post was at 09:48 PM ----------
@WildfireDEV, @El-Conkistador: Any idea why booting TWRP (twrp-2.8.7.0-m8s-qlul.img) restarts my phone and it doesn't boot it after upgrading to Android 6.0?
You can try to see if the last recovery from @Captain_Throwback works on android 6.0.
https://basketbuild.com/filedl/devs...back/One (M8S)/Recovery/twrp-3.0.2-0-m8ql.img (3.0.2.1 is not working)
This one works on 5.0, don't know if on 6 works.
Also maybe you need to use htc_fastboot instead of the fastboot.
To flash the img file for sure, don't know if just to boot tho.
Also locked or unlocked bootloader? I imagine locked if you could upgrade. Take care if you unlock it you will have to factory reset, is doing that when you unlock. Make at least a back-up on HTC servers if not other back-up
If you can boot it up please make a back-up of system and boot image and put it somewhere available.
Respect!
Click to expand...
Click to collapse
BigTree22 said:
Could you link me the exact recovery or tell me the version ? I have tried many of them,of course, from the other threads. and they didn't work.
The ones I tried are 2.8.6.0 | 2.8.7.1 | 3.2.1.0 | 3.2.3.0
Click to expand...
Click to collapse
How did it go? I am writing this cause you probably didnt get notified when I didn't quote you in that last comment.
kruc Ire said:
How did it go? I am writing this cause you probably didnt get notified when I didn't quote you in that last comment.
Click to expand...
Click to collapse
Oooh...you are right, I didn't get notified. I will try it in a couple of hours and post my answer, right now I have a bit of work to do. Thank you so much !
I have the same problem, TWRP 2..5.0.0 and the newest will not stick on my HTC OneM8s.
Curious if you get the problem solved
Oooh, boy, been a mad week for me.
Aside from a ton of work to do (I'm in senior high school and have a lot to do) , 5 days ago I dropped my primary phone (the primary one, a HTC M8) on the floor and it won't boot .
And now I'm left with the M8s as my daily driver and to be honest, I am a bit afraid to try to root it anymore because if this fails, I won't have another phone to go back to.
I opened the m8 up to see if maybe a cable was disconnected, but didn't find anything, I might send it to a repair shop in the near future(or tear it down completely to further inspect it).
As for the recovery, I won't try installing it anymore until I get another phone in the near future.
Sorry for taking so long to provide an update. If I decide to try to root it again I will post here about it, on this thread.
I can understand your ideaś.
I had contact with HTC and they gave me a link for a chat-session with one of their develloppers. But I first have to find out what time they are availablen nextr week and if I hear something useful I will post it here.
Thanx and have a nice weekend.
Related
Does anyone have a nandroid for stock 4.0.2? I've searched the forums but have not come up with anything.
I know what you're thinking =). So before you say anything, no, sorry, due to technical issues the factory image fastboot is not working for me.
and why isn't factory image fastboot working for you?
From what I have read it is not good to restore someone else's nandroid, I imagine it could be even worse for the person providing it to you because it could possibly contain their personal information.
WiredPirate said:
From what I have read it is not good to restore someone else's nandroid, I imagine it could be even worse for the person providing it to you because it could possibly contain their personal information.
Click to expand...
Click to collapse
Some people actually do upload nandroid backups though.... they are purely stock without any information on them. It'd be silly if anyone uploaded their nandroid with all apps/data on it.
I'd say try the mobile odin route if fastboot isn't working
waylo said:
Does anyone have a nandroid for stock 4.0.2? I've searched the forums but have not come up with anything.
I know what you're thinking =). So before you say anything, no, sorry, due to technical issues the factory image fastboot is not working for me.
Click to expand...
Click to collapse
What are the "technical issues" that are affecting your ability to flash the stock 4.0.2 ROM?
And what build are you looking for? Yakju? Yakjuux?
Sent from my Galaxy Nexus using Tapatalk
Why can't you use fastboot? i'd say it's one of the safest ways to get back to 4.0.2.
just follow the guide from http://forum.xda-developers.com/showthread.php?t=1391881 but use an android 4.0.2 image http://code.google.com/android/nexus/images.html
you could try to use ODIN but I actually use Fastboot all the time on my GN.
my milestone has a custom recovery (comparable to ClockworkMOD) and I recently installed some ROMS on Galaxy S's and a Samsung Ace using CM. try to find an "update" to older stock version on that... but please do remember that MD5 codes will not work if you transport a Nandroid from one phone to the other and your'e phone will be screwed up since it's service numbers changes and becomes a duplicate of another registered phone on the network.
It looks like my mobo is dying/failing. Or internal memory. Regardless, something is very very amiss.
See:
http://forum.xda-developers.com/showthread.php?t=1589807
Given the horrendous symptoms the phone has just in recovery, it can't be a ROM issue.
I remember nandroid backups of pure stock with no personal info being more common for other phones, probably because the factory images were not available as they are for the Nexii.
With fastboot, the recovery can be written okay, but the actual ROM data errors out "too many links".
@efrant, either build would be fine. Mine originally came with the "non-google" build whichever that was, but I flashed it over quite quickly.
Of course, getting it onto the /sdcard is another issue. ADB isn't playing very nice either.
amonfog said:
Why can't you use fastboot? i'd say it's one of the safest ways to get back to 4.0.2.
just follow the guide from http://forum.xda-developers.com/showthread.php?t=1391881 but use an android 4.0.2 image http://code.google.com/android/nexus/images.html
you could try to use ODIN but I actually use Fastboot all the time on my GN.
my milestone has a custom recovery (comparable to ClockworkMOD) and I recently installed some ROMS on Galaxy S's and a Samsung Ace using CM. try to find an "update" to older stock version on that... but please do remember that MD5 codes will not work if you transport a Nandroid from one phone to the other and your'e phone will be screwed up since it's service numbers changes and becomes a duplicate of another registered phone on the network.
Click to expand...
Click to collapse
No, restoring someone else's nandroid will not make your phone a clone of the nandroid phone. /factory is not duplicated with nandroid.
The md5 is just of the tar files. With other recoveries (Amon-Ra's for instance) on other phones, there was a lot more altering needed, but it could be done.
waylo said:
It looks like my mobo is dying/failing. Or internal memory. Regardless, something is very very amiss.
See:
http://forum.xda-developers.com/showthread.php?t=1589807
Given the horrendous symptoms the phone has just in recovery, it can't be a ROM issue.
I remember nandroid backups of pure stock with no personal info being more common for other phones, probably because the factory images were not available as they are for the Nexii.
With fastboot, the recovery can be written okay, but the actual ROM data errors out "too many links".
@efrant, either build would be fine. Mine originally came with the "non-google" build whichever that was, but I flashed it over quite quickly.
Of course, getting it onto the /sdcard is another issue. ADB isn't playing very nice either.
Click to expand...
Click to collapse
I personally would try this first, and then do this.
Otherwise, here is your nandroid backup.
Just a question, what's the purpose of the 30 min wait after the final reboot, in the first posted instruction?
waylo said:
Just a question, what's the purpose of the 30 min wait after the final reboot, in the first post?
Click to expand...
Click to collapse
I exagerated a bit there. You shouldn't have to wait 30 mins. It should be more like 5-6 mins, but some people think that the device is not booting properly after waiting a few mins so they pull the battery, so I said wait 30 mins...
By the way, I re-read the first post, and the instructions include what I had linked to in the second link, so ignore that.
WOW
That's some research you did. My search around the internet came up with the same.
sorry guys for that post with clones... my misstake
to re-alocate your MD5 number you can use the following code from the terminal of your ClockworkMod (if you are using that)
Code:
cd /sdcard/clockworkmod/backup/"foldername"
rm nandroid.md5
md5sum *img > nandroid.md5
if you are able to connect to the device using adb use the following string in your command promt
Code:
adb shell
cd /sdcard/clockworkmod/backup/"foldername"
rm nandroid.md5
md5sum *img > nandroid.md5
If nothing works try using another os to get your phone running again. Linux and Mac OS X don't need drivers... so that would be knocking the possibility of driver problems on your computer or your phone.
if nothing works you could try uninstalling the drivers in windows (completely) and restarting your computer. an "android 1.0 device" should pop up in your device manager (after you rebooted your phone to fastboot). but that is a last hope
Thanks for the last ditch hope. I'm guessing there's no harm in trying all this again, it really can't be MORE broken.
amonfog said:
That's some research you did. My search around the internet came up with the same.
sorry guys for that post with clones... my misstake
to re-alocate your MD5 number you can use the following code from the terminal of your ClockworkMod (if you are using that)
Click to expand...
Click to collapse
I apologize if it seemed like I was not appreciating your help. Every thought is appreciated!
On a related note, on the Amon-ra series of recoveries, each backup was saved in a folder which was = the serial #. As I recall (it's been a while since I had my Nexus One) if the whole folder was copied over to another phone, it wouldn't work. The backup would have to be copied into that phone's serial # folder.
waylo said:
Thanks for the last ditch hope. I'm guessing there's no harm in trying all this again, it really can't be MORE broken.
Click to expand...
Click to collapse
Good luck, and let us know how it goes!
Yeah, so this isn't going to work:
F:\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s
F:\android-sdk\platform-tools>fastboot flash boot 402boot.img
sending 'boot' (4074 KB)...
OKAY [ 0.407s]
writing 'boot'...
OKAY [ 0.249s]
finished. total time: 0.656s
F:\android-sdk\platform-tools>fastboot flash system 402system.img
sending 'system' (317594 KB)...
OKAY [ 31.187s]
writing 'system'...
FAILED (status read failed (Too many links))
finished. total time: 56.860s
Same error occurs with the attempt to flash userdata.img.
So I'm thinking for some reason it's unable to write either system or userdata info. Which supports my theory that the hardware is done broken.
Similarly, recovery is forced to reboot when it tries to restore large files and also when it tries to save a new nandroid.
waylo said:
Yeah, so this isn't going to work:
F:\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s
F:\android-sdk\platform-tools>fastboot flash boot 402boot.img
sending 'boot' (4074 KB)...
OKAY [ 0.407s]
writing 'boot'...
OKAY [ 0.249s]
finished. total time: 0.656s
F:\android-sdk\platform-tools>fastboot flash system 402system.img
sending 'system' (317594 KB)...
OKAY [ 31.187s]
writing 'system'...
FAILED (status read failed (Too many links))
finished. total time: 56.860s
Same error occurs with the attempt to flash userdata.img.
So I'm thinking for some reason it's unable to write either system or userdata info. Which supports my theory that the hardware is done broken.
Similarly, recovery is forced to reboot when it tries to restore large files and also when it tries to save a new nandroid.
Click to expand...
Click to collapse
The only other suggestions I have for you are as follows:
1) Uninstall your current fastboot driver, and install this one.
2) Reboot your PC and your device.
3) Change USB cables. Use the one that came with the device, or one that came with a Blackberry, or another high-quality one.
4) Download the attachment and use the fastboot.exe file from that.
5) Try flashing the stock images again.
I believe that error has something to do with a connection problem -- either driver related, or cable related, or, in the worst case, hardware related.
Man, stop giving me hope! =)
It was all snuggled up in the original box, waiting for the RMA to come through.
Okay, one more night of fiddling. I'll install all the new drivers on my rarely used laptop and use the usb cable (same one that came with the phone) plugged directly in.
waylo said:
Man, stop giving me hope! =)
It was all snuggled up in the original box, waiting for the RMA to come through.
Okay, one more night of fiddling. I'll install all the new drivers on my rarely used laptop and use the usb cable (same one that came with the phone) plugged directly in.
Click to expand...
Click to collapse
P.S., the attachment in my last post probably won't download for you (it seems like XDA is having problems with attachments site-wide. Try and get a recent copy of fastboot.exe, just in case there are any incompatibilities with the older versions (I know there was a difference in the adb.exe files between newer and older revisions). If you can't find it anywhere (maybe look in the Toolkit thread), you can download it from the Android SDK, or pm me and I'll see if I can upload it somewhere else.
I understand it is currently not possible to unlock a Razr M with 98.18.94 or 98.30.1 OTA. Never the less, I had been trying to restore a previous VooDoo root that I deleted before the last OTA. Through the experimenting, I screwed up the flash on my phone, and recovering it, I found something that might be interesting.
As others pointed out, downgrading does not work. Flashboot gives various errors. When I screwed up my file system, I was able to flash from 98.18.94 (which I had) to 98.30.1 (which was the only download I could find) using RSD Lite. I was lucky it worked. And since I have been able to experiment and keep flashing 98.30.1 over and over.
I would like to report that in my experiments, I noticed an interesting fact about the recovery.img:
I am able to flash stock 98.18.78 recovery to my phone running 98.30.1.
I have verified the recovery.img contents are not the same, according to a WinMerge file compare, they are ~10% the same
When I try to flash twrp or cwm recovery, the only fastboot error is to the effect "wrong partition size".
The size of .78 and 98.30.1 recovery are the same, 10,485,760 bytes
On the other hand, if I try to flash the .78 system.img fastboot, or use RSD lite to flash .78, I see different security related errors on the phone's fastboot screen- none of which mention partition size. Of course, this is related to the Locked Bootloader I have.
What I wonder is, since the error for the recovery.img is not a security related one, but one of size, and the fact that it took recovery from .78- I wonder if a cwm or twrp made to be the same size as stock Moto recovery, would it be able to sneak in?
Right now my Razr M has gone from 98.18.94 to 98.30.1 with a 98.18.78 recovery. And I'm working ok.
I am not a professional Android Dev. But I am going to do the research and try to modify a cwm type recovery to match the size of a Moto recovery, and see what happens.
I invite anyone with real experience to contribute.
Bryan
bryanwieg said:
What did you say?
Click to expand...
Click to collapse
Well I hope you have something here!
We need someone like jbaumert or Phil3759 to chime in here.
aviwdoowks said:
Well I hope you have something here!
We need someone like jbaumert or Phil3759 to chime in here.
Click to expand...
Click to collapse
I have already found that if I take the OTA recovery and unpackbootimg and then mkbootimg without changing anything.. it recompiles down to aprox 5mb, which is different than the size it started from Moto.
So I am looking at if the size is set in how the img is compiled.
30.1 and .94 are the same updates, just different system versions. As for the other stuff, I'm not even sure what to say. I'm with Avi on this, I definitely would like to see what a dev has to say.
New Philz coming BTW.
http://forum.xda-developers.com/showpost.php?p=48881182&postcount=2003
Others could ask for the padded up Philz or at least Quote my post.
http://forum.xda-developers.com/showpost.php?p=48886733&postcount=2004
aviwdoowks said:
New Philz coming BTW.
http://forum.xda-developers.com/showpost.php?p=48881182&postcount=2003
Others could ask for the padded up Philz or at least Quote my post.
http://forum.xda-developers.com/showpost.php?p=48886733&postcount=2004
Click to expand...
Click to collapse
I found out via a hex editor, both files have empty data insert after the same point, with certificate data at the end, and it winds up making each file the same size. The data before the 'empty data' in each file is mostly different bits.
My current problem is that when I decompile an img, and recompile it, it's bigger, meaning that I cannot insert the 'empty data' at the same point they did.
bryanwieg said:
I found out via a hex editor, both files have empty data insert after the same point, with certificate data at the end, and it winds up making each file the same size. The data before the 'empty data' in each file is mostly different bits.
My current problem is that when I decompile an img, and recompile it, it's bigger, meaning that I cannot insert the 'empty data' at the same point they did.
Click to expand...
Click to collapse
They are both signed with the 128, or more, bit code. Which is what makes this a such a Loooooong shot.
aviwdoowks said:
They are both signed with the 128, or more, bit code. Which is what makes this a such a Loooooong shot.
Click to expand...
Click to collapse
Well, you'r right on the money. I appended data to a CWM recovery the same as Moto did to thiers, including the certificate at the end.
I didn't get a partition size error this time, but I did get a 'Failed to hab check for recovery'.
Granted, I didn't manage to place the 'empty data' at the same point in the file as the stock roms did. Other than that, it must be the certificate.
bryanwieg said:
What I wonder is, since the error for the recovery.img is not a security related one, but one of size, and the fact that it took recovery from .78- I wonder if a cwm or twrp made to be the same size as stock Moto recovery, would it be able to sneak in?
Click to expand...
Click to collapse
No, because it first checks the size (or whether it's a valid image at all) and if the size is correct, it checks the signature.
I found that I can put recovery all the way back to 98.15.66. I haven't tried further back due to kernel version.
I tried to then apply an update ZIP to something pre 98.30.1, and it passed validation (woohoo), but if failed an assert that checked the version in the props. (cry)
I wish there was something in the older recoveies we could exploit.
Really glad to see someone is still trying to find some sort of exploit for this device in it's updated state, it seemed like everyone had completely given up on it. My girlfriend recently grabbed a used Razr M to use for a while but it's fully updated, and I would love to be able to root it for her. I'll be following this thread to see if anything comes of this recovery downgrading
I'm pretty sure you can edit the props from what I can remember.
Sent from my XT907 using xda app-developers app
bryanwieg said:
I found that I can put recovery all the way back to 98.15.66. I haven't tried further back due to kernel version.
I tried to then apply an update ZIP to something pre 98.30.1, and it passed validation (woohoo), but if failed an assert that checked the version in the props. (cry)
I wish there was something in the older recoveies we could exploit.
Click to expand...
Click to collapse
You can use root eplorer free to extract the single img from the 404 or 411 xml.zips
---------- Post added at 10:44 AM ---------- Previous post was at 10:39 AM ----------
Here http://sbf.droid-developers.org/phone.php?device=8
---------- Post added at 10:48 AM ---------- Previous post was at 10:44 AM ----------
The razr hd (2), atrix hd, photon Q all use a recovery w/ same key. Git to work man!
Re:
So, it is RSD that is keeping it from flashing, would the bootloader(locked) boot a recovery partition that isn't signed? Has anybody tried to dd the recovery partition? I will grab a TWRP dd recovery image if you guys have an interest in trying that.
It would still require root and either a terminal emulator or adb shell.
815turbo said:
So, it is RSD that is keeping it from flashing, would the bootloader(locked) boot a recovery partition that isn't signed? Has anybody tried to dd the recovery partition? I will grab a TWRP dd recovery image if you guys have an interest in trying that.
It would still require root and either a terminal emulator or adb shell.
Click to expand...
Click to collapse
Am I alone here now?
Does anyone with a locked boot loader want to try this? I could create a windows shell script to make it easier if that's the worry.
I am willing to try it out. Win 7 64bit... pass me needed staf to flash it
Sent from my XT907 using xda app-developers app
please do
815turbo said:
Am I alone here now?
Does anyone with a locked boot loader want to try this? I could create a windows shell script to make it easier if that's the worry.
Click to expand...
Click to collapse
sure do, i'm on win8, but also had win xp, how can i do it? what to download, what to execute? i can adb shell i think. i've survived from bricked before the screen said "flash failure".
benya274 said:
sure do, i'm on win8, but also had win xp, how can i do it? what to download, what to execute? i can adb shell i think. i've survived from bricked before the screen said "flash failure".
Click to expand...
Click to collapse
I'll post it in just a few minutes. I will also post the required commands and we'll be backing up current recovery. If it fails, it should be no problem to restore your backed up recovery.
Download TWRP image on your phone from: titanroms.com/upload/rec.img
Please get to an adb prompt and run these commands:
su
cd /sdcard
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/recbak1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/recbak2.img
Please ensure that both copies are 10MB. The dd command should end by saying "10485760 Bytes Copied" on all of the "dd" commands.
Now, you should have two backups of the recovery partition and the TWRP Image you downloaded from here all on your sdcard.
You can follow with these commands AFTER your backup has completed.
cp /sdcard/Download/rec.img /sdcard/rec.img
dd if=/sdcard/rec.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=twrprecbak.img
mount -o remount,rw /system
mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak
mv /system/recovery-from-boot.p /system/recovery-from-boot.bak
reboot recovery
In the event of a failed attempt at this you can run the following from adb:
su
cd /sdcard/
dd if=/sdcard/recbak1.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Give me a holler if you don't understand this well. Good luck, guys.
I am gonna try it out tomorrow,i dont have time to do it tonight cause i need to go to work. My pc on work does not have internet connection I will keep u guys posted on any progress.
Sent from my XT907 using xda app-developers app
Just wanted to say I flashed the old ICS recovery to mine using fastboot commands but it didn't get me very far though.if I then try and flash the corresponding blur zip from recovery it just says invalid signature. Was trying to find a way to downgrade so I could get rooted..
Sent from my XT907 using Tapatalk
Hi guys im unsure if you would call me a noob since ive been playing with androids and custom ops for a while, however my girlfriend purchased an lg d855 (stock as a rock)and "all of a sudden" it failed to reboot, now from what i have found it appears to be quite unusual for this to happen but common for the os to crash into a boot freeze or boot loop, i have no complete load of download mode, it comes up with the little blue dots and the picture of the phone or whatever the symbol is. i can get it into fastboot for use with the adb or fastboot apps, i have obtained the stock LAF.img for the 32gb variant, the issue is that after the phone is connected and ready to send operations
i send the command
c:\adb\fastboot erase recovery >
erasing recovery>
FAILED <remote: failed to erase partition>
and on the phone it says
<start>
fastboot: processing commands
fastboot: getvarartition-type: recovery
fastboot erase: recovery
partition getsize 16777216 bytes
erasing card: 0x48000:0x8000
error: command never completed
error: command timeout error
error: command completed with errors
failed to send erase grp start address
mmc erase failed
<end>
so the question, what the hell does that mean, also if i try other commands it also failes to complete them such as erasing the laf file and or replacing it, i feel like i am mostlikely not the only one with this issue, i do have all the correct drivers installed, using the adb that i have which is 1.3 and one that comes with a kit of the sdk tools and all that, i feel like it is a phone issue more than computer as its failing to erase the mmc, i am wondering if there is other commands i could put in the phone to figure this out or if anyone knows what it all means i would greatly appreciate any help Thanks guys an gals.
iv tried also to load a custom recovery but cant do that because it comes up with incomplete bootloader on the phone, is anyone even able to help? i have no idea what the hell i am doing and nobody seems interested to try and help me.
Same problem here
I'm in the same situation as you did you manage to erase the recovery or something else in order to put your smartphone to work? thkx
ferreirix said:
I'm in the same situation as you did you manage to erase the recovery or something else in order to put your smartphone to work? thkx
Click to expand...
Click to collapse
Can I give you a bit of friendly advice firstly if you look at this thread you resurrected it is dated about a year ago and also if you look at the person who posted his last post anywhere on Xda was over a year ago ( you can find this out by clicking on is name/profile and view forum posts).
Now my point is resurrecting this very old post and and asking a question to the person who posted it along time ago is not likely going to get you a answer from him.You probably need to find newer up to date posts or answers by doing a more in depth search.
Saying all that here is a little info that may help you it is a slightly different solution but may help you >> http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359 << this is a more up to date thread and if you post your question there with as much detail as possible about your problem and anything you have done to fix it then you may solve your problem.
If you choose to try the advice given in that thread don't forget to use a tot file for your particulate model and not the one posted in the thread.
Good luck with your problem.
tallman43 said:
Can I give you a bit of friendly advice firstly if you look at this thread you resurrected it is dated about a year ago and also if you look at the person who posted his last post anywhere on Xda was over a year ago ( you can find this out by clicking on is name/profile and view forum posts).
Now my point is resurrecting this very old post and and asking a question to the person who posted it along time ago is not likely going to get you a answer from him.You probably need to find newer up to date posts or answers by doing a more in depth search.
Saying all that here is a little info that may help you it is a slightly different solution but may help you >> http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359 << this is a more up to date thread and if you post your question there with as much detail as possible about your problem and anything you have done to fix it then you may solve your problem.
If you choose to try the advice given in that thread don't forget to use a tot file for your particulate model and not the one posted in the thread.
Good luck with your problem.
Click to expand...
Click to collapse
I can start to see the light with the tuto you recommended thank you so much !
Greetings!
First of all, I am sorry if this is on the wrong section of the forum. Nevertheless i've tried few rooting applications which are stated to be compatible with this ME103K model, but with no results.. Also many fake sites trying to lure you to purchase something.
Is there anyone who could provide me information on how to root my ASUS ME103K tablet? Should I also try every rooting application available out there or is this useless? Can I verify if they are compatible without all the way installing and running them on the device? (Sorry don't know much about this stuff =)! )
Thank you very much in advance
I rooted ME103K on my own - by compiling a custom kernel
Executive summary: Go to youtube and watch video with ID "gqubgQjqfHw" (I can't post links yet, sorry! ) - or search Youtube for "Rooting MemoPAD10 (ME103K) with my custom compiled kernel"
Analysis:
I hated the fact that my recently purchased MemoPAD10 (ME103K) tablet had no open process to allow me to become root. I don't trust the closed-source one-click root apps that use various exploits, and require communicating with servers in.... China. Why would they need to do that? I wonder...
I therefore decided this was a good opportunity for me to study the relevant documentation and follow the steps necessary to build an Android kernel for my tablet. I then packaged my custom-compiled kernel into my custom boot image, and the video shows how I boot from it and become root in the process.
Note that I didn't burn anything in my tablet - it's a 'tethered' root, it has no side-effects.
If you are a developer, you can read in detail about the steps I had to take to modify the kernel (and su.c) and become root - by reading the questions (and answers!) that I posted in the Android StackExchange forum ( can't post links yet, see the video description in Youtube ).
If you are not a developer, you can download my custom boot image from the link below - but note that this means you are trusting me to not do evil things to your tablet as my kernel boots and my /sbin/su is run
Honestly, I haven't done anything weird - I just wanted to run a debootstrapped Debian in my tablet, and succeeded in doing so. But I am also worried about the cavalier attitude I see on the web about rooting your devices - if you want to be truly safe, you must either do what I did (and recompile the kernel yourself) or absolutely trust the person that gives it to you. I do wish Google had forced a UI-accessible "become root" option in Android, just as Cyanogen does (sigh).
The image I created and used in the video to boot in rooted mode, is available from the link show in the Youtube video details.
Enjoy!
ttsiodras said:
Executive summary: Go to youtube and watch video with ID "gqubgQjqfHw" (I can't post links yet, sorry! ) - or search Youtube for "Rooting MemoPAD10 (ME103K) with my custom compiled kernel"
Analysis:
I hated the fact that my recently purchased MemoPAD10 (ME103K) tablet had no open process to allow me to become root. I don't trust the closed-source one-click root apps that use various exploits, and require communicating with servers in.... China. Why would they need to do that? I wonder...
I therefore decided this was a good opportunity for me to study the relevant documentation and follow the steps necessary to build an Android kernel for my tablet. I then packaged my custom-compiled kernel into my custom boot image, and the video shows how I boot from it and become root in the process.
Note that I didn't burn anything in my tablet - it's a 'tethered' root, it has no side-effects.
If you are a developer, you can read in detail about the steps I had to take to modify the kernel (and su.c) and become root - by reading the questions (and answers!) that I posted in the Android StackExchange forum ( can't post links yet, see the video description in Youtube ).
If you are not a developer, you can download my custom boot image from the link below - but note that this means you are trusting me to not do evil things to your tablet as my kernel boots and my /sbin/su is run
Honestly, I haven't done anything - I just wanted to run a deboot-strapped Debian in my tablet. But I am also worried about the cavalier attitude I see on the web about rooting your devices - if you want to be truly safe, you must either do what I did (and recompile the kernel yourself) or absolutely trust the person that gives it to you. I do wish Google had forced a UI-accessible "become root" option in Android, just as Cyanogen does (sigh).
The image I created and used in the video to boot in rooted mode, is available from the link show in the Youtube video details.
Enjoy!
Click to expand...
Click to collapse
Hello ttsiodras,
I had the same problem as OP and didn't want to go the "chinese route" either, especially since there seem to be conflicting reports on whether it works on the ME103k or not so I tried your solution - with mixed results...
Disclaimer: I'm totally new to Android (colour me unpleasantly surprised) and have little experience in Linux, so for further reference I would consider myself an advanced noob. Please keep this in mind when evaluating my claims or judging what I have done so far or am capable of doing by myself in the future.
What I did:
- become developer in the ME103k by tapping the system build repeatedly, then allowing debugging via USB
- use ADB to boot into the bootloader
- use fastboot to boot your boot.rooted.img
What happened:
- I did get root access
- the tab now always boots into the bootloader, even when told via ADB or fastboot to boot normally or into recovery. Pushing buttons etc doesn't seem to work either
- my attempts to do a recovery via the vanilla Asus method has failed due to the same fact that boot never gets past fastboot
Since you claimed in your description that there would be no side-effects since it is a tethered root I am somewhat puzzled as to what exactly happened. From what I understand - which admittedly isn't a lot - what should have happened is that your boot image is loaded, giving me root access until the next reboot without changing anything about the default boot process or image. I read somewhere else that this is how people test out different kernels with fastboot before deciding on which one they want to use on their devices. The whole boot process being changed and corrupted in a way that makes the tablet non-rebootable without having the cable and an adb- and fastboot-capable machine nearby is not really what I would have expected going by your description.
Of course it is entirely possible (and probably even rather likely) that I got something wrong along the way or there is a simple fix to my problem I am not aware of.
As for possible steps maybe you or someone else in the forum could point me to a way to return my tablet to factory settings before risking damaging it beyond repair. I'm assuming that it should be possible and rather straightforward to recover the original setup with the firmware provided by Asus (downloaded the newest version from the homepage) but to be honest I'm a bit scared to go ahead with it before knowing for sure how to do this safely.
One thing seems certain: I won't be able to do it the way Asus says I should unless I can somehow get into normal or recovery boot modes again. I do however still have root access and am able to run fastboot and ADB including shell on the tablet, so it should be possible.
I would certainly appreciate any help very much
Thanks
drsiegberterne said:
. . . From what I understand - which admittedly isn't a lot - what should have happened is that your boot image is loaded, giving me root access until the next reboot without changing anything about the default boot process or image. I read somewhere else that this is how people test out different kernels with fastboot before deciding on which one they want to use on their devices.
Click to expand...
Click to collapse
Your understanding is correct - that's exactly what should have happened.
I can assure you that the kernel I compiled is formed from the Asus sources with the 2 patches I made that have *nothing* to do with the bootloader - they patch the way that the kernel allows dropping privileges and thus allowing root level access.
Something else must have happened - did you by any chance "burn" the image? i.e. `(DONT DO THIS) fastboot flash boot boot.rooted.img` instead of `fastboot boot boot.rooted.img`?
I did not advocate for burning precisely because it is unpredictable - manufactures sometimes require signing images with their private keys before allowing a boot image to boot (AKA "locked bootloaders") which means that any attempt to burn may lead to weird configurations. . .
If you did burn it, maybe you can try burning the original "boot.img" from the Asus OTA (Over the Air) update .zip file (avaible as a big download at the ASUS site - "UL-K01E-WW-12.16.1.12-user.zip" )
I know of no way to help you with the current state of your tablet, except to "ease the pain" by saying that rebooting to fastboot is always "recoverable" - you can always boot into my own (rooted) kernel or the original (from the ASUS .zip file) with `fastboot boot <whatever_image>`. No "harm" can happen from this - as you correctly said, it's the way to try new kernels and images.
UPDATE - after more reverse engineering:
I had a look into the contents of the boot loader running inside the ME103K, and I am pretty sure that if you execute this at fastboot...
# fastboot oem reset-dev_info
# fastboot reboot
... you will get back to normal, un-tethered bootings of your ME103K.
Thanassis.
ttsiodras said:
Your understanding is correct - that's exactly what should have happened.
I can assure you that the kernel I compiled is formed from the Asus sources with the 2 patches I made that have *nothing* to do with the bootloader - they patch the way that the kernel allows dropping privileges and thus allowing root level access.
Something else must have happened - did you by any chance "burn" the image? i.e. `(DONT DO THIS) fastboot flash boot boot.rooted.img` instead of `fastboot boot boot.rooted.img`?
I did not advocate for burning precisely because it is unpredictable - manufactures sometimes require signing images with their private keys before allowing a boot image to boot (AKA "locked bootloaders") which means that any attempt to burn may lead to weird configurations. . .
If you did burn it, maybe you can try burning the original "boot.img" from the Asus OTA (Over the Air) update .zip file (avaible as a big download at the ASUS site - "UL-K01E-WW-12.16.1.12-user.zip" )
I know of no way to help you with the current state of your tablet, except to "ease the pain" by saying that rebooting to fastboot is always "recoverable" - you can always boot into my own (rooted) kernel or the original (from the ASUS .zip file) with `fastboot boot <whatever_image>`. No "harm" can happen from this - as you correctly said, it's the way to try new kernels and images.
Thanassis.
Click to expand...
Click to collapse
Hi Thanassis,
thanks for your quick reply and your efforts. I'm actually around 85% sure I did not flash the image but since I had no Linux on my computer at the time (I know shame on me) I used a Mac and the command line was a bit different. Since I had never used ADB or fastboot I relied on some guide that explained how to even get into the bootloader and might have gotten something wrong.
On the other hand I later read out the commands I used in the Mac shell and couldn't find anything other than the things I should have done and described earlier, so as far as I can tell this all should never have happened. It may be interesting to point out here that the "stuck in fastboot" mode happened immediately after the first time I loaded your kernel and I most definitely just wrote fastboot boot boot.rooted.img at that point.
As for fixing the problem now it's not only about the inconvenience of the whole thing. I also later (after I was already stuck in fastboot mode) installed some apps for helping me manage privileges of different apps (xposed framework and xprivacy) which turned out to not be compatible in some way or another. So now not only is my tablet not booteable in a normal way but its also cluttered with even more useless stuff than before and I would really like to just reset it before thinking about any other possibilities.
If I flash boot the original ASUS boot image found in the file you described and which i dowloaded already, shouldn't that fix the problem if I accidentally did flash your boot image? Or will there be even more trouble?
Alternatively isn't there a manual way to flash the whole zipped recovery image or am I misunderstanding what this ASUS file actually contains?
And which of the two options is safer to try first or in other words - which one might break the tablet once and for all?
Thanks again and sorry for my incompetence
drsiegberterne said:
Hi Thanassis,
If I flash boot the original ASUS boot image found in the file you described and which i dowloaded already, shouldn't that fix the problem if I accidentally did flash your boot image? Or will there be even more trouble?
. . .
Alternatively isn't there a manual way to flash the whole zipped recovery image or am I misunderstanding what this ASUS file actually contains?
. . .
Thanks again and sorry for my incompetence
Click to expand...
Click to collapse
No, don't be sorry We are all either choosing to learn in this world (i.e. make mistakes and learn from them), or choose to remain stuck in ignorance. I applaud your efforts in properly rooting the tablet. . .
To the point - remember, you are root now ; whatever apps you installed, you can definitely uninstall them. You don't necessarily need to wipe it.
If you do want to, I'd suggest booting in recovery and doing it the normal way that Asus recommends. Since you said "buttons don't work", you may want to try using the original recovery .img - i.e. "fastboot boot recovery.img". I'd love to suggest a link from ASUS, but they don't host it (which is bad - they really should) - so instead go to "goo" dot "gl" slash "noegkY" - this will point you to a discussion where a kind soul is sharing his ME103K recovery.img.
Booting from the recovery will allow you to install the ASUS OTA update - and probably try cleaning cache partition, etc
Good luck!
ttsiodras said:
No, don't be sorry We are all either choosing to learn in this world (i.e. make mistakes and learn from them), or choose to remain stuck in ignorance. I applaud your efforts in properly rooting the tablet. . .
To the point - remember, you are root now ; whatever apps you installed, you can definitely uninstall them. You don't necessarily need to wipe it.
If you do want to, I'd suggest booting in recovery and doing it the normal way that Asus recommends. Since you said "buttons don't work", you may want to try using the original recovery .img - i.e. "fastboot boot recovery.img". I'd love to suggest a link from ASUS, but they don't host it (which is bad - they really should) - so instead go to "goo" dot "gl" slash "noegkY" - this will point you to a discussion where a kind soul is sharing his ME103K recovery.img.
Booting from the recovery will allow you to install the ASUS OTA update - and probably try cleaning cache partition, etc
Good luck!
Click to expand...
Click to collapse
The problem here is that he doesn't seem to have the same version as on my tablet. I have the newest version with Lollipop while this seems to be at least a couple of patches earlier with a completely different version of Android. Won't I risk breaking things even more if I try to apply this - as in trying to recover a recovery that is not on my tablet since certainly the recovery.img doesn't contain all the information needed since it's only 10 MB.
As you can probably guess the whole discussion in your link about what part of the system is broken and how to fix it goes right over my head. It also seems like they did not find a satisfactory solution in the end (short of sending the tablet to ASUS). As you can imagine I'm at quite a loss what to try and what not out of fear to make things worse. At least for now I can still use the tablet to do the things I need it to do.
Thanks for your help anyway, I will try to read up more on the topic and decide what to do next.
drsiegberterne said:
The problem here is that he doesn't seem to have the same version as on my tablet. I have the newest version with Lollipop while this seems to be at least a couple of patches earlier with a completely different version of Android. Won't I risk breaking things even more if I try to apply this - as in trying to recover a recovery that is not on my tablet since certainly the recovery.img doesn't contain all the information needed since it's only 10 MB.
Thanks for your help anyway, I will try to read up more on the topic and decide what to do next.
Click to expand...
Click to collapse
I understand how you feel - your tablet is operational now (OK, with the annoyance that you need to boot it in "tethered mode") - so you rightfully fear that you may mess things up with further steps.
Just to clarify something - the recovery img is something that works on its own ; it has no dependency on what kind of Android image is installed in the /system partition.
If you do decide to do it, "fastboot boot recovery.img" will bring you to a spartan menu, showing options that allow you to apply an update (i.e. the ASUS update you downloaded!), clean the /cache partition, etc.
Choose "install update from SD card" (use volume up/down to choose, power btn to select), and navigate to your SD card, where you will have placed the big .zip file from ASUS.
The recovery process will begin, and your tablet will be "wiped" with the image from ASUS. Reboot, and be patient while the tablet boots up - it will be just like the first time you started it (i.e. install from scratch).
Whatever you decide - good luck!
ttsiodras said:
I understand how you feel - your tablet is operational now (OK, with the annoyance that you need to boot it in "tethered mode") - so you rightfully fear that you may mess things up with further steps.
Just to clarify something - the recovery img is something that works on its own ; it has no dependency on what kind of Android image is installed in the /system partition.
If you do decide to do it, "fastboot boot recovery.img" will bring you to a spartan menu, showing options that allow you to apply an update (i.e. the ASUS update you downloaded!), clean the /cache partition, etc.
Choose "install update from SD card" (use volume up/down to choose, power btn to select), and navigate to your SD card, where you will have placed the big .zip file from ASUS.
The recovery process will begin, and your tablet will be "wiped" with the image from ASUS. Reboot, and be patient while the tablet boots up - it will be just like the first time you started it (i.e. install from scratch).
Whatever you decide - good luck!
Click to expand...
Click to collapse
Okay, a little update from the battlefront:
I tried the recovery image and did get into the menu, however the recovery failed with the same two error messages as in your earlier link ("footer is wrong" and "signature verification failed"). My output from fastboot getvar all is also very similar to the one from that guy except I have a different bootloader version than him (3.03).
Another thing I noticed is that if I boot the standard boot.img found in the ASUS zip it will recognize the internal sdcard normally, however when I boot your rooted image the internal memory doesn't seem to be recognized, at least not through the pre-installed file manager. Downloading a file to the internal storage also failed while rooted but all the apps and the OS itself so far seem totally unaffected otherwise.
My last resort at the moment is the fastboot flash boot boot.img but I have little hope it would change anything since in the thread you linked they proposed just that and if it had worked they probably would have mentioned it.
Can it theoretically break the tablet even more? I would hate to have to send it in because I completely bricked it...
drsiegberterne said:
Okay, a little update from the battlefront:
Another thing I noticed is that if I boot the standard boot.img found in the ASUS zip it will recognize the internal sdcard normally, however when I boot your rooted image the internal memory doesn't seem to be recognized.
Click to expand...
Click to collapse
Not the case for me - everything works fine (including internal and external sdcard), so it's definitely not my kernel causing this.
drsiegberterne said:
My last resort at the moment is the fastboot flash boot boot.img but I have little hope it would change anything since in the thread you linked they proposed just that and if it had worked they probably would have mentioned it.
Can it theoretically break the tablet even more? I would hate to have to send it in because I completely bricked it...
Click to expand...
Click to collapse
Flashing is always dangerous (from what you've said, I actually theorize that you did, actually, flash already...)
I doubt this will solve the boot issue, to be honest - if I were you, I'd continue to boot tethered (with my image when you need root access, and (maybe) the Asus image when you don't). Myself, I always boot my own bootimage, since I have zero problems with it, and it allows me to run a complete Debian distro in a chroot (thus making my tablet a full-blown UNIX server - e.g. I run privoxy on it to filter all stupid ads in all apps on the tablet, etc).
No matter what you decide, good luck!
Thanassis.
ttsiodras said:
Not the case for me - everything works fine (including internal and external sdcard), so it's definitely not my kernel causing this.
Flashing is always dangerous (from what you've said, I actually theorize that you did, actually, flash already...)
I doubt this will solve the boot issue, to be honest - if I were you, I'd continue to boot tethered (with my image when I need root access, and (maybe) the Asus image when I don't). Myself, I always boot my own bootimage, since I have zero problems with it, and it allows me to run a complete Debian distro in a chroot (thus making my tablet a full-blown UNIX server - e.g. I run privoxy on it to filter all stupid ads in all apps on the tablet, etc).
No matter what you decide, good luck!
Thanassis.
Click to expand...
Click to collapse
I already tried to flash the original boot.img yesterday but it didn't change anything as you correctly assumed so I guess for now there is nothing more to do. I might write to the Asus support and maybe send the tablet in if it is free of charge for me (which I doubt). The only other option is to spend the next months to get sufficiently versed in Android to actually fix the problems myself but even for that I would probably need some files or source code from Asus. I find it rather disappointing the way these "closed" systems work nowadays, with the advancement of Linux and Open Source I really would have expected the opposite to be true but apparently people care more about convenience than actually being able to use the tools they buy in the way they want to.
Getting these Android devices like buying a hammer that can't hammer things in on Sundays.
drsiegberterne said:
I find it rather disappointing the way these "closed" systems work nowadays, with the advancement of Linux and Open Source I really would have expected the opposite to be true but apparently people care more about convenience than actually being able to use the tools they buy in the way they want to
Click to expand...
Click to collapse
I share the sentiment - it's really sad.
Undoing the tethered root
drsiegberterne said:
I already tried to flash the original boot.img yesterday but it didn't change anything as you correctly assumed so I guess for now there is nothing more to do. I might write to the Asus support and maybe send the tablet in if it is free of charge for me (which I doubt). The only other option is to spend the next months to get sufficiently versed in Android to actually fix the problems myself but even for that I would probably need some files or source code from Asus. I find it rather disappointing the way these "closed" systems work nowadays, with the advancement of Linux and Open Source I really would have expected the opposite to be true but apparently people care more about convenience than actually being able to use the tools they buy in the way they want to.
Getting these Android devices like buying a hammer that can't hammer things in on Sundays.
Click to expand...
Click to collapse
Hi drsiegberterne - I had a look into the contents of the boot loader running inside the ME103K, and I am pretty sure that if you execute this at fastboot...
# fastboot oem reset-dev_info
# fastboot reboot
... you will get back to normal, un-tethered bootings of your ME103K.
Hope this solves your problem!
Kind regards,
Thanassis.
I rebooted in to recovery (B partition) from custom ROM , ran Migrator Magisk module twice (as directions say-second run does FDR), booted into A partition of my Pixel XLto flash new ROM and for some reason EVERYTHING is encrpyted (do not have screen lock or pin applied) ..... I remember seeing something like this when I first got the device but cant recall how to deal with it.
Every attempt to adb sideload, adb push , etc not working ....
C.Hatfield said:
I rebooted in to recovery (B partition) from custom ROM , ran Migrator Magisk module twice (as directions say-second run does FDR), booted into A partition of my Pixel XLto flash new ROM and for some reason EVERYTHING is encrpyted (do not have screen lock or pin applied) ..... I remember seeing something like this when I first got the device but cant recall how to deal with it.
Every attempt to adb sideload, adb push , etc not working ....
Click to expand...
Click to collapse
So, I take it you were trying to 'migrate' to another ROM?
My suggestion is this, use this guide: https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3825866/
- Start fresh
- Do #4 'wipe data'
was just using the magisk migrator module - it backed up all my files on 1st run, then 2nd run it did FDR .... I would REALLY prefer not wiping my internal/sdcard ..... everything is still there but encrypted, unusable for the moment - hoping there is a workaround bc Ihave sooo much data that I havent backed up externally/cloud for a month or 3 .... got nothing I can boot from as well as no access to ALL the tons of stuff stored on my phone to flash .... was thinking to use Factory image but removing the [-w] from the bat file ..... would that work to keep my data integrity ?
Honestly, im wondering how things got encrypted when the process (xc for what im unsure the mod did extra besides FDR) is practically, if not identical, to the normal protocol for wiping>flashing for PIXEL XL
C.Hatfield said:
was just using the magisk migrator module - it backed up all my files on 1st run, then 2nd run it did FDR .... I would REALLY prefer not wiping my internal/sdcard ..... everything is still there but encrypted, unusable for the moment - hoping there is a workaround bc Ihave sooo much data that I havent backed up externally/cloud for a month or 3 .... got nothing I can boot from as well as no access to ALL the tons of stuff stored on my phone to flash .... was thinking to use Factory image but removing the [-w] from the bat file ..... would that work to keep my data integrity ?
Click to expand...
Click to collapse
...would that work to keep my data integrity ? Yes
will the modded flash-all.bat actually work with all the contents of the internal drive being encrypted?
I only ask bc of all the research Ive been doing for the last 4 hours, I had no idea that the current TWRP [3.2.3.1] made decryption on PIe possible .... I not ref to the PIN/lockscreen/Fingerprint decrypt either > more like decrypting the System partition like with Shamu/N6
**Also** found this during my harried research:
Encrypting does not completely delete the files, but the factory reset process gets rid of the encryption key. As a result, the device has no way it can decrypt the files and, therefore, makes data recovery extremely difficult.
C.Hatfield said:
will the modded flash-all.bat actually work with all the contents of the internal drive being encrypted?
I only ask bc of all the research Ive been doing for the last 4 hours, I had no idea that the current TWRP [3.2.3.1] made decryption on PIe possible .... I not ref to the PIN/lockscreen/Fingerprint decrypt either > more like decrypting the System partition like with Shamu/N6
**Also** found this during my harried research:
Encrypting does not completely delete the files, but the factory reset process gets rid of the encryption key. As a result, the device has no way it can decrypt the files and, therefore, makes data recovery extremely difficult.
Click to expand...
Click to collapse
Yes!
Yes, twrp-3.2.3-1 decrypts.
"**Also** found this during my harried research:
Encrypting does not completely delete the files, but the factory reset process gets rid of the encryption key. As a result, the device has no way it can decrypt the files and, therefore, makes data recovery extremely difficult."
Where did you find that? Link please.
Homeboy76 -
Very much appreciate the feedback !! This is the longest downtime I've experienced, likely-ever but I just couldn't make another move until I was certain it was the correct one.
Here is the link where I found the above info you asked about:
https://android.stackexchange.com/questions/149219/android-decrypt-sd-card-after-factory-reset?rq=1
C.Hatfield said:
Homeboy76 -
Very much appreciate the feedback !! This is the longest downtime I've experienced, likely-ever but I just couldn't make another move until I was certain it was the correct one.
Here is the link where I found the above info you asked about:
https://android.stackexchange.com/questions/149219/android-decrypt-sd-card-after-factory-reset?rq=1
Click to expand...
Click to collapse
Edit: Wrong link, it happens.
this is what it shows me:
It is in the default factory reset state ( like a new device ). You can't decrypt the device even if you wish to as the encryption password (generated from a combination of user lock screen PIN and encryption algorithm ) is lost
From Android's Factory Reset Does Not Wipe Your Data: Here's The Solution
Encrypting does not completely delete the files, but the factory reset process gets rid of the encryption key. As a result, the device has no way it can decrypt the files and, therefore, makes data recovery extremely difficult.
C.Hatfield said:
this is what it shows me:
It is in the default factory reset state ( like a new device ). You can't decrypt the device even if you wish to as the encryption password (generated from a combination of user lock screen PIN and encryption algorithm ) is lost
From Android's Factory Reset Does Not Wipe Your Data: Here's The Solution
Encrypting does not completely delete the files, but the factory reset process gets rid of the encryption key. As a result, the device has no way it can decrypt the files and, therefore, makes data recovery extremely difficult.
Click to expand...
Click to collapse
Yes, if you use this url: https://www.techtimes.com/amp/artic...oes-not-wipe-your-data-heres-the-solution.htm but that is not the url that was in your previous post. This is, https://android.stackexchange.com/questions/149219/android-decrypt-sd-card-after-factory-reset?rq=1
I think it is out dated: Android's Factory Reset Does Not Wipe Your Data: Here's The Solution By Anu Passary | May 27, 2015 11:07 PM EDT
hey homeboy76 tried the flash-all bat [-w removed] and the process went through w/o any issues but it immediately rebooted itself and within 30 seconds landed on the stock recovery & it said file may be corrrupt, TRY AGAIN or FDR ....
Do I have any other recourse to save my 100 GBs of data ??? or do I onlly have the unmoddded flash-all -w to do at this point ?
C.Hatfield said:
hey homeboy76 tried the flash-all bat [-w removed] and the process went through w/o any issues but it immediately rebooted itself and within 30 seconds landed on the stock recovery & it said file may be corrrupt, TRY AGAIN or FDR ....
Do I have any other recourse to save my 100 GBs of data ??? or do I onlly have the unmoddded flash-all -w to do at this point ?
Click to expand...
Click to collapse
Did you check the SHA256 of the March 2019 factory image?
I don't think it would hurt to try again. If it doesn't work you can try FDR or flash-all with [ -w] both will erase your internal storage.
Homeboy76 said:
Did you check the SHA256 of the March 2019 factory image?
I don't think it would hurt to try again. If it doesn't work you can try FDR or flash-all with [ -w] both will erase your internal storage.
Click to expand...
Click to collapse
Soooo, check this out .... I finally got a flash-all {no -w] to work and my phone booted - buuuuut it is STILL ENCRYPTED .... opening the root//file explorer I was horrified to see that everything is still encrypted .... it's soooo bizarre. apps from PS are restoring but I cannot get screenshots to save nor can I move any files from my laptop to my Pixel Xl. I wanted screeenshots so bad to show/post this bizarreness but -no- ....
I havent tried to boot into recovery yet or anything else .... so I dont even have root to look any deeper into the partitions. I was wondering if Titanium Backup would run and populate with proper app names, etc
Any more ideas from this unprecedented point bro >? BTW, the SHA256 was good/clean/proper.
BTW, when you flash a factory image, which facking partition (A or B) -should it- be flashed to or flashed "from" - I've let myself get quite confused >???? I have researched & read sooo much, my brain hurts (& is literally fried) .... I figured I would ask you so I could possibly get some firsthand clarification.
C.Hatfield said:
Soooo, check this out .... I finally got a flash-all {no -w] to work and my phone booted - buuuuut it is STILL ENCRYPTED .... opening the root//file explorer I was horrified to see that everything is still encrypted .... it's soooo bizarre. apps from PS are restoring but I cannot get screenshots to save nor can I move any files from my laptop to my Pixel Xl. I wanted screeenshots so bad to show/post this bizarreness but -no- ....
I havent tried to boot into recovery yet or anything else .... so I dont even have root to look any deeper into the partitions. I was wondering if Titanium Backup would run and populate with proper app names, etc
Any more ideas from this unprecedented point bro >? BTW, the SHA256 was good/clean/proper.
BTW, when you flash a factory image, which facking partition (A or B) -should it- be flashed to or flashed "from" - I've let myself get quite confused >???? I have researched & read sooo much, my brain hurts (& is literally fried) .... I figured I would ask you so I could possibly get some firsthand clarification.
Click to expand...
Click to collapse
I can't help you with the file encrypted problem. I've never read about anything like the problem you're having with encryption. TB might work. If your files are backed up on your computer, FDR.
https://forum.xda-developers.com/showpost.php?p=79273902&postcount=481
@C.Hatfield, continuing the discussion...
Topics
1) Forced encryption
2) Output of ls /data/misc/vold/*
3) Advanced approach
VR25-
First, I'll start with a sincere Thank You - I know you're busy with school & life, so I appreciate that you take the time to create such beneficial tools like Migrator. Having used Android OS since it's inception, I've learned a whole lot & seen a whole lot buuut not this craziness. I was unable to get any actionable help within the 2 weeks that I held out doing a full FDR ....
alas, I finally relented & did a full FDR with a full on flash-all.bat & ironically, it was only a couple hours before your response. I didn't read the response until now because I was afraid you'd posted an A, B, C unencryption method for me - in a small way, I'm glad it isn't that lol ....
As for the "did you..." questions you asked in Migrator thread, I followed my usual protocol & did not vary at all, except running the Migrator script 2x's before trying to install new ROM.