yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 4 Q&A, Help & Troubleshooting] vbaschen:
Got it working on 910F

Hi everyone,

the method below is working only for Nameless v.1 and v.2, it DON'T works for v.3 for now untill samsung releases the new base for our F-Models. Also then, we will see if it'll be compatible with v.3 or higher.

So for now F-Users should stay on v.2 (that is also awesome :)) until Er. Aditya update OP with information that some solution for F-Devices is found.

Also I found out, that BOE2 Bootloader isn't the only possible bootloader for Nameless Rom. BOD2 botloader is also compatible. So if you have already flashed via odin one of these bootloaders you should only flash SimplKernel 3.2F. Otherwise, or if you don't know what bootloader you have right now, you can flash with odin whether BOE2 bootloader (BL in odin) or BOD2 bootloader from Dr. Ketan (PDA/AP, since odin will flash bootloader and modem together).

-------------------------------

Initial post (Method):

Hi everyone,

got Nameless v.1 working on 910F Variant. Any problems so far.

What I did:

1. Flashed via odin (BL-Tab) BOE2 Bootloader for 910F here at BobCatRom Thread

Update: Alternatively you can flash with odin (PDA/AP Tab) BOD2 Bootloader and Modem for 910F from Dr. Ketan (initial post here)

P.S.: I flashed via Odin also BOC4 modem from there, but don't know is it really necessary for getting Nameless working on F variant or not.

Update: Not necessary.

2. Clean Install Nameless ROM. I did a full wipe.

(Also here I don't know whether it is necessary to do full wipe or not. I'm just describing how it worked for me)

3. Flash SimpleKernel 3.2F here. Follow download link from there.

Update: SimpleKernel is MUST to boot up. No other kernel I've tried is compatible (for now).

4. Reboot. Done.

___

Thanks and Credits to:

Er. Aditya for his great heavily debloated and quick ROM.

Psycho_666 for Kernel and his post about BOE Bootloader relevance according to aukhan. Thanks to aukhan too for finding it out :)

BoBCatRoM for standalone BOE Bootloader (and Modem) Odin tar(s). Couldn't find it as standalone tar elsewhere, but here at BoBCatRoM Thread.

Dr. Ketan for BOD2 Bootloader and Modem
[Galaxy Note 4 Q&A, Help & Troubleshooting] Er. Aditya:
il surely provide a zip for you bro , my internet broke last night and cannot upload anything till i reach office

just hold on a bit and il send you the zip :)

thanks for posting the info for users mate il update the thread as well credit goes obviously to you buddy :)
[Galaxy Note 4 Q&A, Help & Troubleshooting] lid313:
Screen Write crashes

