Database Develop

[BOOTLOADER BYPASS -WIP] EternityProject Kexec method for Motorola Olympus (Atrix 4G)

Welcome to Eternity Project!
So... as most of you know I'm working on the Atrix solution from TOO MUCH time.
With the collaboration of people on #moto-atrix I've stated that FUSES on Tegra2 are really OTP, so there isn't any way to CRACK the BL, but we can still BYPASS it.
So... what is it?:
kexec is a "fastreboot" that won't pass through the Moto Bootloader, so with it it's possible to use custom kernels and, with some other development, custom Android systems like CM7 and many others.
Where's the poop?
Okay, that's it: I've successfully compiled and ran kexec on the Atrix 4G, so that kexec works, but it needs a kernel that can boot with kexec. On x86 we can build a relocatable kernel so no problems... but not on ARM and obviously not on Tegra.
The thing that is missing is exactly... _the address of the boot params_!
And now?
I'm only searching for help for completing the project and make a kernel that is bootable from my god-it-is-really-working-kexec. Any devs around?
Downloads:
- Kexec pack V0.01: DOWNLOAD
Kexec pack contains:
- ATAGS for MB860 (ATRIX_atags.tar)
- ATAGS hack module (eternity_procfs.tar)
- kexec module (eternity_kexec.tar)
- kexec tools/binaries (kexec-tools.tar)
- Kernel....that doesn't work. (eternity_kexec_kernel.tar)
So, what does work and what does not?
- ATAGS hacky hack: WORKING
- kexec module: WORKING
- kexec tools/binaries WORKING
- Kernel ToDo
How to run it:
0. FLASH AT&T 1.2.6 SBF PRIOR DOING ANYTHING
1. Extract all the archives
2. Insert the procfs_rw.ko module
3. cat atags > /proc/atags
4. Insert the kexec module
5. Run kexec for loading the kernel and jumping to it.
6. Boot! :|
P.S.: I won't release detailed how-tos because at this state I only need a DEVELOPER that can help me to build the kernel.
Thanks to:
- PAulyHoffman (special thanks!)
- unknown
- Sogarth
- the2dcour
- cranch
- eval-
- and many, many others....!

Awesome, i can verify that this kexec is working and will continue testing until we succeed.

random boot animation I made for eternity project
http://diamantephoto.com/bootanimation_red.zip
Also: 1.2.6 without losing /data, in case you were wondering exactly why I made this
http://forum.xda-developers.com/showthread.php?t=1073439

kexec pack updated. now kexec-tools is included

@kholk: Hai;
so basically this is a port of the unix kexec to run on tegra based devices?
From my understanding the android system uses a boot image that has the ramdisk and kernel combined together and they are dependent on each other... so won't overwriting the kernel at runtime give you us some issues since the core initialization of the system is ran from the ramdisk???
wouldn't be a better idea to tackle this issue too? but then again the only reason we can't flash boot images is because of the bootloader but ofcourse this is definitely a step forward for the tegra users.
now about the kernel, theoretically if we build an aosp tegra kernel from http://android.git.kernel.org/?p=kernel/tegra.git;a=summary shouldn't it work?
I can try building us a kernel if that would work
PS: people let's keep this dev ONLY if you want us to get some progress we need able to read through the thread without useless posts.
edit: also found this https://opensource.motorola.com/sf/frs/do/listReleases/projects.atrix/frs.olympus I'm sure having the source for the kernel we are currently running is also helpful

I know we should keep this dev only but please don't tell me this is for ATT only i already feel shafted enough being a Bell user and that would make it a hell of a lot worse if it was

Ratchet556 said:
I know we should keep this dev only but please don't tell me this is for ATT only i already feel shafted enough being a Bell user and that would make it a hell of a lot worse if it was
Click to expand...
Click to collapse
When a kernel that works will be deployed I'll personally port it to Bell Atrix. This will take only some seconds.

kholk, perhaps we can ask a defy developer (or any of the phones that have kexec working) to help us build the kernel.
it's too bad da_g isn't around, he did a custom kernel but wasn't able to boot it.

I'm not a developer so I am hoping someone can help me understand this process better. From my understanding kexec is used as a reboot method that skips initial bootloader and hardware loading so how will this effect if we turn our phone off or pull the battery? Will the device need to be rebooted after initial startup to reactivate the kexec? Sorry to sound like the newbie that I am, I'm just interested in learning more.

lostinbeta said:
I'm not a developer so I am hoping someone can help me understand this process better. From my understanding kexec is used as a reboot method that skips initial bootloader and hardware loading so how will this effect if we turn our phone off or pull the battery? Will the device need to be rebooted after initial startup to reactivate the kexec? Sorry to sound like the newbie that I am, I'm just interested in learning more.
Click to expand...
Click to collapse
Yeah, I'm also a little confused as to what exactly this means for all of us people who want to just flash Custom ROMs and such? In what ways is this different than just an unlocked bootloader and such?

lostinbeta said:
I'm not a developer so I am hoping someone can help me understand this process better. From my understanding kexec is used as a reboot method that skips initial bootloader and hardware loading so how will this effect if we turn our phone off or pull the battery? Will the device need to be rebooted after initial startup to reactivate the kexec? Sorry to sound like the newbie that I am, I'm just interested in learning more.
Click to expand...
Click to collapse
thebeardedchild said:
Yeah, I'm also a little confused as to what exactly this means for all of us people who want to just flash Custom ROMs and such? In what ways is this different than just an unlocked bootloader and such?
Click to expand...
Click to collapse
Assuming my understanding of kexec is correct, this would survive battery pulls. Basically, a custom rom would need to include two kernels: a Motorola kernel in addition to the custom one. The bootloader would run the Motorola kernel, which should pass any checks the bootloader would make. From there, the kernel would use kexec to load the custom kernel over itself in memory, effectively replacing itself. From there the custom kernel can continue loading the rom.
If the booloader were unlocked, the phone could directly boot the custom kernel. The downside of loading the custom one on top of the Motorola one is that the state of the phone might not be entirely known, so it would need to do more work checking what's been initialized and what hasn't. Its a little more work for the kernel/rom developer, but the end result is the same.

