Related
edited!
F.A.Q.​
1. If I unlock my phone's bootloader is my warranty void?
HTC Quote:
It is our responsibility to caution you that not all claims resulting or caused by or from the unlocking of the bootloader may be covered under warranty.
Click to expand...
Click to collapse
Usually HTC honours your warranty unless they know for certain that a hardware propblem or even a software problem has been caused by unlocking your bootloader or any other custom software installed.
2. Will this work with all variants of the One X+?
No. This will not work all the variants and will cause an IMEI loss and Wifi not working if you do not adhere to the Software Number posted above. A correct RUU flash will fix this.
For RUU's go here: http://forum.xda-developers.com/showthread.php?t=1918325
3. My software number is not there. How should I provide my boot.img
Sorry. Butif you have a RUU and are willing to test I will pm some instructions that might help and may work but I am not willing to put it out in the open as people will do things without listening.
4. Great, I'm rooted. Now what should I do?
Here are some links that might help you:
http://android.stackexchange.com/qu...my-phone-now-what-what-do-i-gain-from-rooting
http://lifehacker.com/5806135/the-10-best-android-apps-that-make-rooting-your-phone-worth-the-hassle
http://www.addictivetips.com/mobile/top-15-apps-to-install-after-rooting-your-android-device/
http://www.oneclickroot.com/root-android/top-5-things-to-do-after-rooting-your-android/
I'll add more when I have ideas or you could post some questions in the thread that are applicable
Thanks, great work!
What are the chance of this working with the AT&T version when it comes out?
thekalby said:
What are the chance of this working with the AT&T version when it comes out?
Click to expand...
Click to collapse
Give me a boot.img and I'll make one for that
Sent from my HTC One V
Unfortunately it doesn't work.
As soon as you click 'install-bootroot-windows.bat' it boots and then just hangs on the HTC Quietly Brilliant screen.
It boots immediately once you click on the .bat file. There is no time for anything to be pushed to the phone.
After you get bored looking at the boot screen and long press the power button, the phone just boots normally... no root.
EDIT: I manually booted the bootroot.img file and still no root.
EDIT 2: The boot image kills all data connections.
EDIT 3: I flashed the original boot.img and radios are still FUBARed. I suggest you pull this until you have tested it.
nobnut said:
Unfortunately it doesn't work.
As soon as you click 'install-bootroot-windows.bat' it boots and then just hangs on the HTC Quietly Brilliant screen.
It boots immediately once you click on the .bat file. There is no time for anything to be pushed to the phone.
After you get bored looking at the boot screen and long press the power button, the phone just boots normally... no root.
EDIT: I manually booted the bootroot.img file and still no root.
EDIT 2: The boot image kills all data connections.
EDIT 3: I flashed the original boot.img and radios are still FUBARed. I suggest you pull this until you have tested it.
Click to expand...
Click to collapse
Have you boot loader unlocked....also you have to be in fastboot....give me your stock boot.img and I'll upload another one...
Please provide your software version also....
Sent from my HTC One V using xda app-developers app
nobnut said:
Unfortunately it doesn't work.
As soon as you click 'install-bootroot-windows.bat' it boots and then just hangs on the HTC Quietly Brilliant screen.
It boots immediately once you click on the .bat file. There is no time for anything to be pushed to the phone.
After you get bored looking at the boot screen and long press the power button, the phone just boots normally... no root.
EDIT: I manually booted the bootroot.img file and still no root.
EDIT 2: The boot image kills all data connections.
EDIT 3: I flashed the original boot.img and radios are still FUBARed. I suggest you pull this until you have tested it.
Click to expand...
Click to collapse
You need to push the modules or else data/WiFi won't work.
Sent From My HTC Amaze 4G via Someone's Room
I unlocked and yes, I pushed the modules.
Please answer my questions....also u need the factory unlocked international version...... Give me your boot.img and I'll make one for you...
Sent from my HTC One V using xda app-developers app
shubhamchamaria said:
Please answer my questions....also u need the factory unlocked international version...... Give me your boot.img and I'll make one for you...
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
LOL You might have specified version requirements in the OP
Software version - 1.14.206.13 CL121576 release-keys
Baseband - 3.1204.167.31
EDIT: If you want me to test it, you'd better hurry up. It is a demo unit that I have to give back tomorrow. It doesn't matter that data isn't working as they can resolve that issue. I have my own device, which I haven't flashed.
It's still a load of balls. There is a problem with your script.
Just hangs on the Bootscreen and when you reboot no root (obviously).
nobnut said:
It's still a load of balls. There is a problem with your script.
Just hangs on the Bootscreen and when you reboot no root (obviously).
Click to expand...
Click to collapse
Try perm flashing it.....
fastboot flash boot bootroot.img
Keep your original boot image handy...
Sent from my HTC One V using xda app-developers app
If it doesn't work I'm guessing it could be a problem with my boot.img compiling script because it works for One V and should ideally work with this...
Sent from my HTC One V using xda app-developers app
I did that also. The same as I did yesterday when I lost data on the original version. It doesn't boot (just hangs) and after I flash the original version, data is gone.
Anyway, I don't care, I'm giving it back tomorrow.
---------- Post added at 12:33 PM ---------- Previous post was at 12:31 PM ----------
shubhamchamaria said:
If it doesn't work I'm guessing it could be a problem with my boot.img compiling script
Click to expand...
Click to collapse
That's what I said above... your script isn't doing whatever you wanted it to. It just boots immediately to the Bootscreen and then just hangs.
I'm outta here now. I've work to do.
nobnut said:
I did that also. The same as I did yesterday when I lost data on the original version. It doesn't boot (just hangs) and after I flash the original version, data is gone.
Anyway, I don't care, I'm giving it back tomorrow.
---------- Post added at 12:33 PM ---------- Previous post was at 12:31 PM ----------
That's what I said above... your script isn't doing whatever you wanted it to. It just boots immediately to the Bootscreen and then just hangs.
I'm outta here now. I've work to do.
Click to expand...
Click to collapse
The script itself works but there is a problem while compiling the image and I will look into it....
Sent from my HTC One V using xda app-developers app
Why release something that is not tested ?
All you get is a bunch of bricked phones.....
Please remove the download links. Also, when/if you do upload again, place proper instructions regarding requisite device lock status etc in the OP.
As a 'recognised contributor' you should know better.
I hope this gets unstickied soon.
nobnut said:
Please remove the download links. Also, when/if you do upload again, place proper instructions regarding requisite device lock status etc in the OP.
As a 'recognised contributor' you should know better.
I hope this gets unstickied soon.
Click to expand...
Click to collapse
I work my ass off to get root for a device I do not own and all I get is a load of bull****.....I am getting this thread locked...
Haters gonna hate....
Sorry to the grateful guys.....
Sent from my HTC One V using xda app-developers app
Come on guys. Relax here. Sure it wasn't tested but he did put effort. It doesn't work, then it doesn't work. He should remove the download link to make it so nobody had issues. Nobody should be talking down on anybody. Constructive criticism is fine but not flaming one another. We are a community. We help, not push new, potential devs who are looking to help. I didn't get to where I am by myself. I had support from the community. Now, my username is a google search and my stuff is popular. This is all thanks to community that I'm involved in.
Sent From My HTC Amaze 4G via Someone's Room
I did a quick battery pull and now whenever I turn the phone on, it keeps trying to update. SOOOO, is there a way to stop this or take it off through PC with ODIN????
I'm not ready to lose root yet....
Anybody have any ideas? Can I flash a custom rom through ODIN?
KappaAce2010 said:
Anybody have any ideas? Can I flash a custom rom through ODIN?
Click to expand...
Click to collapse
You sure you didn't brick your device? I was under the impression doing battery pulls during the update process would mess up your phone.
Someone posted something similar yesterday. Another person suggested pulling the sim card out and then rooting the phone as usual.
Edit: you already have root?
Dr. Cornelius asks you to calm down.
KappaAce2010 said:
Anybody have any ideas? Can I flash a custom rom through ODIN?
Click to expand...
Click to collapse
If the update went through, sorry, you're stuck for now. Here's a link to inform you of the situation.
http://forum.xda-developers.com/showthread.php?t=2359090
Crooke356 said:
Someone posted something similar yesterday. Another person suggested pulling the sim card out and then rooting the phone as usual.
Edit: you already have root?
Dr. Cornelius asks you to calm down.
Click to expand...
Click to collapse
Yes, I already have root. The phone is currently next to me with the battery out.
First off, I'm no expert here. I'm hesitant to offer any advise. Are you able to boot directly to recovery?
Dr. Cornelius asks you to calm down.
Phatdawg said:
You sure you didn't brick your device? I was under the impression doing battery pulls during the update process would mess up your phone.
Click to expand...
Click to collapse
Luckily no, but this is very frustrating. It hasn't fully loaded yet. Trying to figure out if there is a to do a factory reset and have go it go back to what it was in the box.
I would've responded sooner but since I'm a new member.... 5 minute interval responses.
Crooke356 said:
First off, I'm no expert here. I'm hesitant to offer any advise. Are you able to boot directly to recovery?
Dr. Cornelius asks you to calm down.
Click to expand...
Click to collapse
I tried that. It keeps trying to do that damn update.
I've never taken an OTA on a Samsung device. In my experience there is a prompt that verifies you want to install after the download. IF it's the same here, I would THINK your safe to Odin.
If you can get to recovery, throw a ROM on your SD card and flash.
Edit: oh new member
Dr. Cornelius asks you to calm down.
---------- Post added at 10:16 PM ---------- Previous post was at 10:10 PM ----------
By "loading" do you mean downloading? Or is actually installing?
Dr. Cornelius asks you to calm down.
you have to poke a accept after it downloads
then it boots to download mode
if you like
you can revert stock to MDK wipes everything
http://www.sxtpdevelopers.com/showthread.php?t=237
flash to complete stock and re-root ??
Not sure how far out of the way you would like to go..
I downloaded the OTA and let it site on the stock MDK phone for over a day before I rooted and installed ota root keeper to test to see if I can restore root..with out bricking
I could of easily delete the fota cache where it downloaded to and frozen the propitiate file to stop the update
Crooke356 said:
I've never taken an OTA on a Samsung device. In my experience there is a prompt that verifies you want to install after the download. IF it's the same here, I would THINK your safe to Odin.
If you can get to recovery, throw a ROM on your SD card and flash.
Edit: oh new member
Dr. Cornelius asks you to calm down.
---------- Post added at 10:16 PM ---------- Previous post was at 10:10 PM ----------
By "loading" do you mean downloading? Or is actually installing?
Dr. Cornelius asks you to calm down.
Click to expand...
Click to collapse
Its actually installing. Can't get into recovery.
Please read forum rules before posting
Questions and help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
KappaAce2010 said:
Anybody have any ideas? Can I flash a custom rom through ODIN?
Click to expand...
Click to collapse
no custom roms thru odin.
---------- Post added at 07:35 AM ---------- Previous post was at 07:33 AM ----------
get into recovery and just flash a custom rom.
If you have titanium backup, use it to freeze SDM 1.0 and FWUpdate. This will keep the new software from downloading and keep the software update notification from appearing (provided it hasn't been installed by now).
Sent from my SCH-I545 using Tapatalk 4 Beta
best idea has been said, get that thing into custom recovery where the OTA cant install. try beating the phone as it tries to install and get it into download mode and see if u can flash a custom recovery though ODIN
What you can do at this point depends a lot on what has already been updated on your phone.
If the bootloader is already updated, then there's no way for you to load the older kernel onto it to get it ready to root.
What I'd suggest you do is to go ahead at try the rooting process.
Boot the phone into download mode and try to push the MD2 kernel onto it,
If the install tries to restart, it'll fail since you don't have the expected software, which hopefully will give you a usable system.
Then use motochopper to try to get "su" access.
If ODIN refuses to flash the MD2 software, it's probably the case that you've already gone past the point of no return (i.e. you've got the updated, locked bootloader) and you might as well let the update finish.
If you succeed, then install MDK and Voodoo OTA Keeper and cross your fingers.
Good luck!
Q&A for Pure AOSP 4.4.4 ***international rom***
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Pure AOSP 4.4.4 ***international rom***. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
plsdontpwn.me seems to be down
plsdontpwn.me does not respond. Cloudflare reports host error.
sameersbn said:
plsdontpwn.me does not respond. Cloudflare reports host error.
Click to expand...
Click to collapse
Thanks, looking into it
sameersbn said:
plsdontpwn.me does not respond. Cloudflare reports host error.
Click to expand...
Click to collapse
It's back online now, thanks for pointing it out.
Lloir,
Trying to figure out why my SuperSU won't work properly on this ROM is beyond my skills. Works fine on Omni. Relocked, unlocked bootloader multiple times, flashed the ROM/gapps/supersu (2.16) via CWM, but still get "SU binary not installed and SuperSU can't install it...". Found su in system/xbin where my root checker app said it was, busybox installed v1.22.1 in system/xbin. Maybe su binary permissions are not correct? Anyway, if there is anything else I can do, please let me know when you get a moment. In the meantime, I am loving your AOSP 4.3. Yeah, I know, why go back to JB? Wanted to try your AOSP ROM as a daily driver (and need a camera) so it works perfectly.
I did learn from my past mistake and actually posted in the CORRECT thread.
Lloir,
I asked Chainfire about my SuperSU issues. From the logs I sent, was told the su daemon wasn't starting at boot time. Was told to ask if ROM supported starting install-recovery.sh at boot time? I hope my explanation makes sense. Thank you for your time.
stickt73 said:
Lloir,
I asked Chainfire about my SuperSU issues. From the logs I sent, was told the su daemon wasn't starting at boot time. Was told to ask if ROM supported starting install-recovery.sh at boot time? I hope my explanation makes sense. Thank you for your time.
Click to expand...
Click to collapse
I'm one person...Give me time
I have problem with starting ROM.
After flashing it is stuck on screen where is showing word Android (with animation). Left it like that for one hour and something, still didn't want to boot, restarted it, same thing. CWM is from link from thread.
Steps for flashing I applied:
1.Flashes rom zip from recovery, deleted cache and data before
2. Booted to fastboot and flashed kernel
3. Flashed gapps and rebooted
While waiting rom to start adb on my pc cannot see device.
Can you help me with this?
Sent from my HTC One X+ using XDA Free mobile app
komple said:
I have problem with starting ROM.
After flashing it is stuck on screen where is showing word Android (with animation). Left it like that for one hour and something, still didn't want to boot, restarted it, same thing. CWM is from link from thread.
Steps for flashing I applied:
1.Flashes rom zip from recovery, deleted cache and data before
2. Booted to fastboot and flashed kernel
3. Flashed gapps and rebooted
While waiting rom to start adb on my pc cannot see device.
Can you help me with this?
Sent from my HTC One X+ using XDA Free mobile app
Click to expand...
Click to collapse
you should have deleted system too not just cache and data. This rom 100% boots so it's something you are doing wrong.
komple said:
I have problem with starting ROM.
After flashing it is stuck on screen where is showing word Android (with animation). Left it like that for one hour and something, still didn't want to boot, restarted it, same thing. CWM is from link from thread.
Steps for flashing I applied:
1.Flashes rom zip from recovery, deleted cache and data before
2. Booted to fastboot and flashed kernel
3. Flashed gapps and rebooted
While waiting rom to start adb on my pc cannot see device.
Can you help me with this?
Sent from my HTC One X+ using XDA Free mobile app
Click to expand...
Click to collapse
Also, make sure you are flashing the Elite Kernel from nik3r and NOT the boot.img from the ROM zip. Like Lloir said, there's no reason for the ROM not to boot unless you've done something wrong.
Lloir said:
you should have deleted system too not just cache and data. This rom 100% boots so it's something you are doing wrong.
Click to expand...
Click to collapse
I was wrong sorry guys, wrong kernel.
Sorry for asking this, when can we expect camera or version 5.0?
---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------
stickt73 said:
Also, make sure you are flashing the Elite Kernel from nik3r and NOT the boot.img from the ROM zip. Like Lloir said, there's no reason for the ROM not to boot unless you've done something wrong.
Click to expand...
Click to collapse
I had wrong kernel, after posting this I realized that , off course
stickt73 said:
Lloir,
Trying to figure out why my SuperSU won't work properly on this ROM is beyond my skills. Works fine on Omni. Relocked, unlocked bootloader multiple times, flashed the ROM/gapps/supersu (2.16) via CWM, but still get "SU binary not installed and SuperSU can't install it...". Found su in system/xbin where my root checker app said it was, busybox installed v1.22.1 in system/xbin. Maybe su binary permissions are not correct? Anyway, if there is anything else I can do, please let me know when you get a moment. In the meantime, I am loving your AOSP 4.3. Yeah, I know, why go back to JB? Wanted to try your AOSP ROM as a daily driver (and need a camera) so it works perfectly.
I did learn from my past mistake and actually posted in the CORRECT thread.
Click to expand...
Click to collapse
Lloir,
After what seemed like forever, I found a solution to my problem of not having root access. Found this in another forum, but it solved the same problem I had:
Run in adb shell:
mount -o remount,rw /system
echo persist.sys.root_access=1 >> /system/build.prop
reboot
It's amazing what can happen when the search button is used.
Download links do not work
shalane said:
Download links do not work
Click to expand...
Click to collapse
It's being worked on, huge issue when the server got moved.
Lloir when will you upload bug free aosp 4.4.4 Rom for one x plus
Thanks in advance
pranavrocksharma said:
Lloir when will you upload bug free aosp 4.4.4 Rom for one x plus
Thanks in advance
Click to expand...
Click to collapse
Never :good:
Lloir said:
Never :good:
Click to expand...
Click to collapse
Sorry for posting the same post here and there.
Please don't change your decision.
Please
Q&A for [RECOVERY][volantis] TWRP 2.8.2.1 touch recovery [2014-11-18]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY][volantis] TWRP 2.8.2.1 touch recovery [2014-11-18]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Skid71 said:
...The .img file is in the same folder I start the command line from. The output reads just like the picture in your guide
At this point I'm wondering if the recovery_fixed.img is supposed to look like stock/aosp and not like TWRP...
Click to expand...
Click to collapse
The same happend to me yesterday. I don't know why. And not, the TWRP recovery looks like 'TWRP recovery'.
Finally, i chose the new CF-Auto-Root's ChainFire, because i only wanted to become root.
But i haven't TWRP recovery
Hi all, when I reboot into twrp recovery it takes a long time before its booted in recovery. Any ideas why?
hill67 said:
Hi all, when I reboot into twrp recovery it takes a long time before its booted in recovery. Any ideas why?
Click to expand...
Click to collapse
Maybe it's decrypting the data partition upon starting recovery...
guyd said:
Maybe it's decrypting the data partition upon starting recovery...
Click to expand...
Click to collapse
So decrypting the n9 would help getting faster in recovery?
hill67 said:
So decrypting the n9 would help getting faster in recovery?
Click to expand...
Click to collapse
Perhaps, but only the dev can really answer that with certainty.
hill67 said:
So decrypting the n9 would help getting faster in recovery?
Click to expand...
Click to collapse
Decrypting the N9 would do R/W operations a little bit faster (N9's Procesor is enought fast for this, although maybe something isn't optimized completly). I don't think your problem is because N9 is Encrypted.
But with you guys it boots at a normal speed into recovery?
hill67 said:
But with you guys it boots at a normal speed into recovery?
Click to expand...
Click to collapse
No, it takes a fair amount of time. Longer than my n5. I think what you're seeing is normal for the n9
Sent from my Nexus 9 using XDA Free mobile app
recovery with dead android and red triangle
So I think I may have done things out of order. I first logged into android and enable developer options and checked enable oem unlock. Rebooted into fastboot and ran the oem unlock. Without rebooting, I ran the fastboot command to rewrite twrp ( i think was the mistake ). I rebooted and now I have no recovery. I then reflashed the 5.0.1 factory image. https://developers.google.com/android/nexus/images . Still no default recovery or twrp. Any ideas on what I need to do.
zoidberg_md said:
So I think I may have done things out of order. I first logged into android and enable developer options and checked enable oem unlock. Rebooted into fastboot and ran the oem unlock. Without rebooting, I ran the fastboot command to rewrite twrp ( i think was the mistake ). I rebooted and now I have no recovery. I then reflashed the 5.0.1 factory image. https://developers.google.com/android/nexus/images . Still no default recovery or twrp. Any ideas on what I need to do.
Click to expand...
Click to collapse
Flash twrp again in fastboot. Then flash supersu 2.37 in twrp.
Sent from my Nexus 9 using XDA Free mobile app
Any news on twrp for the LTE model?
Vendor partition can't be unmounted
TWRP 2.8.5.0 can't unmount the /vendor partition, and also can't restore it from a nandroid backup. Maybe it's due to the changed vendor location in Lollipop. Can you please update TWRP to deal with this properly? Plz!!!!
Built for my Dev Edition but should work on the converted retail devices.
1. Full backup
2. Wipe EVERYTHING
3. Flash Roasted Marshmallow V2
4. Enjoy.
What's removed... everything. I only kept the Google stuff that reinstalls itself anyway and the base stuff to run the phone. Allshare, ANT, knox, verizon apps, etc. All gone.
this is a rebuild of the rom from an ADB pull of my current build without the apps i added for my daily use. should be pretty much bare bones.
android version: 6.0.1
baseband: cpd1
Kernel : 3.10.40 ([email protected]) [the one in the "marshmallow bootloader unlock" thread, i didnt change this]
thanks goes out to the devs that made the bootloader unlock thats made this possible for so many more people that didnt have an original dev edition.
Lol broken WiFi is is a major problem but hey, you just did more than I ever have so I'll flash it to see if all goes well
Sent from my SM-N915V using XDA-Developers mobile app
---------- Post added at 04:44 AM ---------- Previous post was at 04:43 AM ----------
luverbwoy said:
Lol broken WiFi is is a major problem but hey, you just did more than I ever have so I'll flash it to see if all goes well
Sent from my SM-N915V using XDA-Developers mobile app
Click to expand...
Click to collapse
Actually asks for decryption key so I can't download
Sent from my SM-N915V using XDA-Developers mobile app
Oops, try the link now. I am not used to sharing with mega yet.
Also on a side note, the WiFi may be broken because i am still using the KK bootloader 1ANL1. When i upgraded to MM i skipped out on the bootloader and just flashed the modded stock tar withough a bootloader so i wouldnt overwrite my dev edition boot.
those who took the update may not have a WiFi issue, but i included it in the broken because it is broken on mine and that may not be the only issue. if you flash it on yours and the WiFi works then i'll know thats the issue and i'll just change it to "WiFi broken if you are still using 1ANL1 bootloader".
also if you still cant download with that link let me know, and i'll move it to dropbox or something else.
Edit: WiFi fixed when I updated bootloader. So if you are on native Dev Edition do the full process where you flash the non Dev bootloader, convert back to Dev then upgrade to MM. Then you can flash in TWRP and all should go well.
luverbwoy said:
Lol broken WiFi is is a major problem but hey, you just did more than I ever have so I'll flash it to see if all goes well
Sent from my SM-N915V using XDA-Developers mobile app
---------- Post added at 04:44 AM ---------- Previous post was at 04:43 AM ----------
Actually asks for decryption key so I can't download
Sent from my SM-N915V using XDA-Developers mobile app
Click to expand...
Click to collapse
NekoShinigami said:
Oops, try the link now. I am not used to sharing with mega yet.
Also on a side note, the WiFi may be broken because i am still using the KK bootloader 1ANL1. When i upgraded to MM i skipped out on the bootloader and just flashed the modded stock tar withough a bootloader so i wouldnt overwrite my dev edition boot.
those who took the update may not have a WiFi issue, but i included it in the broken because it is broken on mine and that may not be the only issue. if you flash it on yours and the WiFi works then i'll know thats the issue and i'll just change it to "WiFi broken if you are still using 1ANL1 bootloader".
also if you still cant download with that link let me know, and i'll move it to dropbox or something else.
Edit: WiFi fixed when I updated bootloader. So if you are on native Dev Edition do the full process where you flash the non Dev bootloader, convert back to Dev then upgrade to MM. Then you can flash in TWRP and all should go well.
Click to expand...
Click to collapse
Okay well I just got home and I'm waiting for my computer tomorrow so I Can go back to stock to try it and figure out why Noble rom breaks the baseband and IMEI of the phone
Sent from my SM-G935F using XDA-Developers mobile app
---------- Post added at 03:47 AM ---------- Previous post was at 03:46 AM ----------
It did download now tho
Sent from my SM-G935F using XDA-Developers mobile app
Okay I flashed it and nothing happened, I just factory resetted and flashed it again and all the apps are still there. I also just upgraded to twrp 3.0.2.0 so I am going to downgrade it again and see if that was the reason nothing happened.
Downgraded back to TWRP 3.0.0.0 and flashed it again, and still no changes
---------- Post added at 10:22 PM ---------- Previous post was at 10:12 PM ----------
There's another debloat script that works on our phones, the problem is it deletes so many things that it also removes access to private mode, it's here thanks to Danterape
Ok it only works on that particular rom apparently, it causes bootloops on stock
I tried installing the rom and it took awhile to boot up. I was able to connect to my wifi but setup forced closed before the end. I was forced to go through setup again and again with the same force close. I tried to go through setup with wifi, without wifi, with my sim card, without my sim card. It made no difference. I am on lollipop 5.01
I took a look at the zip, and it looked awfully small. There seems to be a LOT of files missing, and several empty folders that a normal ROM would have chock FULL of stuff. Like, the "priv-app" app folder is 100% empty. What happened to all the file that should be there? And the list of stuff in "system/app" ends at "FlashAnnotateSvc". There should be a ton more things there.
Is there something I'm missing here?
sorry my internet is bad lately, it probably got corrupted, i'll take it down and re-up i'll remove the links until fixed.
the file is on my laptop so i'll have to try it from there later this evening. sorry for inconvenience. Also if anyone wants it i can upload the archi kitchen files i used in making it.
Sounds good. I'm actually using your zip as a reference for mine. Might need some help getting mine going more.
Let's get some life back into the 915V!
chevycam94 said:
Sounds good. I'm actually using your zip as a reference for mine. Might need some help getting mine going more.
Let's get some life back into the 915V!
Click to expand...
Click to collapse
Sounds great, i'd love to work with you on this. myself being limited on time it'd be nice to have someone to bounce ideas to/from. I am still relatively new to rom making so it'd be an excellent learning experience for me as well. not sure what tools you are using currently, but i am running archi kitchen on linux mint 18. the kitchen isnt officially supported anymore so it took a bit to setup, but i find it easy to use. at least it was pretty easy for 4.4.4.... 6.0.1 is giving me a little headache, lol copying the system folder keeps getting interrupted, which i overlooked before somehow, but many of the odex files are >100kb and terminal emulator keeps throwing an error out, so right now i am running adb and pulling the folder that way. once i repack it you can have a huge head start there
here is the old 4.4.4 zip
https://www.dropbox.com/s/gfy850bbb9aq18n/superdebloatedwithalittlebloat.zip?dl=0
for reference...
Uploads finished, enjoy and let me know what you think.
Still can't get native tethering running but luckily foxfi still runs on 6.0.1
I have same phone as you, and it just bootloops--gets to screen with Custom, and reboots. (V2)
NekoShinigami, if you want to use my v2.00 ROM as a base, go for it. Might save you quite a bit of headache. I tend to find it much easier if you start by using a factory image, and go from there.
I tried flashing again and it runs fine for me. Did you get the full 1.18gb? I'll take another look at it again.
Also did you upgrade to the unlocked 6.0.1 bootloader?
Edit: nevermind I just read in the other thread that you did not, that is most likely why you are boot looping. This rom and the kernel that is in it won't run on the 1ANL1 bootloader.