Sorry for this. But Screen Write keeps on crashing. When you already edit your screenshot via ScreenWrite and want to save it, a pop up says Screen Write has stopped. The image is saved, but not edited. So its like we just take a normal screenshot. :(
[Galaxy Note 4 Q&A, Help & Troubleshooting] reyocio:
Well works for me..
[Galaxy Note 4 Q&A, Help & Troubleshooting] formula666:
In call

Excuse me Dev I downloaded v3 of this rom on my Canadian n910w8 everything works fine the only problem is that I can't hear anything when I make a call or hear incoming call. Can I get some help with this fix pleasee. ... thank u sir
[Galaxy Note 4 Q&A, Help & Troubleshooting] xaxomis:
will this rom work good to n910f and bootloaders?
[Galaxy Note 4 Q&A, Help & Troubleshooting] vbaschen:
Nameless v.3 isn't compatible with N910F variant with any bootloader (for now).

But you can flash previous version by following my instruction. I'm also on v.2 and don't experience any problem.
[Galaxy Note 4 Q&A, Help & Troubleshooting] ekam330:
viper mod

Brother...is there any way to install vipermod on this Rom?

Kernal is enforcing

Or Any custom kernel which will work on n910g with this rom?
[Galaxy Note 4 Q&A, Help & Troubleshooting] vbaschen:
Hi, do you mean Viper4android Mod? If so you can. Just flash zip attached. Than start the app and click install driver from menu.

With this rom you can flash SimplKernel. Check SimplRom Thread and don't forget to thank dev :)

View attachment 3360618
[Galaxy Note 4 Q&A, Help & Troubleshooting] Rommelly:
Bug Found VPN setup

System UI crashing
[Galaxy Note 4 Q&A, Help & Troubleshooting] vbaschen:
Did you flashed some theme before?
[Galaxy Note 4 Q&A, Help & Troubleshooting] Rommelly:
No i didnt. I just clean flashed your rom and setup my VPN with Private Internet Access and system UI crashing.. man i want your rom. fastest rom ever. but i will keep my current rom at the moment unitl you find a fix.
[Galaxy Note 4 Q&A, Help & Troubleshooting] vbaschen:
Thank you mate for such good words about rom. [MENTION=5750672]Er. Aditya[/MENTION] is a great dev and made great job for us.

And thank you for reporting here. We will take a look on this and will inform you when we will fix it.
[Galaxy Note 4 Q&A, Help & Troubleshooting] Er. Aditya:
thankyou mate for your kind words , if i give a flashable zip will you be able to test that ?

try this and please report

http://www16.zippyshare.com/v/Oh8d72h3/file.html

if this dsnt works try this

http://www55.zippyshare.com/v/1dDBHuig/file.html and please let me know if it worked

thanks a ton mate :)
[Galaxy Note 4 Q&A, Help & Troubleshooting] aks_pk:
Bootloader Link Broken

Can someone please give the latest bootloader link necessary to flash v3?
[Galaxy Note 4 Q&A, Help & Troubleshooting] Er. Aditya:
here you go bro

https://www.androidfilehost.com/?fid=24052804347759010
[Galaxy Note 4 Q&A, Help & Troubleshooting] aks_pk:
Thanks :)

Btw, I have philz touch 6.59 installed. Can I flash this via it?

Sorry for the noob question. I am new to these things
[Galaxy Note 4 Q&A, Help & Troubleshooting] vbaschen:
I didn't try Philz but it will work as they (custom recovery) do actually same job :)
[PAC Feature Development] ARAVIND_PAVAN:
Hi everybody I'm USING PAC LP in Android one device and I'm requesting you to add dsb and halo or hover any of them and floating mode to Pac LP IF it's possible

SENT FROM MY PIECE OF GLOWING GLASS MADE BY MICROMAX

HIT THANKS IF I HELPED OR REPLIED TO YOU ;)
[PAC Feature Development] Cross0x0:
+1
[XDA Assist] izenblaze:
Hi

I have an Asus Fonepad 8 (K016 or FE380CG. 2GB RAM, 16GB ROM), I know it's not popular around here.. But any help is very welcome.

My initial device's state

- Stock rom 4.2.2

- Root (installed: Greenify, App Ops, Coolify, System App Remover (Jumobile))

- I uninstalled about 20 system apps

then I received OTA update to Lollipop and it displayed the infamous android "error" with the red exlamation mark. so i uninstalled every root app, EXCEPT System App Remover (silly me i forgot the most crucial part), probably meaning that

some system apps are still gone

. I also did full unroot inside SuperSU.

I tried factory resetting in order to successfully update to Lollipop, but once I get to the setup Welcome screen, these dreaded messages show up. ENDLESSLY

One time, the endless torture stopped and I was able to access Settings. I opened Applications and there was very (infact, too) few apps installed. Less than 200MB of RAM is used. I thought the factory settings failed, so I tried doing the same thing again in fastboot mode. But still a no-go.

Then I tried

fastboot -w

and it did say "success" but it couldn't format. "File system not supported". I forgot the exact message but that, i think is the point.

In Droidboot Provision OS, there is an option called "SD download". I put the official ROM for my device (.zip) in my SD card, then tried doing exactly that. Still no-go. Below is the entire (not exact) process

I then tried to erase cache and userdata, and ran

fastboot update fw.zip

This appears

Desperate enough, I tried to again erase cache and userdata

and system

