yashsingh1/xdaforums huggingface dataset:
[Motorola Droid RAZR] RustyRazr:
Obviously, I'm new to this site, as I imagine most are when they have their first big issue.

Right off the bat, I want to admit that this is solely my fault, and I have been trying to fix it for the past day... To make matters worse, the phone was a gift from my wife for our anniversary, so, I feel pretty bad about it...

The situation:

I rooted my phone yesterday with RazrBlade. I had to do a factory reset to get it to stick, but that was fine. I then installed Boot Menu Manager. I set up the necessary partitions, system_3 system.img (300mb), cache.img (300mb), and data.img (2Gb). I realize I probably should have given system more room... but I didn't think that was app related. I then flashed Liquid-JB-v2.8-OFFICIAL-spyder and gapps-jb-20130301-signed from goo.im. It didn't tell me the system partition was out of memory, so I assumed (like a fool) that everything was OK...

After a few reboots to the wrong system, namely the stock system, I decided to go into BMM and change the default to system_3, and then I did the dumbest thing possible: I thought to myself, "Wow, it would be a pain to see this bootloader each time my phone reboots. I'll turn the delay to 0!" So... I did...

The Problem:

My phone now boots straight past the recovery to system_3, which seems to have no space allocated for applications at all, including system ones. I attached a picture of the storage details. It goes through the setup process each time I reboot, and wipes any changes I make. I can't download apps, and I can't install them via APK because the phone thinks there is no space left. I don't have BMM installed in this system so I can't turn the delay up, to my knowledge. There is no file explorer on this system, so I can't go into the app files directly. I have tried connecting with "Android Commander" but it doesn't want to detect my device. I installed the ADT bundle for windows to get the usb driver, but still nothing... I also tried a factory reset again, but that does the same thing as rebooting for me now.

The Challange:

To my knowledge, I'm out of options, but I know most of you guys do this to see what you are capable of. I'm sure you've dealt with bigger issues. Can anyone help? Would Verizon techs be smart enough/have the right software to actually reset the phone?

Thanks!
[Motorola Droid RAZR] AztekSoul:
I like to see you getting out of that one :) anyway,have you tried switching default storage? I mean try that I think that way the phone "thinks" your external sd is your internal memory and vice versa that might give you a chance to install BMM or a root explorer and debloat system..you got nothing to loose give it a try man,go to settings/advance and switch default storage,good luck.
[Motorola Droid RAZR] RustyRazr:
FIXED!

Unfortunately, I tried that. The problem was that it requires a reboot, which wiped any settings ;)

HOWEVER, the fix was along that line, it just required me to go into android shell and tell it manually.

I followed these steps to make the phone install to the SD card (internal phone app partition really) by default (because I'm a newb, I can't post links, so just google "how-to-install-android-apps-to-the-sd-card-by-default-move-almost-any-app-to-the-sd-card").

After doing so, I still had a problem downloading BMM from the market, but I think that was due to the market being outdated and troublesome, so I had to find an apk version instead.

I installed it, and restored the boot delay to 30 secs.

I then immediately booted to system_1 to feel safe.

I may try loading the Liquid Smooth rom again once I've fixed the partitions, but I will NEVER turn BMM's boot delay to 0 s EVER again...
[One (M7) Q&A, Help & Troubleshooting] dark_polok:
Just wanted to know what happens when you format /system and /preload partitions.

Suppose you format /system from recovery. Can you boot into you ROM after that? Or is that where the ROM was?
[One (M7) Q&A, Help & Troubleshooting] you_eeeeeediot:
If you format /system in recovery you blow away the ROM, definitely cannot boot after that. If you format /data as well, the only way you'll be able to recover is with an ADB sideload.
[One (M7) Q&A, Help & Troubleshooting] dark_polok:
Thanks.

What if I format /system + /data + cache and dalvik chache and then flash a custom rom right after that, without rebooting the phone in any way [meaning not rebooting into system or bootloader or recovery] that should be ok right? Coz I came from a S3 and that combination worked perfectly for it.

Also still have no idea what the /preload partition and formatting it does.
[One (M7) Q&A, Help & Troubleshooting] erikiksaz:
That's what I do when I update within a rom.

