CM 6 To CM7 X10 - XPERIA X10 General

Hello,
Simple inquiry with regards to flashing the new CM7 RC4 to Xperia X10a
Device is currently on CM 6.1.3. I have downloaded flash tool as baseband version is .55
I wanted to confirm the proper protocol in order to accomplish a successful flash. Having read through the posts/tutorials I've gathered I will need to flash the lower grade baseband version .52 via flash tool.
As my device is currently on modded firmware would I need to flash back to 2.1 utilizing flash tool. Whats confusing me here is the mentioning that the baseband and kernel is included in the CM7 download file. Q/A for flash tool states it can flash original images 1.6>2.1. As I am currently on 2.2 how does this impact flashing of the appropriate baseband in order to upgrade to CM7.
Furthermore if the baseband is included in the ROM file download. Does that implicate a one step process via flash tool for successful flash to CM7. Would I need an original firmware file to work in tandem with the custom rom via flash tool? Or must I flash baseband seperate from ROM
Any clarification is much appreciated.
Thanks everyone
** Flashed over as per suggested instruction. Experiencing random reboot incidents with CM7
Reviewing online information with regards to a fix. Device is randomly power cycling when left idle and when Browser application is launched from dock bar or app drawer.
Any ideas or implementations for a fix would be appreciated as this is quite frustrating.
- Ive noticed that the instructions for rom installation state to allow the device an idle period of a minute before having it go through an automatic power cycle. however this doesnt seem to happen. upon first boot as soon as i attempt to turn on wifi, the phone will automatically boot itself. speculating that wifi may be involved with the above mentioned incident. still researching.
- Attempted reflash. Skip past initial google setup. Activate Wifi, authenticate with a network. Reboot and disconnect from wifi. Reboot to xrec, fix permissions. Unsuccessful. Same result.
- Installed wififix in apps folder. Same result. Phone will power cycle when downloading apps from market via wifi.

I think the same baseband file is included in the rom's zip file.
first use flashtool to go to .52 baseband then flash the rom in xrecovery.
Sent from my X10i using XDA Premium App

1- go here http://forum.xda-developers.com/showthread.php?t=960527
download 2.0.52
2- install 2.0.52 via flashtool
3- go here http://forum.xda-developers.com/showpost.php?p=10561990&postcount=2
download the rar file
4- extract update.zip , gapps.zip from the rar file
5- using xrecovery flash update.zip reboot then flash gapps.zip

thanks everyone
as per DynamicRam. procedure worked successfully. did want to be absolutely sure to avoid any mishaps, bad flashes, or bricking of device.
thanks again

Reflashed ROM and gapps within same session. Same issue being experienced. Will attempt another flash.

Related

basic ways to resolve boot loop stuck phones

if you are stuck in boot loop or having difficulty starting your phone, don't worry, there should be a way.
I have experienced this issue today after flashing wrong file causing my phone to stuck in boot loop. after searching in this forum and after spending over 3 hours, I finally managed to restore my phone and it is now working perfectly fine.
therefore, I thought of making a basic guide to try to resolve such issues. please note, this is a very basic guide to resolve problems with starting your phone, I am not professional but will try to share my experience and help anyone in need. this was done on X10i
lets start:
1- if you have a recent back up and have access to xrec, you can simply restore your phone
2- if you have access to xrec but don't have a backup, try to flash a new ROM
I tried the previous two steps but it kept saying can't mount SD, therfore try the following
3- if you don't have xrec access, use the flash tool
download from here http://www.multiupload.com/7H4JT35B6G
then flash generic 2.1 to your x10, I used this one http://www.mediafire.com/?sqv6274anzfzn2x
here is the guide on how to do it http://forum.xda-developers.com/showpost.php?p=10879528&postcount=3
I have had problem saying "install or re-install drivers", you just need to install the file in the drivers folder in the flash tool main folder and restart the flash tool program
4- after flashing this ROM, restart your phone and root it using the flash tool, after the root your phone will restart, then you need to ask for premession and click xrec to install xrec to your phone
5- before installing new ROM, please make sure that your baseband and karnel is compatible with it (because the ROM you flashed earlier has old karnel and you will be stuck again in the boot loop if you flashed 2.3.3 just like me, then you will need to start again and install new karnel before instaling 2.3.3 ROM or even restore 2.3.3 ROM)
(you can simply install the new ROM then restart in flash mode and flash the new karnel .71 or flash the karnel and restore your backup)
I know that my choices of flash tool version or generic 2.1 version might not be the best, but I used them and resolved my issue and hope it will resolve yours. for any question please do not hesitate to ask me.
credits to everyone who helped, I can't remember everyone because I read quite a lot so please forgive me
nice post my friend
In flash tool I'm getting an error:
ERROR - USB\VID_0FCE&PID_ADDE\5&2BFAB030&0&5
any idea what to do?
it sounds to me that u may need to install the semc flash drivers.. inside the flashtool u may find a folder named drivers, go inside of that folder and install ggsetup.. also do u have pc companion installed?
tripico said:
In flash tool I'm getting an error:
ERROR - USB\VID_0FCE&PID_ADDE\5&2BFAB030&0&5
any idea what to do?
Click to expand...
Click to collapse
can you post the log from the flash tool so I can see at which step exactly this massage came up
I am fairly novice when it comes to flashing so here's a pretty dumb question:
I have an X10a, can I use the X10i software that you've linked in your post or is it just going to brick my phone.

MOTOACTV ROMs

