Related
Hi,
I traded a phone with someone and the rom they had was acting up.. the Infected Rom (cdma verizon)... When I got the phone, I told him he could keep his SD card and I could keep mine.. i guess the P something image file was on there and now Im just rooted with Teamwin recovery and not able to flash any rom or restore the Infected rom i nandroid backed up.
I have fastboot 1.50 S On but unlocked
Now imma be at work and not have a working phone. This isn't cool. PLEASE GET BACK TO ME IF YOU CAN HELP peeps. I would really appreciate it.
I also tried the unlocking method all over again but the Java SDK wont install.. it tells me to disable my virus protection (I did) and then it says unable to install it. This is just a mess man.
stepinmyworld said:
Hi,
I traded a phone with someone and the rom they had was acting up.. the Infected Rom (cdma verizon)... When I got the phone, I told him he could keep his SD card and I could keep mine.. i guess the P something image file was on there and now Im just rooted with Teamwin recovery and not able to flash any rom or restore the Infected rom i nandroid backed up.
I have fastboot 1.50 S On but unlocked
Now imma be at work and not have a working phone. This isn't cool. PLEASE GET BACK TO ME IF YOU CAN HELP peeps. I would really appreciate it.
I also tried the unlocking method all over again but the Java SDK wont install.. it tells me to disable my virus protection (I did) and then it says unable to install it. This is just a mess man.
Click to expand...
Click to collapse
If you're interested in reverting back to completely stock, the RUU files are available at http://www.goo-inside.me/shooter/ruu . Both the PG86IMG.zip and the .exe files are available there.
Interesting the device is flashed to verizon, at least you mention the device is on CDMA verizon. The only issues I can forsee here will be 3G data/MMS might not work via Verizon if using a stock Sprint ROM.
Of course, these *might* work and they can also be *tweaked* but I doubt, out of the box, they will work. Phone calls and SMS should work over verizon using the stock sprint ROM.
Here is my usual lecture, reading this will save you a lot of time and headache, regarding flashing a ROM and kernels on the EVO 3D with hboot 1.5 and htc's unlock method:
Essentially, if you're looking to flash a kernel or ROM (which many times also include a kernel), there are three basic methods (two seem the easier) with hboot 1.50 and htc's unlock method:
1) For Kernel Flashing: From Android mode, using my application, Flash Image GUI. Put the kernel .zip file on your sdcard, select from inside the application and flash.
For ROM Flashing: Pull out the kernel file (usually named boot.img) out of the ROM .zip and push to sdcard. Flash using Flash Image GUI.
If you're away from a computer and want to flash any kernel, this is a great tool!
2) Load the custom recovery, NOT using the traditional method (reboot recovery, bootloader -> recovery, etc), but a specific method for Hboot 1.5. From the prompt use: fastboot boot c:\downloads\cwm-recovery.img.
This will temporarily boot the custom recovery image and the HTC unlock method will grant it write access to the boot partition while in this mode.
In this temporarily booted recovery mode, when a full ROM (with kernel included) is flashed, the kernel will flash correctly.
3) Boot into recovery using the traditional methods, reboot recovery, bootloader -> recovery, etc, and after the custom recovery has loaded, flash the ROM. Reboot into fastboot mode and then separately flash the kernel from the computer: fastboot flash boot c:\boot.img.
Downside to this method would be if a zImage is included instead of the boot.img for the kernel, won't flash correctly.
Being without a phone is rough now a days! Hope that helps and points in the right direction!
so sorry.. i meant to say CDMA Sprint.. i probably was so frustrated and typed verizon. I am about to read what you post completly.
Thank you so much for the reply! I purchased the GUI App from the market a few days ago and I wasnt sure if it would work on my phone because that PG86IMG.zip wasn't on the root of my SD card (it's on the other guy's sd card) I will try your method to flash a ROM.
I was able to get the Rom restored from the nandroid backup someone last night.. I still need a new rom because this one has touch screen problems. Thanks again
Hi, I have a HTC & Asus transformer TF101 and was blissfully unaware that other android devices have convoluted and complicated root / flash procedures, till I was handed my wife's ST15i to root.
I managed to unlock the bootloader and downgrade from ICS stock to gb .42 firmware and rooted using doomlord's zergrush. Then loaded CWMRto the phone (now on .42 gb rooted stock).
I am stuck from here as anything else I flash (custom Rom, upgrade to ICS) gets me to a soft boot (stuck at SE boot logo) or lose root and CWMR on ICS ROM. The help guides, tutorials etc on this forum or elsewhere do not even tell the keypress or tool to use for fastboot, CWMR or how to enter boitloader / recovery. I am no noob on android, adb and rooting, but working with this phone has brought me to tears!
Is the boot IMG and kernel necessarily flashed separately from the ROM on Xperia phones?
My aim is to get to a rooted ICS, non miui ROM for my wife. Please help and /or guide me to achieve this. At this rate, I feel like giving away my HTC to the wife and exchange the Xperia for a more user friendly phone.....
Sent from my HTC Incredible S
Okay, so:
The kernel is seperated from the rom. If you have unlocked the bootloader you can flash a kernel. In most kernels, cwm is included, so you flash the kernel and then you can boot up. While booting you press the volume down button again and again, to come to cwm. There you can install a zip file, in which the rom is.
Are you really sure the bootloader is unlocked? Did you do it by testpoint or sonys official method?
To flash a kernel, you need the boot.img. Before you start flashing the kernel, put the downloaded zip file of the rom on your sd card.
Then, and I would do it like this cause with the normal command line by windows it's the same, you open sony flash tool. There you click on the flash, select fastboot mode and on the right side there is select kernel to flash. There you choose the boot.img. Then you have to shut down your phone, and while you are holding volume up key, you connect phone to pc. There will light up the blue led and flash tool will automaticly flash the kernel. READ THE LOG BEFORE YOU PLUG OFF DEVICE!! If the log is ok (there are no errors), you can plug off device and turn it on. While booting, you press volume down again and again. Then you have to follow the tutorial to the rom (what has to be formatted or wiped and how to install the rom itself. Cause after flashing the kernel, you must install the rom or your device won't boot up!
Okay, now we could do an example:
If you want an ics rom, I would take cyanogenmod 9. Here's a guide:
Download the zip file from here.
Then you extract the zip file, so you have one packed zip file and one unpacked. The packed zip file you copy to your sd card.
In the unpacked, there's a boot.img. If it isn't named boot.img rename it, so it's name is "boot", but windows detects as an image file.
You open sony flash tool and click on the flash, select fastboot mode and then choose "select kernel to flash". Choose the boot.img (make sure it is named boot and it is an image. In flashtool the image you choose should be named boot) and shut down phone. Hold volume up key that the blue led shines, and the kernel is flashed after seconds. Now see the log, if there's no error, plug off the device and power on. While powering on you press the volume down button again and again.
Now you are in cwm. There I would do a backup first. When the backup has finished, you make a factory reset and wipe cache partition.
Then select install zip from sd card and choose zip. There you choose the cm9 zip you copied to your sd card. If it finished installing (don't power off device while installing, sometimes you could think it stuck, but normally it won't. Just wait and drink a coffee!) you can reboot device and normally it should work.
YOU DO THAT ON YOUR OWN RISK. FOR ME ON MINI PRO IT WORKED, BUT I CAN'T PROMISE!
Hope it works and keep up! In the end you will hopefully enjoy your rom (maybe cm9)
Greets
Michael
---------- Post added at 12:31 PM ---------- Previous post was at 11:34 AM ----------
Michi_optimus_me said:
Okay, so:
The kernel is seperated from the rom. If you have unlocked the bootloader you can flash a kernel. In most kernels, cwm is included, so you flash the kernel and then you can boot up. While booting you press the volume down button again and again, to come to cwm. There you can install a zip file, in which the rom is.
Are you really sure the bootloader is unlocked? Did you do it by testpoint or sonys official method?
To flash a kernel, you need the boot.img. Before you start flashing the kernel, put the downloaded zip file of the rom on your sd card.
Then, and I would do it like this cause with the normal command line by windows it's the same, you open sony flash tool. There you click on the flash, select fastboot mode and on the right side there is select kernel to flash. There you choose the boot.img. Then you have to shut down your phone, and while you are holding volume up key, you connect phone to pc. There will light up the blue led and flash tool will automaticly flash the kernel. READ THE LOG BEFORE YOU PLUG OFF DEVICE!! If the log is ok (there are no errors), you can plug off device and turn it on. While booting, you press volume down again and again. Then you have to follow the tutorial to the rom (what has to be formatted or wiped and how to install the rom itself. Cause after flashing the kernel, you must install the rom or your device won't boot up!
Okay, now we could do an example:
If you want an ics rom, I would take cyanogenmod 9. Here's a guide:
Download the zip file from here.
Then you extract the zip file, so you have one packed zip file and one unpacked. The packed zip file you copy to your sd card.
In the unpacked, there's a boot.img. If it isn't named boot.img rename it, so it's name is "boot", but windows detects as an image file.
You open sony flash tool and click on the flash, select fastboot mode and then choose "select kernel to flash". Choose the boot.img (make sure it is named boot and it is an image. In flashtool the image you choose should be named boot) and shut down phone. Hold volume up key that the blue led shines, and the kernel is flashed after seconds. Now see the log, if there's no error, plug off the device and power on. While powering on you press the volume down button again and again.
Now you are in cwm. There I would do a backup first. When the backup has finished, you make a factory reset and wipe cache partition.
Then select install zip from sd card and choose zip. There you choose the cm9 zip you copied to your sd card. If it finished installing (don't power off device while installing, sometimes you could think it stuck, but normally it won't. Just wait and drink a coffee!) you can reboot device and normally it should work.
YOU DO THAT ON YOUR OWN RISK. FOR ME ON MINI PRO IT WORKED, BUT I CAN'T PROMISE!
Hope it works and keep up! In the end you will hopefully enjoy your rom (maybe cm9)
Greets
Michael
Click to expand...
Click to collapse
That won't work if you have no unlocked bootloader! Do this only if you are sure, the bootloader is unlocked!! If it works, it'd be nice if you could tell me!
Michi_optimus_me said:
Okay, so:
The kernel is seperated from the rom. If you have unlocked the bootloader you can flash a kernel. In most kernels, cwm is included, so you flash the kernel and then you can boot up. While booting you press the volume down button again and again, to come to cwm. There you can install a zip file, in which the rom is.
Are you really sure the bootloader is unlocked? Did you do it by testpoint or sonys official method?
To flash a kernel, you need the boot.img. Before you start flashing the kernel, put the downloaded zip file of the rom on your sd card.
Then, and I would do it like this cause with the normal command line by windows it's the same, you open sony flash tool. There you click on the flash, select fastboot mode and on the right side there is select kernel to flash. There you choose the boot.img. Then you have to shut down your phone, and while you are holding volume up key, you connect phone to pc. There will light up the blue led and flash tool will automaticly flash the kernel. READ THE LOG BEFORE YOU PLUG OFF DEVICE!! If the log is ok (there are no errors), you can plug off device and turn it on. While booting, you press volume down again and again. Then you have to follow the tutorial to the rom (what has to be formatted or wiped and how to install the rom itself. Cause after flashing the kernel, you must install the rom or your device won't boot up!
Okay, now we could do an example:
If you want an ics rom, I would take cyanogenmod 9. Here's a guide:
Download the zip file from here.
Then you extract the zip file, so you have one packed zip file and one unpacked. The packed zip file you copy to your sd card.
In the unpacked, there's a boot.img. If it isn't named boot.img rename it, so it's name is "boot", but windows detects as an image file.
You open sony flash tool and click on the flash, select fastboot mode and then choose "select kernel to flash". Choose the boot.img (make sure it is named boot and it is an image. In flashtool the image you choose should be named boot) and shut down phone. Hold volume up key that the blue led shines, and the kernel is flashed after seconds. Now see the log, if there's no error, plug off the device and power on. While powering on you press the volume down button again and again.
Now you are in cwm. There I would do a backup first. When the backup has finished, you make a factory reset and wipe cache partition.
Then select install zip from sd card and choose zip. There you choose the cm9 zip you copied to your sd card. If it finished installing (don't power off device while installing, sometimes you could think it stuck, but normally it won't. Just wait and drink a coffee!) you can reboot device and normally it should work.
YOU DO THAT ON YOUR OWN RISK. FOR ME ON MINI PRO IT WORKED, BUT I CAN'T PROMISE!
Hope it works and keep up! In the end you will hopefully enjoy your rom (maybe cm9)
Greets
Michael
---------- Post added at 12:31 PM ---------- Previous post was at 11:34 AM ----------
That won't work if you have no unlocked bootloader! Do this only if you are sure, the bootloader is unlocked!! If it works, it'd be nice if you could tell me!
Click to expand...
Click to collapse
Bootloader IS unlocked from SE website. I used the unlocking-relocking toil by quaghi. Wow! So many steps in this phone..... And thanks, CM7/CM9 was also one of my choices, though the wife prefers smulrronic..... Thanks a ton you guys......
Sent from my HTC Incredible S
Tried all methods, flashtool, adb & fastboot commands, and everytime I get to a softbrick/stuck at bootloader.
Facts:
1. Bootloader is unlocked (unlock method SE official). Checked by *#*# SERVICE(7378423) #*#* & got no output.
2. Am able to downgrade to .42 firmware and root that firmware (stock gb).
From that point onwards, when I try to flash a new kernel (boot.IMG), or a custom ICS ROM (smultronic & real ICS 5.2) I end up losing boot, root and end up at bootloop. It's all as clear as mud!
I suppose I have to relinquish this phone to my wife,while I try to find out a way to get a rooted ICS ROM up and running on the Xperia ST15i. Any help from this community will be gratefully accepted.
Sent from my HTC Incredible S
But you can use it with the stock bootloader and gingerbread?
With this your phone boots up?
mihahn said:
But you can use it with the stock bootloader and gingerbread?
With this your phone boots up?
Click to expand...
Click to collapse
Tried that too. Does not boot.
Sent from my HTC Incredible S
So the device is bricked up atm?
Can you enter cwm or does it vibrate if you try to turn it on?
Have you tried multiple kernels right now?
Device is ok till I root on .42. Firmware. Thereafter I can't seem to get any custom ROM to boot. After installing CWMR and flashing a custom kernel (x-kernel, krish kernel) & thereafter wipe data, system, cache &dalvik & flash smultronic or clean ICS 1.5 thru aroma, I always seem to end in a bootloop (that too with the gb boot showing Sony Ericsson, not the Sony - Xperia ICS boot). To get back, I have to flashtool the .42 ftf and use the doomlord zergrush exploit to re-obtain root. What am I doing wrong?
Sent from my HTC Incredible S
You should install Android Android 4.0.4. You have to flash it with flashtool.
NEVER UPDATE OVER THE AIR IF YOU HAVE AN UNLOCKED BOOTLOADER!!!
So just flash Android 4.0.4 . Download an android 4 kernel like Extended Stock Kernel from here and download the android 4 rom (4.1.B.0.431) for your xperia mini here. Then you download Real Ics from here.
Then flash the kernel in fastboot mode and without restarting flash the android 4 rom in flashmode.The rom isn't rooted, but you don't need to root, cause cwm is included in the kernel! Then restart. If it restarts you can go on. Shutdown and enter cwm.
There you don't wipe anything!!! Don't format system etc!
You just install the zip from sdcard and after the installation is complete and before you reboot you make a factory reset and wipe dalvik cache...
Then you restart.
Normally it should work!
Greets
Michael
@Michael,
Dankeschön. Will give the way you describe one last try.
Edit....
My wife connected her phone to the laptop and the SEUS updated the phone to stock ICS 4.1xx. Not a big problem I assume, coz I downgraded from that very version.
Sent from my HTC Incredible S
I SOLVED IT!!!! You guys on the Xperia 2011 section are quite unkind to noobs & neophytes. I was wondering... 'After all it is the same Android OS. What can be so difficult in this device?' I did some more research and decided to give it another try:
1. Starting point... ST15i at stock ICS 4.1.B.0.431 firmware with locked boot loader (after a mistaken connection to laptop and SEUS updated to locked boot loader ICS firmware... iI think it is the Sony Smultron WWE equivalent).
2. Ran SE Boot loader Unlocking v1.6 by quangnhut123 (Excellent tool BTW). Got boot loader unlock from SE Official method.
3. While in the same boot loader Locking/Unlocking tool, flashed EXtended Stock Kernel - v2 for 4.1.B.0.431 from fastboot (Blue light, vol up and insert USB?). The kernel is pre-rooted with busybox and has DoomLord's version of CWMR.
4. Viola!!! Root on Stock ICS firmware with CWMR. Here's to you boors who told me that ICS on this phone could not be rooted!!!!
Thanks Michael, you helped me think while every other thread advised outrageous actions and i was quietly led up the garden path (Auf Eis gefurht!!!)
Presently wife prefers stock and wishes only to delete bloat system apps and use hostfiles to block ads.... Hope others find my post helpful to root their devices too....
Sent from my Incredible S
Okay, here's the situation.
I just flashed hboot 1.58 from here: http://forum.xda-developers.com/showpost.php?p=30014044&postcount=7
Beforehand, I flashed Freeza's AIO package posted on 8/1/2012, the one that updates everything but the kernel, recovery, and hboot: http://forum.xda-developers.com/showthread.php?t=1673377
On my bootloader screen I have:
***LOCKED***
SHOOTER XC SHIP S-OFF RL
HBOOT-1.58.0000
RADIO-1.09.00.0706
OpenADSP-v02.6.0.2226.00.0217
eMMc-boot
May 17, 2012,15:06:44
I'm using the latest 4EXT recovery, which is v.1.0.0.5 RC6 Testing, build: 46
I've tried _EVERYTHING_ to get this ROM going: format all partitions (except SD Card), wipe dalvik-cache, even the superwipe. Afterwards I would go into the setup and try to install the ROM. ROM installs, but on reboot I get stuck on a white HTC screen. This used to happen a lot to other people, but I understand this was (mostly) kicked in the rear end.
I've also set all the VPU/CPU speeds to the stock settings in the installation, and still no dice. Just so ya know, I can even install the latest deodexed gingerbread stock ROM for this device, and it works, for the most part (it bootloops until I install the hboot 1.40 revolution version).
Any help would be greatly appreciated.
****EDIT**** I got it to work; see post #10 if you are/were in the same pickle as me
It looks like you've done everything right. How long does it sit in the HTC screen?
Read, Search, Read again, ... Then Ask with Tapatalk 2
coal686 said:
It looks like you've done everything right. How long does it sit in the HTC screen?
Click to expand...
Click to collapse
hi coal, thanks for the reply.
and the phone sits on the HTC screen indefinitely (either till the battery dies or I pull it).
My guess would be incorrect kernel.
sudo passwd root
ZWYATT said:
My guess would be incorrect kernel.
Click to expand...
Click to collapse
see that's what I was thinking too, but..
1. the full AIO freeza package has the kernel but has the potential to reset S-OFF (due to it including hboot 1.58)
and 2. you flash a ROM, the kernel usually comes with it..?
I could not get Tribs rom to push the kernel.
You gotta find a compatible kernel, copy to sd, install via 4ext, then install rom.
sudo passwd root
thanks ZWYATT. is it possible to edit the other freeza update pack to update just the kernel only, or could it be possible to extract just the kernel from the update pack and install VIA 4ext?
and since this'll be my first time flashing a kernel, I just install from zip like always, right?
From what I read, freeza doesn't touch the kernel.
Yep, just dload a compatible kernel, it will be a zip file, and choose install zip in 4ext.
You'll have to ask Trib about extracting a kernel from his rom. I do not know if he wants, or cares, if people do that.
sudo passwd root
ZWYATT said:
From what I read, freeza doesn't touch the kernel.
Yep, just dload a compatible kernel, it will be a zip file, and choose install zip in 4ext.
You'll have to ask Trib about extracting a kernel from his rom. I do not know if he wants, or cares, if people do that.
Click to expand...
Click to collapse
Cool, thanks. As for Trib's ROM, all I know is people can use it as a base, but if people can extract the kernel from his ROM, I have no idea. it'd be nice if he'd check this thread since I can't post in his thread until I have at least ten posts.
EDIT: If it is allowed to extract the kernel from the ROM, can I take the kernel folder and make it into a zip file, then install via 4EXT?
I got it working, thanks to everyone (even Trib over PM, thanks A MILLION )!!!!
Here's how I did it:
***DISCLAIMER*** I take *NO* responsibility for bricks, voided warranties, your boss getting mad at you over the alarm app not working as it should, etc.
Pre-requisites:
* an HTC Evo 3D
* Latest version of Trib's SolidROM (you can either use the Custom or Stock GUI; I used the Stock GUI)
* fully functional adb and fastboot
* HTC drivers installed on your computer
* Virus's AIO package (found in step two)
* PG86IMG.zips of HBOOT 1.4 Revolutionary and HBOOT 1.58 (found in the OP)
* a kernel compatible with SolidROM (if you don't have one, here's one that Trib gave me: http://animeondroid.host22.com/boot.img)
* Latest version of 4EXT Recovery
0. Open a command prompt and navigate to your platform-tools folder
1. Make backups of anything that's important to you, this includes:
* Apps/Data (Use Titanium Backup or similar)
* SMS Text messages (I use SMS Backup & Restore)
* Contacts that aren't otherwise stored on your Google/Exchange/etc accounts
* And finally, ALWAYS NANDROID BACKUP YOUR CURRENT INSTALLATION!! This cannot be stressed enough.
2. Copy over the Virus AIO PG86IMG.zip found here to your SD card.
3. Reboot into bootloader and install Virus's AIO package (don't worry, it won't override your S-OFF)
4. Reboot into recovery and delete the PG86IMG.zip from the root of your SD Card
5. Wipe all partitions except SD Card (additionally, if you have the superwipe.zip feel free to use it also, justin case)
6. Wipe Dalvik Cache; optionally, wipe battery cache (if you haven't wiped it in awhile, now would be a good time to do so as preventative maintenance)
7. Enable smart flash if you haven't done so
8. Install Trib's SolidROM (personally I kept the Processing Unit (3D, 2D, Central) clock speeds as close to stock as I can and enabled V-sync)
9. Enable USB storage after installing the ROM
10. Put the PG86IMG.zip (the one that contains hboot 1.4 revolutionary) onto the root of your SD Card
11. Reboot into bootloader, get into the main screen, and let it install the hboot 1.4 revolutionary PG86IMG.zip; after you install the hboot, you get a black screen on reboot and a blinking power light, this is normal, don't worry. Just unplug your device from your computer and plug it in again
12. Reboot into recovery, enable USB Storage, and delete the PG86IMG.zip from your SD Card
13. Reboot into bootloader, get into fastboot, copy over a compatable ICS kernel into your platform-tools directory in your android SDK, and flash it (Trib was nice enough to give me a copy of his boot.img, see the pre-requisites; thanks A MILLION!!! ); command should be fastboot flash boot boot.img (assuming you're in your platform-tools directory in your android-sdk folder or you set it as part of your path variable, and you named your kernel boot.img)
14. Reboot into recovery, enable USB Storage, and copy over the hboot 1.58 PG86IMG.zip to the root of your SD Card
15. Reboot into bootloader and install hboot 1.58
16. Reboot normally and you should be in Trib's SolidROM!!!
Have fun and enjoy! Oh yeah, don't forget to read over the OP and the thread for SolidROM for all known issues, updates, patches, etc: http://forum.xda-developers.com/showthread.php?t=1808332
Okay. So I see Trib has a new version of his ROM out... problem is, it intermittently likes to reboot.
I've tried EVERYTHING:
* wipe all partitions EXCEPT SD Card, followed by a superwipe
* I _finally_ got my bootloader unlocked, so I tried trib's method of flashing the stock RUU first, THEN his ROM
and either way, it reboots at random.
I even tried flashing the old kernel on his new ROM (and vice versa) to rule out the kernel, but unfortunately things get worse, as I can't even get on 4G or WiFi!!!
Here's a weird bug I got in the Play Store...
Update a user app, any of them. Swipe the progress bar. The update will automatically install and appear to work just fine o.o
However, do this to any of the Sprint bloat apps and it won't work (except voicemail, since it has its own updater)
Anyone else seem to get this?
Hello folks,
I tried following a root/flash tutorial online. This was my first experience. I have a Samsung Galaxy S5 SM-G900w (canadian version). I was running Marshmallow stock.
Rooted phone using Odin.
The tutorial called for recovery using Philz recovery, but it seemed it was outdated or updated, so I tried using Cyanogenmode Recovery.
After rebooting, I used what I believed to be close enough to the next step: Wipe data and erase everything option.
After that, I did not have a 'install from sd card' sort of option and ended up with a reboot of the phone.
At this point, I have option for ODIN or recovery mode. I can point to the SD card or adb.
Each time I try to point to a ROM using SD card option it fails to validate the signature and I cannot complete it. I have tried using different ROMs to no avail.
When I power on the phone normally I get the Samsung Galaxy S5 screen powered by Android with the following in top-left corner of the screen, yellow font.
"Set Waranty Bit: kernel"
By all means I am a newb here.
Would anybody mind lending a hand to get me headed in the right direction? Would like to try using a Cyanogen mod 13 ROM to start.
Kind Regards,
Lonely without a phone
side note: It would be nice to know what I may have done wrong and where to go from here.
Few things that you can try:
Use adb while in recovery to push a rom zip to the internal storage.
Switch to TWRP (preferred recovery for most phones any more)
Make sure the rom zips you are downloading are not corrupted by checking the md5.
I'd personally go with TWRP. I've modded 100s of phones and that's my go to as long as there is a stable version for the phone. https://dl.twrp.me/klte/ I'd use the newest tar file to flash in Download Mode if you are using Marshmallow roms. It also features a file manager that you can transfer zips from SD to internal, if need be. If you want to push files to internal, you can use this: http://forum.xda-developers.com/showthread.php?t=2317790. Put the zip in the folder, open the commands prompt and have phone plugged in recovery mode. Check connection by using the command: adb devices then push file by: adb push nameofrom.zip /sdcard/ Note - you might need to reboot recovery if it does not show up in the root of the intenal storage after successfully pushed to the phone right away.
Hard to say exactly what happened without knowing which versions of the roms and recovery you are trying.
Update
es0tericcha0s said:
Few things that you can try:
Use adb while in recovery to push a rom zip to the internal storage.
Switch to TWRP (preferred recovery for most phones any more)
Make sure the rom zips you are downloading are not corrupted by checking the md5.
I'd personally go with TWRP. I've modded 100s of phones and that's my go to as long as there is a stable version for the phone. https://dl.twrp.me/klte/ I'd use the newest tar file to flash in Download Mode if you are using Marshmallow roms. It also features a file manager that you can transfer zips from SD to internal, if need be. If you want to push files to internal, you can use this: http://forum.xda-developers.com/showthread.php?t=2317790. Put the zip in the folder, open the commands prompt and have phone plugged in recovery mode. Check connection by using the command: adb devices then push file by: adb push nameofrom.zip /sdcard/ Note - you might need to reboot recovery if it does not show up in the root of the intenal storage after successfully pushed to the phone right away.
Hard to say exactly what happened without knowing which versions of the roms and recovery you are trying.
Click to expand...
Click to collapse
Hey es0tericcha0s,
Thanks so much for your help. I focused on switching up the recovery img. I used TWRP and it was SOOOOOO much better/easier, so thank you.
After that, the roms were able to show up and be applied and everything was smooth.
You da man.
You're welcome. I love TWRP. ?
So I got my shiny new device today, and it feels really nice. I worked with the launcher it came with, tried another one, and realized that yep, I gotta root and install a new rom. The notification bar just annoys me too much as I'm used to having quick actions and other things in there.
So, I followed a few guides, and finally worked my way through to having my command line find my device and can successfully reboot it into fastboot mode.
At that point, I realized that I can boot into recoveries without flashing them first (essentially trying them out to see how it works). However, I tried the 4 official version on the twrp site, and one made by a user here (cuoco92). They all successfully boot into the recover using the command "fastboot boot nameOfFileHere.img". At this point, every single recovery failed to respond to touch and volume presses. I can press the power button to turn off the screen, and pressing power to turn the screen back on shows a locked recovery screen, but I can't slide the screen to unlock it.
This is quite concerning to me. I don't want to flash a recovery for good if it's not working properly. I hope this makes sense. Or, is it normal to just flash a recovery and hope for the best? Do recoveries work with just booting to them without being flashed?
I haven't rooted and/or flashed any devices in about 5+ years, the last being a phone from virgin mobile that supported sd cards. When installing new roms, do we store the zips in the root of the phone, or does this get cleared out/deleted when doing the wipe cache/dalvik/etc?
Personally, I just want to make sure I don't rush into this, as there seems to be fragmented results when searching around for twrp not working with touch. I know these things have been asked before plenty of times, and I hope I don't come across as another "ugh, this again" post. I really appreciate any responses!
you never did, then just leave it as it is...its a nice phone eui is not bad... take it easy
Try booting the official TWRP recovery. As far as I remember, some of the versions tweaked by Cuoco92 had issues with the touch panel.
Anyway, EUI is not that bad, as your were told. While I used it, I also used an app called "Notification Toggles", which lets you get Quick Settings like toggles on notification area. It's nice and easy to set up, and the results, although not the same as having the AOSP toggles, is quite nice and convenient.
BTW, which stock ROM did your phone come with?
I have tried 4 different official twrp files (all from the twrp site). My phone is an x820 6gb/64gb and came with EUI version: 5.8.019S (Stable). EUI is nice, very fast and sleek. Maybe I do just need to get used to it, or maybe it's just me itching to try out the different options available since I finally have a phone is not carrier/manufacturer locked down.
Heyyo, hmm that's very odd indeed! I wonder if maybe by temporary booting Cuoco92's TWRP it could have messed up your recovery hmm...
I'd recommend first to flash the stock recovery over your current one and then reboot to fastboot and then flash TWRP. Hopefully this will erase any problem that Cuoco92's recovery could have caused.
This was the guide I followed and it worked flawlessly for me
https://forum.xda-developers.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151
I never actually flashed any of them. I have only ever just tried booting into them using "fastboot boot recovery name.img". I have not used the fastboot flash command for any of the files.
The only thing I can do after booting the recoveries is hold the power button and eventually the phone will boot up normally.
Remember that I just wanted to boot them to make sure they worked before flashing them. I'll be checking out the guide you linked shortly.
Haven't flashed any of them eh? Hmm should work just fine then... Have you tried TWRP 3.0.2-0 ? I know that one was built with Marshmallow sources
As for which ROM to try? I'd recommend OmniROM if you want to try a custom Nougat ROM.
If you want to see why I think so? I made a massive post or two about it here heh
https://forum.xda-developers.com/le-max-2/help/party-rom-best-help-t3691165/
Thank you so much for the guide you linked. I'm making a little bit of progress here.
I found a twrp recover by cuocos92 that is labeled V3 (apparently from what I read in other threads, V3 seems to be good with the 6gb/64gb models). This recovery allows the use of the touchscreen . Remember that I am only using the "fastboot boot" command so no flashing yet.
Now that I am in a working recovery, I kept hitting "keep read only" so that the stock recovery would not be replaced. I set out to make a backup. Well that kept failing with attempts of trying to mount /system and such. Off to more reading, found out that using the Wipe->Swipe to Factory Reset inside twrp fixes this. I did that. I successfully created a backup.
Now to try to flash the SuperSU zip I have, which was previously copied to the root of the phone from my pc. Can't see any zip files on the internal storage. Reboot the phone (forgetting that it takes a long time after the wipe). Copy the backup to my pc. Copy the SuperSU back to root of phone. Restart the process of adb and fastboot -> back into the cuocos92 V3 recovery. Still no zip to be found. Couldn't mount system again...
Did some more reading. I just attempted the Wipe->Format data. I am currently rebooting back into the phone to set it up again. Apparently, a lot of people say this needs to be done if we did not reboot after unlocking the bootloader. Since twrp has been asking for a password each time I entered it, the format data is supposed to solve this.
I'll edit/post again with more steps or results.
I apologize for the second post here, but this seems more than should go into an appended edit:
After doing the Wipe->Format data, it's advised to reboot back into the recovery. Without flashing the twrp cuocos92 recovery, my thoughts are it would just be back into the stock recovery. At least the twrp version works, so I have no problems with flashing it. And then I'll have to Wipe->Format data again, reboot back into recovery, and then I can flash my SuperSU zip. But how can I get my SuperSU zip on the phone?
Doesn't Wipe->Format data remove it? Everytime I reboot my phone after that the SuperSU on the root of the phone is gone. I can't seem to mount to my pc from the recovery either, clicking the usb storage just unchecks itself right away, and clicking the enable MTP doesn't seem to do anything. So, even if I flash the recovery, Wipe-Format data again, reboot back into the recovery, I still don't see a way of getting the SuperSU zip onto the phone anyways.
I know it probably sounds like I'm whining by now about how things aren't as easy as it seems. I'm trying to be descriptive in what I am doing and what's happening.
Hmm by chance are you using Windows 10? At least I've noticed for me it fails to properly mount the correct drivers for ADB and MTP for TWRP. I'd recommend checking device manager.
If I remember correctly here's what mine looked like at first
https://photos.app.goo.gl/wXaqbi3OeH3bKEf62
Select MTP > update driver > browse my computer > let me pick > (standard MTP Device) > MTP USB Device
Sorry I'm not in front of my PC but I'm sure it's something like that to solve it
If that doesn't work? You can always use...
Code:
adb push ROM.zip /sdcard
Which will copy the zip file to the root of your data storage (on the Le Max 2 much like the One Plus 3 they use /Sdcard as a shortcut since we don't have external Sdcard hardware).
As for system read only? Swipe to allow modifications. Can't flash a ROM properly if the system is read only eh? Hence the failed to mount system.
It's really just there as a disclaimer to cover their ass in case people use TWRP improperly and brick their device. Following green man gaming's guide is safe as I've used it plus many other people as you'll see in his replies
I'd also recommend following the guide and flashing TWRP to your recovery. I only did boot recovery image for backup and then booted to EUI and copied that backup to my PC.
Format data is handy to get rid of encryption and also give you full access to your storage capacity because when I didn't before I didn't get 54.43GB of data storage only something like 40GB.
Tbh I haven't used any custom EUI ROMs but if you're fighting with TWRP? I know Cuoco92's eui has a fastboot installable version
Hope this helps
Well thank you so much for the information. I am running windows 10, but never saw mtp under portable devices, only the phone name Le Max 2. That's ok, as I booted (still not flashed) into recovery and this time I swiped to allow modifications. I still couldn't mount /system but I was able to use the adb push command and the SuperSU file appeared inside the /sdcard directory when looking under Install inside twrp. I swiped to flash the zip, then hit reboot system. Looking in the SuperSU app, I noticed that the setting "Install SuperSU into /system" is greyed out. Well, at least I think it worked.
At this point in time, since things appear to be working, I'll be flashing the recovery and installing OmniRom (it was either this or Resurrection Remix). I think if the play store just works on OmniRom like people mention, it'll be worth it.
So, my steps will be to:
adb -> fastboot -> fastboot flash recovery fileName.img
recovery -> wipe -> factory wipe (using factory to get rid of system encryption) -> reboot back into recovery
recovery -> wipe -> dalvik/cache (do i still need to do this after factory wipe?)
adb -> adb push romFileName.zip /sdcard
adb -> adb push gapps.zip /sdcard
recovery -> install -> /sdcard -> romFileName.zip
recover -> install -> /sdcard -> gapps.zip
At any point do I need to flash SuperSU again? I guess I should after flashing the rom/gapps because, afterall, SuperSU is an app.
Once again, thank you so much for all the information that you have already provided!
Heyyo, it's always recommended to do a full wipe when installing a different ROM so you should format data, wipe system, data, dalvik and cache and then install the ROM of choice with Gapps of choice
Wiping system is OK when flashing a ROM as it'll write into system.. plus there's always the risk of instability if system is not wiped if a Gremlin setting is left over from previous ROM
I'd recommend using Magisk v14.3 over SuperSU as SuperSU doesn't have the same functionality as Magisk for passing SafetyNet...
Plus Magisk is full open source software (FOSS) where as SuperSU is closed source so gotta love that open source (this part is more personal preference since Android is built upon open source and people working together).
Plus there's really cool Magisk modules you can do like ART Optimizer and so fourth if you check the XDA forum section for it
Also, you're welcome! We all had our start on XDA at different points and passing on the knowledge I find is just as important as the ROMs we love
Don't use SuperSU. Magisk is the way to go for rooting nowadays. Easy, systemless, updated frequently to pass safetynet. It's a no brainer.