(probably my worst decision). and the device is now stuck in boot logo screen.

I booted my device back to fastboot, and

my serial number was shown as "unknown"

. The same appeared when i type below code in cmd in my PC.

fastboot devices

One thing to be noted. I am really confused with ASUS's official firmware.

There is no recovery.img, system.img, userdata.img or cache.img

Here is a list of files and directories inside of it:

I do not have nandroid or any kind of backup.

I have googled and tried everything I could find for the past 9 hours. So, i think it's high time I ask experts about this.

I am thinking of taking it to the service center. But any more knowledge regarding this beforehand is very valuable to me.

I know this is too long but I've highlighted the most important parts.

Any kind of help is welcome.
[XDA Assist] jd1639:
Hi, thank you for using XDA Assist. Unfortunately there is not a dedicated forum and there is very little information about your device on XDA. There is nothing on how to flash the stock firmware. But it sounds like that's what you need to do right now. Looking at ASUS's web site it looks like there should be another zip file. ifwi.zip, in the one you extracted. That's most likely where the image files you are missing reside.
[XDA Assist] izenblaze:
Hi. Thank you so much for replying and taking the time to read my long "story".

Sadly, yes. There is little to no community for my device.

Regarding ifwi.zip, below is part of the content of the file.

I doubt that it's the system image. The file size is just way too small.

The folder with the largest size is System, and inside there are a lot of folders (app (system apps and asus's bloatwares are inside), bin, etc, fonts, framework, etc, and build.prop). It almost looks like ASUS doesn't package system into a .img file, rather in a folder. That's why I am also looking for a script file that "copies" this folder into the device, if it exists.

I am now downloading the latest (was just uploaded by ASUS) firmware, which is Lollipop.

I'll dig in the file and see if I can find anything interesting.
[XDA Assist] izenblaze:
Ok, download's finished.

Below is the root directory of the new firmware.zip

ifwi.zip has the same contents, only a newer version.

I tried fastboot update fw.zip and the same error pops up

I have attached a screenshot of updater-script I found inside META-INF/com/google/android. and screenshots of the directories of the firmware zip's contents. Hoping any is helpful to solve this.
[XDA Assist] jd1639:
First, I know nothing specific about your device. But do you have a custom recovery on your device? CWM or TWRP. The updater-script looks like it should be flashed in a custom recovery, not with fastboot. Edit, also, what's in the system folder, etc. Are there image files in there?
[XDA Assist] izenblaze:
Sorry for the late reply.

I just got the device back from the service center.

I inquired about where I can get the firmware file, and the guy said ASUS's website, but to flash it I need a tool.

It seems that this tool then copies the entire system folder to the device.

Anyways, the problem is solved now. Thank you very much for your help.
[X 2014 Q&A, Help & Troubleshooting] richar524:
Sorry if it is already available, I tried searching in vain.

Is there any thread which gives me stock pre rooted ROM for Moto X 2014 - 5.0 and 5.1 updates.

If it is not available, can anyone who can do it create flashable zips?

It will be really convenient for all of us.

:fingers-crossed:
[X 2014 Q&A, Help & Troubleshooting] Bl4ckX:
Why would you want a flashable, rooted system zip when you can flash the SuperSu zip file to root your phone yourself? It's the same amount of work and even easier.
[X 2014 Q&A, Help & Troubleshooting] richar524:
Because, if in case Moto X get some future updates, I need to return to stock and then get the OTP. If someone can maintain the Rooted stock so that we can flash over it'll save the in between work right? (If I am not wrong in the first place):rolleyes:
[X 2014 Q&A, Help & Troubleshooting] AGISCI:
It's the same ammount of work because you can't take updates on a rooted system. You have to flash a stock image without root to update. So what you are asking for is useless.

Sent from my XT1095
[X 2014 Q&A, Help & Troubleshooting] richar524:
Ok. Thanks for the info:good:
[MeMO Pad 7 Q&A, Help & Troubleshooting] waces:
Hello,

A fellow colleauge of mine had a MemoPad 7 (176CX) which received an OTA update last week. After the installation the tablet restarted and then a dead droid appeared on the screen with an error message "no command found" then the device restarts automatically and everything starts again (dead droid - no command - reboot - dead droid...). So, it's in a boot loop. (As far as I know the device was rooted and he made a mistake to no un-root before the OTA update but it's irrelevant now)

As he asked for help I checked the XDA forums and found that my idea about reinstalling the factory default firmware should solve the problem. But I'm a little bit afraid of the continous boot loop. How will be able to reflash the firmware when the device keeps rebooting?

Any advice will be helpful.

Thanks in advance.
[MeMO Pad 7 Q&A, Help & Troubleshooting] Lightn1ng:
I know what to do, don't worry. Get into recovery (it's annoying to get into recovery, you need to spam all buttons randomly while the no command screen is up), reboot to bootloader, and boot into a Temporary CWM using a PC.

