yashsingh1/xdaforums huggingface dataset:
[Asus Transformer TF700] Wadesauce:
Here I am

Hey guys, this is Wade, the cause of the whole fiasco.

It was the newest TWRP 2.3.6.2, but I imagine it might've been a problem with the bootloader? I had no idea that the bootloader needed updating; I thought that once you could boot what you wanted, that was it, but obviously I'm mistaken. Where do I find the bootloader version? It was the latest posting to the Asus download site, or the V8, 2013 bootloader edition for JB. 4.2

Basically, I had tried several times that day installing CM11 and the gapps with CWM 6.0.3.1 (which ROM manager says is the up to date version? WTF?) to no avail. It kept giving me md5sum errors, and I couldn't find anything to easily fix that. CWM would also not respond to commands from ROM manager other than backups... If i told it to bootload and flash, it would just reboot normally... ADB also would fail, despite saying that i COULD connect to fastboot.

So i read on the actual CM forum that the newest TWRP 2.6.3.2 would do the trick as well, and tried that. But ya, once i booted into twrp, it threw a password query at me. I never set a password, so I pressed cancel, and that's when the partition showed up as blank.

I went to reboot, but it warned that I had no OS installed. That's about when I freaked out. It would see my microSD fine, but wasn't able to talk to /system to actually flash anything, and ADB would just give "error:closed" if I tried any mount commands there.

So ya, I invited my buddy over, and he recommended we try flashing an old CROMI-X, and it WORKED! sort of. It started to flash, even though a previous CM 10.2 and it's gapps (which I was already running and knew worked) wouldn't!

Then it froze installing Youtube, and after ten mins we held down the power.

And it booted back into CM 10.2 like nothing had happened.

Even though TWRP said I had succesfully factory reset AND wiped AND formatted the internal by that point. Lies!

So ya, I imagine it's a combination of pilot error, and TWRP being a little fluky. My question - where did that 87% CROMI-X flash go, and how can I get rid of it? And i reflashed CWM 6.0.3.1, but I'm still wary of going into the bootloader, just in case bastard TWRP is still lurkin
[Asus Transformer TF700] Wadesauce:
UPDATE

So it was definitely the old ASUS 4.2 bootloader I was using. I had no idea that dasunsrule32 wanted us to use his April 2013 bootloader for 10.2 as well, the site that told me how to put CM 10.2 on my tab said to use the old ASUS one.

Finally manned up and tried my first soft reboot, and it brought up the ASUS menu with the blue loading bar - it seemed like it wanted to go into bootloader. Then it went blank and the regular ASUS logo showed, and then the CM logo and booted. So i didn't walk away from this unscathed; something low-down got messed with...

Can I update the bootloader to his, despite the problems ive been having? How do I do that?

And why does ROM manager only offer 6.0.3.1??

And since CM11 is based on 4.4, wont it eventually be better than CROMi-X?
[Asus Transformer TF700] lj50036:
Can you still boot into fastboot mode on your tablet and can your PC see the tablet in fastboot mode?? What is the OS on your PC??
[Asus Transformer TF700] Wadesauce:
i dunno

I haven't tried booting into bootloader, or even a full power down/power up yet. This is the device I use for school and right now would be a pretty sh**y time for anything serious to happen to it.

I am mainly afraid that TWRP hasn't left yet, or that I won't be able to access the CWM that ROM manager says I just successfully reflashed.

I don't really want to plug it back into the computer until I know more about what happened to it. Is it likely that the CROMI that we tried flashing or the old TWRP will cause me problems? Remember that CROMI said it was 87% successful (had loaded kernel and system and all that jazz)

And I have 64 bit Win7, it should have appropriate drivers
[Asus Transformer TF700] lj50036:
Feedback

Well you just let me know.. I will be here to help out if you would like it ....As always thx lj
[Asus Transformer TF700] berndblb:
Jeez - where to start?

First of all: Do yourself a favor and ditch ROM Manager. It does not work well with the TF700 and several people have hard bricked using it. You have been very lucky so far!

Second: Do not flash anything until you are 150% sure you know what you are doing, you understand the requirements for your situation and have everything you need at hand.

Do not flash anything EVER if you do not know what bootloader version you have. That's like getting into your car blind folded and trusting that your GPS will drive you safely to your destination.

Every ROM has it's requirements in terms of bootloader version and recovery and they are usually clearly stated in the first couple of paragraphs in the OP of the rom thread. If not: Stay away from that rom unless you know exactly what you are doing!

TWRP 2.6.3.2 has major issues when formatting data from it. Stay away from it for now.

To find out what you can do to get a stable system back, you need to know where you are and what you have.