Jotokun said:
Assuming my understanding of kexec is correct, this would survive battery pulls. Basically, a custom rom would need to include two kernels: a Motorola kernel in addition to the custom one. The bootloader would run the Motorola kernel, which should pass any checks the bootloader would make. From there, the kernel would use kexec to load the custom kernel over itself in memory, effectively replacing itself. From there the custom kernel can continue loading the rom.
If the booloader were unlocked, the phone could directly boot the custom kernel. The downside of loading the custom one on top of the Motorola one is that the state of the phone might not be entirely known, so it would need to do more work checking what's been initialized and what hasn't. Its a little more work for the kernel/rom developer, but the end result is the same.
Click to expand...
Click to collapse
I see, thanks for the explanation! So, on the user end, would there be any noticeable differences? This kind of makes it sound like the phone will be doing a lot more work, so could we see performance decrease or perhaps startup lag or something of the sort? Or would this all pretty much function on the surface as if we had flashed a custom ROM on some phone without a locked bootloader?

thebeardedchild said:
I see, thanks for the explanation! So, on the user end, would there be any noticeable differences? This kind of makes it sound like the phone will be doing a lot more work, so could we see performance decrease or perhaps startup lag or something of the sort? Or would this all pretty much function on the surface as if we had flashed a custom ROM on some phone without a locked bootloader?
Click to expand...
Click to collapse
Boot time will be about twice as long. Other then that, everything will run about the same

Yes thank you very much for that explanation... though I do also have the question about stability. By replacing the current kernel in memory with the new modified kernel the phone state may get confused as you mentioned... could this cause instability as a whole or increase risk of kernel panics? Or once everything is loaded and complete does it stabilize with the modified kernel?
Again sorry for the questions. This topic intrigues me and I love learning how stuff works.

thebeardedchild said:
I see, thanks for the explanation! So, on the user end, would there be any noticeable differences? This kind of makes it sound like the phone will be doing a lot more work, so could we see performance decrease or perhaps startup lag or something of the sort? Or would this all pretty much function on the surface as if we had flashed a custom ROM on some phone without a locked bootloader?
Click to expand...
Click to collapse
Only difference would be that it might take slightly longer to boot up. Once the phone is finished booting, there's no difference in terms of performance because by that point the Motorola kernel isnt running, or even loaded.

thebeardedchild said:
Haha yeah I'm checking every like 2 seconds now. What exactly do we wait for then? Someone to just create the custom kernel, and then of course wait for some Custom ROMs to be created? I hope we get CM7!
Click to expand...
Click to collapse
Kexec isn't fully operational yet, still need to find boot params. Then custom kernel.

How easy will this be to install on our phones? will it just be something we need to flash through CWM or will it require some more work then that to install?

Ratchet556 said:
How easy will this be to install on our phones? will it just be something we need to flash through CWM or will it require some more work then that to install?
Click to expand...
Click to collapse
I imagine some of the preliminary stuff may need to be pushed with ADB but devs are always nice and give us very clear guides. And I'm sure either a dev or active member could easily create a batch script.
Even though I'm comfortable with ADB I always make scripts for myself because I regularly wipe me phone and whatnot. Because it's so engaging some people might want to wait until a few normal community members test this out so we can see if there are any glaring challenges with the instructions. Just remember to back things up, read instructions clearly and I'm sure we'll all be fine. We've got SBFs and all that good stuff to cover our asses too.

Would it be possible to bring fastboot off the htc to this? Then we won't have to worry about boot time at all. Even if it did double the boot time...
Sent from my MB860 using XDA App

PixoNova said:
This bypasses the bootloader
Swyped from my Motorola Atrix 4g using XDA Premium App
Click to expand...
Click to collapse
Correct this method has nothing to do with unlocking the bootloader and previous attempts at that proved it maybe impossible.

[WIP] Building CM 10.1

Granted, it has been a while since I've built CM, and never ported it to a new device, but figure this might give some smarter people a head start or at least provide a place for others to collaborate.
I've not gotten very far past the initial vendor setup per http://wiki.cyanogenmod.org/w/Doc:_porting_intro.
A lot of the work is based off the similar ASUS TF700T, https://github.com/CyanogenMod/android_device_asus_tf700t.
I've not messed with the kernel at all at this point, https://github.com/ouya/ouya_1_1-kernel.
I've uploaded everything so far to github, https://github.com/vinny75/android_device_ouya_ouya_1_1

Packages included with official build:
OUYA Framework, Launcher, and Store
Code:
app\OUYAKeyboard.apk
app\OUYALauncher.apk
app\OUYAOOBE.apk
app\OUYAWallpaper.apk
app\ouya-framework.apk
note: some media files I haven't list
CWiid for Android: http://cvpcs.org/projects/android/cwiid4android and https://github.com/cvpcs/android_external_cwiid[.
Code:
bin\wminput
lib\libcwiid.so
etc\acc_led
etc\acc_ptr
etc\buttons
etc\gamepad
etc\ir_ptr
etc\neverball
etc\nunchuk_acc_ptr
etc\nunchuk_stick2btn
Sixpair for PS3 controllers http://www.blog.kaiserapps.com/2012/10/setting-up-sixaxis-controller-android.html.
Code:
/bin/ps3service
/bin/sixpair

