My phone wont turn on wifi. I tried factory reset multiple times. nothing is working. help.
233AK said:
My phone wont turn on wifi. I tried factory reset multiple times. nothing is working. help.
Click to expand...
Click to collapse
Did you flash any roms or make any other changes to your phone ?
clsA said:
Did you flash any roms or make any other changes to your phone ?
Click to expand...
Click to collapse
yeah im using the Android Revolution HD rom.
Wild guess: you are on latest ARHD and you didn't update your firmware to 3.28.401.x, aren't you
Lol, we really need a sticky or something for the latest update. Or the ROM devs need to include a warning. (Not that im saying its any of their responsibility)
bloodhawk said:
Lol, we really need a sticky or something for the latest update. Or the ROM devs need to include a warning. (Not that im saying its any of their responsibility)
Click to expand...
Click to collapse
Not going to help mate, the people don't bother to read, that's the problem.
All the developers can put a warning in THIS BIG and the majority of the people will still scroll past it to just download the ROM in their rush to be "cool hackerz"
There is plenty enough proof of that already, developers clearly state in RED in their first post, THIS WILL NOT WORK WITH VERIZON and within the first 10 replies an idiot will come out and ask "Will this work with Verizon?"
Always read the last several pages on any rom you flash. You will always see any current issues or hot topics that way.
Read read read. That's a requirement for this hobby. ?
update post. I switched roms and still having the same problems. I'm using venom now.
KJ said:
Always read the last several pages on any rom you flash. You will always see any current issues or hot topics that way.
Read read read. That's a requirement for this hobby. ?
Click to expand...
Click to collapse
First 2 pages and last 3 is a must definitely! :good:
---------- Post added at 06:03 AM ---------- Previous post was at 06:01 AM ----------
233AK said:
update post. I switched roms and still having the same problems. I'm using venom now.
Click to expand...
Click to collapse
What version of venom?
233AK said:
update post. I switched roms and still having the same problems. I'm using venom now.
Click to expand...
Click to collapse
Ok first thing, goto the bootloader and check what the OS field says. If it is anything under 3.XX.XXX.X, then your need to update your firmware. Otherwise the problem is something else.
bloodhawk said:
Ok first thing, goto the bootloader and check what the OS field says. If it is anything under 3.XX.XXX.X, then your need to update your firmware. Otherwise the problem is something else.
Click to expand...
Click to collapse
Won't it give the OS version for the ROM he has on which might be 3.x anyways?
I also think it's outdated firmware on his part, radio firmware needs to be updated in order for data, mobile, wifi, bluetooth etc to function properly. This guy can't be bothered so I don't know why we bother either.
ARHD - 10 to 1 he used 21.0
Venom - 10 to 1 it's 3.0
But we should guess these things because he doesn't answer anyone when asked. What version was he on before? Most likely a 2.x but we won't know that either because
He didn't take note of it before he flashed away
He doesn't want to make the effort
It's easier to just expect others to do everything for you.
BerndM14 said:
Won't it give the OS version for the ROM he has on which might be 3.x anyways?
I also think it's outdated firmware on his part, radio firmware needs to be updated in order for data, mobile, wifi, bluetooth etc to function properly. This guy can't be bothered so I don't know why we bother either.
ARHD - 10 to 1 he used 21.0
Venom - 10 to 1 it's 3.0
But we should guess these things because he doesn't answer anyone when asked. What version was he on before? Most likely a 2.x but we won't know that either because
He didn't take note of it before he flashed away
He doesn't want to make the effort
It's easier to just expect others to do everything for you.
Click to expand...
Click to collapse
:cyclops:
I think when i flashed IC 5.0.0 without updating the firmware, my OS version still said 2.XX.XXX.X.Though It is as you say the radio firmwares need to be updated.
Changed to the new one once i flashed the update.
But yeah, you'r right, not many people willing to search the forums. The same issue has been discussed at least 20 times now. With 5 threads on the 2-3 pages of the Q&A section. I found my solution within maybe 2 mins and after reading less than 2 pages of the ROM i was updating. to.
bloodhawk said:
:cyclops:
I think when i flashed IC 5.0.0 without updating the firmware, my OS version still said 2.XX.XXX.X.Though It is as you say the radio firmwares need to be updated.
Changed to the new one once i flashed the update.
But yeah, you'r right, not many people willing to search the forums. The same issue has been discussed at least 20 times now. With 5 threads on the 2-3 pages of the Q&A section. I found my solution within maybe 2 mins and after reading less than 2 pages of the ROM i was updating. to.
Click to expand...
Click to collapse
Oh ok, I thought maybe it took that information from the build as well which would show the ROM's version(3.28.401.7) kinda like doing a getprop
I only flashed a custom ROM once and honestly, didn't even have a look at the OS in bootloader and even if I did happen to look at it the version probably wouldn't have shown what we're looking for now(I was updated to latest firmware so didn't have issues)
BerndM14 said:
Oh ok, I thought maybe it took that information from the build as well which would show the ROM's version(3.28.401.7) kinda like doing a getprop
I only flashed a custom ROM once and honestly, didn't even have a look at the OS in bootloader and even if I did happen to look at it the version probably wouldn't have shown what we're looking for now(I was updated to latest firmware so didn't have issues)
Click to expand...
Click to collapse
The bootloader pulls it probably from the hardware chip or something and then matches, if it doesn't, it shows up in RED. I could be wrong though.
Getprop pulls it from a .ro file on one of the partitions.
I had a massive heart attack when i first got the phone though. Couldn't unlock the bootloader as well since some partition detail was messed up. Talked to some Dev at HTC, and a day later a very convenient 'GPS' OTA shows up and all is good after that. But before i contacted HTC, i thought maybe flashing over some OTA is gonna sort it for me, the phone was on 2.22.1540.4 and i flashed over the 2.22.1540.3 OTA. Was stuck in RUU flash mode for a few hours and couldn't find anything on the forums, the only way to boot the phone was to use fastboot oem boot string. But it would get stuck in the RUU mode after every restart. That is when i noticed the differences on what the OS field says.
Once the correct OTA was flashed all was golden.
Im now waiting for the Dev edition or GPE to get Lollipop and im gonna convert to that SKU.
bloodhawk said:
The bootloader pulls it probably from the hardware chip or something and then matches, if it doesn't, it shows up in RED. I could be wrong though.
Getprop pulls it from a .ro file on one of the partitions.
I had a massive heart attack when i first got the phone though. Couldn't unlock the bootloader as well since some partition detail was messed up. Talked to some Dev at HTC, and a day later a very convenient 'GPS' OTA shows up and all is good after that. But before i contacted HTC, i thought maybe flashing over some OTA is gonna sort it for me, the phone was on 2.22.1540.4 and i flashed over the 2.22.1540.3 OTA. Was stuck in RUU flash mode for a few hours and couldn't find anything on the forums, the only way to boot the phone was to use fastboot oem boot string. But it would get stuck in the RUU mode after every restart. That is when i noticed the differences on what the OS field says.
Once the correct OTA was flashed all was golden.
Im now waiting for the Dev edition or GPE to get Lollipop and im gonna convert to that SKU.
Click to expand...
Click to collapse
Yeah perhaps it does get it from boot.img or something similar, even then the new ROM flashed already contains those version numbers so I just figured it'll show the ROMs number and not the old OS version. Either way... It's cool. Like I said I never actually bothered to look at the OS Version there when I flashed Venom, had it on for 2 days and went back to stock(converted to Dev Edition).
GPE Will no doubt have it faster but I don't want to convert to GPE. Personally I'm not a major fan of "vanilla android". I actually like Sense. So hopefully it won't be too long after GPE gets the update that it'll roll out for Dev Edition.
That said, I'll probably do the exact opposite of what I just said and convert to GPE anyways just to see what Lollipop is like
BerndM14 said:
Yeah perhaps it does get it from boot.img or something similar, even then the new ROM flashed already contains those version numbers so I just figured it'll show the ROMs number and not the old OS version. Either way... It's cool. Like I said I never actually bothered to look at the OS Version there when I flashed Venom, had it on for 2 days and went back to stock(converted to Dev Edition).
GPE Will no doubt have it faster but I don't want to convert to GPE. Personally I'm not a major fan of "vanilla android". I actually like Sense. So hopefully it won't be too long after GPE gets the update that it'll roll out for Dev Edition.
That said, I'll probably do the exact opposite of what I just said and convert to GPE anyways just to see what Lollipop is like
Click to expand...
Click to collapse
Big sense fan here myself.. But cant wait for thr sense update. Let's see how fast they do it.
In the mean time hope the OP UPDATED his firmware.
bloodhawk said:
Big sense fan here myself.. But cant wait for thr sense update. Let's see how fast they do it.
In the mean time hope the OP UPDATED his firmware.
Click to expand...
Click to collapse
:laugh: I was just thinking that... yet somehow I doubt it, next post will probably be to ask how he does that.
Oh well, we should probably stop high jacking his thread even though he started it and doesn't say anything in it himself.
I've never seen so many people not read the threads before blindly flashing things, seriously.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Related
Magnolia X 1.0 Initial Release (4/26/2012)
I have paused development of this ROm while I work on my own tweaks app, a skin and CM style notification toggle. I will be back up in a week or so. Please feel fre to try the ROM, below, but just be aware it is pretty bare-bones right now. It is still very smooth, snappy and stable, however.
This is the initial release of my One X ROM. My focus is on stable, smooth and simple ROMs - the kind I use myself on a daily basis. If you like flashy, super tweaked ROMs, this may not be for you. This is just an initial base ROM that I will be building from, as I get more into the device and possibilities for modding. There is MUCH more to come, including CM-Style Notification Toggles (j4n87 beat me to quick settings...) and my full matte Rosie theme, which HTC seems to have partially taken for sense 4.0... (http://forum.xda-developers.com/showpost.php?p=16944397&postcount=1)
If you like the ROM, please hit the thanks button...!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FEATURES
Based on Latest OTA update for Asia WWE 1.28.707.10;
Unsecured stock kernel with edits for init.d, nano text editing, etc;
Tegra3 power mngmt fixed and full GPU rendering, courtesy of the great mike1986;
All bloatware and extraneous images, etc. removed;
My own blend of init.d scripts (combined into one script) for stable and smooth performance;
Semi-transparent notifications bar (app drawer to come once m10 tools done);
Recent apps key remapped to settings, long press home key for recent apps (this does NOT have the volume key media mod, as I can't stand it);
Simple extended power menu mod, just has the additional reboot functions (NOT part of a tweaks program);
All widgets & app shortcuts, except the weather clock, removed from home screens on first boot so you don't have to waste time removing them...
PNGs in main graphics apks (com.htc.resources, framework-res, Rosie, etc.) optimized;
More I can't remember...
Known Issues
After first boot graphics on notifications bar gimped, this goes away after another reboot;
All gapps may not be perfectly up-to-date...;
Installation Instructions
MAKE A NANDROID BACKUP!!!
It is best, but not absolutely necessary, to have the latest 1.28.707.10 firmware on your device. If you already have the latest firmware, ignore the following. If you don't, do this:
- re-lock your bootloader (reboot to fastboot and type "fastboot oem lock" in terminal/command prompt),
- flash the 1.26.707.2 RUU (here),
- install the OTA update when you are prompted to,
- unlock bootloader at htcdev.com,
- flash CWM recovery (see this forum for the thread), and you are set to go...
Flash the boot.img linked to below by placing the "boot.img" in the same folder as your fastboot file, booting into fastboot and then typing "fastboot flash boot boot.img" (in OS X, you can place the boot.img in your home folder);
No need to wipe anything as flashing this ROM will wipe everything for you, including data --- I REPEAT, FLASHING THIS ROM WILL WIPE EVERYTHING, INCLUDING YOUR DATA!!! This will NOT happen in future versions (although I always suggest a full wipe before flashing);
Flash the ROM in CWM recovery;
Let things settle down, sync, etc.;
Enjoy, and post feedback, suggestions in the thread....
Downloads
boot.img (FLASH FIRST!!)
Mirror 1 (Goo-IM): http://tinyw.in/HwgY
Mirror 2 (MediaFire): http://www.mediafire.com/download.php?6d4n0tsqnkk5t1o
MD5: f0c09cc279256ddf591d75c1f3e0aa80
ROM
Mirror 1 (Dev-Host): http://d-h.st/5BI
Mirror 2 (FileFactory):http://www.filefactory.com/file/xc5oxx6vsa1/n/Magnolia_X_1_0.zip
Mirror 3 (Dropbox): http://bit.ly/Ic6i6o
MD5: 3669bf4c13795b4868b57a4d34aa44d9
Thanks & Credits
Mike1986 for spotting the tegra3 power screw up and for the full GPU mod;
j4n87, |||bored|||, Chingy and blubbers for the code that I based my key remaps and power menu tweaks off of (coded them myself, but these were the models);
Goo Inside Me for hosting my ROMs for free;
XDA and all its devs for being awesome;
If I missed anyone else, it was UNINTENTIONAL, and a PM will see things set straight!
WARNING
While I have tested this ROM extensively, I cannot guarantee that it is free from bugs and/or will not harm your device. Accordingly, YOU FLASH THE ROM LINKED TO IN THIS POST AT YOU OWN RISK. I cannot and will not be held responsible in any way for anything that may happen to you, your device or others as a direct or indirect result of flashing the ROM linked to in this post.
Changelog
This is the initial release...
Just in case
This is for the inevitable other stuff that comes up later on...
Hello Nice to see another dev....
I think you are uploading ?... Must wait for download....
JEZ69 said:
Hello Nice to see another dev....
I think you are uploading ?... Must wait for download....
Click to expand...
Click to collapse
Nope. It's up. Mediafire just stinks. I am working on a better mirror, but giving me a hard time...
Thank s to reply
Ok don t worry ....we will wait ...just happy to test new rom
Just one question the screen scrolling lags are gone with this Rom?
no longer with verizon
nice work though sk806
nitsuj17 said:
no longer with verizon
nice work though sk806
Click to expand...
Click to collapse
My tablet is Verizon, well one of them...I have been travelling for work a lot and vzw is not great for that. I also still have my rezound.
I am pondering whether to release my rezound Rom....
Sent from my HTC One X using xda premium
So tell me why should i use yours?
and not the others`?
will be testing this tonight...
hyundai2010 said:
So tell me why should i use yours?
and not the others`?
Click to expand...
Click to collapse
I have no idea. Do what makes you happy.....
Oh, and this is based on the RUU for Asian WWE units, so there may be some nice synergies for those, like me, who don't have an EU device.
Steve
hyundai2010 said:
So tell me why should i use yours?
and not the others`?
Click to expand...
Click to collapse
here's some reasons:
1. because you can
2. why not?
3. that rosie theme mod that you read about in the OP right?
sk806 said:
I have no idea. Do what makes you happy.....
Oh, and this is based on the RUU for Asian WWE units, so there may be some nice synergies for those, like me, who don't have an EU device.
Steve
Click to expand...
Click to collapse
By asian WWE units....do you mean batches made in china? I have the SH23 batch...may try this out.
Also, do you have screen flicker issue on light grey colors?
JEZ69 said:
Thank s to reply
Ok don t worry ....we will wait ...just happy to test new rom
Just one question the screen scrolling lags are gone with this Rom?
Click to expand...
Click to collapse
I put up a dropbox mirror for now. Will also have filefactory in a bit. Wonder why Goo.im isn't working for me....
Oh, and I see no lag in scrolling, although I think we really need to flatten the 3D effect some. I know it's supposed to be better than 3.5, but I am getting seasick. I have integrated the 3.5 "ultrasmooth" mod into it (my test rom, not this release), but HTC changed the code where the "smooth" part of the mod goes, so it's not quite there. I am still trying to figure out how it all works in sense 4.0...
Steve
thanks for mirroir ....testing will start
pewpewbangbang said:
By asian WWE units....do you mean batches made in china? I have the SH23 batch...may try this out.
Also, do you have screen flicker issue on light grey colors?
Click to expand...
Click to collapse
Yes, that is what I mean. Serial numbers that start with SH23. However, I especially mean those who have the 1.2x.707.x firmware, which, I understand, is quite a lot of people...
No screen flicker issues with light gray, but I have noticed it when you are using the still camera outside and move around...pictures still fine, but kind of annoying.
sk806 said:
Yes, that is what I mean. Serial numbers that start with SH23. However, I especially mean those who have the 1.2x.707.x firmware, which, I understand, is quite a lot of people...
No screen flicker issues with light gray, but I have noticed it when you are using the still camera outside and move around...pictures still fine, but kind of annoying.
Click to expand...
Click to collapse
Is firmware the build number? My first HTC device haha....have had samsung for like my past 3 androids. All the Galaxy basically.
Im running ARHD and im guessing my build number/RUU is 1.28.401.9, is that firmware? I'll probably do a backup and try out your ROM later today.
pewpewbangbang said:
Is firmware the build number? My first HTC device haha....have had samsung for like my past 3 androids. All the Galaxy basically.
Im running ARHD and im guessing my build number/RUU is 1.28.401.9, is that firmware? I'll probably do a backup and try out your ROM later today.
Click to expand...
Click to collapse
Firmware is different. Generally an RUU or OTA update will have a separate package that installs firmware, which is basically what makes your hardware work (this is simplifying a great deal), while the ROM, through the kernel, is the software that works with the firmware/hardware. So, for instance, a firmware package might change your radio, while a ROM will not. I have run ROMs meant for the EU firmware on my phone just fine...I have the dreaded "No CID" version, so I can't switch firmware to the EU version.
Hope this helps.
Steve
sk806 said:
Firmware is different. Generally an RUU or OTA update will have a separate package that installs firmware, which is basically what makes your hardware work (this is simplifying a great deal), while the ROM, through the kernel, is the software that works with the firmware/hardware. So, for instance, a firmware package might change your radio, while a ROM will not. I have run ROMs meant for the EU firmware on my phone just fine...I have the dreaded "No CID" version, so I can't switch firmware to the EU version.
Hope this helps.
Steve
Click to expand...
Click to collapse
hmm I have no CID also....well about to try out ur ROM
how exactly do u check firmware also then?
sk806 said:
I put up a dropbox mirror for now. Will also have filefactory in a bit. Wonder why Goo.im isn't working for me....
Oh, and I see no lag in scrolling, although I think we really need to flatten the 3D effect some. I know it's supposed to be better than 3.5, but I am getting seasick. I have integrated the 3.5 "ultrasmooth" mod into it (my test rom, not this release), but HTC changed the code where the "smooth" part of the mod goes, so it's not quite there. I am still trying to figure out how it all works in sense 4.0...
Steve
Click to expand...
Click to collapse
I m still testing and everything goes ok...Nice job...
Have you tweaks rosies?...because it s run with less lag...
I m with eu firmware 1.28.409.1 and flash was ok ...no probleme
Thank s
Update: this will not work on the recent firmware updates.
Hey, you can't jailbreak an Android.. yeah, i know, but "Jailbreak" is a protected act under the USA DMCA Exemption of 2012 and "Unlocking" is illegal without carrier permission. There will be no misunderstandings here.
WARNING:
This is not a normal bootloader unlock. This is even higher. It's an IROM unlock. This device went from the most secure Galaxy Note 10.1 to the least secure. After performing the technique in this thread your device will allow you to flash a Justin Beiber MP3 over your bootloaders (that means a hard brick). BE VERY CAREFUL and never flash with Odin or Heimdall unless you're absolutely sure it is intended for a SCH-I925. Odin or Heimdall can easily brick your device.
Introduction
CASUAL will guide you through the process of unlocking your bootloader using exploits developed by Lee Harrison. It works on Windows, Linux, and Mac. Put your device into “Developer Mode>USB Debugging”. Click the do it button. Any problems will be addressed with updates. See the About CASUAL section below.
Overview
You are expected to be STOCK.... Stock anything, but stock. This will install a stock kernel and that may affect non-stock roms. You will need to download and execute the CASUAL application below. Make sure you're connected to the internet. Then click the Do It! button. You need Java. Do you have Java?.
Windows 32/64 Users: CASUAL will put your device into Download Mode. It will automatically flash everything. If drivers are required, jrloper's CADI (CASUAL Automated Driver installer) will handle it. Make sure you're connected to the internet.
Linux 32/64/raspberry pi Users There may be a permission escalation in order to install heimdall, either way sit back and relax. CASUAL automates the entire process.
Please run the following in a terminal first:
Mac Users: Mac works easierr than any other system at the time of this release on 32bit systems. Please report problems.
Download
Take Note Verizon CASUAL(R478b) CASUAL is used to automate the process. The exploit was developed by Elite Recognized Developer Ralekdev and packaged by AdamOutler. To run CASUAL you need Java. Do you have Java?
Note: Please don't mirror this file. Link to this thread for download. d-h.st is a fast server. If I find people mirroring old versions of CASUAL, i will throw the killswitch and their browser will bring them back here to download the new one so they end up downloading it twice, otherwise I have to support multiple versions.
Videos
Demonstration on Linux. It is roughlty the same on Windows and Mac, but if anyone wants to make a video I will put it here.
About CASUAL
CASUAL stands for Cross-platform ADB Scripting, Univeral Android Loader. CASUAL jar files are a wrapper for the CASUAL scripting language. CASUAL allows rapid and accurate deployment of hacks and exploits. CASUAL is an Open Format, meaning, you can find out as much as you need to about how it works because they're easily taken apart and modified with WinZip. CASUAL is also secure. At any time, if a serious problem is detected with any script, the kill-switch will be flipped and you will be brought to a support page (most likely here) so you can download the latest version. Otherwise for minor corrections, new CASUAL scripts can be deployed remotely.
Here's a picture of CASUAL and a Verizon GNote10.1 running Team Win Recovery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Change Log
3May13: Initial Release
6May13: Updated Recovery to support Internal SD. -R478b
This unlock was basically identical to the second Galaxy Note 2 unlock except I had to add a few more tweaks because we're shoving a modified N8010 bootloader onto the i925.
great work guys as usual! you guys never cease to amaze me
Does this install the same TWRP version as Dees-Troy is working on in this forum? Just curious because that one is pretty rough with touch issues and it would be great to have a more functional one. I have the 8013...
Sent from my note 2
I have the U.S. Cellular i925u. Is there anyway to get this to work. I'm not interested in keeping the 4g capability. I'm ok with using WiFi only. I tried using the Casual install but it failed.
JasonGeiger said:
Does this install the same TWRP version as Dees-Troy is working on in this forum? Just curious because that one is pretty rough with touch issues and it would be great to have a more functional one. I have the 8013...
Sent from my note 2
Click to expand...
Click to collapse
This was packaged from the TWRP nightly released last night.
pro_b said:
I have the U.S. Cellular i925u. Is there anyway to get this to work. I'm not interested in keeping the 4g capability. I'm ok with using WiFi only. I tried using the Casual install but it failed.
Click to expand...
Click to collapse
CASUAL will let you root, but it won't install files that will damage your device. Even if it would, it's a bad idea. This is an IROM unlock, intended for Verizon devices only. IROM unlock means you can flash anything you want including files that destory your device.
You don't need this if you can flash custom kernels and ROMs. We have taken down all defenses here. If the U.S. Cellular version is locked down and you cant flash kernels/ROMs without it, I can release a new, updated version.
beanstown106 said:
great work guys as usual! you guys never cease to amaze me
Click to expand...
Click to collapse
This is so awesome man. Great stuff, beans is right, you guys really never cease to amaze. Now I need jellybeans Rom on my jail broken note 10.1. Ahem..................... I think we know who I'm talking to.
Sent from my HTC6435LVW using Tapatalk 2
AdamOutler said:
This was packaged from the TWRP nightly released last night.
CASUAL will let you root, but it won't install files that will damage your device. Even if it would, it's a bad idea. This is an IROM unlock, intended for Verizon devices only. IROM unlock means you can flash anything you want including files that destory your device.
You don't need this if you can flash custom kernels and ROMs. We have taken down all defenses here. If the U.S. Cellular version is locked down and you cant flash kernels/ROMs without it, I can release a new, updated version.
Click to expand...
Click to collapse
Thanks Sir. The U.S. Cellular version is locked down like the Verizon version as far as I can tell. Since the US Carriers decided to do the same crap with the bootloaders. I have root using framaroot but I'm unable to install a recovery or flash a kernel.
pro_b said:
Thanks Sir. The U.S. Cellular version is locked down like the Verizon version as far as I can tell. Since the US Carriers decided to do the same crap with the bootloaders. I have root using framaroot but I'm unable to install a recovery or flash a kernel.
Click to expand...
Click to collapse
Hit me up on an email with the output of terminal emulator command "cat /system/build.prop"
Update: rebooted windows 8 and the install went through fine.
Adam,
So here is what I am seeing, see the pictures attached
Alright guys. I'm uploading two new packages....
The first one is the latest copy of the Take Note Verizon jailbreak. It includes a modified Recovery by Dees_Troy. Our Note 10.1's are different than the other ones.
Differences: The partition structure is totally different. The kernels are totally different. This means you will soft-brick your device by flashing anything in these forums involving a recovery or a kernel other than this one. That being said..... It may be a good idea to get a separate forum. If you are interested, please start a *NEW THREAD* in General forums listing all the i925 specific threads which could be moved.
Alright. For the second part, I'm uploading a Rooted back-to-stock which I packaged from my own device before unlocking it and flashing stuff. Here's the technique used. http://forum.xda-developers.com/showthread.php?t=2082951 . This file is large so it will be a while before it's uploaded. The files included are basically everything needed to safely get back from a custom ROM and be rooted stock again.
Files included: boot.img, hidden.img, modem.bin, param.bin, recovery.img, system.img
We don't have a way to remove the modified system status currently. There is no completely back to stock.
AdamOutler said:
Alright guys. I'm uploading two new packages....
The first one is the latest copy of the Take Note Verizon jailbreak. It includes a modified Recovery by Dees_Troy. Our Note 10.1's are different than the other ones.
Differences: The partition structure is totally different. The kernels are totally different. This means you will soft-brick your device by flashing anything in these forums involving a recovery or a kernel other than this one. That being said..... It may be a good idea to get a separate forum. If you are interested, please start a *NEW THREAD* in General forums listing all the i925 specific threads which could be moved.
Alright. For the second part, I'm uploading a Rooted back-to-stock which I packaged from my own device before unlocking it and flashing stuff. Here's the technique used. http://forum.xda-developers.com/showthread.php?t=2082951 . This file is large so it will be a while before it's uploaded. The files included are basically everything needed to safely get back from a custom ROM and be rooted stock again.
Files included: boot.img, hidden.img, modem.bin, param.bin, recovery.img, system.img
We don't have a way to remove the modified system status currently. There is no completely back to stock.
Click to expand...
Click to collapse
Looking forward to trying this
So does N8010 boot loader mean N8010 ROMs or no...
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
DJsCrIBbLe said:
So does N8010 boot loader mean N8010 ROMs or no...
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
no. The hardware is different. The bootloaders are similar. You need a different kernel
As a note: Never flash an N8010 bootloader. this is a SPECIAL bootloader based on the N8010 bootloader. Just pretend it has nothing to do with N8010. For all practical purposes, this is an I925 bootloader we crafted out of an N8010 because we didn't have a i925 to work with.
Ok thanks, mostly just curious as i own the N8013 but considered the verizon version or selling and getting the unlocked international.
Thanks a ton Adam! Worked perfectly.
So if I have this correctly, we will be running stock until we get a dev to start working on our variant? I would assume that the other roms wouldn't install correctly with the partitions being different correct?
*Madmoose* said:
Thanks a ton Adam! Worked perfectly.
So if I have this correctly, we will be running stock until we get a dev to start working on our variant? I would assume that the other roms wouldn't install correctly with the partitions being different correct?
Click to expand...
Click to collapse
Yeah... don't flash nothin' or you will die. . We need a ROM dev.
Great work Adam, almost sent you a PM begging you to take this project on about 6 weeks ago... thanks!
But I had some problem as I ran the script, it stopped after it had rebooted and was stuck in Download Mode and asked me for my XDA username for some pastebin. The last information in that pastebin was:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
ERROR: Protocol initialisation failed!
Releasing device interface...
[ERROR]
[Heimdall Error Report] Detected:
Heimdall failed to initialize protocol; Script halted
[/Heimdall Error Report]
[DEBUG]HALT RECEIVED
[DEBUG]Finishing remaining commands:$SENDLOG
[DEBUG]Sendlog Command Issued!
No remaining commands
[DEBUG]Pastebin Login Successful
Click to expand...
Click to collapse
After unpluging and holding the power down for a few secs it rebooted as usually, but I dont know if it completed or not... how do I know if the bootloader got unlocked?
If you would like to see the pastebin then I'd be glad to be able to help, just let me know.
Thanks again,
Snarlster said:
Great work Adam, almost sent you a PM begging you to take this project on about 6 weeks ago... thanks!
But I had some problem as I ran the script, it stopped after it had rebooted and was stuck in Download Mode and asked me for my XDA username for some pastebin. The last information in that pastebin was:
After unpluging and holding the power down for a few secs it rebooted as usually, but I dont know if it completed or not... how do I know if the bootloader got unlocked?
If you would like to see the pastebin then I'd be glad to be able to help, just let me know.
Thanks again,
Click to expand...
Click to collapse
Use a different usb cable and port on your computer. There is a problem with the communications.
[Q&A] ★ ☆ [ROM|RADIO|FIRMWARE][4.4.3] Stock-Rooted | Sense 6 | m7wlv | 09-17-14
Q&A for ★ ☆ [ROM|RADIO|FIRMWARE][4.4.3] Stock-Rooted | Sense 6 | m7wlv | 09-17-14
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. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Making sure I'm doing this right
Hi all,
I just want to make sure I'm doing this right. I'm relatively new to rooting. Updating the firmware / radio is something I've never done before, so I'm just going to guess at the information I need to provide. Sorry if I leave anything out.
I have an m7vzw running SlimKat version 8.0. It's android 4.4.4 and the baseband version is 1.12.41.1112_2. My phone is S-OFF and I have TWRP installed. Can I just keep SlimKat installed, download the latest firmware / radio.zip in the second post, and follow the fastboot instructions there to update? Or do I need to revert to stock, then update, then return to custom?
Thanks so much for your help.
(I just realized it made a new thread for me. The post I'm referring to is here: http://forum.xda-developers.com/showthread.php?t=2485319)
Kbrotkowski said:
Hi all,
I just want to make sure I'm doing this right. I'm relatively new to rooting. Updating the firmware / radio is something I've never done before, so I'm just going to guess at the information I need to provide. Sorry if I leave anything out.
I have an m7vzw running SlimKat version 8.0. It's android 4.4.4 and the baseband version is 1.12.41.1112_2. My phone is S-OFF and I have TWRP installed. Can I just keep SlimKat installed, download the latest firmware / radio.zip in the second post, and follow the fastboot instructions there to update? Or do I need to revert to stock, then update, then return to custom?
Thanks so much for your help.
(I just realized it made a new thread for me. The post I'm referring to is here: http://forum.xda-developers.com/showthread.php?t=2485319)
Click to expand...
Click to collapse
Yes, it has been discussed in that thread. When you flash firmware only, you do not need to change roms. I would personally do a "fastboot erase cache" command before rebooting into system after firmware flash
Sent from my HTC6500LVWBLU using XDA Free mobile app
Uzephi said:
Yes, it has been discussed in that thread. When you flash firmware only, you do not need to change roms. I would personally do a "fastboot erase cache" command before rebooting into system after firmware flash
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
Awesome. I just wanted to get another opinion because I found some instructions elsewhere that said it was fine and some that said it would brick my phone, etc... Anyway, I really appreciate the help. I'll clear the cache too like you suggested.
Thanks again!
With the release of the GPE edition is a firmware update for our M7 close or do we have to wait until Verizon releases our official Lollipop update?
calash said:
With the release of the GPE edition is a firmware update for our M7 close or do we have to wait until Verizon releases our official Lollipop update?
Click to expand...
Click to collapse
We will have to wait for HTC to release the next version of sense.
I am having issues flashing the firmware. I flash the firmware as directed in the thread and flash 5.28.605.2 through Fastboot. Fastboot appears to work as the bar fills up to the last 1/10th of the progress bar. After that the instruction is to use Fastboot reboot bootloader From there I reboot the phone.
When I reboot back into the Bone Stock ROM after flashing the firmware it looks like the firmware remains as the 4.10.605.3 version in the "about" page of the phone. It does not update to 5.28.605.2
Can anyone help me?
Reboot to the bootloader / hboot screen and read the text there. OS-######.
Any way to disable one Mic? It seems one of mine is broken and it is not in warranty anymore. I'd just need for calls, elsewhere it's working. Thank you.
Hi guys,
I'm a new here and I have some questions about updating. Sorry for stupid questions. I've red many instructions and now in my mind mixed all of them. )
I could't find full instruction for updating (HTC One M7 from Verizon), step by step. Always all instructions begins from the middle, missing many things.
I have used HTC One M7 m7lvw from Verizon with Android 4.4.3
I'd like to update up Lolilop 5.02 (6.22.605.3_M7_WL_L50_SENSE60_MR_Debloated.zip) from Santod040.
But I confused about steps of updating. There are a lot different things, I'm just lost.
Steps to upgrade firmware and ROM (as I understood):
1) Nandroid. What is it? No information on first page. I guess this is saving your own info but not sure. If I don't have my own info can I skip this step?
2) Unlock bootloader with custom recovery. How? No information on first page. I guess TWRP 2.7.0.8 or newer is related to this section.
3) Wipe everything. For what? If I'm going to install new ROM why I need to wipe? And it doesn't info how to wipe.
4) Update firmware (downloaded: m7vzw_6.22.605.3_LP_Firmware_NoBoot-NoRecovery-combo.zip). The instruction is clear on page 1.
5) Update ROM (downloaded: 6.22.605.3_M7_WL_L50_SENSE60_MR_Debloated.zip). Flash the ROM and reboot. How? No info.
If I did mistakes (for sure I did) please correct me.
Thank you.
argument777 said:
Hi guys,
I'm a new here and I have some questions about updating. Sorry for stupid questions. I've red many instructions and now in my mind mixed all of them. )
I could't find full instruction for updating (HTC One M7 from Verizon), step by step. Always all instructions begins from the middle, missing many things.
I have used HTC One M7 m7lvw from Verizon with Android 4.4.3
I'd like to update up Lolilop 5.02 (6.22.605.3_M7_WL_L50_SENSE60_MR_Debloated.zip) from Santod040.
But I confused about steps of updating. There are a lot different things, I'm just lost.
Steps to upgrade firmware and ROM (as I understood):
1) Nandroid. What is it? No information on first page. I guess this is saving your own info but not sure. If I don't have my own info can I skip this step?
2) Unlock bootloader with custom recovery. How? No information on first page. I guess TWRP 2.7.0.8 or newer is related to this section.
3) Wipe everything. For what? If I'm going to install new ROM why I need to wipe? And it doesn't info how to wipe.
4) Update firmware (downloaded: m7vzw_6.22.605.3_LP_Firmware_NoBoot-NoRecovery-combo.zip). The instruction is clear on page 1.
5) Update ROM (downloaded: 6.22.605.3_M7_WL_L50_SENSE60_MR_Debloated.zip). Flash the ROM and reboot. How? No info.
If I did mistakes (for sure I did) please correct me.
Thank you.
Click to expand...
Click to collapse
Are you s-off and rooted? If not, just install HTC sync and plug your phone until your PC. If the phone is sick it will update automagically
Hi Guys,
In your opinion what is the best ROM for M7WLV? I have HTC One from Verizon with version 4.4.3 and it has never updated. Now I'm trying to figure out what version of Android to choose for updating. I don't know how will work the phone with new updates. I mean may be it will work with low speed, lags, loose stability, and etc. Could you please to share with your experience to make me right choice. Thank you.
argument777 said:
Hi Guys,
In your opinion what is the best ROM for M7WLV? I have HTC One from Verizon with version 4.4.3 and it has never updated. Now I'm trying to figure out what version of Android to choose for updating. I don't know how will work the phone with new updates. I mean may be it will work with low speed, lags, loose stability, and etc. Could you please to share with your experience to make me right choice. Thank you.
Click to expand...
Click to collapse
The FAQ thread has the answer for you. It also has other odd frequent questions asked. It having slow downs lag and instability is because of the apps you install or maybe power saver enabled? My wife's phone is stock and only had slow downs with apps that clogged her phone's memory up. I didn't know which did it and just factory reset the thing and the lag was gone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my HTC6500LVW using Tapatalk
Can't find my firmware but I do see a baseland and it's number is no where In line with any firmware versions numbers. I'm trying to see my HTC One Verizon firmware is up to date. Any help would appreciate
---------------
Admin Note: this thread has a dedicated questions and answers section which you can access here -->.
Sent from my HTC6500LVW using Tapatalk
Can't find my firmware but I do see a baseland and it's number is no where In line with any firmware versions numbers. I'm trying to see my HTC One Verizon firmware is up to date. Any help would appreciate
Okay so quick question I haven't flashed a Rom in a while, if I flash this Rom with the firmware and radio update will I be able to use other carrier bands? Cause I'm stuck on metro right now with edge and I want 4G LTE on another carrier, I've heard straight talk but some say it doessnt work I'm on a VZW Branded M7 I JUST WANT 4GLTE!!! PLEASE HELP
rickey95 said:
Okay so quick question I haven't flashed a Rom in a while, if I flash this Rom with the firmware and radio update will I be able to use other carrier bands? Cause I'm stuck on metro right now with edge and I want 4G LTE on another carrier, I've heard straight talk but some say it doessnt work I'm on a VZW Branded M7 I JUST WANT 4GLTE!!! PLEASE HELP
Click to expand...
Click to collapse
You won't get 4G or hspa on US Carriers on the Verizon Branded HTC one.
Hi,
any leak, prevision about modding for this device?
I mean, will CM, AOSPA, AOKP etc support it officially? How is the situation with the other HTC's flagships?
Can it be unlocked as M7 with HTC dev site?
Thank you guys
davide136 said:
Hi,
any leak, prevision about modding for this device?
I mean, will CM, AOSPA, AOKP etc support it officially? How is the situation with the other HTC's flagships?
Can it be unlocked as M7 with HTC dev site?
Thank you guys
Click to expand...
Click to collapse
Bit early considering we aren't even positive what the final product's hardware will entirely be Can't wait though
can't wait too that's why i have written xD i don't know what to buy, my s6 is the worst phone for modding and updates, 1 year and i still have not rooted anything! I was getting used to root the first day when i was buying new phones don't want my next phone to be like s6
davide136 said:
can't wait too that's why i have written xD i don't know what to buy, my s6 is the worst phone for modding and updates, 1 year and i still have not rooted anything! I was getting used to root the first day when i was buying new phones don't want my next phone to be like s6
Click to expand...
Click to collapse
Exactly that's what I'm afraid of, too. If I decide to buy a new phone, I'd like to compile ROMs for it by myself, too, but therefore the vendor, device and kernel tree need to be published by HTC. I've just been looking around how custom development for the HTC One M9 looks like. Although I couldn't find many ROMs, there are official Cyanogenmod versions and open device and kernel trees. Thus I could compile many ROMs for the One M9. This gives me hope regarding the HTC 10. The Galaxy S6 instead didn't have no huge moding posibilities. There's only an unofficial, unstable device and kernel tree alongside a bugy CM-version. Just like the S6 the S7 probably won't get huge development support as well. This is what gives me hope regarding the HTC 10.
The only question I'm currently asking myself is if I should buy the HTC 10 or wait for the Oneplus 3 which will be published later in Q2 2016. Compared to the OP2 and OP1 it'll be a bit more expensive but it'll also be better equiped. Furthermore the price will probably be much lower than the price of the HTC 10. What are your expectations and what have you been able to definitely find out so far?
I'm still tryng to figure out what to do...lg has dropped support for rooted or bootloader unlocked device in italy, and the g5 seems to be a bit strange te me, i mean, it's not as premium as g4..regarding oneplus devices, for the 1 and 2 i read about bad screens and something else wich i don't remember, never saw one...i'd prefer staying on a strong brand...samsung obviously is exhiliated from any decision...sony maybe but no xD never liked the screens in the past...
My old nexus 5 make me wish about a decent nexus around 5" screen, I'd really love it, especially powered from a snapdragon 820 cpu..
Mi5 is lovable, but, you know...it's xiaomi...china brand, china support, 30 days for travelling a device if something happens, and that is for 2 times...its frightening xD
Htc 10 seems to be the best choice, ut will surely be premium, even if it does not have a good camera i don't care, just bought an eos 700d xD i just hope there will be a lot of modding, that is why i asked here
Htcdev.com is still working good for all the other htc, it must have decent modding, i think I'll go for it. At least, that's what I'm thinking now...but who knows
Inviato dal mio SM-G920F utilizzando Tapatalk
Yeah, Xiaomi is a brand I've been looking at over the last two years. I recommended Xiaomi phones to friends who wanted to have good and cheap devices. They are lucky all together but the only phone by Xiaomi I'd buy is the Mi Note Pro as a phone should have 5,7 inch in my opinion. I'd also like to have an AMOLED-Display in my next device so I hope HTC will release a bigger version of the 10 as well. The LG G5 is not really what I am looking for since it's a bit strange to have several components you can choose from. I think I'll buy a OP3 when it's published as it'll probably be more developer friendly but maybe the 10 by HTC will convince me, too. I'm really excited about the upcoming devices especially because my Nexus 4 from 2012 becomes slower and slower. Very anoying. Maybe a new Nexus will be released at the Google IO this year. This would be awesome. Anyway, I hope the potent upcoming phones will come sooner than later as I don't know how long my N4 will survive.
Very informed you guys are. I like this thread cause' I think a lot like you.
Sent from my Nexus 5 using XDA-Developers mobile app
Also looking for an answer on this: I was tempted by the Galaxy S7, but the huge issues I've had running anything but TouchWiz based ROMs on my S4 (and so issues running anything Marshmallow based) have put me right off.
How easily moddable have HTC phones been in recent years?
Rohaq said:
Also looking for an answer on this: I was tempted by the Galaxy S7, but the huge issues I've had running anything but TouchWiz based ROMs on my S4 (and so issues running anything Marshmallow based) have put me right off.
How easily moddable have HTC phones been in recent years?
Click to expand...
Click to collapse
The M7, M8, M9, and A9 are all very easy to do basic modding on. Getting s-off and deep modding is a different story. On the M8, at least, you can flash custom ROMs and kernels without s-off, so basically everything most people needs
Anonaru said:
The M7, M8, M9, and A9 are all very easy to do basic modding on. Getting s-off and deep modding is a different story. On the M8, at least, you can flash custom ROMs and kernels without s-off, so basically everything most people needs
Click to expand...
Click to collapse
Well, looks like it paid to wait then, come on, release day!
Anonaru said:
The M7, M8, M9, and A9 are all very easy to do basic modding on. Getting s-off and deep modding is a different story. On the M8, at least, you can flash custom ROMs and kernels without s-off, so basically everything most people needs
Click to expand...
Click to collapse
does it mean that with m9 if you do not s-off you can't touch system, boot or recovery partition? ( i'm still leaving in the time when you did fastboot oem unlock and everything was ok )
davide136 said:
does it mean that with m9 if you do not s-off you can't touch system, boot or recovery partition? ( i'm still leaving in the time when you did fastboot oem unlock and everything was ok )
Click to expand...
Click to collapse
No, the things you can't do without S-Off are:
*flash unsigned firmware packages
*flash firmware packages that don't match CID/MID
*flash RUUs that don't match CID/MID
*change CID/MID
*restore "locked" status (without you can only get "relocked" status)
*restore "software status: official" flag in bootloader (flag sets to "software status: modified" if you flash anything)
What you can do without S-Off:
*unlock bootloader (via HTCdev)
*flash recovery
*root (via superSU package or your favorite custom ROM)
*flash ROMs
0verdaflow said:
When is this gonna be released ??
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
we will know tomorrow on the announcement but the leaks lead so far for beginning of May release
JEANRIVERA said:
we will know tomorrow on the announcement but the leaks lead so far for beginning of May release
Click to expand...
Click to collapse
Maybe there's another HTC phone to come in early may, hopefully a phablet but let's see...
Anyone know how we will get root on the unlocked version?
km8j said:
Anyone know how we will get root on the unlocked version?
Click to expand...
Click to collapse
By flashing TWRP Recovery then flashing the current SuperSU package ( or use the built-in TWRP option to flash SuperSU if available)
Behold_this said:
By flashing TWRP Recovery then flashing the current SuperSU package ( or use the built-in TWRP option to flash SuperSU if available)
Click to expand...
Click to collapse
Is this a big process? Is everything already available? Does any part of the rooting process wipe the device? If so, may make more sense to just do it right out of the box to avoid losing info
TWRP can already be found and downloaded; at least if one will look for it at the right place . I already downloaded it. SuperSU can as well be downloaded for MM devices. By this I'd guess the root procedure can be done as it always has been.
Sent from my HTC One M9 using XDA Labs
HTCNerdYoda said:
TWRP can already be found and downloaded; at least if one will look for it at the right place . I already downloaded it. SuperSU can as well be downloaded for MM devices. By this I'd guess the root procedure can be done as it always has been.
Click to expand...
Click to collapse
But does the bootloader unlock wrote y the phone?
km8j said:
But does the bootloader unlock wrote y the phone?
Click to expand...
Click to collapse
If you meant wipe the phone, then yes, it does.
Need to rollback, or be advised of any custom ROMS that work..
Try Elite ROM from ROM section. it should work fine.
I personally would not recommend installing Elite ROM as it is more hassle than it is worth when you try to switch ROMs. It re/debrands your device and even after restoring a nandroid your audio will not work nor will your camera function properly. What files have bad keys? I put a lot of those up and the keys should work fine....
@shashank1320 check the links in the BLN-L24 section....something got messed up when you copied my links as mine work.
@ghostair is your device bricked? IMO none of the ROMs for this phone are worth installing on a main phone because there is too much functionality lost, no disrespect to the devs. Elite ROM does have the least amount of bugs but it is a hassle as I mentioned earlier. My main gripe about it is when installing and uninstalling apps you must restart the device in order for the apps to be added or removed from the app drawer....its a major annoyance.
BLN-L24C567B110 Thanks to @Dazed No More
boot - https://mega.nz/#!ceRkHQoA!L8MECn8Ul...8JwO7ZuVEEr8mk
recovery - https://mega.nz/#!sOZAUJTZ!QKKROoWkI...UPNDwL79ZI1yQI
BLN-L24C567B360 Thanks to @Dazed No More
boot - https://mega.nz/#!hDQB3RCT!YTH2j1IhJ...y_prJHEgHdSrxg
recovery - https://mega.nz/#!Fa4DBbxS!XDIczpXcr...TApUtNvcOMEDnc
TWRP 3.1.1 didn't work for me, nor did EliteROM or his version of TWRP.
ghostair said:
TWRP 3.1.1 didn't work for me, nor did EliteROM or his version of TWRP.
Click to expand...
Click to collapse
Is your device bricked? You say you want to rollback, but have you started the process....what firmware are you on?
Dazed No More said:
....
@shashank1320 check the links in the BLN-L24 section....something got messed up when you copied my links as mine work.
.
Click to expand...
Click to collapse
Let me check mate. Thanks for pointing that out.
No it's not bricked, actually I am on TWRP 3.1.1-0, it was only EliteROM's version that didn't work. I haven't even been able to use the phone at all, for a week, and am currently on LineageOS 13 as it was only release that works for my model it seems.
ghostair said:
No it's not bricked, actually I am on TWRP 3.1.1-0, it was only EliteROM's version that didn't work. I haven't even been able to use the phone at all, for a week, and am currently on LineageOS 13 as it was only release that works for my model it seems.
Click to expand...
Click to collapse
Im confused....your original post says you need to rollback but you say you are currently on LOS 13?? Rolling back refers to downgrading from Android 7.0 (Nougat) to 6.0.1 (MM) but you are already on MM if you are running LOS 13. You also say your device is not bricked but then in the next sentence say you havent been able to use it at all for a week.....and lastly you say LOS 13 was the only release to work for your model yet every single ROM in the development forum can be flashed to the BLN-L24, I know because I have done it.
What exactly are you trying to accomplish here? Your posts are contradictory and make no sense. Id be glad to help but you gotta give me something to work with here.
Im assuming you did not make a full backup in TWRP before flashing any ROMs, in which case you have learned a valuable lesson....always have a backup. But since you dont we will get you back to EMUI which I assume is what you mean when you say roll back.
Dazed No More said:
Im confused....your original post says you need to rollback but you say you are currently on LOS 13?? Rolling back refers to downgrading from Android 7.0 (Nougat) to 6.0.1 (MM) but you are already on MM if you are running LOS 13. You also say your device is not bricked but then in the next sentence say you havent been able to use it at all for a week.....and lastly you say LOS 13 was the only release to work for your model yet every single ROM in the development forum can be flashed to the BLN-L24, I know because I have done it.
What exactly are you trying to accomplish here? Your posts are contradictory and make no sense. Id be glad to help but you gotta give me something to work with here.
Click to expand...
Click to collapse
I understand, I probably should have just used, "go back," to EMUI. Since LOS 13 isn't usable in the least, as I can't make calls, and it drops LTE.
If they work then how? I followed everything, flashing vendor.img with fastboot, then flashing the respective zip?
I'd rather not go back to EMUI, it's why I haven't been able to actually "use it as a phone," since purchase.
Why would you not want to go back to EMUI? Its smooth and everything works. EMUI is the reason you havent been able to use it as a phone?? There is not one single ROM for this device that works entirely and has full functionality. You're always going to be missing something whether its the camera, LTE, calls, etc.
You're going to have to go back to EMUI so you can update to Anrdoid 7.0 (be sure to make a full backup) and then flash away all the ROMS you like and you will see they are all broken in some way. This is most definitely not the phone to use if you are looking for polished ROMs.
My last tip before departing......download the flashable vendor zip if you still want to mess around with the ROMs, it makes life much easier. Its in one of the threads in that forum I think AOKP