Related
Hi all, I am going to be as thorough as I can. I am rather new, and I'm stuck trying to downgrade my MT4G to froyo (PD15IMG). I have read the tutorials, and learned enough about adb to attempt this task, but I think by doing the HTC Bootloader unlocking update last week, it may be the reason I'm stuck. I follow the instructions on the tutorial, to gain temp root, until I get to the part where I should get a "#" in the command Window when I type "adb shell" but I keep getting "$" instead, although everything seems to be going ok until I get to that point.
*Also, I put the PD15IMG.zip on the root of my sd card, and start my phone in bootloader mode, and it finds the PD15IMG.zip, and a blue progress bar appears in the top right corner of my phone for about 90 seconds, it then displays "parsing PD15IMG.zip" then stops at the hboot screen and does nothing. I just select power down, then power on my phone and nothing will have been done to my phone. I guess what I need to know is, by doing the HTC bootloader unlock update (which I did before I read that it was a bad idea), can I still downgrade and root with normal methods, or will I have to do something different?
Sent from my HTC Glacier using Tapatalk
You can start differently. Since you've unlocked the bootloader, try to flash recovery directly, by downloading recovery image directly from Clockworkmod site, rebooting to FASTBOOT (adb reboot bootloader) and using the command "fastboot flash recovery your_just_downloaded_recovery.img".
If recovery flash doesn't work for you - download the 2.2.1 PD15IMG, unzip it, and flash the following 2 files from it:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase userdata
Then reboot. You should end up on 2.2.1, which is perm-rootable using the guide (Visionary for temp-root, gfree for S-OFF, and then perm-root if you want).
Then flash the recovery and the engineering bootloader.
Here is what I did, I am giving a link to pastebin as instructed, it seems to go perfectly until I try to flash the StockRom. In the meantime I will attempt what was just posted above^^^^^^^ http://pastebin.com/fYrC6tAZ
One last thing before i have to throw away my phone. I couldnt leave well enough alone. I did this "fastboot flash boot boot.img" as you stated in the post above. It was successful. I then entered this one "fastboot flash system system.img", and it failed (said the img was too big or something) so I did the "fastboot-windows reboot" command and it is now stuck on the white HTC MyTouch 4g splashscreen. Is my phone toast? My PC no longer recognizes that my phone is connected to the USB port, however I can hold the volume dwn & power button and it comes on in the hboot mode.Is there any hope?
Also, when I boot it up by vol/dwn & pwr, the Hboot screen comes up and finds the PD15IMG that is on my sd card, goes through a 1 minute or so process (a blue status bar loads in top right corner), then it just stays on the hboot. It did that before it stuck on the splash screen, but never actually wrote anything i dont beleive.
OK its letting me use FASTBOOT and here is exactly what I got when i tried to flash the 2nd file in your post above. It came from the PD15IMG.zip as you instructed:
C:\adb>fastboot flash system system.img
sending 'system' (571388 KB)... FAILED (remote: data length is too large)
finished. total time: 0.016s
Can someone please let me know if there is hope for my phone? I can communicate with it through Fastboot (on my PC) and it will boot up in hboot mode. But it WON'T go past the Tmobile/MyTouch splash screen. If I get it fixed, I promise to never touch it again until I study! I truly feel there is hope, but I think don't know enough to figure it out. I loaded the PD15IMG on my SD, and it attempts to flash it, (a blue status bar appears in top right corner and fills up in about 90 seconds), but afterwards, it still sticks on splashscreen. Is there anything I can do to fix it? Anything I can flash it with in Fastboot? Please anyone?
You mixed 2 ways, and did it completely wrong way. And you didn't attempt to flash the recovery at all.
The first part, that went well (till ./flashgc), already prepared your phone for downgrading, and you should have recognized and understood it. You don't need anything else, no flashes from bootloader or anything. All you needed was to continue - put PD15IMG.ZIP on the SD card, reboot into bootloader, and let it downgrade.
You can still do it, so please do.
---------- Post added at 06:16 PM ---------- Previous post was at 06:13 PM ----------
Once you end up on 2.2.1, please follow the "Ultimate rooting guide" from Development section, and flash Engineering bootloader.
Jack_R1 said:
You mixed 2 ways, and did it completely wrong way. And you didn't attempt to flash the recovery at all.
The first part, that went well (till ./flashgc), already prepared your phone for downgrading, and you should have recognized and understood it. You don't need anything else, no flashes from bootloader or anything. All you needed was to continue - put PD15IMG.ZIP on the SD card, reboot into bootloader, and let it downgrade.
You can still do it, so please do.
---------- Post added at 06:16 PM ---------- Previous post was at 06:13 PM ----------
Once you end up on 2.2.1, please follow the "Ultimate rooting guide" from Development section, and flash Engineering bootloader.
Click to expand...
Click to collapse
Thank for your response. I have tried doing the PD15IMG.zip by booting my phone in bootloader mode. It finds the PD15IMG.zip and then a blue progress bar appears in the top right corner of the phone, finishes in about 90 seconds, the a message appears that says "wrong zip file". I would be happy just to get my phone back on with the gingerbread 2.3.4 on it, and simply leave it alone until I know what Im doing. Is there a way to just flash the original s/w back on it? If so if you could tell me how I will not mess with it again until I study alot more. But flashing the PD15IMG doesnt appear to be working for me.
Download the file again, and check MD5SUM on it before you use it.
If it responds "wrong ZIP" - it's because the ZIP is corrupted. When you'll download a good ZIP, it'll work.
Jack_R1 said:
Download the file again, and check MD5SUM on it before you use it.
If it responds "wrong ZIP" - it's because the ZIP is corrupted. When you'll download a good ZIP, it'll work.
Click to expand...
Click to collapse
Ok you were right, the one I had the wrong MD5SUM, but i d/l the correct one, it had the correct MD5SUM, but it still gave me the "wrong zip file error". I feel like there is hope, but I cant figure this out!! Thank you for trying, is there anything else I can do? I also tried going into recovery and doing factory reset/ data wipe etc...but it continues to get stuck on the splash screen....
How did you copy the correct one to the phone's SD card, and where did you put it? You either didn't copy it to your SD card, or named it wrong, or put it in wrong location, not overwriting the older file.
In any case, if flashing PD15IMG fails for you:
Download CWM recovery from here:
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-glacier.img
Boot to bootloader.
Enter FASTBOOT.
Execute:
fastboot flash recovery recovery-clockwork-5.0.2.0-glacier.img
Boot to recovery. You should have Clockworkmod.
Download a stock rooted 2.2.1 ROM from Development section.
Flash it in Clockworkmod recovery.
Extract boot.img from this ROM.
Flash it in fastboot, using "fastboot flash boot boot.img".
Boot into the ROM.
Proceed with gfree.
OK!! I got it fixed and it all makes sense to me now! I flashed the 2.2.1 boot.img to my phone, when it still had the 2.3.4 on it. It was as simple as that. I hadnt flashed the downgrade on it when I flashed the boot.img and I guess it was a mismatch. I read your last post to extract the "boot.img" from the rom and then it clicked! Yesterday I wrote the 2.2.1 boot img. to a phone that had 2.3.4...so I found a stock 2.3.4 rom, extracted the boot.img from it a BAM! its rolling again....thank you so much....
Yes, indeed, you flashed a mismatched, older kernel to your ROM. I was suggesting that you install custom recovery and change the ROM to match your boot.img, but the other way around also works - as long as you don't need to root your phone, that is.
Jack_R1 said:
Yes, indeed, you flashed a mismatched, older kernel to your ROM. I was suggesting that you install custom recovery and change the ROM to match your boot.img, but the other way around also works - as long as you don't need to root your phone, that is.
Click to expand...
Click to collapse
Well I will soon attempt it again, however I think I need to read a little more so I can understand the concept of what I am doing. I learned a ton by making that mistake. But as soo as I got it fixed, I couldnt resist, I used revovery and flashed [ROM]:: ProjectMIUI 2.2.17 [R6]- UPDATED 2/21/12 - [Stable + Smooth from the DEV section and I have never been happier with my phones performance! I will soon try the cyanmod, but I want to chill with this rom for a week or so. Again, I appreciate your help, I learned alot.
As long as you don't mind flashing kernels separately using fastboot for each ROM you flash, you can go indefinitely and flash ROMs as much as you like with your current setup, not needing anything else. The only good reason for you to go for S-OFF would be to flash Engineering HBOOT, to be able to flash kernels from recovery directly, avoiding extra fastboot step.
Also, thanks for finally confirming that you can flash recovery using fastboot on HTC-Dev-unlocked device. There was one device that didn't allow it (I think Incredible S, but not sure), so it's good to know that on MT4G it works as it should.
http://code.google.com/android/nexus/images.html#yakju
https://groups.google.com/forum/?fromgroups#!topic/android-building/b50nY_onbP4
^Thanks.
This can be flashed via CWM recovery ?
(after a 'fastboot oem lock/unlock' ?)
No. They are fastboot images. If you're not sure what these are and how to use them then I would not mess with them.
^ gotcha
can someone please put up a tutorial/guide to do this.
I really want to try this.
The shell script gives you the exact fastboot commands to run if you want to do it manually. And it will restore your phone to a true factory state with 4.0.4.
if i will use the factory img the baseband version in bootloader will be change? i see now i9020xxkl1 but my nexus is i9023?
I was wondering the same .. In the zip it says :require board=herring
require version-bootloader=I9020XXJK1|I9020XXKA3|I9020XXKI1|I9020XXKL1
require version-baseband=I9020XXJK8|I9020XXKB1|I9020XXKD1|I9020XXKF1|I9020XXKI1|I9020UCKB2|I9020UCKD1|I9020UCKF1|I9020UCKJ1|I9020KRKB3|M200KRKC1
So it should be okay , because when I reboot into the bootloader of my phone it says :
Bootloader version: I9020XXKL1
Baseband version : I9020XXKI1
My phone actually is a I9023 so I gues the images are okay to flash on a I9023
Just noticed that the full ROM version for Nexus S is 4.0.4 IMM76D. Wouldn't be better to flash this complete rom instead of the partial patch OTA which is clearly giving troubles?
HELPPPPP
can someone please put up a tutorial/guide to do this.
I really want to try this.
i wrote a guide
http://forum.xda-developers.com/showthread.php?t=1572307
goldy_rocky said:
can someone please put up a tutorial/guide to do this.
I really want to try this.
Click to expand...
Click to collapse
(No time to write a full tutorial right now but...) I'd say...
Pls wait for someone experimented to confirm what I say because I couldn't try it to confirm it works right now... And also try it at your own risk...
If your bootloader is not unlocked, follow PART 1 & PART 2 of this tutorial. (you will loose data)
(Note that ADB is not in tools folder anymore but in /platform-tools so that's where the part2 cmd as to be runned from)
Then if windows (I guess you would know what to do if on Linux) use 7zip to extract (2 times) all files from the archive.
Then copy the files to the /platform-tools folder.
The open a command prompt in that folder (shift+right click>open a command prompt here).
Then use the commands provided in the .sh script to flash all files (you can read it easily with Notepad++ for instance) one by one...
Note I don't think you can run the "sleep 5" cmd manually but you can of course wait 5' manually .
Code:
fastboot flash bootloader bootloader-crespo-i9020xxkl1.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-crespo-i9020xxki1.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-soju-imm76d.zip
I'm not really sure if bootloader will be locked at this time but my guess is no so just reboot the bootloader ("fastboot reboot-bootloader" or shut down the device then "Boot the SNS into the Bootloader Interface, by holding Volume UP & Power button" and look for the "LOCK STATE - LOCKED" or "LOCK STATE - UNLOCKED").
If "LOCK STATE - UNLOCKED" you may want to lock the bootloader again, just follow part2 again and replace "fastboot oem unlock" by "fastboot oem lock"
EDIT :
ale.landra91 said:
i wrote a guide
http://forum.xda-developers.com/showthread.php?t=1572307
Click to expand...
Click to collapse
You just made me feel so useless ...
First of all, the credits goes to "a2b". I am only put his work here via a link.
Secondly, PLEASE KEEEP IN YOUR MIND THAT NEITHER ME OR "a2b" IS RESPONSABLE FOR ANY LOSS OF YOURS IF YOUR PHONE GET BRICKED.
The thrid, I have tried the method on my Nexus i9023. It works perfectly for me. BUT, I cannot gurentee it works for everyone.
Okay, I just flashed the factory img according to a2b's tutorial for Galaxy Nexus. But for me I just needed to change the names for few files. If you cannot figure out what to change, I suggest you follow albundy2010's advice on post #3
Good luck!
http://androidtobe.blogspot.com/2011/12/galaxy-nexus-installing-ics-402-from.html
Seems most are not familiar with doing this so here are some things you should know.
Doing this will wipe EVERYTHING off your phone. Yes, everything including /sdcard.
Do not be a fool and flash these images to the 4g.
I am not certain about this and if you it and your phone gets messed up do not blame me.
The 9020a should be able to run this factory image. Check to see what version of the bootloader you have. If it matches one of the bootloaders in the .sh script you should be fine. I would NOT flash the bootloader included in this factory image myself. Since I do not know for sure if they are the same for both GSM models. If you follow the guide minus the parts where you flash the bootloader and the radio image I believe it will work.
Again if you try this and it breaks your phone that is on you. I am not responsible for it. I do not have a 9020a to test this on and verify it. I am fairly certain it will work perfectly. If anybody tries it let me/us know the outcome.
is there any specific advantage in flashing the factory image as opposed to flashing the incremental update ? I successfully flashed 4.0.4 using CWR over a full rom installation of 4.0.3 back from December. I wonder if there may be some subtle differences that maybe make it a bit better option to install the factory image ?
mindwalkr said:
is there any specific advantage in flashing the factory image as opposed to flashing the incremental update ? I successfully flashed 4.0.4 using CWR over a full rom installation of 4.0.3 back from December. I wonder if there may be some subtle differences that maybe make it a bit better option to install the factory image ?
Click to expand...
Click to collapse
No
Sent from my Nexus S using XDA App
I used the flash-all.sh script from the factory image file and it didn't wipe the sdcard. Backed it up beforehand anyway just in case. Recovery was broken on reboot. Flashed CWM recovery and all good. i9023.
Hi, I am a happy owner of the HP Slate 7 Extreme which is basically the same device as you guys are using.I am still on the 4.2 Jelly bean since HP are not pushing over the air updates with our devices.I want to use the script from the development forum "[Script] [Utility] Nvidia Tegra Note 7 Kitkat Unlock BL, Restore, Recovery, & Root", I want to know if anyone has tried to use it with the Slate Extreme or if it simply should work on the Jelly Bean aswell. Thanks guys.
still have freeze/hang issue..
http://forum.xda-developers.com/showthread.php?t=2663449&page=2
mofared said:
still have freeze/hang issue..
http://forum.xda-developers.com/showthread.php?t=2663449&page=2
Click to expand...
Click to collapse
What about the 4.3+ ?
crazyhacker202 said:
What about the 4.3+ ?
Click to expand...
Click to collapse
i have not test that yet but i believe it should work because i have tested the 4.4.2 and 4.2.2 evga ROM from here using the cwm install from sdcard method..
http://forum.xda-developers.com/showthread.php?t=2627671
The only thing that puzzles me now is i am unable to perform a system recovery from HP update.zip using cwm.
http://h10025.www1.hp.com/ewfrf/wc/...en&cc=us&dlc=en&sw_lang=&product=6608632#N147
So right now i am stuck with 4.2.2 evga ROM all is good and functional.
I have read some post that by updating OTA fix issue in 4.4 but i have no idea on how to get the OTA update.
p/s: This is my first tablet and root attempt...
edit:
i found out that rootjunky has already released the 4.4.2 with 2.3 OTA i will give it a try and feedback later
mofared said:
i have not test that yet but i believe it should work because i have tested the 4.4.2 and 4.2.2 evga ROM from here using the cwm install from sdcard method..
http://forum.xda-developers.com/showthread.php?t=2627671
The only thing that puzzles me now is i am unable to perform a system recovery from HP update.zip using cwm.
http://h10025.www1.hp.com/ewfrf/wc/...en&cc=us&dlc=en&sw_lang=&product=6608632#N147
So right now i am stuck with 4.2.2 evga ROM all is good and functional.
I have read some post that by updating OTA fix issue in 4.4 but i have no idea on how to get the OTA update.
p/s: This is my first tablet and root attempt...
edit:
i found out that rootjunky has already released the 4.4.2 with 2.3 OTA i will give it a try and feedback later
Click to expand...
Click to collapse
First, nope, you'll still get freezing. I've tried all the ROMs.
Second, If you want to go back to HP's recovery, do the following:
Create a copy of update.zip and navigate to META-INF\com\google\android and open up updater-script
Delete the first three lines.
Transfer your new update.zip to your device and flash. Allow it to re-write the recovery partition.
NOTE THAT YOUR DEVICE WILL NOT ADVANCE PAST THE BOOT ANIMATION. THIS IS NORMAL.
Copy the original update.zip to a SD card and insert it into the device.
Now go to the HP recovery partition that now exists on your device and follow HP's restore instructions.
You're done, the stock 4.2.2 that came with your device is now installed.
Had to figure this out the hard way after I lost my original backup.
To the original poster, you can get it to work, but you need to make modifications to the script's fastboot commands (they will require "fastboot -i 0x03F0" before they will do anything) and you will need to setup your machine for ADB with the Slate 7 Extreme. It won't work out of the box, you can find support for that here: http://h30434.www3.hp.com/t5/Android-Tablets-e-g-HP-Slate-7/ADB-drivers/td-p/2574571
There was an individual who has received the 4.4.2 update from HP on his Slate Extreme over at the HP forums. I believe he stated he received 20 units donated directly from HP and was wondering why only 1 of them received the update. I believe the reason stated is that he most likely received a non-retail unit by accident. Not sure if he ever dumped the ROM or even knows how. I don't know either otherwise I'd try to contact him to get him to do so.
Re-write recovery partition?
Robo_Leader said:
First, nope, you'll still get freezing. I've tried all the ROMs.
Second, If you want to go back to HP's recovery, do the following:
Create a copy of update.zip and navigate to META-INF\com\google\android and open up updater-script
Delete the first three lines.
Transfer your new update.zip to your device and flash. Allow it to re-write the recovery partition.
NOTE THAT YOUR DEVICE WILL NOT ADVANCE PAST THE BOOT ANIMATION. THIS IS NORMAL.
Copy the original update.zip to a SD card and insert it into the device.
Now go to the HP recovery partition that now exists on your device and follow HP's restore instructions.
You're done, the stock 4.2.2 that came with your device is now installed.
Had to figure this out the hard way after I lost my original backup.
To the original poster, you can get it to work, but you need to make modifications to the script's fastboot commands (they will require "fastboot -i 0x03F0" before they will do anything) and you will need to setup your machine for ADB with the Slate 7 Extreme. It won't work out of the box, you can find support for that here: http://h30434.www3.hp.com/t5/Android-Tablets-e-g-HP-Slate-7/ADB-drivers/td-p/2574571
Click to expand...
Click to collapse
I did flash the modified update.zip but CWM doesn't give me the option to re-write the recovery partition. I go straight to "Install from sdcard complete". How is that re-write done?
*Update* All done - Had to select NO to questions on reboot (Replace recovery and root). Thanks so much - back to stock 4.2.2
Belmichel said:
I did flash the modified update.zip but CWM doesn't give me the option to re-write the recovery partition. I go straight to "Install from sdcard complete". How is that re-write done?
*Update* All done - Had to select NO to questions on reboot (Replace recovery and root). Thanks so much - back to stock 4.2.2
Click to expand...
Click to collapse
See my HP Slate 7 Extreme Root post: http://forum.xda-developers.com/showthread.php?t=2850893
What am I supposed to open updater-script with?
---------- Post added at 03:47 AM ---------- Previous post was at 03:31 AM ----------
Robo_Leader said:
First, nope, you'll still get freezing. I've tried all the ROMs.
Second, If you want to go back to HP's recovery, do the following:
Create a copy of update.zip and navigate to META-INF\com\google\android and open up updater-script
Delete the first three lines.
Transfer your new update.zip to your device and flash. Allow it to re-write the recovery partition.
NOTE THAT YOUR DEVICE WILL NOT ADVANCE PAST THE BOOT ANIMATION. THIS IS NORMAL.
Copy the original update.zip to a SD card and insert it into the device.
Now go to the HP recovery partition that now exists on your device and follow HP's restore instructions.
You're done, the stock 4.2.2 that came with your device is now installed.
Had to figure this out the hard way after I lost my original backup.
To the original poster, you can get it to work, but you need to make modifications to the script's fastboot commands (they will require "fastboot -i 0x03F0" before they will do anything) and you will need to setup your machine for ADB with the Slate 7 Extreme. It won't work out of the box, you can find support for that here: http://h30434.www3.hp.com/t5/Android-Tablets-e-g-HP-Slate-7/ADB-drivers/td-p/2574571
Click to expand...
Click to collapse
---------- Post added at 04:25 AM ---------- Previous post was at 03:47 AM ----------
I downloaded a script editor and deleted the first three lines of updater script but it still fails to flash.
Finally success!
Robo_Leader said:
First, nope, you'll still get freezing. I've tried all the ROMs.
Second, If you want to go back to HP's recovery, do the following:
Create a copy of update.zip and navigate to META-INF\com\google\android and open up updater-script
Delete the first three lines.
Transfer your new update.zip to your device and flash. Allow it to re-write the recovery partition.
NOTE THAT YOUR DEVICE WILL NOT ADVANCE PAST THE BOOT ANIMATION. THIS IS NORMAL.
Copy the original update.zip to a SD card and insert it into the device.
Now go to the HP recovery partition that now exists on your device and follow HP's restore instructions.
You're done, the stock 4.2.2 that came with your device is now installed.
Had to figure this out the hard way after I lost my original backup.
To the original poster, you can get it to work, but you need to make modifications to the script's fastboot commands (they will require "fastboot -i 0x03F0" before they will do anything) and you will need to setup your machine for ADB with the Slate 7 Extreme. It won't work out of the box, you can find support for that here: http://h30434.www3.hp.com/t5/Android-Tablets-e-g-HP-Slate-7/ADB-drivers/td-p/2574571
Click to expand...
Click to collapse
I have the 4450 extreme and one the things that was a little different- is that I had put the update zip on the sd card prior and it did the update on its own... WEIRD but acceptable! rooted and on 4.4.2- thanks man!
I didn't have any luck doing it this way. I ended up getting there by a slightly different avenue.
My s7e was totally non functional beyong fastboot and recovery mode being operational. I ended up downloading tegratools 2.2. Using the fastboot included in that I unlocked my boot loader with fastboot by the command
Code:
fastboot -i 0x03F0 oem unlock
(The '-i 0x03F0' is a code relating to the specific model, apparently without this the tablet will ignore your command. Please also remember that the unlock factory resets the tablet.)
It may be overboard again, but I also formatted all the system partitions
Code:
fastboot -i 0x03F0 erase boot
fastboot -i 0x03F0 erase system
fastboot -i 0x03F0 erase userdata
fastboot -i 0x03F0 erase cache
fastboot -i 0x03F0 erase preinstall
fastboot -i 0x03F0 reboot
I uploaded cwm recovery from the above version of tegratools to my s7e as it seems a bit more forgiving with signatures than the stock recovery. I used that to upload a version of update.zip with the "assert" lines removed from META-INF\com\google\android\updater-script. I also self signed the .zip to reduce the likelyhood of my upload being rejected by the tablet, it may not be needed, but I did it anyway.
Code:
adb sideload slate7update-signed.zip
when completing the firmware flash, apparently there is a common problem of the kernel not flashing correctly when recovery takes place and giving an "Error 7", this is the problem I think you solved by re-writing the unmodified firmware (but that didn't work for me)
Anyway I had to fix it by dropping back to fastboot and flashing it to "staging", which puts the kernel in a placeholder until the next boot, at which point the kernel will be written to the correct spot. Because of this writing to the correct partition, you will notice a quick double-boot as the updated kernel is written to the correct point in firmware.
Code:
fastboot -i 0x03F0 flash staging "c:\fastboot-s7e\blob"
I hope this helps.
Oh and to those curious, the beats version appears incompatible with the standard s7e, I tried modifying a rom in the same way as above and it just went to a blank screen. My guess is they've done some form of sanity check in the kernel, given that every "beats" version I've read about in tablets has been a software-only modification. I've not bothered trying to use the beats version rom with the s7e kernel, I'll leave that for someone else to try in greater depth as I'm just happy that I got everything working again.
references:
Fastboot (previously this): This is a copy of the twrp/cwm roms as well as fastboot & adb taken from tegratools 2.2 mentioned above.
SignApk (Previously this): The java files and self signing certificate I used to sign the .zip file. It was actually a bit of a pain to find a working signapk.jar that had the valid certificates included, most were broken in one way or another when trying to sign on ubuntu 12.04.
slate7update-signed.zip (previously this): A signed copy of update.zip with META-INF\com\google\android\updater-script modified to remove the assert validation lines sanity checks, be careful with this, you could nuke your tablet if you use it on an incompatible bit of hardware.
guide.txt (previously this): A full how-to with a number of things I've omitted from this response.
To those wondering, I collated the above procedure from a dozen different links on a good four or five websites, including a number of threads here on XDA. Thank you to anyone out there that contributed to the information I found, you really made my day so much better in being able to recover my tablet.
It Worked! But...
mike-s said:
I didn't have any luck doing it this way. I ended up getting there by a slightly different avenue.
My s7e was totally non functional beyong fastboot and recovery mode being operational. I ended up downloading tegratools 2.2. Using the fastboot included in that I unlocked my boot loader with fastboot by the command
Code:
fastboot -i 0x03F0 oem unlock
(The '-i 0x03F0' is a code relating to the specific model, apparently without this the tablet will ignore your command. Please also remember that the unlock factory resets the tablet.)
It may be overboard again, but I also formatted all the system partitions
Code:
fastboot -i 0x03F0 erase boot
fastboot -i 0x03F0 erase system
fastboot -i 0x03F0 erase userdata
fastboot -i 0x03F0 erase cache
fastboot -i 0x03F0 erase preinstall
fastboot -i 0x03F0 reboot
I uploaded cwm recovery from the above version of tegratools to my s7e as it seems a bit more forgiving with signatures than the stock recovery. I used that to upload a version of update.zip with the "assert" lines removed from META-INF\com\google\android\updater-script. I also self signed the .zip to reduce the likelyhood of my upload being rejected by the tablet, it may not be needed, but I did it anyway.
Code:
adb sideload slate7update-signed.zip
when completing the firmware flash, apparently there is a common problem of the kernel not flashing correctly when recovery takes place and giving an "Error 7", this is the problem I think you solved by re-writing the unmodified firmware (but that didn't work for me)
Anyway I had to fix it by dropping back to fastboot and flashing it to "staging", which puts the kernel in a placeholder until the next boot, at which point the kernel will be written to the correct spot. Because of this writing to the correct partition, you will notice a quick double-boot as the updated kernel is written to the correct point in firmware.
Code:
fastboot -i 0x03F0 flash staging "c:\fastboot-s7e\blob"
I hope this helps.
Oh and to those curious, the beats version appears incompatible with the standard s7e, I tried modifying a rom in the same way as above and it just went to a blank screen. My guess is they've done some form of sanity check in the kernel, given that every "beats" version I've read about in tablets has been a software-only modification. I've not bothered trying to use the beats version rom with the s7e kernel, I'll leave that for someone else to try in greater depth as I'm just happy that I got everything working again.
references:
Fastboot: This is a copy of the twrp/cwm roms as well as fastboot & adb taken from tegratools 2.2 mentioned above.
SignApk: The java files and self signing certificate I used to sign the .zip file. It was actually a bit of a pain to find a working signapk.jar that had the valid certificates included, most were broken in one way or another when trying to sign on ubuntu 12.04.
slate7update-signed.zip: A signed copy of update.zip with META-INF\com\google\android\updater-script modified to remove the assert validation lines sanity checks, be careful with this, you could nuke your tablet if you use it on an incompatible bit of hardware.
guide.txt: A full how-to with a number of things I've omitted from this response.
To those wondering, I collated the above procedure from a dozen different links on a good four or five websites, including a number of threads here on XDA. Thank you to anyone out there that contributed to the information I found, you really made my day so much better in being able to recover my tablet.
Click to expand...
Click to collapse
I was able to unlock my bootloader using the above method and it worked. My s7e rebooted and everything was working normally. I loaded the bootloader again to go in and do a cache wipe and my 3 year old bumped into me as I was holding down the volume+ and power buttons. Now I'm stuck in ADX mode (black screen but recognized by my pc, have tried connecting to charger, volume+ and power, volume - and power, nothing works) . I've read that Advent has released adx files for the Vega Note 7 and you can use Tegra Note 7 Super Tools to restore the Nvidia Note 7. I'm wondering if I can use the update.zip file and the nvflash files from Nvidia to restore my tablet from ADX mode.
Any suggestions?
Mike-S, Thanks for the in depth how-to. I tried to sell my Extreme 4450 and the guy that I sold it to said when he received it was in boot loop. I got it back and it is indeed the one I sent him, however, now I have a bricked tab that doesn't even allow fastboot. I have, like others tried calling HP, tried installing per you instruction and finally considered just throwing away or selling. I almost seems like the recovery was wiped... I can get to uploading from SD and have tried using your info to accomplish with no success. Any suggestions? I hate to smash it or try and sell if I can fix it.
Thank you in advance for anyone's help
som1special2 said:
however, now I have a bricked tab that doesn't even allow fastboot. I have, like others tried calling HP, tried installing per you instruction and finally considered just throwing away or selling.
Click to expand...
Click to collapse
Damn, I'm sorry to say that I'm unsure if i'll be able to help much or at all. All i can suggest is look and see if there is any pre-boot subsystem that connects to your pc via usb, similar to the mediatek "preboot mt65xx" which can sort of provide a last gasp chance of recovery.
help with ROM
Hi there,
Need desperate help. I followed the instructions here but ended up with no OS in the s7e. I kept on trying to install a signed ROM via ADB, it reaches 100% senidng but always failed inside TWRP. Not succesful even with CWM. I even tried installing from SD card but no success. Please help, thank you.
Anyone still around here?
Mike S ... not sure you (or anyone else) is paying any attention to this thread anymore (and the HP Slate 7 Extreme at this point is a fairly old device) ... but I can't get any of these methods to work and my S7E (model 4450) is basically useless right now. When cold (i.e. not booted up in prior 30mins or so), I can boot it normally, but within about 10mins, it will "crash" to the all-white HP splash screen and will never recover. Holding the power button just has it go through initial startup, get to the white HP splash screen, and sit there until the battery runs down. I haven't been able to root it yet, so the bootloader still shows "locked". What's ironic is that this device is really all I need -- I don't play high-end games and mostly just stream shows -- but now it's completely unusable. I'm not sure which is easier ... trying to get this to root or just buying something else?
So far, to root, I've tried towelroot and Cydia Impactor, but both of those returned errors as others have reported. I tried following the steps that Mike S put up here, but without my tablet being rooted, adb and fastboot don't even detect my device from the PC (though the PC detects it because I'm able to see it in Windows Explorer and drag files to the storage) ... so it seems like I can't even get to install CWM or anything further.
Maybe the right thing to do is just to dump the paperweight ... it used to work so well but about 6 months ago this stupid HP white screen crash started happening, and since then it's become a regular thing that only takes about 10 mins (at most) before it craps out. I can get to the bootloader and onboard recovery mode, but that doesn't let me load anything.
Not sure where to go next but any advice would be appreciated!
--AJ
MGrad92 said:
Mike S ... not sure you (or anyone else) is paying any attention to this thread anymore (and the HP Slate 7 Extreme at this point is a fairly old device) ... but I can't get any of these methods to work and my S7E (model 4450) is basically useless right now. When cold (i.e. not booted up in prior 30mins or so), I can boot it normally, but within about 10mins, it will "crash" to the all-white HP splash screen and will never recover. Holding the power button just has it go through initial startup, get to the white HP splash screen, and sit there until the battery runs down. I haven't been able to root it yet, so the bootloader still shows "locked". What's ironic is that this device is really all I need -- I don't play high-end games and mostly just stream shows -- but now it's completely unusable. I'm not sure which is easier ... trying to get this to root or just buying something else?
So far, to root, I've tried towelroot and Cydia Impactor, but both of those returned errors as others have reported. I tried following the steps that Mike S put up here, but without my tablet being rooted, adb and fastboot don't even detect my device from the PC (though the PC detects it because I'm able to see it in Windows Explorer and drag files to the storage) ... so it seems like I can't even get to install CWM or anything further.
Maybe the right thing to do is just to dump the paperweight ... it used to work so well but about 6 months ago this stupid HP white screen crash started happening, and since then it's become a regular thing that only takes about 10 mins (at most) before it craps out. I can get to the bootloader and onboard recovery mode, but that doesn't let me load anything.
Not sure where to go next but any advice would be appreciated!
--AJ
Click to expand...
Click to collapse
Get your device drivers right (try androidsdk if it's still not getting recognised) and fastboot the stock system images (fastboot is not root dependent). By the way why were you trying those weird rooting methods ??? Just flash supersu from cwm/twrp and be done with it.
Thanks ... I'll try androidsdk. I actually am a root n00b and so I was trying to figure out the simplest way to go. I guess I guessed wrong! But of course before I can get that working I need the right drivers ... So I'll try that first. I was thinking the drivers were OK since my PC recognized the S7E when Android loaded (before it crashed to the white screen).
Couldn't get androidsdk to work
Hello again... I never could get androidsdk to work. My computer never recognized the tablet to be able to fastboot. *sigh* As much as I hate to give up, I don't know what else to do.... I might try another PC?
Looking for update.zip for S7E
mike-s said:
I didn't have any luck doing it this way. I ended up getting there by a slightly different avenue.
My s7e was totally non functional beyong fastboot and recovery mode being operational. I ended up downloading tegratools 2.2. Using the fastboot included in that I unlocked my boot loader with fastboot by the command
Code:
fastboot -i 0x03F0 oem unlock
(The '-i 0x03F0' is a code relating to the specific model, apparently without this the tablet will ignore your command. Please also remember that the unlock factory resets the tablet.)
It may be overboard again, but I also formatted all the system partitions
Code:
fastboot -i 0x03F0 erase boot
fastboot -i 0x03F0 erase system
fastboot -i 0x03F0 erase userdata
fastboot -i 0x03F0 erase cache
fastboot -i 0x03F0 erase preinstall
fastboot -i 0x03F0 reboot
I uploaded cwm recovery from the above version of tegratools to my s7e as it seems a bit more forgiving with signatures than the stock recovery. I used that to upload a version of update.zip with the "assert" lines removed from META-INF\com\google\android\updater-script. I also self signed the .zip to reduce the likelyhood of my upload being rejected by the tablet, it may not be needed, but I did it anyway.
Code:
adb sideload slate7update-signed.zip
when completing the firmware flash, apparently there is a common problem of the kernel not flashing correctly when recovery takes place and giving an "Error 7", this is the problem I think you solved by re-writing the unmodified firmware (but that didn't work for me)
Anyway I had to fix it by dropping back to fastboot and flashing it to "staging", which puts the kernel in a placeholder until the next boot, at which point the kernel will be written to the correct spot. Because of this writing to the correct partition, you will notice a quick double-boot as the updated kernel is written to the correct point in firmware.
Code:
fastboot -i 0x03F0 flash staging "c:\fastboot-s7e\blob"
I hope this helps.
Oh and to those curious, the beats version appears incompatible with the standard s7e, I tried modifying a rom in the same way as above and it just went to a blank screen. My guess is they've done some form of sanity check in the kernel, given that every "beats" version I've read about in tablets has been a software-only modification. I've not bothered trying to use the beats version rom with the s7e kernel, I'll leave that for someone else to try in greater depth as I'm just happy that I got everything working again.
references:
Fastboot: This is a copy of the twrp/cwm roms as well as fastboot & adb taken from tegratools 2.2 mentioned above.
SignApk: The java files and self signing certificate I used to sign the .zip file. It was actually a bit of a pain to find a working signapk.jar that had the valid certificates included, most were broken in one way or another when trying to sign on ubuntu 12.04.
slate7update-signed.zip: A signed copy of update.zip with META-INF\com\google\android\updater-script modified to remove the assert validation lines sanity checks, be careful with this, you could nuke your tablet if you use it on an incompatible bit of hardware.
guide.txt: A full how-to with a number of things I've omitted from this response.
To those wondering, I collated the above procedure from a dozen different links on a good four or five websites, including a number of threads here on XDA. Thank you to anyone out there that contributed to the information I found, you really made my day so much better in being able to recover my tablet.
Click to expand...
Click to collapse
Hey Mike, you wouldn't still happen to have that signed update.zip since you've don't have it on Dropbox anymore?
Hello to everybody, so i was thinking my nakasi was really dead this time, the last thing i did was flashing a 5.1.1 rom next when i rebooted got stuck on lolipop boot loop so i restarted the tablet
manually to access the recovery, and to my awe, i couldn't no more access the recovery ! (latest twrp) tried again and again nothing, no recovery no bootloader, can't start the OS
always stuck on google logo with the options above, start, bootloader, recovery etc, today i realized i could access the bootloader and fastboot mode (ADB recognize my device when i type fastboot devices)
so i tried flashing stock image and stuff with no luck, tried many stock roms, tried wug's toolkit and the flash all.bat still no luck, i get all kind of error messages here is a screenshot, help is really appreciated if there is anything i can do to save it :
View attachment 3305126
the problem seems to be that i can't write the things i send to the tablet via ADB, tried the NVflash recovery today and got :
View attachment 3306049
Have you tried not imputing the full file address as you have the emulator already running from that location.
So recovery command would be.
Fastboot flash recovery "name of recovery Img file here"
Just make sure that the image file is in the platform-tools folder.
Probably not your issue but its going to save you some typing.
Good luck
gaosphappy said:
Have you tried not imputing the full file address as you have the emulator already running from that location.
So recovery command would be.
Fastboot flash recovery "name of recovery Img file here"
Just make sure that the image file is in the platform-tools folder.
Probably not your issue but its going to save you some typing.
Good luck
Click to expand...
Click to collapse
Thank you for the tip I'll certainly use it, but i don't think it is the culprit since as you can see in the screenshots
the files get sent successfully but cannot be written, my bootloader is unlocked by the way
Homurato said:
Thank you for the tip I'll certainly use it, but i don't think it is the culprit since as you can see in the screenshots
the files get sent successfully but cannot be written, my bootloader is unlocked by the way
Click to expand...
Click to collapse
Did you try the latest factory image? I noticed you are flashing a very old bootloader, possibly the first one? 4.23 is the current version.
Where is flatline_grouper.img coming from? I've never seen that.
adomol said:
Did you try the latest factory image? I noticed you are flashing a very old bootloader, possibly the first one? 4.23 is the current version.
Where is flatline_grouper.img coming from? I've never seen that.
Click to expand...
Click to collapse
Hello kind sir, of course at first i tried the 5.1.1 full factory image with the NRT toolkit and got the same writing errors next i tried many bootloaders
(one of them found it here as a 100% working bootloader) the Flatline is the recovery of the NVflash tool where you can access it to unbrick full bricked N7s
if you got blobs.bin of your N7 backed up (clearly not my case)
the flashing writing error i get it with everything i try to flash, recoverys bootloader system etc
when i send them with the flash all command they got sent to the tablet okay, but when writing i get the errors
i don't know but there is a small informations if that can help, before it broke my system was in EXT4 and all the rest in F2FS
It's entirely possible your memory has failed. I'm reading more and more people running into corrupted memory issues.
You can get a replacement motherboard cheap on eBay if nothing else works.
fwayfarer said:
It's entirely possible your memory has failed. I'm reading more and more people running into corrupted memory issues.
You can get a replacement motherboard cheap on eBay if nothing else works.
Click to expand...
Click to collapse
I'm still hoping for a software solution since my fastboot works fine, I'll let the motherboard solution my last i guess
Hello some news about the still staggering situations : when the tablet is off and i put the charger i get the battery refiling animation ! so that mean the bootloader isn't broken
and i still can access fastboot mode, even when i push a bootloader i get a signature match message, but the problem is still that the things i push can't be written as i'm still getting a :
FAILED <Remote: <FileWriteFailed>> changed usb cables, changed ports, the last time the tablet was working i had the system on EXT4 and the rest on F2FS, maybe if i can convert everything to EXT4 ?
I followed step by step: https://clickitornot.com/install-twrp-recovery-and-root-sony-xperia-x-compact/
(the xda guides lingo was hard to understand and follow, I'm a noob at rooting sony phones. I don't have previous knowledge so I followed the above)
-Got stuck in TWRP recovery mode after following the link posted.
-Looked into it and read something about a boot.img missing?
-Downloaded boot.img from here: https://forum.xda-developers.com/x-compact/how-to/stock-8-0-root-recovery-t3747479
-Flashed recovery on boot_32.img via TWRP, now screen stays at white Sony logo. Cannot go into TWRP at all, computer doesn't recognize phone and Sony flash tools does not recognize phone.
I just need this phone to root and turn on so I can get my old photos and conversation back. :crying:
Been stuck for 12 hours...any help is much appreciated!
1 - what do you ultimately want, rooted stock rom, custom rom, or...?
2 - what was the state of your phone when you started, (fully stock, which fw version, etc)?
3 - Did you do anything else to it besides flashing twrp and flashing boot.img?
levone1 said:
1 - what do you ultimately want, rooted stock rom, custom rom, or...?
2 - what was the state of your phone when you started, (fully stock, which fw version, etc)?
3 - Did you do anything else to it besides flashing twrp and flashing boot.img?
Click to expand...
Click to collapse
1. Anything, I simply just need it to work so I can use a software to get my lost data. In order to get my data back the phone needs to be rooted under the prerequisites for the Dr. Fone software.
2.Fully stock android 8.0
3. No, it was fine and I went through dozens of threads and youtube tutorials. It kept going into TWRP exclusively until I flashed boot.img now it just boot loops or crashes on the white sony screen.
(BTW, my phone finally has been recognized by Flash Tools (Emma). I have updated it via Emma but it has done absolutely nothing.
ThisAintEz said:
1. Anything, I simply just need it to work so I can use a software to get my lost data. In order to get my data back the phone needs to be rooted under the prerequisites for the Dr. Fone software.
2.Fully stock android 8.0
3. No, it was fine and I went through dozens of threads and youtube tutorials. It kept going into TWRP exclusively until I flashed boot.img now it just boot loops or crashes on the white sony screen.
(BTW, my phone finally has been recognized by Flash Tools (Emma). I have updated it via Emma but it has done absolutely nothing.
Click to expand...
Click to collapse
So the whole Emma process completed successfully, but the phone still won't boot? That's strange, because Emma usually overrides everything, (including your userdata, I think, so if you wanted to save it, that may have been the wrong thing to do). If all you did was flash a bad boot img, then re-flashing stock fw should solve the problem, but you might lose your data with Emma, so Androxyde Flashtool might be better choice, since it gives you the option.
Did you unlock the bootloader? If not, then nothing is going to work. If you did, then it will be easy to get the phone booted again...
levone1 said:
So the whole Emma process completed successfully, but the phone still won't boot? That's strange, because Emma usually overrides everything, (including your userdata, I think, so if you wanted to save it, that may have been the wrong thing to do). If all you did was flash a bad boot img, then re-flashing stock fw should solve the problem, but you might lose your data with Emma, so Androxyde Flashtool might be better choice, since it gives you the option.
Did you unlock the bootloader? If not, then nothing is going to work. If you did, then it will be easy to get the phone booted again...
Click to expand...
Click to collapse
The phone itself has been factory reset (long story short x compact said my password was incorrect and factory reset, itself after numerous tries, even though I only have one password) so I know my info is gone but the software can get the most of the things I want.
Yes, boot loader is unlocked. I have basically rooted it but the last step of actually getting to use it is out of reach.
ThisAintEz said:
The phone itself has been factory reset (long story short x compact said my password was incorrect and factory reset, itself after numerous tries, even though I only have one password) so I know my info is gone but the software can get the most of the things I want.
Yes, boot loader is unlocked. I have basically rooted it but the last step of actually getting to use it is out of reach.
Click to expand...
Click to collapse
For TWRP recovery, you need to flash via fastboot. I wasn't clear what you were saying about how you did it before. You should,
- Download TWRP img file (there is official TWRP for xc, so download the latest from TWRP site)
- Open command prompt in the directory you downloaded it to
- Connect the phone in fastboot mode, (power off > hold volume up while connecting cable and don't let go of the button until you see blue led)
- Type
Code:
fastboot flash recovery (name of file).img
Then you can boot into recovery by powering off, and holding volume down while powering on. Then do a reset in recovery.
Now you'll need to flash a boot img...
You said it was stock 8.0, but do you know if it was the latest update? (fw ending in. 118) If so, and if your system files are still intact, then you should be able to download this - https://mega.nz/#!14VkzCCB!GK-KEv0A-ZyhysXc1-IusyJjJEB-D5ZWOLm1DRt31tA - (it's a boot img), and flash it with fastboot. So,
- Download the boot img file
- Open a command prompt in the directory you downloaded it
- Connect the phone in fastboot mode, (power off > hold volume up while connecting cable and don't let go of the button until you see blue led)
- Type in command prompt,
Code:
fastboot flash boot (name of file).img
- Reboot
I'm assuming that since you used Emma already that you have drivers installed, so should work. If the commands complete successfully, but your phone still doesn't boot, then probably system is messed up, and you'll have to flash a new rom.
levone1 said:
For TWRP recovery, you need to flash via fastboot. I wasn't clear what you were saying about how you did it before. You should,
- Download TWRP img file (there is official TWRP for xc, so download the latest from TWRP site)
- Open command prompt in the directory you downloaded it to
- Connect the phone in fastboot mode, (power off > hold volume up while connecting cable and don't let go of the button until you see blue led)
- Type
Code:
fastboot flash recovery (name of file).img
Then you can boot into recovery by powering off, and holding volume down while powering on. Then do a reset in recovery.
Now you'll need to flash a boot img...
You said it was stock 8.0, but do you know if it was the latest update? (fw ending in. 118) If so, and if your system files are still intact, then you should be able to download this - https://mega.nz/#!14VkzCCB!GK-KEv0A-ZyhysXc1-IusyJjJEB-D5ZWOLm1DRt31tA - (it's a boot img), and flash it with fastboot. So,
- Download the boot img file
- Open a command prompt in the directory you downloaded it
- Connect the phone in fastboot mode, (power off > hold volume up while connecting cable and don't let go of the button until you see blue led)
- Type in command prompt,
Code:
fastboot flash boot (name of file).img
- Reboot
I'm assuming that since you used Emma already that you have drivers installed, so should work. If the commands complete successfully, but your phone still doesn't boot, then probably system is messed up, and you'll have to flash a new rom.
Click to expand...
Click to collapse
Thank you, the good news is I can finally get back into TWRP, so that's a relief! I appreciate you for saving me there!
I followed the instructions with the boot.img with the following script
max download size of 536870912 bytes
sending 'boot' (17220 KB)...
OKAY [ 0.556s]
writing 'boot'...
OKAY [ 0.113s]
finished. total time: 0.673s
But I'm back to square one with the screen prompt "your devices has been unlocked and cant be trusted. Your device will boot in 5 sec" with the Sony white screen back to the "your device has been unlocked" screen and then it freezes at the Sony white screen. The only way i can turn off my phone from here is Power button + volume up
ThisAintEz said:
Thank you, the good news is I can finally get back into TWRP, so that's a relief! I appreciate you for saving me there!
I followed the instructions with the boot.img with the following script
max download size of 536870912 bytes
sending 'boot' (17220 KB)...
OKAY [ 0.556s]
writing 'boot'...
OKAY [ 0.113s]
finished. total time: 0.673s
But I'm back to square one with the screen prompt "your devices has been unlocked and cant be trusted. Your device will boot in 5 sec" with the Sony white screen back to the "your device has been unlocked" screen and then it freezes at the Sony white screen. The only way i can turn off my phone from here is Power button + volume up
Click to expand...
Click to collapse
So now you can just decide if you want to go the route of stock rom or custom. Quickest choice to get the phone booted would probably be Omni or something. Just download the rom, download the oem file, and flash in fastboot. Check the Omni threads in "Roms" forum... If you wanted to go stock, I would suggest Androxyde Flashtool, but would be a few more steps... Or you could try Emma again...
levone1 said:
So now you can just decide if you want to go the route of stock rom or custom. Quickest choice to get the phone booted would probably be Omni or something. Just download the rom, download the oem file, and flash in fastboot. Check the Omni threads in "Roms" forum... If you wanted to go stock, I would suggest Androxyde Flashtool, but would be a few more steps... Or you could try Emma again...
Click to expand...
Click to collapse
I tried Emma again but my phone is still frozen on the white Sony screen. I checked out the ROM threads but the "download weekly" links are down for both Pie 9.0 and Oreo 8.1
ThisAintEz said:
I tried Emma again but my phone is still frozen on the white Sony screen. I checked out the ROM threads but the "download weekly" links are down for both Pie 9.0 and Oreo 8.1
Click to expand...
Click to collapse
Strange - I wonder what's going on... I might have a zip I can upload. Meanwhile, maybe try Lineage - https://forum.xda-developers.com/x-compact/development/rom-lineageos-16-0-xperia-x-compact-t4080903
levone1 said:
Strange - I wonder what's going on... I might have a zip I can upload. Meanwhile, maybe try Lineage - https://forum.xda-developers.com/x-compact/development/rom-lineageos-16-0-xperia-x-compact-t4080903
Click to expand...
Click to collapse
Thank you for your help! I checked out the thread but I'm not advanced enough to understand the steps without it being written out as I'm still new to this. Is their any links or tutorials you would recommend? My apologies!
ThisAintEz said:
Thank you for your help! I checked out the thread but I'm not advanced enough to understand the steps without it being written out as I'm still new to this. Is their any links or tutorials you would recommend? My apologies!
Click to expand...
Click to collapse
- Download the zip - https://drive.google.com/open?id=14iXmvLOMXLoZdJoCahcRhBzbUr1Eu7gw (There are 2 options, just pick one - one's a little newer)
- Copy to phone's SD card
- Boot to recovery
- Choose "wipe data/factory reset"
- Choose "install", and select the zip file you downloaded
- Reboot
There are more options, but I think you want to just get the phone to boot at this point. You can do more later if you want...
BTW - what is happening when you flash with Emma? I haven't seen it ever flash successfully, but not work on the phone. Are you getting errors?
levone1 said:
- Download the zip - https://drive.google.com/open?id=14iXmvLOMXLoZdJoCahcRhBzbUr1Eu7gw (There are 2 options, just pick one - one's a little newer)
- Copy to phone's SD card
- Boot to recovery
- Choose "wipe data/factory reset"
- Choose "install", and select the zip file you downloaded
- Reboot
There are more options, but I think you want to just get the phone to boot at this point. You can do more later if you want...
BTW - what is happening when you flash with Emma? I haven't seen it ever flash successfully, but not work on the phone. Are you getting errors?
Click to expand...
Click to collapse
Much appreciated! I will try that out soon. Regarding Emma it seems pretty useless, unless I'm missing something. Every time I use it, it says it's successful but nothing changes.
LEVONE1 YOU ARE THE MAN!!! I cannot thank you enough! It worked! You made my day, I appreciate your patience and willingness to help a stranger out even when you didn't have to!
ThisAintEz said:
LEVONE1 YOU ARE THE MAN!!! I cannot thank you enough! It worked! You made my day, I appreciate your patience and willingness to help a stranger out even when you didn't have to!
Click to expand...
Click to collapse
Glad to hear it... It's been done for me more than once, so....
Maybe your happy with Lineage, but if you're feeling ambitious, you can start messing around with Androxyde Flashtool, and getting back to stock, and you can try my eXistenZ port - https://forum.xda-developers.com/x-compact/themes/existenz-xc-t3867917 - I think eXistenZ is the best rom for this phone, (probably for Sony phones overall). The downside is that it is based on stock, so no updates since 2018 for XC...
The processes are a bit more complicated, so might take some time / learning to get it down, but with TWRP, you can always make a quick backup, and flash right back to where you were any time...
levone1 said:
Glad to hear it... It's been done for me more than once, so....
Maybe your happy with Lineage, but if you're feeling ambitious, you can start messing around with Androxyde Flashtool, and getting back to stock, and you can try my eXistenZ port - https://forum.xda-developers.com/x-compact/themes/existenz-xc-t3867917 - I think eXistenZ is the best rom for this phone, (probably for Sony phones overall). The downside is that it is based on stock, so no updates since 2018 for XC...
The processes are a bit more complicated, so might take some time / learning to get it down, but with TWRP, you can always make a quick backup, and flash right back to where you were any time...
Click to expand...
Click to collapse
Will do. Cheers!