Wipe system, cache, dalvik. Flash rom, then wipe cache/dalvik again.

Just a habit after all the different recommendations from previous devs in the past.
[One (M7) Q&A, Help & Troubleshooting] henrybravo:
Yes you can wipe /system, /data and /cache and you're good to flash a ROM, no need to reboot back into recovery again. Dalvik-cache is located on /data, so no need to wipe dalvik when you're wiping data, it's redundant. There is no need to worry about wiping or formatting /preload in almost all situations, otherwise the ROM devs would be telling us to do it. Back in my Galaxy s3 days I remember some ROMs would wipe and flash /preload but I don't think it's a big deal on the One. If it needs to be done, the ROM installation script will handle it.

Most ROM installation scripts wipe /system so it usually isn't necessary to do it yourself. However I do it anyway just to insure a completely clean installation in case the dev's script is messed up (it does happen). Wiping /data is optional of course but it is recommended when changing the base version (for example, 4.1.2 to 4.2.2) or if you're anal like me you can wipe data when upgrading between HTC base versions (2.17 to 2.24 for instance). Some people don't ever wipe /data and don't have any problems, but I can guarantee many of the weird odd-ball issues on this forum could have been prevented with a full wipe.
[One (M7) Q&A, Help & Troubleshooting] dark_polok:
Very helpful replies guys. Thanks =}
[HTC Sensation] wjcarpenter:
I have a Sensation 4G running Android Revolution HD 6.7.2 (bought used, came with, never changed it). I'm generally pretty happy with this situation, but there are two specific situations where it just slows to a crawl. As far as i can recall, it's always been this way for these two situations. (I've been using the phone with this ROM for about a year.)

The first situation is when I install any new app or even an update for an app. For several minutes after that, everything is very sluggish. I can still use the phone, but it's a huge pain. This is true whether or not I try to use the just-installed app or update. My best guess about this (and it's only a guess) is that the slow-down is due to populating the Dalvik cache for the new/updated app. Still, that seems like it ought to be a background thing with only minor impact on foreground performance.

The second situation is when I run the Chrome browser. Other browsers (native, FireFox, Puffin) are just fine. When I run Chrome, things really, really, really tank. When I use the developer option to overlay the load average on the screen, I've seen it go as high as 65. I don't care what kind of phone hardware you have ... if your load average is 65, you are not having a good day. Anyhow, things stay zonked pretty much forever, even if I don't actually do anything in Chrome, and even if it's in the background. I've waited literally hours hoping that something just had to "settle", but no luck. I often resort to a battery pull after Chrome experiments because it's too sluggish to wait for the power button long press. (I have Chrome on a couple other mobile devices, and it behaves just fine there.)

Anybody got any clues about things for me to try to alleviate by undeserved suffering?
[HTC Sensation] malybru:
Hi,

6.7.2 is quite old ,now.

Have you considered upgrading?

7.3 has just come out,with very few problems reported.

What does your bootloader say?

:)
[HTC Sensation] wjcarpenter:
Long ago, on another phone, I was one of those guys who regularly flashed ROMs in chase of ... something (I forget what :) ). Now, I'm just a guy who wants to use his phone every day with the zillion little application customizations and preferences and whatnot. If I decided to endure the pain of setting everything up again (and I'm probably exaggerating that pain in my brain-pan), I'd probably just flash back to stock. Although the ROM might be the problem, the specific nature of the two problems makes me hope/think/wonder that it might be just some setting somewhere that needs a punch in the arm.