Reply with questions.

---------- Post added at 01:19 PM ---------- Previous post was at 01:19 PM ----------

I know what to do, don't worry. Get into recovery (it's annoying to get into recovery, you need to spam all buttons randomly while the no command screen is up), reboot to bootloader, and boot into a Temporary CWM using a PC.

Reply with questions.

---------- Post added at 01:22 PM ---------- Previous post was at 01:19 PM ----------

Sorry for the double post.

---------- Post added at 01:22 PM ---------- Previous post was at 01:22 PM ----------

Sorry for the double post.
[MeMO Pad 7 Q&A, Help & Troubleshooting] waces:
Hello,

Thanks for the reply. Unfortunatelly the issue seems to be a little bit more complicated.

So, things I checked:

- boot into droidboot with Vol+ + Power - works well, able to boot into droidboot. But see this strange notice in the bottom:

FASTBOOT INIT....

e:Failed to mount device '/dev/block/sda1' as installer partition using fs_type

ition using fs_type 'vfat'

continue fastboot process

E:installer device ignored

FASTBOOT CMD WAITING...

E:installer device ignored

E:No valid installer medium found

Could not open /sys/devices/virtual/backlight

Now, I can select Reboot Droidboot - no luck

Reboot - no luck

Recovery - reboot into bootloop

Power off - yeah, it works and turns of the device.

If I try to boot into Fastboot with Vol - + Powoer receive the dead droid with the No command message.

Any idea where can I go forward?
[MeMO Pad 7 Q&A, Help & Troubleshooting] jakeco2u:
X2 With the OTA missing partition. Seemed like a straight forward update but completely screwed up my tablet. SOL for the moment. I imagine this post will become popular very quick.
[MeMO Pad 7 Q&A, Help & Troubleshooting] Lightn1ng:
Try the following:

Boot into DROIDBOOT

Download & Install Android Studio

Go into a cmd and type "fastboot devices"

If it shows a device, than:

Use a temp CWM session to flash 182.
[MeMO Pad 7 Q&A, Help & Troubleshooting] waces:
Hello,

Nope, in Droidboot the PC cannot see and connect any device.

fastboot devices - return with empty line

fastboot getvar - return with <waiting for device>
[MeMO Pad 7 Q&A, Help & Troubleshooting] waces:
minor correcftion. was able to access the device with fastboot devices and it shows the connected device as well. i followed the steps described here : http://xdaforums.com/android/help/instructions-reviving-me170c-me170cx-t3017466 but no luck. what did i missed?
[MeMO Pad 7 Q&A, Help & Troubleshooting] Lightn1ng:
Fastboot? AWESOME! You're covered, Jimmy. (If you didn't have access to fastboot, you would be six callers ahead of us...)

Download this temp CWM:

https://www.androidfilehost.com/?fid=23991606952604606

open the batch file (with droidboot open on the tablet, and tethered to the pc), and type "ACCEPT". Now, type "T4", and click enter, and a temporary CWM session should open.