Boot into the bootloader (and do not use ROM Manager to do it!) and read the tiny script. It'll probably be 10.6.1.14.10 or .8

Post the result.

Boot into the recovery to check what you have installed. Versions matter!

The proper way of installing a custom recovery is in fastboot mode. Which is different from ADB, btw - you've been mixing those up I think.

Google "adb fastboot tutorial" and do some reading. Once you understand, get it set up on your PC, boot the tablet into the bootloader, connect both via original USB cable and test the connection with

fastboot devices

If it returns the serial number of your tablet, you are in business and we can continue from there.

Happy studying!
[Asus Transformer TF700] Wadesauce:
Getting there...

Alright, I have done some reading as far as all of this goes. I understand a lot of it better now.

So I'm positive now that it was because I hadn't updated my bootloader before trying through CWM. And TWRP obviously was no more useful.

I haven't quite checked what the bootloader version is - I think there may be something wrong with it still (given my weird boot-up) and I don't want to go there until I'm totally sure what I'm doing. I'd hate to hit bootloader and then realize something was seriously wrong, and my time was ticking.

However, I have never changed the bootloader since I used ASUS's one from their website originally - since it says v8, I imagine thats the .8 one?

Before I uninstalled ROM manager, I checked what it said my recovery was - and it said I had CWM 6.0.3.1 still, even though the TWRP fiasco has just gone down. I used ROM to reflash the same 6.0.3.1 from the device, and it said it was successful.

So before I begin, could i possibly ask a few questions?

1) Could I have corrupted the bootloader?

2) Can more than one recovery exist? Is it maybe true that CWM 6.0.3.1 would be the one I will boot into if I went into recovery? I REALLY don't want it to be TWRP again as it might not survive the experience (I had put TWRP on via fastboot). Should I just get to bootloader, flash a new recovery right away and go from there?

3) When I go to finally solve it, what are the hypothetical steps I should take? Right now, as far as I can tell, it will be:

a) Make sure all drivers are working, and files (including backup) are on my PC.

b) reboot into bootloader, check version.

c) flash the 10.6.1.14.4 bootloader

d) reboot

e) reboot into bootloader

f) flash CWM. 6.0.4.6

g) reboot

i) reboot into bootloader, into recovery, then flash CM 11 and gapps

j) reboot

Ya? No? Any help would be appreciated :)
[Asus Transformer TF700] LetMeKnow:
1. No, your bootloader is still good because you still can boot into your system. You need your bootloader to initiate your hardware before your OS is booting.. I am very sure that is the case but it would be nice for someone to confirm it...:)

2. Your recovery partition is too small for two custom recoveries to exist. So it is almost impossible for you to have two recoveries..

Before you want to go further, it is easier to find out your bootloader and recovery versions so you know what is the next step that you need to do. Otherwise, it is just a guess or a shot in the dark... I think that you are fine but you need to wait for some experts to confirm it... Good luck...:fingers-crossed:
[Asus Transformer TF700] Wadesauce:
Please bear with me

Sorry hahah, I know I must seem really frustrating...

I have held off for 2 reasons:

1. The first time I did a soft reboot after my fiasco, upon boot it went through the first series of steps trying to load into the bootloader, but then booted fine. Another time a few days after, it rebooted while i was using it, and just went blank after the asus logo. Holding the power down caused it to boot fine. Still, neither of those had ever happened before, and I am pretty sure that some point along the line of bootloader-->OS something is broken. Hopefully on the OS side.

2. I am not going to attempt to boot into recovery until I know that it isn't the same TWRP 2.6.3.2 that got me into this whole fiasco. I know it sounds like a catch 22, not wanting to reboot into recovery to check what it is, but I have NO IDEA how to get out of this TWRP as it stands. I had to flash a CROMI (which failed at 87%) and hard reboot. Not willing to go out on a limb and assume that hard-reboot will work during any step of that process.

So, why do I have to check it? Can't I boot into bootloader, flash a new bootloader, flash a new recovery, and then reboot normally? Assuming I'll be able to establish fastboot (drivers still work, so fingers crossed on that one).
[Asus Transformer TF700] LetMeKnow:
It is good to understand totally before flashing anything....:good: I just tried to answer your questions about the bootloader and recovery....:) I did not follow the whole story but I did scan through your posts. I believed that there is nothing wrong with your bootloader. If it was screwed, then you can not boot into your system.. I think that your bootloader is still good so you don't have to worry about it..

The reason people asked for your bootloader and recovery version is if you have the current and working bootloader and recovery, you don't have to flash all over again to reduce something is going wrong and hardbrick your device...:)