Thanks for the suggestion though. Maybe I'll go poke around the changelogs for Android Revolution and see what's to see.
[HTC Sensation] ganeshp:
The first issue is because of our slow internal memory. The stall happening when updating/installing an app is because of long I/O waits :( it probably might happen over other custom roms you try here too but not as long as you said.. I used to have sluggish behavior couple of seconds after app installation (max 10 seconds). Now the only roms which were able to bypass this issue were the sense 4+ jellybean roms viz revelation / viperS 3.1.0 roms. If you want to prevent this annoying issue then change to either of those above roms.. Somehow jellybean roms were able to keep those I/O waits less.

Now to the second issue.. Sensation by default has less ram (yes 768 MB is not enough for ics/JB roms). Now when you fill your device with apps due to true multitasking nature of the Android lots of apps keep on running in the background (even restarting by themselves when killed). And Chrome is one Ram eating b***h it at least needs 50MB of memory (where other browsers like dolphin browser can run smooth over 20MB ram) so it's always slow for me takes ages to open up properly. So my suggestion is switch to different browser or install an app called "greenify" (rooted app.. You need to give root permissions) . The advantage of using this greenify app is it can hibernate persistent apps.. Thus giving you enough ram and battery. Greenify is one acclaimed rooted app which does what it says. Try it and see how the device is doing after this
[HTC Sensation] wjcarpenter:
FWIW, I decided to take the plunge and upgrade to the latest ARHD. At first glance, it seems to have dealt with these two performance items. However, I'm still installing/configuring some of the assorted junk I had before. I'm on the lookout for the one thing that clobbers me and will report here if I find such a thing. (I'm also working through a couple of FCs of system stuff, but that's not for this thread.)
[Nexus 7 Themes and Apps] jr866gooner:
Hello

Bit confused I can't find this app on the N7 in uk? Can quite happy find it on my phone!

Sent from my GS2 running LSW NeatRom
[Nexus 7 Themes and Apps] bunt83:
do you have a 3G Nexus 7?

If not you won't be able to install in to your nexus...
[T-Mobile, Samsung Galaxy SIII] bstylz911:
If I unlock my phone can my company know I'm using a s3?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Sorry, maybe its just me today, but the question just doesn't make sense to me.

Unlocking simply lets you use the phone on another carriers network. How or why would your company care what model your cell is?
[T-Mobile, Samsung Galaxy SIII] bstylz911:
Because when it is not unlocked some companies require you or automatically puts u into a data plan.

So my question -

Can your company detect what phone you are using if it is unlocked?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
When you say "your company" do you mean your carrier or cellular provider, such as T-Mobile or AT&T?

If that's what you mean then yes, they are usually able to tell what kind of phone you are using.
[T-Mobile, Samsung Galaxy SIII] serio22:
I don't think they'll make you get a data plan if you bring your own phone, and can't you cancel the data after a while?
[T-Mobile, Samsung Galaxy SIII] bstylz911:
Cause my company T-Mobile didn't know what phone I was using so they had to ask me.

I'm using an unlocked atnt s3
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Aou:
I've got my RIFFbox, and I've been able to connect to the device just fine. I can send the resurrection to the dead body, but I can't get it to boot to Odin mode still. When connecting to PC, it still shows the QPST download mode (QDL mode). I'm currently trying to flash individual partitions to the device.

Any help or suggestions to get this thing out of QPST mode? :/

Thanks!

I've tried 301k & 619k JIGs also, and several known combinations of keys to boot Odin mode.

UPDATE [7-23-13]:

At this time, I've determined that this device is permanently bricked until I can get my hands on the Kies MF3 Odin package and manually load these files via JTAG. However, even this is not guaranteed to fix it. For the time being, I've replaced the device. I'll hold onto the carcass for a little while longer to see if I can get MF3 to boot on it. If I can, I will use this as a test bed for developers to attempt to unlock bootloaders or develop an MF3 root. Otherwise, I eventually plan to part it out, selling things like the screen, etc.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] AxAtAx:
Did you PM my tech?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Aou:
Yup. No reply yet. :(

Currently flashing the whole 1GB image. Takes forever, so I will let you all know how it goes in a couple hours. I haven't tried flashing the whole MF3 boot chain but it's looking like that's what I will end up needing to try.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] AxAtAx:
I have no doubt you will get it straightened out.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Aou:
:( No go on the full 1GB flash. In a last-ditch effort, I threw the MF3 version of SBL2, SBL3, ABOOT, TZ, and RPM at it.

Still boots to QHUSB_DLOAD mode. :(
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Aou:
This is unbelievably frustrating. No matter what I throw at this thing, it refuses to boot. Also, it seems that the only people that know how to JTAG one of these things are not responding. :(
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Red_81:
Try getting a hold of Josh over at mobile tech videos. I believe he goes by connexion2005 here on XDA.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Aou:
Thank you, but he was the first person I tried contacting. Seems to ignore my PMs, or just doesn't have the time? :(
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Red_81:
He's pretty busy most Days. His business takes up most of his time.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Devo7v:
Have you tried contacting [MENTION=3682533]AdamOutler[/MENTION]? If I remember from the early Captivate days he worked with Josh to get the JTAG stuff working. He's definitely very knowledgeable when it comes to Samsung hardware.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] AdamOutler:
I'm pretty sure you need a JTAG flash with an up to date firmware. There was someone else who's device refused to boot and he managed to unbrick with software. I take it that this is due to messing with bootloaders and trying to revert? btw... quote or mention usually gets my attention.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Aou:
... :D - didn't try - last I knew he didn't accept PMs. ;)

Yes, this is from flashing MF3 Sbl2 and Sbl3 (without aboot and tz). I've tried flashing the whole MF3 bootchain, and it still doesn't like it. Still boots to QPST mode.

EDIT/ADD:

At this point, I've flashed these:

PGPT (and SGPT) from the 1GB "full dump" provided by riffbox (assuming MDB or MDL - it was released 7/3/13)

PIT from the forums around here somewhere (seems identical to one from dump)

MD5 from dump

(empty area) from dump

apnhlos (aka non-hlos) from MF3

MDM from MF3

sbl1 from AdamOutler's MDB dump

sbl2 from MF3

sbl3 from MF3

aboot from MF3

rpm from MF3

tz from MF3
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Aou:
Yeah, tried it all again, for good measure. Starting to wonder if this thing is completely and utterly bricked? It makes no logical sense. Something is still triggering it to enter QPST mode. Again, I've tried using 301k (and a few other) Ohm resistance JIGs to try booting immediately the flash. Nada. Using the 4.2v power supply from the Riffbox, tried USB power (kinda difficult to flash things solderless when the daughterboard is attached, but possible), tried battery power only... All appear to work fine in Riff, all allow me to read and write any address I want.

I'm about to the point where I'm going to scrap this for parts to help get a new one. :/
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] jetlitheone:
Could sell for parts for around 300 or so ?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] AxAtAx:
Adam is right, you did get the newest firmware they have online right?

Did Derek get hold of you? I had him busy at work today, he had to load 50+ laptops with win 7, big money involved, I will IM him for you.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] BeansTown106:
[MENTION=3682533]AdamOutler[/MENTION] [MENTION=1124755]Aou[/MENTION]

same exact thing happened to me i did the same thing with the verizon update and sent it out to josh @ mobiletechvideos.com

just got my device back today and its still Bricked !?!?!?!? either josh and his guys just failed to test it or there is no way to fix these phones :(

1. this really pisses me off i sent it to the most reputable guy in the buisness and got it back in this condition.

2. for the odd case that its just a complete loss i have one thing to say to samsung, vzw, att....

basically moral of the story is i wouldnt sell your phone for parts to get another wait until i/we hear back from mobiletechvideo then sell you device and never buy a samsung device again as long as it is locked
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] AdamOutler:
I've been a diehard Samsung supporter since the GS1 came out. The hardware quality is awesome. Unfortunately, their policies are beginning to become unfriendly for developers. The issue you're having is due 100% to Samsung's desire to lock people out of custom kernels.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Airtioteclint:
Isn't it AT&T and VZW who are locking it?
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Aou:
I got the latest firmware that I could find - but it's dated 7-3-13 (a week before the MF3 patch). Does Kies have MF3 yet? I might be able to live with MF3 if I were able to retain a custom recovery and therefore root (via injection). It'd mean no custom ROMs until a new "Loki" (or equivalent) is made, or we get these blasted bootloaders unlocked.

I would REALLY like to hear what the deal was with mobiletechvideos.com & [MENTION=1602851]connexion2005[/MENTION] has to say about our situation here. My plan was to cut my losses on Monday if I am not able to get it fixed this weekend. This is really crazy news for me - Josh is indeed the most reputable JTAG guy in the industry (afaik). For them to send that back still bricked is a really bad sign! (Makes my situation look pretty much hopeless!)

Indeed, I've had the Infuse, S2, and now the S4. I love Samsung's handsets, and I traditionally loved how much modification you could do to these handsets to customize them. However, with locked bootloaders and such, this is becoming quite the joke - and the joke's on us, it seems.

----------

As an update to my situation, I haven't tried anything new since my last post. Still waiting to find new ideas or hear some suggestions.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] RockRatt:
I screwed up my S4 recently and it was being fixed (hopefully) from MobileTechVideos. Josh is really a good guy and back in my S1 Cappy days I had to send one to him. We chatted on the phone about android stuff quite a bit back then.

So I screwed up the kernel I believe trying to make a kernel splash screen, flashed in recovery and when it rebooted I just got a vibration every 3-5 seconds. Tried Odin MDB and MDL firmware with both always passing. But still same results when it went to reboot.

Now seeing this comment you made has me actually worried now. Have you contacted them about it still being bricked yet? Or did they send it back with refunding the charges since it wouldn't work? Crap it I f'ed it over after only 1 week of having it and it cannot be resurrected. Now I know my situation is different as I have NOT messed with anything from MF3 at all. But if something else is going on inside that MobileTechVideos couldn't fix has me worried.

Also [MENTION=4058151]Adam[/MENTION], I feel the same way about the quality of the Galaxy lines as I have had the S1,S2, S3, and now S4. But I am seeing the writing on the wall with Samsung and ATT showing me this COULD BE my last of them.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] jeboo:
Damn, it looks like a little reversing is going to be needed to figure out what's holding up the recovery process. I'm more than willing to help, although I can't do much beyond dead-list analysis since I don't have a JTAG.