Rooting and updating your MotoActv is about to get significantly easier! No more waiting games for developers to update their ROMs or tools when Motorola pushes a new OTA; now you can do it yourself! I honestly have not seen these types of files ANYWHERE else, so I had to create these myself (with quite a bit of help from [mbm]). But enough blabbing, here are the files and how to use them:
(Note: all these methods assume we have full fastboot access! -- Which we still have at this point)
- Stock Images:
These are not just mere update.zips that you might be accustomed to elsewhere in Android. Nor are these mere fxzs that you might be accustomed to elsewhere with newer Motorola devices. They are in fact both and more. There are 3 main ways to flash these files onto your device, giving you options based on what OS you run and how comfortable you are flashing files to your device.
1) FXZ:
- Operating System: Windows
- Requires: RSD Lite with FXZ Support
- Instructions: Simply load up the file as any standard fxz (it is very straight-forward)
2) Recovery:
- Operating System: Anything that can mount your device
- Requires: The ability to get into recovery
- Instructions: Place the file on the sdcard, boot into recovery, flash as normal
- Note: Recovery does not wipe your device, it is suggested that you do so before flashing stock images
3) Fastboot:
- Operating System: Windows/Linux/Mac
- Instructions (Windows): Unpack the zip, run flash-all.bat (if it fails, run as administrator)
- Instructions (Linux/Mac): Unpack the zip, run flash-all.sh (it should already have proper permissions)
Miscellaneous Images:
These miscellaneous images are nothing you haven't seen before at this point, but their purposes are new, so they too require explanation.
1) AnyRoot:
AnyRoot is based on koush's AnyKernel in the sense that it unpacks and repacks the boot.img on the fly. However, as the name suggests, AnyKernel is meant for kernels, while AnyRoot, actually roots the device on the fly. This will work on any MotoActv device. It is flashed as a normal update.zip and everything is done in the background so you won't noticed much. However, for ease of access, the stock and rooted boot.img is exported to your sdcard in /sdcard/recovery/. Also note, that if you happen to flash AnyRoot over an already rooted device, nothing will happen as it has built-in error checking.
2) rebootRecovery:
rebootRecovery is another fxz type zip, the same as the stock and rooted images, except it can't be flashed in recovery (would be a little redundant don't you think?). This flashes a specially made misc.img by [mbm] that tells the device to reboot into recovery from boot. This means you can flash AnyRoot on any stock device.
How Tos / FAQs:
Now that you know what the files do, I can explain in short steps how to use these files to get what you want:
1) How to Return the Device to Stock?
- flash a stock image using any of the 3 methods
- you can now update via Motocast if you so wish
2) How to Root a Stock Device?
- update your device via Motocast to the latest version (suggested)
- place AnyRoot on your sdcard
- boot into fastboot, and flash rebootRecovery using either of the 2 methods
- flash AnyRoot in recovery
- reboot
3) How do I update my Rooted Device?
- flash a stock image using any of the 3 methods
- update your device via Motocast to the latest version
- place AnyRoot on your sdcard
- boot into fastboot, and flash rebootRecovery using either of the 2 methods
- flash AnyRoot in recovery
- reboot
Q: After using rebootRecovery I can't get out of recovery!?
A: You are using an old recovery that doesn't clear the 'reboot-recovery' command; use the newer recovery: https://dl.dropbox.com/u/5849675/android/f100/CWMR5x_F100_recoveryB2.img
Q: What do these ROM offer over other custom ROMs?
A: Nothing, they are simply stock images, but you can upgrade with them.
Q: How much battery should I have when I flash?
A: Performing any kind of these flashes will drain at least 10% of your battery, I wouldn't suggest you flash below 60% ESPECIALLY IF YOU FLASH rebootRecovery!
Q: What happens if I flash a 16gb zip on my 8gb or visa-versa?
A: Don't freak, it will still boot, but it's not the best thing in the world to do, just go back and flash the correct model zip.
Q: Can I extract the images from your zips and flash them my own way?
A: yep (couldn't really think of anything else to say)
Q: I manually flashed the stock-boot.img from AnyRoot, and now I can't update. Why?!
A: The boot.imgs need to be truncated before they can be flashed to correctly work with Motorola's updates, just use the stock images.
Q: What's next?
A: HyprActv -- What's this?
Stock Images (w/ md5sums):
8gb-NA: https://dl.dropbox.com/u/5849675/android/f100/MA_1710_8GB_NA.zip (5e228bf56a67aced012c8cbb2d7f7c76)
16gb-NA: https://dl.dropbox.com/u/5849675/android/f100/MA_1710_16GB_NA.zip (21b067dc629f7ccd18b43799d8d5fb17)
8gb-EU: https://dl.dropbox.com/u/5849675/android/f100/MA_1710_8GB_EU.zip (5b79a46d87728303fc2c920eec71c2e8)
Miscellaneous Images (w/ md5sums:
AnyRoot: https://dl.dropbox.com/u/5849675/android/f100/MA_AnyRoot.zip (2f867b006da42865ef861094db0eb6e6)
Reboot Recovery: https://dl.dropbox.com/u/5849675/android/f100/MA_RebootRecovery.zip (1623c9c61462db9bb20b55bc8f1144aa)
Mirror (thanks Iownox!): http://www.androtransfer.com/?developer=lownox&folder=MotoACTV
This is Reserved.
I rooted and flashed in recovery (the stock 4.55.97 and the the rooted version 4.55.97) and I stay on 4.55.78 no matter what! The flashes go through successfully... But nothing has changed and the System version still says 4.55.78... But like I said, the flashes both completed! I did a factory reset... and the updater-script wipes system, so what could be my issue?
Moose8106 said:
I rooted and flashed in recovery (the stock 4.55.97 and the the rooted version 4.55.97) and I stay on 4.55.78 no matter what! The flashes go through successfully... But nothing has changed and the System version still says 4.55.78... But like I said, the flashes both completed! I did a factory reset... and the updater-script wipes system, so what could be my issue?
Click to expand...
Click to collapse
It sounds like you flashed that old boot.img. Do you have the battery percentage in the status bar? According to TheEndGame7 that is another surefire way to tell if you are on 4.55.97, if you used any of the root tools, it's possible that they automatically flash the old boot.img.
CEnnis91 said:
It sounds like you flashed that old boot.img. Do you have the battery percentage in the status bar? According to TheEndGame7 that is another surefire way to tell if you are on 4.55.97, if you used any of the root tools, it's possible that they automatically flash the old boot.img.
Click to expand...
Click to collapse
I think I did flash the old boot.img (root tools :O ). I'll try flashing the modified boot img again. Thanks! I had no idea the root tool took me back to the old boot img
Moose8106 said:
I think I did flash the old boot.img (root tools :O ). I'll try flashing the modified boot img again. Thanks! I had no idea the root tool took me back to the old boot img
Click to expand...
Click to collapse
Yes, any and all tools that exist so far will need to be updated.
I wiped data / cache and used recovery (b) to install the rooted-4.55.97 zip and didn't have any luck either. I did not use the root tools to flash. Also wiped dalvik cache after and fastboot -w for fun.
innovatelife said:
I wiped data / cache and used recovery (b) to install the rooted-4.55.97 zip and didn't have any luck either. I did not use the root tools to flash. Also wiped dalvik cache after and fastboot -w for fun.
Click to expand...
Click to collapse
Did you end up doing any restore of some kind after you flashed?
Update
There are "new" instructions that might fix the issue where the rooted 4.55.97 appears to not flash. Simply wipe the boot.img image before you flash. And don't use the root tools until they are updated.
Also, if you have success, please post it. Usually "Thanks, it works" is annoying, but in this case where I don't have the device, I need to make sure this is working on some level.
I formated everything from recovery, now I got stuck with Moto logo with no animation when it starts, how to get out of this?
NA
Is there any mirrors for the download of these roms? the dropbox links are down
NORCALkID said:
Is there any mirrors for the download of these roms? the dropbox links are down
Click to expand...
Click to collapse
They were pulled, they're not working. There has been some form of mis-communication when I did my testing. I am not working on these until I can get the device from utkanos. Check Update 2, in the initial post.
Success
CEnnis91
I was lucky the second time, first time I succeeded to upgrade to rooted 4.55.97 but for some reason I didn't get the battery percentage on the status bar but all other issues are OK and status indicated version number 4.55.97, I repeated flash from recovery but after wiping and remounting all folders, this time for stock 4.55.97
Now I'm on stock 4.55.97 with battery percent on status bar and syncing from my mac.
thanks CEnnis91
NA
I went into recovery>mounts, and didn't see any wipe for boot. I took a shot at system since I had already wiped cache and data. Didn't seem to help either. Tried 'fastboot erase boot" and re-flashed. No go. Couldn't start back up the device at all. Tried flashing the latest rooted image using "fastboot flash boot boot.img". No go.
I messed around trying to get the device to boot back up for a while, but it won't even charge right. Only charges long enough to kick off the Motorola 'M', and that is it. On attempts at loading fastboot, I just keep getting an error saying that the battery is low. I know I can only blame myself for this. No fastboot access and no adb access. All attempts at resetting the device have failed.
Before I attempted all of this, my battery was full. Unfortunately, wouldn't charge anymore even plugged into the wall. Any ideas?
Hopefully nobody else makes my mistake.
Man I can't wait till this is perfect, you guys are fricken awesome. I raped your thanks buttons op lol
MoPhoACTV Initiative
Will be working on this tonight. I just found out how to make the flash script clear cache and dalvik for you, pre-install. That'll probably save some headache, but it works only in edify format. Not sure what the stock recovery uses...
Anyways, I'm home!
ClearD said:
Will be working on this tonight. I just found out how to make the flash script clear cache and dalvik for you, pre-install. That'll probably save some headache, but it works only in edify format. Not sure what the stock recovery uses...
Anyways, I'm home!
Click to expand...
Click to collapse
All recoveries will now use edify, amend is old and depreciated, you will only find that on old devices.
Corrupt Kernel...
innovatelife said:
I went into recovery>mounts, and didn't see any wipe for boot. I took a shot at system since I had already wiped cache and data. Didn't seem to help either. Tried 'fastboot erase boot" and re-flashed. No go. Couldn't start back up the device at all. Tried flashing the latest rooted image using "fastboot flash boot boot.img". No go.
I messed around trying to get the device to boot back up for a while, but it won't even charge right. Only charges long enough to kick off the Motorola 'M', and that is it. On attempts at loading fastboot, I just keep getting an error saying that the battery is low. I know I can only blame myself for this. No fastboot access and no adb access. All attempts at resetting the device have failed.
Before I attempted all of this, my battery was full. Unfortunately, wouldn't charge anymore even plugged into the wall. Any ideas?
Hopefully nobody else makes my mistake.
Click to expand...
Click to collapse
This is a classical case of a corrupt Kernel. Not that the images are corrupt, but somewhere along your update, your boot.img did not install the kernel properly and now you have a broken power manager within kernel.
What I would do is the following:
Hook your watch to the charger and let the M sign show up.
Even if it hangs on the M, leave your watch hooked over night.
Try downloading an older image and use fastboot to erase everything and then flash everything back again. This should return your watch to a working state again.
You may then choose to customize it as you see fit.
Root tool > "return to stock"
Sent from my HTC Inspire 4G using XDA-funded carrier pigeons
simx said:
CEnnis91
I was lucky the second time, first time I succeeded to upgrade to rooted 4.55.97 but for some reason I didn't get the battery percentage on the status bar but all other issues are OK and status indicated version number 4.55.97, I repeated flash from recovery but after wiping and remounting all folders, this time for stock 4.55.97
Now I'm on stock 4.55.97 with battery percent on status bar and syncing from my mac.
thanks CEnnis91
NA
Click to expand...
Click to collapse
I'm about to try this.. but it's making me think... Do you think the updater-script doesn't correctly format system? Think about it... our devices say 4.55.97 (mine changed to that after a reboot or two), and we only had partial features... sounds like something isn't wiping correctly.

Newbie guide for installing a Custom ROM in SGP312 Sony Xperia Tablet Z

The objective of this post is to explain how to currently install a custom ROM in our device. (for total newbies like me, you can also refer -among others- to my previous post). I give the general procedure which wipes everything in your device, but you can check various precious posts in xda that variate this procedure.
The codename for our device is "pollux_windy", which is the Wifi-only version. The LTE version (I should probably get the LTE!) is "pollux" and I suppose the general procedure (with the corresponding firmwares to your specific device) will work for any Xperia device. You can also get the general idea from this post.
As a general rule of thumb do not forget after/before every firmware flashing to:
Enable developer mode (explained here)
Enable the USB Debugging mode (explained here)
Trust installation from unknown sources (explained here)
Steps.
A. Unlock the bootloader.
You can refer here and then check that it is successfully unlocked with these steps (taken from here ):
Open the Contacts app.
Click the menu button.
Click Settings.
Long press (for about 5 seconds) somewhere in the empty space just above status bar, as indicated by the red frame in the screenshot below, and then release your finger. A button named Enter service code will then appear in the same area (this may take a few tries).
Click Enter service code. A dialler will appear.
Dial *#*#7378423#*#* . Then go to -> "Service Info" -> "Configuration". If there is:
Bootloader unlock allowed - Yes << this means that your Bootloader is Locked
Bootloader Unlocked - Yes << this means that your bootloader is unlocked
B. Flash a firmware in which you will root the device
Download/install FlashTool.
Download and place to the FlashTool's folder "firmwares" the firmware "SGP312_10.5.A.0.230_VMo UK_IE.ftf". More information here . In sort, download and extract http://d-h.st/MrI and http://d-h.st/ULc
Open FlashTool and connect the powered-off device (USB cable) in Flashmode, holding the Volume Down button while you plugin the usb cable. The FlashTool should say that it is connected in Flashmode. Then flash the 10.5.A.0.230 firmware in it.
C. Gain root to the new firmware
Open the device, complete the setup wizard and connect to a wireless network. You do not have to setup the Google Account since you can download every application googling the respective APK files, but Google Play is easier to use.
Get (click λ) the towelroot APK, install it and run it (click "make it rain"). You should have root, which you can check with a Root Cheker like this one.
Download/Install SuperSU APK (this is actively developed, while SuperUser is abandoned at the moment) as described here.
D. Install a Recovery to easily flash new ROMs
NUT has done excellent work with XZDualRecovery.Follow the instructions for installing it in his thread. In short:
Download the installer, run it and follow its instructions.
Select SuperSU and of course grant access to your computer from your tablet (watch the tablet screen).
E. Download a Custom ROM and Google Apps
I had problems with Cyanogenmod (versions 11 and 12) that I cannot explain. I had no GPS and no media sound from the speakers, but I did have "notifications" sound! I could listen to "media" sounds using headphones, though. So I tried the nightly OmniROM which seems very stable and fast at the moment, with no sound problems and also has a working GPS! You can get it directly from their site (the NIGHTLY I downloaded is omni-4.4.4-20150223-pollux_windy-NIGHTLY.zip which runs just fine). Somewhere I read that PacMan ROM - also works perfectly but I have not tested it yet.
I had device recognition problems from the Recoveries ("Status 7 Error") that I think dear NUT will solve promptly. What I did to solve them is
Upack the ROM zip.
Remove the first line (from assert(...); till the column) of META_INF/com/google/android/updater-script and save the file.
repack the ROM to a zip.
Then copy this zip to your external SD card. If you need google apps (you probably do, to use Google Play instead of other applications like Aptoide), you will also need to download and place to your external SD card the corresponding google apps from here - (I found it in this post - which also explains the different gapps versions)
F. Install the Custom ROM
So now that both the ROM and (optionally) gapps are in the device's SD card:
Enter the Recovery while repeatedly pressing Volume Up or Down while the device boots.
Wipe everything (except the external SD card, obviously --- if you delete the zip files by mistake you must begin again from step B. using the FlashTool to flash the *.230* ftf).
Reboot and setup/enjoy your new ROM.
It seemed that with OmniROM I had lost root access so I had to reinstall SuperSU. I did this by downloading the flashable/installable zip - and flashing/installing it through the recovery.
In the end a did a full backup with the TWRP recovery and one with Titanium backup
Magnus_E said:
The objective of this post is to explain how to currently install a custom ROM in our device. (for total newbies like me, you can also refer -among others- to my previous post). I give the general procedure which wipes everything in your device, but you can check various precious posts in xda that variate this procedure.
Click to expand...
Click to collapse
For installing customs (CM/AOSP/GPe based ROM's), you don't need to install .230 firmware, furthermore you don't need root (except for backup TA procedure), furthermore you don't need XZDualRecovery (cause it works only for Stock and Custom STOCK based rom's - see this post).
So you you only need to flash kernel via fastboot, and then enter recovery (integrated in kernel), and install .zip with custom, SuperSU and Gapps from there.
hello i was following this guide but im stuck on status 7 error, i tried deleting assert but the twrp recovery dont get any answer to "getprop ro.product.device" and it just doesnt proceed...
and Rootk1t i cant find any kernels flashable via fastboot or flashtool can you point one to me? all of the kernels i see are in '.zip's .... i want to have android 6.0 so i think i should have black kernel but how?
bluealef said:
hello i was following this guide but im stuck on status 7 error, i tried deleting assert but the twrp recovery dont get any answer to "getprop ro.product.device" and it just doesnt proceed...
and Rootk1t i cant find any kernels flashable via fastboot or flashtool can you point one to me? all of the kernels i see are in '.zip's .... i want to have android 6.0 so i think i should have black kernel but how?
Click to expand...
Click to collapse
.zips are installed through recovery, .ftf through flashtool.
6.0.1 ROM you can find here.

finally custom rom for lg g3 d858hk

hey guys i found custom ROM for d858hk version which is here
http://bbs.gfan.com/android-7892224-1-1.html
can be translated through Google but we need someone to explain to us in details.
I might able to help, I can read Chinese
let me know if you want any explanations.
it's based on lollipop 20d
- v1.0 LED not working, and this v2.0 fixed the problem
- rooted, superSU v2.46
- once you flashed the ROM, no need to flash the ROOT again
- busybox is in the system and no app not there
- works on D857 858 and 858HK
- it's a LIGHT version, there are functions that are deleted, like weather widget for example
- including deleted app inside the ROM, and could recover yourself
- app can write data to external SD card
- split view works for 3rd party app
- smart cover function removed, user can download the "deleted app" and put back into the system to get it working
deleted apps
http://pan.baidu.com/s/1mg86X6o
HOW TO FLASH
FOR D858HK
1. ROOT
2. install TWRP 2.8.1.0
3 Reboot to TWRP 2.8.1.0 and upgrade it to 2.8.5.1
4. Flash ROM using this newest TWRP
D857 and D858
1. ROOT
2. download build.prop.zip, extract, using ES explorer to replace the one in "system" folder
3 flash D858HK 's TOT (http://bbs.gfan.com/android-7502599-1-1.html)
4.install TWRP 2.8.1.0
5. Reboot to TWRP 2.8.1.0 and upgrade it to 2.8.5.1
6. Flash ROM using this newest TWRP
Do "double wipe" after flashing the ROM, otherwise might have FC messages
Thanks alot i think this will help ...will try it now
but can we install twrp when in lollipop as i am now on lollipop
any ideas?
maybe these
http://bbs.gfan.com/android-7677473-1-1.html
one click Recovery installation
need to be rooted
1. extract files to computer
2 connect phone
3 turn on usb debugging
4. run Recovery.bat
---------------------------------------
old temp way, didn't say if it works on L or only KK
http://bbs.gfan.com/android-7727191-1-1.html
So...can any of you fluent Chinese speakers/readers help with the actual downloading of the ROM? It seems the rom is available at http://pan.baidu.com/s/1mg86X6o, but I get a little overloaded and can't figure out how to download from there. It seems to want me to log in, but I can't figure out if there's a non-login download ability lurking somewhere?
Do you have some screenshoots ?
Two things. First, I had the wrong link before. Correct one is: http://pan.baidu.com/s/1sjoKe4l. Second, I realized the reason is that the zip file is over 1GB and they force you to a "download butler". So the login thing is related to copying that file into your (QQ, for example) account and then you could download the file from there.
If anyone with a D858HK is interested, I was able to install this custom rom on my phone without any problems. I followed steps elsewhere to root (the one click version) and install TWRP. The rom is basically a slim version of the standard lollipop rom. If you end up deciding to install this, be aware that the Google Contact Sync app is not included within the rom and you'll need to also download the "deleted apps" zip file mentioned in the same post (link in OP). In the "deleted apps" zip, you'll want to grab the Gooogle Contact Sync apk and install that ... otherwise you can't get your contacts copied to the new rom. There were a bunch of other apks, but this one the only one so far that seemed like it shouldn't have been removed from the rom.
FYI, here are the version details of the rom:
Android version: 5.0.1
Baseband version: MPSS.DI.3.0.c6.2-00011-M8974AAAAANAZM-1
Kernel version: 3.4.0
Build number: (some chinese)1121561(more chinese)
Software version: D858HK20d-HKG-XX
So in total its not worth installing it? But anyway, thanks for your report!
silencer1979 said:
So in total its not worth installing it? But anyway, thanks for your report!
Click to expand...
Click to collapse
I guess that depends on how easy it is to remove LG's bloatware and whether or not you need all/any of it. I personally didn't care for it anyway. But yeah, other than that, nothing special about the rom.
There were a bunch of other apks, but this one the only one so far that seemed like it shouldn't have been removed from the rom.
i believe there's a thread somewhere in this forum (http://bbs.gfan.com/forum-1508-type-10913.html) regarding d858 MIUI, could someone confirm? Thanks
Edit
twrp flashh from MM
has anyone successfully flashed TWRP from an MM rom i tried it and i got bricked and i cant seem to find one for MM only for LP
Lg g3 d858hk
Hey, did you install? There is a problem or not? All programs worked fluently?
xdax1 said:
let me know if you want any explanations.
it's based on lollipop 20d
- v1.0 LED not working, and this v2.0 fixed the problem
- rooted, superSU v2.46
- once you flashed the ROM, no need to flash the ROOT again
- busybox is in the system and no app not there
- works on D857 858 and 858HK
- it's a LIGHT version, there are functions that are deleted, like weather widget for example
- including deleted app inside the ROM, and could recover yourself
- app can write data to external SD card
- split view works for 3rd party app
- smart cover function removed, user can download the "deleted app" and put back into the system to get it working
deleted apps
http://pan.baidu.com/s/1mg86X6o
HOW TO FLASH
FOR D858HK
1. ROOT
2. install TWRP 2.8.1.0
3 Reboot to TWRP 2.8.1.0 and upgrade it to 2.8.5.1
4. Flash ROM using this newest TWRP
D857 and D858
1. ROOT
2. download build.prop.zip, extract, using ES explorer to replace the one in "system" folder
3 flash D858HK 's TOT (http://bbs.gfan.com/android-7502599-1-1.html)
4.install TWRP 2.8.1.0
5. Reboot to TWRP 2.8.1.0 and upgrade it to 2.8.5.1
6. Flash ROM using this newest TWRP
Do "double wipe" after flashing the ROM, otherwise might have FC messages
Click to expand...
Click to collapse
My LG-D858HK phone hard bricked:
What happened/how I hard bricked the phone. I'd already rooted the phone with Marshmallow and then tried to flash phone TWRP by (mistakenly) using https://play.google.com/store/apps/details?id=b007.autorecd858hk when it hard bricked the phone. Now, the phone screen is black/blank and blue/red LED light flashing.
In addition, my PC doesn't recognise phone when plugged into USB port/s. Pop-up on PC screen says; “The last USB device you connected to this computer malfunctioned and windows do not recognize it.” And in Device Manager, I see a ‘yellow triangle’ next to LGE Platform Android Composite USB Device Driver.
I tried different methods to go into download mode and I’m not sure if any worked. Because, obviously, I can’t see anything on the phone screen to carry out procedures to fix phone in download mode. Moreover, I’m not even sure if the phone goes into download mode apart from a sound made from PC and the pop-up straight after.
PC always recognised phone when plugged into USB port/s before it was hard bricked.

TWRP, Rooting and Custom Rom HELP SM-T510 Tablet Tab A 10.1

Hey guys, this is my first post. I just bought a Samsung SM-T510 and would like to unlock all the features. I'm currently trying to follow multiple guides on how to do so. To my understanding, my best bet is lineageOs 16. I've been following https://forum.xda-developers.com/gal...-16-0-t3987317 alongside with https://forum.xda-developers.com/gal...howto-t3989361 and I'm pretty confused on the method order i need to follow. What I mean is do I install rom first, TWRP, Magisk etc.?
More guides ive been following:
https://forum.xda-developers.com/gal...-10-1-t3934805
https://forum.xda-developers.com/app...mless-t3473445
https://topjohnwu.github.io/Magisk/i...system-as-root
I see posts saying I need and don't need Multidisabler so I'm confused on what I actually need: https://forum.xda-developers.com/gal...ption-t3963020
Another one: https://forum.xda-developers.com/gal...ption-t3919714
https://forum.xda-developers.com/gal...eries-t3918699
I have so many tabs open currently; I know I'm missing a few important ones.
So given all that info, i think i have all the software to do this between kernels, rom, twrp, odin, magisk, multi disabler? and i think thats all.
My sm-t510 build number is T510XXU2ASK5, looking through the lineage rom guide, I click the link https://samfrew.com/model/SM-T510/ and i see different versions. I'm honestly completely confused about this file and how I'm going to use it. I understand it to be the stock rom? as in factory software? With TWRP too, the numbers don't match my current build number leaving me very confused.
Do I need to downgrade my build number (i don't know if it's even a thing just asking)?
I think i can do everything relatively easy once I have an understanding of what to do first (order of things) and the specific files for the specific steps. When I'm reading these guides, I honestly have no idea which download goes for what. For ex. going back to https://forum.xda-developers.com/gal...-16-0-t3987317 like what do I need to download, the build number listed in notes regarding kernel or go to the download section right below and use that? Or both and if both, how do I use them separately for there a specific purpose? I cannot find anything that makes me feel comfortable rooting/custom rom on my device. Not comfortable in terms of I don't know what I'm doing exactly. I have put days of reading into this and still, I cannot figure out how to do this. I would really appreciate it if someone could help me. This is stressing me out and I would like to get this done before Monday due to me having some serious surgery. The reason being; I won't be as fresh on everything I've read recently.
I'm sorry if this post is choppy and all over the place. I'm just exhausted and clueless at this point. If I left any info out in order for someone to help me please let me know so I can provide it.
EDIT: The TWRP file ends in build number SK1, the file lineage-16.0-20191019-UNOFFICIAL-T510XXU2ASI4.tar.md5 doesn't match the TWRP file as well as my current build number; which ends in SK5. So nothing is matching the 3 last characters in my build number across all guides besides the samfrew link.
Also, I keep seeing i need a .tar TWRP file for recovery (?) but when I unzip both files are .img (named boot/recovery)
You don’t unzip the .tar files. Keep them as is.
secretwolf98 said:
You don’t unzip the .tar files. Keep them as is.
Click to expand...
Click to collapse
I don't get a .tar file until I unzip the folder; I get a filed with .tar.md5
My recommendation would be to first upgrade to T510XXS2ASK1 of the OEM firmware, since that's the latest version for which Samsung has published kernel source. Use the latest release of Odin and install BL, AP and HOME_CSC. After this, unlock the bootloader and prevent VaultKeeper from relocking it by always enabling Debugger Options while connected to the Internet after a factory wipe.
From there, you could just install TWRP, install the latest MultiDisabler, and live with the Samsung firmware. You could even install Magisk to root. However, I prefer a clean Google OS without all the OEM bloatware, so I'd recommend installing the latest Nexus Stock (which includes TWRP and the custom kernel that disables Knox boot security features). Again, use Odin and install it to AP and do a factory wipe in TWRP because file-based encryption is still unsupported on these custom ROMs.
You could install LineageOS instead, but I haven't yet updated that for T510XXS2ASK1. I've just been busy and Andy hasn't been releasing any new LineageOS 16 GSIs. We're also pretty close to releasing a LineageOS 17 build.
fountainb234 said:
I don't get a .tar file until I unzip the folder; I get a filed with .tar.md5
Click to expand...
Click to collapse
Just rename the file cutting off the .md5.
is it possible to downgrade from sk5 to sk1? you cannot upgrade to a later version, and I know downgrading can have reverse effects on the tablet. I have same tablet I would like to know. if I flash sk1 is there a way to fix it if it bricks?
Magendanz said:
My recommendation would be to first upgrade to T510XXS2ASK1 of the OEM firmware, since that's the latest version for which Samsung has published kernel source. Use the latest release of Odin and install BL, AP and HOME_CSC. After this, unlock the bootloader and prevent VaultKeeper from relocking it by always enabling Debugger Options while connected to the Internet after a factory wipe.
From there, you could just install TWRP, install the latest MultiDisabler, and live with the Samsung firmware. You could even install Magisk to root. However, I prefer a clean Google OS without all the OEM bloatware, so I'd recommend installing the latest Nexus Stock (which includes TWRP and the custom kernel that disables Knox boot security features). Again, use Odin and install it to AP and do a factory wipe in TWRP because file-based encryption is still unsupported on these custom ROMs.
You could install LineageOS instead, but I haven't yet updated that for T510XXS2ASK1. I've just been busy and Andy hasn't been releasing any new LineageOS 16 GSIs. We're also pretty close to releasing a LineageOS 17 build.
Click to expand...
Click to collapse
fountainb234 said:
Hey guys, this is my first post. I just bought a Samsung SM-T510 and would like to unlock all the features. I'm currently trying to follow multiple guides on how to do so. To my understanding, my best bet is lineageOs 16. I've been following https://forum.xda-developers.com/gal...-16-0-t3987317 alongside with https://forum.xda-developers.com/gal...howto-t3989361 and I'm pretty confused on the method order i need to follow. What I mean is do I install rom first, TWRP, Magisk etc.?
More guides ive been following:
https://forum.xda-developers.com/gal...-10-1-t3934805
https://forum.xda-developers.com/app...mless-t3473445
https://topjohnwu.github.io/Magisk/i...system-as-root
I see posts saying I need and don't need Multidisabler so I'm confused on what I actually need: https://forum.xda-developers.com/gal...ption-t3963020
Another one: https://forum.xda-developers.com/gal...ption-t3919714
https://forum.xda-developers.com/gal...eries-t3918699
I have so many tabs open currently; I know I'm missing a few important ones.
So given all that info, i think i have all the software to do this between kernels, rom, twrp, odin, magisk, multi disabler? and i think thats all.
My sm-t510 build number is T510XXU2ASK5, looking through the lineage rom guide, I click the link https://samfrew.com/model/SM-T510/ and i see different versions. I'm honestly completely confused about this file and how I'm going to use it. I understand it to be the stock rom? as in factory software? With TWRP too, the numbers don't match my current build number leaving me very confused.
Do I need to downgrade my build number (i don't know if it's even a thing just asking)?
I think i can do everything relatively easy once I have an understanding of what to do first (order of things) and the specific files for the specific steps. When I'm reading these guides, I honestly have no idea which download goes for what. For ex. going back to https://forum.xda-developers.com/gal...-16-0-t3987317 like what do I need to download, the build number listed in notes regarding kernel or go to the download section right below and use that? Or both and if both, how do I use them separately for there a specific purpose? I cannot find anything that makes me feel comfortable rooting/custom rom on my device. Not comfortable in terms of I don't know what I'm doing exactly. I have put days of reading into this and still, I cannot figure out how to do this. I would really appreciate it if someone could help me. This is stressing me out and I would like to get this done before Monday due to me having some serious surgery. The reason being; I won't be as fresh on everything I've read recently.
I'm sorry if this post is choppy and all over the place. I'm just exhausted and clueless at this point. If I left any info out in order for someone to help me please let me know so I can provide it.
EDIT: The TWRP file ends in build number SK1, the file lineage-16.0-20191019-UNOFFICIAL-T510XXU2ASI4.tar.md5 doesn't match the TWRP file as well as my current build number; which ends in SK5. So nothing is matching the 3 last characters in my build number across all guides besides the samfrew link.
Also, I keep seeing i need a .tar TWRP file for recovery (?) but when I unzip both files are .img (named boot/recovery)
Click to expand...
Click to collapse
without reading answers i can say that im with YOU! Im almost 3 days to root my T510! We must RAMDISK YES in Magisk but to do that we need to extract recovery.img (https://www.droidwin.com/install-magisk-in-recovery-root-android/) from stock original ROM T510OXM5CUJ1 and Im stucked at the part NORAMDISK trying to patch recovery.img with Magisk Manager (with recovery mode checked) but i only get the "waiting for device in ADB" and I conect disconect USB C and nothing...Still NO RAMDISK...
I used 3 different ROMS but no lucky and tried with firmware CUJ1 but no lucky again. Without "NORAMDISK: YES" no root...stucked. But i saw a T510 with OrangeFOX!
framC0 said:
without reading answers i can say that im with YOU! Im almost 3 days to root my T510! We must RAMDISK YES in Magisk but to do that we need to extract recovery.img (https://www.droidwin.com/install-magisk-in-recovery-root-android/) from stock original ROM T510OXM5CUJ1 and Im stucked at the part NORAMDISK trying to patch recovery.img with Magisk Manager (with recovery mode checked) but i only get the "waiting for device in ADB" and I conect disconect USB C and nothing...Still NO RAMDISK...
I used 3 different ROMS but no lucky and tried with firmware CUJ1 but no lucky again. Without "NORAMDISK: YES" no root...stucked. But i saw a T510 with OrangeFOX!
Click to expand...
Click to collapse
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file. You can flash the Nexus ROM without first flashing anything else but the latest CUL1 (not CUJ1) stock ROM. Nexus includes both TWRP and gapps. The only time you have to patch things to get Magisk installed is when you are trying to root a stock ROM instead of a custom ROM. Custom ROMs always to the patching for you.
lewmur said:
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file. You can flash the Nexus ROM without first flashing anything else but the latest CUL1 (not CUJ1) stock ROM. Nexus includes both TWRP and gapps. The only time you have to patch things to get Magisk installed is when you are trying to root a stock ROM instead of a custom ROM. Custom ROMs always to the patching for you.
Click to expand...
Click to collapse
Wow i will try this today and will post feedback. Are you on Android 11? Thank You!
UPDATE: So...flashed with T510XXU5CUL1...
From OEM stock firmware:
Unlock bootloader -> done
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin --> twrp-3.6.0_11-2-T510XXU5CUL1-20220218.tar ---> this put the tablet into emergency mode... had to do again "Hold Vol Up & Vol Down buttons during restart to enter Download mode" and reflash it again. stucked at this point. cant flash TWRP with that! Maybe this TWRP file its for Android 11.2 and im on 11?
framC0 said:
Wow i will try this today and will post feedback. Are you on Android 11? Thank You!
UPDATE: So...flashed with T510XXU5CUL1...
From OEM stock firmware:
Unlock bootloader -> done
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin --> twrp-3.6.0_11-2-T510XXU5CUL1-20220218.tar ---> this put the tablet into emergency mode... had to do again "Hold Vol Up & Vol Down buttons during restart to enter Download mode" and reflash it again. stucked at this point. cant flash TWRP with that! Maybe this TWRP file its for Android 11.2 and im on 11?
Click to expand...
Click to collapse
You don't need to flash TWRP if you flash https://forum.xda-developers.com/t/...k-for-2019-galaxy-tab-a-10-1-sm-t510.4234889/ TWRP is built into this ROM. After installing stock CUL1, did you boot it, connect to wifi, skip the rest of setup and then enable Dev mode before rebooting to download and flashing from Odin?
edit: Don't attempt to download from the regular download link. Use the link under Build archives that says Android File Host and scroll down till you find the CUL1 md5 file.
lewmur said:
You don't need to flash TWRP if you flash https://forum.xda-developers.com/t/...k-for-2019-galaxy-tab-a-10-1-sm-t510.4234889/ TWRP is built into this ROM. After installing stock CUL1, did you boot it, connect to wifi, skip the rest of setup and then enable Dev mode before rebooting to download and flashing from Odin?
edit: Don't attempt to download from the regular download link. Use the link under Build archives that says Android File Host and scroll down till you find the CUL1 md5 file.
Click to expand...
Click to collapse
AH! So donwloaded Nexus_Stock_CR_T510XXU5CUL1-20220219.tar and put into AP in Odin... and FAIL. Error: "Only official released binaries are allowed". Before i flashed with T510XXU5CUL1 didnt conect wifi and enabled usb debug.
EDIT: i dont have OEM unlock option in DEV but its unlocked, i checked when in downloaded mode it says "lock device and..." so its unlocked.
framC0 said:
AH! So donwloaded Nexus_Stock_CR_T510XXU5CUL1-20220219.tar and put into AP in Odin... and FAIL. Error: "Only official released binaries are allowed". Before i flashed with T510XXU5CUL1 didnt conect wifi and enabled usb debug.
Click to expand...
Click to collapse
You must connect wifi and enable Dev mode before flashing. If, after flashing CUL1, you went through the regular setup routine and put in a Google Account, you must also enable OEM in Dev options.
lewmur said:
You must connect wifi and enable Dev mode before flashing. If, after flashing CUL1, you went through the regular setup routine and put in a Google Account, you must also enable OEM in Dev options.
Click to expand...
Click to collapse
YES!!!!!! YOU ARE THE BEST!!!! Done! It booted directly to TWRP!!! THANK YOU!!!! So now will flash Magisk with twrp right? Alawys rooted my devices but this 510 wow...never saw a thing like this
Edit: The fight continues - So i did wipe and format data in TWRP and reboot system and im IN. Installed Magisk 23.0.apk and noticed that im still with "RAMDISK: no"... Searching how to do next to root! Im very near of the goal!!!! Finally! Big thanks to lewmur!
lewmur said:
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file. You can flash the Nexus ROM without first flashing anything else but the latest CUL1 (not CUJ1) stock ROM. Nexus includes both TWRP and gapps. The only time you have to patch things to get Magisk installed is when you are trying to root a stock ROM instead of a custom ROM. Custom ROMs always to the patching for you.
Click to expand...
Click to collapse
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file.
Click to expand...
Click to collapse
Sorry just one more question im very near. I will flash this Magisk (magisk_patched-24300_tkk90.img) in TWRP or Odin? And is this file from https://forum.xda-developers.com/t/...019-galaxy-tab-a-10-1-sm-t510.4234889/page-18 ?
My brain will explode few days in a row to get it rooted
EDIT: Since an older version dont know witch, Magisk Manager and Magisk are joined in apk so i just flashed Magisk 23.0.apk in TWRP...rooted!!! DONE!!!! FINALLY
framC0 said:
Sorry just one more question im very near. I will flash this Magisk (magisk_patched-24300_tkk90.img) in TWRP or Odin? And is this file from https://forum.xda-developers.com/t/...019-galaxy-tab-a-10-1-sm-t510.4234889/page-18 ?
My brain will explode few days in a row to get it rooted
Click to expand...
Click to collapse
Download latest Magisk from https://magiskapp.com/zip/ and flash with TWRP.
lewmur said:
Download latest Magisk from https://magiskapp.com/zip/ and flash with TWRP.
Click to expand...
Click to collapse
Thank you!! Im facing a problem when connect USB to PC...sometime tablet restarts and sometimes dont appear on PC even in device manager. Did you got this also? Not very important because i will access via FTP. Just to learn...thanks!
framC0 said:
Thank you!! Im facing a problem when connect USB to PC...sometime tablet restarts and sometimes dont appear on PC even in device manager. Did you got this also? Not very important because i will access via FTP. Just to learn...thanks!
Click to expand...
Click to collapse
USB cables are notorious for being flaky. Sometimes it helps to just turn the cable over and plug it back in. I always keep several on hand so that if I have connection problems I can try another cable.

Categories

Resources