I noticed that the recovery.fstab committed is from the Ouya stock recovery partition. When getting cwm to work properly with the internal sdcard, we ended up having to change the sdcard line.
I made the change and submitted a pull request.
Edit: I saw you merged the change.
Sent from my Nexus 7 using xda premium

mybook4 said:
I noticed that the recovery.fstab committed is from the Ouya stock recovery partition. When getting cwm to work properly with the internal sdcard, we ended up having to change the sdcard line.
I made the change and submitted a pull request.
Edit: I saw you merged the change.
Click to expand...
Click to collapse
Thanks, appreciate the help, hopefully, we'll have a working build soonish

If you need any help with kernel debugging/boot issues, I'll be happy to offer up the assistance of my bus pirate.
I was looking at building CM also, but there was always that step in every tut I looked at for "how to port CM to a new device" that basically said "select your device from the build tree"... well if it was in the device tree it wouldn't really be a "new" device then would it!
Also you may want to look at building 10 instead of 10.1, might have less kernel issues as its 4.1.2 jb... at least so we can get some alternative rom working then go for 10.1 after that.
Good luck!

Vinny75,
What method did you use to create the files?
"Method 1: Use mkvendor.sh to generate skeleton files"
"Method 2: Fork a similar device's git repository"
or "Method 3: create the directories and files manually"

mybook4 said:
Vinny75,
What method did you use to create the files?
"Method 1: Use mkvendor.sh to generate skeleton files"
"Method 2: Fork a similar device's git repository"
or "Method 3: create the directories and files manually"
Click to expand...
Click to collapse
I started out with Method 1 then moved over files and settings from the ASUS TF700T.

professorpoptart said:
If you need any help with kernel debugging/boot issues, I'll be happy to offer up the assistance of my bus pirate.
I was looking at building CM also, but there was always that step in every tut I looked at for "how to port CM to a new device" that basically said "select your device from the build tree"... well if it was in the device tree it wouldn't really be a "new" device then would it!
Also you may want to look at building 10 instead of 10.1, might have less kernel issues as its 4.1.2 jb... at least so we can get some alternative rom working then go for 10.1 after that.
Good luck!
Click to expand...
Click to collapse
Yes, building the new device tree has been... uhm... educational... and I am still learning. If I don't make any headway on 10.1, I might drop back to 10 - at least most of the legwork will be done.

Ok, so I'm in the middle of a build
Have a vendor tree on my git and I forked Vinny75's device tree, modified it some
Also a kernel tree up there, which is required for my device tree (prefer to build the kernel myself =) I've booted a custom-built kernel on it already, so that shouldn't be an issue)
I'm nervous to flash this though. I did a bit of searching but couldn't come up with a way to get back into recovery should this thing not boot. You guys know of anything?

Other than using adb to reboot to recovery, http://forums.ouya.tv/discussion/1380/recovery-mode is all I've seen so far to force into recovery mode.
Sent from my Nexus 7 using xda premium

mybook4 said:
Other than using adb to reboot to recovery, http://forums.ouya.tv/discussion/1380/recovery-mode is all I've seen so far to force into recovery mode.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Yea, that's what I'm seeing.
So here's my 'solution'
Since we have fastboot, we can boot a boot.img without having to worry about flashing it.
I've successfully booted my cm boot.img, with ro.secure=0 and ro.adb.secure=0, I can adb reboot it when it fails miserably to boot
Quick and dirty script to unsecure a boot.img:
http://pastie.org/8033076
It assume that unpackbootimg and mkbootimg are in your path, you can get them here: http://invisiblek.org/mkbootfs_tools.zip
Getting closer...

THere's a keyboard solution in the Ouya Questions forum in the thread, [Q] Is My Ouya Dead?

dibblebill said:
THere's a keyboard solution in the Ouya Questions forum in the thread, [Q] Is My Ouya Dead?
Click to expand...
Click to collapse
Yeah, I think that is the same solution posted earlier:
mybook4 said:
Other than using adb to reboot to recovery, http://forums.ouya.tv/discussion/1380/recovery-mode is all I've seen so far to force into recovery mode.
Click to expand...
Click to collapse
THis might be another option too:
tylerwhall said:
I started looking into bootloader-level recovery tonight before messing with the file system too much and potentially getting into a bad state. I couldn't find this information anywhere else.
Bootloader strap
On the back of the board in the center, there is an unpopulated button (U33). When jumped while the power button is pressed, this appears to put the bootloader into USB recovery mode. It enumerates with an nvidia vendor id. Presumably nvflash or tegrarcm could be used to unbrick the device.
I haven't done anything with the bootloader recovery since I haven't yet made a backup. I'm not sure how much of the functionality is allowed given the state of the production fuse, but I would think we could use this to at least get back to a stock state.
Click to expand...
Click to collapse