Now, (you'll need a external SD card), flash this file:

http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ME176C-WW-3_2_23_182.zip

And you should be on KitKat... and take OTAs from there to get to lollipop. Use the same temp CWM and flash SuperSU to get root.
[MeMO Pad 7 Q&A, Help & Troubleshooting] Lightn1ng:
---------- Post added at 01:50 PM ---------- Previous post was at 01:17 PM ----------

Just wondering... did you end up fixing the device? You don't seem to be very active on this fourm.
[MeMO Pad 7 Q&A, Help & Troubleshooting] jakeco2u:
Wondering if you could help me for a sec... I followed what you have here and all works fine but the sd card won't mount, I've formatted with both file systems but no. I'm very new but learning, what did I miss?
[MeMO Pad 7 Q&A, Help & Troubleshooting] Lightn1ng:
Tell me the exact steps you took.

Did you take the OTAs to Lollipop?
[MeMO Pad 7 Q&A, Help & Troubleshooting] jakeco2u:
Yes, was rooted, OTA to Lollipop and tablet stuck in bootloop. I followed your post and was not able to install your link but had success with WW_V12.10.1.17. The tablet stated it had been installed so I went back and reboot but its still stuck in the bootloop. Hope that makes sense.

Like I said, I'm new to working on these so be nice. Should I install firmware and source code from the Asus website?
[MeMO Pad 7 Q&A, Help & Troubleshooting] Lightn1ng:
Did you factory reset after installing the WW_V12.10.1.17 ROM?
[MeMO Pad 7 Q&A, Help & Troubleshooting] jakeco2u:
I did, back to bootloop.
[MeMO Pad 7 Q&A, Help & Troubleshooting] Lightn1ng:
Did the Lollipop OTA finish? (As in, did you see all the BIOS updating text?)
[MeMO Pad 7 Q&A, Help & Troubleshooting] jakeco2u:
I'm not sure if the bios updated (I assume we are talking about the first OTA round before the problem). It had finished the download, the droid was shown for a bit, and when I came back after about 1/2 hr. to check on it the 'Asus powered by Android' screen kept cycling about every minute. I didn't see bios updating text. BTW thank for the help...

And as the OP stated in fastboot i get:

E:installer device ignored

continue the fastboot process

E:failed to mount device '/dev/block/sda1' as installer partition using fs_type

ition using fs_type 'vfat'

FASTBOOT CMD WAITING...

E:installer device ignored

E:No valid installer medium found

Could not open /sys/devices/virtual/backlight
[MeMO Pad 7 Q&A, Help & Troubleshooting] Lightn1ng:
Try downloading each ROM from the OP, and flashing them in order.
[MeMO Pad 7 Q&A, Help & Troubleshooting] jakeco2u:
Sorry, which ROMs? Are we talking about the firmware and kernels from the Asus website? I'm not seeing any ROMs in this post except the one you posted and the Asus one. And again, thanks for taking the time...
[MeMO Pad 7 Q&A, Help & Troubleshooting] Lightn1ng:
Sorry, didn't make what to download clear enough.

ME176C/X K013 ROMS AND UPDATES:

WW .182 ROM

http://dlcdnet.asus.com/pub/ASUS/Eee...3_2_23_182.zip

WW OTA 191

http://fota.asus.com/delta_package/e...104/update.zip

https://drive.google.com/file/d/0B5G...ew?usp=sharing

http://www26.zippyshare.com/v/49210353/file.html

WW OTA 198

http://www21.zippyshare.com/v/f1NwNFH5/file.html

WW OTA 199

http://www.mediafire.com/download/ec...c8j/update.zip

WW OTA 201

http://www48.zippyshare.com/v/PtRl8YI9/file.html

WW Lollipop release

http://www.mediafire.com/download/2v...1/lollipop.zip

download each one of those (sorry, lots of downloads lol) and flash them each in order using a temp CWM. then do a factory reset and reboot.

EDIT: some links are down. I'm assuming you already have the 182 ROM.

Flash the 182 ROM, and then flash all the updates you can download in order.
[MeMO Pad 7 Q&A, Help & Troubleshooting] jakeco2u:
OK, I tried to download these links most are dead and the three that did download came up as errors when attempting to flash them.

I'm going to try and explain the best I can with pictures as I can only assume I'm doing something wrong.

This is what I get when I go into fastboot, or droidboot or whatever.

OK, I install update from Asus website(as its the only file that hasn't caused an error.

After the install...

Wipe data...

Reboot... I don't know why it asks for root on reboot???

Then starts bootloop...

Any thoughts? Or should I just toss it.. It seems there has to be a way but it's beyond my skill set. Thanks again for the help.
[XDA Assist] Ra1908:
Hi Everyone, I forgot my lock for moto G 2nd gen mobile running with Lollypop 5.02. I dont want to hard reset the mobile and loose the data. Is there any way i can remove the lock code. Please assist me:(

Model : Moto G (2nd GEN)

OS : Android Lollypop 5.02 ver.
[XDA Assist] jd1639:
Hi, thank you for using XDA Assist. The only way to remove the password is to flash the stock firmware. And, yes, you will lose data. That's what the password is there for.
[XDA Assist] Ra1908:
Hi..thanq for the reply..is there any way i can extract the data before resetting it. I can access the guest user account, can it help in any way to get the photos?
[XDA Assist] jd1639:
Again, that's what passwords are for. They're there so someone who doesn't have the password can't access the data. So the answer is no.
[One (M7) Q&A, Help & Troubleshooting] luigi311:
I was wondering if anyone has miracast working? I'm trying to use it with a roku but can't screen mirror to it via miracast and usually causes me to disconnect briefly from the WiFi. Seems to happen to me with all roms besides CM based roms but the front camera issues kills it for me. I was wondering if this is specific to Sprint roms since I own a Sprint HTC one m7 or is this with all m7
[Transformer TF300T Q&A, Help & Troubleshooting] citronax:
Hi,

I am trying to restore my TF300T to stock ROM and when accessing fastboot I get the <device not found message>

I have ADB/FASTBOOT installed on my laptop (running Win7 64bit)

My tablet details are below:

Device = Unlocked

Key driver not found..Booting OS

Android cardhu-user bootloader <1.00e> released by "TW_epad-10.6.1.15.3-20130416" A03

Starting Fastboot USB download protocol

I have the RCK / Android and Wipe Data icons but no USB icon (I believe this is correct as I am automatically in fastboot mode, based upon the information above)

I have read a lot of posts but an unable to resolve this matter. Any help is greatly appreciated.

Thanks in advance.
[Transformer TF300T Q&A, Help & Troubleshooting] UncleManuel:
Hi!

That is correct. The "starting fastboot USB download protocol" tells you that you are in fastboot mode. Now comes the tricky part: Finding a fastboot package that works with your computer and your Transformer. F.e. I have three different ADB/Fastboot installations and only one works. I've installed this one here: http://xdaforums.com/showthread.php?t=2588979

Note: The programm installs itself into C:\adb\ so you have to copy your recovery there...

You have to check first if your Transformer is connected. If "fastboot devices" is retuning a serial number than it's all fine... :good:
[Galaxy S 4 Q&A, Help & Troubleshooting] Imtigerclaw:
Hi, I accidently rooted and installed cwm on my galaxy s4 gt i9-505, without disabling knox, and now I want to go back to the orginal samsung bootloader, (I don't not want to know how to get the stock firmware), I want to unroot and restore the bootloader, really need help asap, would be apperiated thanks.
[Galaxy S 4 Q&A, Help & Troubleshooting] Imtigerclaw:
Update: I'm on Android L 5.0.1, and installed cwm before rooting which was a silly mistake, because knox then countered that, and it's conflicting root problems when I tryed to root afterwards, but now I just want to go back to the Samsung bootloader, root issue fix but still don't know how to fix bootloader.
[Galaxy S 4 Q&A, Help & Troubleshooting] th3cr0w:
Not sure what is there to fix - if phone boots correctly it is good.

If you try to revert back to knox 0x0 I'm afraid it is not possible.
[Galaxy S 4 Q&A, Help & Troubleshooting] DSA:
Flashing root and cwm doesn't replace your bootloader

How do you

accidentally

flash root and a customised recovery?