I think that it is best to let berndblb and lj50036 to continue to give you advises because they are following your issues more closely... Good luck..:fingers-crossed:

By any chance, do you have NVFlash blob?
[Asus Transformer TF700] Wadesauce:
about le bootloader

Thanks for your help!

I think I might be ok to be honest. I definitely don't have the newest bootloader or recovery. I'm positive I have the v8 ASUS stock bootloader, unless something about installing CM 10.2 gave me a new one (which as far as I understand, it shouldn't). So that will probably be the bootloader.

The recovery is either TWRP 2.3.6.2 (which I had last pushed via fastboot, before fiasco, and refuse to boot into), or CWM 6.0.3.1 (which I just recently reflashed from the device itself, in ROM manager, which has successfully installed the same in the past).

I think what might be safest would be to connect to fastboot and flash the new bootloader (dasunsrule32) and CWM 6.0.4.4, and then try to reboot to CM 10.2 that I currently run.

No chance that the new bootloader would fail to boot 10.2?
[Asus Transformer TF700] berndblb:
I suspect you are confusing the Asus Unlock tool version with your bootloader. There is not v8 for the bootloader.

Yeah, and ROM manager also tells you you have the latest CWM version installed with 6.0.3.1 - forget ROM manager!

LMK is right: More than likely than not your bootloader (whatever it is??????) is just fine

And if ROM Manger would tell me the time of day, I would not bet 10 cents on that. More than likely you still have TWRP 2.6.3.2 installed, which is ok!

Sorry if I gave a wrong impression, but TWRP 2.6.3.2 is not LETHAL. There are problems with it if you format data, but for most purposes it should work ok.

Booting into the bootloader should be the first thing you do since it is the pre-requisite for anything that may follow!

LMK is again totally right: Without knowing what bootloader you have, there is no way for us to give you good advice!

Flashing just a bootloader is not that easy and frankly - I am not going to lead you down that path unless absoultley necessary. Flashing a COMPATIBLE recovery and a COMPATIBLE rom should do it.

But how would we know what to tell you if you don't tell us what bootloader you are on?????

And the 10.6.1.14.4 bootloader is not going to be it! Where did you get that info????

To flash CM 11 (which you seem to crave for whatever reason) you have to be on the 10.6.1.4.10 bootloader AND CWM 6.0.4.6 or later (6.0.4.7 has been released - no idea if it's stable)

I think you are running no risk at all by booting into the BL and finding out what version you are running. Just select the Android icon afterwards to boot back into system.

If you insist on flashing a recovery once you boot into the BL, download TWRP 2.6.1. It's been rock solid with this device on almost any bootloader and flash it.

Give us solid info and you get solid advice.....

---------- Post added at 11:09 PM ---------- Previous post was at 11:02 PM ----------

dasunsule provided a new bootloader??? Do you have a link please?
[Galaxy Note 3 Q&A, Help & Troubleshooting] GeneralAdidish:
So I flash 4.4.2 on note 3 and now I have this symbol and the status bar and my battery drains really fast

The picture below is the symbol I'm trying to get rid and think why my battery is draining fast
[Galaxy Note 3 Q&A, Help & Troubleshooting] meti84:
It's "no cellular network coverage" icon...
[Galaxy Note 3 Q&A, Help & Troubleshooting] GeneralAdidish:
Hey

Hey thanks for the responds i was think that it is a factory setting thing because occasionally when i reboot i get a toast notification

And a paragraph flashes and just disappear
[Galaxy Note 3 Q&A, Help & Troubleshooting] radicalisto:
Go to settings > about device and see if you are getting a signal - Check you have a Baseband version in there.
[Galaxy Note 3 Q&A, Help & Troubleshooting] ultramag69:
The reason you're battery is going quick is it's probably continually scanning for network... It's a HUGE battery drain....
[Galaxy Note 3 Q&A, Help & Troubleshooting] GeneralAdidish:
hey what do I do if the baseband is missing

if there is anyway to stop my phone for searching or could i flash any 4.4.2 modem that would be great
[Galaxy Note 3 Q&A, Help & Troubleshooting] radicalisto:
Firstly is your baseband missing? - if not then no need to worry. If so.. then you will need to repair your efs.
[Galaxy Note 3 Q&A, Help & Troubleshooting] GeneralAdidish:
Yes it is missing

How by any chance do i repair my efs
[Galaxy Note 3 Q&A, Help & Troubleshooting] radicalisto:
Follow THIS - It means you'll have to trip KNOX if you haven't already, and install a custom recovery.
[Galaxy Note 3 Q&A, Help & Troubleshooting] GeneralAdidish:
Hey thanks for the link

I don't care about Knox or anything phones this days are very near unbrickable
[Galaxy Note 3 Q&A, Help & Troubleshooting] radicalisto:
Keep that fix on your sd card for future just in case. Efs on the note 3 is notoriously dodgy currently
[Galaxy Note 3 Q&A, Help & Troubleshooting] GeneralAdidish:
Thanks

Hey guys wanted to thanks all of you contributors for helping me get my Note 3 back on track really appreciate it
[Android Themes] deanokidd95:
Hello Everyone!

Today, I would like to announce a sweet new package that I have created, called MI(BADA$$)UI.

This package is for CyanogenMOD Users who love the functionality and speed of CyanogenMOD, but want the overall theme and aesthetics of MIUI :)

I have composed this package of currently 4 (four) market apps that are free on the Play Store, more details available on the official Project Site, mibadassui.net16.net/ :)