I think at this point the goal is to get MF3 booting and ebay ASAP for a tmobile/i9505. This BL fiasco has seriously soured this phone. The devs are pissed and the user base is limited, guess it's time to move on..:mad:
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] BeansTown106:
i hear ya fully. my first was the s3 but because i liked it so much i have gotten the note2 and now the s4. obviously all locked because of verizon.. and samsung i guess :( on the s3 we were lucky because of the leaked prerelease aboot, the note2 you and ralekdev just anniahlated :highfive: and the s4.. is just another story we have not one but 3 leaked prerelease aboots on verizon and still nothing. i feel ya though i love the quality of samsung over any other oem but them letting verizon/att dictate thier policies on locking the phones down is getting rediculious

ya from what i assume they are doing it at the request of the carriers. i dont think they are fully doing it themselves because thier main phones aka i9500, i9505 are completely unlocked as well as all thier wifi tablets etc. the only time anything ends up locked was when verizon got thier hands on it. aka s3, note2, s4, note10, gtab2 7.0 and now att is following suit

my guess is the possible only way to fix it would be to use the mf3 firmware(you should be able to snag it from kies) but even at that point i dont know. also with mf3 there is currently no way of running a custom recovery or using loki etc. at this point the only way of obtaining root released to the public is using ota rootkeeper and taking the update via the ota method instead of the kies method.

on the mobile tech videos front i have no idea whats going on they havent replied to any of my messages etc. or even sent me a "status" update but when i recieved my phone yesterday it was in the exact same condition it was when i sent it other than it had a download mode jig taped to it lol. my buddy invisiblek had the same thing happen to his vzw version and Mobile tech has it so we will see what happens to his phone. my first experience with mobile tech about a year ago was excellent but i dont know whats going on here.. with no communication at all its kinda annoying. at least a message saying the new ota's for att/vzw are making jtag impossible at the moment.

on the plus side i called and complained to verizon and they are sending me a new phone. maybe try that with att?

will probably sell it and get the dev edition and wait til my contract is up then move to tmobile or sprint. possibly att? do you guys know if international variants work well with att? from my research i dont think so but i could be wrong
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Aou:
My only issue with trying this with AT&T, is that there are very slight little etch marks on/around the JTAG pads, thanks to my [countless] attempts to resurrect this thing. I'd be concerned that if I sent it in, they'd find this and blame me.

What exactly did you tell Verizon? Also, congrats. :)