Some NVidia devices lock access out at the nvflash level unless you've got the manufacturer's key. I believe you get locked out with a 0x4 (nvflash's way of saying "go away").
Using fastboot is probably the quickest, easiest, and safest way to test new kernels.
Sent from my SCH-I535 using xda premium

mybook4 said:
Some NVidia devices lock access out at the nvflash level unless you've got the manufacturer's key. I believe you get locked out with a 0x4 (nvflash's way of saying "go away").
Using fastboot is probably the quickest, easiest, and safest way to test new kernels.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
ah he makes it sound like it puts you in USB recovery mode fo you could ADB in to push an update.

Just wanted to say I'm totally stoked on this guys! Can't wait to see what you do with this. Wish I could help, but I'm really not a developer.

i agree with rebel! but when you guys have it readyish ill test flash it and tell you what happens!!

So, OUYA isn't really as interested in being an open console as they suggest.
I'm keeping a track of how many requests we get relating custom firmware, and from what I'm seeing the user base is not as interested in custom firmware as you might think, which is echoed by this thread (we've shipped 60,000+ units, and less than 10 people have commented in the last month in this thread about getting access to recovery mode).
That doesn't mean that we're shooting the idea down, you need to keep in mind that in terms of priorities this is way down the list as you'd expect from any feature where it's being requested by less than one tenth of one percent of the user-base.
I'm sure @Wajeemba is familiar with CM requests that a very small minority of the user-base are very passionate about, so hopefully you can understand why we're not rushing to work on this.
Click to expand...
Click to collapse
Go to this thread and let them know we want support:
http://forums.ouya.tv/discussion/1380/recovery-mode

That's not even slightly surprising. If every user demanded CM10 they still wouldn't comply, because then they'd lose their one means of profit (ouya store), the fact that "nobody is asking for it" is their excuse, and they'll think of another one if that ever changes.
This is why we just need to proceed without them. I'm on week two of who knows how many weeks away from home on work, so my efforts at porting CM have been put on hold. Have you been able to make any progress? I'd totally loan my Ouya to Fattire or Dalingrin, or another whiz porter if they'd be willing to work on it...

sonofskywalker3 said:
That's not even slightly surprising. If every user demanded CM10 they still wouldn't comply, because then they'd lose their one means of profit (ouya store), the fact that "nobody is asking for it" is their excuse, and they'll think of another one if that ever changes.
This is why we just need to proceed without them. I'm on week two of who knows how many weeks away from home on work, so my efforts at porting CM have been put on hold. Have you been able to make any progress? I'd totally loan my Ouya to Fattire or Dalingrin, or another whiz porter if they'd be willing to work on it...
Click to expand...
Click to collapse
I'd check with invisiblek about how to avoid bricking the OUYA. Apparently his is bricked. It's stuck in nvflash mode. I think it was a kernel written with a bad init.rc that did it. not sure though.
Sent from my Nexus 7 using xda premium

CM12 rom for the CDMA(Verizon) Variant of the One Mini 2

The One remix has S-off and root now thanks to the sunshine team. how hard would it be to get cyanogen mod onto this device?

Fullmetal99012 said:
The One remix has S-off and root now thanks to the sunshine team. how hard would it be to get cyanogen mod onto this device?
Click to expand...
Click to collapse
It shouldn't be that difficult since you now have S-OFF. Only patches will be required IMO to get it running, so you should request u-ra(the developer of CM12 for our device).
Did you try to flash the current build?

csoulr666 said:
It shouldn't be that difficult since you now have S-OFF. Only patches will be required IMO to get it running, so you should request u-ra(the developer of CM12 for our device).
Did you try to flash the current build?
Click to expand...
Click to collapse
I'm also curious about this too, but I am not in a position to flash the current build right now...
Somewhat off topic, is there something I have to do to the stock firmware to get root to stick after running Sunshine? Flashing the zip in twrp doesn't work...

Txjacob said:
I'm also curious about this too, but I am not in a position to flash the current build right now...
Somewhat off topic, is there something I have to do to the stock firmware to get root to stick after running Sunshine? Flashing the zip in twrp doesn't work...
Click to expand...
Click to collapse
I used SUInstaller from the same guys who do sunshine. worked fine for me.
How did you get TWRP installed? I can't seem to get it to work.
As for installing the current build, not really sure I want to do that, since I don't have a backup phone to use right now.

I had to use a different TWRP from the official website for the HTC One Remix. I can't seem to get SU installed... The package from the Sunshines guys just reboots my phone and doesn't do anything, while flashing through TWRP has no errors, but doesn't do anything either...
This is where I got TWRP:
http://twrp.me/devices/htconeremix.html

Txjacob said:
I had to use a different TWRP from the official website for the HTC One Remix. I can't seem to get SU installed... The package from the Sunshines guys just reboots my phone and doesn't do anything, while flashing through TWRP has no errors, but doesn't do anything either...
This is where I got TWRP:
http://twrp.me/devices/htconeremix.html
Click to expand...
Click to collapse
That's where I looked too. did you do the fastboot install? I'm trying the app from the store, but it doesn't list the device.
also, interesting. the SUInstaller worked on mine, but it is hit and miss. not sure how to root it otherwise.

Yes, I just did the fastboot install. Just realized I wasn't following the SUinstaller instructions preoperly. Works now!

Txjacob said:
Yes, I just did the fastboot install. Just realized I wasn't following the SUinstaller instructions preoperly. Works now!
Click to expand...
Click to collapse
glad to hear!
ill have to do the fastboot TWRP when I get home.
not sure what is needed for the One Remix to get CM12 support. HTC has the kernel source for the M7 and M8 online(and even the one Max), but not the remix.

It doesn't seem like a whole lot should be done. The hardware ought to be very similar to the HTC One Mini 2, just has to be adjusted for CDMA rather then GSM.
I tried to flash the current CM 12 build, but TWRP complains about the code-names not matching, and the update script failed. I then had to restore from a backup to get it to boot up to the original firmware.

csoulr666 said:
It shouldn't be that difficult since you now have S-OFF. Only patches will be required IMO to get it running, so you should request u-ra(the developer of CM12 for our device).
Did you try to flash the current build?
Click to expand...
Click to collapse
Could everyone please stop suggesting One Remix owners try flashing One Mini 2 stuff? It's not gonna work. Ever.
While they probably share >90% of the same features, they're not the same device.
One Remix won't be getting CM builds until someone starts working on it. Given that CM has a policy of not maintaining devices you don't own, it's not gonna be me.

u-ra said:
Could everyone please stop suggesting One Remix owners try flashing One Mini 2 stuff? It's not gonna work. Ever.
While they probably share >90% of the same features, they're not the same device.
One Remix won't be getting CM builds until someone starts working on it. Given that CM has a policy of not maintaining devices you don't own, it's not gonna be me.
Click to expand...
Click to collapse
what is needed to work on a build? I would be interested, but not sure If i need kernel source or device specific drivers. neither of which HTC dev supplies for the One Remix.

It doesn't appear to be much. I've been digging through the CM Porting Guide, and specs on the phones and they appear pretty similar. They both have the same SoC (Qualcomm Snapdragon 400) and GPU (Adreno 305), but the Remix has 1.5GB RAM instead of 1GB. Haven't had a chance to compare the partition schemes, but Verizon might have made them different... Some things need to be changed in the source of the Mini 2 to make it compatible, but the Kernel should be fine.

What about the Radios? does the difference in Radio CDMA vs GSM change anything major. I'll take a look at the porting guide and see if I can get something booted.

https://github.com/kfechter/android_device_htc_memwl
I forked the memul build of CM and renamed it. any help in grabbing stuff from the Remix would be great (kernels, drivers, recovery images)

One more update.
I've asked HTC for kernel source for the one remix. hopefully HTCDev actually comes through and provides it. hopefully also for Lollipop.

I don't think there is a separate kernel source for the Remix. On the cyanogen wiki for the HTC One Mini 2, they are just using the kernel source for the M8. That should work fine for the Remix also.

Txjacob said:
I don't think there is a separate kernel source for the Remix. On the cyanogen wiki for the HTC One Mini 2, they are just using the kernel source for the M8. That should work fine for the Remix also.
Click to expand...
Click to collapse
I did see that. I've been editing the build files and device information that I forked from the one mini 2 device repo. I've been having issues with the repo sync for actual cyanogenmod though(my repo is just the specific device properties). I'll work on it when I can, but I'm also working on intelligent vision stuff and schoolwork.
Also, Need to figure out what to change to get the CDMA radio support, and need to grab the partition tables from my device.
Is there somewhere I would be able to restore the stock rom from in case something goes horribly wrong?

Txjacob said:
Yes, I just did the fastboot install. Just realized I wasn't following the SUinstaller instructions preoperly. Works now!
Click to expand...
Click to collapse
How do you install the twrp img file from fastboot? I've rooted my remix and am with you guys in the search for a Rom or help building one. Just need to get a recovery installed. Have SuperSU installed as well, thanks

Fullmetal99012 said:
I did see that. I've been editing the build files and device information that I forked from the one mini 2 device repo. I've been having issues with the repo sync for actual cyanogenmod though(my repo is just the specific device properties). I'll work on it when I can, but I'm also working on intelligent vision stuff and schoolwork.
Also, Need to figure out what to change to get the CDMA radio support, and need to grab the partition tables from my device.
Is there somewhere I would be able to restore the stock rom from in case something goes horribly wrong?
Click to expand...
Click to collapse
Yes, in TWRP you can make a backup of your current partitions (It just dumps the current partition to IMG files), then if you have a problem you can just restore back from those files.
neuclear said:
How do you install the twrp img file from fastboot? I've rooted my remix and am with you guys in the search for a Rom or help building one. Just need to get a recovery installed. Have SuperSU installed as well, thanks
Click to expand...
Click to collapse
First, download the TWRP build from the TWRP website, the one in this forum is for the Mini 2 and won't work with the Remix. Then boot your phone into fastboot mode and run "fastboot flash recovery twrp.img" on your computer. Then reboot, and after when you select recovery from the bootloader it should open TWRP.

When I boot into fastboot usb, i enter the command to flash recovery and it says error cannot load twrp.img BUT when i type the same command but add USB after fastboot it loads the commands list. Still cant get it to load. The file name in the Android-adb file is twrp.img as well. Ive done everything correct as far as I know. Any input would be appreciated. thanks.
---------- Post added at 08:06 AM ---------- Previous post was at 07:55 AM ----------
I figured it out.
Went into file Android-adb and did shift right click open command window here. typed the command and it worked on the first try. now its time to develop a rom and make this phone worth something!

Phone unable to get past CM13 boot logo (with video)

Basically, I had to do a battery pull on my LG D415, after the better pull, I booted up the device like I normally would. After starting the device, I am now experiencing an issue where I am unable to get past the CM13 boot logo, where it will continue the booting animation with the CM13 logo, and then the device will just shut down. Attached is a video of this happening.
Is this essentially the inevitable bootloop that is found in many Android devices? If so, how can I go about fixing the issue? I had a lot of stuff on the device and would prefer to not have to reflash anything, as I spent already hours setting up the device in the first place.
Here is the video: https://www.youtube.com/watch?v=1kgh-DFxKBg&feature=youtu.be

darkgiant said:
Basically, I had to do a battery pull on my LG D415, after the better pull, I booted up the device like I normally would. After starting the device, I am now experiencing an issue where I am unable to get past the CM13 boot logo, where it will continue the booting animation with the CM13 logo, and then the device will just shut down. Attached is a video of this happening.
Is this essentially the inevitable bootloop that is found in many Android devices? If so, how can I go about fixing the issue? I had a lot of stuff on the device and would prefer to not have to reflash anything, as I spent already hours setting up the device in the first place.
Here is the video:
&feature=youtu.be
Click to expand...
Click to collapse
Usually a bootloop restarts your phone or doesn't pass the CM (in this case) logo.. I think u can classify as bootloop nevertheless.. u can try reflashing the same version of cm13 on top of that.. you maybe won't loose anything important but I don't know what you had done in your device.. it's just my opinion..

Warimation said:
Usually a bootloop restarts your phone or doesn't pass the CM (in this case) logo.. I think u can classify as bootloop nevertheless.. u can try reflashing the same version of cm13 on top of that.. you maybe won't loose anything important but I don't know what you had done in your device.. it's just my opinion..
Click to expand...
Click to collapse
So if I were to flash CM13 (without wiping anything) I should be safe in terms of not wiping anything? Would I also need to flash GAPPS again?

darkgiant said:
So if I were to flash CM13 (without wiping anything) I should be safe in terms of not wiping anything? Would I also need to flash GAPPS again?
Click to expand...
Click to collapse
I don't know.. again it's your decision.. but if your going to flash, try 1st without Gapps.. if they don't stay then flash Gapps.. btw I saw u want to download cm13.. that's a bummer because cyanogen is over.. they closed CyanogenMod OS. So no more cm's for anyone. Instead u have lineage OS that's made by CM team and we don't have official. It's the same with changed brand.. I don't know if you will succeed downloading a cm13 version but search here in L90 forums.. maybe you find a solution..

Warimation said:
I don't know.. again it's your decision.. but if your going to flash, try 1st without Gapps.. if they don't stay then flash Gapps.. btw I saw u want to download cm13.. that's a bummer because cyanogen is over.. they closed CyanogenMod OS. So no more cm's for anyone. Instead u have lineage OS that's made by CM team and we don't have official. It's the same with changed brand.. I don't know if you will succeed downloading a cm13 version but search here in L90 forums.. maybe you find a solution..
Click to expand...
Click to collapse
Oh yeah, I totally forgot that CyanogenMod closed down its OS. This is a huge bummer, as this essentially means I need to find a new ROM anyways...
Any suggestions? Anything super stable, and runs fast is what I was looking for. If not, I might just go back to the stock ROM and stay rooted or something.

darkgiant said:
Oh yeah, I totally forgot that CyanogenMod closed down its OS. This is a huge bummer, as this essentially means I need to find a new ROM anyways...
Any suggestions? Anything super stable, and runs fast is what I was looking for. If not, I might just go back to the stock ROM and stay rooted or something.
Click to expand...
Click to collapse
I'm currently using Aicp os. Its super fast and it's working good.. it's nougat so expect a better battery life but still have some bugs.. It's going to become official.
forum.xda-developers.com/lg-l90/development/rom-android-ice-cold-project-12-1-t3559656/page3

Warimation said:
I'm currently using Aicp os. Its super fast and it's working good.. it's nougat so expect a better battery life but still have some bugs.. It's going to become official.
forum.xda-developers.com/lg-l90/development/rom-android-ice-cold-project-12-1-t3559656/page3
Click to expand...
Click to collapse
Thanks for the advice, I'll go ahead and take a look at it! As long as it's stable, and good to use as a daily driver, it works for me.
Though, I am currently having an issue with booting into TWRP to flash the ROMs, as I keep trying the volume up + power button steps to get into recovery, but it's just sending me directly to the CM13 loading logo. And because I can't even get into CM13 because of the boot issue, I am not sure if I can connect the device to a computer... Any advice on how I can fix this issue?

darkgiant said:
Thanks for the advice, I'll go ahead and take a look at it! As long as it's stable, and good to use as a daily driver, it works for me.
Though, I am currently having an issue with booting into TWRP to flash the ROMs, as I keep trying the volume up + power button steps to get into recovery, but it's just sending me directly to the CM13 loading logo. And because I can't even get into CM13 because of the boot issue, I am not sure if I can connect the device to a computer... Any advice on how I can fix this issue?
Click to expand...
Click to collapse
Its power button and volume down.. I read that ur going to give your L90 To another person.. I think u should not flash nougat Roms yet.. they are still "beta ish" Roms.. Instead try this https://www.androidfilehost.com/?fid=673368273298925163
Its a unofficial build of lineage 13 made by @slimshadys and is basically cm13 last nightly made.. should be very stable.. doesn't bring root by default but just flash SuperSU 2.79 (last version I think) and will work ok

Warimation said:
Its power button and volume down.. I read that ur going to give your L90 To another person.. I think u should not flash nougat Roms yet.. they are still "beta ish" Roms.. Instead try this https://www.androidfilehost.com/?fid=673368273298925163
Its a unofficial build of lineage 13 made by @slimshadys and is basically cm13 last nightly made.. should be very stable.. doesn't bring root by default but just flash SuperSU 2.79 (last version I think) and will work ok
Click to expand...
Click to collapse
Haha silly me, yes volume down + power did the trick. I always get confused with that because it seems to be different for many devices. Yeah as I posted in my other thread, this phone is meant for a friend who uses it daily, it sounds like that lineage 13 is pretty much fit for the task? Would it receive updates in the future? I am always open for trying other ROMS of course, as long as they are 100% working and have no issues/

darkgiant said:
Haha silly me, yes volume down + power did the trick. I always get confused with that because it seems to be different for many devices. Yeah as I posted in my other thread, this phone is meant for a friend who uses it daily, it sounds like that lineage 13 is pretty much fit for the task? Would it receive updates in the future? I am always open for trying other ROMS of course, as long as they are 100% working and have no issues/
Click to expand...
Click to collapse
As it is now lineage 13 is the best option for stable.. But dont expect updates on 13.. Later you can use 14.1 but now it have some issues..

Warimation said:
As it is now lineage 13 is the best option for stable.. But dont expect updates on 13.. Later you can use 14.1 but now it have some issues..
Click to expand...
Click to collapse
Oh okay, thanks! I'll go ahead and just do a fresh install since I forgot this phone has an SD card, so the majority of the data needed is already there. Thanks for your help! I'll keep looking at 14.1 and rest of the Nougat ROMs, and consider flashing it if they become stable soon.

Warimation said:
Its power button and volume down.. I read that ur going to give your L90 To another person.. I think u should not flash nougat Roms yet.. they are still "beta ish" Roms.. Instead try this https://www.androidfilehost.com/?fid=673368273298925163
Its a unofficial build of lineage 13 made by @slimshadys and is basically cm13 last nightly made.. should be very stable.. cumps
Click to expand...
Click to collapse
So I installed lineage OS, but for some reason can't provide root access to apps? Attached a screenshot, not sure why it's not allowing me to select apps, and only showing ADB...
EDIT: No idea how, but the SIM card reader stopped working... I tried flashing another ROM just to see if it was lineage, but it wasn't. The phone is still under warranty, but I assume if I send it back it'd have to be unrooted... any idea how I can go about that?

darkgiant said:
So I installed lineage OS, but for some reason can't provide root access to apps? Attached a screenshot, not sure why it's not allowing me to select apps, and only showing ADB...
EDIT: No idea how, but the SIM card reader stopped working... I tried flashing another ROM just to see if it was lineage, but it wasn't. The phone is still under warranty, but I assume if I send it back it'd have to be unrooted... any idea how I can go about that?
Click to expand...
Click to collapse
https://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
Do this and you have a warranty covered phone.

Warimation said:
https://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
Do this and you have a warranty covered phone.
Click to expand...
Click to collapse
Oh great, thanks! I used to have the old myTouch 4G, and unrooting that phone was such a pain, I nearly spent 6 full hours because of all the steps needed and it was so easy to mess up. This looks pretty straight forward. On the bright side, I now know once I get the phone back I can flash lineage OS and should be good to go.

darkgiant said:
Oh great, thanks! I used to have the old myTouch 4G, and unrooting that phone was such a pain, I nearly spent 6 full hours because of all the steps needed and it was so easy to mess up. This looks pretty straight forward. On the bright side, I now know once I get the phone back I can flash lineage OS and should be good to go.
Click to expand...
Click to collapse
Before you flash kdz maybe the problem was bootstack.. Dont really know if that was the problem because its supposed to work if you still have a KitKat bootstack installed but try changing that.. Just be carefull to choose the right one..
https://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632/page7

AT&T Razer Phone 2 stock recovery?

Hi,
Would anybody be willing to upload the stock recovery from the At&t Razer Phone 2 please.
I would really appreciate it. I'm trying to work on some more for this phone.
Thank you

I know another att variant guy captured the newest pie zip URL and I downloaded it. The recovery lives in the boot.img right?
Were AT&T the ones that sent you the THX model? Or did you buy it straight from Razer?
I'll find that URL and past it here. I've extracted the previous Oreo update from the att build prior to moving to the global version. I had to capture the URL from a log, then downloaded it, then extracted it then I had to use python to fully extract pieces of the payload. Which included the boot.img.
Not a developer but I think I can help here.
Here's the URL for pie July security for att:
https://android.googleapis.com/pack.../2965f0fadb65852413dba10a4fed1029ecce838f.zip
This will help you extract the payload.bin in the zip:
https://shorturl.at/ABEMW

jonchance_84 said:
I know another att variant guy captured the newest pie zip URL and I downloaded it. The recovery lives in the boot.img right?
Were AT&T the ones that sent you the THX model? Or did you buy it straight from Razer?
I'll find that URL and past it here. I've extracted the previous Oreo update from the att build prior to moving to the global version. I had to capture the URL from a log, then downloaded it, then extracted it then I had to use python to fully extract pieces of the payload. Which included the boot.img.
Not a developer but I think I can help here.
Here's the URL for pie July security for att:
https://android.googleapis.com/pack.../2965f0fadb65852413dba10a4fed1029ecce838f.zip
This will help you extract the payload.bin in the zip:
https://shorturl.at/ABEMW
Click to expand...
Click to collapse
I received it from Razer for development/testing. Yes the recovery is in the boot.img. My computer is down right now do to kid damage lol. Got to repair it. I've downloaded the payload.bin but I need help extracting it.
Thank you

kountry83 said:
I received it from Razer for development/testing. Yes the recovery is in the boot.img. My computer is down right now do to kid damage lol. Got to repair it. I've downloaded the payload.bin but I need help extracting it.
Thank you
Click to expand...
Click to collapse
I'll pull out my old dumpy laptop. Good one is at work. I'll see if I can extract the boot.img.
---------- Post added at 07:27 PM ---------- Previous post was at 06:44 PM ----------
Try that.
https://mega.nz/#!d0MSGIIQ!imc6jZyK0wyJrzFvDt9WhgSqwLZTdV9oexaYBP9gfeQ

Hey bud,
Thank you for the extracted image. I really appreciate it. I fixed my laptop this morning and extracted the whole payload.bin with python. I'm currently doing research on the partitions. I'm also trying to figure out why the arter97 r10 kernel won't boot with at&t latest update. Just hangs at boot. It installs nicely with global. Again thank you very much for your time and effort.
Kountry

kountry83 said:
Hey bud,
Thank you for the extracted image. I really appreciate it. I fixed my laptop this morning and extracted the whole payload.bin with python. I'm currently doing research on the partitions. I'm also trying to figure out why the arter97 r10 kernel won't boot with at&t latest update. Just hangs at boot. It installs nicely with global. Again thank you very much for your time and effort.
Kountry
Click to expand...
Click to collapse
R10 works just fine on my device updated to AT&T's latest.

JDBarlow said:
R10 works just fine on my device updated to AT&T's latest.
Click to expand...
Click to collapse
Hmm I wonder what I'm doing wrong. I followed the exact steps I did on the global firmware. Is their something I'm missing. Mine just sits at boot animation. What's your steps if you don't mind me asking bud.
Thank you

kountry83 said:
Hmm I wonder what I'm doing wrong. I followed the exact steps I did on the global firmware. Is their something I'm missing. Mine just sits at boot animation. What's your steps if you don't mind me asking bud.
Thank you
Click to expand...
Click to collapse
Not at all. Of course I unlocked both bootloader and critical.
Then I've extracted the AT&T Oreo file on Razers website into my adb folder and run the flash all .bat file. After first boot I allow it to update to latest Pie update. Are you on AT&T?? I'm the one that posted the captured OTA link.

@JDBarlow Yes I'm on latest At&T. I've had it working a few days ago but switched to global for a minute to do a vendor/system comparison. Now I can't get it to work again. Thank you for the it's captured link bud. I've done the same thing you did but my phone came development unlocked with different recovery setup. I backed up all of my development firmware.

kountry83 said:
@JDBarlow Yes I'm on latest At&T. I've had it working a few days ago but switched to global for a minute to do a vendor/system comparison. Now I can't get it to work again. Thank you for the it's captured link bud. I've done the same thing you did but my phone came development unlocked with different recovery setup. I backed up all of my development firmware.
Click to expand...
Click to collapse
@kountry83 I know bro I'm patiently waiting on someone (dev) to step up and take this device on..I love it man has so much potential if we had more development :good:

Nice to see someone taking a swing at it. So tired of people trash talking this phone, when it's capable of so much. I'm not a dev but seems to me that this phone would be easy to tinker with since Razer pretty much begs you to. Welp I guess JD and I will be here to test anything or help any way we can. I've really only seen him and one other dude using this phone on att. Openly that is. I ended up on global cause I hated waiting on att to release pie update.
JD, how's your cell connection quality? I can literally stare at my signal and it drops out completely from 3 bars or so. Maybe I could flash the modem.img to see if the basebands are different? I might just flash the Oreo att firmware them let it update, then flash arter kernel, then flash magisk zip within arter twrp to get root.

jonchance_84 said:
Nice to see someone taking a swing at it. So tired of people trash talking this phone, when it's capable of so much. I'm not a dev but seems to me that this phone would be easy to tinker with since Razer pretty much begs you to. Welp I guess JD and I will be here to test anything or help any way we can. I've really only seen him and one other dude using this phone on att. Openly that is. I ended up on global cause I hated waiting on att to release pie update.
JD, how's your cell connection quality? I can literally stare at my signal and it drops out completely from 3 bars or so. Maybe I could flash the modem.img to see if the basebands are different? I might just flash the Oreo att firmware them let it update, then flash arter kernel, then flash magisk zip within arter twrp to get root.
Click to expand...
Click to collapse
@jonchance_84 Honestly I've gotten such great reception in my area I haven't even diagnosed that. I can pay more attention to it and see what happens. We actually get the 5G Evo in our area..
The flashing sequence you stated above is the exact order I've done mine twice now and everything works very well!!
Edit: I don't get the 5Ge on the Razer 2.. didn't want you to think that ?

JDBarlow said:
@jonchance_84 Honestly I've gotten such great reception in my area I haven't even diagnosed that. I can pay more attention to it and see what happens. We actually get the 5G Evo in our area..
The flashing sequence you stated above is the exact order I've done mine twice now and everything works very well!!
Click to expand...
Click to collapse
I'm not even a mile from i-20 in East Texas. This is all I get on lte, but the weird thing is that never settles in.

@jonchance_84 I live in East Texas too! I got a little land, log cabin, man cave, and guest house that use to be a bed and breakfast lol. Love this country living. I'm on T-Mobile.

kountry83 said:
@jonchance_84 I live in East Texas too! I got a little land, log cabin, man cave, and guest house that use to be a bed and breakfast lol. Love this country living. I'm on T-Mobile.
Click to expand...
Click to collapse
Nice! Other than the heat right now, love it here. I work in IT for an oil and gas company. Starting to tinker more with Android as a hobby. Last phone was a Nexus 6. Always been able to flash, follow directions with no problem, but the dev side seems a bit tricky.

@JDBarlow
I just did the same thing you did with the at&t update and booted up to setup. Then booted to bootloader then flashed arter boot.img to both a and b. Tried to boot back to setup and hangs on boot animation. Don't get why I'm having a hard time getting this to boot off this kernel. Ugh

kountry83 said:
@JDBarlow
I just did the same thing you did with the at&t update and booted up to setup. Then booted to bootloader then flashed arter boot.img to both a and b. Tried to boot back to setup and hangs on boot animation. Don't get why I'm having a hard time getting this to boot off this kernel. Ugh
Click to expand...
Click to collapse
Any errors when flashing arter boot.img via fastboot?

jonchance_84 said:
Nice! Other than the heat right now, love it here. I work in IT for an oil and gas company. Starting to tinker more with Android as a hobby. Last phone was a Nexus 6. Always been able to flash, follow directions with no problem, but the dev side seems a bit tricky.
Click to expand...
Click to collapse
kountry83 said:
@JDBarlow
I just did the same thing you did with the at&t update and booted up to setup. Then booted to bootloader then flashed arter boot.img to both a and b. Tried to boot back to setup and hangs on boot animation. Don't get why I'm having a hard time getting this to boot off this kernel. Ugh
Click to expand...
Click to collapse
@kountry83 @jonchance_84
That's just freaking crazy lol I'm in East Texas too
Instead of flashing the kernel to both slots try ONLY <fastboot flash boot arter97.img> then reboot before installing magisk
Edit: the last time did this flashing sequence I actually booted to recovery right after installing arter97 installed magisk then booted to system

@jonchance_84 no errors. @JDBarlow just tried that also. Don't know what's going on here. I think it might be a little different hardware and software wise.

JDBarlow said:
@[email protected]_84
That's just freaking crazy lol I'm in East Texas too
Instead of flashing the kernel to both slots try ONLY <fastboot flash boot arter97.img> then reboot before installing magisk
Click to expand...
Click to collapse
Maybe he isn't setup with the a/b scheme?
Edit: Maybe the arter kernel isn't compatible with some hardware that's different? Causing kernel panic which results in bootloop? It's gotta be something simple though. Otherwise the att firmware wouldn't even boot at all.