Don't Flash too often, Police Infractions will get in the way of that new Android phone you wanted! X'D

Peace,

Deanokidd95
[JAMin, XDA Neo, S200 Software Upgrading] rcnomad:
Bought JAFWM yesterday and here is what I have found:

-Tried flashing New Jamin Rom

Result-Stuck in perpetual reset mode most of the time

When I did manage to get out of the automatic reset loop here is what I found:

1. Radio rom was not installed (=no phone, wifi, bluetooth functionality

2. device had incredibly poor response to any commands (severe lag issues)

3. Basic functionality (even without phone) was very bad

-Tried flashing Qtek Rom

Result-similar as imate (listed above)

1. No radio rom

2. device had better response than imate rom but still poor

Flashed back to shipped dopod 818 pro rom

-Thank God my device returned to normal (radio rom was installed this time)

Conclusion:

I don't think JAFWM can unlock CID (based on my exerience)

If their are any JAFWM experts out there please let me know if there is a way to get the radio rom installed with the new ROMS (ie. QTEK,IMATE)

If JAFWM can't unlock the CID than there is no advantage to using this device other than it's user friendly interface (which is quite easy for unexperienced rom flashers)

Still waiting for Dopod's new rom (that seems to be my only answer for AKU2)
[JAMin, XDA Neo, S200 Software Upgrading] ta_mobile:
I tried flash my Dopod 818 pro to any rom such as Jamin or Qtek S200 by JAFWM and all run well.

You should know when to keep the bootloader and when to skip it.

If you want to play ROM JAMIN in your Dopod 818 pro, do like I did:

1. Use JAFWM downgrade bootloader to 1.0 by flashing Dopod818pro_WWE_1001321_10013102_11320_Ship without skip bootloader.

2. Unlock CID by aWizard. JAFWM will have function unlock soon be sure.

3. If you want to play ROM JAMIN with OS 2.0 do: use JAFWM flash RUU_Prophet_2100728_21007109_020720_QtekDAN_Ship without skip bootloader. Then flash JAMin_WWE_2130923_21309112_020720_ship. Cos as I know, only Qtek Rom can upgrade both IPL and SPL. And Dopod Rom can downgrade both. JAMin can not.

And if you just need to upgrade your radio only, you have to dump it to nba file, then use aWizard burn it to you phone. Cos the package of Prophet ROM always exits with 1 file nk.nbf.

If you use JAFWM mobility with other software, it'll greatly help.

That's my experience, hope your PDA work well :D

BR
[JAMin, XDA Neo, S200 Software Upgrading] raskal:
Re: JAFWM-May not be the answer to flashing difficult prophe

Thanks for the feedback, in case JAFWM have some bug, your post will help me to debug it. It would help me also if you could post here your JAFWMLOG.txt , you can find it in same dir JAFWM.exe is located.

But I will check it also myself and will post result here, but sofar i know there are not any problems known until now. However, i have no NEO i will buy one at monday and play little bit. Maybe os not match bootloader or whatever, but let see after i have my NEO.
[JAMin, XDA Neo, S200 Software Upgrading] rcnomad:
JAFWM-CAN FLASH DIFFICULT PROPHETS>>>IT REALLY WORK

Thanks TA_mobile

I did as you recommended and it worked!

JAFWM does what it is supposed to do...
[JAMin, XDA Neo, S200 Software Upgrading] raskal:
Re: JAFWM-CAN FLASH DIFFICULT PROPHETS>>>IT REALLY

Today played little bit with my Qtek s200. I flashed it with with follow roms:

JAMin_WWE_ 2130923_21309112_020720_ship

RUU_Prophet_1001321_10013102_11320_DopodAsia_Ship

I did not unlock any CID before and all functions was normal. I did it with skipped and witout skipped bootloader flash. If any one have any problem with a secific rom, plz tell me and i will test it.

All this tests we has done with the new version (1.3beta) released today. You can download from http://forums.phone-tools.cn/showthread.php?t=9411 and try it.
[JAMin, XDA Neo, S200 Software Upgrading] Tamagochi:
Hello ta_mobile,

After flashing Dopod ROM into my Xda Neo using JAF without skip IPL/SPL, I got IPL=1.0 and SPL=2.09 and the device stucked at the bootloader mode with 3 colors and could not load the OS. I then flashed Neo with Qtek ROM 2.09 skiping IPL/SPL. My Neo works fine but now I have IPL 1.0 and SPL 2.09, I could not unlock CID using aWizard. Is there any way to get SPL 1.0 and do CID unlock????

Thanks
[JAMin, XDA Neo, S200 Software Upgrading] raskal:
But what is the reason you want upgrade or downgrade your bootloader? I can not get it :?
[JAMin, XDA Neo, S200 Software Upgrading] Zappalapap:
Hello,

i have an German O2 Neo and sometimes Problems with CID unlocking for Flashing. Start aWizard an use the option "e". Then show on youre XDA and start the enablerapi.cab on youre XDA. At next use aWizard with the option unlockCID and test flashing!

With this Method i can backup my Neo with aWizard and flash the new Jamin ROM, the Qtek ROM not. Rebackup to German ROM also OK but only the OS, the BootScreen (SplashScreen) not.

Sry for my miserable english!
[Galaxy Note 3 Q&A, Help & Troubleshooting] covers:
forgive me if this has been solved somewhere else but i have spent nearly 2 hours trying to figure this out but to no avail.

the details of my device are below.

model: SM-900W8

Build: MJ4

Carrier: Rogers

android ver: 4.3

stock rooted

now this all started a month ago i realized the LTE symbol had disappeared. i live in an area with LTE coverage and places where i go that i normally get LTE now i only see a 4G symbol. the most recent changes i have made to the device was installing wanam and xposed installer.

by no means am i suggesting that any of these mods contributed to my loss of LTE, just simply stating the most recent changes i made to the phone before this has happened.

i checked my data/property file and i dont see the persist.radio.lteon file. im not sure if i ever had because i didnt check until i started researching this problem but it would make sense if i did.

anyhow now ive only been getting 4G 3G H+ thats it, no LTE.

in my settings LTE/GSM/WCDMA is selected

anyone have any idea what may have gone wrong?

tia
[Galaxy Note 3 Q&A, Help & Troubleshooting] stokedcrf:
Have you changed roms? Different carriers have different CSC files that contain the icons that you are talking about.

My guess, is the rom you are using says 4G as your LTE. To verify, do a speedtest in an LTE area. Additionally, you can go to SETTINGS>ABOUT>STATUS and look for LTE in the Mobile network type area.

If it says lte, then I wouldn't worry about it. :)
[Galaxy Note 3 Q&A, Help & Troubleshooting] covers:
No I didn't change roms, I'm still on stock rogers MJ4. I used to get the LTE, just all of a sudden for the past month I haven't. It's strange, I haven't performed any mods other than wanam, and xposed.

In settings it shows LTE/GSM/WCDMA selected.

And one thing I know with rogers network is when you're on 4G it's 4G, and LTE is LTE, they are 2 different speeds. And the LTE is not showing. I downloaded some app I think its called vaireo, something like that and it shows I was on LTE14. Not sure what went wrong here
[Galaxy Note 3 Q&A, Help & Troubleshooting] Dahdoul:
Did you uninstall Wanam?
[Galaxy Note 3 Q&A, Help & Troubleshooting] covers:
Yea I uninstalled it rebooted and still the same, strange thing is that in app/property persist.radio.lteon is gone. I believe it's an xml file from what I've been reading. Tbh I can't say for certain that I had that there before but it does make sense to have had it no?
[Galaxy Note 3 Q&A, Help & Troubleshooting] Dahdoul:
I don't know but am pretty sure that Wanam has to do something with the network.

Yesrerday I installed Wanam at 10 PM with Xposed rebooted it. So I noticed after that the time has advanced 1 hour to 11 PM (wrong time),I checked date and time settings and everything was on defualt set on automatic network time and automatic time zone but the zone is changed, werid right?
[Galaxy Note 3 Q&A, Help & Troubleshooting] covers:
Damn that is weird, I mean I was always getting the LTE before, then I started messing around with wanam and the xposed installer and since then i have never seen LTE again
[Galaxy Note 3 Q&A, Help & Troubleshooting] Dahdoul:
Try this go to Xposed >> framework >> uninstall then reboot your phone, if didn't work do a factory reset